forked from w3c/charter-drafts
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathsw-charter.html
488 lines (417 loc) · 21.3 KB
/
sw-charter.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
<!DOCTYPE html>
<html lang="en-US">
<head>
<meta charset="utf-8" />
<title>[PROPOSED] 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/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: #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="#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>
<!-- enable when chartered div class="noprint">
<p class="join"><a href="https://www.w3.org/2004/01/pp-impl/#####/join">Join the Service Workers Working Group.</a></p>
</div-->
<section id="details">
<table class="summary-table">
<tr id="Duration">
<th>
Start date
</th>
<td>
[dd month yyyy the date when the group call for participation starts]
</td>
</tr>
<tr id="Duration">
<th>
End date
</th>
<td>
30 June 2019
</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>Jatinder Mann, Microsoft</li>
</ul>
</td>
</tr>
<tr>
<th>
Team Contacts
</th>
<td>
<a href="mailto:[email protected]">Mike Smith</a>, <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,
2 or 3 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.
<!--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">
</ul>
</div-->
<div>
<h3>Success Criteria</h3>
<p>In order to advance to
<a href="https://www.w3.org/2017/Process-20170301/#RecsPR">Proposed Recommendation</a>,
each specification is expected to have
<a href="https://www.w3.org/2017/Process-20170301/#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/2017/Process-20170301/#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 id="deliverables">
<h2>
Deliverables
</h2>
<p>More detailed milestones and updated publication schedules are available on the
<a href="https://www.w3.org/wiki/[groupname]/PubStatus">group publication status 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>
<div id="normative">
<h3>
Normative Specifications
</h3>
<p>
The Working Group will deliver the following W3C normative specifications:
</p>
<dl>
<dt id="service-worker" class="spec"><a href="https://w3c.github.io/ServiceWorker/">Service Workers</a></dt>
<dd>
<p>This specification defines an API.</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> Version 1, Q4 2017</p>
<dl>
<dt>Adopted Working Draft:</dt>
<dd><a href="https://www.w3.org/TR/2016/WD-service-workers-1-20161011/">Service Workers</a>, November 10, 2016.
<dt>Reference Draft:</dt>
<dd><a href="https://www.w3.org/TR/2016/WD-service-workers-1-20161011/">Service Workers</a>, November 10, 2016,
produced under the <a href="https://www.w3.org/2016/11/webplatform-charter.html">Web Platform Working Group</a>.
</dd>
</dl></dl>
<p>
The Working Group may deliver the following W3C normative specifications:
</p>
<dl>
<dt id="service-worker" class="spec"><a href="https://github.com/WICG/BackgroundSync">Background Synchronisation</a></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>
</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>
</div>
<div id="ig-other-deliverables">
<h3>
Other Deliverables
</h3>
<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>
</div>
<div id="timeline">
<h3>Timeline</h3>
<ul>
<li>June 2017: First teleconference</li>
<li>August-September 2017: First face-to-face meeting</li>
<li>October 2017: Service Workers 1 Candidate Recommendation</li>
<li>October 2017: FPWD for Service Workers 2</li>
<li>2019: Service Workers 2</li>
<li>March 2019: Proposal for rechartering or closing the Working Group</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/2017/Process-20170301//#RecsWD" title="First Public Working Draft">FPWD</a>
and <a href="https://www.w3.org/2017/Process-20170301//#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/2017/Process-20170301//#WGCharter">W3C Process Document</a>:</p>
<div>
<h3 id="w3c-coordination">W3C Groups</h3>
<dl>
<dt><a href="https://www.w3.org/WebPlatform/WG/">Web Platform 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>
</div>
<div><h3 id="external-coordination">External Groups</h3>
<a href="http://ecma-international.org/memento/TC39.htm">TC39 - ECMAScript Standards Body</a></dt>
</div>
</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,
subject to contributors' 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/2017/Process-20170301//#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.
The meetings themselves may 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="">Service Workers Working Group home page.</a>
</p>
<p>
Working Group teleconferences will focus on discussion of particular issues,
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 subject to agreement to the terms of the
<a href="https://www.w3.org/Consortium/Patent-Policy/">W3C Patent Policy</a> contribute to this work.
</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/2017/Process-20170301//#Consensus"> W3C Process Document (section 3.3</a>).
For technical decisions, an editor or other participant typically 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>
If consensus is not achieved after careful consideration of the range of views presented
but a decision is necessary for timely progress, the Chairs may call for a vote,
in accordance with the <a href="https://www.w3.org/Consortium/Process/policies#Votes">W3C Process Document (Section 3.4, Votes)</a>
and the process for asynchronous resolution described in the following paragraphs
in which case they will record a decision along with any objections.
</p>
<p>
To afford asynchronous decisions and organizational deliberation, any resolution including
<a href="https://www.w3.org/2017/Process-20170301/#transition-reqs">requests for transition of document states</a> decisions
taken in a face-to-face meeting or teleconference will be considered provisional.
</p>
<p>
Any resolution taken in a face-to-face meeting or teleconference is to be considered <em>provisional</em>
until 10 (ten) working days after the publication of the resolutions in meeting minutes
on the working group's mailing list.
</p>
<p>
A call for consensus (CfC) will be issued for all resolutions not proposed at a teleconference or face to face meeting
with a response period of at least one week, based on the chair's evaluation of the group consensus on the issue.
</p>
<p>
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="http://w3.org/Consortium/Patent-Policy-20040205/">W3C Patent Policy</a>
(5 February 2004 Version). 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 Service Workers specification was originally chartered as a deliverable of the
<a href="https://www.w3.org/2008/webapps/">Web Applications Working Group</a> in its
<a href="https://www.w3.org/2014/06/webapps-charter.html#deliverables">charter for 2014-2016</a>. When that group was merged
into the <a href="https://www.w3.org/2015/10/webplatform-charter.html#deliverables">Web Platform Working Group</a>, the deliverable was maintained in its
<a href="http://www.w3.org/WebPlatform/WG/">first</a> and
<a href="https://www.w3.org/2016/11/webplatform-charter.html">second</a> charters.</p>
<p>The <a href="https://github.com/WICG/BackgroundSync">Background Synchronisation proposal</a> has been developed in the W3C's
<a href="https://wicg.io">Web Platform Incubator Group</a></p>
<p>This charter [proposal] brings the Service Worker specification to a new Working Group, and proposes the
Background Synchronization specification a W3C Recommendation-track deliverable, according to the
<a href="https://www.w3.org/2017/Process-20170301//#CharterReview">W3C Process Document (section 5.2.3)</a>.</p>
</section>
</section>
</main>
<hr />
<footer>
<address>
<i class="todo"><a href="mailto:">[team contact name]</a></i>
</address>
<p class="copyright">
<a href="https://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> ©
2017
<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="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>