W3C home > Mailing lists > Public > public-audio@w3.org > April to June 2012

Re: Web MIDI API test suite

From: olivier Thereaux <olivier.thereaux@bbc.co.uk>
Date: Fri, 8 Jun 2012 12:32:13 +0100
Cc: <public-audio@w3.org>
Message-Id: <76B1D88F-06A0-47FF-9D55-F13F1E7EDE23@bbc.co.uk>
To: Jussi Kalliokoski <jussi.kalliokoski@gmail.com>
Hi Jussi,


On 8 Jun 2012, at 10:25, Jussi Kalliokoski wrote:
> I have now released a test suite [1] for the Web MIDI API as it's currently specified. It's a really basic test suite to see if the features are there, not if they work that correctly (as JS has no other means of accessing MIDI devices, proper functionality testing is almost impossible). The test obviously requires user input for getting the MIDIAccess object, otherwise it's quite automatic.

That's awesome. What would it take to have it hosted (and versioned) in the Audio WG's space?

> In other news, I wanted ask about how W3C defines "independent implementations of a spec", in regard of Spec Advancement[2]. Because I'm currently working on a node module that serves the Web MIDI API for node (and it passes the test suite, yay), I'm wondering if it counts as an implementation? Or if midibridge does? Or are only browser engines counted?

If it implements all the feature in the spec within a given class of product, it will be considered an independent implementation. Doesn't have to be a browser engine.

http://www.w3.org/TR/qaframe-spec/#what-conform

Olivier

Received on Friday, 8 June 2012 11:32:44 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 8 June 2012 11:32:44 GMT