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

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

From: <bugzilla@jessica.w3.org>
Date: Mon, 26 Sep 2011 22:26:03 +0000
To: public-html-a11y@w3.org
Message-Id: <E1R8Jch-0005We-R9@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=13359

Ian 'Hixie' Hickson <ian@hixie.ch> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         AssignedTo|ian@hixie.ch                |contributor@whatwg.org

--- Comment #18 from Ian 'Hixie' Hickson <ian@hixie.ch> 2011-09-26 22:26:02 UTC ---
(In reply to comment #13)
> 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

Yes it can. P1...P4 would just tell O what they are. I don't understand the
problem here. This is a well-established pattern on the Web. An aggregator site
gets information from third parties and those parties tell the aggregator
exactly what they are providing, so that the aggregator can make use of it.
Sometimes the aggregator explicitly specifies the format (e.g. Google Maps'
transit directions feature has a specified format that transit companies can
use), sometimes it's the other way around (e.g. Yahoo! Finance pulls
information in from a number of different sources each of which might use its
own format). Either way, though, the aggregator knows what the format of the
data is.

-- 
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 Monday, 26 September 2011 22:26:05 GMT

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