- From: Ralph Giles <giles@mozilla.com>
- Date: Thu, 22 Dec 2011 10:33:16 -0800
- To: David Singer <singer@apple.com>
- CC: public-texttracks@w3.org
On Thu Dec 22 10:18:24 2011, David Singer wrote: > These categories probably overlap. I'm thinking of examples like > -- "looks better if these style-sheets are used" > -- "has an overall language of en-US" > -- "is intended for this 'kind' in HTML" > -- "when used with the expected mpeg-2 transport stream, <this> VTT timestamp is (maps to) <that> MPEG-2 clock reference" > ... > Do we have proposals, or are we at the use-case and data-collection stage? I hadn't thought of your last two examples, so I'd say we're in the data-collection phase. Metadata is always open-ended, so I think we should define an extensible mechanism and pick some simple categories to standardize for initial interoperability. I would add title, author, date, translator, etc. labels. I really like the timecode offset suggestion. How would software handle this? Does the CMS Re-timestamp the webvtt file when it's deployed in conjunction with that video? Are videos referenced by string? SHA-1? Would user agents parse and apply this on the fly? -r
Received on Thursday, 22 December 2011 18:33:47 UTC