W3C home > Mailing lists > Public > public-html-a11y@w3.org > August 2011

[Bug 13359] A way is needed to identify the type of data in a track element

From: <bugzilla@jessica.w3.org>
Date: Tue, 23 Aug 2011 05:52:03 +0000
To: public-html-a11y@w3.org
Message-Id: <E1Qvju7-0005Pu-IR@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=13359

--- Comment #13 from Glenn Adams <glenn@skynav.com> 2011-08-23 05:52:03 UTC ---
(In reply to comment #12)
> Please note that there is no reason to quote the entirety of a comment when
> replying. Either quote nothing or quote just what you are responding to.
> 
> 
> Is there a _concrete_ example here? I really don't understand the use case
> being presented. Re comment 3, for example, why would O be exposing content
> from P?

CableTVCorp (O) creates an electronic program guide with a page depicted as a
grid of videos V1...V4 provided by 3rd party content providers P1...P4.
V1...V4, in turn, contain or refer to timed track metadata content (e.g., video
descriptions, etc), which UA (upon decoding V1...V4) expose to O's JS client
code via TextTrackCue.getCueAsSource(). O does not (generally cannot) a priori
know the timed track metadata content type, however, the UA does (or can) know
it, since it decoded V1...V4 and was responsible for exposing the cue data to
JS in the first place.

Knowing the actual content type of metadata M1...M4 (associated with V1...V4),
O's JS client code can decode cue data and use it for various purposes, e.g.,
to annotate chapters and scenes being depicted in grid on V1...V4, etc.

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Received on Tuesday, 23 August 2011 05:52:09 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 04:42:44 GMT