Rechartering

[svgeesus]

Our current charter expires 08 November 2026.

I have prepared a draft charter which is now open for Audio WG review. It is basically the same as the current one, updated as needed from the charter template.

I expect to update the deliverables section once an updated WD of Web Audio API 1.1 is published

[hoch]

Following up on @padenot thought about the Web Speech API and our upcoming charter renewal in November, here are some thoughts on how we might shape the new charter:

1. Adopting Web Speech API:
   I think bringing Web Speech into the Audio WG makes a lot of sense. Keeping it as a single unified spec (covering both synthesis and recognition) feels like the cleanest path and preserves continuity with the current CG report.
2. Spec Editorship:
   I am considering:
   • Web Audio API 1.1: Bringing in @mjwilson-google as a new spec editor, who has been actively driving many of the recent spec changes and fixes.
   • Web Speech API: @padenot and @evanbliu can continue on editorship for the speech spec.
   • Of course, we'd love to co-edit alongside anyone from Apple/WebKit or the community who wants to join in!
3. Tentative Roadmap / Milestones (2026–2028):
   • Web Audio 1.1: Aim for Recommendation by 2028.
   • Web MIDI: Candidate Recommendation by 2027.
   • Web Speech: Transition from CG to FPWD early 2027, then push toward Candidate Recommendation by 2028.

What do you all think? Let's chat here and we can put it on the agenda for our next call!

@mdjp @padenot @mjwilson-google @evanbliu

[svgeesus]

I agree that adding Web Speech in scope makes a lot of sense.

The editorship changes sound good to me also.

Milestones, I wish we didn't have to estimate them since the estimates are rarely correct but these will do fine for rechartering.

[svgeesus]

I expect to update the deliverables section once an updated WD of Web Audio API 1.1 is published

Following publication, that change is done. Web Speech API also added to tentative deliverables.