Re: ISSUE-163 navigating-tracks: Chairs Solicit Change Proposals

On Wed, 06 Jul 2011 14:56:12 +0200, Silvia Pfeiffer  
<silviapfeiffer1@gmail.com> wrote:

>>> For WebVTT I am expecting a discussion in the WHATWG, since it's not
>>> specified in this WG. There is bugs that track this, see
>>> http://www.w3.org/Bugs/Public/show_bug.cgi?id=12662 .
>>
>> OK, thanks.
>
> Do you also think this approach of putting hierarchies inside cues is
> simpler than building hierarchical structures through separate cues,
> or even with separate tracks? Or do you have a nicer way of dealing
> with DAISY-like requirements?

There are a few things with  
<http://www.w3.org/WAI/PF/HTML/wiki/Media_Navigation> that I'm not a fan  
of:

  * I seems a bit random to me to represent top-level chapters as time  
ranges, but sub-chapters as time cues.
  * There can be no more than two levels. Not a big deal, but all else  
equal not having this limitation would be better.
  * New WebVTT markup and somewhat magic transformation to HTML.

Something that could be trivially parsed by both web browsers and scripts  
would be nicer, IMO. If you consider that a chapter is a range, you can  
build a chapter tree by just looking at which chapters are contained  
within another. Example:

WEBVTT

00:00:00.000 --> 00:00:10.700
Title Slide

00:00:10.700 --> 00:00:47.600
Introduction by Naomi Black

00:00:47.600 --> 00:07:37.900
Talk on WebVTT

00:00:47.600 --> 00:01:50.100
Impact of Captions on the Web

00:01:50.100 --> 00:03:33.000
Requirements of a Video text format

00:03:33.000 --> 00:04:57.766
Simple WebVTT file

00:04:57.766 --> 00:06:16.666
Styled WebVTT file

00:06:16.666 --> 00:07:37.900
Internationalized WebVTT file

 From this you could programmatically find the chapter tree. It also has  
the benefit that it's possible to use this as a visible track for  
debugging purposes, as all currently active chapters would be visible.  
With some script+CSS I suppose it might even be a useful technique in  
production. The only downside that I can see is that it's a bit tricky to  
author.

-- 
Philip Jägenstedt
Core Developer
Opera Software

Received on Wednesday, 6 July 2011 13:50:47 UTC