-
Notifications
You must be signed in to change notification settings - Fork 34
/
Copy pathindex.html
2260 lines (2017 loc) · 124 KB
/
index.html
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
---
title: Organize a Technical Report Transition (2023 Process)
submenu: [publication-policies]
toc: false
---
<div class="l-box">
<form>
<div class="l-cluster l-cluster--vertical-align">
<div class="field">
<label for="profile"><span class="field-label">Select your <a href="https://www.w3.org/policies/process/#maturity-stages">Transition steps</a> to</span></label>
<select id="profile" name="profile" class="input-width-20" >
<!-- @@ Mozilla Firefox doesn't understand the label attribute ?!? so keeping the option element text content :( -->
<optgroup label="Recommendation Track">
<option value="FPWD" label="First Public Working Draft" data-status="Working Draft">First Public Working Draft</option>
<option selected="selected" value="WD" label="Working Draft">Working Draft</option>
<option value="CR" label="Candidate Recommendation">Candidate Recommendation</option>
<option value="PR" label="Proposed Recommendation">Proposed Recommendation</option>
<option value="REC" label="Recommendation">Recommendation</option>
<option value="PR-RSCND" label="Proposed Rescinded Recommendation">Proposed Rescinded Recommendation</option>
<option value="PR-OBSL" label="Proposed Obsolete or Superseded Recommendation">Proposed Obsolete or Superseded Recommendation</option>
<option value="RSCND" label="Rescinded Recommendation">Rescinded Recommendation</option>
<option value="OBSL" label="Obsolete or Superseded Recommendation">Obsolete or Superseded Recommendation</option>
<option value="DISC" label="Discontinued Draft">Discontinued Draft</option>
</optgroup>
<optgroup label="Note Track">
<option value="FPIG-NOTE" label="First Public Interest Group Note" data-status="Interest Group Note">First Public Interest Group Note</option>
<option value="IG-NOTE" label="Interest Group Note">Interest Group Note</option>
<option value="FPWG-NOTE" label="First Public Working Group Note" data-status="Working Group Note">First Public Working Group Note</option>
<option value="WG-NOTE" label="Working Group Note">Working Group Note</option>
</optgroup>
</select>
</div>
</div>
<!-- Disabled publication of REC with echidna for now -->
<div class="field">
<fieldset id="echidna-selection" data-profile="WD|WG-NOTE|IG-NOTE|CR" data-cr="draft|snapshot" data-rec="editorial|candidate-corrections|candidate-additions">
<div class="checkbox-item">
<input type="checkbox" id="echidna-checkbox" name="echidna-checkbox">
<label for="echidna-checkbox">With the <a href="https://github.com/w3c/echidna/wiki">W3C automatic publishing system</a></label>
</div>
</fieldset>
</div>
<div class="field">
<fieldset id="draft-options" data-profile="FPWD|WD">
<div class="checkbox-item" data-profile="WD">
<input type="checkbox" id="returning-checkbox" name="returning-checkbox">
<label for="returning-checkbox">Returning to a Working Draft <a href="https://www.w3.org/policies/process/20231103/#revising-wd">for further work</a></label>
</div>
<div class="checkbox-item">
<input type="checkbox" id="informativeOnly-checkbox" name="informativeOnly-checkbox">
<label for="informativeOnly-checkbox">Not intended to become a normative Recommendation</label>
</div>
</fieldset>
</div>
<div class="field">
<fieldset id="cr-options" data-profile="CR">
<div class="radio-item">
<input type="radio" id="cr-new" name="cr" value="new" checked="checked">
<label for="cr-new">Previously published as a Working Draft or returning from Proposed Recommendation</label>
</div>
<div class="radio-item">
<input type="radio" id="cr-draft" name="cr" value="draft">
<label for="cr-draft">Updating as a Candidate Recommendation Draft</label>
</div>
<div class="radio-item">
<input type="radio" id="cr-snapshot" name="cr" value="snapshot">
<label for="cr-snapshot">Updating as a Candidate Recommendation Snapshot</label>
</div>
</fieldset>
<p data-profile="CR" data-cr="new"><strong>Note:</strong> The first Candidate Recommendation publication after verification of a transition request is also considered a Candidate Recommendation Snapshot.</p>
</div>
<div class="field">
<fieldset id="pr-options" data-profile="PR">
<div class="radio-item">
<input type="radio" id="pr-new" name="pr" value="new" checked="checked">
<label for="pr-new">Proposed by an active Working Group</label>
</div>
</fieldset>
</div>
<div class="field" data-profile="REC">
<fieldset id="rec-options">
<div class="radio-item">
<input type="radio" id="rec-new" name="rec" value="new" checked="checked">
<label for="rec-new">Previously published as a Proposed Recommendation</label>
</div>
<div class="radio-item">
<input type="radio" id="rec-editorial" name="rec" value="editorial">
<label for="rec-editorial">Publishing an existing Recommendation with editorial changes</label>
</div>
<div class="radio-item">
<input type="radio" id="rec-candidate-corrections" name="rec" value="candidate-corrections">
<label for="rec-candidate-corrections">Publishing a Recommendation with candidate corrections (substantive changes)</label>
</div>
<div class="radio-item">
<input type="radio" id="rec-candidate-additions" name="rec" value="candidate-additions">
<label for="rec-candidate-additions">Publishing a Recommendation with candidate additions (new features)</label>
</div>
<div class="radio-item">
<input type="radio" id="rec-proposed-corrections" name="rec" value="proposed-corrections">
<label for="rec-proposed-corrections">Publishing a Recommendation with proposed corrections (substantive changes)</label>
</div>
<div class="radio-item">
<input type="radio" id="rec-proposed-additions" name="rec" value="proposed-additions">
<label for="rec-proposed-additions">Publishing a Recommendation with proposed additions (new features)</label>
</div>
<div class="radio-item">
<input type="radio" id="rec-substantive" name="rec" value="substantive">
<label for="rec-substantive">Incorporating proposed corrections (substantive changes) into an existing Recommendation</label>
</div>
<div class="radio-item">
<input type="radio" id="rec-features" name="rec" value="features">
<label for="rec-features">Incorporating proposed additions (new features) into an existing Recommendation</label>
</div>
</fieldset>
<p>You <em class="rfc2119">may</em> also follow <a href="?profile=CR&cr=rec-update">Candidate Recommendation</a> for substantive corrections</p>
<p>We allow some <strong>in place modifications</strong> of Recommendations, including markup changes. See <a href="https://www.w3.org/guide/standards-track/republishing">In-place modification of W3C Technical Reports</a>.</p>
</div>
<div class="field">
<fieldset id="fp-note-options" data-profile="FPWG-NOTE|FPIG-NOTE">
<div class="radio-item">
<input type="radio" id="notehistory-first" name="notehistory" value="first" checked="checked">
<label for="notehistory-first">Chartered to be a group Note, never before published, group not closing</label>
</div>
<div class="radio-item">
<input type="radio" id="notehistory-none" name="notehistory" value="none">
<label for="notehistory-none">Chartered to be a group Note and previously published as a Working Draft, group not closing</label>
</div>
<div class="radio-item">
<input type="radio" id="notehistory-notchartered" name="notehistory" value="notchartered">
<label for="notehistory-notchartered">Not chartered to be a group Note, group not closing</label>
</div>
<div class="radio-item">
<input type="radio" id="notehistory-closure" name="notehistory" value="closure">
<label for="notehistory-closure">Publication as a group Note since group closing</label>
</div>
</fieldset>
</div>
<p><em>Not sure what's your next step? Try our <a href="nextstep">step finder</a>
and look at <a href="https://w3c.github.io/spec-releases/milestones/">milestones calculator</a>.</em></p>
</form>
</div>
<h2 id="sotd">About This Document</h2>
<p>This resource describes the internal W3C Technical Report
publication processes. A <a href="details">companion document</a> provides
more information about roles involved in these processes and
interactions with the W3C Communications Team.</p>
<div data-profile="WD|FPWD|CR|PR|PR-OBSL|PR-RSCND|WG-NOTE|DISC|IG-NOTE|FPWG-NOTE|FPIG-NOTE|REC|OBSL|RSCND">
<h2 id="steps">Steps for
<span data-profile="FPWD|CR|PR|PR-OBSL|PR-RSCND|FPWG-NOTE|FPIG-NOTE|REC|OBSL|RSCND" data-rec="new" data-cr="new">transition to</span>
<span data-profile="CR|REC" data-cr="snapshot" data-rec="substantive|features">an update request for a</span>
<span data-profile="WD|WG-NOTE|CR|REC|DISC" data-cr="draft" data-rec="editorial|candidate-corrections|candidate-additions|proposed-corrections|proposed-additions">publication of a</span>
<span data-profile="IG-NOTE">publication of an</span>
<span class="label-name">LABEL</span>
<span data-profile="CR" data-cr="snapshot">Snapshot</span>
<span data-profile="CR" data-cr="rec-update">(intended to update a Recommendation)</span>
<span data-profile="CR" data-cr="draft">Draft</span>
<span data-profile="REC" data-rec="candidate-corrections">(with candidate corrections)</span>
<span data-profile="REC" data-rec="candidate-additions">(with candidate additions)</span>
<span data-profile="REC" data-rec="proposed-corrections">(with proposed corrections)</span>
<span data-profile="REC" data-rec="proposed-additions">(with proposed additions)</span>
<span data-profile="REC" data-rec="editorial">(with editorial changes)</span>
<span data-profile="REC" data-rec="substantive">(incorporating proposed corrections)</span>
<span data-profile="REC" data-rec="features">(incorporating proposed additions)</span>
</h2>
<p>
<span data-profile="FPWD|CR|PR|REC|PR-OBSL|PR-RSCND|OBSL|RSCND" data-cr="new|snapshot|snapshot" data-rec="new|candidate-corrections|candidate-additions|proposed-corrections|proposed-additions|substantive|features">
Once the Process Document <a id="reqs-adv">requirements for the transition to
<span class="label-name">LABEL</span></a> have been satisfied
(see
<span class="procdocsection" data-profile="FPWD"><a href="https://www.w3.org/policies/process/20231103/#first-wd">section 6.3.5</a></span>
<span class="procdocsection" data-profile="CR" data-cr="new"><a href="https://www.w3.org/policies/process/20231103/#transition-cr">section 6.3.7</a></span>
<span class="procdocsection" data-profile="CR" data-cr="snapshot"><a href="https://www.w3.org/policies/process/20231103/#publishing-crrs">section 6.3.8.1</a></span>
<span class="procdocsection" data-profile="PR"><a href="https://www.w3.org/policies/process/20231103/#transition-pr">section 6.3.9</a></span>
<span class="procdocsection" data-profile="REC" data-rec="substantive|features"><a href="https://www.w3.org/policies/process/20231103/#change-review">section
6.3.11.5</a> and <a href="https://www.w3.org/policies/process/20231103/#update-requests">section 6.3.4</a></span>
<span class="procdocsection" data-profile="REC" data-rec="candidate-corrections"><a href="https://www.w3.org/policies/process/20231103/#revised-rec-substantive">section 6.3.11.3</a></span>
<span class="procdocsection" data-profile="REC" data-rec="candidate-additions"><a href="https://www.w3.org/policies/process/20231103/#revised-rec-features">section 6.3.11.4</a></span>
<span class="procdocsection" data-profile="REC" data-rec="new"><a href="https://www.w3.org/policies/process/20231103/#transition-rec">section 6.3.10</a>
or <a href="https://www.w3.org/policies/process/20231103/#deactivation">section 6.3.12.4</a> for restoring a
<em>Recommendation</em></span>
<span class="procdocsection" data-profile="PR-OBSL|PR-RSCND"><a href="https://www.w3.org/policies/process/20231103/#deactivation">section 6.3.12.4</a></span>
<span class="procdocsection" data-profile="OBSL|RSCND"><a href="https://www.w3.org/policies/process/20231103/#rec-rescind">section 6.3.12.4</a></span>),
W3C follows the steps described below to complete the transition.</span>
<span data-profile="WD">
Once the Group determined that the requirements of <span class="procdocsection"><a href="https://www.w3.org/policies/process/20231103/#revising-wd">section 6.3.6</a></span> apply, the W3C follows
the steps described below to update a
<span class="status-name">STATUS</span>.
</span>
<span data-profile="REC" data-rec="editorial">
Once the Group, or the <a href="details#MaintainerContact">Maintainer Contact</a>, determined that the requirements of <span class="procdocsection"><a href="https://www.w3.org/policies/process/20231103/#revised-rec-editorial">section 6.3.11.2</a></span> apply, the W3C follows
the steps described below to update a
<span class="status-name">STATUS</span>.
</span>
<span data-profile="CR" data-cr="draft">
Once the Group determined that the requirements of <span class="procdocsection"><a href="https://www.w3.org/policies/process/20231103/#publishing-crud">section 6.3.8.2</a></span> have been
satisfied, the Working Group follows the steps described below to publish a
<span class="status-name">STATUS</span>.
</span>
<span data-profile="FPIG-NOTE|FPWG-NOTE">
W3C follows the steps described below for transition to a
First Public
<span class="status-name">STATUS</span>.
</span>
These steps are
grouped by theme. They are not strictly ordered; in practice, some
steps are completed in parallel. For instance, groups often manage
the transition request/meeting steps
in parallel with the publication request steps.
</p>
<p class="internetmediatype" data-profile="FPWD|CR|PR|REC" data-rec="new|substantive|features" data-cr="new|snapshot">
<strong>Note:</strong> If your specification involves (or updates) an Internet
Media Type, before the transition to
<span data-profile="FPWD">First Public</span>
<span class="status-name">STATUS</span>, see also <cite><a href=""https://www.w3.org/guide/editor/mediatypes">Register
an Internet Media Type for a W3C Specification</a></cite>
<span class="mediatypespecifics" data-profile="FPWD">to review the entire Internet Media Type
registration process.</span>
<span class="mediatypespecifics" data-profile="WD">for information about
what you should do several months <strong>before</strong> advancing
to Candidate Recommendation.</span>
<span class="mediatypespecifics" data-profile="CR" data-cr="new|snapshot">for information
about
alerting the W3C liaisons to the
IETF so that they may request formal review and approval by the
IESG.</span>
<span class="mediatypespecifics" data-profile="PR|REC">for information about
how the W3C liaisons to the IETF track the registration process.</span>
</p>
<p class="xpointerregistry" data-profile="CR" data-cr="new|snapshot">
<strong>Note:</strong> If your specification defines (or updates) an XPointer
Scheme, before the transition to <span class="status-name">STATUS</span>, please register the scheme in the <a href="https://www.w3.org/2005/04/xpointer-schemes/">W3C XPointer Scheme
Registry</a>.
</p>
<dl>
<dt data-profile="CR" data-cr="new|snapshot">Negotiation of Review Schedule</dt>
<dd class="negotiatereview" data-profile="CR" data-cr="new|snapshot">
<ul>
<li>
The Chair negotiates the <a href="https://www.w3.org/policies/process/20231103/#wide-review">wide review</a>
schedule with the Chairs of groups with dependencies (on [email protected]) <strong>before</strong> going to
<span class="status-name">STATUS</span>.
<span data-profile="CR" data-cr="new">The Group <span class="rfc2119">MUST</span> show that the
specification has received
wide review in order to move to Candidate Recommendation.</span>
<span data-profile="CR" data-cr="new">The Group <span class="rfc2119">MUST</span> show that
all horizontal <code>*-needs-resolution</code> issues have been closed by the relevant
horizontal group in the <a href="https://www.w3.org/PM/horizontal/">horizontal group's tracker</a>
in order to publish the <span class="status-name">STATUS</span>.</span>
<span data-profile="CR" data-cr="snapshot">The Group <span class="rfc2119">MUST</span> show that any
horizontal <code>*-needs-resolution</code> issues have been acknowledged in order to publish
the <span class="status-name">STATUS</span>.</span>
<span data-profile="CR" data-cr="snapshot">The Group <span class="rfc2119">MUST</span> show that the changes
have received wide review in order to publish the <span class="status-name">STATUS</span>.</span>
See the <a href="../documentreview/">considerations, guidelines and best practices</a>
that groups should follow to get early and wide review of a document.
</li>
</ul>
</dd>
<dt data-profile="FPWD|CR|PR|PR-OBSL|PR-RSCND|FPWG-NOTE|FPIG-NOTE|REC|OBSL|RSCND" data-rec="new" data-cr="new" data-notehistory="notchartered|first">Transition request</dt>
<dt data-profile="CR|REC" data-cr="snapshot" data-rec="substantive|features">Update request</dt>
<dd data-profile="FPWD|CR|PR|PR-OBSL|PR-RSCND|FPWG-NOTE|FPIG-NOTE|REC|OBSL|RSCND" data-cr="new" data-rec="new" data-notehistory="notchartered|first">
<ul>
<li id="obs-webreqmail" data-profile="PR-OBSL|PR-RSCND" data-notehistory="notchartered|first">If an individual
made a request to the relevant Working Group, or the TAG (using <a href="https://github.com/w3ctag/obsoletion/issues">w3ctag/obsoletion</a>) if such a group does not exist,
to <span data-profile="PR-OBSL">obsolete or to supersede</span><span data-profile="PR-RSCND">rescind</span>
a Recommendation, <strong>and</strong> the request was not answered within 90 days, the individual should
<li id="transreqmail" class="transitionreq" data-profile="FPWD|FPWG-NOTE|FPIG-NOTE|CR|PR|PR-OBSL|PR-RSCND|REC|OBSL|RSCND" data-rec="new" data-cr="new|snapshot" data-notehistory="notchartered|first">
<span class="transwhen" data-profile="CR|PR|PR-OBSL|PR-RSCND|REC|OBSL|RSCND" data-cr="new|snapshot">At least one week prior to an expected
decision from or <a href="#team-mtg">meeting with the Team</a>, the</span>
<span class="transwhen" data-profile="FPWD|FPWG-NOTE|FPIG-NOTE" data-notehistory="notchartered|first">The <a href="details#DocContact">Document Contact</a>
<span class="transwho" data-profile="FPWD|FPWG-NOTE|CR|PR|PR-OBSL|PR-RSCND" data-cr="new|snapshot" data-notehistory="notchartered|first">
creates a <a href="#transreq">transition request</a> in <a href="https://github.com/w3c/transitions/issues">w3c/transitions</a>.
<span data-profile="CR" data-cr="snapshot" data-echidna="true">For the purpose of the automatic publishing
system, it's <strong>important</strong> that the title of the issue ends with the shortname of your
specification, thus you will need one single issue for each specification.</span>
<span data-profile="FPWD|FPWG-NOTE" data-notehistory="notchartered|first"><strong>Note:</strong>
For the TAG, no First Public Working Draft transition request is required; the request is assumed to be
approved by the Team.
</span>
</span>
<span class="transwho" data-profile="REC|OBSL|RSCND">
sends a <a href="#transreq">transition request</a> to
[email protected]. An issue is also created in <a href="https://github.com/w3c/transitions/issues">w3c/transitions</a> (for tracking purposes).
</span>
<span>A <a href="https://lists.w3.org/Archives/Public/public-transition-announce/">public archive of
transition requests</a> is available (since October 2019).</span>
</span></li>
<li class="transitionmtg" data-profile="FPWD|CR|PR|PR-OBSL|PR-RSCND|REC|OBSL|RSCND" data-cr="new|snapshot">
Following an initial review by the Team, the <a href="details#DocContact">Document Contact</a>
<span class="rfc2119">MAY</span> be asked to organize a <a href="#dir-mtg">transition meeting
with the Team</a> to discuss the request.
</li>
<li class="transitionreq-approval" data-profile="FPWD|CR|PR|PR-OBSL|PR-RSCND|FPWG-NOTE|FPIG-NOTE|REC|OBSL|RSCND" data-cr="new|snapshot" data-notehistory="notchartered|first">
<span class="transitionreq-approvalwho" data-profile="FPWD|FPWG-NOTE|FPIG-NOTE" data-notehistory="notchartered|first">
The <span data-profile="FPWD|FPWG-NOTE">Project Management</span>
<span data-profile="FPIG-NOTE">Industry or Strategy</span> Lead approve the transition request.
The Lead <span class="rfc2119">MAY</span> ask the
CEO (or someone assigned by the CEO) to take responsibility for approving the transition
request.
</span>
<span class="transitionreq-approvalwho" data-profile="CR|PR|REC|OBSL|RSCND|PR-OBSL|PR-RSCND" data-cr="new|snapshot">
The Team verifies the transition request.
</span>
<span data-profile="CR|PR">Approvals are expected to appear as an issue comment <a href="https://github.com/w3c/echidna/blob/master/lib/transition-checker.js#L31">"Transition
approved."</a> in <a href="https://github.com/w3c/transitions/issues">w3c/transitions</a>
<span data-profile="CR" data-cr="snapshot" data-echidna="true">and
the label '<a href="https://github.com/w3c/echidna/blob/master/lib/transition-checker.js#L40">Awaiting
Publication</a>' will need to be set</span>.</span>
<span class="transitionreq-approvalwho-when" data-profile="CR|PR|REC|OBSL|RSCND|PR-OBSL|PR-RSCND" data-cr="new|snapshot">
In most cases the decision to approve the transition is made on Fridays.
</span>
</li>
</ul>
</dd>
<dd data-profile="CR|REC" data-cr="snapshot" data-rec="substantive|features">
<ul>
<li>
The <a href="details#DocContact">Document Contact</a> issue an <a href="#updaterequest">update request</a>
in <a href="https://github.com/w3c/transitions/issues">w3c/transitions</a>, if there are substantive changes
other than to remove features explicitly identified as at risk.
</li>
<li>if the only substantive changes are to remove features explicitly identified as at risk, there is no need
for Team's approval.
</li><li>
If the <a href="#transreq">update request</a> satisfies the criteria for <a href="https://www.w3.org/policies/process/20231103/#streamlined-update">Streamlined Publication Approval</a>,
the Team automatically grants the request without formal review.
<span data-profile="CR|PR">Automatic approvals are expected to appear as an issue comment <a href="https://github.com/w3c/echidna/blob/master/lib/transition-checker.js#L31">"Transition approved
automatically."</a> in <a href="https://github.com/w3c/transitions/issues">w3c/transitions</a>
<span data-profile="CR" data-cr="snapshot" data-echidna="true">and
the label '<a href="https://github.com/w3c/echidna/blob/master/lib/transition-checker.js#L40">Awaiting
Publication</a>' will be set</span>.</span>
</li>
<li>
If the <a href="#transreq">update request</a> does not satisfy the criteria for <a href="https://www.w3.org/policies/process/20231103/#streamlined-update">Streamlined Publication Approval</a>,
the Team may approve the request after review.
<span data-profile="CR|PR">Approvals are expected to appear as an issue comment <a href="https://github.com/w3c/echidna/blob/master/lib/transition-checker.js#L31">"Transition
approved."</a> in <a href="https://github.com/w3c/transitions/issues">w3c/transitions</a>
<span data-profile="CR" data-cr="snapshot" data-echidna="true">and
the label '<a href="https://github.com/w3c/echidna/blob/master/lib/transition-checker.js#L40">Awaiting
Publication</a>' will need to be set</span>.</span>
<span class="transitionreq-approvalwho-when" data-profile="CR|PR|REC|OBSL|RSCND|PR-OBSL|PR-RSCND" data-cr="new|snapshot">
In most cases the decision to approve the transition is made on Fridays.
</span></li>
</ul>
</dd>
<dt data-profile="FPWD|CR|PR|FPIG-NOTE|FPWG-NOTE|WD|CR|WG-NOTE|DISC|IG-NOTE|REC|OBSL|RSCND">Publication Planning</dt>
<dd class="docpreparation" data-profile="WD|CR|WG-NOTE|IG-NOTE|REC" data-cr="draft|snapshot" data-rec="editorial|candidate-corrections|candidate-additions" data-echidna="true">
<ul>
<li class="mailinglist-prep" data-profile="REC">
The <a href="details#DocContact">Document Contact</a> ensures that
there is a public archived github repository
available for comments.
</li>
<li>The <a href="details#DocContact">Document Contact</a> prepares the
document in accordance with <a href="https://www.w3.org/pubrules/">pubrules</a> (use the "Echidna-ready"
check).
</li>
<li data-profile="WG-NOTE|IG-NOTE">
If the publication is the result
of stopping work on a specification, the <a href="details#DocContact">Document Contact</a>
alerts the
<a href="details#Webmaster">Webmaster</a> at [email protected],
optionally cc'ing [email protected] (which has a Member-visible archive).
</li>
</ul>
</dd>
<dd class="docpreparation" data-profile="WD|WG-NOTE|DISC|IG-NOTE|FPWD|CR|PR|REC|OBSL|RSCND|FPWG-NOTE|FPIG-NOTE" data-echidna="false">
<ul>
<li class="mailinglist-prep" data-profile="FPWD|FPIG-NOTE|FPWG-NOTE">
The <a href="details#DocContact">Document Contact</a> ensures that
there is a public archived place (github or mailing list)
available for comments; (for mailing list, the Team Contact uses the <a href="https://www.w3.org/Systems/Mail/ListRequest">mailing list request
form</a>).</li>
<li id="edrec-webreqmail" data-profile="REC" data-rec="editorial">If an individual made a request to the
relevant Working Group, or the <a href="details#MaintainerContact">Maintainer Contact</a>, to update a
Recommendation, <strong>and</strong> the request was not answered within 90 days, the individual should
create a <a href="#transreq">transition request</a> in <a href="https://github.com/w3c/transitions/issues">w3c/transitions</a> to draw attention.</li>
<li class="mailinglist-prep" data-profile="REC">
The <a href="details#DocContact">Document Contact</a> ensures that
there is a public archived github repository
available for comments.
</li>
<li>The <a href="details#DocContact">Document Contact</a> prepares the
document in accordance with <a href="https://www.w3.org/pubrules/">pubrules</a> and develops a proposed
<a href="#schedule-pubreq">publication schedule</a>, taking into
account possible <a href="#moratoria">publishing moratoria</a>. The
<a href="#title-page-date">title page date</a>
is chosen based on the anticipated publication schedule.
</li>
<li>Before sending the publication request, the Team Contact <span class="rfc2119">SHOULD</span> install the
document in its final
location. The <a href="details#DocContact">Document
Contact</a> <span class="rfc2119">MAY</span> request publication of a
document that is not yet installed at its final location, but in this
case <span class="rfc2119">MUST</span> provide installation
instructions to the Webmaster.
If a document to be published consists of more than one HTML
file (i.e., there are style sheets, schemas, etc.), all
materials <span class="rfc2119">MUST</span>
be made available to the Webmaster from a single
directory (which may include subdirectories).
</li>
<li id="pubreqmail">
The <a href="details#DocContact">Document Contact</a> sends a <a href="#pubreq">publication request</a> to the
<a href="details#Webmaster">Webmaster</a> at [email protected],
optionally cc'ing [email protected] (which has a Member-visible archive).
See below for details about
<a href="#title-page-date">scheduling a publication</a>, and specifically requirements about advance notice
to the Webmaster.
<span data-profile="FPWG-NOTE|WG-NOTE|DISC|IG-NOTE" data-notehistory="none|closure">
If the publication is the result
of stopping work on a specification, the <a href="details#DocContact">Document Contact</a>
alerts the
<a href="details#Webmaster">Webmaster</a> as well.
</span>
</li>
</ul>
</dd>
<dt class="listprep" data-profile="PR|PR-OBSL|PR-RSCND">Form and Announcement Preparation</dt>
<dt class="listprep" data-profile="FPWD|FPIG-NOTE|FPWG-NOTE|WD|CR|OBSL|RSCND|REC" data-returning="true" data-cr="new|snapshot" data-notehistory="first" data-rec="new|proposed-corrections|proposed-additions|substantive|features">Announcement Preparation</dt>
<dd data-profile="FPWD|FPIG-NOTE|FPWG-NOTE|WD|CR|REC|OBSL|RSCND|PR|PR-OBSL|PR-RSCND" data-cr="new|snapshot" data-notehistory="first" data-rec="new|proposed-corrections|proposed-additions|substantive|features">
<ul>
<li class="transannc-draft" data-profile="WD" data-returning="true">
The
<a href="details#DocContact">Document Contact</a> sends a draft <a href="#trans-annc">transition announcement</a>
to the Communications Team at [email protected], which explains why the document was returned for further
work.
</li>
<li class="reviewform-prep" data-profile="PR|PR-OBSL|PR-RSCND|REC" data-rec="proposed-corrections|proposed-additions">
The Team Contact builds a
<span class="status-name">STATUS</span>
<a href="https://www.w3.org/2002/09/wbs/33280/factory">review
form</a> that the Project Manager reviews for correctness. The Team Contact ensures that there is a
mailing list with
a Team-only archive available for AC Representative comments; this list
is cited from the review form.
<span class="reviewform-prep2" data-profile="PR">
<strong>Note:</strong>
At the current time, WBS review forms are generated from
installed documents, but before the Webmaster completes
publication.</span>
</li>
<li class="transannc-draft" data-profile="CR|PR|REC|PR-OBSL|PR-RSCND|OBSL|RSCND" data-cr="new|snapshot">The
<a href="details#DocContact">Document Contact</a> sends a draft <a href="#trans-annc">transition announcement</a>
to the Communications Team at [email protected].
<span data-profile="CR" data-cr="new">If the publication is the result
of <a href="https://www.w3.org/policies/process/20231103/#revising-wd">returning a document to a Working
Group for further work</a>, the announcement
explains why the document was returned for further work.</span>
</li>
<li data-profile="CR" data-cr="snapshot" data-echidna="true">The Communications Team
approves the draft using an issue comment
<a href="https://github.com/w3c/echidna/blob/master/lib/transition-checker.js#L32">"Draft transition
approved"</a>
in <a href="https://github.com/w3c/transitions/issues">w3c/transitions</a>
</li>
</ul>
</dd>
<dt class="transition-announcement" data-profile="FPWD|FPIG-NOTE|FPWG-NOTE|CR|PR|REC|OBSL|RSCND" data-cr="new" data-notehistory="first" data-rec="new|proposed-corrections|proposed-additions|substantive|features">Publication and Transition Announcement</dt>
<dt class="transition-announcement" data-profile="CR" data-cr="snapshot">Publication and Update Announcement</dt>
<dt class="transition-announcement" data-profile="WD|WG-NOTE|DISC|IG-NOTE|FPIG-NOTE|FPWG-NOTE|CR|REC" data-cr="draft" data-notehistory="none|notchartered|closure" data-rec="editorial|candidate-corrections|candidate-additions">Publication</dt>
<dt class="transition-announcement" data-profile="PR-OBSL|PR-RSCND">Transition Announcement</dt>
<dd>
<ul>
<li class="publication-announcement" data-profile="WD|FPWD|CR|WG-NOTE|DISC|IG-NOTE|FPWG-NOTE|FPIG-NOTE|REC" data-rec="editorial|candidate-corrections|candidate-additions" data-echidna="false">The Webmaster completes <a href="#publication">publication</a> and notifies the Chair
and Team Contact of publication, cc'ing [email protected]<span data-profile="FPWD|CR|WG-NOTE|DISC|IG-NOTE|FPWG-NOTE|FPIG-NOTE" data-cr="new|snapshot">
and [email protected]</span>.
</li>
<li class="publication-announcement" data-profile="WD|CR|REC|WG-NOTE|IG-NOTE" data-cr="draft|snapshot" data-rec="editorial|candidate-corrections|candidate-additions" data-echidna="true">The <a href="details#DocContact">Document
Contact</a>
publishes the document using the <a href="https://github.com/w3c/echidna/wiki">W3C automatic system</a>.
</li>
<li class="publication-announcement" data-profile="CR|PR|REC|OBSL|RSCND" data-cr="new|snapshot" data-echidna="false" data-rec="new|proposed-corrections|proposed-additions|substantive|features">
After coordination with the Communications Team on the transition
announcement timing (especially those accompanied
by press releases; see more about
<a href="details#commteam">interactions with the
Communications Team</a>), the Webmaster completes <a href="#publication">publication</a> and notifies the
person who
sent the request, cc'ing [email protected] and [email protected].
Publication <span class="rfc2119">SHOULD</span> precede the transition announcement by
only a small amount of time.
</li>
<li class="trans-announcement" data-profile="FPWD">
The W3C Communications Team makes an
announcement on the <a href="https://www.w3.org/">W3C home page</a>.
</li>
<li class="trans-announcement" data-profile="WD" data-returning="true">
The W3C Communications Team sends the <a href="#trans-annc">transition announcement</a> to
</li>
<li class="trans-announcement" data-profile="WD" data-returning="false">
Since September 2015, the Communications Team no longer posts homepage news for regular WDs, unless
explicitely requested.
</li>
<li class="trans-announcement" data-profile="CR|PR|PR-OBSL|PR-RSCND|REC|OBSL|RSCND" data-cr="new|snapshot" data-rec="new|proposed-corrections|proposed-additions|substantive|features">
The W3C Communications Team sends the
<a href="#trans-annc">transition announcement</a>
<span data-profile="CR|PR|PR-OBSL|PR-RSCND|REC|OBSL|RSCND" data-cr="new|snapshot">and
[email protected]</span>
<span data-profile="CR|PR|REC" data-cr="new|snapshot">and on the <a href="https://www.w3.org/">W3C home page</a></span>.
<span data-profile="PR">The Advisory Committee review is started.</span>
<span data-profile="REC">The Call for Exclusions and the Advisory Committee review are started.</span>
</li>
<li class="trans-announcement" data-profile="CR" data-cr="snapshot">
The W3C Communications Team sends the
<a href="#trans-annc">update announcement</a>
to [email protected] and on the <a href="https://www.w3.org/">W3C home page</a>.
</li>
<li class="trans-announcement" data-profile="CR|PR|PR-OBSL|PR-RSCND" data-cr="new|snapshot" data-pr="new" data-echidna="false">The Chair or Team Contact(s) <span class="rfc2119">SHOULD</span> forward
the announcement to the Working
Group's public mailing list <strong>taking caution</strong> not to
send any Member-confidential information to a public list.</li>
<li class="trans-announcement" data-profile="CR" data-cr="snapshot" data-echidna="true">The
<a href="details#DocContact">Document Contact</a> <span class="rfc2119">SHOULD</span> forward the announcement to the Working
Group's public mailing list.
</li>
<li class="trans-announcement" data-profile="REC" data-rec="new|substantive|features">The Team
Contact <span class="rfc2119">SHOULD</span> forward the announcement to the appropriate public forum
<strong>taking caution</strong> not to
send any Member-confidential information to a public list.</li>
</ul>
</dd>
</dl>
<p data-profile="WG-NOTE|IG-NOTE">
<strong>Note:</strong> Instructions for publication of
an Ordinary
<span class="status-name">STATUS</span>
are included for convenience even though
this is not a <a href="https://www.w3.org/policies/process/20231103/#rec-track">Recommendation
Track transition</a> as defined in the W3C Process.
</p>
<p data-profile="PR-OBSL|PR-RSCND">
<strong>Note:</strong>
<span class="status-name">STATUS</span>
is not a <a href="https://www.w3.org/policies/process/20231103/#maturity-stages">maturity stage</a> defined in the <a href="https://www.w3.org/policies/process/20231103/">W3C Process</a> but is described as a proposal before the next
step.
</p>
<hr>
<p> </p>
<div id="adv-reqs">
<div data-profile="FPWD|CR|PR|REC" data-cr="new" data-rec="new">
<h2 id="transition-reqs">Transition Requirements for <span class="status-name">STATUS</span></h2>
<p data-profile="REC" data-rec="new">The decision to advance a document to <a data-link-type="dfn" href="https://www.w3.org/policies/process/20231103/#RecsW3C" id="ref-for-RecsW3C">Recommendation</a> is a
<a data-link-type="dfn" href="https://www.w3.org/policies/process/20231103/#def-w3c-decision" id="ref-for-def-w3c-decision">W3C Decision</a>.
</p>
<p>The <span data-profile="FPWD|CR|PR" data-pr="new" data-cr="new|draft|snapshot">Working
Group</span><span data-profile="CR|PR|REC" data-cr="rec-amended" data-pr="rec-amended">W3C</span>:</p>
<ul>
<li> <em class="rfc2119">must</em> record the <span data-profile="FPWD|CR|PR|REC" data-pr="new" data-cr="new|draft|snapshot">group’s</span><span data-profile="CR|PR" data-cr="rec-amended" data-pr="rec-amended">individual(s)</span> decision to request advancement.
<p class="note">Provide a link to meeting minutes, github issues, or email announcing the decision.</p>
<p data-profile="REC" class="note">For a Recommendation, you may reuse the group's decision to move to
Proposed Recommendation.</p>
</li>
<li> <em class="rfc2119">must </em> obtain <a data-link-type="dfn" href="https://www.w3.org/policies/process/20231103/#team" id="ref-for-def-Team">Team</a>
verification.
<p class="note">Submit a <a href="#transreq">transition request</a>.</p>
</li>
<li data-profile="CR" data-cr="new|draft|snapshot"> <em class="rfc2119 ">must</em> publicly
document all new features
(<a href="https://www.w3.org/policies/process/20231103/#class-4">class 4 changes</a>) to the
technical report
since the previous publication.
<p class="note">Include a link to a change log where new features are highlighted, highlight them in the
Status of the Document. </p>
</li>
<li data-profile="CR" data-cr="rec-amended"> <em class="rfc2119 ">must not</em> contain new features
(<a href="https://www.w3.org/policies/process/20231103/#class-4">class 4 changes</a>) to the
technical report
since the Recommendation.
</li>
<li data-profile="CR"> <em class="rfc2119">must</em> publicly document if other substantive changes
(<a href="https://www.w3.org/policies/process/20231103/#class-3">class 3 changes</a>) have been made,
and <em class="rfc2119">should</em> document the details of such changes.
<div class="note">
<ul>
<li>For example, include a link to a change log where important changes are highlighted. </li>
<li>If this specification is a revision of a previous Recommendation, does the document clearly state
the
relation of this version to the previous one? For instance, does it obsolete or supersede a previous
Recommendation? Where is this stated (e.g., the status section)? Does the specification explain
whether
authors should create content according to the previous or current version? Does the specification
explain
whether processors should continue to process content according to the previous Recommendation?</li>
<li>If there will be two Recommendations of different major revision numbers, does the newer
specification explain the relationship?</li>
</ul></div>
</li>
<li data-profile="CR|PR|REC"> <em class="rfc2119">should</em> publicly document if <a data-link-type="dfn" href="https://www.w3.org/policies/process/20231103/#class-2" id="ref-for-editorial-change">editorial
changes</a> have been made,
and <em class="rfc2119">may</em> document the details of such changes.
</li>
<li data-profile="CR|PR|REC" data-cr="new|draft|snapshot"> <em class="rfc2119">must</em> <a data-link-type="dfn" href="https://www.w3.org/policies/process/20231103/#formally-addressed" id="ref-for-formally-addressed">formally address</a> all issues
raised about the document since the previous <a href="https://www.w3.org/policies/process/20231103/#maturity-levels">maturity level</a>.
<div class="note">
<ul>
<li>Include a link to an issues list, such as GitHub issues, that indicates that the group has been
responsive to reviewers who have raised issues since the previous transition. The Team's
expectations are that, as a document advances, there will be an increasingly precise record of how it
has formally addressed each issue.</li>
<li>For changes in the issues list since the previous transition:
<ul>
<li>Highlight issues where the Group has declined to make a change, with rationale. See also <a href="https://lists.w3.org/Archives/Member/chairs/2000JanMar/0109.html">Clarification: tables
summarizing review</a>, Tim Berners-Lee (Tue, Feb 15 2000).
</li><li>Highlight issues where the Group has not satisfied a reviewer and has either not yet responded
to the reviewer, or the reviewer has not yet acknowledged the Group's decision.</li>
<li>Show, without highlighting:
<ul>
<li>Issues where the Working Group has accepted a proposed change.</li>
<li>Issues where the Working Group has clarified the specification to the satisfaction of the
reviewer.</li>
</ul>
</li>
</ul>
</li>
</ul>
</div>
</li>
<li data-profile="CR" data-cr="rec-amended"> <em class="rfc2119">should</em> <a data-link-type="dfn" href="https://www.w3.org/policies/process/20231103/#formally-addressed" id="ref-for-formally-addressed">formally
address</a> all errata
raised about the document since the Recommendation.
<p class="note">Include a link to an issues list, such as GitHub issues, that indicates that errata have been
responded.</p>
</li>
<li> <em class="rfc2119">must</em> provide public documentation of any <a data-link-type="dfn" href="https://www.w3.org/policies/process/20231103/#FormalObjection" id="ref-for-FormalObjection">Formal Objections</a>.
<p class="note">
Provide link(s) to the objection, attempts to satisfy the reviewer, and a public record of the decision.
</p>
</li>
<li data-profile="CR|PR|REC" data-cr="new"> <em class="rfc2119">should</em> report which, if any, of the <span data-profile="CR|PR|REC" data-pr="new" data-cr="new|draft|snapshot">Working Group's</span><span data-profile="CR|PR" data-cr="rec-amended" data-pr="rec-amended">individual(s)</span> requirements
for this document have changed since the previous step.
</li>
<li data-profile="CR|PR|REC" data-cr="new|draft|snapshot"> <em class="rfc2119">should</em> report any changes in
dependencies with other groups.
<div class="note" data-profile="PR|REC">
<ul>
<li>In general, documents do not advance to Proposed Recommendation with normative references to other
specifications that are considered unstable. See also <a href="https://www.w3.org/guide/process/tilt/normative-references">Normative References Guidelines</a>.</li>
<li>Documents must not include normative references to a Rescinded/Obsolete/Superseded Recommendation. </li>
</ul>
</div>
</li>
<li data-profile="FPWD|CR" data-pr="new" data-cr="new|draft|snapshot"> <em class="rfc2119">should</em>
provide information about implementations known to the <span data-profile="FPWD|CR" data-pr="new" data-cr="new|draft|snapshot">Working Group</span><span data-profile="CR" data-cr="rec-amended" data-pr="rec-amended">individual(s)</span>.
</li>
<li data-profile="CR" data-cr="rec-amended"> <em class="rfc2119">must</em> provide information about
implementations known to the individual(s).
<p class="note" data-profile="PR">See <a href="https://www.w3.org/policies/process/20231103/#implementation-experience">implementation experience</a></p>
</li>
<li data-profile="PR|REC"> <em class="rfc2119">must</em> provide information about implementations known to the
<span data-profile="PR|REC" data-pr="new" data-rec="new">Working Group</span><span data-profile="PR|REC" data-rec="rec-amended" data-pr="rec-amended">individual(s)</span>.
<div class="note">
<ul>
<li data-profile="PR|REC" data-pr="rec-amended">Unless this information changed since the previous
transition, indicate "No change".</li>
<li data-profile="PR" data-pr="new">Include a link to a final implementation report, or, if there is
no such report, rationale why the Team should approve the request nonetheless.</li>
<li>If you use WPT results, provide a snapshot of those results, e.g <a href="https://www.w3.org/2021/04/wpt-fyi-snapshot.html?filter=webauthn">wpt.fyi
snapshot of webauthn</a> (save a copy of the resulting report)</li>
</ul>
</div>
</li>
</ul>
</div>
<div data-profile="WD">
<h2 id="revising-wd">Requirements for revising a <span class="status-name">STATUS</span></h2>
<p>A <a data-link-type="dfn" href="https://www.w3.org/policies/process/20231103/#GroupsWG" id="ref-for-GroupsWG⑤">Working Group</a> <em class="rfc2119">should</em> <a data-link-type="dfn" href="https://www.w3.org/policies/process/20231103/#publishing" id="ref-for-publishing">publish</a> a <a data-link-type="dfn" href="https://www.w3.org/policies/process/20231103/#RecsWD" id="ref-for-RecsWD">Working Draft</a> to the W3C Technical Reports page
when there have been significant changes
to the previous published document
that would benefit from review beyond the Working Group.</p>
<p>If 6 months elapse without significant changes to a specification,
a Working Group <em class="rfc2119">should</em> publish a revised <a data-link-type="dfn" href="https://www.w3.org/policies/process/20231103/#RecsWD" id="ref-for-RecsWD">Working Draft</a>,
whose status section <em class="rfc2119">should</em> indicate reasons for the lack of change.</p>
<p>To publish a revision of a Working draft, a Working Group:</p>
<ul>
<li> <em class="rfc2119">must</em> record the group’s decision to request publication. <a data-link-type="dfn" href="https://www.w3.org/policies/process/20231103/#def-Consensus" id="ref-for-def-Consensus">Consensus</a> is
not required,
as this is a procedural step,
<div class="note">
<p>Provide a link to meeting minutes, github issues, or email announcing the decision. The decision may be
applicable to one or more revisions.</p>
<p data-profile="WD" data-echidna="true">
This link should be given to the <a href="https://github.com/w3c/echidna/wiki">W3C automatic system</a>
using the <code>decision</code> parameter.
</p>
</div>
</li>
<li> <em class="rfc2119">must</em> provide public documentation
of <a data-link-type="dfn" href="https://www.w3.org/policies/process/20231103/#substantive-change" id="ref-for-substantive-change">substantive changes</a> to the technical report
since the previous <a data-link-type="dfn" href="https://www.w3.org/policies/process/20231103/#RecsWD" id="ref-for-RecsWD">Working Draft</a>,
</li>
<li> <em class="rfc2119">should</em> provide public documentation
of significant <a data-link-type="dfn" href="https://www.w3.org/policies/process/20231103/#class-2" id="ref-for-editorial-change">editorial changes</a> to the technical report
since the previous step,
</li>
<li> <em class="rfc2119">should</em> report which,
if any,
of the Working Group’s requirements for this document
have changed since the previous step,
</li>
<li> <em class="rfc2119">should</em> report any changes in dependencies with other groups,
</li>
</ul>
</div>
<div data-profile="CR|REC" data-cr="snapshot" data-rec="substantive|features">
<h2 id="update-reqs">Requirements for updating a <span class="status-name">STATUS</span></h2>
<p class="advisement" data-profile="REC" data-rec="features">WARNING: If your existing Recommendation was not
approved for <a href="https://www.w3.org/policies/process/20231103/#allow-new-features">accepting new features</a>,
you are not allowed to follow these steps. You MUST follow the <a href="?profile=FPWD">First Public Working
Draft</a> steps instead.</p>
<p data-profile="REC" data-rec="substantive|features">The decision to incorporate proposed amendments in a <a data-link-type="dfn" href="https://www.w3.org/policies/process/20231103/#RecsW3C" id="ref-for-RecsW3C">Recommendation</a> is a
<a data-link-type="dfn" href="https://www.w3.org/policies/process/20231103/#def-w3c-decision" id="ref-for-def-w3c-decision">W3C Decision</a>.
</p>
<p data-profile="CR">The Working Group:</p>
<p data-profile="REC">The W3C:</p>
<ul>
<li> <em class="rfc2119">must </em> obtain <a data-link-type="dfn" href="https://www.w3.org/policies/process/20231103/#team" id="ref-for-def-Team">Team</a>
verification,
or fulfill the criteria for <a href="https://www.w3.org/policies/process/20231103/#streamlined-update">Streamlined Publication Approval</a>.
<p class="note">Submit an update request.</p>
</li>
<li> <em class="rfc2119">must</em> record the group’s decision to request the update.
<p class="note">Provide a link to meeting minutes, github issues, or email announcing the decision.</p>
</li>
<li> <em class="rfc2119">must</em> show that the <span data-profile="CR">changes</span>
<span data-profile="REC">proposed amendments</span> have received <a data-link-type="dfn" href="https://www.w3.org/policies/process/20231103/#dfn-wide-review" id="ref-for-dfn-wide-review">wide
review</a>.
<div class="note">
<ul>
<li>Was the public requested to review the changes (such as announcement from a previous publication)?
</li>
<li>Which are the groups with dependencies, per the Group's charter, and did they review the document?
</li>
<li>Were the horizontal groups given proper opportunities to review subtantive changes? Are there any <a href="https://www.w3.org/PM/horizontal/"><code>*-needs-resolution</code>
issue</a> pending?</li>
<li>Was there early review from implementers? Are the changes already deployed in implementations?</li>
<li data-profile="CR" data-streamline="true">
Streamlined Publication Approval requires, for each of the W3C Horizontal Groups,
if the Horizontal Review Group has made available a set criteria under which their review is not
necessary,
the Working Group <span class="rfc2119">must</span> document that these criteria have been fulfilled.
Otherwise, the Working Group <span class="rfc2119">must</span> show that review from that group has been
solicited and received.
</li>
</ul>
<p data-profile="REC">
Proposed amendments can only be incorporated as-is, per <a href="https://www.w3.org/policies/process/20231103/#change-review">section 6.3.11.5</a>.
</p>
</div>
</li>
<li data-profile="CR|REC" data-streamline="true">
Streamlined Publication Approval requires the group to <a data-link-type="dfn" href="https://www.w3.org/policies/process/20231103/#formally-addressed" id="ref-for-formally-addressed">formally address</a>:
<ul>
<li data-md="">
<p>all issues raised against the document that resulted in changes since the previous publication</p>
</li>
<li>
<p>all issues raised against changes since the previous publication</p>
</li>
<li>
<p>all issues raised against the document that were closed since the previous publication with no change
to the document</p>
</li>
</ul>
<p>The response to each of these issues <em class="rfc2119">must</em> be to the satisfaction
of the person who raised it:
their proposal has been accepted,
or a compromise has been found,
or they accepted the Working Group’s rationale for rejecting it. This implies no pending <a href="https://www.w3.org/PM/horizontal/"><code>*-needs-resolution</code></a> issues,
and no pending <a href="https://www.w3.org/2020/06/DRAFT-PP2020.html#sec-PAG-conclude">PAG conclusions</a>.
</p>
</li>
<li> <em class="rfc2119">must</em> provide public documentation of any <a data-link-type="dfn" href="https://www.w3.org/policies/process/20231103/#FormalObjection" id="ref-for-FormalObjection">Formal
Objections</a>.
<div class="note">
<ul>
<li>Provide link(s) to the objection, attempts to satisfy the reviewer, and a public record of the
decision.</li>
<li data-profile="CR|REC" data-streamline="true">
Streamlined Publication Approval requires <strong>no formal objection</strong> have been registered.
</li>
</ul></div>
</li>
<li data-profile="CR|REC" data-rec="features"> <em class="rfc2119 ">must</em> publicly document of all new
features
(<a href="https://www.w3.org/policies/process/20231103/#class-4">class 4 changes</a>) to the technical
report
since the previous publication.
<p class="note">Include a link to a change log where new features are highlighted, highlight them in the
Status of the Document. </p>
</li>
<li> <em class="rfc2119">must</em> publicly document if other substantive changes
(<a href="https://www.w3.org/policies/process/20231103/#class-3">class 3 changes</a>) have been made,
and <em class="rfc2119">should</em> document the details of such changes.
<p class="note">For example, include a link to a change log where important changes are highlighted.</p>
<p data-profile="REC" data-rec="substantive|features">For Recommendations, other substantive changes
<em class="rfc2119">must not</em> happen, unless it was a proposed amendment.
</p>
</li>
<li> <em class="rfc2119">should</em> publicly document if <a data-link-type="dfn" href="https://www.w3.org/policies/process/20231103/#class-2" id="ref-for-editorial-change">editorial
changes</a> changes have been made,
and <em class="rfc2119">may</em> document the details of such changes.
</li>
<li> <em class="rfc2119">must</em> show that the revised specification
meets all <a data-link-type="dfn" href="https://www.w3.org/policies/process/20231103/#GroupsWG" id="ref-for-GroupsWG">Working Group</a> requirements,
or explain why the requirements have changed or been deferred,
<div class="note">
<ul>
<li>Where are the requirements defined (e.g,. a charter or requirements document)?</li>
<li>Are any requirements previously satisfied no longer satisfied? Are any requirements previously
unsatisfied now satisfied?</li>
<li data-profile="CR|REC" data-streamline="true">
Streamlined Publication Approval requires no changes to Working Group requirements.
</li>
</ul>
</div>
</li>
<li> <em class="rfc2119">should</em> report which, if any, of the <a data-link-type="dfn" href="https://www.w3.org/policies/process/20231103/#GroupsWG" id="ref-for-GroupsWG">Working Group</a>'s
requirements
for this document have changed since the previous step.
<div class="note">
<ul>
<li data-profile="CR|REC" data-streamline="true">
Streamlined Publication Approval requires no changes to Working Group requirements.
</li>
</ul>
</div>
</li>
<li> <em class="rfc2119">should</em> report any changes in dependencies with other groups.
</li>
<li> <em class="rfc2119">should</em> provide information about implementations known to the <a data-link-type="dfn" href="https://www.w3.org/policies/process/20231103/#GroupsWG" id="ref-for-GroupsWG">Working Group</a>.
</li>
</ul>
</div>
<div data-profile="CR" data-cr="new">
<!-- <h2 id='transition-cr'>Additions to Transitioning to <span class="status-name">STATUS</span></h2> -->
<ul>
<li> <em class="rfc2119">must</em> show that the specification
has met all <span data-profile="FPWD|CR|PR|REC" data-pr="new" data-cr="new|draft|snapshot">Working
Group</span><span data-profile="CR|PR" data-cr="rec-amended" data-pr="rec-amended">individual(s)</span>
requirements,
or explain why the requirements have changed or been deferred,
<div class="note">
<ul>
<li>Where are the requirements defined (e.g,. a charter or requirements document)?</li>
<li>Are any requirements previously satisfied no longer satisfied? Are any requirements previously
unsatisfied now satisfied?</li>
</ul>
</div>
</li>
<li> <em class="rfc2119">must</em> document changes to dependencies during the development of the specification,
<div class="note">
<ul>
<li>Does this specification have any normative references to other
specifications that are not yet stable?
The Team's expectations are that, as a document advances, there will be an increasingly need
for normative referenced materials to be scrutinized. See <a href="https://www.w3.org/guide/process/tilt/normative-references">Normative References Guidelines</a>.
</li>
<li>Does this specification have any normative references to a Rescinded/Obsolete/Superseded
Recommendation? Documents <span class="rfc2119">must not</span> include normative references to a
Rescinded/Obsolete/Superseded Recommendation.
</li>
<li class="groups-satisfied" data-profile="CR" data-cr="new|snapshot">Have other Groups
confirmed that dependencies
have been satisfied? For example, does the issues list show that
these groups are satisfied as a result of their review of the
document? Are there dependencies that have not been satisfied?</li>
<li class="new-impl-dependencies" data-profile="PR" hidden="hidden">Is there evidence that additional
dependencies
related to implementation have been satisfied?</li>
</ul>
</div>
</li>
<li> <em class="rfc2119">must</em> document
how <a data-link-type="dfn" href="https://www.w3.org/policies/process/20231103/#adequate-implementation" id="ref-for-adequate-implementation">adequate implementation experience</a> will be demonstrated,
<div class="note">
<p>This is also known as "CR exit criteria".</p>
<ul>
<li>Are there tests or test suites available that will allow the WG to demonstrate/evaluate that features
have been implemented (e.g., a matrix showing how different pieces or classes of software implement
different features)? Is the expectation to show two complete implementations (e.g., there are two
software instances, each of which conforms) or to show that each feature is implemented twice in some
piece of software?</li>
<li>What are the Group's plans for showing implementation of optional features? In general, the Team
expects mandatory features and optional features that affect interoperability to be handled similarly.
Optional features that are truly optional (i.e., that do not affect interoperability) may require less
implementability testing.</li>
<li>Does the WG have additional implementation experience that will help demonstrate interoperability
(e.g., has there been an interoperability day or workshop? Is one planned?)?</li>
</ul>
</div>
</li>
<li> <em class="rfc2119">may</em> identify features in the document as <dfn class="dfn-paneled" data-dfn-type="dfn" data-export="" id="at-risk">at risk</dfn>.
These features <em class="rfc2119">may</em> be removed
before advancement to <a data-link-type="dfn" href="https://www.w3.org/policies/process/20231103/#RecsPR" id="ref-for-RecsPR">Proposed Recommendation</a> without a requirement to publish a new <a data-link-type="dfn" href="https://www.w3.org/policies/process/20231103/#RecsCR" id="ref-for-RecsCR">Candidate
Recommendation</a>.
<p class="note">If any, the list of features <em>at-risk</em> <em class="rfc2119">must</em> appear in the
Status of the Document.</p>
</li>
<li> <em class="rfc2119">must</em> specify the deadline for comments,
which <em class="rfc2119">must</em> be <strong>at least</strong> 28 days after publication,
and <em class="rfc2119">should</em> be longer for complex documents, and,
<p class="note">This deadline <em class="rfc2119">must</em> appear in the Status of the Document.</p>
</li>
<li> <em class="rfc2119">must</em> show that the specification has received <a data-link-type="dfn" href="https://www.w3.org/policies/process/20231103/#dfn-wide-review" id="ref-for-dfn-wide-review">wide
review</a>.
<div class="note">
<ul>
<li>Make sure to look at <cite><a href="../documentreview/">How to do Wide
Review</a></cite></li>
<li>Was the public requested to review the document (such as announcement from a previous publication)?
</li>
<li>Which are the groups with dependencies, per the Group's charter, and did they review the document?
</li>
<li>Were the horizontal groups given proper opportunities to review subtantive changes? Are there any <a href="https://www.w3.org/PM/horizontal/"><code>*-needs-resolution</code>
issue</a> pending? How recently were the reviews done?</li>
<li>Was there early review from implementers? Are the changes already deployed in implementations?</li>
</ul>
</div>
</li>
</ul>
</div>
</div>
<div data-profile="CR" data-cr="snapshot">
<!-- <h2 id='publishing-crrs'>Additions to Updating a <span class="status-name">STATUS</span></h2>
<p>The Working Group:</p> -->
<ul>
<li> <em class="rfc2119">must</em> specify the deadline for further comments,
which <em class="rfc2119">must</em> be <strong>at least</strong> 28 days after publication,
and <em class="rfc2119">should</em> be longer for complex documents,
<p class="note">This deadline <em class="rfc2119">must</em> appear in the Status of the Document.</p>
</li>
<li> <em class="rfc2119">may</em> identify features in the document as <a data-link-type="dfn" href="https://www.w3.org/policies/process/20231103/#at-risk" id="ref-for-at-risk">at risk</a>.
These features <em class="rfc2119">may</em> be removed
before advancement to <a data-link-type="dfn" href="https://www.w3.org/policies/process/20231103/#RecsPR" id="ref-for-RecsPR⑤">Proposed Recommendation</a> without a requirement to publish a new <a data-link-type="dfn" href="https://www.w3.org/policies/process/20231103/#RecsCR" id="ref-for-RecsCR">Candidate
Recommendation</a>.
<p class="note">The list of features <em>at-risk</em> <em class="rfc2119">must</em> appear in the Status of the
Document, if any.</p>
</li>