Re: Web Audio API is now a W3C Candidate Recommendation (Call for Implementations)

Thanks for forwarding - agreed, it looks more interesting for implementors than standardizers. 

> On Sep 18, 2018, at 12:50 PM, Daniel Weck <daniel.weck@gmail.com> wrote:
> 
> Hello,
> Like the HTML5 Audio element, the Web Audio API can be a useful building block for reading system developers (i.e. implementors of EPUB3 Media Overlays, "audio books" Web Publications, etc.), and it can also be a useful tool for content creators (e.g. publications with sounds cues, interactive aural user experiences, etc.).
> However I do not think that the Web Publications standard needs to specifically reference (normatively or informatively) the Web Audio API, consequently I do not think that this "affects our work on audio books / Sync media". In my view, Web Audio is an important enabling technology on the Open Web Platform, but it is not central to standardizing Web Publications and its audio "derivations".
> Regards, Daniel
> 
> 
> On Tue, 18 Sep 2018 at 14:49, Siegman, Tzviya <tsiegman@wiley.com <mailto:tsiegman@wiley.com>> wrote:
> Hi All,
> 
> I know almost nothing about audio, so I may be way off, but does this affect our work on audio books? Sync media?
> 
> Thanks,
> Tzviya
> 
> Tzviya Siegman
> Information Standards Lead
> Wiley
> 201-748-6884
> tsiegman@wiley.com <mailto:tsiegman@wiley.com> 
> 
> -----Original Message-----
> From: Xueyuan [mailto:xueyuan@w3.org <mailto:xueyuan@w3.org>] 
> Sent: Tuesday, September 18, 2018 9:21 AM
> To: w3c-ac-forum@w3.org <mailto:w3c-ac-forum@w3.org>
> Cc: chairs@w3.org <mailto:chairs@w3.org>
> Subject: Web Audio API is now a W3C Candidate Recommendation (Call for Implementations)
> 
> 
> Dear Advisory Committee Representative,
> Chairs,
> 
> I am pleased to announce that Web Audio API is a W3C Candidate
> Recommendation:
>    https://www.w3.org/TR/2018/CR-webaudio-20180918/ <https://www.w3.org/TR/2018/CR-webaudio-20180918/>
> 
> The approval and publication are in response to this transition request:
>    https://github.com/w3c/transitions/issues/89 <https://github.com/w3c/transitions/issues/89>
> 
> Please provide feedback by 12 December 2018 as follows:
>    raise an issue on GitHub
>    https://github.com/WebAudio/web-audio-api/issues <https://github.com/WebAudio/web-audio-api/issues>
> 
> Patent disclosures relevant to this specification may be found on the Audio Working Group's patent disclosure page in conformance with W3C policy:
>    https://www.w3.org/2004/01/pp-impl/46884/status <https://www.w3.org/2004/01/pp-impl/46884/status>
> 
> This Call for Implementations follows section 6.4 "Candidate Recommendation" of the W3C Process Document:
>    https://www.w3.org/2018/Process-20180201/#candidate-rec <https://www.w3.org/2018/Process-20180201/#candidate-rec>
> 
> Thank you,
> 
> For Tim Berners-Lee, Director, and
> Philippe Le Hégaret, Project Management Lead; Xueyuan Jia, W3C Marketing & Communications
> 
> ==============================================
> Quoting from
> Web Audio API
> W3C Candidate Recommendation, 18 September 2018
> 
> This version:
>    https://www.w3.org/TR/2018/CR-webaudio-20180918/ <https://www.w3.org/TR/2018/CR-webaudio-20180918/>
> Latest published version:
>    https://www.w3.org/TR/webaudio/ <https://www.w3.org/TR/webaudio/>
> 
> Abstract:
> 
> This specification describes a high-level Web 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 script processing and synthesis is also supported.
> 
> The Introduction section covers the motivation behind this specification.
> 
> This API is designed to be used in conjunction with other APIs and elements on the web platform, notably: XMLHttpRequest [XHR] (using the responseType and response attributes). For games and interactive applications, it is anticipated to be used with the canvas 2D [2dcontext] and WebGL [WEBGL] 3D graphics APIs.
> 
> Status of this document:
> 
> This section describes the status of this document at the time of its publication. Other documents may supersede this document. A list of current W3C publications and the latest revision of this technical report can be found in the W3C technical reports index at https://www.w3.org/TR/ <https://www.w3.org/TR/>.
> 
> This document was published by the the Web Audio Working Group as a Candidate Recommendation. This document is intended to become a W3C Recommendation. This document will remain a Candidate Recommendation at least until 12 December 2018 in order to ensure the opportunity for wide review.
> If you wish to make comments regarding this document, please file an issue on the specification repository or send them to public-audio@w3.org <mailto:public-audio@w3.org> (subscribe, archives).
> 
> A preliminary implementation report is available.
> 
> Publication as a Candidate Recommendation 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 W3C Patent Policy. 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.
> 
> This document is governed by the 1 February 2018 W3C Process Document.
> ==============================================
> 
> 
> 
> 
>