forked from w3c/process
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathindex.bs
5481 lines (4543 loc) · 221 KB
/
index.bs
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
<!--
This document is formatted using Bikeshed.
Roughly speaking, it is a Markdown preprocessor,
with additional functionality for cross-spec autolinking,
automatic generation of indexes/ToC/etc,
and many other features.
See https://tabatkins.github.io/bikeshed/ for detailed documentation.
When making edits, please respect the following coding style:
- Tabs for indentation, spaces for alignment.
- Semantic line breaks: at phrases boundaries, each line < ~80ch
- Indent the entire spec one level except for headings.
- Line break after opening heading tag, so heading text
is easy to pick out when scanning the source.
- Empty lines between blocks.
- Indent contents of block-level HTML elements
(except <p>, which we usually imply via Markdown formatting
and otherwise leave inlined at the start of the paragraph).
Definitely leave a break and indent
after any block start tag with attributes, though.
- No optional end tags.
- Use manual IDs so that IDs remain stable as you adjust the heading text;
add old IDs (via empty elements with IDs, or e.g. Bikeshed's oldids attribute)
when removing or changing IDs so that links to your spec don't break.
-->
<pre class='metadata'>
Title: W3C Process Document
Group: processcg
Status: CG-DRAFT
ED: https://www.w3.org/Consortium/Process/Drafts/
TR: https://www.w3.org/Consortium/Process/
Previous Version: https://www.w3.org/2021/Process-20211102/
Previous Version: https://www.w3.org/2020/Process-20200915/
Previous Version: https://www.w3.org/2019/Process-20190301/
Previous Version: https://www.w3.org/2018/Process-20180201/
Previous Version: https://www.w3.org/2017/Process-20170301/
Editor: Elika J. Etemad / fantasai, Invited Expert, https://fantasai.inkedblade.net/contact
Editor: Florian Rivoal, Invited Expert, https://florian.rivoal.net/
Former Editor: Natasha Rooney, Invited Expert
Former Editor: Charles McCathie Nevile, Yandex, http://yandex.com
Former Editor: Ian Jacobs, W3C, https://www.w3.org/
Level: none
Repository: w3c/w3process
Shortname: w3process
Abstract:
The mission of the World Wide Web Consortium (<abbr>W3C</abbr>) is to lead the World Wide Web to its full potential
by developing common protocols that promote its evolution and ensure its interoperability.
The W3C Process Document describes the organizational structure of the W3C and processes,
responsibilities and functions that enable W3C to accomplish its mission.
This document does not describe the internal workings of the Team.
For more information about the W3C mission and the history of W3C,
please refer to <a href="https://www.w3.org/Consortium/">About W3C</a>.
Status Text:
This document,
which is based on the <a href="https://www.w3.org/2021/Process-20211102/">2 November 2021 Process</a>,
is a work in progress
and further changes may occur before completion of this revision cycle.
As detailed in <a href="https://www.w3.org/Consortium/Process/#GAProcess">Section 11 Process Changes</a>,
once the W3C Advisory Board considers it ready for adoption,
it will be offered for W3C Advisory Committee Review.
Issue Tracking: Github (preferred) https://github.com/w3c/w3process/issues/
Issue Tracking: Public mailing list https://lists.w3.org/Archives/Public/public-w3process/
Issue Tracking: Member-only mailing list https://lists.w3.org/Archives/Member/process-issues
Boilerplate: repository-issue-tracking off
</pre>
<style>
.about { margin-left: 3em; margin-right: 3em; font-size: .83em}
table { margin-left: auto; margin-right: auto }
.diagram { text-align: center; margin: 2.5em 0 }
.issue::before {content: "Issue: "}
.issue {border: 2px dashed red; background-color: #ffa;}
.issue .issue {background-color: #fcc;}
.rfc2119 {font-variant:small-caps}
/*for the SVG - navigation highlighting */
:focus path,
:focus polygon,
:focus 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>
<!--[if lt IE 9]><script src='undefined://www.w3.org/2008/site/js/html5shiv.js'></script><![endif]-->
<h2 class="no-num no-toc no-ref" id="pp">
Relation of Process Document to Patent Policy</h2>
W3C Members' attention is called to the fact
that provisions of the Process Document are binding on Members
per the <a href="https://www.w3.org/Consortium/Agreement/Member-Agreement">Membership Agreement</a> [[MEMBER-AGREEMENT]].
The <a href="https://www.w3.org/Consortium/Patent-Policy/">W3C Patent Policy</a> [[!PATENT-POLICY]]
is incorporated by normative reference as a part of the Process Document,
and is thus equally binding.
The Patent Policy places 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 and Patent Policy have been designed to allow them to evolve independently.
In the Process Document, the term “participant” refers to an individual, not an organization.
<h2 class="no-num no-toc no-ref" id=terms>
Conformance and specialized terms</h2>
The terms
<em class="rfc2119">must</em>,
<em class="rfc2119">must not</em>,
<em class="rfc2119">should</em>,
<em class="rfc2119">should not</em>,
<em class="rfc2119">required</em>,
and <em class="rfc2119">may</em>
are used in accordance with <a href="https://www.ietf.org/rfc/rfc2119.txt">RFC 2119</a>.
The term <dfn id="not-required" noexport><em class="rfc2119">not required</em></dfn>
is equivalent to the term <em class="rfc2119">may</em>
as defined in RFC2119
[[!RFC2119]].
Some terms have been capitalized in this document (and in other W3C materials)
to indicate that they are entities with special relevance to the W3C Process.
These terms are defined within this document,
and readers are reminded that the ordinary English definitions are insufficient
for the purpose of understanding this document.
<nav data-fill-with="table-of-contents"></nav>
<main>
<h2 id="Intro">
Introduction</h2>
W3C work revolves around the standardization of Web technologies.
To accomplish this work, W3C follows processes that promote the development of high-quality standards
based on the <a href="#Consensus">consensus</a> of the Membership, Team, and public.
W3C processes promote fairness, responsiveness, and progress:
all facets of the W3C mission.
This document describes the processes W3C follows in pursuit of its mission.
The W3C Process promotes the goals of quality and fairness in technical decisions
by encouraging <a href="#Consensus">consensus</a>,
soliciting reviews (by both Members and public),
incorporating implementation and interoperability experience,
and requiring Membership-wide approval as part of the <a href="#Reports">technical report development process</a>.
[[#group-participation|Participants]] in W3C include
<a href="#member-rep">representatives of its Members</a> and the [=Team=],
as well as <a href="#invited-expert-wg">Invited Experts</a>
who can bring additional expertise or represent additional stakeholders.
[=Team=] representatives both contribute to the technical work
and help ensure each group's proper integration with the rest of W3C.
W3C’s technical standards, called [=W3C Recommendations=],
are developed by its [=Working Groups=];
W3C also has other types of publications,
all described in [[#Reports]].
W3C has various types of groups;
this document describes the formation and policies
of its chartered [=Working Groups=] and [=Interest Groups=],
see [[#Policies]] and [[#GAGeneral]].
W3C also operates Community and Business Groups,
which are separately described in <a href="https://www.w3.org/community/about/agreements/">their own process document</a> [[BG-CG]].
In addition, several groups are formally established by the Consortium:
the <a href="#AC">W3C Advisory Committee</a>, which has a representative from each Member,
and two oversight groups elected by its membership:
the <a href="#AB">Advisory Board (AB)</a>,
which helps resolve Consortium-wide non-technical issues and manages the <a href="#GAProcess">evolution of the W3C process</a>;
and the <a href="#TAG">Technical Architecture Group (TAG)</a>,
which helps resolve Consortium-wide technical issues.
Here is a general overview of how W3C initiates standardization of a Web technology:
<ol>
<li>
People generate interest in a particular topic.
For instance, Members express interest by developing proposals in Community Groups
or proposing ideas in <a href="#Submission">Member Submissions</a>.
Also, the <a href="#Team">Team</a> monitors work inside and outside of W3C for signs of interest,
and helps organize <a href="#GAEvents">Workshops</a> to bring people together
to discuss topics that interest the W3C community.
<li>
When there is enough interest and an engaged community,
the [=Team=] works with the Membership
to draft proposed <a href="#WGCharterDevelopment">Interest Group or Working Group charters</a>.
W3C Members <a href="#CharterReview">review</a> the proposed charters,
and when there is support within W3C for investing resources in the topic of interest,
the W3C approves the group(s),
and they begin their work.
</ol>
Further sections of this Process Document deal with topics including
liaisons ([[#Liaisons]]),
confidentiality ([[#dissemination]]),
and formal decisions and appeals ([[#decisions]]).
<h2 id="Organization">
Members and the Team</h2>
W3C's mission is to 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 id="Members">
Members</h3>
<dfn lt="W3C Member|Member">W3C Members</dfn> are
organizations subscribed according to the <a href="https://www.w3.org/Consortium/Agreement/Member-Agreement">Membership Agreement</a> [[MEMBER-AGREEMENT]].
They are represented in W3C processes as follows:
<ol>
<li>
One representative per Member organization particiaptes
in the [=Advisory Committee=]
which oversees the work of the W3C.
<li>
Representatives of Member organizations participate
in <a href="#GAGeneral">Working Groups and Interest Groups</a>,
where they author and review <a href="#Reports">technical reports</a>.
</ol>
<p id="MemberSubscription">W3C membership is open to all entities,
as described in “<a href="https://www.w3.org/Consortium/join">How to Join W3C</a>” [[JOIN]];
(refer to the public list of <a href="https://www.w3.org/Consortium/Member/List">current W3C Members</a> [[MEMBER-LIST]]).
The <a href="#Team">Team</a> <em class="rfc2119">must</em> ensure
that Member participation agreements remain <a href="#Team-only">Team-only</a>
and that no Member receives preferential treatment within W3C.
<p id="IndividualParticipation">While W3C does not have a class of membership tailored to individuals,
individuals <em class="rfc2119">may</em> join W3C.
Restrictions pertaining to <a href="#MemberRelated">related Members</a> apply
when the individual also <a href="#member-rep">represents</a> another W3C Member.
<h4 id="MemberBenefits">
Rights of Members</h4>
Each Member organization enjoys the following rights and benefits:
<ul>
<li>
A seat on the <a href="#AC">Advisory Committee</a>;
<li>
Access to <a href="#Member-only">Member-only</a> information;
<li>
The <a href="#Submission">Member Submission</a> process;
<li>
Use of the W3C Member logo on promotional material and to publicize the Member's participation in W3C.
For more information, please refer to the Member logo usage policy
described in the <a href="https://www.w3.org/Member/Intro">New Member Orientation</a> [[INTRO]].
</ul>
Furthermore, subject to further restrictions included in 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">W3C Fellows</a>.
</ul>
The rights and benefits of W3C membership [[MEMBER-AGREEMENT]]
are contingent upon conformance to the processes described in this document.
Disciplinary action for anyone participating in W3C activities is described in [[#discipline]].
Additional information for Members is available at the <a href="https://www.w3.org/Member/">Member Web site</a> [[MEMBER-HP]].
<h4 id="RelatedAndConsortiumMembers">
Member Consortia and Related Members</h4>
<h5 id="MemberConsortia">
Membership Consortia</h5>
A “<dfn id=fdn-member-consortium lt="Member Consortium | Member Consortia">Member Consortium</dfn>” means a consortium,
user society,
or association of two or more individuals,
companies,
organizations or governments,
or any combination of these entities
which has the purpose of participating in a common activity
or pooling resources to achieve a common goal other than participation in,
or achieving certain goals in,
W3C.
A joint-stock corporation or similar entity is not a [=Member Consortium=]
merely because it has shareholders or stockholders.
If it is not clear whether a prospective Member qualifies as a [=Member Consortium=],
the [=CEO=] may reasonably make the determination.
For a [=Member Consortium=], the rights and privileges of W3C Membership
described in the W3C Process Document extend to the [=Member Consortium=]'s paid staff
and Advisory Committee representative.
[=Member Consortia=] <em class="rfc2119">may</em> also designate
up to four (or more at the Team's discretion) individuals
who, though not employed by the organization,
<em class="rfc2119">may</em> exercise the rights of <a href="#member-rep">Member representatives</a>.
For [=Member Consortia=] that have individual people as members,
these individuals <em class="rfc2119">must</em> disclose their employment affiliation
when participating in W3C work.
Provisions for <a href="#MemberRelated">related Members</a> apply.
Furthermore, these individuals <em class="rfc2119">must</em> represent the broad interests of the W3C Member organization
and not the particular interests of their employers.
For Member Consortia that have organizations as Members,
all such designated representatives <em class="rfc2119">must</em> be an official representative of the Member organization
(e.g. a Committee or Task Force Chairperson)
and <em class="rfc2119">must</em> disclose their employment affiliation when participating in W3C work.
Provisions for <a href="#MemberRelated">related Members</a> apply.
Furthermore, these individuals <em class="rfc2119">must</em> represent the broad interests of the W3C Member organization
and not the particular interests of their employers.
For all representatives of a Member Consortium,
IPR commitments are made on behalf of the Member Consortium,
unless a further IPR commitment is made by the individuals' employers.
<h5 id="MemberRelated">
Related Members</h5>
In the interest of ensuring the integrity of the consensus process,
Member involvement in some of the processes in this document is affected by related Member status.
As used herein, two Members are <dfn export lt="Related Member">related</dfn> if:
<ol>
<li>
Either Member is a [=subsidiary=] of the other, or
<li>
Both Members are [=subsidiaries=] of a common entity, or
<li>
The Members have an employment contract or consulting contract that affects W3C participation.
</ol>
A <dfn>subsidiary</dfn> is an organization of which effective control and/or majority ownership rests with another,
single organization.
[=Related Members=] <em class="rfc2119">must</em> disclose these relationships
according to the mechanisms described in the <a href="https://www.w3.org/Member/Intro">New Member Orientation</a> [[INTRO]].
<h3 id="Team">
The W3C Team</h3>
The <dfn export lt="Team | W3C Team">Team</dfn> consists of
the Director,
<dfn>CEO</dfn>,
W3C paid staff,
unpaid interns,
and W3C Fellows.
<dfn id="fellows">W3C Fellows</dfn> are Member employees working as part of the Team;
see the <a href="https://www.w3.org/Consortium/Recruitment/Fellows">W3C Fellows Program</a> [[FELLOWS]].
The Team provides technical leadership about Web technologies,
organizes and manages W3C activities to reach goals
within practical constraints (such as resources available),
and communicates with the Members and the public
about the Web and W3C technologies.
The [=Director=] and CEO <em class="rfc2119">may</em> delegate responsibility
(generally to other individuals in the Team)
for any of their roles described in this document,
except <a href="#tag-participation">participation in the TAG</a>.</p>
<dfn noexport lt="Team Decision | Team's Decision">Team Decisions</dfn> derive from the [=Director=] and [=CEO=]'s authority,
even when they are carried out by other members of the [=Team=].
The <dfn id="def-Director" export lt="Director|W3C Director">Director</dfn> is the lead technical architect at W3C,
whose responsibilities are identified throughout this document in relevant places.
Some key ones include:
assessing <a href="#def-Consensus" id="DirectorDecision">consensus</a> within W3C for architectural choices,
publication of <a href="#Reports">technical reports</a>,
and chartering new Groups;
appointing group <a href="#GeneralChairs">Chairs</a>,
adjudicating as "tie-breaker" for [=Group decision appeals=],
and deciding on the outcome of formal objections;
the Director is generally Chair of the <a href="#TAG">TAG</a>.
Team administrative information such as Team salaries,
detailed budgeting,
and other business decisions
are <a href="#Team-only">Team-only</a>,
subject to oversight by the [=Host institutions=].
Note: W3C is not currently incorporated.
For legal contracts, W3C is represented by four <dfn id="hosts" lt="Hosts|Host institutions">“Host” institutions</dfn>:
Beihang University,
the European Research Consortium for Informatics and Mathematics (<abbr>ERCIM</abbr>),
Keio University,
and the Massachusetts Institute of Technology (<abbr>MIT</abbr>).
Within W3C, the Host institutions are governed by hosting agreements;
the [=Hosts=] themselves are not W3C Members.
<h2 id=groups>
Groups and Participation</h2>
For the purposes of this Process, a <dfn lt="W3C Group" local-lt="group">W3C Group</dfn> is one of W3C’s
<a href="#wgparticipant">Working Groups</a>,
<a href="#igparticipant">Interest Groups</a>,
<a href="#AC">Advisory Committee</a>,
<a href="#ABParticipation">Advisory Board</a>,
or <a href="#tag-participation">TAG</a>,
and a <dfn>participant</dfn> is a member of such a group.
<h3 id="Policies">
Policies for Participation in W3C Groups</h3>
<h4 id="ParticipationCriteria">
Individual Participation Criteria</h4>
<h5 id="discipline">
Expectations and Discipline</h5>
There are three qualities an individual is expected to demonstrate in order to participate in W3C:
<ol>
<li>
Technical competence in one's role;
<li>
The ability to act fairly;
<li>
Social competence in one's role.
</ol>
[=Advisory Committee representatives=] who nominate individuals from their organization for participation in W3C activities
are responsible for assessing and attesting to the qualities of those nominees.
<p>Participants in any W3C activity <em class="rfc2119">must</em> abide
by the terms and spirit of the <a href="https://www.w3.org/Consortium/cepc/">W3C Code of Ethics and Professional Conduct</a> [[!CEPC]]
and the participation requirements described in
“Disclosure”
in the W3C Patent Policy [[!PATENT-POLICY]].
The [=CEO=] <em class="rfc2119">may</em> take disciplinary action,
including suspending or removing for cause
a participant in any group (including the [=AB=] and [=TAG=])
if serious and/or repeated violations,
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 id="coi">
Conflict of Interest Policy</h5>
Individuals participating materially in W3C work <em class="rfc2119">must</em> disclose significant relationships
when those relationships might reasonably be perceived as creating a conflict of interest with the individual's role at W3C.
These disclosures <em class="rfc2119">must</em> be kept up-to-date
as the individual's affiliations change and W3C membership evolves
(since, for example, the individual might have a relationship with an organization that joins or leaves W3C).
Each section in this document that describes a W3C group
provides more detail about the disclosure mechanisms for that group.
The ability of an individual to fulfill a role within a group
without risking a conflict of interest depends on the individual's affiliations.
When these affiliations change,
the individual's assignment to the role <em class="rfc2119">must</em> be evaluated.
The role <em class="rfc2119">may</em> be reassigned according to the appropriate process.
For instance,
the [=Team=] <em class="rfc2119">may</em> appoint a new group [=Chair=]
when the current Chair changes affiliations
(e.g., if there is a risk of conflict of interest,
or if there is risk that the Chair's new employer will be over-represented within a W3C activity).
The following are some scenarios where disclosure is appropriate:
<ul>
<li>
Paid consulting for an organization whose activity is relevant to W3C,
or any consulting compensated with equity
(shares of stock, stock options, or other forms of corporate equity).
<li>
A decision-making role/responsibility
(such as participating on the Board) in other organizations relevant to W3C.
<li>
A position on a publicly visible advisory body,
even if no decision-making authority is involved.
</ul>
Individuals seeking assistance on these matters <em class="rfc2119">should</em> contact the [=Team=].
[=Team=] members are subject to the <a href="https://www.w3.org/2000/09/06-conflictpolicy">W3C Team conflict of interest policy</a> [[!CONFLICT-POLICY]].
<h5 id="member-rep">
Individuals Representing a Member Organization</h5>
Generally, individuals representing a Member in an official capacity within W3C
are employees of the Member organization.
However, an [=Advisory Committee representative=] <em class="rfc2119">may</em> designate a non-employee
to represent the Member.
Non-employee Member representatives <em class="rfc2119">must</em> disclose
relevant affiliations to the Team and to any group in which the individual participates.
In exceptional circumstances
(e.g., situations that might jeopardize the progress of a group or create a <a href="#coi">conflict of interest</a>),
the [=CEO=] <em class="rfc2119">may</em> decline
to allow an individual designated by an Advisory Committee representative to participate in a group.
A group charter <em class="rfc2119">may</em> limit
the number of individuals representing a W3C Member
(or group of <a href="#MemberRelated">related Members</a>).
<h4 id="GeneralMeetings">
Meetings</h4>
The requirements in this section apply to the official meetings of any [=W3C group=].
<p>W3C distinguishes two types of meetings:</p>
<ol>
<li>
A <dfn id="ftf-meeting">face-to-face meeting</dfn> is one
where most of the attendees are expected to participate in the same physical location.
<li>
A <dfn id="distributed-meeting">distributed meeting</dfn> is one
where most of the attendees are expected to participate from remote locations
(e.g., by telephone, video conferencing, or <abbr title="Internet Relay Chat">IRC</abbr>).
</ol>
A [=Chair=] <em class="rfc2119">may</em> invite an individual with a particular expertise
to attend a meeting on an exceptional basis.
This person is a meeting guest,
not a group [=participant=].
Meeting guests do not have <a href="#Votes">voting rights</a>.
It is the responsibility of the Chair to ensure
that all meeting guests respect the chartered <a href="#confidentiality-levels">level of confidentiality</a>
and other group requirements.
<h5 id="meeting-schedules">
Meeting Scheduling and Announcements</h5>
Meeting announcements <em class="rfc2119">should</em> be sent to all appropriate group mailing lists,
i.e. those most relevant to the anticipated meeting participants.
The following table lists <em class="rfc2119">recommendations</em> for organizing a meeting:
<table class="data">
<thead>
<tr>
<td>
<th scope=col>Face-to-face meetings
<th scope=col>Distributed meetings
<tbody>
<tr>
<th scope=row>Meeting announcement (before)
<td><span class="time-interval">eight weeks<sup>*</sup></span>
<td><span class="time-interval">one week<sup>*</sup></span>
<tr>
<th scope=row>Agenda available (before)
<td><span class="time-interval">two weeks</span>
<td><span class="time-interval">24 hours</span> (or longer if a meeting is scheduled after a weekend or holiday)
<tr>
<th scope=row>Participation confirmed (before)
<td><span class="time-interval">three days</span>
<td><span class="time-interval">24 hours</span>
<tr>
<th scope=row>Action items available (after)
<td><span class="time-interval">three days</span>
<td><span class="time-interval">24 hours</span>
<tr>
<th scope=row>[=Minutes=] available (after)
<td><span class="time-interval">two weeks</span>
<td><span class="time-interval">48 hours</span>
</table>
<sup>*</sup> To allow proper planning (e.g., travel arrangements),
the Chair is responsible for giving sufficient advance notice
about the date and location of a meeting.
Shorter notice for a meeting is allowed
provided that there are no objections from group participants.
<h5 id="meeting-minutes">
Meeting Minutes</h5>
Groups <em class=rfc2119>should</em> take and retain <dfn>minutes</dfn> of their meetings,
and <em class="rfc2119">must</em> record
any official [=group decisions=] made during the meeting discussions.
Details of the discussion leading to such decisions are not required,
provided that the rationale for the [=group decision=] is nonetheless clear.
<h5 id="meeting-recording">
Meeting Recordings and Transcripts</h5>
No-one may take an audio or video recording of a meeting,
or retain an automated transcript,
unless the intent is announced at the start of the meeting,
and no-one participating in the recorded portion of the meeting withholds consent.
If consent is withheld by anyone, recording/retention <em class=rfc2119>must</em> not occur.
The announcement <em class=rfc2119>must</em> cover:
(a) who will have access to the recording or transcript and
(b) the purpose/use of it and
(c) how it will be retained (e.g. privately, in a cloud service) and for how long.
<h4 id="tooling">
Tooling for Discussions and Publications</h4>
For [=W3C Groups=] operating under this Process,
a core operating principle is to allow access across disabilities,
across country borders,
and across time.
Thus in order to allow all would-be participants to effectively participate,
to allow future participants and observers to understand the rationale and origins of current decisions,
and to guarantee long-lived access to its publications,
W3C requires that:
<ul>
<li id=report-stability>
All reports, publications, or other deliverables
produced by the group for public consumption
(i.e. intended for use or reference outside its own membership)
<em class=rfc2119>should</em> be published and promoted at a W3C-controlled URL,
and backed up by W3C systems
such that if the underlying service is discontinued,
W3C can continue to serve such content without breaking incoming links
or other key functionality.
<li id=report-accessibility>
All reports, publications, or other deliverables
produced by the group for public consumption
<em class=rfc2119>should</em> follow best practices for internationalization
and for accessibility to people with disabilities.
Network access to W3C-controlled domains may be assumed.
<li id=discussion-archiving>
Official meeting minutes and other records of decisions made <em class=rfc2119>must</em>
be archived by W3C for future reference;
and other persistent text-based discussions
sponsored by the group,
pertaining to their work
and intended to be referenceable by all group members
<em class=rfc2119>should</em> be.
This includes discussions conducted over email lists
or in issue-tracking services
or any equivalent fora.
Materials referenced from discussions
and necessary to understand them
should be available at a stable URL,
at a level of confidentiality no stricter than the discussion minutes.
Note: The lack, or loss, of such archives does not by itself
invalidate an otherwise-valid decision.
<li id=tool-accessibility>
Any tooling used by the group
for producing its documentation and deliverables
or for official group discussions
<em class=rfc2119>should</em> be usable
(without additional cost)
by all who wish to participate,
including people with disabilities,
to allow their effective participation.
Note: If a new participant joins who cannot use the tool,
this can require the [=Working Group=] to change its tooling
or operate some workaround.
<li id=where-is-your-stuff>
All tools and archives used by the group
for its discussions and recordkeeping
<em class=rfc2119>should</em> be documented
such that new participants and observers
can easily find the group’s tools and records.
</ul>
The [=Team=] is responsible for ensuring adherence to these rules
and for bringing any group not in compliance into compliance.
<h4 id="resignation">
Resignation from a Group</h4>
A W3C Member or Invited Expert <em class="rfc2119">may</em> resign from a group.
On written notification from an Advisory Committee representative
or Invited Expert
to the team,
the Member and their representatives
or the Invited Expert
will be deemed to have resigned from the relevant group.
The team <em class="rfc2119">must</em> record the notification.
See “Exclusion and Resignation from the Working Group” in the W3C Patent Policy [[PATENT-POLICY]]
for information about obligations remaining after resignation from certain groups.
<h3 id="AC">
The Advisory Committee (AC)</h3>
<h4 id=ac-role>
Role of the Advisory Committee</h4>
<p id=ReviewAppeal>
The <dfn export lt="Advisory Committee|AC">Advisory Committee</dfn> represents
the [=Members=] of the 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 the W3C:
<a href="#CharterReview">Charter Proposals</a>,
<a href="#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>
[=Advisory Committee representatives=] <em class="rfc2119">may</em> initiate
an <a href="#ACAppeal">Advisory Committee Appeal</a>
of a [=W3C decision=]
or [=Director=]'s decision.
See also the additional roles of [=Advisory Committee representatives=]
described in the W3C Patent Policy [[PATENT-POLICY]].
<h4 id=ac-participation>
Participation in the Advisory Committee</h4>
The [=Advisory Committee=]
is composed of one <dfn export lt="Advisory Committee representative| AC representative">representative</dfn>
from each Member organization
(refer to the [=Member-only=] list
of <a href="https://www.w3.org/Member/ACList">current Advisory Committee representatives</a>. [[CURRENT-AC]])
When an organization joins W3C
(see “<a href="https://www.w3.org/Consortium/join">How to Join W3C</a>” [[JOIN]]),
it <em class="rfc2119">must</em> name its Advisory Committee representative as part of the Membership Agreement.
The <a href="https://www.w3.org/Member/Intro">New Member Orientation</a> [[INTRO]]
explains how to subscribe or unsubscribe to Advisory Committee mailing lists,
provides information about <a href="#ACMeetings">Advisory Committee Meetings</a>,
explains how to name a new [=Advisory Committee representative=],
and more.
[=Advisory Committee representatives=] <em class="rfc2119">must</em> follow the <a href="#coi">conflict of interest policy</a>
by disclosing information according to the mechanisms described in the New Member Orientation.
The AC representative may delegate any of their rights and responsibilities
to an <dfn export lt="alternate AC representative | alternate Advisory Committee representative | alt AC rep">alternate</dfn>
(except the ability to designate an alternate).
<h4 id="ACCommunication">
Advisory Committee Mailing Lists</h4>
The [=Team=] <em class="rfc2119">must</em> provide two mailing lists for use by the [=Advisory Committee=]:
<ol>
<li>
One for official announcements (e.g., those required by this document) from the [=Team=] to the [=Advisory Committee=].
This list is read-only for Advisory Committee representatives.
<li>
One for discussion among [=Advisory Committee representatives=].
Though this list is primarily for Advisory Committee representatives,
the [=Team=] <em class="rfc2119">must</em> monitor discussion
and <em class="rfc2119">should</em> participate in discussion when appropriate.
Ongoing detailed discussions <em class="rfc2119">should</em> be moved to other appropriate lists
(new or existing, such as a mailing list created for a <a href="#GAEvents">Workshop</a>).
</ol>
An [=Advisory Committee representative=] <em class="rfc2119">may</em> request
that additional individuals from their organization be subscribed to these lists.
Failure to contain distribution internally
<em class="rfc2119">may</em> result in suspension of additional email addresses,
at the discretion of the Team.
<h4 id="ACMeetings">
Advisory Committee Meetings</h4>
The [=Team=] organizes a <a href="#ftf-meeting">face-to-face meeting</a> for the [=Advisory Committee=]
<span class="time-interval">twice a year</span>.
The [=Team=] appoints the Chair of these meetings (generally the CEO).
At each Advisory Committee meeting,
the Team <em class="rfc2119">should</em> provide an update to the Advisory Committee about:
<dl>
<dt><em>Resources</em>
<dd>
<ul>
<li>
The number of W3C Members at each level.
<li>
An overview of the financial status of W3C.
</ul>
<dt><em>Allocations</em>
<dd>
<ul>
<li>
The allocation of the annual budget, including size of the Team and their approximate deployment.
<li>
A list of all activities (including but not limited to Working and Interest Groups)
and brief status statement about each,
in particular those started or terminated since the previous Advisory Committee meeting.
<li>
The allocation of resources to pursuing <a href="#Liaisons">liaisons</a> with other organizations.
</ul>
</dd>
</dl>
Each Member organization <em class="rfc2119">should</em> send one <a href="#member-rep">representative</a>
to each Advisory Committee Meeting.
In exceptional circumstances
(e.g., during a period of transition between representatives from an organization),
the meeting Chair <em class="rfc2119">may</em> allow a Member organization to send two representatives to a meeting.
The [=Team=] <em class="rfc2119">must</em> announce the date and location of each Advisory Committee meeting
no later than at the end of the previous meeting;
<span class="time-interval">one year's</span> notice is preferred.
The Team <em class="rfc2119">must</em> announce the region of each Advisory Committee meeting
at least <span class="time-interval">one year</span> in advance.
More information about <a href="https://www.w3.org/Member/Meeting/">Advisory Committee meetings</a> [[AC-MEETING]]
is available at the Member Web site.
<h3 id=elected-groups>
Elected Groups: The AB and the TAG</h3>
The W3C Process defines two types of <dfn id=elected-group export>elected groups</dfn>:
the [=Advisory Board=] (AB) and
the [=Technical Architecture Group=] (TAG),
both elected by the [=Advisory Committee=].
<h4 id="AB">
Advisory Board (AB)</h4>
<h5 id=ab-role>
Role of the Advisory Board</h5>
The <dfn export lt="Advisory Board|AB">Advisory Board</dfn> provides ongoing guidance to the Team
on issues of strategy,
management,
legal matters,
process,
and conflict resolution.
The Advisory Board also serves the Members
by tracking issues raised between Advisory Committee meetings,
soliciting Member comments on such issues,
and proposing actions to resolve these issues.
The Advisory Board manages the <a href="#GAProcess">evolution of the Process Document</a>.
The Advisory Board hears a <a href="#SubmissionNo">Submission Appeal</a>
when a Member Submission is rejected
for reasons unrelated to Web architecture;
see also the <a href="#TAG">TAG</a>.
The [=Advisory Board=] is <strong>not</strong> a board of directors
and has no decision-making authority within W3C;
its role is strictly advisory.
Details about the Advisory Board
(e.g., the list of Advisory Board participants,
mailing list information, and summaries of Advisory Board meetings)
are available at the <a href="https://www.w3.org/2002/ab/">Advisory Board home page</a> [[AB-HP]].
<h5 id="ABParticipation">
Composition of the Advisory Board</h5>
The [=Advisory Board=] consists of nine to eleven elected participants and one Chair
(who <em class=rfc2119>may</em> be one of the elected participants).
With the input of the [=AB=],
the [=Team=] appoints the Chair,
who <em class=rfc2119>should</em> choose a co-chair among the elected participants.
The Chair(s) are subject to ratification by secret ballot
by two thirds of the AB upon appointment and at the start of each AB term.
The team also appoints a <a href="https://www.w3.org/Guide/teamcontact/role.html">Team Contact</a>,
as described in <a href="#ReqsAllGroups"></a>.
The CEO and Team Contact have a standing invitation
to all regular Advisory Board sessions.
The nine to eleven [=Advisory Board=] participants are elected by the W3C [=Advisory Committee=]
following the <a href="#AB-TAG-elections">AB/TAG nomination and election process</a>.
The terms of elected Advisory Board participants are for <span class="time-interval">two years</span>.
Terms are staggered so that each year,
either five or six terms expire.
If an individual is elected to fill an incomplete term,
that individual's term ends at the normal expiration date of that term.
Regular Advisory Board terms begin on 1 July and end on 30 June.</p>
<h5 id=ab-comm>
Communications of the Advisory Board</h5>
The [=Team=] <em class="rfc2119">must</em> make available a mailing list,
confidential to the Advisory Board and Team,
for the Advisory Board to use for its communication.
The [=Advisory Board=] <em class="rfc2119">should</em> send a summary of each of its meetings
to the Advisory Committee and other group Chairs.
The Advisory Board <em class="rfc2119">should</em> also report on its activities
at each <a href="#ACMeetings">Advisory Committee meeting</a>.
<h4 id="TAG">
Technical Architecture Group (TAG)</h4>
<h5 id=tag-role>
Role of the Technical Architecture Group</h5>
The mission of the <dfn export lt="Technical Architecture Group|TAG">TAG</dfn> is stewardship of the Web architecture.
There are three aspects to this mission:
<ol>
<li>
to document and build consensus around principles of Web architecture
and to interpret and clarify these principles when necessary;
<li>
to resolve issues involving general Web architecture brought to the TAG;
<li>
to help coordinate cross-technology architecture developments inside and outside W3C.
</ol>
The [=TAG=] hears a <a href="#SubmissionNo">Submission Appeal</a>
when a Member Submission is rejected for reasons related to Web architecture;
see also the <a href="#AB">Advisory Board</a>.
The [=TAG=]'s scope is limited to technical issues about Web architecture.
The TAG <em class="rfc2119">should not</em> consider
administrative,
process,
or organizational policy issues of W3C,
which are generally addressed by
the W3C Advisory Committee,
Advisory Board,
and Team.
Please refer to the <a href="https://www.w3.org/2004/10/27-tag-charter.html">TAG charter</a> [[TAG-CHARTER]]
for more information about the background and scope of the TAG,
and the expected qualifications of TAG participants.
When the [=TAG=] votes to resolve an issue,
each TAG participant
(whether appointed, elected, or the Chair)
has one vote;
see also the section on <a href="https://www.w3.org/2004/10/27-tag-charter.html#Voting">voting in the TAG charter</a> [[TAG-CHARTER]]
and the general section on <a href="#Votes">votes</a> in this Process Document.
Details about the [=TAG=]
(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> [[TAG-HP]].
<h5 id="tag-participation">
Composition of the Technical Architecture Group</h5>
The [=TAG=] consists of:
<ul>
<li>
Tim Berners-Lee, who is a life member;
<li>
The [=Director=],
sitting <i>ex officio</i>;
<li>
Three participants appointed by the [=Director=];
<li>
Six participants elected by the [=Advisory Committee=]