-
Notifications
You must be signed in to change notification settings - Fork 11
/
Copy pathindex.html
705 lines (596 loc) · 42.6 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
<!DOCTYPE html>
<html lang="en-US">
<head>
<meta charset="utf-8" />
<title>*PROPOSED* Web Performance Working Group Charter</title>
<link rel="stylesheet" href="https://www.w3.org/2005/10/w3cdoc.css" type="text/css" media="screen" />
<link rel="stylesheet" type="text/css" href="https://www.w3.org/Guide/pubrules-style.css" />
<link rel="stylesheet" type="text/css" href="https://www.w3.org/2006/02/charter-style.css" />
<style type="text/css">
ul#navbar {
font-size: small;
}
dt.spec {
font-weight: bold;
}
dt.spec new {
background: yellow;
}
ul.out-of-scope > li {
font-weight: bold;
}
ul.out-of-scope > li > ul > li{
font-weight: normal;
}
.issue {
background: cornsilk;
font-style: italic;
}
.todo {
color: red;
}
footer {
font-size: small;
}
</style>
</head>
<body>
<header id="header">
<aside>
<ul id="navbar">
<li><a href="#scope">Scope</a></li>
<li><a href="#deliverables">Deliverables</a></li>
<li><a href="#coordination">Coordination</a></li>
<li><a href="#participation">Participation</a></li>
<li><a href="#communication">Communication</a></li>
<li><a href="#decisions">Decision Policy</a></li>
<li><a href="#patentpolicy">Patent Policy</a></li>
<li><a href="#licensing">Licensing</a></li>
<li><a href="#about">About this Charter</a></li>
</ul>
</aside>
<p>
<a href="https://www.w3.org/"><img alt="W3C" height="48" src="http://www.w3.org/Icons/w3c_home" width="72" /></a>
</p>
</header>
<main>
<h1 id="title">*PROPOSED* Web Performance Working Group Charter</h1>
<p class="mission">The <strong>mission</strong> of the <a href="/2010/webperf">Web Performance Working Group</a> is to provide methods to observe and improve aspects of application performance of user agent features and APIs.</p>
<div class="noprint">
<p class="join"><a href="https://www.w3.org/2004/01/pp-impl/45211/join">Join the Web Performance Working Group</a>.</p>
</div>
<section id="details">
<table class="summary-table">
<tr id="Duration">
<th>
Start date
</th>
<td>
The start date is the date of the "Call for Participation"
</td>
</tr>
<tr id="Duration">
<th>
End date
</th>
<td>
30 June 2020
</td>
</tr>
<tr>
<th>Charter extension</th>
<td>See <a href="#history">Change History</a>.
</td>
</tr>
<tr>
<th>
Chairs
</th>
<td>
Ilya Grigorik, Google
<br>Todd Reifsteck, Microsoft
<br>Yoav Weiss, Invited Expert
</td>
</tr>
<tr>
<th>
Team Contacts
</th>
<td>
Philippe Le Hégaret, Xiaoqian Wu (0.3 <abbr title="Full-Time Equivalent">FTE</abbr>)
</td>
</tr>
<tr>
<th>
Meeting Schedule
</th>
<td>
<strong>Teleconferences:</strong> bi-weekly
<br />
<strong>Face-to-face:</strong> we will meet during the W3C's annual Technical Plenary week; one additional face-to-face meeting per year may be scheduled by consent of the participants.
<br> IRC channel: #webperf
</td>
</tr>
</table>
</section>
<section id="scope" class="scope">
<h2>Scope</h2>
<p>Web developers are building sophisticated applications where application performance is a critical feature. Web developers want the ability to observe the performance characteristics of their applications, and they want the ability to write more efficient applications, using well-defined interoperable methods.
Their methods must be both secure and privacy-enabling by design, using well-defined interoperable methods that conform to the current Web browser security model.</p>
<p>The Web Performance Working Group's scope of work includes user agent features and APIs to observe and improve aspects of application performance, such as measuring network and rendering performance, responsiveness and interactivity, memory and CPU use, application failures, and similar APIs and infrastructure to enable measurement and delivery of better user experience. Such deliverables will apply to desktop and mobile browsers and other non-browser environments where appropriate, and will be consistent with Web technologies designed in other working groups including HTML, CSS, Web Application Security, Web Platform, Device and Sensors, and SVG.</p>
<p>
In addition to developing Recommendation Track documents, the Web Performance Working Group may provide review of specifications from other Working Groups.
</p>
<div id="section-out-of-scope">
<h3 id="out-of-scope">Out of Scope</h3>
<p>The following features are out of scope, and will not be addressed by this working group.</p>
<ul class="out-of-scope">
<li>performance data analysis techniques or algorithms.</li>
</ul>
</div>
<div>
<h3>Success Criteria</h3>
<p>In order to advance to <a href="https://www.w3.org/2015/Process-20150901/#RecsCR" title="Proposed Recommendation">Proposed Recommendation</a>, each specification is expected to have at least two independent implementations of each of feature defined in the specification.</p>
<p>Each specification should contain a section detailing any <a href='https://www.w3.org/TR/security-privacy-questionnaire/'>known security</a>, fingerprinting, and privacy implications, and suggested <a href='https://w3c.github.io/perf-security-privacy/'>mitigation strategies</a> for implementers, Web authors, and end users. The group should not publish a specification if acceptable mitigation strategies cannot be found.</p>
<p>Normative specification changes are generally expected to have a corresponding set of tests, either in the form of new tests or modifications to existing tests, or must include the rationale for why test updates are not required for the proposed update.</p>
</div>
</section>
<section id="deliverables">
<h2>
Deliverables
</h2>
<p>Note: Latest milestone and publication schedules for the group's deliverables listed below can be found on the <a href="https://docs.google.com/spreadsheets/d/1JIB8c7hfyH_wuxkf6bLgovFekHP1LpTtqBTJGEUIK7E/edit#gid=0">publication status page</a>.</p>
<p><i>Draft state</i> indicates the state of the deliverable at the time of the charter approval. <i>Next Recommendation expected completion</i> indicates when the deliverable is projected to become a Recommendation, or otherwise reach a stable state.</p>
<div id="normative">
<h3>
Normative Specifications
</h3>
<p>
The working group will deliver incremental revisions of the following W3C normative specifications:
</p>
<dl>
<dt id="hr-time" class="spec"><a href="https://w3c.github.io/hr-time/">High Resolution Time</a></dt>
<dd>
<p>This document defines an API that provides the current time in sub-millisecond resolution such that it is not subject to system clock skew or adjustments. </p>
<p class="draft-status"><b>Draft state:</b> <a href="https://www.w3.org/TR/hr-time-2/">Candidate Recommendation</a></p>
<p class="milestone"><b>Next Recommendation expected completion:</b> Q2 2019</p>
<p>Latest publication: <a href="https://www.w3.org/TR/2018/CR-hr-time-2-20180301/">01 March 2018</a><br>Reference Draft:
<a href="https://www.w3.org/TR/2018/CR-hr-time-2-20180301/">https://www.w3.org/TR/2018/CR-hr-time-2-20180301/</a><br>
associated <a href="https://lists.w3.org/Archives/Member/member-cfe/2018Mar/0000.html"> Call for Exclusion</a> on 01 March 2018
ended on 30 April 2018<br>Produced under Working Group Charter: https://www.w3.org/2016/07/webperf
</dd>
<dt id="performance-timeline" class="spec"><a href="https://w3c.github.io/performance-timeline/">Performance Timeline</a></dt>
<dd>
<p>This specification defines a unified interface to store and retrieve performance metric data.</p>
<p class="draft-status"><b>Draft state:</b> <a href="https://www.w3.org/TR/performance-timeline/">Candidate Recommendation</a></p>
<p class="milestone"><b>Next Recommendation expected completion:</b> Q2 2019</p>
<p>Latest publication: <a href="https://www.w3.org/TR/2016/CR-performance-timeline-2-20161208/">08 December 2016</a><br>Reference Draft:
<a href="https://www.w3.org/TR/2016/CR-performance-timeline-2-20161208/">https://www.w3.org/TR/2016/CR-performance-timeline-2-20161208/</a><br>
associated <a href="https://lists.w3.org/Archives/Member/member-cfe/2016Dec/0001.html"> Call for Exclusion</a> on 08 December 2016
ended on 06 February 2017<br>Produced under Working Group Charter: https://www.w3.org/2016/07/webperf
</dd>
<dt id="resource-timing" class="spec"><a href="https://w3c.github.io/resource-timing/">Resource Timing</a></dt>
<dd>
<p>An interoperable means for site developers to collect real-world performance information from the user agent while loading resources as specified from the root document of a webpage. The user agent captures the end to end latency associated with loading resources from a web server. This includes the time associated with fetching the resource from the network and the time associated to load the resource within the user agent. This might include:</p>
<ul>
<li>timing associated with the network;</li>
<li>timings associated with loading the resource in the document;</li>
<li>a resource may be one of the following elements: iframe, img, script, object, embed and link.</li>
</ul>
<p class="draft-status"><b>Level 1 Draft state:</b> <a href="https://www.w3.org/TR/resource-timing-1/">Candidate Recommendation</a></p>
<p class="milestone"><b>Next Recommendation expected completion:</b> Q3 2018</p>
<p>Latest publication: <a href="https://www.w3.org/TR/2017/CR-resource-timing-1-20170330/">30 March 2017</a><br>Reference Draft:
<a href="https://www.w3.org/TR/2017/CR-resource-timing-1-20170330/">https://www.w3.org/TR/2017/CR-resource-timing-1-20170330/</a><br>
associated <a href="https://lists.w3.org/Archives/Member/member-cfe/2017Mar/0005.html">Call for Exclusion</a> on 30 March 2017
ended on 29 May 2017<br>Produced under Working Group Charter: https://www.w3.org/2016/07/webperf
<p class="draft-status"><b>Level 2 Draft state:</b> <a href="https://www.w3.org/TR/resource-timing-2/">Working Draft</a></p>
<p class="milestone"><b>Next Recommendation expected completion:</b> Q2 2019</p>
<p>Latest publication: <a href="https://www.w3.org/TR/2018/WD-resource-timing-2-20180518/">18 May 2018</a><br>Reference Draft:
<a href="https://www.w3.org/TR/2016/WD-resource-timing-2-20161103/">https://www.w3.org/TR/2016/WD-resource-timing-2-20161103/</a><br>
associated <a href="https://lists.w3.org/Archives/Member/member-cfe/2016Nov/0005.html"> Call for Exclusion</a> on 03 November 2016
ended on 02 April 2017<br>Produced under Working Group Charter: https://www.w3.org/2016/07/webperf</p>
</dd>
<dt id="navigation-timing" class="spec"><a href="https://w3c.github.io/navigation-timing/">Navigation Timing</a></dt>
<dd>
<p>An interoperable means for site developers to collect real-world performance information from the user agent while loading the root document of a webpage. The user agent captures the end to end latency associated with loading a webpage from a web server. This includes the time associated with fetching the document from the network to the time associated to load the document within the user agent.</p>
<p class="draft-status"><b>Draft state:</b> <a href="https://www.w3.org/TR/navigation-timing-2/">Working Draft</a></p>
<p class="milestone"><b>Next Recommendation expected completion:</b> Q2 2019</p>
<p>Note: after Level 2 of Navigation Timing is ratified, future development of new Navigation Timing features will be done within Resource Timing; Navigation Timing will be merged with Resource Timing.</p>
<p>Latest publication: <a href="https://www.w3.org/TR/2017/WD-navigation-timing-2-20171205/">05 December 2017</a><br>Reference Draft:
<a href="https://www.w3.org/TR/2015/WD-navigation-timing-2-20150120/">https://www.w3.org/TR/2015/WD-navigation-timing-2-20150120/</a><br>
associated <a href="https://lists.w3.org/Archives/Member/member-cfe/2013Jan/0014.html">Call for Exclusion</a> on 31 January 2013
ended on 30 June 2013<br>Produced under Working Group Charter: https://www.w3.org/2013/01/webperf
</dd>
<dt id="user-timing" class="spec"><a href="https://w3c.github.io/user-timing/">User Timing</a></dt>
<dd>
<p>An interoperable means for site developers to capture timing information with a developer supplied name. The user agent captures the time stamp at the point and time specified in the code executing in the user agent.</p>
<p class="draft-status"><b>Draft state:</b> <a href="https://www.w3.org/TR/user-timing-2/">Candidate Recommendation</a></p>
<p class="milestone"><b>Next Recommendation expected completion:</b> Q2 2019</p>
<p>Latest publication: <a href="https://www.w3.org/TR/2018/WD-user-timing-2-20180402/">02 April 2018</a><br>Reference Draft:
<a href="https://www.w3.org/TR/2016/WD-user-timing-2-20161101/">https://www.w3.org/TR/2016/WD-user-timing-2-20161101/</a><br>
associated <a href="https://lists.w3.org/Archives/Member/member-cfe/2016Nov/0002.html"> Call for Exclusion</a> on 01 November 2016
ended on 31 March 2017<br>Produced under Working Group Charter: https://www.w3.org/2016/07/webperf</p>
</dd>
<dt id="page-visibility" class="spec"><a href="https://w3c.github.io/page-visibility/">Page Visibility</a></dt>
<dd>
<p>An interoperable means for site developers to programmatically determine the current visibility of a document and be notified of visibility changes.</p>
<p class="draft-status"><b>Draft state:</b> <a href="https://www.w3.org/TR/page-visibility-2/">Proposed Recommendation</a></p>
<p class="milestone"><b>Next Recommendation expected completion:</b> Q2 2019</p>
<p>Latest publication: <a href="https://www.w3.org/TR/2017/PR-page-visibility-2-20171017/">17 October 2017</a><br>Reference Draft:
<a href="https://www.w3.org/TR/2017/CR-page-visibility-2-20170328/">https://www.w3.org/TR/2017/CR-page-visibility-2-20170328/</a><br>
associated <a href="https://lists.w3.org/Archives/Member/member-cfe/2017Mar/0003.html"> Call for Exclusion</a> on 29 March 2017
ended on 27 May 2017<br>Produced under Working Group Charter: https://www.w3.org/2016/07/webperf</p>
</dd>
<dt id="beacon" class="spec"><a href="https://w3c.github.io/beacon/">Beacon</a></dt>
<dd>
<p>An interoperable API for site developers to asynchronously transfer data from the user agent to a web server, with a guarantee from the user agent that the data will be eventually sent.</p>
<p class="draft-status"><b>Draft state:</b> <a href="https://www.w3.org/TR/beacon/">Candidate Recommendation</a></p>
<p class="milestone"><b>Next Recommendation expected completion:</b> Q2 2019</p>
<p>Latest publication: <a href="https://www.w3.org/TR/2017/CR-beacon-20170413/">13 April 2017</a><br>Reference Draft:
<a href="https://www.w3.org/TR/2017/CR-beacon-20170413/">https://www.w3.org/TR/2017/CR-beacon-20170413/</a><br>
associated <a href="https://lists.w3.org/Archives/Member/member-cfe/2017Apr/0004.html"> Call for Exclusion</a> on 13 April 2017
ended on 12 June 2017<br>Produced under Working Group Charter: https://www.w3.org/2016/07/webperf
</dd>
<dt id="ric" class="spec"><a href="https://w3c.github.io/requestidlecallback/">Cooperative Scheduling of Background Tasks</a></dt>
<dd>
<p>An API that web page authors can use to cooperatively schedule background tasks such that they do not introduce delays to other high priority tasks that share the same event loop, such as input processing, animations and frame compositing.</p>
<p class="draft-status"><b>Draft state:</b> <a href="https://www.w3.org/TR/requestidlecallback/">Proposed Recommendation</a></p>
<p class="milestone"><b>Next Recommendation expected completion:</b> Q4 2018</p>
<p>Latest publication: <a href="https://www.w3.org/TR/2017/PR-requestidlecallback-20171010/">10 October 2017</a><br>Reference Draft:
<a href="https://www.w3.org/TR/2017/CR-requestidlecallback-20170131/">https://www.w3.org/TR/2017/CR-requestidlecallback-20170131/</a><br>
associated <a href="https://lists.w3.org/Archives/Member/member-cfe/2017Feb/0000.html"> Call for Exclusion</a> on 02 February 2017
ended on 01 April 2017<br>Produced under Working Group Charter: https://www.w3.org/2016/07/webperf</p>
</dd>
<dt id="resource_hints" class="spec"><a href="https://w3c.github.io/resource-hints/">Resource Hints</a></dt>
<dd>
<p>This specification defines the dns-prefetch, preconnect, prefetch, and prerender relationships of the HTML Link Element (<link>).</p>
<p class="draft-status"><b>Draft state:</b> <a href="https://www.w3.org/TR/resource-hints/">Working Draft</a></p>
<p class="milestone"><b>Next Recommendation expected completion:</b> Q4 2019</p>
<p>Latest publication: <a href="https://www.w3.org/TR/2018/WD-resource-hints-20180115/">15 January 2018</a><br>Reference Draft:
<a href="https://www.w3.org/TR/2014/WD-resource-hints-20141021/">https://www.w3.org/TR/2014/WD-resource-hints-20141021/</a><br>
associated <a href="https://lists.w3.org/Archives/Member/member-cfe/2014Oct/0006.html"> Call for Exclusion</a> on 23 October 2014
ended on 20 March 2015<br>Produced under Working Group Charter: https://www.w3.org/2013/01/webperf
</dd>
<dt id="preload" class="spec"><a href="https://w3c.github.io/preload/">Preload</a></dt>
<dd>
<p>This specification defines the link relation type <code>preload</code>, a declarative fetch primitive that initiates an early fetch and separates fetching from resource execution.</p>
<p class="draft-status"><b>Draft state:</b> <a href="https://www.w3.org/TR/preload/">Candidate Recommendation</a></p>
<p class="milestone"><b>Next Recommendation expected completion:</b> Q2 2019</p>
<p>Latest publication: <a href="https://www.w3.org/TR/2017/CR-preload-20171026/">26 October 2017</a><br>Reference Draft:
<a href="https://www.w3.org/TR/2017/CR-preload-20171026/">https://www.w3.org/TR/2017/CR-preload-20171026/</a><br>
associated <a href="https://lists.w3.org/Archives/Member/member-cfe/2017Oct/0007.html"> Call for Exclusion</a> on 26 October 2017
ended on 25 December 2017<br>Produced under Working Group Charter: https://www.w3.org/2016/07/webperf</p>
</dd>
<!-- Incubated in: https://github.com/WICG/longtasks -->
<dt id="longtasks" class="spec"><a href="https://w3c.github.io/longtasks/">Long Task</a></dt>
<dd>
<p>This specification defines an API that web page authors can use to detect presence of "long tasks" that monopolize the UI thread for extended periods of time and block other critical tasks from being executed - e.g. reacting to user input.</p>
<p class="draft-status"><b>Draft state:</b> <a href="https://www.w3.org/TR/longtasks-1/">Working Draft</a></p>
<p class="milestone"><b>Next Recommendation expected completion:</b> Q4 2019</p>
<p>Latest publication: <a href="https://www.w3.org/TR/2017/WD-longtasks-1-20170907/">07 September 2017</a><br>Reference Draft:
<a href="https://www.w3.org/TR/2017/WD-longtasks-1-20170907/">https://www.w3.org/TR/2017/WD-longtasks-1-20170907/</a><br>
associated <a href="https://lists.w3.org/Archives/Member/member-cfe/2017Dec/0001.html"> Call for Exclusion</a> on 07 December 2017
ended on 04 February 2018<br>Produced under Working Group Charter: https://www.w3.org/2016/07/webperf</p>
</dd>
<!-- Incubated in: https://github.com/WICG/paint-timing -->
<dt id="paint-timing" class="spec"><a href="https://w3c.github.io/paint-timing/">Paint Timing</a></dt>
<dd>
<p>An interoperable API for site developers to capture the set of key moments during pageload - e.g. first paint and first contentful paint.</p>
<p class="draft-status"><b>Draft state:</b> <a href="https://www.w3.org/TR/paint-timing/">Working Draft</a></p>
<p class="milestone"><b>Next Recommendation expected completion:</b> Q4 2019</p>
<p>
<br>Latest publication: <a href="https://www.w3.org/TR/2017/WD-paint-timing-20170907/">07 September 2017</a><br>Reference Draft:
<a href="https://www.w3.org/TR/2017/WD-paint-timing-20170907/">https://www.w3.org/TR/2017/WD-paint-timing-20170907/</a><br>
associated <a href="https://lists.w3.org/Archives/Member/member-cfe/2017Dec/0001.html"> Call for Exclusion</a> on 07 December 2017
ended on 04 February 2018<br>Produced under Working Group Charter: https://www.w3.org/2016/07/webperf</p>
</dd>
<!-- Incubated in: https://github.com/WICG/server-timing -->
<dt id="server-timing" class="spec"><a href="https://w3c.github.io/server-timing/">Server Timing</a></dt>
<dd>
<p>This specification enables a server to communicate performance metrics about the request-response cycle to the user agent. It also standardizes a JavaScript interface to enable applications to collect, process, and act on these metrics to optimize application delivery.
</p>
<p class="draft-status"><b>Draft state:</b> <a href="https://www.w3.org/TR/server-timing/">Working Draft</a></p>
<p class="milestone"><b>Next Recommendation expected completion:</b> Q2 2019</p>
<p>Latest publication: <a href="https://www.w3.org/TR/2017/WD-server-timing-20171229/">29 December 2017</a><br>Reference Draft:
<a href="https://www.w3.org/TR/2017/WD-server-timing-20170713/">https://www.w3.org/TR/2017/WD-server-timing-20170713/</a><br>
associated <a href="https://lists.w3.org/Archives/Member/member-cfe/2017Jul/0005.html"> Call for Exclusion</a> on 13 July 2017
ended on 10 December 2017<br>Produced under Working Group Charter: https://www.w3.org/2016/07/webperf
</dd>
<!-- Incubated in: https://github.com/WICG/device-memory -->
<dt id="device-memory" class="spec"><a href="https://w3c.github.io/device-memory/">Device Memory</a></dt>
<dd>
<p>This specification defines a JavaScript API and HTTP Client Hint header to surface device capability for memory — i.e. device RAM, in order to enable web apps to customize content depending on device memory constraints.
</p>
<p class="draft-status"><b>Draft state:</b> <a href="https://w3c.github.io/device-memory/">CG report</a></p>
<p class="milestone"><b>Next Recommendation expected completion:</b> Q4 2019</p>
</dd>
<!-- Incubated in: https://github.com/WICG/reporting -->
<dt id="reporting" class="spec"><a href="https://w3c.github.io/reporting/">Reporting</a></dt>
<dd>
<p>This specification defines a generic reporting framework which allows web developers to associate a set of named reporting endpoints with an origin. Various platform features (like Content Security Policy, Network Error Reporting, and others) will use these endpoints to deliver feature-specific reports in a consistent manner.
</p>
<p class="draft-status"><b>Draft state:</b> <a href="https://w3c.github.io/reporting/">CG report</a></p>
<p class="milestone"><b>Next Recommendation expected completion:</b> Q4 2019</p>
<p>
Reference Draft: <a href="https://www.w3.org/TR/2016/WD-reporting-1-20160407/">https://www.w3.org/TR/2016/WD-reporting-1-20160407/</a><br>
associated <a href="https://lists.w3.org/Archives/Member/member-cfe/2016Apr/0001.html"> Call for Exclusion</a> on 7 April 2016
ended on 4 September 2016<br>Produced under Working Group Charter: https://www.w3.org/2015/06/webperf
</p>
</dd>
<!-- Incubated in: https://github.com/WICG/network-error-logging -->
<dt id="nel" class="spec"><a href="https://w3c.github.io/network-error-logging">Network Error Logging</a></dt>
<dd>
<p>This specification defines a mechanism that enables developers to declare a network error reporting policy for a web application. A user agent can use this policy to report encountered network errors that prevented it from successfully fetching requested resource
</p>
<p class="draft-status"><b>Draft state:</b> <a href="https://w3c.github.io/network-error-logging">CG report</a></p>
<p class="milestone"><b>Next Recommendation expected completion:</b> Q4 2019</p>
<p>
Reference Draft: <a href="https://www.w3.org/TR/2014/WD-navigation-error-logging-20140211/">https://www.w3.org/TR/2014/WD-navigation-error-logging-20140211/</a><br>
associated <a href="https://lists.w3.org/Archives/Member/member-cfe/2014Feb/0008.html">Call for Exclusion</a> on 12 February 2014
ended on 11 July 2014<br>Produced under Working Group Charter: https://www.w3.org/2013/01/webperf
</p>
</dd>
<!--
<dt id="" class="spec"></dt>
<dd>
<p></p>
<p class="draft-status"><b>Draft state:</b> <a href="https://www.w3.org/TR/">Working Draft</a></p>
<p class="milestone"><b>Next Recommendation expected completion:</b> Q3 2017</p>
</dd>
-->
</dl>
</div>
<div id="ig-other-deliverables">
<h3>
Other Deliverables
</h3>
<p>
The Group will maintain a <a href='https://w3c.github.io/perf-timing-primer/'>non-normative Primer document</a> to facilitate the understanding of the interrelationships between its deliverables.</p>
</p>
<p>Other non-normative documents may be created such as:</p>
<ul>
<li><a href="https://w3c.github.io/perf-security-privacy/">Security and Privacy considerations for Performance APIs</a></li>
<li>Test suites for each specification;</li>
<li>Use cases documents to support development and exploration of performance-critical web platform features and APIs;</li>
<li>Primer or Best Practice documents to support web developers when designing applications with performance in mind;</li>
<li>Developer and user guides for its normative specifications;</li>
<li>Best practice document explaining how data is commonly gathered between the client and the server.</li>
</ul>
</div>
</section>
<section id="coordination">
<h2>Coordination</h2>
<p>For all specifications, this Working Group will seek <a href="https://www.w3.org/Guide/Charter.html#horizontal-review">horizontal review</a> for accessibility, internationalization, performance, privacy, and security with the relevant Working and Interest Groups, and with the <a href="https://www.w3.org/2001/tag/" title="Technical Architecture Group">TAG</a>. Invitation for review must be issued during each major standards-track document transition, including <a href="https://www.w3.org/2015/Process-20150901/#RecsWD" title="First Public Working Draft">FPWD</a> and <a href="https://www.w3.org/2015/Process-20150901/#RecsCR" title="Candidate Recommendation">CR</a>, and should be issued when major changes occur in a specification.</p>
<p>Additional technical coordination with the following Groups will be made, per the <a href="https://www.w3.org/2015/Process-20150901/#WGCharter">W3C Process Document</a>:</p>
<div>
<h3 id="w3c-coordination">W3C Groups</h3>
<dl>
<dt><a href="https://www.w3.org/2001/tag/">Technical Architecture Group (TAG)</a></dt>
<dd>The WG may ask the Technical Architecture Group to review some of its specifications.</dd>
<dt><a href="https://www.w3.org/WebPlatform/WG/">Web Platform Working Group</a></dt>
<dd>This Working Group develops APIs for client-side development and for markup vocabularies for describing and controlling client-side application behavior.</dd>
<dt><a href="https://www.w3.org/2011/webappsec/">Web Application Security Working Group</a></dt>
<dd>This Working Group develops security and policy mechanisms to improve the security of Web Applications, and enable secure cross-site communication.</dd>
<dt><a href="https://www.w3.org/Style/CSS/members">CSS Working Group</a></dt>
<dd>The group develops and maintains CSS, which is relevant for specifications such as page visibility.</dd>
<dt><a href="https://www.w3.org/Privacy/IG/">Privacy Interest Group</a></dt>
<dd>This group monitors ongoing privacy issues that affect the Web, investigates potential areas for new privacy work, and provides guidelines and advice for addressing privacy in standards development.</dd>
<dt><a href="https://www.w3.org/community/wicg/">Web Platform Incubator Community Group</a></dt>
<dd>
This group provides a lightweight venue for proposing, incubating and discussing new web platform features. The Web Performance Working group will incubate and review new proposals that are within scope of our charter within the WICG. Once such WICG-incubated proposal is implemented and available in at least one major browser, and has support from one more, it may be adopted by the Web Performance Working group.
</dd>
</dl>
<h3 id="external-coordination">External Organizations</h3>
<dl>
<dt><a href="http://www.ecma-international.org/memento/TC39.htm" id="tc39">ECMA Technical Committee 39 (TC39)</a></dt>
<dd>This is the group responsible for ECMAScript standardization, and related ECMAScript features like E4X. As the Web Performance Working Group will be developing ECMAScript APIs, it should collaborate with TC39.</dd>
<dt><a title="IETF Home Page" href="http://www.ietf.org/" id="ietf">Internet Engineering Task Force</a></dt>
<dd>The IETF is responsible for defining robust and secure protocols for Internet functionality, in particular HTTP. The Working Group should coordinate protocol-related work (e.g. profiles of hybi or HTTP) with the appropriate IETF WGs.</dd>
<dt><a title="WHATWG" href="https://whatwg.org/" id="whatwg">Web Hypertext Application Technology Working Group (WHATWG)</a></dt>
<dd>The Web Hypertext Application Technology Working Group (WHATWG) is a community of people interested in evolving the web through standards and tests.</dd>
</dl>
</div>
</section>
<section class="participation">
<h2 id="participation">
Participation
</h2>
<p>
To be successful, this Working Group is expected to have 5 or more active participants for its duration, including representatives from the key implementors of this specification, and active Editors and Test Leads for each specification. The Chairs, specification Editors, and Test Leads are expected to contribute half of a day per week towards the Working Group. There is no minimum requirement for other Participants.
</p>
<p>
The group encourages questions, comments and issues on its public mailing lists and document repositories, as described in <a href='#communication'>Communication</a>.
</p>
<p>
The group also welcomes non-Members to contribute technical submissions for consideration upon their agreement to the terms of the <a href="https://www.w3.org/Consortium/Patent-Policy/">W3C Patent Policy</a>.
</p>
</section>
<section id="communication">
<h2>
Communication
</h2>
<p id="public">
Technical discussions for this Working Group are conducted in <a href="https://www.w3.org/2015/Process-20150901/#confidentiality-levels">public</a>. Meeting minutes from teleconference and face-to-face meetings will be archived for public review, and technical discussions and issue tracking will be conducted in a manner that can be both read and written to by the general public. Working Drafts and Editor's Drafts of specifications will be developed on a public repository, and may permit direct public contribution requests.
</p>
<p>
Information about the group (including details about deliverables, issues, actions, status, participants, and meetings) will be available from the <a href="https://www.w3.org/2010/webperf/">Web Performance Working Group home page.</a>
</p>
<p>
Most Web Performance Working Group teleconferences will focus on discussion of particular specifications, and will be conducted on an as-needed basis.
</p>
<p>
This group primarily conducts its technical work in its <a href="https://github.com/orgs/w3c/teams/web-performance/repositories">public repositories</a>. There is also a public mailing list <a id="public-name" href="mailto:[email protected]">[email protected]</a> (<a href="https://lists.w3.org/Archives/Public/public-web-perf/">archive</a>). The public is invited to contribute to the github repositories and post messages to the list. Regular activity summaries around the github repositories will be provided.
</p>
</section>
<section id="decisions">
<h2>
Decision Policy
</h2>
<p>
This group will seek to make decisions through consensus and due process, per the <a href="https://www.w3.org/2015/Process-20150901/#Consensus"> W3C Process Document (section 3.3</a>). Typically, an editor or other participant makes an initial proposal, which is then refined in discussion with members of the group and other reviewers, and consensus emerges with little formal voting being required.</p>
<p>
However, if a decision is necessary for timely progress, but consensus is not achieved after careful consideration of the range of views presented, the Chairs may call for a group vote, and record a decision along with any objections.
</p>
<p>
To afford asynchronous decisions and organizational deliberation, any resolution (including publication decisions) taken in a face-to-face meeting or teleconference will be considered provisional until 10 working days after the publication of the resolution in draft minutes sent, which will be published within 5 working days of the meeting to the working group's mailing list with a 'call for consensus' in the subject line. If no objections are raised on the mailing list by the end of the response period, the resolution will be considered to have consensus as a resolution of the Working Group.
</p>
<p>
All decisions made by the group should be considered resolved unless and until new information becomes available, or unless reopened at the discretion of the Chairs or the Director.
</p>
<p>
This charter is written in accordance with the <a href="https://www.w3.org/Consortium/Process/policies#Votes">W3C Process Document (Section 3.4, Votes)</a>, and includes no voting procedures beyond what the Process Document requires.
</p>
</section>
<section id="patentpolicy">
<h2>
Patent Policy
</h2>
<p>
This Working Group operates under the <a href="https://www.w3.org/Consortium/Patent-Policy-20170801/">W3C Patent Policy</a> 5 February 2004 (updated 1 August 2017). To promote the widest adoption of Web standards, W3C seeks to issue Recommendations that can be implemented, according to this policy, on a Royalty-Free basis.
For more information about disclosure obligations for this group, please see the <a href="https://www.w3.org/2004/01/pp-impl/">W3C Patent Policy Implementation</a>.
</p>
</section>
<section id="licensing">
<h2>Licensing</h2>
<p>This Working Group will use the <a href="https://www.w3.org/Consortium/Legal/copyright-software">W3C Software and Document license</a> for all its deliverables.</p>
</section>
<section id="about">
<h2>
About this Charter
</h2>
<p>
This charter has been created according to <a href="https://www.w3.org/Consortium/Process/groups#GAGeneral">section 5.2</a> of the <a href="https://www.w3.org/Consortium/Process">Process Document</a>. In the event of a conflict between this document or the provisions of any charter and the W3C Process, the W3C Process shall take precedence.
</p>
<section id="history">
<h3>
Charter History
</h3>
<p>The following table lists details of all changes from the initial charter, per the <a href="https://www.w3.org/2015/Process-20150901/#CharterReview">W3C Process Document (section 5.2.3)</a>:</p>
<table class="history">
<tbody>
<tr>
<th>
Charter Period
</th>
<th>
Start Date
</th>
<th>
End Date
</th>
<th>
Changes
</th>
</tr>
<tr>
<th>
<a href="https://www.w3.org/2010/08/webperf">Initial Charter</a>
</th>
<td>
2010-08-18
</td>
<td>
2011-06-30
</td>
<td>
none
</td>
</tr>
<tr>
<th>
<a href="https://www.w3.org/2011/04/webperf">Rechartered</a>
</th>
<td>
2011-04-25
</td>
<td>
2012-06-30
</td>
<td>
<p>Added Page Visibility, Efficient Script Yielding, Display Paint notifications</p>
</td>
</tr>
<tr>
<th>
<a href="https://www.w3.org/2013/01/webperf">Rechartered</a>
</th>
<td>
2013-06-06
</td>
<td>
2015-05-31
</td>
<td>
<p>Added Performance Timeline, Timing control for script-based animations, Resource Priorities, Beacon, Diagnostics, Pre-render, Display Performance, Async scroll, HAR. Removed Display Paint notifications.</p>
</td>
</tr>
<tr>
<th>
<a href="https://www.w3.org/2015/06/webperf">Rechartered</a>
</th>
<td>
2015-06-25
</td>
<td>
2016-05-31
</td>
<td>
<p>Added Server Timing, Resource Hints, NEL, Preload (previously Pre-render), Frame Timing, CPU and Memory monitoring. Removed Resource Priorities, Diagnostics, Display Performance, Async scroll.</p>
</td>
</tr>
<tr>
<th>
<a href="https://www.w3.org/2016/07/webperf">Rechartered</a>
</th>
<td>
2016-06-01
</td>
<td>
2018-05-31
</td>
<td>
<p>Removed CPU and Memory monitoring. Moved to WICG: Frame Timing, Server Timing, NEL, Reporting. Moved to Software and Document license.</p>
</td>
</tr>
<tr>
<th>
<a href="">Proposed</a>
</th>
<td>
2018-06-30
</td>
<td>
2020-06-30
</td>
<td>
<p>Removed Memory Pressure. Added: Reporting, NEL, Device Memory.</p>
</td>
</tr>
</tbody>
</table>
</section>
</section>
</main>
<hr />
<footer>
<address>
Ilya Grigorik, <a href="mailto:[email protected]">Philippe Le Hégaret</a>, Todd Reifsteck
</address>
<p class="copyright">
<a href="https://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> ©
2018
<a href="https://www.w3.org/"><abbr title="World Wide Web Consortium">W3C</abbr></a><sup>®</sup>
(
<a href="https://www.csail.mit.edu/"><abbr title="Massachusetts Institute of Technology">MIT</abbr></a>,
<a href="http://www.ercim.eu/"><abbr title="European Research Consortium for Informatics and Mathematics">ERCIM</abbr></a>,
<a href="http://www.keio.ac.jp/">Keio</a>,
<a href="http://ev.buaa.edu.cn/">Beihang</a>
), All Rights Reserved.
<abbr title="World Wide Web Consortium">W3C</abbr> <a href="https://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>, <a href="https://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a> and <a href="https://www.w3.org/Consortium/Legal/copyright-documents">document use</a> rules apply.
</p>
<p>
<!-- $Date: 2015/04/30 16:53:49 $ -->
</p>
</footer>
</body>
</html>