- From: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
- Date: Thu, 28 Oct 2010 17:50:51 +1100
- To: John Foliot <jfoliot@stanford.edu>
- Cc: Frank Olivier <Frank.Olivier@microsoft.com>, HTML Accessibility Task Force <public-html-a11y@w3.org>
On Thu, Oct 28, 2010 at 5:08 PM, John Foliot <jfoliot@stanford.edu> wrote: >> <Frank.Olivier@microsoft.com> wrote: >> > Overall feedback from the Internet Explorer team: >> > >> > Option 1 - Overloading <track> and keeping the DOM parsing very >> simple would be the most elegant way to proceed, with every track >> having a 'kind' attribute - Generally, I expect to be able to activate >> a single alternate track of a particular type (Also, this would also >> sync up well with a simple javascript API - I would expect that I (as >> an author) would be able to enumerate a flat list of alternate >> representations, with metadata that indicates the kind. > > There has been some mention of metadata here before. I am curious as to > how and what this metadata might look like (as I am unsure of this). Do > you have a specific spec or idea regarding this metadata (schema)? Oh, I did not mean to refer to the full list of metadata that you can think about for video (in fact, that work is being done in the W3C Media Annotations WG). Sorry for the confusion. I only meant to refer to three specific attributes that are absolutely necessary wrt multitrack media: @kind, @language, and @label. They will help create a menu through which a user can interactively activate/deactivate a track, and they will help the same way in the JavaScript API or in user preferences. If you are interested in metadata for video, you might be curious to read my recent blog post about "your metadata is not my metadata" at http://blog.gingertech.net/2010/10/01/your-metadata-is-not-my-metadata/ which talks a lot more about the different types of metadata that we have to deal with for video. Cheers, Silvia.
Received on Thursday, 28 October 2010 06:51:53 UTC