W3C home > Mailing lists > Public > public-media-annotation@w3.org > February 2010

Re: awareness of HTML5 media multitrack API

From: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
Date: Wed, 17 Feb 2010 23:02:24 +1100
Message-ID: <2c0e02831002170402h41badf94k99a6c409e43574c9@mail.gmail.com>
To: "Bailer, Werner" <werner.bailer@joanneum.at>
Cc: "public-media-annotation@w3.org" <public-media-annotation@w3.org>
On Wed, Feb 17, 2010 at 7:24 PM, Bailer, Werner
<werner.bailer@joanneum.at> wrote:
> Dear Silvia,
>
> Thanks for bringing this to our attention.
>
> I think the relation to our API is discovering the tracks and getting their properties (identifier, role, type, language). This issue was raised by RaphaŽl some time ago [1]. The result of the short discussion on the list was that ma:fragments needs to return also track and not just temporal/spatial fragments to support this. I think we have not reached a formal decision on this, so I suggest to put it on the agenda of the F2F meeting next week.
>
> This would allow querying for the list of tracks using ma:fragments, and then you could request further properties for each of the tracks. We could think about providing also a shortcut here, i.e. function that returns the list of track objects and their properties. Any views on this from Chris, Florian, Wonsuk, others?
>

I'm actually happy right now with the statement that such an API does
not interfere with what you're doing, but can work with it. It sounds
like the multitrack media API is orthogonal to the metadata API that
you are specifying, so that is good. I just want to make sure to
re-use where sensible, or interoperate with other W3C approaches.

Cheers,
Silvia.
Received on Wednesday, 17 February 2010 12:03:16 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 17 February 2010 12:03:17 GMT