[Bug 25354] [DataCue] data attribute should be ArrayBuffer?

https://www.w3.org/Bugs/Public/show_bug.cgi?id=25354

--- Comment #14 from Eric Carlson <eric.carlson@apple.com> ---
(In reply to Silvia Pfeiffer from comment #12)
> (In reply to Edward O'Connor from comment #0)
> > Some media frameworks do not make raw metadata available, but only a parsed
> > form (which we can expose on .value as proposed in bug 25353). Because UAs
> > built on such media frameworks may not have access to the raw metadata, we
> > should make .data optional.
> 
> Is the use case here indeed ID3 tags? I am not aware of ID3 being a timed
> metadata format - I always thought it's just providing file metadata at the
> beginning of the file. That doesn't map into the text tracks model of
> time-aligned cues IMHO.

The proposal is meant to make it easier to consume any metadata format that a
UA is able to parse. 

ID3 is one such format. An ID3 tag can be located anywhere in an MP3 bit
stream, not just at the beginning or end. This means that an ID3 tags can show
up at arbitrary times in an MP3 stream, which would seem to map nicely to what
we have been calling time-aligned metadata.

Apple's HTTP Live streams can also include timed metadata within the
audio/video stream (whether live or stored). HLS supports inclusion of metadata
in ID3 format.

Shoutcast streams can also have timed metadata although the metadata isn't
necessarily ID3 tags, the metadata blocks can be simple text strings with
name-value pairs.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Monday, 21 April 2014 17:27:38 UTC