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 Java Script processing and synthesis is also supported.The introductory section covers the motivation behind this specification.

W3C maintains a public list of any patent disclosures made in connection with the deliverables of the group; that page also includes instructions for disclosing a patent.

An individual who has actual knowledge of a patent which the individual believes contains Essential Claim(s) must disclose the information in accordance with section 6 of the W3C Patent Policy. Audio on the web has been fairly primitive up to this point and until very recently has had to be delivered through plugins such as Flash and Quick Time.

The introduction of the element in HTML5 is very important, allowing for basic streaming audio playback.

But, it is not powerful enough to handle more complex audio applications.

For sophisticated web-based games or interactive applications, another solution is required.

It is a goal of this specification to include the capabilities found in modern game audio engines as well as some of the mixing, processing, and filtering tasks that are found in modern desktop audio production applications.

The APIs have been designed with a wide variety of use cases in mind.

Publication as a Working Draft does not imply endorsement by the W3C Membership.

This is a draft document and may be updated, replaced or obsoleted by other documents at any time.

It is inappropriate to cite this document as other than work in progress.

This document was produced by a group operating under the 5 February 2004 W3C Patent Policy.