Audio Working Group Charter
The mission of the Audio Working Group is to add advanced sound and music synthesis capabilities to the Open Web Platform.
|Start date||22 December 2016|
|End date||22 December 2018|
Raymond Toy (Google)
Matt Paradis (BBC)
Chris Lilley (0.2 FTE)
Teleconferences: 1-hour calls will be held weekly
Face-to-face: we will meet during the W3C's annual Technical Plenary week; additional face-to-face meetings may be scheduled by consent of the participants, no more than 3 per year.
Building upon and expanding the basic functionalities brought by HTML5's
<video> media elements and
MediaStream object, the Audio Working Group defines 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
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 PCM 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.
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. MIDI 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.
The scope of this working group includes:
- Developing a client-side script API for processing and synthesizing PCM audio streams, including direct scripted solutions.
- Access to audio devices, such as for microphones or other audio inputs, and multi-channel speakers or other audio outputs.
- APIs and advanced functionality regarding audio cache management and audio capability information.
- Defining a client-side script API for accessing and manipulating MIDI-capable devices available on the users' systems.
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, such as microphones and speakers.
Out of Scope
The following features are out of scope, and will not be addressed by this Working group.
This group will not work on audio representation markup during this charter period; discussions of music notation formats happens in the Music Notation Community Group.
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.
Specific functionality for speech synthesis 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.
Audio codec selection and support is out of scope.
Each specification should contain a section detailing any known security or privacy implications for implementers, Web authors, and end users.
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.
More detailed milestones and updated publication schedules are available on the group publication status page.
Draft state indicates the state of the deliverable at the time of the charter approval. Expected completion indicates when the deliverable is projected to become a Recommendation, or otherwise reach a stable state.
The Working Group will deliver and maintain the following W3C normative specifications:
- Web Audio API 1.0
Draft state: Working Draft, being readied for CR
Expected completion: Q3 2017
- Web Audio API 2.0
This specification builds on Web Audio API 1.0, adding features which were requested by users or implementors but which were deferred to the next version of Web Audio API.
Draft state: No draft, see issues list
- Web MIDI
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.
Draft state: Working Draft
Expected completion: Q2 2018
Other non-normative documents may be created such as:
- Use case and requirement documents;
- Test suite and implementation report for the specification;
- Primer or Best Practice documents to support web developers when designing applications.
- Q4 2016: Candidate Recommendation of Web Audio API v.1
- Q2 2017: Candidate Recommendation of Web MIDI
- Q3 2017: Proposed Recommendation of Web Audio API v.1
- Q1 2018: Proposed Recommendation of Web MIDI
For all specifications, this Working Group will seek horizontal review for accessibility, internationalization, performance, privacy, and security with the relevant Working and Interest Groups, and with the TAG. Invitation for review must be issued during each major standards-track document transition, including FPWD and CR, and should be issued when major changes occur in a specification.
Additional technical coordination with the following Groups will be made, per the W3C Process Document:
- Device and Sensors Working Group
- Supply use cases, requirements, and review of specifications related to audio, including microphone access and speaker output
- Web Platform Working Group
- Ensure that the audio APIs are compatible with the relevant HTML elements
- Web and TV Interest Group
- This Group may review existing work and identify requirements and potential solutions to with a view to improving audio on the Web for TVs.
- MIDI Manufacturers Association
- Coordinate on the relationship between the audio API and the Musical Instrument Digital Interface protocol
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 a working day per week towards the Working Group. There is no minimum requirement for other Participants.
The group encourages questions, comments and issues on its public mailing lists and document repositories, as described in Communication.
The group also welcomes non-Members to contribute technical submissions for consideration upon their agreement to the terms of the W3C Patent Policy.
Technical discussions for this Working Group are conducted in public: the meeting minutes from teleconference and face-to-face meetings will be archived for public review, and technical discussions and issue tracking will be conducted in a manner that can be both read and written to by the general public. Working Drafts and Editor's Drafts of specifications will be developed on a public GitHub repository, and encourages public suggestions. The Working Group will consider such suggestions, but is not required to adopt them. The meetings themselves are not open to public participation, however.
Information about the group (including details about deliverables, issues, actions, status, participants, and meetings) will be available from the Audio Working Group wiki.
Most Audio Working Group teleconferences will focus on discussion of particular specifications, and will be conducted on an as-needed basis.
This group primarily conducts its technical work on GitHub issues. The public is invited to review, discuss and make suggestions for improvement to this work.
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.
This group will seek to make decisions through consensus and due process, per the W3C Process Document (section 3.3). 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.
However, 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 call for a group vote, and record a decision along with any objections.
To afford asynchronous decisions and organizational deliberation, any resolution (including publication decisions) taken in a face-to-face meeting or teleconference will be considered provisional. A call for consensus (CfC) will be issued for all resolutions (for example, via email and/or web-based survey), with a response period from one week to 10 working days, depending on the chair's evaluation of the group consensus on the issue. If no objections are raised on the mailing list by the end of the response period, the resolution will be considered to have consensus as a resolution of the Working Group.
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.
This charter is written in accordance with the W3C Process Document (Section 3.4, Votes), and includes no voting procedures beyond what the Process Document requires.
This Working Group operates under the W3C Patent Policy (5 February 2004 Version). To promote the widest adoption of Web standards, W3C seeks to issue Recommendations that can be implemented, according to this policy, on a Royalty-Free basis. For more information about disclosure obligations for this group, please see the W3C Patent Policy Implementation.
This Working Group will use the W3C Software and Document license for all its deliverables.
About this Charter
This charter has been created according to section 5.2 of the Process Document. 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.
The following table lists details of all changes from the initial charter, per the W3C Process Document (section 5.2.3):
|Charter Period||Start Date||End Date||Changes|
|Initial Charter||25 March 2011||28 February 2013||none|
|Rechartered||26 September 2012||01 September 2014||
The charter of this Working Group included two Recommendation-track deliverables, the Web Audio API specification and the Web MIDI API specification.
|Charter Extension||11 September 2014||01 September 2016||none|
|Rechartered||22 December 2016||22 December 2018||Split existing Web Audio deliverable into 1.0 and 2.0. Change of document license.|
|Chairs||23 Jan 2018||22 December 2018||Raymond Toy appointed; Joe Berkovitz steps down.|