-
Notifications
You must be signed in to change notification settings - Fork 1
/
Copy pathw3c-highlights-201609-cn.html
1817 lines (1805 loc) · 111 KB
/
w3c-highlights-201609-cn.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
<!DOCTYPE html>
<html lang="en">
<head>
<meta content="text/html; charset=UTF-8" http-equiv="content-type">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<title>W3C Highlights - September 2016</title>
<link rel="stylesheet" href="/StyleSheets/TR/base.css">
<link rel="stylesheet" href="/2014/10/w3c-highlights/default.css">
<link rel="stylesheet" href="/2014/10/w3c-highlights/styles.css">
<style>
img {
float: right;
max-width: 227px;
}
h2 {
padding: 0.2em 0.5em;
white-space: nowrap;
background: #005A9C;
color: white;
display: inline;
line-height: 2.8;
border-radius: 3px;
text-decoration: none
}
.quote {
margin-left: 19%;
margin-top: 0;
margin-bottom: 2em;
}
blockquote {
margin: 20px 0 20px 120px;
padding: 10px 0 10px 10px;
border: 0;
font-size: 100%;
font: inherit;
vertical-align: baseline;
}
blockquote::before {
position: absolute;
margin: -16px 0 0 -80px;
color: #CCC;
font: 200px/1 'PT Sans',sans-serif;
content: '\201C';
}
.QuoteAttr {
font-style: italic;
}
table, td, th {
border: 2px solid #005A9C;
padding: 6px;
margin: 15px 0px 30px 0px;
width: 100%;
border-collapse: collapse;
border-spacing: 0;
text-align: left;
}
</style>
</head>
<body>
<div id="container">
<p><a href="http://www.w3.org/"><img alt="W3C" src="/Icons/w3c_home" height="48"
width="72"></a></p>
<h1>W3C Highlights <br>
September 2016</h1>
<div class="section">
<div class="status">
<p>This <strong>public</strong> report was first prepared for the <a
href="https://www.w3.org/2016/09/TPAC/ac-agenda.html">W3C
Advisory Committee Meeting</a>, part of <a href="https://www.w3.org/2016/09/TPAC/">TPAC
2016</a>.
See the accompanying <a href="https://www.w3.org/2016/09/factsheet.html">W3C
Fact Sheet — September
2016</a>. For the previous edition, see the <a href="https://www.w3.org/2016/03/w3c-highlights/">March
2016 W3C highlights</a>. For future
editions of this report, please consult the <a href="https://www.w3.org/Consortium/highlights/">latest
version</a>.</p>
<!-- <p>A <a href="http://www.chinaw3c.org/w3c-highlights-201603.html" hreflang="zh">Chinese</a> translation is available.</p> -->
</div>
<div id="toc">
<p><a title="Show/Hide Table of Contents" href="#toc_list" onclick="toggleNav(); return false;">☰
Contents</a></p>
<ul class="contents" id="toc_list">
<li><a href="#intro">Introduction</a></li>
<li><a href="#digpub">Digital Publishing</a></li>
<li><a href="#htmlcss">Application Development: HTML, CSS, Houdini Task Force</a></li>
<li><a href="#cohesion">Cohesive Web Platform</a>
<ul>
<li><a href="#security">Security</a></li>
<li><a href="#webpayments">Web Payments</a></li>
<li><a href="#wot">Web of Things</a></li>
<li><a href="#webrtc">WebRTC</a></li>
<li><a href="#vr">Virtual Reality</a></li>
</ul>
</li>
<li><a href="indepth">In depth</a>
<ul>
<li><a href="#digpub2">Digital Publishing</a>
<ul>
<li><a href="#idpf">Cooperation between IDPF and W3C</a></li>
<li><a href="#annotations">Annotations</a></li>
</ul>
</li>
<li><a href="#automotive">Automotive</a></li>
<li><a href="#telecommunications">Telecommunications</a></li>
<li><a href="#webpayments2">Web Payments</a></li>
<li><a href="#entertainment">Entertainment</a>
<ul>
<li><a href="#vr2">Virtual Reality</a></li>
<li><a href="#html-media">HTML Media</a></li>
<li><a href="#cloud-browser">Cloud Browser</a></li>
<li><a href="#ggie">GGIE (Glass-to-Glass Internet Ecosystem)</a></li>
<li><a href="#second-screen">Second Screen</a></li>
<li><a href="#tv-control-api">TV Control API</a></li>
<li><a href="#multi-device-timing">Multi-device Timing</a></li>
</ul>
</li>
<li><a href="#application-development">Application Development</a>
<ul>
<li><a href="#html">HTML</a>
<ul>
<li><a href="#html51">Track for HTML 5.1 REC</a></li>
<li><a href="#webapps">Extensible Web & (real) Web Applications</a></li>
<li><a href="#app-dev-other">Other ongoing work</a></li>
</ul>
</li>
<li><a href="#css">CSS</a></li>
<li><a href="#timed-text">Timed Text</a></li>
<li><a href="#performance">Performanca</a></li>
<li><a href="#testing">Testing</a></li>
</ul>
</li>
</ul>
</li>
<li><a href="#privacy-security">Privacy and Security</a></li>
<li><a href="#wot2">Web of Things</a></li>
<li><a href="#blockchains">Blockchains</a></li>
<li><a href="#data">Web of Data</a>
<ul>
<li><a href="#vre4eic">Workshop: Smart Descriptions & Smarter Vocabularies</a></li>
</ul>
</li>
<li><a href="#web-for-all">Web for All</a>
<ul>
<li><a href="#i18n">Internationalization (i18n)</a></li>
<li><a href="#accessibility">Web accessibility</a></li>
</ul>
</li>
<li><a href="#world">W3C in the World</a>
<ul>
<li><a href="#training">Training</a></li>
<li><a href="#liaisons">Liaisons</a></li>
</ul>
</li>
<li><a href="#org">Organizational evolution</a></li>
<li><a href="#conclusion">Conclusion</a></li>
</ul>
</div>
<h2 id="intro">Introduction</h2>
<p>A few months ago, we <a href="https://www.w3.org/2016/03/w3c-highlights/Overview.html">highlighted</a>
W3C's particular focus on Web Security and putting the future of the
Web on the track of the future of Industry. Our top-level messages
this time around are:</p>
<ul>
<li>Digital Publishing: Making Web = Publishing truer and truer.</li>
<li>HTML: bleeding edge, fresh and regular releases.</li>
<li>Cohesive Web Platform: so many areas are getting traction in W3C
—payments, WoT, webRTC, important things in core.</li>
</ul>
<p>Last but not least, W3C embarked on an internal functional <a href="org">reorganization</a>
that better accords with the nature of today’s Web and the
expectations of its diverse users, developers, and implementers.</p>
<h2 id="digpub">Digital Publishing</h2>
<p>W3C continues to steer and build Web technologies where they impact
industries. Digital Publishing was one of the first fields to be
addressed under the banner of a vertical industry, embracing the
industry transformation that the Web offers through integrated
experiences across devices.</p>
<p>The Web encapsulates all that civilization needs; and the march of
technology continues to be enhanced to meet the new needs. It is the
new needs that require everyone's engagement. Digital Publishing is an
area W3C has increased focus on this year.</p>
<p>The boundary between digital publications and other Web content is
blurring, creating a rich media environment for digital publishing
that opens up new possibilities for readers, authors, and publishers.
To fully align the publishing industry and core Web technology, the
team and the <abbr title="International Digital Publishing Forum">IDPF</abbr>,
having collaborated for many years, are discussing --and since then
announced-- <a href="https://www.w3.org/2016/05/digpub.html.en">W3C
and IDPF exploring plans to combine</a> to more quickly advance
publishing technologies on the Open Web Platform.</p>
<p>In order to achieve the vision of publishing on the Web, IDPF and W3C
have been developing for three years a universal accessible
interchange and delivery ecosystem for digital publications,
furthering IDPF’s adoption of HTML5 and especially CSS during the
development of EPUB 3 which also incorporates SVG and MathML; and
collaborated to develop a shared vision of a future <abbr title="Portable Web Publications">PWP</abbr>,
the evolution of EPUB 3. The Digital Publishing Interest Group has
just recently published the first draft of a <a href="https://www.w3.org/TR/pwp-ucr/">Portable
Web Publications Use Cases and Requirements</a> document, that will
be a basis of the future evolution of PWP and EPUB. IDPF's work has
led to CSS improvements, W3C's work on Web Accessibility is
fundamental to the design of accessible electronic publications. W3C
will help make EPUB and portable Web publications more visible and
credible outside the book publishing industry, while IDPF’s strong
connections to the publishing industry will help make the PWP work
begun in W3C more relevant and credible for the publishing community.
With more of the Web community we will facilitate the broader adoption
of the evolution of EPUB 3 as the standard for Web-based portable
documents in general.</p>
<p>Read more <a href="digpub2">below</a>.</p>
<h2 id="htmlcss">Application Development: HTML, CSS, Houdini Task Force</h2>
<p>HTML is on the bleeding edge, with fresh and regular releases; it is
being improved without a pause. HTML5 was released in October 2014 and
HTML 5.1 is on track to REC in the Fall 2016. In fact, we are
finishing HTML 5.1 and starting HTML 5.2, making regular incremental
updates to HTML a reality.</p>
<p>In order to achieve this, HTML 5.1 <a href="https://lists.w3.org/Archives/Public/public-webapps/2016JulSep/0086.html">enters
Proposed Recommendation</a> in September. This update (<a href="http://w3c.github.io/html/changes.html#changes">changes</a>
are noted in the spec itself) improves upon HTML5, makes it more
reliable, more readable and understandable, a better match for
reality, and easier to use by the Web community.</p>
<p>At the same time, the Web Platform Working Group continues to update
the Editor's Draft, and proposed a First Public Working Draft of <a href="https://www.w3.org/TR/html52/">HTML 5.2</a>.
This will probably include some new features, some features that
were not interoperable –and so not included in HTML 5.1– and
some more bug fixes. This will kick off a program of regular Working
Draft releases until HTML 5.2 is ready to be moved to W3C
Recommendation sometime in the next year or so.</p>
<p><a href="https://www.w3.org/TR/html52/">For substantial new features
we prefer development first in a separate, “incubator” group, and
drafts to only enter the Working Group where there is sufficient
support from various kinds of implementers including browsers,
authoring tools, producers of content, and users. The </a><a href="https://www.w3.org/community/wicg/">Web
Platform Incubator Community Group (WICG)</a> was set up for this
purpose.</p>
<p>The Web Platform Working Group is determining how to transition work
from the incubator group to the working group, as proposals are
maturing. Nothing is really imminent but a few are in the pipeline
such as payments, directory upload, viewport API, background sync, as
well as a few specs of the <a href="https://github.com/w3c/css-houdini-drafts/wiki">CSS
Houdini</a> (CSS + <abbr title="Technical Architecture Group">TAG</abbr>)
task force.</p>
<p>Track progress using <a href="https://github.com/w3c/html/pulse/monthly">Github
pulse</a>, or by following on Twitter <a href="https://twitter.com/html_commits">@HTML_commits</a>
or <a href="https://twitter.com/htmlwg/">@HTMLWG</a>.</p>
<p>Read more <a href="application-development">below</a>.</p>
<h2 id="cohesion">Cohesive Web Platform</h2>
<p>In addition to developing HTML, and beyond the build-up of exploring
a merger in Publishing on the Web, there is excitement on the way the
Web Platform and W3C’s interest is expanding: Web Payments, Web of
Things, WebRTC, Web security; all getting traction in W3C, converging
to lay a cohesive Web Platform. Recently, we've started looking at
possibilities around Blockchain (<a href="https://www.w3.org/2016/04/blockchain-workshop/">Blockchains
and the Web, a W3C Workshop on Distributed Ledgers on the Web</a>,
29–30 June 2016). Find in the <a href="https://www.w3.org/2016/04/blockchain-workshop/report.html">Blockchains
Workshop report</a> the many topics for possible standardization or
incubation, including various aspects of identity and
proof-of-existence, as well as smaller blockchain primitives that
could increase interoperability across different distributed ledgers.</p>
<p><a href="https://www.w3.org/2016/Talks/ac2016-Jeff/public.html">Earlier
this year</a> the W3C Advisory Committee explored candidate areas
for the next big thing for the Web. A straw poll yielded:</p>
<ol>
<li> Security</li>
<li> Web Payments and Web of Things were tied</li>
<li> HTML and the continuation of OWP</li>
<li> WebRTC</li>
<li> Industry support</li>
<li> Virtual Reality</li>
</ol>
<h3 id="security">Security</h3>
<ul>
<li> <a href="https://www.w3.org/webauthn/">Web Authentication
Working Group</a> launched and published the <strong>FPWD of its
<a href="https://www.w3.org/TR/webauthn/">WebAuthn API</a></strong>,
bringing strong cryptographic authentication to the Web platform (to
reduce the reliance on password-based authentication). </li>
<li> <a href="http://www.w3.org/2011/webappsec/">WebAppSec WG</a>
published a <strong>Recommendation of <a href="https://www.w3.org/TR/SRI/">Subresource
Integrity</a></strong>, and Candidate Recommendations of <a href="http://www.w3.org/TR/2015/CR-CSP2-20150721/">CSP
Level 2</a>, <a href="http://www.w3.org/TR/2015/CR-upgrade-insecure-requests-20151008/">Upgrade
Insecure Requests</a> and <a href="http://www.w3.org/TR/2015/CR-mixed-content-20151008/">Mixed
Content</a>. </li>
<li>Read more <a href="privacy-security">below</a>.</li>
</ul>
<h3 id="webpayments">Web Payments</h3>
<ul>
<li> The <a href="https://www.w3.org/Payments/WG/">Web Payments
Working Group</a> is making payments easier and more secure on the
Web by maturing three <abbr title="First Public Working Draft">FPWD</abbr>s:
<ul>
<li> <a href="http://www.w3.org/TR/payment-request/">Payment
Request API</a>: Web API to allow merchants to easily accept
payments from different payment methods with minimal
integration. User agents will facilitate the payment flow
between merchant and user. </li>
<li> <a href="http://www.w3.org/TR/payment-method-id/">Payment
Method Identifiers</a>: Payment method identifier strings so
that components in the payment ecosystem can determine which
parties support which payment methods. </li>
<li> <a href="http://www.w3.org/TR/payment-method-basic-card/">Basic
Card Payment</a>: Data formats used by the Payment Request API
to support payment by payment cards such as credit or debit
cards. </li>
</ul>
</li>
<li> The <a href="https://www.w3.org/Payments/IG/">Web Payments
Interest Group</a> continues to look for standardization
opportunities for W3C and to hold discussions with other
organizations.
<ul>
<li> On its agenda are topics such as: verifiable claims,
blockchain (next steps following the Workshop), coupons and
loyalty, interledger protocol, and its own mission and
operations. </li>
</ul>
</li>
<li>Read more <a href="webpayments2">below</a>.</li>
</ul>
<h3 id="wot">Web of Things</h3>
<ul>
<li> Progressing towards overcoming the fragmentation of the Internet
of Things; enabling end to end interoperability across different
platforms. </li>
<li> The <a href="http://www.w3.org/WoT/IG/">Web of Things Interest
Group</a> is chartering a Working Group. </li>
<li> Liaisons with the Open Connectivity Foundation, the Industrial
Internet Consortium, Industry 4.0, OPC Foundation, ETSI and oneM2M,
IETF and IRTF, GSMA, Hypercat, the Open Group, and a number of
others. </li>
<li>Read more <a href="wot2">below</a>.</li>
</ul>
<h3 id="webrtc">WebRTC</h3>
<ul>
<li> WebRTC milestone: publication last May as Candidate
Recommendation of <a href="https://www.w3.org/TR/mediacapture-streams/">getUserMedia</a>, one of the two main APIs behind the
WebRTC technology. </li>
<li> Once WebRTC 1.0 reaches Candidate Recommendation, work will start
in earnest on the next version of WebRTC, which aims at converging
in more depth with the work started in the ORTC Community Group. </li>
<li>Read more <a href="telecommunications">below</a>.</li>
</ul>
<h3 id="vr">Virtual Reality</h3>
<ul>
<li>The <a href="https://www.w3.org/2016/06/vr-workshop/">upcoming
workshop on Web & Virtual Reality</a> will provide an early
perspective on how the two fields can benefit from one another. </li>
<li>Read more <a href="#vr2">below</a>.</li>
</ul>
<h2 id="indepth">In depth</h2>
<h3 id="digpub2">Digital Publishing</h3>
<p><a href="https://www.w3.org/TR/#tr_Digital_Publishing">All Standards
and Drafts: Digital Publishing</a></p>
<p>The publishing community is an important community to engage in W3C.
Digital publishing is increasingly impacted by the Web. Publishers
need to understand how the technology of the Web is evolving. The Web
can benefit from the centuries of expertise in the publishing industry
on typography and layout, improving the core Web technologies not only
for electronic publications but for all Web content.</p>
<p>Currently one W3C group is dedicated to understanding and documenting
the particular needs of the publishing community: the <a href="http://www.w3.org/dpub/IG">Digital
Publishing Interest Group</a>.</p>
<p>The Interest Group aims at continuing the work on and around <abbr title="Portable Web Publications">PWP</abbr>,
CSS related issues, as well as Accessibility. Reinforcing the ties
with the publishing community at large, in particular with
implementers, tool developers, but also with the scholarly publishing
community, remains high on the agenda, as well as outreach activities
around the relationships between publishing and the development of Web
Technologies.</p>
<ul>
<li> Ongoing work by the Digital Publishing Interest Group:
<ul>
<li> Several drafts of the <a href="http://www.w3.org/TR/pwp/">“Portable
Web Publications for the Open Web Platform”</a> (see also the
<a href="https://w3c.github.io/dpub-pwp/">Editors’ draft</a>),
which is giving the overall framework most of the Interest
Group’s work. The current work concentrates on a <strong>comprehensive
<a href="https://www.w3.org/TR/pwp-ucr/">Portable Web
Publications Use Cases and Requirements</a></strong>. The
Interest Group is also busy in the area of <strong>Accessibility,
working with the ARIA Working Group</strong> (<a href="https://www.w3.org/TR/dpub-aria-1.0/">Digital
Publishing WAI-ARIA Module 1.0</a>); finally, it has a <strong>strong
cooperation with the CSS Working Group</strong> on various
issues related to the needs of the Digital Publishing Community.
</li>
<li> <a href="https://www.w3.org/TR/2016/NOTE-dpub-accessibility-20160503/">Digital
Publishing and Accessibility in W3C Documents</a> (Interest
Group Note). </li>
</ul>
</li>
</ul>
<ul>
<li> Events:
<ul>
<li> The Interest Group held "virtual" face to face meetings on
May 25, 2016 and July 7, 2016; <a href="https://www.w3.org/2016/05/25-dpub-minutes.html">a
summary of the May meeting</a> is available, as wll as the <a
href="https://www.w3.org/2016/07/07-dpub-minutes.html">minutes
of the July meeting</a> </li>
<li> Members and staff are presenting in various public events,
e.g. <a href="http://edrlab.org/edrlab/index.php/epub-summit/">EPUB
Summit</a>, Bordeaux, 7-8 April, and the <a href="https://www.w3.org/2016/04/w3c-track.html">W3C
Track at the WWW2016 Conference</a>, Montréal, Canada,
13 April. </li>
<li> There was also a strong presence of the team at the DigiCon
conference in Chicago, USA, 10-11 May, as well as the <a href="http://iannotate.org/">I
Annotate</a> Workshop on 19–20 May in Berlin, Germany. </li>
</ul>
</li>
</ul>
<h4 id="idpf">Plans for a closer cooperation between IDPF and W3C</h4>
<p>The International Digital Publishing Forum (<a href="http://idpf.org">IDPF</a>)
is a global standards organization dedicated to the development and
promotion of electronic publishing and digital content consumption.
IDPF members include publishers, technology firms, other industry
associations, and government and educational organizations. IDPF is
the developer of the EPUB standard format for interchange and
distribution of digital publications.</p>
<p>As <a href="https://lists.w3.org/Archives/Member/w3c-ac-members/2016AprJun/0009.html">announced
to Members</a> and subsequently in <a href="https://www.w3.org/blog/news/archives/5399">home
page news</a> and a <a href="https://www.w3.org/2016/05/digpub.html.en">press
release</a> the IDPF leadership and W3C leadership are studying the
possibility of merging the work of IDPF into W3C. There is near-total
synergy between the technical work of the two organizations. IDPF's
work is fully dependent on core Open Web Platform technologies; the
EPUB 3 standard is based on HTML, CSS, SVG, and MathML. W3C's Web
Accessibility work is fundamental to the design of accessible
electronic publications. Technical contributions from the publishing
community are helping to improve the capabilities of CSS. Publication
packaging technology specified especially for EPUB ought to be based
on new OWP technologies in scope for the Web Platform Working Group.</p>
<h4 id="annotations">Annotations</h4>
<p><a href="https://www.w3.org/TR/#tr_Web_Annotation">All Standards and
Drafts: Web Annotation</a></p>
<p>Web Annotation is a type of <abbr title="user-generated content">UGC</abbr>
content that refers and links to other Web content (<strong>deep
linking</strong>). This may be a comment on an article, a set of
captions on an image or video, a footnote in an eBook, a citation in a
scholarly paper, an editorial highlight in a copy-edit workflow, or
many other types of referential content. Often, web annotations are
published and shared elsewhere than the original content, and may be
shared on social media, like Twitter or Facebook, with a link back to
the original content.</p>
<ul>
<li> Ongoing work:
<ul>
<li> The <a href="http://www.w3.org/annotation/">Web Annotation
Working Group</a> is focused on the initial steps, <strong>providing
an interchange model/format that encapsulates these different
kinds of <abbr title="user-generated content">UGC</abbr>
content, an API for deep linking into specific parts of
primary content, and a protocol for publishing and retrieving
annotations across different services</strong>. </li>
<li> The Group has published three Candidate Recommendations at
the beginning of July, namely:
<ul>
<li> <a href="https://www.w3.org/TR/2016/CR-annotation-model-20160906/">Web
Annotation Data Model</a> </li>
<li> <a href="https://www.w3.org/TR/2016/CR-annotation-vocab-20160906/">Web
Annotation Vocabulary</a> </li>
<li> <a href="https://www.w3.org/TR/2016/CR-annotation-protocol-20160906/">Web
Annotation Protocol</a> </li>
</ul>
</li>
</ul>
</li>
</ul>
<ul>
<li> Events:
<ul>
<li> The group had a face-to-face meeting in Berlin, Germany, on
the 17-18 May </li>
<li> There was also a strong presence of the team at the <a href="http://iannotate.org/">I
Annotate</a> Workshop on 19–20 May in Berlin, Germany (the
event was also co-sponsored by W3C) </li>
<li> W3C is also represented in the <a href="https://www.force11.org/group/annotating-all-knowledge-working-group">Annotating
All Knowledge coalition</a> hosted by Force11. </li>
</ul>
</li>
</ul>
<h3 id="automotive">Automotive</h3>
<p><a href="https://www.w3.org/TR/#tr_Automotive">All Standards and
Drafts: Automotive</a></p>
<p>The W3C <a href="https://www.w3.org/2014/automotive/">Automotive
Working Group</a>, based on conversations with other groups at TPAC,
took a step back and looked at the <strong>architecture</strong> for
its API and accompanying data spec. </p>
<ul>
<li> Ongoing work:
<ul>
<li> The previous Working Draft was a WebIDL approach that would
require someone to write a browser extension to make a native
Vehicle object available to developers and the accompanying data
spec was an attempt at trying to define a common core set of
signal data that most auto manufacturers could provide. After
deliberation, exploring and dismissing Sensor API approach, we
considered a <strong>RESTful API and Web Sockets service
approach</strong>. Some of the benefits, in brief, are <strong>not
needing to maintain browser extensions in step with security
upgrades, ability to be more granular in access control for a
service as security is a major concern and that the API can be
used in the vehicle by other platforms other than a web
runtime</strong>. </li>
<li> This RESTful API can be used by QT In-Vehicle-Infotainment
systems and headless applications. The architecture debate
concluded at the <a href="https://www.w3.org/2016/04/28-auto-minutes.html#item02">April
F2F</a>. There is industry interest in this new approach. <strong>We
have also started collaborating on a more ambitious and
extensive data spec that can accommodate the differences in
data auto manufacturers provide</strong>. </li>
<li> The group's charter was extended and will be rechartered when
we have a better sense of timeline and deliverables. It has made
tremendous progress on a new API and data specs. </li>
</ul>
</li>
</ul>
<ul>
<li> Events:
<ul>
<li> <a href="https://www.w3.org/auto/wg/wiki/Main_Page#Meetings">July
F2F</a> hosted by Jaguar Land Rover. </li>
</ul>
</li>
</ul>
<ul>
<li> Companion Business Group:
<ul>
<li> The W3C Automotive BG acts as an incubator for possible
standards work. Its two main focuses are <strong>contributing
automotive media tuner use cases and requirements to the TV
Controller API WG and Location Based Services API</strong>,
the latter is being led by engineers from Alibaba and Peugeot. </li>
</ul>
</li>
</ul>
<h3 id="telecommunications">Telecommunications</h3>
<ul>
<li> <a href="https://www.w3.org/TR/#tr_Web_Real_Time_Communication">All
Standards and Drafts: Web Real Time Communication</a> </li>
<li> <a href="https://www.w3.org/TR/tr-groups-all#tr_Device_and_Sensors_Working_Group">All
Standards and Drafts:Device and Sensors Working Group</a> </li>
</ul>
<p>The W3C agenda continues to support important challenges and
opportunities that emerge from the telco industry.</p>
<ul>
<li> Ongoing work:
<ul>
<li> A first important milestone for the WebRTC work was reached
in May, with the publication as a <strong>Candidate
Recommendation of getUserMedia, one of the two main APIs
behind the WebRTC technology</strong> </li>
<li> Work on <strong>bringing the 2nd API (WebRTC 1.0) to CR</strong>
continues, taking into account the feedback received during the
wide review of the existing draft. The Working Group will be
meeting at TPAC. </li>
</ul>
</li>
</ul>
<ul>
<li> Upcoming work:
<ul>
<li> Once WebRTC 1.0 reaches Candidate Recommendation, work will
start in earnest on the next version of WebRTC, which aims at
converging in more depth with the work started in the ORTC
Community Group. </li>
<li> The <a href="https://www.w3.org/2016/06/vr-workshop/">upcoming
workshop on Web & Virtual Reality</a> will provide an
early perspective on how the two fields can benefit from one
another, and open the road to new opportunities of network
utilization for the bandwidth & latency demanding needs of
VR. </li>
</ul>
</li>
</ul>
<ul>
<li> Security tie-in:
<ul>
<li> The <a href="https://www.w3.org/webauthn/">Web
Authentication Working Group</a> charter was approved, and the
Working Group has already published its <strong>first public
working draft of adapting FIDO-based authentication to
browsers</strong>. This illustrates another field where the
telecommunications industry is bound to benefit from the
standardization pushed by W3C to simplify identity management,
an important need that operators can both help fulfill and
benefit from. </li>
<li> While the <a href="https://w3c.github.io/websec/hasec-charter">Hardware
Security Working Group draft charter</a> did not receive
enough support to proceed as a Working Group, it triggered the
creation of an incubation Community Group in this space, the <a
href="https://www.w3.org/community/hb-secure-services/">Hardware
Based Secure Services CG</a>, which already had its first
face-to-face meeting and published its <strong><a href="https://w3c.github.io/websec/hbss.html">Hardware
Based Secure Services preliminary technical analysis and
proposal</a></strong>. This work brings the prospects of
enabling the high security ensured by hardware-tokens (such as
SIM cards) to the Web platform. </li>
</ul>
</li>
</ul>
<ul>
<li> Device perspective:
<ul>
<li> The <a href="http://www.w3.org/2009/dap/">Device &
Sensors Working Group</a> new charter was approved, with <strong>work
on the generic Sensor API</strong> continuing apace, getting
ready for its wide review by other groups. It promises to make
the Web a more malleable platform when it comes to interaction
with physical sensors. </li>
<li> Renewed interest on the <strong>Network Information API</strong>
has led to the Web Platform Incubator Community Group restarting
work on the spec, with the goal of bringing it back to the
Device & Sensors Working Group for finalization when clear
implementation plans make it compatible with the requirements
from the Recommendation track </li>
</ul>
</li>
</ul>
<ul>
<li> Overlapping work:
<ul>
<li> Many operators also provide media services to their
customers; the activity in the <a href="http://www.w3.org/2011/webtv/">Web
and TV Interest Group</a> continues to provide new
capabilities for Web-based services in this area, as illustrated
by the ongoing work on the TV Control API. The work started in
the Cloud Browser Task Force which aims at facilitating the
deployment of Web-based media services in thin-clients (e.g. set
top boxes) is well positioned to provide great cost-saving and
better UX to operators. </li>
<li> (See <a href="#Web_Payments">Web Payments section</a>) W3C
work on Payments and Internet of Things completes the picture of
the many places where the telecommunication industry can bring
its expertise and its requirements to the future of the Web. </li>
</ul>
</li>
</ul>
<h3 id="webpayments2">Web Payments</h3>
<p><a href="https://www.w3.org/TR/#tr_Web_Payments">All Standards and
Drafts: Web Payments</a></p>
<p>E-commerce is growing as a proportion of all commerce. According to
Forrester, the web in 2018 will account for 11% of total retail sales,
up from 8% in 2013. However, a number of challenges are limiting the
potential of E-commerce, such as fraud losses, user expectations in
particular with mobile device usage, technology (biometrics, Web of
Things, automotive advances, and NFC adoption), regulation.</p>
<p>There are numerous discussions currently at W3C around technology
intended to improve payments directly or indirectly.</p>
<h4>Working and Interest Groups</h4>
<ul>
<li>Payments:
<ul>
<li> <a href="https://www.w3.org/Payments/WG/">Web Payments
Working Group</a>: open APIs to streamline checkout </li>
<li> <a href="https://www.w3.org/Payments/IG/">Web Payments
Interest Group</a>: use cases and requirements gathering,
liaisons </li>
</ul>
</li>
<li>Security:
<ul>
<li> <a href="https://www.w3.org/Webauthn/">Web Authentication
Working Group</a></li>
<li> <a href="http://www.w3.org/2011/webappsec/">WebAppSec</a></li>
<li> <a href="http://www.w3.org/2012/webcrypto/">WebCrypto</a></li>
</ul>
</li>
</ul>
<h4>Community Groups</h4>
<ul>
<li> Payments:
<ul>
<li> <a href="https://www.w3.org/community/webpayments/">Web
Payments Community Group</a>: pre-standardization research </li>
</ul>
</li>
<li>Security:
<ul>
<li> <a href="https://www.w3.org/community/hb-secure-services/">Community
Group</a> discussion about Hardware Security (HaSec) </li>
</ul>
</li>
<li> Clearing and Settlement:
<ul>
<li> <a href="https://www.w3.org/community/interledger/">Interledger
Payments Community Group</a>: easier payments across disparate
payment systems </li>
</ul>
</li>
<li> Verifiable Attributes / Identity:
<ul>
<li> <a href="https://www.w3.org/community/credentials/">Credentials
Community Group</a> </li>
</ul>
</li>
</ul>
<h4>Web Payments Working Group</h4>
<p>The mission of the <a href="https://www.w3.org/Payments/WG/">Web
Payments Working Group</a> is to make payments easier and more
secure on the Web. </p>
<ul>
<li> Ongoing work:
<ul>
<li> The WPWG <a href="https://www.w3.org/blog/wpwg/2016/04/21/first-public-working-drafts-of-payment-request-api/">published
three FPWDs</a> in April 2016. Those drafts have evolved
significantly as the WG resolves <a href="https://github.com/w3c/browser-payment-api/issues">issues</a>.
We are beginning to see <strong>early implementations</strong>;
see for instance the <a href="https://youtu.be/yelPlCVZLEE">demo
at Google I/O</a>. </li>
<li> The WPWG is also working on (but has not yet resolved to
request FPWD status):
<ul>
<li><a href="https://w3c.github.io/webpayments-payment-apps-api/">Payment
App API</a>, which will describe <strong>how users
register third-party payment applications</strong>, and
how browsers launch and communicate payment requests and
responses with those applications. </li>
<li>A <a href="http://w3c.github.io/webpayments-methods-credit-transfer-direct-debit/">SEPA
credit transfer</a> payment method specification.</li>
<li> Two specifications regarding <strong>HTTP-based payments</strong>
(e.g., for the Web of Things): <a href="https://w3c.github.io/webpayments-http-api/">Web
Payments HTTP API 1.0</a> and <a href="https://w3c.github.io/webpayments-http-messages/">Web
Payments HTTP Messages 1.0</a>. </li>
</ul>
</li>
</ul>
</li>
</ul>
<ul>
<li> New Members and events:
<ul>
<li>American Express and Groupement des Cartes Bancaires have
joined W3C</li>
<li> Blockstream, Tencent, Shopify, Gemalto, and CDT have joined
the Web Payments Working Group. </li>
<li> Ian Jacobs participated on a panel in the Card Not Present
conferience.</li>
<li> Canton Consulting organized a gathering in Paris around
payments, including representatives from W3C staff as well as
the WG and IG. </li>
<li> The group held a <a href="https://github.com/w3c/webpayments/wiki/Web-Payments-Working-Group-FTF-Meeting-%28July-2016%29">Face-to-Face
meeting 7-8 July in London at Visa Europe</a>. </li>
</ul>
</li>
</ul>
<h4>Web Payments Interest Group</h4>
<p>The <a href="https://www.w3.org/Payments/IG/">Web Payments IG</a>
continues to look for standardization opportunities for W3C and to
hold discussions with other organizations. </p>
<ul>
<li> Ongoing work:
<ul>
<li> The Verifiable Claims Task Force (a joint task force with the
Credentials Community Group) has had discussions around a draft
charter and supporting materials. They are continuing to seek
support from W3C Members and non-Members for the work. </li>
<li> The IG has had some conversations around <strong>loyalty and
digital coupons</strong>, and how integration might layer on
top of the initial work of the Web Payments Working Group. </li>
</ul>
</li>
</ul>
<ul>
<li> Event:
<ul>
<li> The IG held a <a href="https://www.w3.org/Payments/IG/wiki/Main_Page/FTF_Jul2016">face-to-face
meeting in Boston on 1 July</a>, to discuss <strong>verifiable
claims, blockchain (next steps following the Workshop),
coupons and loyalty, interledger protocol</strong>, and its
own mission and operations. </li>
</ul>
</li>
</ul>
<h3 id="entertainment">Entertainment</h3>
<p><a href="https://www.w3.org/TR/#tr_Web_and_TV">All Standards and
Drafts: Web and TV</a></p>
<p>The <a href="http://www.w3.org/2011/webtv/">Web and TV Interest
Group</a> serves as steering committee for the TV and Entertainment
activity within W3C. Over the years, it contributed to launch a number
of Community Groups and Working Groups including the HTML Media
Extensions Working Group, the Second Screen Working Group, the TV
Control Working Group, and a few other community groups and task
forces. On top of the activities mentioned below, note that the group
has discussed at TPAC 2015 the <strong>possibility to define a Web
profile for TV</strong>, and may start work in that area by TPAC
2016.</p>
<h4 id="vr2">Virtual Reality</h4>
<p>A number of industry players have announced important investments or
initial products in Virtual Reality. What are the new features and
improvements needed to make the Web a compelling platform for actual
VR development?</p>
<p>The <a href="https://www.w3.org/community/webvr/">WebVR Community
Group</a> was created in March 2016 to incubate a <a href="https://w3c.github.io/webvr/">WebVR
API specification</a>, under the impulse of Mozilla.</p>
<p>W3C is organizing a <a href="https://www.w3.org/2016/06/vr-workshop/">Web
& Virtual Reality workshop</a> on 19-20 October 2016 on the West
Coast to look at the intersection of Web and Virtual Reality
technologies. Topics of interest include: displaying stereoscopic
content, detecting & adapting to characteristics of VR headsets,
handling new input methods for VR (gamepad, hand position, …), 3D
audio, 3D media synchronization, interoperable formats and codecs for
3D and 360 content, bringing VR as progressive enhancement to classic
Web browsing, etc.</p>
<h4 id="html-media">HTML Media</h4>
<p><a href="https://www.w3.org/TR/tr-groups-all#tr_HTML_Media_Extensions_Working_Group">All
Documents: HTML Media Extensions Working Group</a></p>
<p>The industry and the Consortium choice is to enhance HTML to be
capable of playing video content without the help of plug-in video
players, streaming technologies over HTTP such as Dynamic Adaptive
Streaming over HTTP (DASH) has rapidly emerged in the industry. W3C
took to develop two HTML5 extensions to enable UAs to play such
streams.</p>
<p>These extensions are essential to meet the industry requirements for
video content delivery on the Web, by providing Web apps with more
flexible control over video content, which enable advanced services
such as dynamic ad-insertion.</p>
<p>HTML Media, core media features of Web platform, is developed in the
HTML Media Extensions Working Group. It is working on providing
control over playback of encrypted content.</p>
<p>Ongoing work:</p>
<ul>
<li> The <a href="http://www.w3.org/html/wg/">HTML Media Extensions
Working Group</a> is currently working on two extensions: Media
Source Extensions (MSE) and Encrypted Media Extensions (EME).
<ul>
<li> MSE is a Candidate Recommendation that allows JavaScript to <strong>send
byte streams to media codecs within Web browsers that support
HTML5 video</strong>. It facilitates a variety of use cases
like adaptive streaming and time shifting live streams (<a href="https://github.com/w3c/media-source">MSE
Github page</a>). </li>
<li> EME is a Candidate Recommendation for providing a <strong>communication
channel between Web browsers and content protection systems to
allow playback of encrypted audio and video on the Web</strong>.
This allows the use of HTML5 video to play back DRM-wrapped
content such as streaming video services without the need for
third-party media plugins like Adobe Flash or Microsoft
Silverlight. (<a href="https://github.com/w3c/encrypted-media/">EME
on Github</a>) </li>
</ul>
</li>
<li> version 1.0 of the two extensions are planned to become W3C
Recommendations on September 29th, as specified by the <a href="https://lists.w3.org/Archives/Public/public-html-media/2016May/0029.html">Group
timeline</a>. </li>
<li> There are some industry requests for additional features and
participants are eager to start the work on them. TPAC 2016 will be
an important milestone for the future work. </li>
</ul>
<h4 id="cloud-browser">Cloud Browser</h4>
<p>The <a href="https://www.w3.org/2011/webtv/wiki/Main_Page/Cloud_Browser_TF">Cloud
Browser TF</a>, subset of the Web and TV Interest Group, discusses <strong>support
for web browser technology within devices such as HDMI dongles</strong>
and lightweight <abbr title="set-top box">STB</abbr>s.</p>
<p>New cloud browser Runtime Environments (RTEs) require the definition
of APIs that would enable communication between the cloud browser and
the client.</p>
<ul>
<li> Ongoing work:
<ul>
<li> The TF develops an <a href="https://www.w3.org/2011/webtv/wiki/Main_Page/Cloud_Browser_TF/Architecture">Architecture</a>
document to help identify technical gaps </li>
<li> The TF discusses <a href="https://www.w3.org/2011/webtv/wiki/Main_Page/Cloud_Browser_TF/UseCases">use
cases and requirements</a> </li>
</ul>
</li>
</ul>
<h4 id="ggie">GGIE (Glass-to-Glass Internet Ecosystem)</h4>
<p>Thanks to the international and interdependent standards developed by
global organizations including W3C, IETF, IEEE, CEA, SMPTE, MPEG, etc.
the Internet-based or Web-based video content delivery services are
expanding in the entertainment content market. Because of the
distributed and sometime ad-hoc nature of the efforts, there is a need
to go back to use cases: capture existing use cases, analyze them, and
enhance them to further develop new standards for better services.</p>
<p>The <a href="https://www.w3.org/2011/webtv/wiki/GGIE_TF">GGIF TF</a>,
subset of the Web and TV Interest Group, discusses the <strong>end to
end Internet digital video ecosystem, focusing on all phases of the
video life cycle</strong>:
Capture-Edit-Package-Distribute-Find-Watch for both professional and
non-professional digital video, and will identify recommended
standards and features that could be developed.</p>
<ul>
<li> Ongoing work:
<ul>
<li> The TF elaborates key components of a flexible content
identification mechanism, and writes down <a href="https://www.w3.org/2011/webtv/wiki/GGIE_TF/UseCases">GGIE
Use Cases</a> and requirement docs which could be used to
begin new technical works. The second round is expected to
finish at TPAC 2016. </li>
</ul>
</li>
</ul>
<h4 id="second-screen">Second Screen</h4>
<p><a href="https://www.w3.org/TR/tr-groups-all#tr_Second_Screen_Presentation_Working_Group">All
Documents: Second Screen Presentation Working Group</a></p>
<p>Web content is available on an ever expanding array of devices
including eBook readers, phones, tablets, laptops, auto displays, and
electronic billboards, and there are a variety of mechanisms that
allow these devices to use secondary display screens available in the
local environment, attached by wired connections or remotely with
wireless, peer-to-peer media. However, in most cases, lower layers
such as OS provide those connection mechanisms, which Web apps,
consequently, have no access and control over. Web apps should be
capable of implementing services which cover scenarios such as using a
big screen device to watch a movie selected on and streamed from a
smartphone are getting more common as <abbr title="Over-the-top content">OTT</abbr>
services like Netflix emerge.</p>
<p>The <a href="https://www.w3.org/2014/secondscreen/">Second Screen
Working Group</a> aims at <strong>defining simple APIs that allow
web applications to show and control web content on one or more
secondary displays</strong>. </p>
<ul>
<li> Ongoing work:
<ul>
<li> <a href="http://www.w3.org/TR/2016/CR-presentation-api-20160714/">Presentation
API</a> published as Candidate Recommendation mid-July 2016. </li>
<li> Making progress on the <a href="https://www.w3.org/TR/2016/WD-remote-playback-20160714/">Remote
Playback API</a> that allows controlling remote playback of
media from a web page. The group published the First Public
Working Draft mid-July 2016. </li>
<li> The group is actively working on a <a href="https://github.com/w3c/web-platform-tests/tree/master/presentation-api">test
suite for the Presentation API</a>. </li>
</ul>
</li>
</ul>
<ul>
<li>Upcoming::
<ul>
<li>WG participants discussed the possibility to develop an <strong>open
protocol for the Presentation API</strong> within the <a href="https://www.w3.org/community/webscreens/">Second
Screen Community Group</a>, so as to allow a device to connect
to another vendor's device. A new charter for the CG is being
finalized accordingly. Expectation is to move this work to a WG,
the IETF, or some other organization once sufficiently
incubated. </li>
<li>The Working Group will re-charter by end of October 2016 to
finalize the Presentation API and the Remote Playback API. Scope
may not change as discussions within the CG will likely not have
made enough progress by then. We encourage interested parties to
share their thoughts with their favorite point of contact in the
team. </li>
</ul>
</li>
</ul>
<h4 id="tv-control-api">TV Control API</h4>
<p>The <a href="https://www.w3.org/2016/tvcontrol/">TV Control Working
Group</a> was launched in May 2016 to develop an API that would <strong>allow
Web apps to access radio/TV tuners and other broadcasting resources</strong>.
The WG takes of the work done by the TV Control API Community Group
since 2014.</p>
<ul>
<li> Ongoing work:
<ul>
<li> The <a href="http://w3c.github.io/tvapi/spec/">TV Control
API Specification</a> should be published as FPWD by TPAC. </li>
<li> The Auto BG is providing the TV Control API CG use cases for
automotive Media Tuner needs. </li>
</ul>
</li>
</ul>
<h4 id="multi-device-timing">Multi-device Timing</h4>
<p>In 2015, The Web and TV IG launched the <a href="https://www.w3.org/community/webtiming/">Multi-device
Timing Community Group</a> to create a draft specification that
defines a <strong>common, multi-device, timing mechanism and a
practical programming model e.g. to allow Web apps to synchronize
the playback of multiple streams on multiple devices</strong>.
Timing mechanisms allow operations to be executed at the correct time.
On the Web, different specs use different synchronization mechanisms,
and there is no support for multi-device timing. </p>
<ul>
<li> Ongoing work:
<ul>
<li>Initial draft of the <a href="https://webtiming.github.io/timingobject/">Timing
Object</a> specification, along with a reference polyfill
implementation in JavaScript. </li>
</ul>
</li>
</ul>
<ul>
<li>Upcoming::
<ul>
<li> The group needs <strong>involvement from would-be
implementers</strong>. Contributions to the discussions would
be particularly welcome! </li>
<li> <strong>The CG meeting at TPAC 2016</strong> on Tuesday
afternoon. </li>
<li> Multi-device timing is important for the broadcasting
industry, as well as for digital signage, and audio use cases. </li>
<li> Such a mechanism could also <strong>improve the
accessibility of media content on the Web</strong>. For
example, third party can easily provide additional audio track,
such as <a href="https://www.w3.org/TR/media-accessibility-reqs/#clean-audio">Clean
Audio</a>. </li>
<li> More generally, multi-device timing has wide utility in
communication, collaboration and multi-screen presentation. </li>
</ul>
</li>
</ul>
<h2 id="application-development">Application development</h2>
<h3 id="html">HTML</h3>
<p><a href="https://www.w3.org/TR/tr-groups-all#tr_Web_Platform_Working_Group">All