-
Notifications
You must be signed in to change notification settings - Fork 59
/
audio-2022.html
672 lines (566 loc) · 32.1 KB
/
audio-2022.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
<!DOCTYPE html>
<html lang="en-US">
<head>
<meta charset="utf-8">
<title>Audio Working Group Charter</title>
<link rel="stylesheet" href="https://www.w3.org/2005/10/w3cdoc.css" type="text/css" media="screen">
<link rel="stylesheet" type="text/css" href="https://www.w3.org/OldGuide/pubrules-style.css">
<link rel="stylesheet" type="text/css" href="https://www.w3.org/2006/02/charter-style.css">
<style>
main {
max-width: 60em;
margin: 0 auto;
}
ul#navbar {
font-size: small;
}
dt.spec {
font-weight: bold;
}
dt.spec new {
background: yellow;
}
.issue {
background: cornsilk;
font-style: italic;
}
.todo {
color: #900;
}
footer {
font-size: small;
}
</style>
</head>
<body>
<header id="header">
<aside>
<ul id="navbar">
<li><a href="#background">Background</a></li>
<li><a href="#scope">Scope</a></li>
<li><a href="#deliverables">Deliverables</a></li>
<li><a href="#success-criteria">Success Criteria</a></li>
<li><a href="#coordination">Coordination</a></li>
<li><a href="#participation">Participation</a></li>
<li><a href="#communication">Communication</a></li>
<li><a href="#decisions">Decision Policy</a></li>
<li><a href="#patentpolicy">Patent Policy</a></li>
<li><a href="#licensing">Licensing</a></li>
<li><a href="#about">About this Charter</a></li>
</ul>
</aside>
<p>
<a href="https://www.w3.org/"><img alt="W3C" height="48" src="https://www.w3.org/Icons/w3c_home" width="72"></a>
</p>
</header>
<main>
<h1 id="title">Audio Working Group Charter</h1>
<p class="mission">The <strong>mission</strong> of the <a href="https://www.w3.org/groups/wg/audio">Audio Working Group</a> is to add advanced sound and music synthesis capabilities to the Open Web Platform.</p>
<div class="noprint">
<p class="join"><a href="https://www.w3.org/groups/wg/audio/join">Join the Audio Working Group.</a></p>
</div>
<p style="padding: 0.5ex; border: 1px solid green"> This charter is available
on <a href="https://github.com/w3c/charter-drafts/blob/gh-pages/2022/audio-2022.html">GitHub</a>.
Feel free to raise <a href="https://github.com/w3c/charter-drafts/issues">issues</a>.
</p>
<section id="details">
<table class="summary-table">
<tr id="Status">
<th>
Charter Status
</th>
<td>
See the <a href="https://www.w3.org/groups/wg/audio/charters">group status page</a> and <a href="#history">detailed change history</a>.</i>
</td>
</tr>
<tr id="Duration">
<th>
Start date
</th>
<td>
14 June 2022
</td>
</tr>
<tr id="CharterEnd">
<th>
End date
</th>
<td>
14 June 2024
</td>
</tr>
<tr>
<th>
Chairs
</th>
<td>
Hongchan Choi (Google)<br/> Matt Paradis (BBC)<br/>
</td>
</tr>
<tr>
<th>
Team Contacts
</th>
<td>
<a href="mailto:chris@w3.org">Chris Lilley</a> (0.1 <abbr title="Full-Time Equivalent">FTE</abbr>)
</td>
</tr>
<tr>
<th>
Meeting Schedule
</th>
<td>
<strong>Teleconferences:</strong> 1-hour calls will be held fortnightly
<br>
<strong>Face-to-face:</strong> we will meet during the W3C's annual Technical Plenary week; additional face-to-face meetings may be scheduled by consent of the participants, usually no more than 3 per year.
</td>
</tr>
</table>
</section>
<section id="background" class="background">
<p>
Building upon and expanding the basic functionalities brought by HTML5's <code><audio></code> and <code><video></code> media elements and <code>MediaStream</code> object, the Audio Working Group
has developed the <code>Web Audio API</code>
and continues to define client-side script APIs
which support the features required by rich interactive applications including the ability to process and synthesize audio streams directly in script, as well as giving access to musical instruments through a bridge with existing system-level
MIDI APIs.
</p>
<p>
The audio API provides methods to read audio samples, write audio data, create sounds, and perform client-side audio processing and synthesis with minimal latency. It also adds programmatic access to the
<abbr title="Pulse Code Modulation">PCM</abbr> audio stream for low-level manipulation
directly in script. This API can be used for interactive applications, games, 3D environments, musical applications, educational applications, and for the purposes of accessibility. It includes the ability to synchronize, visualize, or
enhance sound information when used in conjunction with graphics APIs. Sound synthesis can be used to enhance user interfaces or produce music. The addition of advanced audio capabilities to user agents presents new options to Web developers
and designers and has many accessibility opportunities and challenges that this working group will continue to keep in mind.
</p>
<p>
The Web Audio API, which became a W3C Recommendation in June 2021,
will be maintained both by continuous refinement based on implementation
experience and also by adding new features, based on user demand,
practicality, ease of writing a polyfil/prototyping and utility.
Prioritisation of new features is informed by the
<a href="/2011/audio/2021_Web_Audio_API_Survey.pdf ">2021 Web Audio Developer
survey results</a>. The Working Group maintains a
<a href="https://github.com/WebAudio/web-audio-api/issues?q=is%3Aopen%20is%3Aissue%20project%3Awebaudio%2Fweb-audio-api%2F5">prioritized list of potential new features</a> on GitHub.
</p>
<p>
In addition to an audio processing API, this group has received feedback from the audio and music community and industry, who wish to Web-enable their MIDI-capable devices. <abbr title="Musical Instrument Digital Interface">MIDI</abbr> is
an electronic device interface, developed by the musical instrument industry, that includes communication protocols for two-way connection and control of a wide variety of devices, including digital musical instruments, digital audio workstations,
lighting sytems, game controllers, and many other systems. The MIDI specification has wide adoption and interoperable deployment across devices and computer operating systems, and to extend this existing infrastructure, the Audio Working
Group is also developing a specification to create a bridge between the browser and existing system-level MIDI APIs, to make musical instruments first-class citizens of the Web.
</p>
<p>
The Web MIDI API, which now has a second in-browser implementation,
is expected to progress to Candidate Recommendation during this charter period.
</p>
<p>
This working group will take into account common work-flows for sound creators, including considerations for common audio formats. This group will also liaise with other groups for direct connection to audio inputs and outputs, such as microphones and
speakers.
</p>
</section>
<section id="scope" class="scope">
<h2>Scope</h2>
<ul>
<li>Developing a client-side script API for processing and synthesizing PCM audio streams, including direct scripted solutions.</li>
<li>Access to audio devices, such as microphones or other audio inputs, and multi-channel speakers or other audio outputs.</li>
<li>APIs and advanced functionality regarding audio cache management and audio capability information.</li>
<li>Defining a client-side script API for accessing and manipulating MIDI-capable devices available on the users' systems.</li>
</ul>
<section id="section-out-of-scope">
<h3 id="out-of-scope">Out of Scope</h3>
<p>The following features are out of scope, and will not be addressed by this Working Group.</p>
<ul class="out-of-scope">
<li>
<p>This group will not work on audio representation markup during this charter period; discussions of music notation formats happens in the
<a href="https://www.w3.org/community/music-notation/">Music Notation Community Group</a>.</p>
</li>
<li>
<p>The audio API is intended to operate on local and remote sources including synthesis, files, and sound-capture sources. APIs for implementing interactive audio streaming directly between users is not in scope. </p>
</li>
<li>
<p>Specific functionality for speech synthesis
and speech recognition
is out of the direct scope of this group, though discussions and collaborations may occur with groups chartered to do such work, for the best compatibility.</p>
</li>
<li>
<p>Audio codec selection and support is out of scope.</p>
</li>
</ul>
</section>
</section>
<section id="deliverables">
<h2>
Deliverables
</h2>
<!--
https://www.w3.org/groups/wg/audio/deliverables
-->
<p>Updated document status is available on the <a href="https://www.w3.org/groups/wg/audio/publications">group publication status page</a>.</p>
<p><i>Draft state</i> indicates the state of the deliverable at the time of the charter approval. <i>Expected completion</i> indicates when the deliverable is projected to become a Recommendation, or otherwise reach a stable state.</p>
<section id="normative">
<h3>
Normative Specifications
</h3>
<p>
The Working Group will deliver the following W3C normative specifications:
</p>
<dl>
<dt id="web-audio" class="spec"><a href="https://webaudio.github.io/web-audio-api/">Web Audio API</a></dt>
<dd>
<p>This specification defines a high-level JavaScript API for processing and synthesizing audio in web applications. The primary paradigm is of an audio routing graph, where a number of AudioNode objects are connected together to define the overall audio rendering. The actual processing will primarily take place in the underlying implementation (typically optimized Assembly / C / C++ code), but direct JavaScript processing and synthesis is also supported.</p>
<p class="draft-status"><b>Draft state:</b> <a href="https://www.w3.org/TR/2021/REC-webaudio-20210617/">W3C Recommendation</a></p>
<p class="milestone"><b>Expected completion:</b> Q4 2025</p>
<dt id="web-midi" class="spec"><a href="https://webaudio.github.io/web-midi-api/">Web MIDI API</a></dt>
<dd>
<p>This specification defines an API supporting the MIDI protocol, enabling web applications to enumerate and select MIDI input and output devices on the client system and send and receive MIDI messages. It is intended to enable non-music MIDI applications as well as music ones, by providing low-level access to the MIDI devices available on the users' systems.</p>
<p class="draft-status"><b>Draft state:</b> <a href="https://www.w3.org/TR/2015/WD-webmidi-20150317/">Working Draft</a></p>
<p class="milestone"><b>Expected completion:</b> Q3 2024</p>
<dl><dt>
<p><b>Adopted Draft:</b> <a href='https://www.w3.org/TR/2015/WD-webmidi-20150317/'>Web MIDI API</a>, <a href='https://www.w3.org/TR/2015/WD-webmidi-20150317/'>https://www.w3.org/TR/2015/WD-webmidi-20150317/</a>, 2015-03-17
<p><b>Exclusion Draft:</b> <a href='https://www.w3.org/TR/2012/WD-webmidi-20121025/'>Web MIDI API</a>, <a href='https://www.w3.org/TR/2012/WD-webmidi-20121025/'>https://www.w3.org/TR/2012/WD-webmidi-20121025/</a>, 2012-10-25
<br> Exclusion period <b>began</b> 2012-11-01; Exclusion period <b>ended</b> 2013-03-24.
<p><b>Exclusion Draft Charter:</b> Produced under Working Group Charters:
<a href="http://www.w3.org/2011/audio/charter/2011/">http://www.w3.org/2011/audio/charter/2011/</a>, <a href="http://www.w3.org/2011/audio/charter/2012/">http://www.w3.org/2011/audio/charter/2012/</a>
</dd>
</dl></dl>
</section>
<section id="wg-other-deliverables">
<h3>
Other Deliverables
</h3>
<p>
Other non-normative documents may be created such as:
</p>
<ul>
<li>Use case and requirement documents;</li>
<li>Test suite and implementation reports for the specifications;</li>
<li>Primer or Best Practice documents to support web developers when designing applications.</li>
</ul>
</section>
<section id="timeline">
<h3>Timeline</h3>
<ul >
<li>Q3 2022: Updated Working Draft of Web MIDI API</li>
<li>Q4 2022: Updated Recommendation of Web Audio API</li>
<li>Q3 2023: Candidate Recommendation of Web MIDI API</li>
<li>Q4 2023: Updated Recommendation of Web Audio API</li>
<li>Q4 2024: Updated Recommendation of Web Audio API</li>
<li>Q3 2025: W3C Recommendation of Web MIDI API</li>
<li>Q4 2025: Updated Recommendation of Web Audio API</li>
</ul>
</section>
</section>
<section id="success-criteria">
<h2>Success Criteria</h2>
<p>In order to advance to <a href="https://www.w3.org/Consortium/Process/#RecsPR" title="Proposed Recommendation">Proposed Recommendation</a>, each normative specification is expected to have <a href="https://www.w3.org/Consortium/Process/#implementation-experience">at least two independent implementations</a> of every feature defined in the specification.</p>
<p>Each specification should contain separate sections detailing all known security and privacy implications for implementers, Web authors, and end users.</p>
<p>There should be testing plans for each specification, starting from the earliest drafts.</p>
<p>
Each specification should contain a section on accessibility that describes the benefits and impacts, including ways specification features can be used to address them, and
recommendations for maximising accessibility in implementations.</p>
<p>To promote interoperability, all changes made to specifications should have <a href='https://www.w3.org/2019/02/testing-policy.html'>tests</a>.</p>
</section>
<section id="coordination">
<h2>Coordination</h2>
<p>For all specifications, this Working Group will seek <a href="https://www.w3.org/Guide/documentreview/#how_to_get_horizontal_review">horizontal review</a> for
accessibility, internationalization, performance, privacy, and security with the relevant Working and
Interest Groups, and with the <a href="https://www.w3.org/2001/tag/" title="Technical Architecture Group">TAG</a>.
Invitation for review must be issued during each major standards-track document transition, including
<a href="https://www.w3.org/Consortium/Process/#RecsWD" title="First Public Working Draft">FPWD</a>. The
Working Group is encouraged to engage collaboratively with the horizontal review groups throughout development of
each specification. The Working Group is advised to seek a review at least 3 months before first entering
<a href="https://www.w3.org/Consortium/Process/#RecsCR" title="Candidate Recommendation">CR</a> and is encouraged
to proactively notify the horizontal review groups when major changes occur in a specification following a review.</p>
<p>Additional technical coordination with the following Groups will be made, per the <a href="https://www.w3.org/Consortium/Process/#WGCharter">W3C Process Document</a>:</p>
<section>
<h3 id="w3c-coordination">W3C Groups</h3>
<dl>
<dt><a href="https://www.w3.org/groups/wg/webrtc">Web Real-Time Communications Working Group</a></dt>
<dd>Supply use cases, requirements, and review of specifications related to audio, including microphone access and speaker output</dd>
<dt><a href="https://www.w3.org/groups/ig/me">Media and Entertainment Interest Group</a></dt>
<dd>This Group may review existing work
and identify requirements and potential solutions to
with a view to improving media related features on the web across all devices. </dd>
<dt><a href="https://www.w3.org/groups/wg/media">Media Working Group</a></dt>
<dd>This group develops and improves client-side media processing and playback features on the Web.</dd>
<dt><a href="https://www.w3.org/groups/wg/apa">Accessible Platform Architectures (APA) Working Group</a></dt>
<dd>Ensure that audio streams from speech synthesis
are not adversely impacted by
audio streams from Web Audio.</dd>
<dt><a href="https://www.w3.org/groups/wg/publishing">Audiobooks Working Group</a></dt>
<dd>Coordinate on use of Web Audio API in <a href="https://www.w3.org/TR/audiobooks/">AudioBooks</a> and <a href="https://www.w3.org/TR/pub-manifest/">Publication Manifest</a></dd>
</dl>
</section>
<section>
<h3 id="external-coordination">External Organizations</h3>
<dl>
<dt><a href="https://whatwg.org/">WHATWG</a></dt>
<dd>Ensure that the audio APIs are compatible with the relevant HTML elements</dd>
<dt><a href="https://www.midi.org/">MIDI Manufacturers Association</a></dt>
<dd>Coordinate on the relationship between the audio API and the Musical Instrument Digital Interface protocol</dd>
<dt><a href="https://www.web3d.org/">Web3D Consortium</a></dt>
<dd>Coordinate on the use of spatial audio in
<a href="https://www.web3d.org/standards">standards for real-time 3D communication</a> </dd>
<!--
<dt><a href=""><i class="todo">[other name]</i> Working Group</a></dt>
<dd><i class="todo">[specific nature of liaison]</i></dd>
-->
</dl>
</section>
</section>
<section class="participation">
<h2 id="participation">
Participation
</h2>
<p>
To be successful, this Working Group is expected to have 6 or more active participants for its duration, including representatives from the key implementors of this specification, and active Editors and Test Leads for each specification. The Chairs, specification Editors, and Test Leads are expected to contribute half of a working day per week towards the Working Group. There is no minimum requirement for other Participants.
</p>
<p>
The group encourages questions, comments and issues on its public mailing lists and document repositories, as described in <a href='#communication'>Communication</a>.
</p>
<p>
The group also welcomes non-Members to contribute technical submissions for consideration upon their agreement to the terms of the <a href="https://www.w3.org/Consortium/Patent-Policy/">W3C Patent Policy</a>.
</p>
<p>Participants in the group are required (by the <a href="https://www.w3.org/Consortium/Process/#ParticipationCriteria">W3C Process</a>) to follow the
W3C <a href="https://www.w3.org/Consortium/cepc/">Code of Ethics and Professional Conduct</a>.</p>
</section>
<section id="communication">
<h2>
Communication
</h2>
<p id="public">
Technical discussions for this Working Group are conducted in <a href="https://www.w3.org/Consortium/Process/#confidentiality-levels">public</a>: the meeting minutes from teleconference and face-to-face meetings will be archived for public review, and technical discussions and issue tracking will be conducted in a manner that can be both read and written to by the general public. Working Drafts and Editor's Drafts of specifications will be developed in public repositories and may permit direct public contribution requests.
The meetings themselves are not open to public participation, however.
</p>
<p>
Information about the group (including details about deliverables, issues, actions, status, participants, and meetings) will be available from the <a href="https://www.w3.org/groups/wg/audio">Audio Working Group home page.</a>
</p>
<p>
Most Audio Working Group teleconferences will focus on discussion of particular specifications, and will be conducted on an as-needed basis.
</p>
<p>
This group primarily conducts its technical work
on <a id="public-github" href="https://github.com/WebAudio/web-audio-api">GitHub issues</a>.
The public is invited to review, discuss and contribute to this work.
</p>
<p>
The group may use a Member-confidential mailing list for administrative purposes and, at the discretion of the Chairs and members of the group, for member-only discussions in special cases when a participant requests such a discussion.
</p>
</section>
<section id="decisions">
<h2>
Decision Policy
</h2>
<p>
This group will seek to make decisions through consensus and due process, per the <a href="https://www.w3.org/Consortium/Process/#Consensus"> W3C Process Document (section 5.2.1, Consensus</a>). Typically, an editor or other participant makes an initial proposal, which is then refined in discussion with members of the group and other reviewers, and consensus emerges with little formal voting being required.</p>
<p>
However, if a decision is necessary for timely progress and consensus is not achieved after careful consideration of the range of views presented, the Chairs may call for a group vote and record a decision along with any objections.
</p>
<p>
To afford asynchronous decisions and organizational deliberation, any resolution (including publication decisions) taken in a face-to-face meeting or teleconference will be considered provisional.
A call for consensus (CfC) will be issued for all resolutions (for example, via email, GitHub issue or web-based survey), with a response period from one week, depending on the chair's evaluation of the group consensus on the issue.
If no objections are raised by the end of the response period, the resolution will be considered to have consensus as a resolution of the Working Group.
</p>
<p>
All decisions made by the group should be considered resolved unless and until new information becomes available or unless reopened at the discretion of the Chairs or the Director.
</p>
<p>
This charter is written in accordance with the <a href="https://www.w3.org/Consortium/Process/#Votes">W3C Process Document (Section 5.2.3, Deciding by Vote)</a> and includes no voting procedures beyond what the Process Document requires.
</p>
</section>
<section id="patentpolicy">
<h2>
Patent Policy
</h2>
<p>
This Working Group operates under the <a href="https://www.w3.org/Consortium/Patent-Policy/">W3C Patent Policy</a> (Version of 15 September 2020). To promote the widest adoption of Web standards, W3C seeks to issue Web specifications that can be implemented, according to this policy, on a Royalty-Free basis.
For more information about disclosure obligations for this group, please see the <a href="https://www.w3.org/groups/wg/audio/ipr">licensing information</a>.
</p>
</section>
<section id="licensing">
<h2>Licensing</h2>
<p>This Working Group will use the <a href="https://www.w3.org/Consortium/Legal/copyright-software">W3C Software and Document license</a> for all its deliverables.</p>
</section>
<section id="about">
<h2>
About this Charter
</h2>
<p>
This charter has been created according to <a href="https://www.w3.org/Consortium/Process/#GAGeneral">section 3.4</a> of the <a href="https://www.w3.org/Consortium/Process/">Process Document</a>. In the event of a conflict between this document or the provisions of any charter and the W3C Process, the W3C Process shall take precedence.
</p>
<section id="history">
<h3>
Charter History
</h3>
<p>The following table lists details of all changes from the initial charter, per the <a href="https://www.w3.org/Consortium/Process/#CharterReview">W3C Process Document (section 4.3, Advisory Committee Review of a Charter)</a>:</p>
<table class="history">
<tbody>
<tr>
<th>
Charter Period
</th>
<th>
Start Date
</th>
<th>
End Date
</th>
<th>
Changes
</th>
</tr>
<tr>
<th>
<a href="https://www.w3.org/2011/audio/charter/2011/">Initial Charter</a>
</th>
<td>
<i>25 March 2011</i>
</td>
<td>
<i>28 February 2013 </i>
</td>
<td>
<i>none</i>
</td>
</tr>
<tr>
<th>
<a href="https://www.w3.org/2011/audio/charter/2012/">Rechartered</a>
</th>
<td>
<i>26 September 2012</i>
</td>
<td>
<i>01 September 2014</i>
</td>
<td>
<p>The charter of this Working Group included two Recommendation-track deliverables, the Web Audio API specification and the Web MIDI API specification.
</p>
</td>
</tr>
<tr>
<th>
<a href="https://www.w3.org/2011/audio/charter/Overview-2014.html">Charter Extension</a>
</th>
<td>
<i>11 September 2014</i>
</td>
<td>
<i>01 September 2016</i>
</td>
<td>
<i>none</i>
</td>
</tr>
<tr>
<th>
<a href="https://www.w3.org/2011/audio/charter/audio-2016.html">Rechartered</a>
</th>
<td> <i>22 December 2016</i> </td>
<td> <i>22 December 2018</i> </td>
<td>
<i>Split existing Web Audio deliverable into 1.0 and 2.0. Change of document license.</i>
</td>
</tr>
<tr>
<th>
<a href="https://lists.w3.org/Archives/Member/w3c-ac-members/2018JanMar/0014.html">Chairs</a>
</th>
<td> <i>23 January 2018</i> </td>
<td> <i>22 December 2018</i> </td>
<td>
<i>Raymond Toy appointed; Joe Berkovitz steps down. </i>
</td>
</tr>
<tr>
<th>
<a href="https://lists.w3.org/Archives/Member/w3c-ac-members/2018OctDec/0067.html">Charter Extension</a>
</th>
<td> <i>22 December 2018</i> </td>
<td> <i>30 June 2019</i> </td>
<td>
<i>none</i>
</td>
</tr>
<tr>
<th>
<a href="https://lists.w3.org/Archives/Member/w3c-ac-members/2019JulSep/0019.html">Charter
Extension</a>
</th>
<td> <i>12 August 2019</i> </td>
<td> <i>31 December 2019</i> </td>
<td>
<i>none</i>
</td>
</tr>
<tr>
<th>
<a href="">Charter
Extension</a>
</th>
<td> <i>20 December 2019</i> </td>
<td> <i>14 February 2020</i> </td>
<td>
<i>none</i>
</td>
</tr>
<tr>
<th>
Rechartered
</th>
<td> 04 March 2020 </td>
<td> 04 March 2022 </td>
<td>
<i>Added new deliverable</i>
</td>
</tr>
<tr>
<th>Rechartered</th>
<td>15 December 2020</td>
<td>04 March 2022</td>
<td>New Patent Policy
<ul><li><a href="https://lists.w3.org/Archives/Member/w3c-ac-members/2021JulSep/0035.html">2021-08-31</a>: Hongchan Choi appointed as co-Chair of the group; Raymond Toy stepped down</li></ul></td>
</tr>
<tr>
<th>This charter</th>
<td>14 June 2022</td>
<td>14 June 2024</td>
<td>Rather than creating a v2.0, Web Audio API will be maintained by updating the Recommendation.</td>
</tr>
</tbody>
</table>
</section>
<section id="changelog">
<h3>Change log</h3>
<!-- Use this section for changes _after_ the charter was approved by the Director. -->
<p>Changes to this document are documented in this section.</p>
<!--
<dl id='changes'>
<dt>YYYY-MM-DD</dt>
<dd>[changes]]</dd>
</dl>
-->
</section>
</section>
</main>
<hr>
<footer>
<address>
<a href="mailto:chris@w3.org">Chris Lilley</a>
</address>
<p class="copyright">
<a href="https://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> ©
2022
<a href="https://www.w3.org/"><abbr title="World Wide Web Consortium">W3C</abbr></a><sup>®</sup>
(
<a href="https://www.csail.mit.edu/"><abbr title="Massachusetts Institute of Technology">MIT</abbr></a>,
<a href="https://www.ercim.eu/"><abbr title="European Research Consortium for Informatics and Mathematics">ERCIM</abbr></a>,
<a href="https://www.keio.ac.jp/">Keio</a>,
<a href="https://ev.buaa.edu.cn/">Beihang</a>
), All Rights Reserved.
<abbr title="World Wide Web Consortium">W3C</abbr> <a href="https://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>, <a href="https://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a> and <a href="https://www.w3.org/Consortium/Legal/copyright-documents">document use</a> rules apply.
</p>
<hr>
<p><a href="https://github.com/w3c/charter-drafts/blob/gh-pages/2022/audio-2022.html">Yes, it's on GitHub!</a>.</p>
</footer>
</body>
</html>