- From: Chris Wilson <cwilso@google.com>
- Date: Tue, 19 Mar 2019 14:47:58 -0700
- To: Chris Lilley <chris@w3.org>
- Cc: "public-audio@w3.org Group" <public-audio@w3.org>
- Message-ID: <CAJK2wqWyFJP0o1TPB0q9J1oEKuer=9DbePUoZY6KHh4EwRBbYA@mail.gmail.com>
(Sorry, was on jury duty) There are actually 9 issues currently marked "ready for editing". I have been derelict. :/ (However, I removed it from that issue, as Hongchan rightly pointed out that AudioWorklet might be a more appropriate place to add it.) I think we should go ahead and republish now, and I'll try to wrap up all the ready-for-editing bits in the next two months. On Fri, Mar 15, 2019 at 7:22 AM Chris Lilley <chris@w3.org> wrote: > Hi > > The last publication of Web MIDI was four years ago, 17 March 2015 > > https://www.w3.org/TR/webmidi/ > > While there hasn't been a huge amount of change, the editors draft does > have some updates and is more recent, with several issues updated. Last > edit 17 December 2018 > > https://github.com/WebAudio/web-midi-api/commits/gh-pages/index.html > http://webaudio.github.io/web-midi-api/ > > This is just a Working Draft not a Candidate Recommendation, so > republishing merely requires this group to agree to do so, and then I > can take care of the rest. > > Chris, are there any important pending edits that you want to fold in > before that happens? I see one issue marked `ready for editing` although > that label was added in 2015 so maybe it isn't something that can be > folded in quickly: > > MIDI API should be available from Workers? #99 > https://github.com/WebAudio/web-midi-api/issues/99 > > instead, the best approach and v.1/v.next should probably be discussed > on a call. > > -- > Chris Lilley > @svgeesus > Technical Director @ W3C > W3C Strategy Team, Core Web Design > W3C Architecture & Technology Team, Core Web & Media > >
Received on Tuesday, 19 March 2019 21:48:34 UTC