- From: David Singer <singer@apple.com>
- Date: Wed, 29 Aug 2012 17:55:01 -0700
- To: Ian Hickson <ian@hixie.ch>
- Cc: public-texttracks <public-texttracks@w3.org>
I'll respond to the other points later, but… On Aug 29, 2012, at 17:46 , Ian Hickson <ian@hixie.ch> wrote: > What data are we talking about here, anyway? <track> only has four > relevant attributes as far as I can tell; srclang="" will be dealt with > inline via this bug: > > https://www.w3.org/Bugs/Public/show_bug.cgi?id=15922 which has a key: value syntax: "File-level would look like this: WEBVTT language: fr " > WebVTT already has a way to extend it to support new data blocks like > style, as is also discussed in that bug. I don't see why we'd want to use > a complicated name-value pair syntax for embedding CSS. seems pretty simple for me (described in remarkably little prose), and provides excellent forward-compatibility, to have a general structure which we then use, rather than ad-hoc'ing every individual case. It's not as if name-value pairs are even an uncommon design approach. Seems to work for HTTP, for example. > As in: > > WEBVTT > > 00:11.000 --> 00:13.000 > <v Roger Bingham>We are in New York City > > OFFSET -01:00.000 > > 01:13.000 --> 01:16.000 > <v Roger Bingham>We're actually at the Lucern Hotel, just down the > > ...or some such. I can't see how you could do that in a backwards-compatible fashion. David Singer Multimedia and Software Standards, Apple Inc.
Received on Thursday, 30 August 2012 00:55:50 UTC