- From: Chris Lilley <chris@w3.org>
- Date: Mon, 9 Feb 2015 23:21:50 +0100
- To: Joseph Berkovitz <joe@noteflight.com>
- CC: Doug Schepers <schepers@w3.org>, Audio WG <public-audio@w3.org>
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> 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 Monday, 9 February 2015 22:21:55 UTC