Re: Updated WebVTT spec with region specification

On Mon, Jul 8, 2013 at 3:55 AM, Silvia Pfeiffer
<silviapfeiffer1@gmail.com> wrote:
> On Sat, Jul 6, 2013 at 12:42 PM, Silvia Pfeiffer
> <silviapfeiffer1@gmail.com> wrote:
>>
>> 7. WebVTT API for Browsers
>>   7.1 WebVTTCue interface
>>   7.2 Extension of the TextTrack interface for region support
>>   7.3 Extension of the TextTrackCue interface for region support
>>   7.4 TextTrackRegion interface
>>   7.5 TextTrackRegionList interface
>
> I've already noticed one bug and am fixing it: section 7.3 should not
> extend the TextTrackCue, but the WebVTTCue. So, I'm dropping that
> section.
> I'm also renaming WebVTTCue to VTTCue (see
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=22020 ).
>
>
> Also, what do people think about the TextTrackRegion interface. Should
> that be restricted to WebVTT files?
> My original motivation for creating a generic TextTrackRegion rather
> than a VTTRegion was that other files (in particular CEA708 and TTML
> files) also have regions with similar properties. But I may be
> assuming too much.
>
> I'm thinking of renaming TextTrackRegion to VTTRegion and
> TextTrackRegionList to VTTRegionList.

I personally think such a rename is appropriate, since regions were
developed as an extension to WebVTT in order to cover features that
don't exist there (and this isn't true for TTML or CEA708).

> And we would not add the TextTrackRegionList to the TextTrack object,
> but create a VTTTrack object with these extended interfaces.

Could you elaborate a bit more on this? I'm tempted to say that it's
not necessarily worth going with the TextTrack object in the same
direction as with TextTrackCue only because of VTTRegions, unless
there are other track-level specific attributes (even for other
formats) that might lead anyway to such a separation later.

Victor

Received on Tuesday, 9 July 2013 15:42:59 UTC