- From: Doug Schepers <schepers@w3.org>
- Date: Wed, 18 Feb 2015 09:03:01 -0500
- To: Joseph Berkovitz <joe@noteflight.com>, Chris Lilley <chris@w3.org>, Chris Wilson <cwilso@google.com>, Jussi Kalliokoski <jussi.kalliokoski@gmail.com>
- CC: Audio WG <public-audio@w3.org>
Hi, ChrisW, Jussi– In prepping the Web MIDI API spec for publication, we made a few changes that you may want to sync up with the Editor's Draft: * added a Feedback link to the Audio WG mailing list in the heading list * updated the copyright statement (this is administrivia, but it currently says 2012-2015, when it should just say 2015) * added "editor-data-id" attributes to the editor DDs * fixed some duplicate IDs: ** idl-def-ForEachCallback (changed to idl-def-MIDIInputMap-ForEachCallback and idl-def-MIDIOutputMap-ForEachCallback) ** widl-ForEachCallback-id (changed to widl-MIDIInputMap-ForEachCallback-id and widl-MIDIOutputMap-ForEachCallback-id) ** widl-ForEachCallback-port (changed to widl-MIDIInputMap-ForEachCallback-port and widl-MIDIOutputMap-ForEachCallback-port) * fixed a couple broken links: ** fragment #event-midiacces-disconnect (text "MIDIConnectionEvent") was not found, so I replaced the link with #idl-def-MIDIConnectionEvent (like other links with the same text) ** http://avd.io was 404, so I changed the link to http://juss.in/ If any of these changes are incorrect, please let me know. The document is prepped and will be published on Thursday. Regards– –Doug On 2/11/15 10:29 AM, Joseph Berkovitz wrote: > Hi Chris, > > Since it is so very easy: please consider this a request to publish a > new update to the Web MIDI API Working Draft. Thank you so much. > > Best, > > . . . . . ...Joe > > *Joe Berkovitz* > President > > *Noteflight LLC* > Boston, Mass. > phone: +1 978 314 6271 > www.noteflight.com <http://www.noteflight.com> > "Your music, everywhere" > > On Feb 9, 2015, at 4:21 PM, Chris Lilley <chris@w3.org > <mailto:chris@w3.org>> wrote: > >> Hello Joseph, >> >> Monday, February 9, 2015, 7:17:22 PM, you wrote: >> >>> I’ll wait to hear from the editors, but of course I’d love to get >>> the ball rolling (I’ll need a bit of help understanding the mechanics >>> of same). >> >> Its an update to a Working Draft so its easy. The WG decides to >> publish, tells me to do it, and I do it. >> >> >>> …Joe >> >> >>> On Feb 9, 2015, at 1:07 PM, Doug Schepers <schepers@w3.org >>> <mailto:schepers@w3.org>> wrote: >> >>> Hey, folks– >> >>> I was informed that the Editor's Draft link on the Web MIDI API is >>> wrong; it points to the ED for the Web Audio API. >> >>> I requested permission to update this spec in place, but was told >>> it's against our current policy (which, thankfully, seems to be >>> changing soon); we don't change our specs in TR after publication >>> (not even metadata, apparently). >> >>> Instead, I was told to publish a new draft with the correct link in >>> place. >> >>> We should publish a new draft of the Web MIDI API anyway, to meet >>> heartbeat publication requirements (normally every 3 months... we're >>> about 5 publications behind ^_^). >> >>> Would the editors be okay with publishing a new draft? (Are there >>> any changes that can be reflected in a new draft? Or, perhaps, >>> issues that could be resolved quickly?) >> >>> If so, would the Chairs be willing to get this ball rolling, by >>> putting out a RFC for publication? >> >>> Regards– >>> –Doug >> >> >> >> >>> >> >>> >> >> >> -- >> Best regards, >> Chris Lilley, Technical Director, W3C Interaction Domain >> > >
Received on Wednesday, 18 February 2015 14:03:13 UTC