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

http://www.w3.org/Bugs/Public/show_bug.cgi?id=13359

--- Comment #7 from Silvia Pfeiffer <silviapfeiffer1@gmail.com> 2011-08-20 07:12:03 UTC ---
(In reply to comment #6)
> (In reply to comment #5)
> > (In reply to comment #4)
> > > (In reply to comment #3)
> > > To expand, consider 3rd party P adding three in-band signaling tracks: IB1 -
> > > content advisories for parental control, IB2 - SCTE35 segment descriptors for
> > > targeted advertising and IB3 - EISS for interactive television. The user agent
> > > executing Page O recognizes these in-band tracks and sources them as three
> > > different track elements with kind = metadata as described in [1]. Since the
> > > user agent knows how to recognize these in-band tracks it can inform JS of the
> > > metadata type by a new TextTrack.type IDL attribute. Without this new
> > > attribute, JS will have to contain logic to infer the metadata type, redoing
> > > what the UA has already done.
> > 
> > How would a general-purpose UA (such as Opera, Chrome, Safari or Firefox)
> > recognize IB1, IB2, and IB3? They are not specified in HTML so there is no
> > requirement for them to be able to decode them and I haven't seen any moves
> > that spans across these and other UAs to make IB1-3 a standard-supported format
> > in them. If there is, then it would make a lot more sense to have actual
> > kind=IB1-3 values as part of the spec IMHO.
> 
> There is no requirement that an HTML5 UA decode PNG files, JPEG files, MPEG
> video, or even JavaScript or CSS for that matter. So what's the point of your
> question?

There is also no field in HTML that provides a hint on which image file format
is being used. Why would there need to be one that hints on which metadata
format is being used?

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Saturday, 20 August 2011 07:12:05 UTC