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

Re: Systematic access to media/plugin metadata

From: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
Date: Wed, 13 Apr 2011 11:48:46 +1000
Message-ID: <BANLkTikezbGeSNKXnsUeJTLSe5GcZ909xw@mail.gmail.com>
To: Eric Carlson <eric.carlson@apple.com>
Cc: Danny Ayers <danny.ayers@gmail.com>, "public-html@w3.org (public-html@w3.org)" <public-html@w3.org>
On Wed, Apr 13, 2011 at 6:46 AM, Eric Carlson <eric.carlson@apple.com> wrote:
>
> On Apr 12, 2011, at 1:25 PM, Danny Ayers wrote:
>
>> On 12 April 2011 22:13, Eric Carlson <eric.carlson@apple.com> wrote:
>>
>>>  First, meta-data is stored and interpreted differently in different media file formats so this would have to be done for every format.
>>
>> This doesn't necessarily follow, in fact I'd turn it around - if there
>> was a generic API for access to metadata, the material could be
>> exposed consistently for any formats that were supported.
>>
>>> Therefore I it is out of scope for the HTML WG.
>>
>> There is already a model specified for media elements, for example a
>> media element may have text tracks which have labels. This is
>> specified without dependence on any specific formats. The same
>> approach could easily be extended to include other pieces of metadata.
>>
>  My point was that as far as I know, no media file format has a standard way to mark a text track as a "transcript". Therefore the media format specific metadata has to be defined, eg. what 'udta' or 'meta' value signals a transcript in a QuickTime/MPEG-4 file, before the HTML WG can define a mapping to it.


I think it's worse even: transcripts that are meant to be received as
alternatives to video cannot be delivered inside video and the
inherent timing that encapsulation in video brings is not useful
either. So, in-band delivery of transcripts is utterly useless IMHO.

Cheers,
Silvia.
Received on Wednesday, 13 April 2011 01:49:33 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:17:28 GMT