- From: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
- Date: Mon, 14 Nov 2011 18:30:17 +1100
- To: Jim King <jking@adobe.com>
- Cc: Ian Hickson <ian@hixie.ch>, "public-texttracks@w3.org" <public-texttracks@w3.org>
Hi all, I have been thinking about the structure of those documents that we will create around WebVTT. As stated, I think we need two documents: one targeted at video players that display captions (which includes browsers, but not exclusively), and a second one that is a tutorial targeted at caption authors or authoring applications (as Jim put it: "someone who is creating time text material can read to figure out what to output"). Here are roughly the table of contents that I would imagine for these documents: WebVTT Specification ================= 1. Syntax 2. Conformance requirements & extensibility 3. Parsing 4. Rendering (HTML/CSS-independent - more like the caption model) 5. MIME type registration Appendix: A. WebVTT and Web Browsers A.1. WebVTT cue text DOM construction rules A.2. Applying CSS properties to WebVTT Node Objects A.3. CSS extensions WebVTT Tutorial ============= 1. WebVTT file structure 2. WebVTT file header sections 3. WebVTT cue format 4. WebVTT cue settings 5. WebVTT cue content tags Since Ian will be editing the WebVTT Specification, this is also an attempt to figure out what exactly goes into this document - a question that Ian asked earlier. Did I miss anything? Cheers, Silvia.
Received on Monday, 14 November 2011 07:31:14 UTC