- From: David Singer <singer@apple.com>
- Date: Mon, 10 Oct 2011 17:37:18 -0700
- To: Ian Hickson <ian@hixie.ch>
- Cc: Silvia Pfeiffer <silviapfeiffer1@gmail.com>, public-texttracks@w3.org
This isn't quite answering your question, and it's not the document you agreed to write, but I suspect that it might be good to knock up a draft of the 'VTT author's guide' or the like, that 'documents' (non-normatively) what a VTT document looks like, and can contain etc. The current extract is, um, a little hard to read in that respect. That would make it easier to answer 'can I express what I want to express in this, does it have the effect I intend?'. I *think* Silvia might have wanted to write such; am I right? On Oct 10, 2011, at 17:25 , Ian Hickson wrote: > On Tue, 11 Oct 2011, Silvia Pfeiffer wrote: >> >> 4. The WebVTT specification >> >> I'm sure you're all waiting to see the WebVTT specification in a place >> where we can all start contributing. Right now, there are some licensing >> issues to be sorted through, but I hope this can be resolved very soon. > > In the meantime, people should feel free to continue sending feedback as > they have been. > > One thing that would be helpful for me as editor is determining exactly > what aspects of the HTML standard people consider to be "WebVTT" so that > we can extract just those. Is it just the syntax? Does it include the > caption data model? Are the DOM APIs part of WebVTT? Is the rendering > model part of WebVTT? How about the CSS extensions? Unfortunately the > "webvtt.html" file people may have been looking at in the past is not a > particularly good starting point as it is very coarse -- it's missing huge > chunks of defining material (e.g. there's no conformance section). > > -- > Ian Hickson U+1047E )\._.,--....,'``. fL > http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,. > Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.' > David Singer Multimedia and Software Standards, Apple Inc.
Received on Tuesday, 11 October 2011 00:37:59 UTC