CINXE.COM

<!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="Bikeshed version 29c533fbc, updated Mon Oct 23 12:41:25 2023 -0700" name="generator"> <link href="https://www.w3.org/policies/process/" rel="canonical"> <meta content="80cac31c369377b5df60b4dab69f55f680d3f4d8" 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); --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-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> <link href="https://www.w3.org/StyleSheets/TR/2021/base" rel="stylesheet"> <body class="h-entry"> <div class="head"> <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> <h1 class="p-name no-ref" id="title">W3C Process Document</h1> <time class="dt-updated" datetime="2023-11-03">3 November 2023</time> <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/20231103/">https://www.w3.org/policies/process/20231103/</a> <dt>Latest published version: <dd><a href="https://www.w3.org/policies/process/">https://www.w3.org/policies/process/</a> <dt>Editor's Draft: <dd><a href="https://www.w3.org/policies/process/drafts/">https://www.w3.org/policies/process/drafts/</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> (Apple) <dd class="editor p-author h-card vcard"><a class="p-name fn u-url url" href="https://florian.rivoal.net/">Florian Rivoal</a> (Invited Expert) <dt class="editor">Former Editors: <dd class="editor p-author h-card vcard">Natasha Rooney (Invited Expert) <dd class="editor p-author h-card vcard"><a class="p-name fn u-url url" href="http://yandex.com">Charles McCathie Nevile</a> (Yandex) <dd class="editor p-author h-card vcard"><a class="p-name fn u-url url" href="https://www.w3.org/">Ian Jacobs</a> (W3C) </dl> </div> </details> <div data-fill-with="warning"></div> <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>® <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. <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">Abstract</h2> 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. 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>. </div> <h2 class="no-num no-toc no-ref heading settled" id="sotd">Status of this document</h2> <div data-fill-with="status"> Status Update (June 2024): The links to this version of the process document, its latest version and the editor's draft have been updated and are now located in the policies section of the website. This document is the <a href="https://www.w3.org/policies/process/20231103/">3 November 2023 Process</a>. 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. 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). A <a href="#changes">history of substantial changes</a> from previous versions of the Process Document is provided. </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">1 Introduction</a> <li> <a href="#Organization">2 Members and the Team</a> <ol class="toc"> <li> <a href="#Members">2.1 Members</a> <ol class="toc"> <li><a href="#MemberBenefits">2.1.1 Rights of Members</a> <li> <a href="#RelatedAndAssociatedMembers">2.1.2 Member Associations and Related Members</a> <ol class="toc"> <li><a href="#MemberAssoc">2.1.2.1 Membership Associations</a> <li><a href="#MemberRelated">2.1.2.2 Related Members</a> </ol> </ol> <li><a href="#Team">2.2 The W3C Team</a> </ol> <li> <a href="#groups">3 Groups and Participation</a> <ol class="toc"> <li> <a href="#Policies">3.1 Policies for Participation in W3C Groups</a> <ol class="toc"> <li> <a href="#ParticipationCriteria">3.1.1 Individual Participation Criteria</a> <ol class="toc"> <li><a href="#discipline">3.1.1.1 Expectations and Discipline</a> <li><a href="#coi">3.1.1.2 Conflict of Interest Policy</a> <li><a href="#member-rep">3.1.1.3 Individuals Representing a Member Organization</a> </ol> <li> <a href="#GeneralMeetings">3.1.2 Meetings</a> <ol class="toc"> <li><a href="#meeting-schedules">3.1.2.1 Meeting Scheduling and Announcements</a> <li><a href="#meeting-minutes">3.1.2.2 Meeting Minutes</a> <li><a href="#meeting-recording">3.1.2.3 Meeting Recordings and Transcripts</a> </ol> <li><a href="#tooling">3.1.3 Tooling and Archiving for Discussions and Publications</a> <li><a href="#resignation">3.1.4 Resignation from a Group</a> </ol> <li> <a href="#AC">3.2 The Advisory Committee (AC)</a> <ol class="toc"> <li><a href="#ac-role">3.2.1 Role of the Advisory Committee</a> <li><a href="#ac-participation">3.2.2 Participation in the Advisory Committee</a> <li><a href="#ACCommunication">3.2.3 Advisory Committee Mailing Lists</a> <li><a href="#ACMeetings">3.2.4 Advisory Committee Meetings</a> </ol> <li> <a href="#elected-groups">3.3 Elected Groups: The AB and the TAG</a> <ol class="toc"> <li> <a href="#AB">3.3.1 Advisory Board (AB)</a> <ol class="toc"> <li><a href="#ab-role">3.3.1.1 Role of the Advisory Board</a> <li><a href="#ABParticipation">3.3.1.2 Composition of the Advisory Board</a> <li><a href="#ab-comm">3.3.1.3 Communications of the Advisory Board</a> <li><a href="#ab-bod-liaison">3.3.1.4 Liaisons between the Advisory Board and the Board of Directors</a> </ol> <li> <a href="#TAG">3.3.2 Technical Architecture Group (TAG)</a> <ol class="toc"> <li><a href="#tag-role">3.3.2.1 Role of the Technical Architecture Group</a> <li><a href="#tag-participation">3.3.2.2 Composition of the Technical Architecture Group</a> <li><a href="#tag-comm">3.3.2.3 Communications of the Technical Architecture Group</a> </ol> <li> <a href="#AB-TAG-participation">3.3.3 Participation in Elected Groups</a> <ol class="toc"> <li><a href="#elected-expectations">3.3.3.1 Expectations for Elected Groups Participants</a> <li><a href="#AB-TAG-constraints">3.3.3.2 Elected Groups Participation Constraints</a> <li><a href="#AB-TAG-elections">3.3.3.3 Advisory Board and Technical Architecture Group Elections</a> <li><a href="#TAG-appointments">3.3.3.4 Technical Architecture Group Appointments</a> <li><a href="#random">3.3.3.5 Verifiable Random Selection Procedure</a> <li><a href="#AB-TAG-vacated">3.3.3.6 Elected Groups Vacated Seats</a> </ol> </ol> <li> <a href="#GAGeneral">3.4 Chartered Groups: Working Groups and Interest Groups</a> <ol class="toc"> <li><a href="#ReqsAllGroups">3.4.1 Requirements for All Chartered Groups</a> <li><a href="#group-participation">3.4.2 Participation in Chartered Groups</a> <li> <a href="#chartered-group-participants">3.4.3 Types of Participants in Chartered Groups</a> <ol class="toc"> <li><a href="#member-rep-wg">3.4.3.1 Member Representative in a Working Group</a> <li><a href="#member-rep-ig">3.4.3.2 Member Representative in an Interest Group</a> <li><a href="#invited-expert-wg">3.4.3.3 Invited Expert in a Working Group</a> <li><a href="#invited-expert-ig">3.4.3.4 Invited Expert in an Interest Group</a> <li><a href="#team-rep-wg">3.4.3.5 Team Representative in a Working Group</a> <li><a href="#team-rep-ig">3.4.3.6 Team Representative in an Interest Group</a> </ol> </ol> </ol> <li> <a href="#group-lifecyle">4 Lifecycle of Chartered Groups</a> <ol class="toc"> <li><a href="#WGCharterDevelopment">4.1 Initiating Charter Development</a> <li><a href="#WGCharter">4.2 Content of a Charter</a> <li><a href="#CharterReview">4.3 Advisory Committee Review of a Charter</a> <li><a href="#cfp">4.4 Call for Participation in a Chartered Group</a> <li><a href="#charter-extension">4.5 Charter Extension</a> <li><a href="#GeneralTermination">4.6 Chartered Group Closure</a> </ol> <li> <a href="#decisions">5 Decisions</a> <ol class="toc"> <li><a href="#decision-types">5.1 Types of Decisions</a> <li> <a href="#consensus-building">5.2 Consensus Building</a> <ol class="toc"> <li><a href="#Consensus">5.2.1 Consensus</a> <li><a href="#managing-dissent">5.2.2 Managing Dissent</a> <li><a href="#Votes">5.2.3 Deciding by Vote</a> </ol> <li><a href="#formal-address">5.3 Formally Addressing an Issue</a> <li><a href="#WGChairReopen">5.4 Reopening a Decision When Presented With New Information</a> <li><a href="#registering-objections">5.5 Registering Formal Objections</a> <li> <a href="#addressing-fo">5.6 Addressing Formal Objections</a> <ol class="toc"> <li><a href="#team-fo-mediation">5.6.1 Investigation and Mediation by the Team</a> <li> <a href="#council">5.6.2 W3C Council</a> <ol class="toc"> <li><a href="#council-composition">5.6.2.1 Council Composition</a> <li><a href="#council-delegation">5.6.2.2 Extraordinary Delegation</a> <li><a href="#council-participation">5.6.2.3 Council Participation, Dismissal, and Renunciation</a> <li><a href="#council-short-circuit">5.6.2.4 Unanimous Short Circuit</a> <li><a href="#council-chairing">5.6.2.5 Council Chairing</a> <li><a href="#council-deliberations">5.6.2.6 Council Deliberations</a> <li><a href="#council-decision">5.6.2.7 Council Decision Report</a> <li><a href="#council-appeals">5.6.2.8 Appealing Council Decisions</a> </ol> </ol> <li> <a href="#ACReview">5.7 Advisory Committee Reviews</a> <ol class="toc"> <li><a href="#ACReviewStart">5.7.1 Start of a Review Period</a> <li><a href="#ACReviewAfter">5.7.2 After the Review Period</a> </ol> <li><a href="#ACVotes">5.8 Advisory Committee Votes</a> <li><a href="#ACAppeal">5.9 Appeal by Advisory Committee Representatives</a> </ol> <li> <a href="#Reports">6 W3C Technical Reports</a> <ol class="toc"> <li><a href="#recs-and-notes">6.1 Types of Technical Reports</a> <li> <a href="#general-requirements">6.2 General Requirements for Technical Reports</a> <ol class="toc"> <li><a href="#publication">6.2.1 Publication of Technical Reports</a> <li> <a href="#doc-reviews">6.2.2 Reviews and Review Responsibilities</a> <ol class="toc"> <li><a href="#wide-review">6.2.2.1 Wide Review</a> </ol> <li><a href="#correction-classes">6.2.3 Classes of Changes</a> <li><a href="#errata">6.2.4 Errata Management</a> <li><a href="#candidate-amendments">6.2.5 Candidate Amendments</a> <li><a href="#contributor-license">6.2.6 License Grants from Non-Participants</a> </ol> <li> <a href="#rec-track">6.3 The W3C Recommendation Track</a> <ol class="toc"> <li><a href="#maturity-stages">6.3.1 Maturity Stages on the Recommendation Track</a> <li><a href="#implementation-experience">6.3.2 Implementation Experience</a> <li><a href="#transition-reqs">6.3.3 Advancement on the Recommendation Track</a> <li> <a href="#update-reqs">6.3.4 Updating Mature Publications on the Recommendation Track</a> <ol class="toc"> <li><a href="#streamlined-update">6.3.4.1 Streamlined Publication Approval</a> </ol> <li><a href="#first-wd">6.3.5 Publishing a First Public Working Draft</a> <li><a href="#revising-wd">6.3.6 Revising a Working Draft</a> <li><a href="#transition-cr">6.3.7 Transitioning to Candidate Recommendation</a> <li> <a href="#revising-cr">6.3.8 Revising a Candidate Recommendation</a> <ol class="toc"> <li><a href="#publishing-crrs">6.3.8.1 Publishing a Candidate Recommendation Snapshot</a> <li><a href="#publishing-crud">6.3.8.2 Publishing a Candidate Recommendation Draft</a> </ol> <li><a href="#transition-pr">6.3.9 Transitioning to Proposed Recommendation</a> <li><a href="#transition-rec">6.3.10 Transitioning to W3C Recommendation</a> <li> <a href="#revising-rec">6.3.11 Revising a W3C Recommendation</a> <ol class="toc"> <li><a href="#revised-rec-markup">6.3.11.1 Revising a Recommendation: Markup Changes</a> <li><a href="#revised-rec-editorial">6.3.11.2 Revising a Recommendation: Editorial Changes</a> <li><a href="#revised-rec-substantive">6.3.11.3 Revising a Recommendation: Substantive Changes</a> <li><a href="#revised-rec-features">6.3.11.4 Revising a Recommendation: New Features</a> <li><a href="#change-review">6.3.11.5 Incorporating Candidate Amendments</a> </ol> <li><a href="#rec-track-regression">6.3.12 Regression on the Recommendation Track</a> <li> <a href="#tr-end">6.3.13 Retiring Recommendation Track Documents</a> <ol class="toc"> <li><a href="#abandon-draft">6.3.13.1 Abandoning an Unfinished Recommendation</a> <li><a href="#rescind-cr">6.3.13.2 Rescinding a Candidate Recommendation</a> <li><a href="#rec-rescind">6.3.13.3 Abandoning a W3C Recommendation</a> <li><a href="#deactivation">6.3.13.4 Process for Rescinding, Obsoleting, Superseding, Restoring a Recommendation</a> </ol> </ol> <li> <a href="#note-track">6.4 The Note Track (Notes and Statements)</a> <ol class="toc"> <li><a href="#Note">6.4.1 Group Notes</a> <li><a href="#publishing-notes">6.4.2 Publishing Notes</a> <li><a href="#w3c-statement">6.4.3 Elevating Group Notes to W3C Statement status</a> <li><a href="#revising-memo">6.4.4 Revising W3C Statements</a> </ol> <li> <a href="#registries">6.5 The Registry Track</a> <ol class="toc"> <li><a href="#reg-def">6.5.1 Registry Definitions</a> <li><a href="#reg-pub">6.5.2 Publishing Registries</a> <li><a href="#reg-table-update">6.5.3 Updating Registry Tables</a> <li><a href="#reg-data-reports">6.5.4 Registry Data Reports</a> <li><a href="#reg-ref-specifications">6.5.5 Specifications that Reference Registries</a> </ol> <li><a href="#switching-tracks">6.6 Switching Tracks</a> <li><a href="#further-reading">6.7 Further reading</a> </ol> <li> <a href="#dissemination">7 Dissemination Policies</a> <ol class="toc"> <li><a href="#pub-com">7.1 Public Communication</a> <li><a href="#confidentiality-levels">7.2 Confidentiality Levels</a> <li><a href="#confidentiality-change">7.3 Changing Confidentiality Level</a> </ol> <li><a href="#GAEvents">8 Workshops and Symposia</a> <li><a href="#Liaisons">9 Liaisons</a> <li> <a href="#Submission">10 Member Submission Process</a> <ol class="toc"> <li> <a href="#SubmissionRights">10.1 Submitter Rights and Obligations</a> <ol class="toc"> <li><a href="#SubmissionScope">10.1.1 Scope of Member Submissions</a> <li><a href="#SubmissionReqs">10.1.2 Information Required in a Submission Request</a> </ol> <li><a href="#TeamSubmissionRights">10.2 Team Rights and Obligations</a> <li><a href="#SubmissionYes">10.3 Acknowledgment of a Submission Request</a> <li><a href="#SubmissionNo">10.4 Rejection of a Submission Request, and Submission Appeals</a> </ol> <li><a href="#GAProcess">11 Process Evolution</a> <li><a href="#acks">12 Acknowledgments</a> <li> <a href="#changes">13 Changes</a> <ol class="toc"> <li><a href="#changes-2023-1"> Changes since the 12 June 2023 Process</a> <li><a href="#changes-previous"> Changes since earlier versions</a> </ol> <li> <a href="#index"> Index</a> <ol class="toc"> <li><a href="#index-defined-here"> Terms defined by this specification</a> <li><a href="#index-defined-elsewhere"> Terms defined by reference</a> </ol> <li> <a href="#references"> References</a> <ol class="toc"> <li><a href="#normative"> Normative References</a> <li><a href="#informative"> Informative References</a> </ol> </ol> </nav> <main> <h2 class="no-num no-toc no-ref heading settled" id="pp"> 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> <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. 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. In the Process Document, the term “participant” refers to an individual, not an organization. <h2 class="no-num no-toc no-ref heading settled" id="terms"> Conformance and specialized terms</h2> The terms must, must not, should, should not, required, and may 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">not required<a class="self-link" href="#not-required"></a></dfn> is equivalent to the term may 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>. Some terms have been capitalized in this document (and in other W3C materials) to indicate that they are entities with special relevance to the W3C Process. These terms are defined within this document, and readers are reminded that the ordinary English definitions are insufficient for the purpose of understanding this document. <nav data-fill-with="table-of-contents"></nav> <h2 class="heading settled" data-level="1" id="Intro">1. Introduction<a class="self-link" href="#Intro"></a></h2> W3C work revolves around the standardization of Web technologies. To accomplish this work, W3C follows processes that promote the development of high-quality standards based on the <a href="#Consensus">consensus</a> of the Membership, Team, and public. W3C processes promote fairness, responsiveness, and progress: all facets of the W3C mission. This document describes the processes W3C follows in pursuit of its mission. The W3C Process promotes the goals of quality and fairness in technical decisions by encouraging <a href="#Consensus">consensus</a>, soliciting reviews (by both Members and public), incorporating implementation and interoperability experience, and requiring Membership-wide approval as part of the <a href="#Reports">technical report development process</a>. <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. 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>. In addition, several groups are formally established by the Consortium: the <a href="#AC">W3C Advisory Committee</a>, which has a representative from each Member, and two oversight groups elected by its membership: the <a href="#AB">Advisory Board (AB)</a>, which helps resolve Consortium-wide non-technical issues and manages the <a href="#GAProcess">evolution of the W3C process</a>; and the <a href="#TAG">Technical Architecture Group (TAG)</a>, which helps resolve Consortium-wide technical issues. Here is a general overview of how W3C initiates standardization of a Web technology: <ol> <li> People generate interest in a particular topic. For instance, Members express interest by developing proposals in Community Groups or proposing ideas in <a href="#Submission">Member Submissions</a>. Also, the <a href="#Team">Team</a> monitors work inside and outside of W3C for signs of interest, and helps organize <a href="#GAEvents">Workshops</a> to bring people together to discuss topics that interest the W3C community. <li> When there is enough interest and an engaged community, the <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> 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>). <h2 class="heading settled" data-level="2" id="Organization">2. Members and the Team<a class="self-link" href="#Organization"></a></h2> 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. <h3 class="heading settled" data-level="2.1" id="Members">2.1. Members<a class="self-link" href="#Members"></a></h3> <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: <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> 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> must 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. While W3C does not have a class of membership tailored to individuals, individuals may join W3C. Restrictions pertaining to <a href="#MemberRelated">related Members</a> apply when the individual also <a href="#member-rep">represents</a> another W3C Member. <h4 class="heading settled" data-level="2.1.1" id="MemberBenefits">2.1.1. Rights of Members<a class="self-link" href="#MemberBenefits"></a></h4> Each Member organization enjoys the following rights and benefits: <ul> <li> A seat on the <a href="#AC">Advisory Committee</a>; <li> Access to <a href="#Member-only" 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> Furthermore, subject to further restrictions included in the Member Agreement, representatives of Member organizations participate in W3C as follows: <ul> <li> In <a href="#GAGeneral">Working Groups and Interest Groups</a>. <li> In <a href="#GAEvents">Workshops and Symposia</a>; <li> On the Team, as <a href="#fellows" id="ref-for-fellows">W3C Fellows</a>. </ul> 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>. 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>. <h4 class="heading settled" data-level="2.1.2" id="RelatedAndAssociatedMembers">2.1.2. Member Associations and Related Members<a class="self-link" href="#RelatedAndAssociatedMembers"></a></h4> <h5 class="heading settled" data-level="2.1.2.1" id="MemberAssoc">2.1.2.1. Membership Associations<a class="self-link" href="#MemberAssoc"></a></h5> 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. <a data-link-type="dfn" href="#member-association" id="ref-for-member-association④">Member Associations</a> may also designate up to four (or more at the Team’s discretion) individuals who, though not employed by the organization, may exercise the rights of <a href="#member-rep">Member representatives</a>. 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 must disclose their employment affiliation when participating in W3C work. Provisions for <a href="#MemberRelated">related Members</a> apply. Furthermore, these individuals must represent the broad interests of the W3C Member organization and not the particular interests of their employers. For Member Associations that have organizations as Members, all such designated representatives must be an official representative of the Member organization (e.g. a Committee or Task Force Chairperson) and must disclose their employment affiliation when participating in W3C work. Provisions for <a href="#MemberRelated">related Members</a> apply. Furthermore, these individuals must represent the broad interests of the W3C Member organization and not the particular interests of their employers. For all representatives of a Member Association, IPR commitments are made on behalf of the Member Association, unless a further IPR commitment is made by the individuals' employers. <h5 class="heading settled" data-level="2.1.2.2" id="MemberRelated">2.1.2.2. Related Members<a class="self-link" href="#MemberRelated"></a></h5> In the interest of ensuring the integrity of the consensus process, Member involvement in some of the processes in this document is affected by related Member status. As used herein, two Members are <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="Related Member" id="related-member">related</dfn> if: <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> 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. <a data-link-type="dfn" href="#related-member" id="ref-for-related-member">Related Members</a> must 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>. <h3 class="heading settled" data-level="2.2" id="Team">2.2. The W3C Team<a class="self-link" href="#Team"></a></h3> 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. The CEO may 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>. 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. Note: 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. <h2 class="heading settled" data-level="3" id="groups">3. Groups and Participation<a class="self-link" href="#groups"></a></h2> 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. <h3 class="heading settled" data-level="3.1" id="Policies">3.1. Policies for Participation in W3C Groups<a class="self-link" href="#Policies"></a></h3> <h4 class="heading settled" data-level="3.1.1" id="ParticipationCriteria">3.1.1. Individual Participation Criteria<a class="self-link" href="#ParticipationCriteria"></a></h4> <h5 class="heading settled" data-level="3.1.1.1" id="discipline">3.1.1.1. Expectations and Discipline<a class="self-link" href="#discipline"></a></h5> There are three qualities an individual is expected to demonstrate in order to participate in W3C: <ol> <li> Technical competence in one’s role; <li> The ability to act fairly; <li> Social competence in one’s role. </ol> <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. Participants in any W3C activity must 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>. The <a data-link-type="dfn" href="#ceo" id="ref-for-ceo②">CEO</a> may 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>. <h5 class="heading settled" data-level="3.1.1.2" id="coi">3.1.1.2. Conflict of Interest Policy<a class="self-link" href="#coi"></a></h5> Individuals participating materially in W3C work must 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 must be kept up-to-date as the individual’s affiliations change and W3C membership evolves (since, for example, the individual might have a relationship with an organization that joins or leaves W3C). Each section in this document that describes a W3C group provides more detail about the disclosure mechanisms for that group. The ability of an individual to fulfill a role within a group without risking a conflict of interest depends on the individual’s affiliations. When these affiliations change, the individual’s assignment to the role must be evaluated. The role may be reassigned according to the appropriate process. For instance, the <a data-link-type="dfn" href="#team" id="ref-for-team⑤">Team</a> may 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). The following are some scenarios where disclosure is appropriate: <ul> <li> Paid consulting for an organization whose activity is relevant to W3C, or any consulting compensated with equity (shares of stock, stock options, or other forms of corporate equity). <li> A decision-making role/responsibility (such as participating on a Board) in other organizations relevant to W3C. <li> A position on a publicly visible advisory body, even if no decision-making authority is involved. </ul> Individuals seeking assistance on these matters should contact the <a data-link-type="dfn" href="#team" id="ref-for-team⑥">Team</a>. <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>. <h5 class="heading settled" data-level="3.1.1.3" id="member-rep">3.1.1.3. Individuals Representing a Member Organization<a class="self-link" href="#member-rep"></a></h5> 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> may designate a non-employee to represent the Member. Non-employee Member representatives must disclose relevant affiliations to the Team and to any group in which the individual participates. In exceptional circumstances (e.g., situations that might jeopardize the progress of a group or create a <a href="#coi">conflict of interest</a>), the <a data-link-type="dfn" href="#ceo" id="ref-for-ceo③">CEO</a> may decline to allow an individual designated by an Advisory Committee representative to participate in a group. A group charter may limit the number of individuals representing a W3C Member (or group of <a href="#MemberRelated">related Members</a>). <h4 class="heading settled" data-level="3.1.2" id="GeneralMeetings">3.1.2. Meetings<a class="self-link" href="#GeneralMeetings"></a></h4> 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>. W3C distinguishes two types of meetings: <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> A <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs①">Chair</a> may 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. <h5 class="heading settled" data-level="3.1.2.1" id="meeting-schedules">3.1.2.1. Meeting Scheduling and Announcements<a class="self-link" href="#meeting-schedules"></a></h5> Meeting announcements should be sent to all appropriate group mailing lists, i.e. those most relevant to the anticipated meeting participants. The following table lists recommendations for organizing a meeting: <table class="data"> <thead> <tr> <td> <th scope="col">Face-to-face meetings <th scope="col">Distributed meetings <tbody> <tr> <th scope="row">Meeting announcement (before) <td>eight weeks* <td>one week* <tr> <th scope="row">Agenda available (before) <td>two weeks <td>24 hours (or longer if a meeting is scheduled after a weekend or holiday) <tr> <th scope="row">Participation confirmed (before) <td>three days <td>24 hours <tr> <th scope="row">Action items available (after) <td>three days <td>24 hours <tr> <th scope="row"><a data-link-type="dfn" href="#minutes" id="ref-for-minutes">Minutes</a> available (after) <td>two weeks <td>48 hours </table> * 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. <h5 class="heading settled" data-level="3.1.2.2" id="meeting-minutes">3.1.2.2. Meeting Minutes<a class="self-link" href="#meeting-minutes"></a></h5> Groups should take and retain <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="minutes">minutes</dfn> of their meetings, and must 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. <h5 class="heading settled" data-level="3.1.2.3" id="meeting-recording">3.1.2.3. Meeting Recordings and Transcripts<a class="self-link" href="#meeting-recording"></a></h5> No-one may take an audio or video recording of a meeting, or retain an automated transcript, unless the intent is announced at the start of the meeting, and no-one participating in the recorded portion of the meeting withholds consent. If consent is withheld by anyone, recording/retention must not occur. The announcement must cover: (a) who will have access to the recording or transcript and (b) the purpose/use of it and (c) how it will be retained (e.g. privately, in a cloud service) and for how long. <h4 class="heading settled" data-level="3.1.3" id="tooling">3.1.3. Tooling and Archiving for Discussions and Publications<a class="self-link" href="#tooling"></a></h4> 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: <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) should 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 should 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 must 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 should be. This includes discussions conducted over email lists or in issue-tracking services or any equivalent fora. Materials referenced from discussions and necessary to understand them should be available at a stable URL, at a level of confidentiality no stricter than the discussion minutes. Note: The lack, or loss, of such archives does not by itself invalidate an otherwise-valid decision. <li id="tool-accessibility"> <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 should be usable (without additional cost) by all who wish to participate, including people with disabilities, to allow their effective participation. Note: If a new participant joins who cannot use the tool, this can require the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG②">Working Group</a> to change its tooling or operate some workaround. <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 should be documented such that new participants and observers can easily find the group’s tools and records. </ul> 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. <h4 class="heading settled" data-level="3.1.4" id="resignation">3.1.4. Resignation from a Group<a class="self-link" href="#resignation"></a></h4> A W3C Member or Invited Expert may 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> must 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. <h3 class="heading settled" data-level="3.2" id="AC">3.2. The Advisory Committee (AC)<a class="self-link" href="#AC"></a></h3> <h4 class="heading settled" data-level="3.2.1" id="ac-role">3.2.1. Role of the Advisory Committee<a class="self-link" href="#ac-role"></a></h4> 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: <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> <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative②">Advisory Committee representatives</a> may 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. 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>. <h4 class="heading settled" data-level="3.2.2" id="ac-participation">3.2.2. Participation in the Advisory Committee<a class="self-link" href="#ac-participation"></a></h4> 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>) 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 must 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> must follow the <a href="#coi">conflict of interest policy</a> by disclosing information according to the mechanisms described in the New Member Orientation. The AC representative may 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). <h4 class="heading settled" data-level="3.2.3" id="ACCommunication">3.2.3. Advisory Committee Mailing Lists<a class="self-link" href="#ACCommunication"></a></h4> The <a data-link-type="dfn" href="#team" id="ref-for-team①②">Team</a> must provide two mailing lists for use by the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee②">Advisory Committee</a>: <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> must monitor discussion and should participate in discussion when appropriate. Ongoing detailed discussions should be moved to other appropriate lists (new or existing, such as a mailing list created for a <a href="#GAEvents">Workshop</a>). </ol> An <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative⑦">Advisory Committee representative</a> may request that additional individuals from their organization be subscribed to these lists. Failure to contain distribution internally may result in suspension of additional email addresses, at the discretion of the Team. <h4 class="heading settled" data-level="3.2.4" id="ACMeetings">3.2.4. Advisory Committee Meetings<a class="self-link" href="#ACMeetings"></a></h4> 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> twice a year. 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 should provide an update to the Advisory Committee about: <dl> <dt>Resources <dd> <ul> <li> The number of W3C Members at each level. <li> An overview of the financial status of W3C. </ul> <dt>Allocations <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> Each Member organization should 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 may allow a Member organization to send two representatives to a meeting. The <a data-link-type="dfn" href="#team" id="ref-for-team①⑦">Team</a> must announce the date and location of each Advisory Committee meeting no later than at the end of the previous meeting; one year’s notice is preferred. The Team must announce the region of each Advisory Committee meeting at least one year in advance. 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. <h3 class="heading settled" data-level="3.3" id="elected-groups">3.3. Elected Groups: The AB and the TAG<a class="self-link" href="#elected-groups"></a></h3> 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>. <h4 class="heading settled" data-level="3.3.1" id="AB">3.3.1. Advisory Board (AB)<a class="self-link" href="#AB"></a></h4> <h5 class="heading settled" data-level="3.3.1.1" id="ab-role">3.3.1.1. Role of the Advisory Board<a class="self-link" href="#ab-role"></a></h5> 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>. 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. Note: 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>. 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>. <h5 class="heading settled" data-level="3.3.1.2" id="ABParticipation">3.3.1.2. Composition of the Advisory Board<a class="self-link" href="#ABParticipation"></a></h5> 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 may 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 should 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 must be run at least at the start of each regular term, as well as when a majority of the participants request it; and may 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>, 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. 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>. The terms of elected Advisory Board participants are for two years. Terms are staggered so that each year, either five or six terms expire. If an individual is elected to fill an incomplete term, that individual’s term ends at the normal expiration date of that term. Regular Advisory Board terms begin on 1 July and end on 30 June. <h5 class="heading settled" data-level="3.3.1.3" id="ab-comm">3.3.1.3. Communications of the Advisory Board<a class="self-link" href="#ab-comm"></a></h5> The <a data-link-type="dfn" href="#team" id="ref-for-team①⑨">Team</a> must make available a mailing list, confidential to the Advisory Board and Team, for the Advisory Board to use for its communication. The <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board⑧">Advisory Board</a> should send a summary of each of its meetings to the Advisory Committee and other group Chairs. The Advisory Board should also report on its activities at each <a href="#ACMeetings">Advisory Committee meeting</a>. <h5 class="heading settled" data-level="3.3.1.4" id="ab-bod-liaison">3.3.1.4. Liaisons between the Advisory Board and the Board of Directors<a class="self-link" href="#ab-bod-liaison"></a></h5> 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> may 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. The <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board①①">Advisory Board</a> should reevaluate who is assigned to this role at least at the beginning of each term, and may swap its appointees more frequently as they deem appropriate. <h4 class="heading settled" data-level="3.3.2" id="TAG">3.3.2. Technical Architecture Group (TAG)<a class="self-link" href="#TAG"></a></h4> <h5 class="heading settled" data-level="3.3.2.1" id="tag-role">3.3.2.1. Role of the Technical Architecture Group<a class="self-link" href="#tag-role"></a></h5> 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: <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> 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>. 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 should not 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. 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. 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>. <h5 class="heading settled" data-level="3.3.2.2" id="tag-participation">3.3.2.2. Composition of the Technical Architecture Group<a class="self-link" href="#tag-participation"></a></h5> The <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group⑥">TAG</a> consists of: <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> 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 must be selected from the participants of the TAG. Chair selection must be run at least at the start of each regular term, as well as when a majority of the participants request it; and may 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 <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>. The terms of TAG participants last for two years. 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. <h5 class="heading settled" data-level="3.3.2.3" id="tag-comm">3.3.2.3. Communications of the Technical Architecture Group<a class="self-link" href="#tag-comm"></a></h5> The <a data-link-type="dfn" href="#team" id="ref-for-team②②">Team</a> must make available two mailing lists for the TAG: <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> The <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group⑨">TAG</a> may 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 may use a list that will be <a href="#Member-only" id="ref-for-Member-only①④">Member-only</a>. The <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group①⓪">TAG</a> should 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> should also report on its activities at each <a href="#ACMeetings">Advisory Committee meeting</a>. <h4 class="heading settled" data-level="3.3.3" id="AB-TAG-participation">3.3.3. Participation in Elected Groups<a class="self-link" href="#AB-TAG-participation"></a></h4> <h5 class="heading settled" data-level="3.3.3.1" id="elected-expectations">3.3.3.1. Expectations for Elected Groups Participants<a class="self-link" href="#elected-expectations"></a></h5> <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 should attend <a href="#ACMeetings">Advisory Committee meetings</a>. 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. 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>). Participation in the TAG or AB is afforded to the specific individuals elected or appointed to those positions, and a participant’s seat must not be delegated to any other person. <h5 class="heading settled" data-level="3.3.3.2" id="AB-TAG-constraints">3.3.3.2. Elected Groups Participation Constraints<a class="self-link" href="#AB-TAG-constraints"></a></h5> 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: <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 must 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 must 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 30 days 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 must not participate on both the TAG and the AB. </ul> <h5 class="heading settled" data-level="3.3.3.3" id="AB-TAG-elections">3.3.3.3. Advisory Board and Technical Architecture Group Elections<a class="self-link" href="#AB-TAG-elections"></a></h5> 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> may modify the tabulation system after the Call for Nominations but must 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>. 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. 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. Each Member (or group of <a data-link-type="dfn" href="#related-member" id="ref-for-related-member①">related Members</a>) may nominate one individual. A nomination must be made with the consent of the nominee. In order for an individual to be nominated as a Member representative, the individual must 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> must 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 must 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> must 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> must first secure approval from <a data-link-type="dfn" href="#team" id="ref-for-team②⑦">Team</a> management. A nominee is not required to be an employee of a Member organization, and may be a <a href="#fellows" id="ref-for-fellows①">W3C Fellow</a>. The nomination form must 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 may 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 should include a few informative paragraphs about the nominee. If, after the deadline for nominations, the number of nominees is: <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> 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>) may 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. 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. 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. <h5 class="heading settled" data-level="3.3.3.4" id="TAG-appointments">3.3.3.4. Technical Architecture Group Appointments<a class="self-link" href="#TAG-appointments"></a></h5> 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> should 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. The <a data-link-type="dfn" href="#team" id="ref-for-team③②">Team</a> should actively seek candidates for appointment to the TAG, and must 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>. 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 must not be appointed for more than two consecutive 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 may 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>. 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. 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> should 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> should seek to appoint a replacement unless a regular Call for Nominations is scheduled within 2 months, and it must announce the ratified appointment no later than the Call for Nominations of the next scheduled election. <h5 class="heading settled" data-level="3.3.3.5" id="random">3.3.3.5. Verifiable Random Selection Procedure<a class="self-link" href="#random"></a></h5> 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”. W3C applies this procedure as follows: <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">3.3.3.6. Elected Groups Vacated Seats<a class="self-link" href="#AB-TAG-vacated"></a></h5> 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: <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> 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. Vacated seats are filled according to this schedule: <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 should not request such an election if the next regularly scheduled election is fewer than three months away. <li> The group Chair may 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> 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. </ul> <h3 class="heading settled" data-level="3.4" id="GAGeneral">3.4. Chartered Groups: Working Groups and Interest Groups<a class="self-link" href="#GAGeneral"></a></h3> This document defines two types of <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="chartered-group">chartered groups</dfn>: <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>. 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>”. <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. 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>. </dl> <h4 class="heading settled" data-level="3.4.1" id="ReqsAllGroups">3.4.1. Requirements for All Chartered Groups<a class="self-link" href="#ReqsAllGroups"></a></h4> Each group must 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 must be public (even if other proceedings of the group are <a href="#Member-only" id="ref-for-Member-only①⑤">Member-only</a>). Each group must 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. Note: 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>. Each group must 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. Note: 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>. 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 should not be the same individual. Each group must 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>. A <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs⑥">Chair</a> may form task forces (composed of group participants) to carry out assignments for the group. The scope of these assignments must not exceed the scope of the group’s charter. A group should 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 may choose to publish their results as part of a technical report. <h4 class="heading settled" data-level="3.4.2" id="group-participation">3.4.2. Participation in Chartered Groups<a class="self-link" href="#group-participation"></a></h4> 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>). 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>. 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>. A participant may 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 must all be members of the group. An individual may 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>. On an exceptional basis, a Working or Interest Group participant may 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 should inform the <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs⑦">Chair</a>. The substitute may act on behalf of the participant, including for <a href="#Votes">votes</a>. For the substitute to vote, the participant must 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 should authorize another participant to act as <a href="#proxy" id="ref-for-proxy">proxy</a> for votes. 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 may split it into an Interest Group (a discussion forum) and a much smaller Working Group (a core group of highly dedicated participants). <h4 class="heading settled" data-level="3.4.3" id="chartered-group-participants">3.4.3. Types of Participants in Chartered Groups<a class="self-link" href="#chartered-group-participants"></a></h4> <h5 class="heading settled" data-level="3.4.3.1" id="member-rep-wg">3.4.3.1. Member Representative in a Working Group<a class="self-link" href="#member-rep-wg"></a></h5> 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: <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> 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> must 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 information, 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>): <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> 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: <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">3.4.3.2. Member Representative in an Interest Group<a class="self-link" href="#member-rep-ig"></a></h5> 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: <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> 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 must follow the instructions in the <a href="#cfp">Call for Participation</a> and charter. Member participation in an Interest Group ceases under the same conditions as for a Working Group. <h5 class="heading settled" data-level="3.4.3.3" id="invited-expert-wg">3.4.3.3. Invited Expert in a Working Group<a class="self-link" href="#invited-expert-wg"></a></h5> The <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs①⓪">Chair</a> may invite an individual with a particular expertise to participate in a Working Group. This individual may represent an organization in the group (e.g., if acting as a liaison with another organization). 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: <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> 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> must 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. 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 must: <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> The <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs①③">Chair</a> should not 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 must not use Invited Expert status to circumvent participation limits imposed by the <a href="#WGCharter">charter</a>. An Invited Expert participates in a Working Group from the moment the individual joins the group until any of the following occurs: <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">3.4.3.4. Invited Expert in an Interest Group<a class="self-link" href="#invited-expert-ig"></a></h5> 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>. <h5 class="heading settled" data-level="3.4.3.5" id="team-rep-wg">3.4.3.5. Team Representative in a Working Group<a class="self-link" href="#team-rep-wg"></a></h5> 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. A Team representative participates in a Working Group from the moment the individual joins the group until any of the following occurs: <ul> <li> the group closes, or <li> W3C management changes Team representation by sending email to the Chair, copying the group mailing list. </ul> The Team participates in a Working Group from the moment the creation of the group is announced until the group closes. <h5 class="heading settled" data-level="3.4.3.6" id="team-rep-ig">3.4.3.6. Team Representative in an Interest Group<a class="self-link" href="#team-rep-ig"></a></h5> 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. <h2 class="heading settled" data-level="4" id="group-lifecyle">4. Lifecycle of Chartered Groups<a class="self-link" href="#group-lifecyle"></a></h2> <h3 class="heading settled" data-level="4.1" id="WGCharterDevelopment">4.1. Initiating Charter Development<a class="self-link" href="#WGCharterDevelopment"></a></h3> 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 must 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 may provide feedback on the <a href="#ACCommunication">Advisory Committee discussion list</a> or via other designated channels. W3C may begin work on a Working Group or Interest Group charter at any time. <h3 class="heading settled" data-level="4.2" id="WGCharter">4.2. Content of a Charter<a class="self-link" href="#WGCharter"></a></h3> A Working Group or Interest Group <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="charter">charter</dfn> must include all of the following information. <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. Note: A charter is not required to include schedules for review of other group’s deliverables. <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 must 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 must not be sooner than eight weeks 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> 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>. 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 must provide the following information: <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<a class="self-link" href="#exclusion-draft-charter"></a></dfn>”). </ul> All of the above data must be identified in the adopting Working Group’s charter using the labels indicated. 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> must each be adopted in their entirety and without any modification. The proposed charter must 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. An Interest Group charter may include provisions regarding participation, including specifying that the only requirement for participation (by anyone) in the Interest Group is subscription to the Interest Group mailing list. This type of Interest Group may have <a href="#public-participant-ig" id="ref-for-public-participant-ig">public participants</a>. A charter may include provisions other than those required by this document. The charter should 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>). <h3 class="heading settled" data-level="4.3" id="CharterReview">4.3. Advisory Committee Review of a Charter<a class="self-link" href="#CharterReview"></a></h3> The <a data-link-type="dfn" href="#team" id="ref-for-team③⑨">Team</a> must solicit <a href="#ACReview">Advisory Committee review</a> of every new or substantively modified Working Group or Interest Group charter, except for either: <ul> <li data-md> a charter extension <li data-md> substantive changes to a charter that do not affect the way the group functions in any significant way. </ul> The review period must 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. The Call for Review of a substantively modified charter must 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 may request an extended review period. 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> must ensure that the Call for Participation for the Working Group occurs at least 60 days after the Call for Review of the charter. <h3 class="heading settled" data-level="4.4" id="cfp">4.4. Call for Participation in a Chartered Group<a class="self-link" href="#cfp"></a></h3> 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 may be amended based on review comments per <a href="#ACReviewAfter">§ 5.7.2 After the Review Period</a> before the Call for Participation. If the decision is to charter the group, the <a data-link-type="dfn" href="#team" id="ref-for-team④①">Team</a> must issue a Call for Participation to the Advisory Committee. For a new group, this announcement officially creates the group. The announcement must 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). After a Call for Participation, any <a href="#member-rep">Member representatives</a> and <a href="#invited-expert-wg">Invited Experts</a> must 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). Advisory Committee representatives may initiate an <a href="#ACAppeal">Advisory Committee Appeal</a> against the decision to create or substantially modify a Working Group or Interest Group charter. <h3 class="heading settled" data-level="4.5" id="charter-extension">4.5. Charter Extension<a class="self-link" href="#charter-extension"></a></h3> The <a data-link-type="dfn" href="#team" id="ref-for-team④②">Team</a> may 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> must 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 must indicate the new duration. The announcement must 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). After a charter extension, Advisory Committee representatives and the <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs①⑦">Chair</a> are not required to re-designate <a href="#member-rep">Member representatives</a> and <a href="#invited-expert-wg">Invited Experts</a>. Advisory Committee representatives may 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. <h3 class="heading settled" data-level="4.6" id="GeneralTermination">4.6. Chartered Group Closure<a class="self-link" href="#GeneralTermination"></a></h3> 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. 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> may propose to close a group prior to the date specified in the charter in any of the following circumstances: <ul> <li data-md> There are insufficient member resources to produce chartered deliverables or to maintain the group, according to priorities established within W3C. <li data-md> 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 should be terminated. <li data-md> 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. <li data-md> The group produced all chartered deliverables ahead of schedule. </ul> 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>. 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>. <h2 class="heading settled" data-level="5" id="decisions">5. Decisions<a class="self-link" href="#decisions"></a></h2> W3C attempts to resolve issues through dialog. Individuals who disagree strongly with a decision should register with the Chair any <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection③">Formal Objections</a>. <h3 class="heading settled" data-level="5.1" id="decision-types">5.1. Types of Decisions<a class="self-link" href="#decision-types"></a></h3> 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>. 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”). 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>. 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>. <h3 class="heading settled" data-level="5.2" id="consensus-building">5.2. Consensus Building<a class="self-link" href="#consensus-building"></a></h3> <h4 class="heading settled" data-level="5.2.1" id="Consensus">5.2.1. Consensus<a class="self-link" href="#Consensus"></a></h4> 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 may 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>. 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: <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 may 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> Note: 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. 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 may include a quorum requirement for consensus decisions. Where <a data-link-type="dfn" href="#def-Unanimity" id="ref-for-def-Unanimity">unanimity</a> is not possible, a group should 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 should set minimum thresholds of active support before a decision can be recorded. The appropriate percentage may vary depending on the size of the group and the nature of the decision. A charter may 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. <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.). If questions or disagreements arise, the final determination of consensus remains with the chair. </div> <h4 class="heading settled" data-level="5.2.2" id="managing-dissent">5.2.2. Managing Dissent<a class="self-link" href="#managing-dissent"></a></h4> 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> may 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 should move on. Groups should 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. Note: 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>. <h4 class="heading settled" data-level="5.2.3" id="Votes">5.2.3. Deciding by Vote<a class="self-link" href="#Votes"></a></h4> A group should only conduct a vote to resolve a substantive issue 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> must 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): <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> In order to vote to resolve a substantive issue, an individual must be a group <a data-link-type="dfn" href="#participant" id="ref-for-participant①">participant</a>. Each organization represented in the group must 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: <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> Unless the charter states otherwise, <a href="#invited-expert-wg">Invited Experts</a> may vote. If a participant is unable to attend a vote, that individual may 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 must 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. A group may 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. A group may 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 not required to state the reasons for votes, and the group is not required to record individual votes. A group charter may include formal voting procedures (e.g., quorum or threshold requirements) for making decisions about substantive issues. <h3 class="heading settled" data-level="5.3" id="formal-address">5.3. Formally Addressing an Issue<a class="self-link" href="#formal-address"></a></h3> 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 should seek clarification before reaching a decision. As a courtesy, both Chairs and reviewers should set expectations for the schedule of responses and acknowledgments. The group should reply to a reviewer’s initial comments in a timely manner. The group should 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 should realize that their comments will carry less weight if not sent to the group in a timely manner. Substantive responses should be recorded. The group should 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). <h3 class="heading settled" data-level="5.4" id="WGChairReopen">5.4. Reopening a Decision When Presented With New Information<a class="self-link" href="#WGChairReopen"></a></h3> The <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs②④">Chair</a> may reopen a decision when presented with new information, including: <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> The <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs②⑤">Chair</a> should record that a decision has been reopened, and must do so upon request from a group participant. <h3 class="heading settled" data-level="5.5" id="registering-objections">5.5. Registering Formal Objections<a class="self-link" href="#registering-objections"></a></h3> Any individual (regardless of whether they are associated with a Member) may 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 should inform their <a href="#TeamContact" id="ref-for-TeamContact⑧">Team Contact</a> as well as the group’s Chair(s). The Team Contact must 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. Note: 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>. A <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection⑦">Formal Objection</a> must include a summary of the issue (whether technical or procedural), the decision being appealed, and the rationale for the objection. It should 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 may 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 should also be recorded. 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 must 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 must be made <a href="#confidentiality-change">available to Members</a>. A Call for Review to the Advisory Committee must identify any <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection①②">Formal Objections</a> related to that review. Note: <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>. 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. <h3 class="heading settled" data-level="5.6" id="addressing-fo">5.6. Addressing Formal Objections<a class="self-link" href="#addressing-fo"></a></h3> <h4 class="heading settled" data-level="5.6.1" id="team-fo-mediation">5.6.1. Investigation and Mediation by the Team<a class="self-link" href="#team-fo-mediation"></a></h4> 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. 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> must 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. <h4 class="heading settled" data-level="5.6.2" id="council">5.6.2. W3C Council<a class="self-link" href="#council"></a></h4> 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. <h5 class="heading settled" data-level="5.6.2.1" id="council-composition">5.6.2.1. Council Composition<a class="self-link" href="#council-composition"></a></h5> 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>): <ul> <li data-md> 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 <li data-md> the members of the <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board②⑥">Advisory Board</a> <li data-md> the members of the <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group③①">Technical Architecture Group</a> </ul> Participation in a <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council⑥">W3C Council</a> must not require attendance of <a data-link-type="dfn" href="#ftf-meeting" id="ref-for-ftf-meeting③">face-to-face meetings</a>. 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> should 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. 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. <h5 class="heading settled" data-level="5.6.2.2" id="council-delegation">5.6.2.2. Extraordinary Delegation<a class="self-link" href="#council-delegation"></a></h5> 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 may confidentially discuss and must 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 must 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. The <a data-link-type="dfn" href="#team" id="ref-for-team⑤⑥">Team</a> must 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. <h5 class="heading settled" data-level="5.6.2.3" id="council-participation">5.6.2.3. Council Participation, Dismissal, and Renunciation<a class="self-link" href="#council-participation"></a></h5> 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. Note: 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. The <a data-link-type="dfn" href="#team" id="ref-for-team⑤⑦">Team</a> must 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, must be given an opportunity to contribute possible reasons to this list. Affected members must 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>. 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. Note: 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. An individual may 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 should not be used to excuse an absence of participation. 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> may still solicit and hear their testimony, as they can of anyone else in the W3C community. <h5 class="heading settled" data-level="5.6.2.4" id="council-short-circuit">5.6.2.4. Unanimous Short Circuit<a class="self-link" href="#council-short-circuit"></a></h5> The full Council process may 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. This step may 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>. Note: 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. <h5 class="heading settled" data-level="5.6.2.5" id="council-chairing">5.6.2.5. Council Chairing<a class="self-link" href="#council-chairing"></a></h5> 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 must 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. <h5 class="heading settled" data-level="5.6.2.6" id="council-deliberations">5.6.2.6. Council Deliberations<a class="self-link" href="#council-deliberations"></a></h5> 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. Having reviewed the information gathered by the <a data-link-type="dfn" href="#team" id="ref-for-team⑥①">Team</a>, the Council may conduct additional research or analysis, or request additional information or interviews from anyone, including the Team. The Council may further attempt to broker consensus, which, if successful, disposes the formal objection. 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> may <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. When <a data-link-type="dfn" href="#uphold" id="ref-for-uphold">upholding</a> an objection, it should 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 should 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. Note: 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. A Council may 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> should be unanimous, and may 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. 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 may write a <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="minority-opinion">Minority Opinion</dfn> explaining the reason for their disagreement. 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>. 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> must 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> may additionally make this report <a href="#confidentiality-levels">public</a>. <h5 class="heading settled" data-level="5.6.2.7" id="council-decision">5.6.2.7. Council Decision Report<a class="self-link" href="#council-decision"></a></h5> 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: <ul> <li data-md> must 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). <li data-md> must provide a rationale supporting the decision, which should address each argument raised in the Formal Objection(s). <li data-md> must include any recommendation decided by the <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council②⑥">Council</a>. <li data-md> if the <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection②③">Formal Objection</a> has been upheld, should include any suggested <a href="#fo-mitigations">mitigations</a>. <li data-md> must include the <a data-link-type="dfn" href="#minority-opinion" id="ref-for-minority-opinion">Minority Opinion</a>(s), if any. <li data-md> must 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. <li data-md> must report the names of the individuals who participated in the final decision. <li data-md> may report vote totals, if any vote was held. <li data-md> must not attribute any position to any individual on the Council. </ul> The <a data-link-type="dfn" href="#team" id="ref-for-team⑥⑤">Team</a> must 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 must also be mentioned. <a data-link-type="dfn" href="#council-report" id="ref-for-council-report①">Council Reports</a> must be no more confidential than the decision or document being objected to. The <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council②⑦">Council</a> may 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> should be self-sufficient and understandable without reference to Supplemental Confidential Council Reports. <h5 class="heading settled" data-level="5.6.2.8" id="council-appeals">5.6.2.8. Appealing Council Decisions<a class="self-link" href="#council-appeals"></a></h5> <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 a Council decision issued in a <a data-link-type="dfn" href="#council-report" id="ref-for-council-report③">Council Report</a>. <h3 class="heading settled" data-level="5.7" id="ACReview">5.7. Advisory Committee Reviews<a class="self-link" href="#ACReview"></a></h3> <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. <h4 class="heading settled" data-level="5.7.1" id="ACReviewStart">5.7.1. Start of a Review Period<a class="self-link" href="#ACReviewStart"></a></h4> 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 may send one review, which must be returned by its <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative①④">Advisory Committee representative</a>. 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> must be expressed as a <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection②④">Formal Objection</a>. The Team must provide two channels for Advisory Committee review comments: <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> The <a data-link-type="dfn" href="#reviewform" id="ref-for-reviewform">Call for Review</a> must specify which channel is the default for review comments on that Call. Reviewers may send information to either or both channels. A reviewer may also share their own reviews with other Members on the <a href="#ACCommunication">Advisory Committee discussion list</a>, and may also make it available to the public. A Member organization may modify its review during a review period (e.g., in light of comments from other Members). <h4 class="heading settled" data-level="5.7.2" id="ACReviewAfter">5.7.2. After the Review Period<a class="self-link" href="#ACReviewAfter"></a></h4> 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 must announce to the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee①⑦">Advisory Committee</a>. The announcement must 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>. 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> must be one of: <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> 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> must be one of: <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> If the proposal is adopted with changes other than <a href="#class-1">class 1 (markup) changes</a>, then those changes must 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 must 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. <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> 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> should not expect an announcement sooner than two weeks after the end of a review period. If, after three weeks, the outcome has not been announced, the <a data-link-type="dfn" href="#team" id="ref-for-team⑥⑨">Team</a> should provide the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee②③">Advisory Committee</a> with an update. <h3 class="heading settled" data-level="5.8" id="ACVotes">5.8. Advisory Committee Votes<a class="self-link" href="#ACVotes"></a></h3> 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. <h3 class="heading settled" data-level="5.9" id="ACAppeal">5.9. Appeal by Advisory Committee Representatives<a class="self-link" href="#ACAppeal"></a></h3> <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative①⑤">Advisory Committee representatives</a> may appeal certain decisions, though appeals are only expected to occur in extraordinary circumstances. 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> may 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. <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative①⑦">Advisory Committee representatives</a> may 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="#mou" id="ref-for-mou">Memoranda of Understanding</a>. In all cases, an <a data-link-type="dfn" href="#advisory-committee-appeal" id="ref-for-advisory-committee-appeal③">appeal</a> must be initiated within three weeks of the decision. 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. Note: 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>. Within one week the <a data-link-type="dfn" href="#team" id="ref-for-team⑦②">Team</a> must 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 must be <a data-link-type="dfn" href="#Member-only" id="ref-for-Member-only③">member-only</a>. If, within one week 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 must 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. The ballot must allow for three possible responses: “Approve”, “Reject”, and “Abstain”, together with Comments. 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: <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">6. W3C Technical Reports<a class="self-link" href="#Reports"></a></h2> 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: <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> 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>. <h3 class="heading settled" data-level="6.1" id="recs-and-notes">6.1. Types of Technical Reports<a class="self-link" href="#recs-and-notes"></a></h3> 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>. <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> 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> should adopt additional processes for developing publications, so long as they do not conflict with the requirements in this chapter. <h3 class="heading settled" data-level="6.2" id="general-requirements">6.2. General Requirements for Technical Reports<a class="self-link" href="#general-requirements"></a></h3> <h4 class="heading settled" data-level="6.2.1" id="publication">6.2.1. Publication of Technical Reports<a class="self-link" href="#publication"></a></h4> <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 must be a public document. W3C strives to make archival documents indefinitely available at their original address in their original form. Every document published as part of the technical report development process must clearly indicate its <a href="#maturity-stages">maturity stage</a>, and must include information about the status of the document. This status information: <ul> <li> must be unique each time a specification is <a data-link-type="dfn" href="#publishing" id="ref-for-publishing①">published</a>, <li> must state which <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG①⑧">Working Group</a> developed the specification, <li> must state how to send comments or file bugs, and where these are recorded, <li> must include expectations about next steps, <li> should explain how the technology relates to existing international standards and related work inside or outside W3C, and <li> should explain or link to an explanation of significant changes from the previous version. </ul> 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 must 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. The Team is not required 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 naming, status information, style, and copyright requirements). These rules are subject to change by the Team from time to time. The Team must 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. 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. <h4 class="heading settled" data-level="6.2.2" id="doc-reviews">6.2.2. Reviews and Review Responsibilities<a class="self-link" href="#doc-reviews"></a></h4> 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 should <a data-link-type="dfn" href="#formally-addressed" id="ref-for-formally-addressed">formally address</a> any substantive review comment about a technical report in a timely manner. Reviewers should 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> should record substantive or interesting proposals raised by reviews but not incorporated into a current specification. <h5 class="heading settled" data-level="6.2.2.1" id="wide-review">6.2.2.1. Wide Review<a class="self-link" href="#wide-review"></a></h5> 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. 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> should follow the <a href="https://www.w3.org/Guide/documentreview/#how_to_get_horizontal_review">W3C Horizontal Groups</a>’ review processes, and should 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. 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. <h4 class="heading settled" data-level="6.2.3" id="correction-classes">6.2.3. Classes of Changes<a class="self-link" href="#correction-classes"></a></h4> 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>. <dl> <dt id="class-1"> <a class="self-link" href="#class-1"></a> <ol> <li data-md> No changes to text content </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> Changes that do not functionally affect interpretation of the document </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> Other changes that do not add new features </ol> <dd> For <a data-link-type="dfn" href="#w3c-recommendation-track" id="ref-for-w3c-recommendation-track④">Recommendation-track</a> documents, these changes may 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> New features </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> Changes to the contents of a <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table">registry table</a> </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">6.2.4. Errata Management<a class="self-link" href="#errata"></a></h4> 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>. <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG②⑦">Working Groups</a> must 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 should be compiled no less frequently than quarterly. <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG②⑧">Working Groups</a> decide how to document errata. Such documentation must 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 may 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> should 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 may be documented in a separate errata page or tracking system. They may, 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). <h4 class="heading settled" data-level="6.2.5" id="candidate-amendments">6.2.5. Candidate Amendments<a class="self-link" href="#candidate-amendments"></a></h4> An <a data-link-type="dfn" href="#erratum" id="ref-for-erratum">erratum</a> may 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—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. Note: 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. 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. 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> may 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 must 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> must 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. <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>. 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. <h4 class="heading settled" data-level="6.2.6" id="contributor-license">6.2.6. License Grants from Non-Participants<a class="self-link" href="#contributor-license"></a></h4> 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> must request a recorded royalty-free patent commitment; for a change in class 4, the Team must secure such commitment. Such commitment should 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>. <h3 class="heading settled" data-level="6.3" id="rec-track">6.3. The W3C Recommendation Track<a class="self-link" href="#rec-track"></a></h3> <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>. 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: <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 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 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> 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>. W3C may <a href="#tr-end">end work on a technical report</a> at any time. 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. <h4 class="heading settled" data-level="6.3.1" id="maturity-stages">6.3.1. Maturity Stages on the Recommendation Track<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. For all Working Drafts a Working Group: <ul> <li> should document outstanding issues, and parts of the document on which the Working Group does not have consensus, and <li> may request publication of a Working Draft even if its content is considered unstable and does not meet all Working Group requirements. </ul> 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>. <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> Note: 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. Candidate Recommendation publications take one of two forms: <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. 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>). <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. 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. A <a data-link-type="dfn" href="#candidate-recommendation-draft" id="ref-for-candidate-recommendation-draft①">Candidate Recommendation Draft</a> does not 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>. </dl> 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. <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 may 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> must not 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. Note: 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). <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> Only sufficiently technically mature work should be advanced. 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. 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. <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> may 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. <h4 class="heading settled" data-level="6.3.2" id="implementation-experience">6.3.2. Implementation Experience<a class="self-link" href="#implementation-experience"></a></h4> 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): <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> 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. <h4 class="heading settled" data-level="6.3.3" id="transition-reqs">6.3.3. Advancement on the Recommendation Track<a class="self-link" href="#transition-reqs"></a></h4> For all 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: <ul> <li> must record the group’s decision to request advancement. <li> must 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>) must 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 must 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> must publicly document all new features (<a href="#correction-classes">class 4 changes</a>) to the technical report since the previous publication. <li> must publicly document if other substantive changes (<a href="#correction-classes">class 3 changes</a>) have been made, and should document the details of such changes. <li> should publicly document if <a data-link-type="dfn" href="#editorial-change" id="ref-for-editorial-change">editorial changes</a> have been made, and may document the details of such changes. <li> must <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> must provide public documentation of any <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection②⑨">Formal Objections</a>. <li> should 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> should report any changes in dependencies with other groups. <li> should provide information about implementations known to the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG④⓪">Working Group</a>. </ul> 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. <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>. <h4 class="heading settled" data-level="6.3.4" id="update-reqs">6.3.4. Updating Mature Publications on the Recommendation Track<a class="self-link" href="#update-reqs"></a></h4> 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: <ul> <li> must record the group’s decision to request the update. <li> must 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> must 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>), should be withheld if any Process requirements are not met, and may 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> must provide public documentation of any <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection③⓪">Formal Objections</a>. <li> must publicly document of all new features (<a href="#correction-classes">class 4 changes</a>) to the technical report since the previous publication. <li> must publicly document if other substantive changes (<a href="#correction-classes">class 3 changes</a>) have been made, and should document the details of such changes. <li> should publicly document if <a data-link-type="dfn" href="#editorial-change" id="ref-for-editorial-change①">editorial changes</a> changes have been made, and may document the details of such changes. <li> must 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> should 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> should report any changes in dependencies with other groups. <li> should provide information about implementations known to the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG④⑤">Working Group</a>. </ul> There is usually a formal review meeting to verify that the requirements have been met. Note: <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>. The <a data-link-type="dfn" href="#team" id="ref-for-team⑧⑤">Team</a> must announce the publication of the revised specification to other W3C groups and the Public. <h5 class="heading settled" data-level="6.3.4.1" id="streamlined-update">6.3.4.1. Streamlined Publication Approval<a class="self-link" href="#streamlined-update"></a></h5> Note: 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. 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 additional criteria are fulfilled: <ul> <li> There must 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> must document that these criteria have been fulfilled. Otherwise, the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG④⑧">Working Group</a> must 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> must have <a data-link-type="dfn" href="#formally-addressed" id="ref-for-formally-addressed②">formally addressed</a>: <ul> <li data-md> all issues raised against the document that resulted in changes since the previous publication <li data-md> all issues raised against changes since the previous publication <li data-md> all issues raised against the document that were closed since the previous publication with no change to the document </ul> The response to each of these issues must 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 <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>: <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> must 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. Note: 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>. </ul> 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. After publication, if an AC Representative or Team member doubts that the evidence presented supports the claims, they may request that a formal review meeting be convened post facto. If that review finds that the requirements were not fulfilled, the Team may 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 class="heading settled" data-level="6.3.5" id="first-wd">6.3.5. Publishing a First Public Working Draft<a class="self-link" href="#first-wd"></a></h4> 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> must meet the applicable <a href="#transition-reqs">requirements for advancement</a>. 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="#fpwd" id="ref-for-fpwd⑤">First Public Working Draft</a> to other W3C groups and to the public. <h4 class="heading settled" data-level="6.3.6" id="revising-wd">6.3.6. Revising a Working Draft<a class="self-link" href="#revising-wd"></a></h4> A <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑤④">Working Group</a> should <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. If 6 months elapse without significant changes to a specification, a Working Group should publish a revised <a data-link-type="dfn" href="#RecsWD" id="ref-for-RecsWD⑨">Working Draft</a>, whose status section should indicate reasons for the lack of change. To publish a revision of a Working draft, a Working Group: <ul> <li> must 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> must 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> should 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> should report which, if any, of the Working Group’s requirements for this document have changed since the previous step, <li> should report any changes in dependencies with other groups, </ul> Possible next steps for any Working Draft: <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">6.3.7. Transitioning to Candidate Recommendation<a class="self-link" href="#transition-cr"></a></h4> 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>: <ul> <li> must 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> must document changes to dependencies during the development of the specification, <li> must document how <a data-link-type="dfn" href="#adequate-implementation" id="ref-for-adequate-implementation②">adequate implementation experience</a> will be demonstrated, <li> must 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 must be at least 28 days after publication, and should be longer for complex documents, <li> must 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> may identify features in the document as <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="at-risk">at risk</dfn>. These features may 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> 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> must 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. Possible next steps after a <a data-link-type="dfn" href="#candidate-recommendation-snapshot" id="ref-for-candidate-recommendation-snapshot⑦">Candidate Recommendation Snapshot</a>: <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> <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee③⑤">Advisory Committee</a> representatives may initiate an <a href="#ACAppeal">Advisory Committee Appeal</a> of the decision to advance the technical report. <h4 class="heading settled" data-level="6.3.8" id="revising-cr">6.3.8. Revising a Candidate Recommendation<a class="self-link" href="#revising-cr"></a></h4> <h5 class="heading settled" data-level="6.3.8.1" id="publishing-crrs">6.3.8.1. Publishing a <a data-link-type="dfn" href="#candidate-recommendation-snapshot" id="ref-for-candidate-recommendation-snapshot⑧">Candidate Recommendation Snapshot</a><a class="self-link" href="#publishing-crrs"></a></h5> 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> must 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. In addition the Working Group: <ul> <li> must specify the deadline for further comments, which must be at least 28 days after publication, and should be longer for complex documents, <li> may identify features in the document as <a data-link-type="dfn" href="#at-risk" id="ref-for-at-risk①">at risk</a>. These features may 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> The <a data-link-type="dfn" href="#team" id="ref-for-team⑧⑨">Team</a> must 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. 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> should 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> should not be published more often than approximately once every 6 months. Note: <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>. <h5 class="heading settled" data-level="6.3.8.2" id="publishing-crud">6.3.8.2. Publishing a <a data-link-type="dfn" href="#candidate-recommendation-draft" id="ref-for-candidate-recommendation-draft②">Candidate Recommendation Draft</a><a class="self-link" href="#publishing-crud"></a></h5> A <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑤⑧">Working Group</a> should <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. 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: <ul> <li> must record the group’s decision to request publication, <li> must 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> should 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> should document outstanding issues, and parts of the document on which the Working Group does not have consensus, <li> should report which, if any, of the Working Group’s requirements for this document have changed since the previous step, <li> should report any changes in dependencies with other groups. </ul> Note: A Working Group does not 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>. Possible next steps after a <a data-link-type="dfn" href="#candidate-recommendation-draft" id="ref-for-candidate-recommendation-draft⑥">Candidate Recommendation Draft</a>: <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">6.3.9. Transitioning to Proposed Recommendation<a class="self-link" href="#transition-pr"></a></h4> In addition to meeting the <a href="#transition-reqs">requirements for advancement</a>, <ul> <li> The status information must specify the deadline for <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review①①">Advisory Committee review</a>, which must be at least 28 days after the publication of the <a data-link-type="dfn" href="#RecsPR" id="ref-for-RecsPR⑦">Proposed Recommendation</a> and should 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> A Working Group: <ul> <li> must 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> must 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> must 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> must 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> must not 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> may 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> The <a data-link-type="dfn" href="#team" id="ref-for-team⑨⓪">Team</a>: <ul> <li> must 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 must 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> may 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> must explain the reasons for that decision, and that information must 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> Since a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C②⑦">W3C Recommendation</a> must not 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> must 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>. 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. 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> </ul> <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 to advance the technical report. <h4 class="heading settled" data-level="6.3.10" id="transition-rec">6.3.10. Transitioning to W3C Recommendation<a class="self-link" href="#transition-rec"></a></h4> 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>. In addition to meeting the <a href="#transition-reqs">requirements for advancement</a>, <ul> <li> A <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C③①">Recommendation</a> must identify where errata are tracked, and <li> A <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C③②">Recommendation</a> must not 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> must publish the substantive content of the dissent to W3C and the general public, and must <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> may 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> must 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> 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 may be: <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">6.3.11. Revising a W3C Recommendation<a class="self-link" href="#revising-rec"></a></h4> This section details the process for making changes to a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C③⑦">Recommendation</a>. <h5 class="heading settled" data-level="6.3.11.1" id="revised-rec-markup">6.3.11.1. Revising a Recommendation: Markup Changes<a class="self-link" href="#revised-rec-markup"></a></h5> A <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑥⓪">Working group</a> may 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>.) 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> may republish the <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C④⓪">Recommendation</a> with such changes incorporated. <h5 class="heading settled" data-level="6.3.11.2" id="revised-rec-editorial">6.3.11.2. Revising a Recommendation: Editorial Changes<a class="self-link" href="#revised-rec-editorial"></a></h5> <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, may 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>.) 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> may 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>. <h5 class="heading settled" data-level="6.3.11.3" id="revised-rec-substantive">6.3.11.3. Revising a Recommendation: Substantive Changes<a class="self-link" href="#revised-rec-substantive"></a></h5> 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>. Alternatively, a <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑥⑤">Working Group</a> may 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>.) Note: 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>. <h5 class="heading settled" data-level="6.3.11.4" id="revised-rec-features">6.3.11.4. Revising a Recommendation: New Features<a class="self-link" href="#revised-rec-features"></a></h5> 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>. 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. 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 must 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>. <h5 class="heading settled" data-level="6.3.11.5" id="change-review">6.3.11.5. Incorporating Candidate Amendments<a class="self-link" href="#change-review"></a></h5> 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. 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 must: <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</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> 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>. Note: <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>. A <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑥⑦">Working Group</a> may 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 should not be issued more frequently than approximately once every 6 months. 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. 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>. 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.) <h4 class="heading settled" data-level="6.3.12" id="rec-track-regression">6.3.12. Regression on the Recommendation Track<a class="self-link" href="#rec-track-regression"></a></h4> 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. 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> may 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>. <h4 class="heading settled" data-level="6.3.13" id="tr-end">6.3.13. Retiring Recommendation Track Documents<a class="self-link" href="#tr-end"></a></h4> Work on a technical report may cease at any time. Work should 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. <h5 class="heading settled" data-level="6.3.13.1" id="abandon-draft">6.3.13.1. Abandoning an Unfinished Recommendation<a class="self-link" href="#abandon-draft"></a></h5> 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, should 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 must 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>. Such a document should include in its status section an explanation of why it was discontinued. A <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑦⑥">Working Group</a> may 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>. <h5 class="heading settled" data-level="6.3.13.2" id="rescind-cr">6.3.13.2. Rescinding a Candidate Recommendation<a class="self-link" href="#rescind-cr"></a></h5> 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>. <h5 class="heading settled" data-level="6.3.13.3" id="rec-rescind">6.3.13.3. Abandoning a W3C Recommendation<a class="self-link" href="#rec-rescind"></a></h5> 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. W3C may 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> may 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. W3C may 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. W3C may 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”. 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>. Note: 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. <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">6.3.13.4. Process for Rescinding, Obsoleting, Superseding, Restoring a Recommendation<a class="self-link" href="#deactivation"></a></h5> 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: <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> The <a data-link-type="dfn" href="#team" id="ref-for-team⑨⑨">Team</a> must 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> must: <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 must be at least 28 days after the announcement </ul> and should <ul> <li> identify known implementations. </ul> 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> must publish the substantive content of the dissent to W3C and the public, and must <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>. The <a href="#AC">Advisory Committee</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 <a data-link-type="dfn" href="#team" id="ref-for-team①⓪②">Team</a>'s decision. W3C must 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 may remove the main body of the document. The Status of this Document section should 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. Once W3C has published a Rescinded Recommendation, future W3C technical reports must not include normative references to that technical report. Note: W3C strives to ensure that all Technical Reports will continue to be available at their version-specific URL. <h3 class="heading settled" data-level="6.4" id="note-track">6.4. The Note Track (Notes and Statements)<a class="self-link" href="#note-track"></a></h3> <h4 class="heading settled" data-level="6.4.1" id="Note">6.4.1. Group Notes<a class="self-link" href="#Note"></a></h4> 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. <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> may publish work as <a data-link-type="dfn" href="#WGNote" id="ref-for-WGNote②">Notes</a>. Examples include: <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> 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. Note: 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>. <h4 class="heading settled" data-level="6.4.2" id="publishing-notes">6.4.2. Publishing Notes<a class="self-link" href="#publishing-notes"></a></h4> 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: <ul> <li> must 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> should publish documentation of significant changes to the technical report since any previous publication. </ul> 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> may remain a <a data-link-type="dfn" href="#WGNote" id="ref-for-WGNote①②">Note</a> indefinitely. 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> may 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. <h4 class="heading settled" data-level="6.4.3" id="w3c-statement">6.4.3. Elevating Group Notes to W3C Statement status<a class="self-link" href="#w3c-statement"></a></h4> 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 must: <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> A <a data-link-type="dfn" href="#WGNote" id="ref-for-WGNote①⑧">Note</a> specifying implementable technology should not 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> must 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>. Once these conditions are fulfilled, the <a data-link-type="dfn" href="#team" id="ref-for-team①⓪④">Team</a> must 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> must not be updated. 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. 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. <h4 class="heading settled" data-level="6.4.4" id="revising-memo">6.4.4. Revising W3C Statements<a class="self-link" href="#revising-memo"></a></h4> 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. 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 must 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>. 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. <h3 class="heading settled" data-level="6.5" id="registries">6.5. The Registry Track<a class="self-link" href="#registries"></a></h3> 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: <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> The purposes of maintaining a <a data-link-type="dfn" href="#registry" id="ref-for-registry③">registry</a> can include: <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> 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>. Note: 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. <h4 class="heading settled" data-level="6.5.1" id="reg-def">6.5.1. Registry Definitions<a class="self-link" href="#reg-def"></a></h4> 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 must: <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>. 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> should generally be the same entity. </ul> <h4 class="heading settled" data-level="6.5.2" id="reg-pub">6.5.2. Publishing Registries<a class="self-link" href="#reg-pub"></a></h4> <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>. 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 must not 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. 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> must: <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> The <a data-link-type="dfn" href="#team" id="ref-for-team①⓪⑦">Team</a> must 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>. Note: 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. 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: <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">6.5.3. Updating Registry Tables<a class="self-link" href="#reg-table-update"></a></h4> 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. Note: 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—or in the absence of a Working Group, of the Team. 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> must be identified as such. <h4 class="heading settled" data-level="6.5.4" id="reg-data-reports">6.5.4. Registry Data Reports<a class="self-link" href="#reg-data-reports"></a></h4> 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>: <ul> <li> Must 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> May 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> <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>. 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 must 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. 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> may 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> may do so instead. <h4 class="heading settled" data-level="6.5.5" id="reg-ref-specifications">6.5.5. Specifications that Reference Registries<a class="self-link" href="#reg-ref-specifications"></a></h4> 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> must 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. If there are entries that must be implemented, or any other such restrictions, they must be defined or documented in the referencing specification without dependency on the registry. <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">6.6. Switching Tracks<a class="self-link" href="#switching-tracks"></a></h3> 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: <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> <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.). <h3 class="heading settled" data-level="6.7" id="further-reading">6.7. Further reading<a class="self-link" href="#further-reading"></a></h3> 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>. <h2 class="heading settled" data-level="7" id="dissemination">7. Dissemination Policies<a class="self-link" href="#dissemination"></a></h2> <h3 class="heading settled" data-level="7.1" id="pub-com">7.1. Public Communication<a class="self-link" href="#pub-com"></a></h3> 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 should solicit review by the Team prior to issuing press releases about their work within W3C. 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: <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> 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. <h3 class="heading settled" data-level="7.2" id="confidentiality-levels">7.2. Confidentiality Levels<a class="self-link" href="#confidentiality-levels"></a></h3> There are three principal levels of access to W3C information (on the W3C website, in W3C meetings, etc.): public, Member-only, and Team-only. 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 may specify a <a data-link-type="dfn" href="#Member-only" id="ref-for-Member-only④">Member-only</a> confidentiality level for group proceedings. “<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. 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: <ul> <li> must treat the information as confidential within W3C, <li> must use reasonable efforts to maintain the proper level of confidentiality, and <li> must not release this information to the general public or press. </ul> The <a data-link-type="dfn" href="#team" id="ref-for-team①①①">Team</a> must 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 should 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 should contact the Team. <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative②④">Advisory Committee representatives</a> may 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>. <h3 class="heading settled" data-level="7.3" id="confidentiality-change">7.3. Changing Confidentiality Level<a class="self-link" href="#confidentiality-change"></a></h3> 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 may 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> must make public information pertinent to the technical report development process. This document clearly indicates which information must 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: <ol> <li> The <a data-link-type="dfn" href="#team" id="ref-for-team①①③">Team</a> must 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 should remind recipients to provide such alternatives. <li> The <a data-link-type="dfn" href="#team" id="ref-for-team①①④">Team</a> must not 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 may 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">8. Workshops and Symposia<a class="self-link" href="#GAEvents"></a></h2> 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. 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 may solicit position papers for the Workshop program and may 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 may 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 may 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 must issue the Call for Participation no later than six weeks prior to the Workshop’s scheduled start date. For other Workshops and Symposia, the Team must issue a Call for Participation no later than eight weeks 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 class="heading settled" data-level="9" id="Liaisons">9. Liaisons<a class="self-link" href="#Liaisons"></a></h2> 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. All liaisons must 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. W3C may 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 may include joint deliverables, an agreed share of technical responsibilities with due coordination, and/or considerations for confidentiality and specific IPR. 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. 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 should 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 must 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> 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 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> must not 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> should be made public. 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. <h2 class="heading settled" data-level="10" id="Submission">10. Member Submission Process<a class="self-link" href="#Submission"></a></h2> 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> may 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. A <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="MemberSubmission">Member Submission</dfn> consists of: <ul> <li> One or more documents developed outside of the W3C process, and <li> Information about the documents, provided by the Submitter. </ul> One or more Members (called the <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="submitter" id="submitter">Submitter(s)</dfn>) may participate in a Member Submission. Only W3C Members may be listed as <a data-link-type="dfn" href="#submitter" id="ref-for-submitter">Submitters</a>. The Submission process consists of the following steps: <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> must either acknowledge or reject the Submission request. <ul> <li> If <a href="#SubmissionYes">acknowledged</a>, the Team must 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) may 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 not 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> 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 must not be referred to as “work in progress” of W3C. 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. <h3 class="heading settled" data-level="10.1" id="SubmissionRights">10.1. Submitter Rights and Obligations<a class="self-link" href="#SubmissionRights"></a></h3> When more than one Member jointly participates in a Submission request, only one Member formally sends in the request. That Member must 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> must confirm (by email to the Team) their participation in the Submission request. At any time prior to acknowledgment, any <a data-link-type="dfn" href="#submitter" id="ref-for-submitter④">Submitter</a> may 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 must not make statements about withdrawn Submission requests. Prior to acknowledgment, the <a data-link-type="dfn" href="#submitter" id="ref-for-submitter⑤">Submitter</a>(s) must not, under any circumstances, 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) must not 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) may release the documents in the Member Submission to the public prior to acknowledgment (without reference to the Submission request). After acknowledgment, the <a data-link-type="dfn" href="#submitter" id="ref-for-submitter⑨">Submitter</a>(s) must not, under any circumstances, 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>. <h4 class="heading settled" data-level="10.1.1" id="SubmissionScope">10.1.1. Scope of Member Submissions<a class="self-link" href="#SubmissionScope"></a></h4> When a technology overlaps in scope with the work of a chartered Working Group, Members should <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> may incorporate the contributed technology into its deliverables. If the Working Group does not incorporate the technology, it should not 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. On the other hand, while W3C is in the early stages of developing a charter, Members should use the Submission process to build consensus around concrete proposals for new work. Members should not 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>. <h4 class="heading settled" data-level="10.1.2" id="SubmissionReqs">10.1.2. Information Required in a Submission Request<a class="self-link" href="#SubmissionReqs"></a></h4> The <a data-link-type="dfn" href="#submitter" id="ref-for-submitter①⓪">Submitter</a>(s) and any other authors of the submitted material must 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) may hold the copyright for the documents in a Member Submission. The request must 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>. The <a data-link-type="dfn" href="#submitter" id="ref-for-submitter①②">Submitter</a>(s) must 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 must 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 must 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> may hold the copyright for the material contained in these documents, but when made available by W3C, these documents must 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> The request must 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 <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> 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>. <h3 class="heading settled" data-level="10.2" id="TeamSubmissionRights">10.2. Team Rights and Obligations<a class="self-link" href="#TeamSubmissionRights"></a></h3> Although they are not technical reports, the documents in a <a data-link-type="dfn" href="#MemberSubmission" id="ref-for-MemberSubmission⑤">Member Submission</a> must 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>. 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. 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> must hold it in the strictest confidentiality. In particular, the Team must not comment to the media about the Submission request. <h3 class="heading settled" data-level="10.3" id="SubmissionYes">10.3. Acknowledgment of a Submission Request<a class="self-link" href="#SubmissionYes"></a></h3> 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 may 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 four to six weeks 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> must 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. Once a Submission request has been acknowledged, the <a data-link-type="dfn" href="#team" id="ref-for-team①②⑦">Team</a> must: <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> 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) must 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>. <h3 class="heading settled" data-level="10.4" id="SubmissionNo">10.4. Rejection of a Submission Request, and Submission Appeals<a class="self-link" href="#SubmissionNo"></a></h3> The <a data-link-type="dfn" href="#team" id="ref-for-team①②⑧">Team</a> may 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 <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> In case of a rejection, the <a data-link-type="dfn" href="#team" id="ref-for-team①②⑨">Team</a> must 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> must 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 must not make statements about why a Submission request was rejected. 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) may 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>. <h2 class="heading settled" data-level="11" id="GAProcess">11. Process Evolution<a class="self-link" href="#GAProcess"></a></h2> 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. The documents covered by this section are: <ul> <li data-md> the W3C Process (this document) <li data-md> the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a> <li data-md> 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> <li data-md> The W3C Document License <a data-link-type="biblio" href="#biblio-doc-license" title="W3C Document License">[DOC-LICENSE]</a> </ul> The <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board③⑥">Advisory Board</a> initiates review as follows: <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 must last at least 28 days. <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 may initiate an <a data-link-type="dfn" href="#advisory-committee-appeal" id="ref-for-advisory-committee-appeal①③">Advisory Committee Appeal</a> to W3C. </ol> Note: 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>. <h2 class="non-normative heading settled" data-level="12" id="acks">12. Acknowledgments<a class="self-link" href="#acks"></a></h2> This section is non-normative. 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). 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. 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). <h2 class="non-normative heading settled" data-level="13" id="changes">13. Changes<a class="self-link" href="#changes"></a></h2> This section is non-normative. <h3 class="no-num heading settled" id="changes-2023-1"> Changes since the <a href="https://www.w3.org/2023/Process-20230612/">12 June 2023 Process</a><a class="self-link" href="#changes-2023-1"></a></h3> 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=https%3A%2F%2Fwww.w3.org%2F2023%2FProcess-20230612%2F&doc2=https%3A%2F%2Fwww.w3.org%2F2023%2FProcess-20231103%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. The only change is: <ul> <li> Expand the TAG from 6 elected and 3 appointed to 8 and 3. See <a href="https://www.w3.org/policies/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"> Changes since earlier versions<a class="self-link" href="#changes-previous"></a></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> of the Process. </main> <script src="https://www.w3.org/scripts/TR/2021/fixup.js"></script> <h2 class="no-num no-ref heading settled" id="index">Index<a class="self-link" href="#index"></a></h2> <h3 class="no-num no-ref heading settled" id="index-defined-here">Terms defined by this specification<a class="self-link" href="#index-defined-here"></a></h3> <ul class="index"> <li><a href="#advisory-board">AB</a>, in § 3.3.1.1 <li><a href="#WGNote">AB Note</a>, in § 6.4.1 <li><a href="#advisory-committee">AC</a>, in § 3.2.1 <li><a href="#advisory-committee-appeal">AC Appeal</a>, in § 5.9 <li><a href="#advisory-committee-representative">AC representative</a>, in § 3.2.2 <li><a href="#advisory-committee-review">AC Review</a>, in § 5.7 <li><a href="#adequate-implementation">adequate implementation experience</a>, in § 6.3.2 <li><a href="#adopted-draft">Adopted Draft</a>, in § 4.2 <li><a href="#advisory-board">Advisory Board</a>, in § 3.3.1.1 <li><a href="#advisory-committee">Advisory Committee</a>, in § 3.2.1 <li><a href="#advisory-committee-appeal">Advisory Committee Appeal</a>, in § 5.9 <li><a href="#advisory-committee-representative">Advisory Committee representative</a>, in § 3.2.2 <li><a href="#advisory-committee-review">Advisory Committee review</a>, in § 5.7 <li><a href="#technical-agreement">agreement</a>, in § 9 <li><a href="#allow-new-features">allow new features</a>, in § 6.3.9 <li><a href="#alternate-ac-representative">alt AC rep</a>, in § 3.2.2 <li><a href="#alternate-ac-representative">alternate AC representative</a>, in § 3.2.2 <li><a href="#alternate-ac-representative">alternate Advisory Committee representative</a>, in § 3.2.2 <li><a href="#advisory-committee-appeal">Appeal</a>, in § 5.9 <li><a href="#at-risk">at risk</a>, in § 6.3.7 <li><a href="#bod">Board</a>, in § 2.2 <li><a href="#bod">Board of Directors</a>, in § 2.2 <li><a href="#bod">BoD</a>, in § 2.2 <li><a href="#reviewform">Call for Review</a>, in § 5.7.1 <li><a href="#candidate-addition">candidate addition</a>, in § 6.2.5 <li><a href="#candidate-amendment">candidate amendment</a>, in § 6.2.5 <li><a href="#candidate-correction">candidate correction</a>, in § 6.2.5 <li><a href="#RecsCR">Candidate Recommendation</a>, in § 6.3.1 <li><a href="#candidate-recommendation-draft">Candidate Recommendation Draft</a>, in § 6.3.1 <li><a href="#candidate-recommendation-review-period">Candidate Recommendation review period</a>, in § 6.3.7 <li><a href="#candidate-recommendation-snapshot">Candidate Recommendation Snapshot</a>, in § 6.3.1 <li><a href="#candidate-registry">Candidate Registry</a>, in § 6.5.2 <li><a href="#candidate-registry-draft">Candidate Registry Draft</a>, in § 6.5.2 <li><a href="#candidate-registry-snapshot">Candidate Registry Snapshot</a>, in § 6.5.2 <li><a href="#ceo">CEO</a>, in § 2.2 <li><a href="#GeneralChairs">Chair</a>, in § 3.4.1 <li><a href="#chair-decisions">chair decisions</a>, in § 5.1 <li><a href="#charter">charter</a>, in § 4.2 <li><a href="#chartered-group">chartered groups</a>, in § 3.4 <li><a href="#dfn-charter-extension">charter extension</a>, in § 4.5 <li><a href="#def-Consensus">Consensus</a>, in § 5.2.1 <li><a href="#w3c-council">Council</a>, in § 5.6.2 <li><a href="#council-report">Council Report</a>, in § 5.6.2.7 <li><a href="#council-team-contact">Council Team Contact</a>, in § 5.6.2.1 <li><a href="#RecsCR">CR</a>, in § 6.3.1 <li><a href="#candidate-recommendation-draft">CRD</a>, in § 6.3.1 <li><a href="#candidate-recommendation-snapshot">CRS</a>, in § 6.3.1 <li><a href="#custodian">custodian</a>, in § 6.5.1 <li><a href="#discontinuedREC">Discontinued Draft</a>, in § 6.3.1 <li><a href="#dismissed">dismiss</a>, in § 5.6.2.3 <li><a href="#dismissed">dismissal</a>, in § 5.6.2.3 <li><a href="#dismissed">dismissed</a>, in § 5.6.2.3 <li><a href="#def-Dissent">Dissent</a>, in § 5.2.1 <li><a href="#distributed-meeting">distributed meeting</a>, in § 3.1.2 <li><a href="#draft-note">Draft Note</a>, in § 6.4.1 <li><a href="#draft-registry">Draft Registry</a>, in § 6.5.2 <li><a href="#editors-draft">ED</a>, in § 6.3.1 <li><a href="#editors-draft">Editor Draft</a>, in § 6.3.1 <li><a href="#editorial-change">editorial change</a>, in § 6.2.3 <li><a href="#editors-draft">Editor’s Draft</a>, in § 6.3.1 <li><a href="#elected-group">elected groups</a>, in § 3.3 <li><a href="#erratum">errata</a>, in § 6.2.4 <li><a href="#erratum">erratum</a>, in § 6.2.4 <li><a href="#exclusion-draft">Exclusion Draft</a>, in § 4.2 <li><a href="#exclusion-draft-charter">Exclusion Draft Charter</a>, in § 4.2 <li><a href="#ftf-meeting">face-to-face meeting</a>, in § 3.1.2 <li><a href="#fpwd">First Public Working Draft</a>, in § 6.3.1 <li><a href="#formally-addressed">formally addressed</a>, in § 5.3 <li><a href="#FormalObjection">Formal Objection</a>, in § 5.5 <li><a href="#fully-addressed">fully addressed</a>, in § 5.6.2.6 <li><a href="#w3c-group">group</a>, in § 3 <li><a href="#group-decision">group decision</a>, in § 5.1 <li><a href="#WGNote">Group Note</a>, in § 6.4.1 <li><a href="#WGNote">Interest Group Note</a>, in § 6.4.1 <li><a href="#GroupsIG">Interest Groups</a>, in § 3.4 <li><a href="#invited-expert-in-an-interest-group">Invited Expert in an Interest Group</a>, in § 3.4.3.4 <li><a href="#invited-expert-in-a-working-group">Invited Expert in a Working Group</a>, in § 3.4.3.3 <li><a href="#last-call-for-review-of-proposed-additions">Last Call for Review of Proposed Additions</a>, in § 6.3.11.5 <li><a href="#last-call-review">Last Call for Review of Proposed Amendments</a>, in § 6.3.11.5 <li><a href="#last-call-for-review-of-proposed-corrections">Last Call for Review of Proposed Corrections</a>, in § 6.3.11.5 <li><a href="#last-call-for-review-of-proposed-corrections-and-additions">Last Call for Review of Proposed Corrections and Additions</a>, in § 6.3.11.5 <li><a href="#liaison">liaison</a>, in § 9 <li><a href="#w3c-member">Member</a>, in § 2.1 <li><a href="#member-association">Member Association</a>, in § 2.1.2.1 <li><a href="#member-association">Member Associations</a>, in § 2.1.2.1 <li><a href="#Member-only">Member-Only</a>, in § 7.2 <li><a href="#member-representative-in-an-interest-group">Member representative in an Interest Group</a>, in § 3.4.3.2 <li><a href="#member-representative-in-a-working-group">Member representative in a Working Group</a>, in § 3.4.3.1 <li><a href="#MemberSubmission">Member Submission</a>, in § 10 <li><a href="#minority-opinion">Minority Opinion</a>, in § 5.6.2.6 <li><a href="#minutes">minutes</a>, in § 3.1.2.2 <li><a href="#WGNote">Note</a>, in § 6.4.1 <li><a href="#not-required">not required</a>, in § Unnumbered section <li><a href="#RecsObs">Obsolete Recommendation</a>, in § 6.3.1 <li><a href="#obsolete-registry">Obsolete Registry</a>, in § 6.5.2 <li><a href="#overrule">overrule</a>, in § 5.6.2.6 <li><a href="#participant">participant</a>, in § 3 <li><a href="#igparticipant">participants in an Interest Group</a>, in § 3.4.2 <li><a href="#wgparticipant">participants in a Working Group</a>, in § 3.4.2 <li><a href="#inv-expert-info">participate in a Working Group as an Invited Expert</a>, in § 3.4.3.3 <li><a href="#patent-review-drafts">Patent Review Drafts</a>, in § 6.3 <li><a href="#RecsPR">PR</a>, in § 6.3.1 <li><a href="#primary-affiliation">primary affiliation</a>, in § 3.3.3.3 <li><a href="#proposed-additions">proposed additions</a>, in § 6.3.11.5 <li><a href="#proposed-amendments">proposed amendments</a>, in § 6.3.11.5 <li><a href="#proposed-corrections">proposed corrections</a>, in § 6.3.11.5 <li><a href="#RecsPR">Proposed Recommendation</a>, in § 6.3.1 <li><a href="#proxy">proxy</a>, in § 5.2.3 <li><a href="#public-participant-ig">public participants</a>, in § 3.4.2 <li><a href="#publishing">publish</a>, in § 6.2.1 <li><a href="#RecsW3C">REC</a>, in § 6.3.1 <li><a href="#RecsW3C">Recommendation</a>, in § 6.3.1 <li><a href="#w3c-recommendation-track">Recommendation Track</a>, in § 6.3 <li><a href="#w3c-recommendation-track">Recommendation-track</a>, in § 6.3 <li><a href="#w3c-recommendation-track">REC Track</a>, in § 6.3 <li><a href="#registry">registry</a>, in § 6.5 <li><a href="#registry-change">registry change</a>, in § 6.2.3 <li><a href="#registry-data">registry data</a>, in § 6.5 <li><a href="#registry-data-report">Registry Data Report</a>, in § 6.5.4 <li><a href="#registry-definition">registry definition</a>, in § 6.5.1 <li><a href="#registry-entry">registry entry</a>, in § 6.5 <li><a href="#registry-report">registry report</a>, in § 6.5.2 <li><a href="#registry-section">registry section</a>, in § 6.5.2 <li><a href="#registry-table">registry table</a>, in § 6.5 <li><a href="#registry-track">Registry Track</a>, in § 6.5.2 <li><a href="#related-member">Related Member</a>, in § 2.1.2.2 <li><a href="#renounce">renounce</a>, in § 5.6.2.3 <li><a href="#renounce">renunciation</a>, in § 5.6.2.3 <li><a href="#rescinded-candidate-recommendation">Rescinded Candidate Recommendation</a>, in § 6.3.1 <li><a href="#RescindedRec">Rescinded Recommendation</a>, in § 6.3.1 <li><a href="#group-decision">resolution</a>, in § 5.1 <li><a href="#statement">Statement</a>, in § 6.4.3 <li><a href="#submission-appeals">Submission Appeals</a>, in § 10.4 <li><a href="#submitter">submitter</a>, in § 10 <li><a href="#subsidiary">subsidiary</a>, in § 2.1.2.2 <li><a href="#substantive-change">substantive change</a>, in § 6.2.3 <li><a href="#mtg-substitute">substitute</a>, in § 3.4.2 <li><a href="#RecsSup">Superseded Recommendation</a>, in § 6.3.1 <li><a href="#superseded-registry">Superseded Registry</a>, in § 6.5.2 <li><a href="#supplemental-confidential-council-report">Supplemental Confidential Council Report</a>, in § 5.6.2.7 <li><a href="#EventsS">Symposia</a>, in § 8 <li><a href="#EventsS">Symposium</a>, in § 8 <li><a href="#technical-architecture-group">TAG</a>, in § 3.3.2.1 <li><a href="#WGNote">TAG Note</a>, in § 6.4.1 <li><a href="#team">Team</a>, in § 2.2 <li><a href="#TeamContact">Team Contact</a>, in § 3.4.1 <li><a href="#team-correction">Team correction</a>, in § 6.2.5 <li><a href="#team-decision">Team Decision</a>, in § 5.1 <li><a href="#Team-only">Team-Only</a>, in § 7.2 <li><a href="#team-representative-in-an-interest-group">Team representative in an Interest Group</a>, in § 3.4.3.6 <li><a href="#team-representative-in-a-working-group">Team representative in a Working Group</a>, in § 3.4.3.5 <li><a href="#team-decision">Team’s Decision</a>, in § 5.1 <li><a href="#technical-agreement">technical agreement</a>, in § 9 <li><a href="#technical-architecture-group">Technical Architecture Group</a>, in § 3.3.2.1 <li><a href="#technical-report">Technical Report</a>, in § 6.2.1 <li><a href="#trans-req">Transition Requests</a>, in § 6.3.3 <li><a href="#def-Unanimity">Unanimity</a>, in § 5.2.1 <li><a href="#update-requests">Update Requests</a>, in § 6.3.4 <li><a href="#uphold">upheld</a>, in § 5.6.2.6 <li><a href="#uphold">uphold</a>, in § 5.6.2.6 <li><a href="#uphold">upholding</a>, in § 5.6.2.6 <li><a href="#uphold">upholds</a>, in § 5.6.2.6 <li><a href="#validation-notice">validation notice</a>, in § 10.2 <li><a href="#bod">W3C Board of Directors</a>, in § 2.2 <li><a href="#RecsCR">W3C Candidate Recommendation</a>, in § 6.3.1 <li><a href="#w3c-council">W3C Council</a>, in § 5.6.2 <li><a href="#w3c-council-chair">W3C Council Chair</a>, in § 5.6.2.5 <li><a href="#def-w3c-decision">W3C decision</a>, in § 5.1 <li><a href="#fellows">W3C Fellows</a>, in § 2.2 <li><a href="#w3c-group">W3C Group</a>, in § 3 <li><a href="#w3c-member">W3C Member</a>, in § 2.1 <li><a href="#WGNote">W3C Note</a>, in § 6.4.1 <li><a href="#RecsPR">W3C Proposed Recommendation</a>, in § 6.3.1 <li><a href="#RecsW3C">W3C Recommendation</a>, in § 6.3.1 <li><a href="#w3c-recommendation-track">W3C Recommendation Track</a>, in § 6.3 <li><a href="#w3c-registry">W3C Registry</a>, in § 6.5.2 <li><a href="#statement">W3C Statement</a>, in § 6.4.3 <li><a href="#team">W3C Team</a>, in § 2.2 <li><a href="#RecsWD">W3C Working Draft</a>, in § 6.3.1 <li><a href="#RecsWD">WD</a>, in § 6.3.1 <li><a href="#dfn-wide-review">wide review</a>, in § 6.2.2.1 <li><a href="#RecsWD">Working Draft</a>, in § 6.3.1 <li><a href="#WGNote">Working Group Note</a>, in § 6.4.1 <li><a href="#GroupsWG">Working Groups</a>, in § 3.4 <li><a href="#EventsW">Workshops</a>, in § 8 </ul> <h3 class="no-num no-ref heading settled" id="index-defined-elsewhere">Terms defined by reference<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>patent advisory group </ul> </ul> <h2 class="no-num no-ref heading settled" id="references">References<a class="self-link" href="#references"></a></h2> <h3 class="no-num no-ref heading settled" id="normative">Normative References<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/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">Informative References<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 || {}; // 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. const typeFormatters = { 'dfn': (text) => `[=${text}=]`, 'abstract-op': (text) => `[\$${text}\$]`, 'value': (text) => `''${text}''`, 'http-header': (text) => `[:${text}:]`, 'idl': (text) => `{{${text}}}`, 'interface': 'idl', 'constructor': 'idl', 'method': 'idl', 'argument': 'idl', 'attribute': 'idl', 'callback': 'idl', 'dictionary': 'idl', 'dict-member': 'idl', 'enum': 'idl', 'enum-value': 'idl', 'exception': 'idl', 'const': 'idl', 'typedef': 'idl', 'stringifier': 'idl', 'serializer': 'idl', 'iterator': 'idl', 'maplike': 'idl', 'setlike': 'idl', 'extended-attribute': 'idl', 'event': 'idl', 'element': (element) => `<{${element}}>`, 'element-state': 'element', 'element-attr': 'element', 'attr-value': 'element', 'scheme': 'dfn', 'permission': 'dfn', 'grammar': (text) => `${text} (within a <pre class=prod>)`, 'type': (text)=> `<<${text}>>`, 'property': (text) => `'${text}'`, 'descriptor': 'property', 'function': 'value', 'at-rule': 'value', 'selector': 'value', }; const typesUsingFor = new Set( [ "descriptor", "value", "element-attr", "attr-value", "element-state", "method", "constructor", "argument", "attribute", "const", "dict-member", "event", "enum-value", "stringifier", "serializer", "iterator", "maplike", "setlike", "state", "mode", "context", "facet", ], ) const typesNotUsingFor = new Set( [ "property", "element", "interface", "namespace", "callback", "dictionary", "enum", "exception", "typedef", "http-header", "permission", ], ) function linkFormatterFromType(type) { const fnOrType = typeFormatters[type]; if(typeof fnOrType === 'string') { // follow the alias return linkFormatterFromType(fnOrType); } return fnOrType; }; 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(!typesUsingFor.has(type)) { for(const lt of ltAlts) { linkingSyntaxes.push(linkFormatter(lt)); } } if(!typesNotUsingFor.has(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) ) ); }) ) ]; } function genDfnPanel({ dfn, dfnID, url, dfnText, refSections, external }) { const dfnPanel = 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, class:"dfn-link"}, 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})` ), " ", ] ), ), ), ), genLinkingSyntaxes(dfn), ); dfnPanel.forDfn = dfn; if(!dfn) { console.log(dfnPanel); } return dfnPanel; } 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); continue; } const panel = genDfnPanel({ ...panelData, dfn }); append(document.body, panel); insertDfnPopupAction(panel) } } document.addEventListener("DOMContentLoaded", ()=>{ genAllDfnPanels(); 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) { hideAllDfnPanels(); // Only display one at this time. const dfn = dfnPanel.forDfn; dfn.setAttribute("aria-expanded", "true"); dfnPanel.classList.add("on"); positionDfnPanel(dfnPanel); let tabIndex = 100; dfn.tabIndex = tabIndex++; // Increment tabindex for each anchor and button tags in panel const tabbable = dfnPanel.querySelectorAll(":is(a, button)"); for (const el of tabbable) { el.tabIndex = tabIndex++; } } function positionDfnPanel(dfnPanel) { const dfn = dfnPanel.forDfn; const dfnPos = getRootLevelAbsolutePosition(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(dfnPanel) { const dfn = dfnPanel.forDfn; dfn.setAttribute("aria-expanded", "false"); dfn.tabIndex = undefined; dfnPanel.style.position = "absolute"; // unfix it dfnPanel.classList.remove("on"); dfnPanel.classList.remove("activated"); } function toggleDfnPanel(dfnPanel) { if(dfnPanel.classList.contains("on")) { hideDfnPanel(dfnPanel); } else { showDfnPanel(dfnPanel); } } function insertDfnPopupAction(dfnPanel) { const dfn = dfnPanel.forDfn; dfn.setAttribute('role', 'button'); dfn.setAttribute('aria-expanded', 'false') dfn.tabIndex = 0; dfn.classList.add('has-dfn-panel'); dfn.addEventListener('click', (event) => { showDfnPanel(dfnPanel); event.stopPropagation(); }); dfn.addEventListener('keypress', (event) => { const kc = event.keyCode; // 32->Space, 13->Enter if(kc == 32 || kc == 13) { toggleDfnPanel(dfnPanel); event.stopPropagation(); event.preventDefault(); } }); 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, 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(); }); } // Returns the root-level absolute position {left and top} of element. function getRootLevelAbsolutePosition(el) { const boundsRect = el.getBoundingClientRect(); let xPos = 0; let yPos = 0; while (el) { let xScroll = el.scrollLeft; let yScroll = el.scrollTop; // Ignore scrolling of body. if (el.tagName === "BODY") { xScroll = 0; yScroll = 0; } xPos += (el.offsetLeft - xScroll + el.clientLeft); yPos += (el.offsetTop - yScroll + el.clientTop); el = el.offsetParent; } return { left: xPos, top: yPos, right: xPos + boundsRect.width, bottom: yPos + boundsRect.height, }; } function scrolledIntoView(element) { const rect = element.getBoundingClientRect(); return ( rect.top > 0 && rect.bottom < window.innerHeight ); } function scrollToTargetAndHighlight(event) { let hash = event.target.hash; if (hash) { hash = decodeURIComponent(hash.substring(1)); const dest = document.getElementById(hash); if (dest) { // Maybe prevent default scroll. if (scrolledIntoView(dest)) { event.preventDefault(); } dest.classList.add('highlighted'); setTimeout(() => dest.classList.remove('highlighted'), 1000); } } } window.addEventListener("resize", () => { // Pin any visible dfn panel queryAll(".dfn-panel.on, .dfn-panel.activated").forEach(el=>positionDfnPanel(el)); }); } </script> <script>/* Boilerplate: script-dfn-panel-json */ window.dfnpanelData = {}; window.dfnpanelData['b923fc87'] = {"dfnID": "b923fc87", "url": "https://www.w3.org/policies/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"}], "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": "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>