forked from w3c/charter-drafts
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathsw-2019.html
558 lines (488 loc) · 25.7 KB
/
sw-2019.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
<!DOCTYPE html>
<html lang="en-US">
<head>
<meta charset="utf-8" />
<title><i class="todo">[PROPOSED]</i> Service Workers 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/OldGuide/pubrules-style.css">
<link rel="stylesheet" type="text/css" href="https://www.w3.org/2006/02/charter-style.css">
<style>
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: #900;
}
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="#success-criteria">Success Criteria</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="https://www.w3.org/Icons/w3c_home" width="72"></a>
</p>
</header>
<main>
<h1 id="title">[PROPOSED] Service Workers Working Group Charter</h1>
<p class="mission">The <strong>mission</strong> of the <a href="">Service Workers Working Group</a>
is to enable Web applications to take advantage of persistent background processing, including hooks
to enable bootstrapping of web applications while offline.</p>
<div class="noprint">
<p class="join"><a
href="https://www.w3.org/2004/01/pp-impl/101220/join">Join the
Service Workers Working Group.</a></p>
</div>
<p style="padding: 0.5ex; border: 1px solid green"> This proposed charter is available
on <i class="todo"><a href="https://github.com/w3c/charter-drafts/sw-2019.html">GitHub</a>.
Feel free to raise <a href="https://github.com/w3c/charter-drafts/issues">issues</a></i>.
</p>
<section id="details">
<table class="summary-table">
<tr id="Duration">
<th>
Start date
</th>
<td>
<i class="todo">[dd monthname yyyy] (date of the "Call for Participation", when the charter is approved)</i>
</td>
</tr>
<tr id="CharterEnd">
<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>
<ul>
<li>Jake Archibald, Google</li>
<li>Jungkee Song, Microsoft</li>
</ul>
</td>
</tr>
<tr>
<th>
Team Contacts
</th>
<td>
<a href="mailto:[email protected]">Yves Lafon</a>
(0.1 <abbr title="Full-Time Equivalent">FTE</abbr>)
</td>
</tr>
<tr>
<th>
Meeting Schedule
</th>
<td>
<strong>Teleconferences:</strong> Teleconferences will be held approximately monthly.
<br />
<strong>Face-to-face:</strong> The Working Group will meet during the W3C's annual Technical Plenary week;
additional face-to-face meetings will be scheduled by
consent of the participants, 1 or 2 times per year.
</td>
</tr>
</table>
</section>
<section id="scope" class="scope">
<h2>Scope</h2>
<p>Web Applications traditionally assume that the network is reachable, which is not always the case.
The Working Group will specify event-driven services between the network layer and the application,
allowing it to handle network requests gracefully even while offline.
</p>
<!-- <section 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 <i class="todo">(Working|Interest)</i> group.</p>
<ul class="out-of-scope">
</ul>
</section> -->
<section id="success_criteria">
<div>
<h3>Success Criteria</h3>
<p>In order to advance to
<a href="https://www.w3.org/Consortium/Process/#RecsPR">Proposed Recommendation</a>,
each specification is expected to have
<a href="https://www.w3.org/Consortium/Process/#implementation-experience">at least two independent implementations</a>
of each feature defined in the specification.</p>
<p>Each specification should contain a section detailing any known security or privacy implications
for implementers, Web authors, and end users.</p>
<p>Each specification should have an associated testing plan developed in parallel,
and complete by the time the specification reaches
<a href="https://www.w3.org/Consortium/Process/#RecsCR">Candidate Recommendation</a>; by Recommendation, there should be test suite for each deliverable, sufficiently broad to demonstrate interoperability.</p>
<p>Each specification should have implementation reports showing adoption, fostering the ready availability of multiple, independent, interoperable implementations, including in browsers, authoring, and validation tools, and usage on the Web.</p>
<p>If a critical mass of key stakeholders and implementers of this technology do not join the group, its charter should be re-examined by the W3C.</p>
</div>
</section>
</section>
<section id="deliverables">
<h2>
Deliverables
</h2>
<p>More detailed milestones and updated publication schedules
are available from the <a href="https://www.w3.org/sw/">Working Group home page</a>.</p>
<p><i>Draft state</i> indicates the state of the deliverable at the time of the charter approval. <i>Expected completion</i> indicates when the deliverable is projected to become a Recommendation, or otherwise reach a stable state.</p>
<section id="normative">
<h3>
Normative Specifications
</h3>
<p>
The Service Workers Working Group will deliver the following W3C normative specifications:
</p>
<dl>
<dt id="sw1" class="spec"><a
href='https://www.w3.org/TR/service-workers-1' rel='versionof'>Service Workers 1</a></dt>
<dd><b>Latest publication:</b> <a href='https://www.w3.org/TR/2019/WD-service-workers-1-20190813/'>13 August 2019</a></dd>
<dd><b>Reference Draft:</b>
<a href='https://www.w3.org/TR/2017/WD-service-workers-1-20171102/'>https://www.w3.org/TR/2017/WD-service-workers-1-20171102/</a><br>
associated <a href='https://lists.w3.org/Archives/Member/member-cfe/2014May/0008.html'> Call for Exclusion</a> on 13 May 2014
ended on 05 October 2014<br>Produced under Working Group Charter: <a
href="https://www.w3.org/2017/08/sw-charter">https://www.w3.org/2017/08/sw-charter</a></dd>
<dd>
<p>This specification defines an API to enable applications to take advantage of persistent background processing.</p>
<p class="draft-status"><b>Draft state:</b> <a href="https://www.w3.org/TR/service-workers-1/">Working Draft</a></p>
<p class="milestone"><b>Expected completion:</b> <i
class="todo">[Q1 2019]</i></p>
</dd>
<dt id="sw" class="spec"><a
href="https://w3c.github.io/ServiceWorker/"
rel="versionof">Service Workers</a></dt>
<dd>Editors' Draft: <a
href="https://w3c.github.io/ServiceWorker/">https://w3c.github.io/ServiceWorker/</a></dd>
<dd>
<p>This specification defines an API to enable applications to take advantage of persistent background processing.</p>
<p class="draft-status"><b>Draft state:</b> <a href="https://www.w3.org/TR/service-workers/">Working Draft</a></p>
<p class="milestone"><b>Expected completion:</b> <i
class="todo">[Q4 2020]</i></p>
</dd>
</dl>
<p>The Working group may produce multiple versions of each deliverable, reflecting developments
in how much of the relevant technology is interoperably
implemented.
</p>
<p>
The working group intends to use a parallel specification-editing and -testing approach,
where all normative specification changes are generally expected to have a corresponding test change, 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>
<p>
The participants of the current Working Group are looking forward to
moving this work to an "Evergreen standard" model as is being
discussed for Process 2020.
</p>
</section>
<section id="ig-other-deliverables">
<h3>
Other Deliverables
</h3>
<p>The Service Workers Working Group will decide the next steps for the following WICG specification:</p>
<dl>
<dt id="background-fetch" class="spec">Background
Fetch</dt>
<dd><p>An API to handle large uploads/downloads in
the background with user visibility.</p>
<p class="draft-status"><b>Draft state:</b> <a
href="https://wicg.github.io/background-fetch/">Adopted
specification</a> from <a
href="https://www.w3.org/community/wicg/">WICG</a></p>
</dd>
<dl>
<p>Next steps for this document may include promotion to Working Group deliverable (with agreed changes), or deprecation.</p>
<p>The following specifications are in scope for discussion and incubation within the Working Group, but formal publication would require a new charter to get consensus and commitments:</p>
<dt id="background-sync" class="spec">Web Background
Synchronisation</dt>
<dd> <p>This specification defines an API that uses Service Workers to permit both one-off and periodic synchronisation of data,
for applications that use non-local data storage.</p>
<p class="draft-status"><b>Draft state:</b> <a
href="https://wicg.github.io/BackgroundSync/spec/">Adopted
specification</a> from <a
href="https://www.w3.org/community/wicg/">WICG</a></p>
</dd>
<dt id="periodic-background-sync" class="spec">Web Periodic Background
Synchronisation</dt>
<dd> <p>This specification describes a method that enables web applications to periodically synchronize data and content in the background.</p>
<p class="draft-status"><b>Draft state:</b> <a
href="https://wicg.github.io/BackgroundSync/spec/PeriodicBackgroundSync-index.html">Adopted
specification</a> from <a
href="https://www.w3.org/community/wicg/">WICG</a></p>
</dd>
</dl>
<p>Next steps for those documents may include promotion to Working Group deliverables (via a new charter), or deprecation.</p>
<p>
Other non-normative documents may be created such as:
</p>
<ul>
<li>Use case and requirement documents;</li>
<li>Test suite and implementation report for the specification;</li>
<li>Primer or Best Practice documents to support web developers when designing applications.</li>
</ul>
</section>
<section id="timeline">
<h3>Timeline</h3>
<ul>
<li>January 2020: Service Workers 1 Candidate Recommendation</li>
<li>January 2020: FPWD for Service Workers</li>
<li>April 2020: Service Workers 1 Recommendation</li>
<li>May 2020: Proposal for rechartering or closing the Working Group</li>
</ul>
</section>
</section>
<section id="success-criteria">
<h2>Success Criteria</h2>
<p>In order to advance to <a href="https://www.w3.org/Consortium/Process/#RecsPR" title="Proposed Recommendation">Proposed Recommendation</a>, each specification is expected to have <a href="https://www.w3.org/Consortium/Process/#implementation-experience">at least two independent implementations</a> of each of feature defined in the specification.</p>
<p>Each specification should contain a section detailing all known security and privacy implications for implementers, Web authors, and end users.</p>
<p>There should be testing plans for each specification, starting from the earliest drafts.</p>
<p>Each specification of technologies that directly impact user experience should contain a section on accessibility that describes the benefits and impacts, including ways specification features can be used to address them, and
recommendations for maximising accessibility in implementations.</p>
<p>To promote interoperability, all changes made to specifications should have <a href='https://www.w3.org/2019/02/testing-policy.html'>tests</a>.</p>
</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/Consortium/Process/#RecsWD" title="First Public Working Draft">FPWD</a>
and <a href="https://www.w3.org//Consortium/Process/#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/Consortium/Process/#WGCharter">W3C Process Document</a>:</p>
<section>
<h3 id="w3c-coordination">W3C Groups</h3>
<dl>
<dt><a href="https://www.w3.org/2019/webapps/">Web Applications Working Group</a></dt>
<dd>This group enables improved client-side application development on the Web,
including application programming interfaces (APIs) for client-side development.</dd>
<dt><a href="https://www.w3.org/webperf/">Web Performance Working Group</a></dt>
<dd>This group provides methods to measure and improve aspects of application performance of
user agent features and APIs.</dd>
<dt><a href="https://www.w3.org/2011/webappsec/">Web Application Security Working Group</a></dt>
<dd>This group develops security and policy mechanisms to improve the security of Web Applications,
and enable secure cross-origin communication.</dd>
</dl>
</section>
<section>
<h3 id="external-coordination">External Organizations</h3>
<dl>
<dt><a href="http://ecma-international.org/memento/TC39.htm">TC39</a></dt>
<dd>ECMAScript Standards Body</dd>
</dl>
</section>
</section>
<section class="participation">
<h2 id="participation">
Participation
</h2>
<p>
To be successful, this Working Group is expected to have 6 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 working 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>
<p>Participants in the group are required (by the <a href="https://www.w3.org/Consortium/Process/#ParticipationCriteria">W3C Process</a>) to follow the
W3C <a href="https://www.w3.org/Consortium/cepc/">Code of Ethics and Professional Conduct</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/Consortium/Process/#confidentiality-levels">public</a>: the 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.
The meetings themselves are not open to public participation, however.
</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/sw/">Service Worker Working Group home page.</a>
</p>
<p>
Most Service Worker 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 on <a id="public-github" href="https://github.com/w3c/ServiceWorker/issues">GitHub issues</a>.
The public is invited to review, discuss and contribute to this work.
</p>
<p>
The group may use a Member-confidential mailing list for administrative purposes and, at the discretion of the Chairs and members of the group, for member-only discussions in special cases when a participant requests such a discussion.
</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/Consortium/Process/#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 and 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.
A call for consensus (CfC) will be issued for all resolutions (for example, via email and/or web-based survey), with a response period from one week to 10 working days, depending on the chair's evaluation of the group consensus on the issue.
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/#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/">W3C Patent Policy</a> (Version of 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/#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/Consortium/Process/#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/2017/08/sw-charter">Initial Charter</a>
</th>
<td>
02 August 2017
</td>
<td>
30 June 2019
</td>
<td>
none
</td>
</tr>
<tr>
<th><!-- https://lists.w3.org/Archives/Member/w3c-ac-members/2019JulSep/0002.html -->
<a class="todo"
href="https://www.w3.org/2017/08/sw-charter">Charter Extension</a>
</th>
<td>
02 August 2017<!-- or should it be the first day of
the extension, aka 01 July 2019 -->
</td>
<td>
31 December 2019
</td>
<td>
none
</td>
</tr>
<tr>
<th>
<a class="todo" href="">Rechartered</a>
</th>
<td>
22 January 2020
</td>
<td>
30 June 2020
</td>
<td>
<p>Rechartering adding one potential new
deliverables: <a href="#background-fetch">Background Fetch</a>.</p>
</td>
</tr>
</tbody>
</table>
</section>
</section>
</main>
<hr>
<footer>
<address>
<a href="mailto:[email protected]">Yves Lafon</a>
</address>
<p class="copyright">
<a href="https://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> ©
2019
<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="https://www.ercim.eu/"><abbr title="European Research Consortium for Informatics and Mathematics">ERCIM</abbr></a>,
<a href="https://www.keio.ac.jp/">Keio</a>,
<a href="https://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>
<hr>
<p><a href="https://github.com/w3c/charter-drafts">Yes, it's on GitHub!</a>.</p>
</footer>
</body>
</html>