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

RE: [media] WHATWG started requirements collection for time-aligned text

From: Frank Olivier <franko@microsoft.com>
Date: Thu, 22 Apr 2010 15:28:34 +0000
To: Sean Hayes <Sean.Hayes@microsoft.com>, Eric Carlson <eric.carlson@apple.com>, Dick Bulterman <Dick.Bulterman@cwi.nl>
CC: Ian Hickson <ian@hixie.ch>, HTML Accessibility Task Force <public-html-a11y@w3.org>
Message-ID: <DBB7A800D05F0C44A5EBA0231C567C39288AC616@TK5EX14MBXW652.wingroup.windeploy.ntdev.microsoft.com>
I agree with Sean; converting between captioning formats is a trivial problem; the harder (and more pressing) problem is getting some form into support into widespread usage by all browsers.

-----Original Message-----
From: public-html-a11y-request@w3.org [mailto:public-html-a11y-request@w3.org] On Behalf Of Sean Hayes
Sent: Thursday, April 22, 2010 8:24 AM
To: Eric Carlson; Dick Bulterman
Cc: Ian Hickson; HTML Accessibility Task Force
Subject: RE: [media] WHATWG started requirements collection for time-aligned text

It seems to me that we are once again heading towards the impasse that happened when trying to bless a single video and audio codec. It seems likely to me that the solution should focus on how the association is made, where it shows up, and if necessary (which I don't think it is) any API or event model associated, and not get bogged down in which format has the most friends.

-----Original Message-----
From: public-html-a11y-request@w3.org [mailto:public-html-a11y-request@w3.org] On Behalf Of Eric Carlson
Sent: Thursday, April 22, 2010 3:55 PM
To: Dick Bulterman
Cc: Ian Hickson; HTML Accessibility Task Force
Subject: Re: [media] WHATWG started requirements collection for time-aligned text


On Apr 22, 2010, at 7:12 AM, Dick Bulterman wrote:

> On the timed text tracks, I would (once again) like to suggest that rather than inventing yet another form of timed text, the WHATWG look at the work on smilText. This format can be dropped into HTML-5 with little or no change and provides the following advantages:
> 1. It supports absoulte and relative timing of text fragments, 2. It 
> allows CSS to be used for styling text objects 3. It is intuitive for 
> hand-authors, but can also be generated 4. It is structured into a 
> basic module, a styling module and a text motion module, so that 
> growth is possbile 5. It can be supported in an external file as a streaming format or in-line.
> 
> The disadvantages?
> 1. It was not invented by this group.
> 
  How is this a disadvantage?

  Or are just being snarky? If so, how does that help us make a decision - how does it encourage anyone to consider your proposal?

eric
Received on Thursday, 22 April 2010 15:29:15 GMT

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