W3C home > Mailing lists > Public > public-html-a11y@w3.org > March 2010

Re: Moving forward with MultiTrack API [was: Agenda: HTML-A11Y 18 March HEADS UP! at 15:00Z]

From: Maciej Stachowiak <mjs@apple.com>
Date: Fri, 19 Mar 2010 12:32:37 -0700
Cc: Dick Bulterman <Dick.Bulterman@cwi.nl>, Janina Sajka <janina@rednote.net>, HTML Accessibility Task Force <public-html-a11y@w3.org>
Message-id: <FC4DCDF9-8536-4E12-8B4E-E313C55620C9@apple.com>
To: "Michael(tm) Smith" <mike@w3.org>

On Mar 18, 2010, at 11:25 PM, Michael(tm) Smith wrote:

>
> Before the broader issue of lack of integration of explicit timing
> in HTML5 arose, we seemed within the task force to have a
> prevailing consensus that the Multitrack API was viable enough as
> a proposal within the requirements it is scoped for (which are
> bound by the current design of the media elements in the HTML5
> spec) that we were ready to proceed with putting it forward for
> wider discussion within the HTML WG.
>
> So I would like to propose that we do go ahead and move forward
> with it, along with explicitly noting for the record that you are
> working in parallel on putting together a note (or change
> proposal?) for the broader issue of integration of explicit timing
> in HTML5, and with the understanding that your work on that can
> proceed in parallel to further discussion within the HTML WG of
> the Multitrack API as it is currently scoped.

+1
Received on Friday, 19 March 2010 19:33:11 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 04:42:06 GMT