-
Notifications
You must be signed in to change notification settings - Fork 15
/
webplat-wg.html
977 lines (943 loc) · 55.3 KB
/
webplat-wg.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
<!DOCTYPE html>
<html lang="en-US">
<head>
<meta content="text/html; charset=UTF-8" http-equiv="content-type">
<title>[PROPOSED] Web Platform Working Group Charter</title>
<link media="screen" type="text/css" href="https://www.w3.org/2005/10/w3cdoc.css"
rel="stylesheet">
<link href="https://www.w3.org/Guide/pubrules-style.css" type="text/css" rel="stylesheet">
<link href="https://www.w3.org/2006/02/charter-style.css" type="text/css" rel="stylesheet">
<style type="text/css">
body {
/* Layout */
max-width: 50em; /* limit line length to 50em for readability */
margin: 0 auto; /* center text within page */
padding: 1.6em 1.5em 2em 50px; /* assume 16px font size for downlevel clients */
padding: 1.6em 1.5em 2em calc(26px + 1.5em); /* leave space for status flag */
/* Typography */
line-height: 1.5;
font-family: sans-serif;
widows: 2;
orphans: 2;
word-wrap: break-word;
overflow-wrap: break-word;
hyphens: auto;
/* Colors */
color: black;
background: white top left fixed no-repeat;
background-size: 25px auto;
}
.comment
{
width: 90%;
border: 3px solid red;
padding: 6px;
clear: both;
}
.issue {border: 3px solid red; padding: 6px}
.issue::before {content: "@@ISSUE: "}
.helpneeded
{
color: red;
}
#navbar
{
font-size: small;
}
.complete
{
font-weight: bold;
}
</style>
</head>
<body>
<section id="template">
<ul id="navbar">
<li><a href="#scope">Scope</a></li>
<li><a href="#background">Background</a></li>
<li><a href="#deliverables">Deliverables</a></li>
<li><a href="#coordination">Dependencies and Liaisons</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 Working Group charter</a></li>
</ul>
<p><a href="https://www.w3.org/"><img src="https://www.w3.org/Icons/w3c_home" alt="W3C"
height="48" width="72"></a> </p>
<h1 id="title">[PROPOSED]<br>
Web Platform Working Group Charter</h1>
<p class="mission">The mission of the
<a href="https://www.w3.org/WebPlatform/WG/">Web Platform Working Group</a> is to continue
the
development of the <abbr title="HyperText Markup Language">HTML</abbr> language and provide
specifications that enable improved
client-side application development on the Web, including application programming interfaces
(APIs) for client-side development and
markup vocabularies for describing and controlling client-side application behavior.</p>
<!-- UNCOMMENT IF CHARTER IS ADOPTED
<section class="noprint"> <p class="join"><a
href="https://www.w3.org/2004/01/pp-impl/42538/join">Join the Web Platform Working
Group</a>.</p> </section>
-->
<p style="padding: 0.5ex; border: 1px solid green"> This proposed charter is available
on <a href="https://github.com/w3c/charter-html">GitHub</a>.
Feel free to raise <a href="https://github.com/w3c/charter-html/issues">issues</a>.
</p>
<table class="summary-table">
<tbody>
<tr id="Start">
<th rowspan="1" colspan="1">Start date</th>
<td rowspan="1" colspan="1">15 June 2017</td>
</tr>
<tr id="Duration">
<th>End date</th>
<td>30 September 2018</td>
</tr>
<tr>
<th>Confidentiality</th>
<td>Proceedings are <a
href="https://www.w3.org/Consortium/Process/#confidentiality-levels">Public</a></td>
</tr>
<tr>
<th>Chairs</th>
<td>Adrian Bateman, Charles McCathie Nevile, Léonie Watson</td>
</tr>
<tr>
<th>Team Contacts <br>
(FTE %: 100)</th>
<td>Yves Lafon, Xiaoqian Wu</td>
</tr>
<tr>
<th>Usual Meeting Schedule</th>
<td>Teleconferences: There are generally not regular teleconferences. <br>
Topic-specific calls <em>may</em> be held up to once per week if needed. <br>
Face-to-face: we will meet during the W3C's annual Technical Plenary week; up to 2
other F2F meetings may be scheduled for the
full group; Up to 4 meetings per year may be scheduled for subgroups working on
specific topics.<br>
IRC: active participants, particularly editors, regularly use the group's IRC
channel(s)</td>
</tr>
</tbody>
</table>
<section id="background">
<h2>Background</h2>
<p>The Web Platform Working Group was the result of merging the Web Applications Working
Group and the HTML Working Group in 2015,
with some deliverables moved to other groups. The work boundaries between the two Working
Groups had narrowed over the years,
given that it is difficult to introduce new HTML elements and attributes without looking
at their implications at the API level.</p>
<p>The initial experiment in merging the group for 12 months was followed by an 18 month
extension, removing some deliverables
considered unlikely to progress within that period, and including others with a specific
requirement that there is a prospect of
success before work will continue within the Working Group.</p>
<p>This proposed charter update adds some new deliverables, removes some to split the work
into a separate group and extends the
group by a further 6 months.</p>
</section>
<section id="scope">
<h2>Scope</h2>
<p>The group will:</p>
<ul>
<li>Continue the development of the HTML language, and associated APIs.</li>
<li>Ensure that developers can use Web technologies to build client-side applications that
rely on Web engines as application
run-time environments.</li>
<li>Provide generic and consistent interoperability and integration among all target
formats, such as HTML, CSS, and SVG.</li>
<li>Continue to define normative requirements for applications that process HTML
resources, including browsers and other
interactive user agents, authoring tools, content management tools, and conformance
checkers.</li>
<li>Ensure Web applications can work across a wide range of devices and among a broad
diversity of users, in particular addressing
issues of accessibility, device independence, internationalization, privacy, and
security.</li>
</ul>
<section>
<h3 id="success">Success Criteria</h3>
<p>The group will be considered successful if it produces</p>
<ul>
<li>Stable versions of specifications addressing the work items listed in the <a
href="#milestones">Milestones</a> section,
with normative conformance requirements for implementation,</li>
<li>A test suite for each deliverable, sufficiently broad to demonstrate
interoperability,</li>
<li>and Implementation reports for deliverables showing adoption,</li>
</ul>
<p>resulting in the ready availability of multiple, independent, interoperable
implementations of each deliverable, including in
browsers, authoring and validation tools, and usage on the Web.</p>
<p>If participants from fewer than three distinct browser-engine projects are
participating in the group, its charter should be
re-examined by the W3C.</p>
</section>
</section>
<section class="deliverables">
<h2 id="deliverables">Deliverables</h2>
<h3 id="rec-track">Recommendation-Track Deliverables</h3>
<p>The working group will work on the following W3C specifications:</p>
<dl>
<dt id="db"><a href="https://www.w3.org/2008/webapps/wiki/Database">Database and Offline
Application APIs</a></dt>
<dd>A set of objects and interfaces for client-side database functionality. For more
details, see the Web Platform WG <a
href="https://www.w3.org/2008/webapps/wiki/Database">Database
API page</a>. The following Database APIs are deliverables under this charter:
<dl>
<dt><a href="#1321">Indexed Database API (2nd
Edition)</a> - <a href="https://w3c.github.io/IndexDB/">Editors' Copy</a></dt>
<dd>An API for a database of records holding simple values and hierarchical
objects</dd>
</dl>
</dd>
<dt id="dom">Document Object Model (DOM)</dt>
<dd>A set of specifications defining objects and interfaces for interaction with a
document's tree model. These deliverables
include:
<dl>
<dt id="domcore">An update for <a href="#1357">DOM4</a></dt>
<dd>DOM defines a platform-neutral model for events and node trees.</dd>
<dt id="innerhtml"><a href="#952">DOM Parsing and
Serialization</a></dt>
<dd>Parsing markup into a DOM, and serialize for export, an HTML or XML fragment or
document.</dd>
<dt><a href="http://wicg.github.io/IntersectionObserver/">Intersection
Observers</a></dt>
<dd>A specification that gives authors information about the visibility of particular
elements</dd>
<dt id="ui-events"><a href="#194">UI Events</a> - <a
href="https://w3c.github.io/uievents/">Editors' Copy</a></dt>
<dd>Events typically implemented by interactive user agents for user interaction such
as mouse and keyboard input.</dd>
<dt id="dom-l3-code"><a href="#1180">UIEvents
KeyboardEvent code Values</a> - <a
href="https://w3c.github.io/uievents-code/">Editors' Copy</a></dt>
<dd>Identifying the physical key being pressed by the user.</dd>
<dt id="dom-l3-key"><a href="#1181">UIEvents
KeyboardEvent key Values</a> - <a href="https://w3c.github.io/uievents-key/">Editors'
Copy</a></dt>
<dd>Information about the character generated by key events.</dd>
</dl>
</dd>
<dt id="Editing">Editing APIs</dt>
<dd>
<dl>
<dt id="clipops"><a href="#551">Clipboard API and
events</a> - <a href="https://w3c.github.io/clipboard-apis/">Editors' Copy</a></dt>
<dd>Expose common clipboard operations such as cut, copy and paste to Web
Applications.</dd>
<dt id="selection"><a href="#1195">Selection
API</a> - <a href="https://w3c.github.io/selection-api/">Editors' Copy</a></dt>
<dd>APIs for selection, which allows users and authors to select a portion of a
document or specify a point of interest for
copy, paste, and other editing operations.</dd>
<dt><a href="http://garykac.github.io/staticrange/">Static Range</a></dt>
<dd>A utility API defining a simple range, for optimized performance</dd>
<dt><a href="#1323">Input Events</a> - <a
href="https://w3c.github.io/input-events/">Editors' Copy</a></dt>
<dd>A specification defining additions to events for text and related input to allow
for the monitoring and manipulation of
default browser behavior in the context of text editor applications and other
applications that deal with text input and
text formatting.</dd>
<dt><a
href="https://w3c.github.io/editing/contentEditable.html">contentEditable</a> - <a href="http://w3c.github.io/editing/contentEditable.html">Editors' Copy</a></dt>
<dd>A specification defining new values for the <code>contentEditable</code>
attribute.</dd>
<dt><a href="https://w3c.github.io/editing/execCommand.html">execCommand</a></dt>
<dd>Defines the behavior of the editing commands that can be executed with
<code>execCommand</code>.</dd>
</dl>
</dd>
<dt id="file-api"><a title="File API" href="#751">File
API</a> - <a href="https://w3c.github.io/FileAPI/">Editors' Copy</a></dt>
<dd>An API that enables Web applications to select file objects and access their data.
This replaces the File Upload
specification.</dd>
<dt id="gamepad"><a href="#979">Gamepad</a> - <a
href="https://w3c.github.io/gamepad/gamepad.html">Editors' Copy</a></dt>
<dd>APIs that allow Web applications to directly act on gamepad data.</dd>
<dt><a href="https://www.w3.org/TR/html/">HTML</a></dt>
<dd>Specifications to define the HTML language, HTML-specific APIs for interacting with
in-memory representations of resources
that use the HTML language, and to define normative requirements for browsers and other
user agents which process HTML
resources.
<dl>
<dt><a href="#981">HTML</a></dt>
<dd>The core language of the World Wide Web: the Hypertext Markup Language (HTML). The
HTML specification should be
progressively modularized into separate documents or <a
href="https://www.w3.org/TR/html5/introduction.html#extensibility">extension
specifications</a>. Note that many other Working Groups define extensions to HTML.
These should be referenced from the <a
href="https://w3c.github.io/html-extensions/">HTML Extension</a>
specification</dd>
<dt><a href="#1228">HTML Accessibility API
Mappings 1.0</a> - <a href="https://w3c.github.io/aria/html-aam/html-aam.html">Editors'
Copy</a></dt>
<dd>How to map HTML elements and attributes to platform accessibility APIs.</dd>
<dt><a href="#1233">ARIA in HTML</a></dt>
<dd>Describing the use of ARIA attributes on HTML elements.</dd>
<dt><a href="#844">Microdata</a></dt>
<dd>Widely-used attributes on HTML elements to provide metadata, e.g. as Schema.org or
Dublin Core.</dd>
</dl>
</dd>
<dt id="manifest"><a href="#1138">Manifest for Web
applications</a> - <a href="https://w3c.github.io/manifest/">Editors' Copy</a></dt>
<dd>A JSON-based manifest, to provide metadata about a web application.</dd>
<dt id="network">Network</dt>
<dd>Specifications that allow network communications:
<dl>
<dt id="web-sockets"><a title="Web Sockets API"
href="#792">Web Sockets API</a> - <a title="Web Sockets API"
href="https://github.com/w3c/websockets/">Editors' Copy</a></dt>
<dd>An API to use the Web Sockets protocol for two-way communication with a remote
host.</dd>
</dl>
</dd>
<dt id="pointer-lock"><a href="#1345">Pointer Lock (2nd
Edition)</a> - <a href="https://w3c.github.io/pointerlock/">Editors' Copy</a></dt>
<dd>Defines an API that provides scripted access to raw mouse movement data while locking
the target of mouse events to a single
element and removing the cursor from view.</dd>
<dt id="push"><a href="#1000">Push API</a> - <a
href="https://w3c.github.io/push-api/">Editors' Copy</a></dt>
<dd>An API that provides web applications scripted access to server-sent
notifications.</dd>
<dt id="screen-orientation"><a href="#1003">Screen
Orientation API</a> - <a href="https://w3c.github.io/screen-orientation/">Editors'
Copy</a></dt>
<dd>An API to enable reading or locking view orientation, and notification of view
orientation state changes.</dd>
<dt id="webcomponents">Web Components</dt>
<dd>Adding custom elements to a document, with well-defined behavior and rendering.
<dl>
<dt><a href="#1038">Custom Elements</a>
- <a href="https://w3c.github.io/webcomponents/spec/custom/">Editors' Copy</a></dt>
<dd>Define and use new types of DOM elements in a document.</dd>
<dt><a href="#1004">Shadow DOM</a>
- <a href="https://w3c.github.io/webcomponents/spec/shadow/">Editors' Copy</a></dt>
<dd>Functional boundaries between DOM trees and how these trees interact with each
other within a document, enabling better
functional encapsulation within the DOM.</dd>
</dl>
</dd>
<dt id="webidl"><a href="https://heycam.github.io/webidl/">Web Interface Definition
Language (Web IDL)</a></dt>
<dd>Language bindings and types for Web interface descriptions.</dd>
<dt id="web-workers"><a title="Web Workers" href="#797">Web
Workers</a> - <a href="https://w3c.github.io/workers/">Editors' Copy</a></dt>
<dd>An API that allows Web application authors to spawn background workers running scripts
in parallel to their main page,
allowing for thread-like operation with message-passing as the coordination
mechanism.</dd>
</dl>
<h4>Potential deliverables</h4>
<p>The following documents have been identified as potential Recommendation Track
deliverables, if there is consensus in the Working Group that they are
<a href="https://wicg.github.io/admin/intent-to-migrate.html">ready to become Recommendation-track</a>.</p>
<dl>
<dt><a href="https://www.w3.org/TR/2dcontext/">HTML Canvas 2D Context</a></dt>
<dd>An API for the 2D Context of the HTML canvas element.</dd>
<dt><a href="https://w3c.github.io/ime-api/">Input Method (IME) API</a></dt>
<dd>An API that provides access to a (native) input method editor.</dd>
<dt id="file-system-2"><a href="https://w3c.github.io/filesystem-api/">FileSystem
API</a></dt>
<dd>A local sandboxed file system API exposed only to Web Applications.</dd>
<dt id="packaging"><a href="https://w3ctag.github.io/packaging-on-the-web/">Packaging on
the Web</a></dt>
<dd>Defines an approach for creating packages of files for use on the web.</dd>
<dt><a href="https://w3c.github.io/quota-api/">Quota Management API</a></dt>
<dd>An API for managing the amount of storage space (short- or long-term) available for an
application to use e.g. in localStorage.</dd>
<dt><a href="https://w3c.github.io/webcomponents/spec/imports/">HTML Imports</a></dt>
<dd>A way to include and reuse HTML documents in another HTML document.</dd>
</dl>
<p><em>Note:</em> The list of specifications above were Recommendation Track documents in
the previous charter. They are not statements about incubation success,
but examples of the incubation process applied to the list of deliverables in the
previous charter.</p>
<p>Each specification should detail any known security implications for implementers, Web
authors, and end users.</p>
<p>The Web Platform WG will actively seek security, privacy, internationalization,
accessibility and architectural review on all its specifications.</p>
<p>If a specification reaches Recommendation status the working group may work on, and
deliver an updated version of the specification under this charter.
Specifications may be moved to Recommendation and a subsequent version begun
to facilitate the progress of other work which depends on a stable reference.</p>
<p>The Working Group will not adopt new proposals until they have matured through the <a
href="https://wicg.io/">Web Platform Incubator Community Group</a> or a similar incubation phase.
If the Working Group decides to add new Recommendation-track deliverables
then it will recharter with changes to change its deliverables.</p>
<p>For current information on the list of deliverables and their status see the Web Platform
WG <a href="https://www.w3.org/WebPlatform/WG/PubStatus">Publication Status</a> page.</p>
<h4 id="maintenance">Specification Maintenance</h4>
<p>The working group will maintain errata and publish revisions, as necessary, for the
following W3C Recommendations:</p>
<ul>
<li id="dom">DOM specifications</li>
<li id="progress"><a href="https://www.w3.org/TR/progress-events/">Progress
Events</a></li>
<li id="sse"><a href="https://www.w3.org/TR/eventsource/">Server-sent Events</a></li>
<li id="view-mode"><a href="https://www.w3.org/TR/view-mode/">view-mode Media
Feature</a></li>
<li id="webstorage"><a href="https://www.w3.org/TR/webstorage/">Web Storage</a></li>
<li id="webmessaging"><a href="https://www.w3.org/TR/webmessaging/">Web Messaging</a></li>
</ul>
<h3 id="other-deliverables">Other Deliverables</h3>
<p>Other non-normative documents may be created such as:</p>
<section id="ig-other-deliverables">
<ul>
<li>Test suites for each specification</li>
<li>Primers for each specification</li>
<li>Requirements documents for new specifications</li>
<li>Non-normative schemas for language formats</li>
<li>Non-normative group notes</li>
</ul>
<p>A comprehensive test suite for all features of a specification is necessary to ensure
the specification's robustness,
consistency, and implementability, and to promote interoperability between User Agents.
Therefore, each specification must have
a companion test suite, which should be completed before transition to Candidate
Recommendation, and must be completed, with an
implementation report, before transition from Candidate Recommendation to Proposed
Recommendation. Additional tests may be added
to the test suite at any stage of the Recommendation track, and the maintenance of a
implementation report is encouraged. </p>
</section>
<section>
<h3 id="milestones">Milestones</h3>
<p>The group's <a href="https://www.w3.org/WebPlatform/WG/PubStatus">Publication Status</a>
document provides current data about
all of the group's specifications. Although the group expects all of its active
deliverables to progress during this charter
period, the charter does not include detailed <em>milestone</em> data for each
specification because such data is speculative and
easily becomes out of date. The Working Group does expect the following to occur:</p>
<ul>
<li>HTML 5.2 Recommendation in Q4 2017</li>
<li>HTML 5.3 First Public Working Draft in Q3 2017</li>
<li>IndexedDB version 2 Candidate Recommendation in Q3 2017</li>
<li>IndexedDB version 3 First Public Working Draft in Q3 2017</li>
<li>Web Sockets: Recommendation expected in 2017</li>
<li>DOM Parsing and Serialization: Recommendation expected in 2017</li>
<li>DOM 4.1 Recommendation expected in 2017</li>
<li>Microdata: Recommendation expected in late 2017</li>
</ul>
</section>
</section>
<section class="dependencies">
<h2 id="coordination">Dependencies and Liaisons</h2>
<p>HTML depends on, and is depended on by, many specifications. Many specifications in many
Working Groups depend on WebIDL. Web
Sockets depends on work in the <a
href="http://www.ietf.org/dyn/wg/charter/hybi-charter.html">IETF's HyBi Working Group</a>.
</p>
<p>This working group depends on review of aspects such as accessibility, architectural
considerations, internationalisation,
security, and privacy in its deliverables.</p>
<p>The Web Platform Working Group will keep contact with and where applicable request review
from at least the following:</p>
<dl>
<dt><a href="https://www.w3.org/WAI/APA">Accessible Platform Architectures Working
Group</a></dt>
<dd>This Group ensures W3C specifications provide support for accessibility to people with
disabilities.</dd>
<dt><a href="https://www.w3.org/WAI/ARIA">Accessible Rich Internet Applications Working
Group</a></dt>
<dd>WAI-ARIA, the Accessible Rich Internet Applications Suite, defines a way to make Web
content and Web applications more
accessible to people with disabilities and is integrated into HTML to improve the
accessibility and interoperability of web
content and applications.</dd>
<dt><a href="https://www.w3.org/testing/browser/" id="browser-testing">Browser Testing and
Tools Working Group</a></dt>
<dd>This group's Web Driver specification is of interest to the Web Platform WG.</dd>
<dt><a href="https://www.w3.org/Style/Group/" id="css">Cascading Style Sheets Working
Group</a></dt>
<dd>To collaborate on CSS-related aspects of specifications such as Shadow DOM.</dd>
<dt><a href="https://www.w3.org/2009/dap/" id="dap">Device and Sensors Working
Group</a></dt>
<dd>To coordinate regarding APIs for device services.</dd>
<dt><a href="https://www.w3.org/2017/04/publ-wg-charter/#deliverables">Digital Publishing Working Group</a></dt>
<dd>This group has a core interest in the manifest specification,
and its scope includes a packaging deliverable.</dd>
<dt><a href="https://www.w3.org/International/core/">Internationalization Core Working
Group</a></dt>
<dd>This group provides advice or review to ensure that specifications meet the needs of
an international Web.</dd>
<dt><a href="https://www.w3.org/2012/pointerevents/">Pointer Events Working Group</a></dt>
<dd>This group creates DOM extension specifications and is interested in DOM Level 3
Events and UI Events.</dd>
<dt><a href="https://www.w3.org/Privacy/">Privacy Interest Group</a> (PING)</dt>
<dd>The Web Platform WG will request review of specifications from this group. </dd>
<dt><a href="https://www.w3.org/Graphics/SVG" id="svg">SVG (Scalable Vector Graphics)
Working Group</a></dt>
<dd>To help ensure SVG requirements for the Web Platform WG's deliverables are met. The
HTML markup language supports embedding
SVG content and provides support for the Canvas 2D Context API.</dd>
<dt><a href="https://www.w3.org/2001/tag/">Technical Architecture Group</a></dt>
<dd>The Web Platform WG will ask the Technical Architecture Group to review
specifications.</dd>
<dt><a href="https://www.w3.org/2011/webtv/">Media and Entertainment Interest Group</a></dt>
<dd>This Group may review existing work, as well as the relationship between services on
the Web and media services, and identify
requirements and potential solutions to ensure that the Web will function well with
media. </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>
<dt><a href="https://www.w3.org/2010/webperf/">Web Performance Working Group</a></dt>
<dd>Many of their specifications extend Web Platform WG deliverables.</dd>
<dt><a href="https://www.w3.org/community/wicg/">Web Platform Incubator Community
Group</a></dt>
<dd>This group provides a venue for proposing, incubating and discussing new web platform
features to prepare them for
standardisation, often in the Web Platform WG.</dd>
<dt><a href="https://www.w3.org/2011/04/webrtc/">Web Real-Time Communications Working
Group</a></dt>
<dd>This group creates API specifications for Real-Time Communications in Web
browsers.</dd>
<dt><a href="https://www.w3.org/Security/wiki/IG">Web Security Interest Group</a></dt>
<dd>The Web Platform WG will request review of specifications from this group.</dd>
</dl>
<section>
<h3 id="external-groups">External Groups</h3>
<p>The Working Group may also collaborate with: </p>
<dl>
<dt><a href="http://cta.tech/WAVE">Consumer Technology Association (CTA) WAVE project</a></dt>
<dd>The CTA WAVE project aims to improve the way internet delivered video is consumed and distributed, referencing the HTML5 standard in the process. As the Web Platform Working Group develops the HTML specification, it should liaise with the CTA WAVE project.</dd>
<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
Platform 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. A close relationship with the
IETF HTTP work is crucial to ensuring the good design, deployment, and success of
protocol-based APIs such as CORS and Web
Sockets. This Working Group will rely upon review and parallel progress of associated
specifications, and will keep pace with
the <a href="https://datatracker.ietf.org/wg/httpbis/documents/">IETF's HTTPbis</a>
group' work, conditional upon steady
progress. The working group may also liaise with the IETFs security work, either
directly or through its liaison with the
W3C's Web Application Security Working Group. </dd>
<dt><a href="https://whatwg.org/">WHATWG</a></dt>
<dd>The Web Platform WG and the WHAT WG both produce versions of the HTML and DOM
specifications.
The Web Platform WG works on these specifications for many reasons, including:<ul>
<li>The specifications are protected under the W3C Patent Policy,
ensuring that HTML and DOM remain royalty free for use by implementors and
authors;</li>
<li>The specifications are developed with contributions from a broad range of
stakeholders
including implementors and authors,
as well as specialists in accessibility, internationalisation, privacy, and
security;</li>
<li>The specifications are produced by a globally recognised standards organization,
with a governance model that is designed to find consensus
amongst the many diverse constituents of the web platform.</li></ul>
Based on these considerations, the Web Platform WG exercises independent editorial
control over these specifications. The WG nonetheless endeavours to minimize
differences between the WHAT WG and W3C versions that affect
interoperability.</dd>
</dl>
</section>
</section>
<section class="participation">
<h2 id="participation">Participation</h2>
<p>To be successful, the Web Platform Working Group is expected to have 10 or more active
participants for its duration, and to have
the participation of industry leaders in fields relevant to the specifications it
produces.</p>
<p>If participants from fewer than three distinct browser-engine projects are participating
in the group, its charter should be
re-examined by the W3C.</p>
<p>The Chairs, specification Editors and test Facilitators are expected to contribute one to
two days per week towards the Working
Group. There is no minimum requirement for other Participants.</p>
</section>
<section class="communication">
<h2 id="communication">Communication</h2>
<p>The group's <a
href="https://github.com/w3c/WebPlatformWG/blob/gh-pages/WorkMode.md">working mode</a> is
generally not to hold
plenary teleconferences, but to meet face to face at the TPAC for both specific topics and
"in plenary". It holds spec- or
topic-specific meetings from time to time, and certain specifications are developed with
regular teleconferences. Note the <a href="#decisions">Decision
Policy</a> below with regards to meetings. </p>
<p>The Working Group conducts its work primarily through <a
href="https://www.w3.org/WebPlatform/WG/PubStatus">GitHub repositories</a>.
</p>
<p>The Group uses mailing lists. Subscription to these lists is open to the public, subject
to W3C norms of behavior. </p>
<p>Up-to-date information about the group is available from the <a
href="https://www.w3.org/WebPlatform/WG/">Web Platform Working
Group home page</a>.</p>
</section>
<section class="decisions">
<h2 id="decisions">Decision Policy</h2>
<p>As required by the W3C Process Document (<a
href="https://www.w3.org/Consortium/Process/policies#Consensus">section 3.3</a>),
this group will seek to make decisions when there is consensus and with due process. The
expectation is that, an editor or other
participant makes an initial proposal, which is refined in discussion with members of the
group and other reviewers, and consensus
emerges with little formal voting being required.</p>
<p>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 put a question out for voting within the group to allow for
asynchronous participation, using the
mechanism noted in the group's <a
href="https://github.com/w3c/WebPlatformWG/blob/gh-pages/WorkMode.md">Work Mode</a>
documents,
and record a decision, along with any objections. The matter should then be considered
resolved unless and until new information
becomes available.</p>
<p><strong>Any resolution taken in a face-to-face meeting or teleconference is to be
considered provisional until 10 (ten) working
days after the publication of the resolutions in meeting minutes. When the meeting minutes are sent to the appropriate working group mailing list as described
in the <a href="https://github.com/w3c/WebPlatformWG/blob/gh-pages/WorkMode.md">Work
Mode</a> document, the presence of formal resolutions will be clearly indicated in the email. If no objections are
raised on the mailing list within that time, the resolution will be considered to have
consensus as a resolution of the Working
Group.</strong></p>
<p>This charter is written in accordance with <a
href="https://www.w3.org/Consortium/Process/policies#Votes">Section 3.4, Votes</a>
of the W3C Process Document and includes no voting procedures beyond what the Process
Document requires. </p>
</section>
<section class="patent">
<h2 id="patentpolicy">Patent Policy </h2>
<p>This Working Group operates under the <a
href="https://www.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. </p>
<p>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 class="licensing">
<h2 id="licensing">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 class="patent">
<h2 id="about">About this Charter</h2>
<p>This charter for the Web Platform Working Group has been created according to <a
href="https://www.w3.org/Consortium/Process/groups#GAGeneral">section
5</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>
<section class="detailed-deliverables">
<h2 id="detailed-deliverables">Detailed list of Deliverables</h2>
<dl>
<dt id="1321" class="spec"><a href="https://www.w3.org/TR/IndexedDB-2/"
rel="versionof">Indexed Database API 2.0</a>
<br>Latest publication: <a href="https://www.w3.org/TR/2017/WD-IndexedDB-2-20170313/">13
March 2017</a></dt>
<dd>Reference Draft: <a
href="https://www.w3.org/TR/2016/WD-IndexedDB-2-20160818/">https://www.w3.org/TR/2016/WD-IndexedDB-2-20160818/</a><br>
associated <a href="https://lists.w3.org/Archives/Member/member-cfe/2016Aug/0003.html">Call
for Exclusion</a> on 18 August 2016 ended on 15 January 2017
<br>Produced under
<a href="https://www.w3.org/2015/10/webplatform-charter.html">Web Platform Working Group charter</a></dd>
<dt id=1357 class='spec'><a href='https://www.w3.org/TR/dom41/' rel='versionof'>W3C DOM 4.1</a>
<br>Latest publication: <a href='https://www.w3.org/TR/2017/WD-dom41-20170420/'>20 April
2017</a></dt>
<dd>Reference Draft:
<a
href='https://www.w3.org/TR/2017/WD-dom41-20170321/'>https://www.w3.org/TR/2017/WD-dom41-20170321/</a><br>
associated <a href='https://lists.w3.org/Archives/Member/member-cfe/2017Mar/0002.html'> Call for
Exclusion</a> on 22 March 2017
<br><i>Exclusion opportunity will end on 18 August 2017</i><br>Produced under
<a href="https://www.w3.org/2016/11/webplatform-charter.html">Web Platform Working Group charter</a></dd>
<dt id=952 class='spec'><a href='https://www.w3.org/TR/DOM-Parsing/' rel='versionof'>DOM Parsing and
Serialization</a>
<br>Latest publication: <a href='https://www.w3.org/TR/2016/WD-DOM-Parsing-20160517/'>17 May
2016</a></dt>
<dd>Reference Draft:
<a
href='https://www.w3.org/TR/2016/WD-DOM-Parsing-20160517/'>https://www.w3.org/TR/2016/WD-DOM-Parsing-20160517/</a><br>
associated <a href='https://lists.w3.org/Archives/Member/member-cfe/2014May/0005.html'> Call for
Exclusion</a> on 01 May 2014
ended on 30 June 2014<br>Produced under
<a href="https://www.w3.org/2012/webapps/charter/">Web Applications Working Group charter</a></dd>
<dt id=194 class='spec'><a href='https://www.w3.org/TR/uievents/' rel='versionof'>UI Events</a>
<br>Latest publication: <a href='https://www.w3.org/TR/2016/WD-uievents-20160804/'>04 August
2016</a></dt>
<dd>Reference Draft:
<a
href='https://www.w3.org/TR/2013/WD-uievents-20130725/'>https://www.w3.org/TR/2013/WD-uievents-20130725/</a><br>
associated <a href='https://lists.w3.org/Archives/Member/member-cfe/2013Jul/0008.html'> Call for
Exclusion</a> on 25 July 2013
ended on 22 December 2013<br>Produced under
<a href="https://www.w3.org/2012/webapps/charter/">Web Applications Working Group charter</a></dd>
<dt id=1180 class='spec'><a href='https://www.w3.org/TR/uievents-code/' rel='versionof'>UI Events
KeyboardEvent code Values</a>
<br>Latest publication: <a href='https://www.w3.org/TR/2016/WD-uievents-code-20161024/'>24 October
2016</a></dt>
<dd>Reference Draft:
<a
href='https://www.w3.org/TR/2015/WD-uievents-code-20151215/'>https://www.w3.org/TR/2015/WD-uievents-code-20151215/</a><br>
associated <a href='https://lists.w3.org/Archives/Member/member-cfe/2014Jun/0005.html'> Call for
Exclusion</a> on 12 June 2014
ended on 09 November 2014<br>Produced under
<a href="https://www.w3.org/2014/06/webapps-charter.html">Web Applications Working Group charter</a></dd>
<dt id=1181 class='spec'><a href='https://www.w3.org/TR/uievents-key/' rel='versionof'>UI Events
KeyboardEvent key Values</a>
<br>Latest publication: <a href='https://www.w3.org/TR/2016/WD-uievents-key-20161024/'>24 October
2016</a></dt>
<dd>Reference Draft:
<a
href='https://www.w3.org/TR/2015/WD-uievents-key-20151215/'>https://www.w3.org/TR/2015/WD-uievents-key-20151215/</a><br>
associated <a href='https://www.w3.org/2004/01/pp-impl/42538/admin'> Call for Exclusion</a> on 12
June 2014
ended on 09 November 2014<br>Produced under
<a href="https://www.w3.org/2014/06/webapps-charter.html">Web Applications Working Group charter</a></dd>
<dt id=551 class='spec'><a href='https://www.w3.org/TR/clipboard-apis/' rel='versionof'>Clipboard
API and events</a>
<br>Latest publication: <a href='https://www.w3.org/TR/2016/WD-clipboard-apis-20161213/'>13
December 2016</a></dt>
<dd>Reference Draft:
<a
href='https://www.w3.org/TR/2015/WD-clipboard-apis-20151215/'>https://www.w3.org/TR/2015/WD-clipboard-apis-20151215/</a><br>
associated <a href='https://lists.w3.org/Archives/Member/member-webapi/2006Nov/0009.html'> Call for
Exclusion</a> on 16 November 2006
ended on 14 April 2007<br>Produced under
<a href="https://www.w3.org/2006/webapi/admin/charter">Web API Working Group charter</a></dd>
<dt id=1195 class='spec'><a href='https://www.w3.org/TR/selection-api/' rel='versionof'>Selection
API</a>
<br>Latest publication: <a href='https://www.w3.org/TR/2017/WD-selection-api-20170509/'>09 May
2017</a></dt>
<dd>Reference Draft:
<a
href='https://www.w3.org/TR/2015/WD-selection-api-20151124/'>https://www.w3.org/TR/2015/WD-selection-api-20151124/</a><br>
associated <a href='https://lists.w3.org/Archives/Member/member-cfe/2014Oct/0002.html'> Call for
Exclusion</a> on 07 October 2014
ended on 06 March 2015<br>Produced under
<a href="https://www.w3.org/2014/06/webapps-charter.html">Web Applications Working Group charter</a></dd>
<dt id=1323 class='spec'><a href='https://www.w3.org/TR/input-events-1/' rel='versionof'>Input
Events Level 1</a>
<br>Latest publication: <a href='https://www.w3.org/TR/2017/WD-input-events-2-20170321/'>21 March
2017</a></dt>
<dd>Reference Draft:
<a
href='https://www.w3.org/TR/2016/WD-input-events-20160830/'>https://www.w3.org/TR/2016/WD-input-events-20160830/</a><br>
associated <a href='https://lists.w3.org/Archives/Member/member-cfe/2016Aug/0006.html'> Call for
Exclusion</a> on 30 August 2016
ended on 27 January 2017<br>Produced under
<a href="https://www.w3.org/2015/10/webplatform-charter.html">Web Platform Working Group charter</a></dd>
<dt id=751 class='spec'><a href='https://www.w3.org/TR/FileAPI/' rel='versionof'>File API</a>
<br>Latest publication: <a href='https://www.w3.org/TR/2015/WD-FileAPI-20150421/'>21 April
2015</a></dt>
<dd>Reference Draft:
<a
href='https://www.w3.org/TR/2015/WD-FileAPI-20150421/'>https://www.w3.org/TR/2015/WD-FileAPI-20150421/</a><br>
<dt id=979 class='spec'><a href='https://www.w3.org/TR/gamepad/' rel='versionof'>Gamepad</a>
<br>Latest publication: <a href='https://www.w3.org/TR/2017/WD-gamepad-20170125/'>25 January
2017</a></dt>
<dd>Reference Draft:
<a
href='https://www.w3.org/TR/2015/WD-gamepad-20151215/'>https://www.w3.org/TR/2015/WD-gamepad-20151215/</a><br>
associated <a href='https://lists.w3.org/Archives/Member/member-cfe/2012May/0010.html'> Call for
Exclusion</a> on 29 May 2012
ended on 26 October 2012<br>Produced under
<a href="https://www.w3.org/2010/webapps/charter/">Web Applications Working Group charter</a></dd>
<dt id=981 class='spec'><a href='https://www.w3.org/TR/html51/' rel='versionof'>HTML 5.1</a>
<br>Latest publication: <a href='https://www.w3.org/TR/2016/REC-html51-20161101/'>01 November
2016</a></dt>
<dd>Reference Draft:
<a
href='https://www.w3.org/TR/2016/PR-html51-20160915/'>https://www.w3.org/TR/2016/PR-html51-20160915/</a><br>
associated <a href='https://lists.w3.org/Archives/Member/member-cfe/2016Jun/0002.html'> Call for
Exclusion</a> on 21 June 2016
ended on 20 August 2016<br>Produced under
<a href="https://www.w3.org/2015/10/webplatform-charter.html">Web Platform Working Group charter</a></dd>
<dt id=1320 class='spec'><a href='https://www.w3.org/TR/html52/' rel='versionof'>HTML 5.2</a>
<br>Latest publication: <a href='https://www.w3.org/TR/2017/WD-html52-20170509/'>09 May
2017</a></dt>
<dd>Reference Draft:
<a
href='https://www.w3.org/TR/2016/WD-html52-20160818/'>https://www.w3.org/TR/2016/WD-html52-20160818/</a><br>
associated <a href='https://lists.w3.org/Archives/Member/member-cfe/2016Aug/0003.html'> Call for
Exclusion</a> on 18 August 2016
ended on 15 January 2017<br>Produced under
<a href="https://www.w3.org/2015/10/webplatform-charter.html">Web Platform Working Group charter</a></dd>
<dt id=1228 class='spec'><a href='https://www.w3.org/TR/html-aam-1.0/' rel='versionof'>HTML
Accessibility API Mappings 1.0</a>
<br>Latest publication: <a href='https://www.w3.org/TR/2017/WD-html-aam-1.0-20170510/'>10 May
2017</a></dt>
<dd>Reference Draft:
<a
href='https://www.w3.org/TR/2015/WD-html-aam-1.0-20150407/'>https://www.w3.org/TR/2015/WD-html-aam-1.0-20150407/</a><br>
associated <a href='https://lists.w3.org/Archives/Member/member-cfe/2015Apr/0000.html'> Call for
Exclusion</a> on 09 April 2015
ended on 04 September 2015<br>Produced under
<a href="https://www.w3.org/WAI/PF/charter201006">WAI PF Working Group charter</a></dd>
<dt id=1233 class='spec'><a href='https://www.w3.org/TR/html-aria/' rel='versionof'>ARIA in HTML</a>
<br />Also developed by Web Platform Working Group.Web Platform Working Group.<br>Latest
publication: <a href='https://www.w3.org/TR/2017/WD-html-aria-20170323/'>23 March 2017</a></dt>
<dd>Reference Draft:
<a
href='https://www.w3.org/TR/2015/WD-html-aria-20150414/'>https://www.w3.org/TR/2015/WD-html-aria-20150414/</a><br>
associated <a href='https://lists.w3.org/Archives/Member/member-cfe/2015Apr/0005.html'> Call for
Exclusion</a> on 14 April 2015
ended on 11 September 2015<br>Produced under
<a href="https://www.w3.org/2013/09/html-charter">HTML Working Group charter</a></dd>
<dt id=844 class='spec'><a href='https://www.w3.org/TR/microdata/' rel='versionof'>HTML
Microdata</a>
<br>Latest publication: <a href='https://www.w3.org/TR/2017/WD-microdata-20170504/'>04 May
2017</a></dt>
<dd>Reference Draft:
<a
href='https://www.w3.org/TR/2017/WD-microdata-20170504/'>https://www.w3.org/TR/2017/WD-microdata-20170504/</a><br>
associated <a href='https://lists.w3.org/Archives/Member/member-cfe/2017May/0001.html'> Call for
Exclusion</a> on 04 May 2017
<br><i>Exclusion opportunity will end on 30 September 2017</i><br>Produced under Working Group
Charter: <a href="https://www.w3.org/2016/11/webplatform-charter.html">Web Platform Working Group charter</a></dd>
<dt id=1138 class='spec'><a href='https://www.w3.org/TR/appmanifest/' rel='versionof'>Web App
Manifest</a>
<br>Latest publication: <a href='https://www.w3.org/TR/2017/WD-appmanifest-20170510/'>10 May
2017</a></dt>
<dd>Reference Draft:
<a
href='https://www.w3.org/TR/2015/WD-appmanifest-20151124/'>https://www.w3.org/TR/2015/WD-appmanifest-20151124/</a><br>
associated <a href='https://lists.w3.org/Archives/Member/member-cfe/2013Dec/0004.html'> Call for
Exclusion</a> on 17 December 2013
ended on 16 May 2014<br>Produced under
<a href="https://www.w3.org/2012/webapps/charter/">Web Applications Working Group charter</a></dd>
<dt id=792 class='spec'><a href='https://www.w3.org/TR/websockets/' rel='versionof'>The WebSocket
API</a>
<br>Latest publication: <a href='https://www.w3.org/TR/2012/CR-websockets-20120920/'>20 September
2012</a></dt>
<dd>Reference Draft:
<a
href='https://www.w3.org/TR/2012/WD-websockets-20120809/'>https://www.w3.org/TR/2012/WD-websockets-20120809/</a><br>
associated <a href='https://lists.w3.org/Archives/Member/member-cfe/2012Aug/0005.html'> Call for
Exclusion</a> on 09 August 2012
ended on 08 October 2012<br>Produced under
<a href="https://www.w3.org/2012/webapps/charter/">Web Applications Working Group charter</a></dd>
<dt id=1345 class='spec'><a href='https://www.w3.org/TR/pointerlock-2/' rel='versionof'>Pointer Lock
2.0</a>
<br>Latest publication: <a href='https://www.w3.org/TR/2016/WD-pointerlock-2-20161122/'>22 November
2016</a></dt>
<dd>Reference Draft:
<a
href='https://www.w3.org/TR/2016/WD-pointerlock-2-20161122/'>https://www.w3.org/TR/2016/WD-pointerlock-2-20161122/</a><br>
associated <a href='https://lists.w3.org/Archives/Member/member-cfe/2016Nov/0010.html'> Call for
Exclusion</a> on 22 November 2016
ended on 21 April 2017<br>Produced under
<a href="https://www.w3.org/2016/11/webplatform-charter.html">Web Platform Working Group charter</a></dd>
<dt id=1000 class='spec'><a href='https://www.w3.org/TR/push-api/' rel='versionof'>Push API</a>
<br>Latest publication: <a href='https://www.w3.org/TR/2017/WD-push-api-20170508/'>08 May
2017</a></dt>
<dd>Reference Draft:
<a
href='https://www.w3.org/TR/2015/WD-push-api-20151215/'>https://www.w3.org/TR/2015/WD-push-api-20151215/</a><br>
associated <a href='https://lists.w3.org/Archives/Member/member-webapps/2012OctDec/0007.html'> Call
for Exclusion</a> on 18 October 2012
ended on 17 March 2013<br>Produced under
<a href="https://www.w3.org/2012/webapps/charter/">Web Applications Working Group charter</a></dd>
<dt id=1003 class='spec'><a href='https://www.w3.org/TR/screen-orientation/' rel='versionof'>The
Screen Orientation API</a>
<br>Latest publication: <a href='https://www.w3.org/TR/2016/WD-screen-orientation-20161031/'>31
October 2016</a></dt>
<dd>Reference Draft:
<a
href='https://www.w3.org/TR/2015/WD-screen-orientation-20151215/'>https://www.w3.org/TR/2015/WD-screen-orientation-20151215/</a><br>
associated <a href='https://lists.w3.org/Archives/Member/member-webapps/2012AprJun/0003.html'> Call
for Exclusion</a> on 22 May 2012
ended on 19 October 2012<br>Produced under
<a href="https://www.w3.org/2010/webapps/charter/">Web Applications Working Group charter</a></dd>
<dt id=1038 class='spec'><a href='https://www.w3.org/TR/custom-elements/' rel='versionof'>Custom
Elements</a>
<br>Latest publication: <a href='https://www.w3.org/TR/2016/WD-custom-elements-20161013/'>13
October 2016</a></dt>
<dd>Reference Draft:
<a
href='https://www.w3.org/TR/2016/WD-custom-elements-20160119/'>https://www.w3.org/TR/2016/WD-custom-elements-20160119/</a><br>
associated <a href='https://lists.w3.org/Archives/Member/member-cfe/2013Oct/0008.html'> Call for
Exclusion</a> on 24 October 2013
ended on 23 December 2013<br>Produced under
<a href="https://www.w3.org/2012/webapps/charter/">Web Applications Working Group charter</a></dd>
<dt id=1004 class='spec'><a href='https://www.w3.org/TR/shadow-dom/' rel='versionof'>Shadow DOM</a>
<br>Latest publication: <a href='https://www.w3.org/TR/2017/WD-shadow-dom-20170213/'>13 February
2017</a></dt>
<dd>Reference Draft:
<a
href='https://www.w3.org/TR/2015/WD-shadow-dom-20151215/'>https://www.w3.org/TR/2015/WD-shadow-dom-20151215/</a><br>
associated <a href='https://lists.w3.org/Archives/Member/member-webapps/2012AprJun/0003.html'> Call
for Exclusion</a> on 22 May 2012
ended on 19 October 2012<br>Produced under
<a href="https://www.w3.org/2010/webapps/charter/">Web Applications Working Group charter</a></dd>
<dt id=797 class='spec'><a href='https://www.w3.org/TR/workers/' rel='versionof'>Web Workers</a>
<br>Latest publication: <a href='https://www.w3.org/TR/2015/WD-workers-20150924/'>24 September
2015</a></dt>
<dd>Reference Draft:
<a
href='https://www.w3.org/TR/2015/WD-workers-20150924/'>https://www.w3.org/TR/2015/WD-workers-20150924/
</a><br>
associated <a href='https://lists.w3.org/Archives/Member/member-webapps/2012JanMar/0007.html'> Call
for Exclusion</a> on 13 March 2012
ended on 12 May 2012<br>Produced under
<a href="https://www.w3.org/2010/webapps/charter/">Web Applications Working Group charter</a></dd>
</dl>
</section>
<section>
<h3 id="changes-from-wp1">Changes from the previous charter</h3>
<p>The major changes from the <a
href="https://www.w3.org/2016/11/webplatform-charter.html">second Web platform Working Group
Working Group charter</a> include:</p>
<p> </p>
<dl>
<dt>New deliverables:</dt>
<dd>Intersection Observers, Static Range</dd>
<dt>Moved from deliverable to potential deliverable:</dt>
<dd>HTML 2D canvas</dd>
<dt>Removed as deliverables:</dt>
<dd>Service Workers; Background synchronization (transferred to a new WG)</dd>
<dd>High-level user events</dd>
<dt>A further 6-month extension of the Working Group</dt>
<dt>Updated expected milestones</dt>
<dt>Removed note aspiring to modularisation of HTML</dt>
<dd>It's often a useful goal, but pragmatic decisions have shown there is no clearly
right answer
and the Working Group makes things externally or integrates them on a case-by-case
basis.</dd>
</dl>
</section>
<hr>
<address>Yves Lafon, Team Contact<br>
Xiaoqian Wu, Team Contact<br>
Adrian Bateman, Chair<br>
Charles McCathie Nevile, Chair<br>
Léonie Watson, Chair</address>
<p class="copyright"> <a href="https://www.w3.org/Consortium/Legal/ipr-notice#Copyright"
rel="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.</p>
</section>
</body>
</html>