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

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

--- Comment #8 from Eric Carlson <eric.carlson@apple.com> ---
(In reply to Aaron Colwell from comment #7)
> (In reply to Eric Carlson from comment #6)
> > 
> > ID3 metadata values can be text, an image ("APIC") with optional MIME type,
> > a defined structure (eg. "POPM", "AENC", etc), a number (eg. "PCNT"), or
> > arbitrary binary data (GEOB) with optional MIME type. 
> > 
> > It seems to me that will require an ID3Cue attribute(s) to provide at least
> > String, Object, and ArrayBuffer values. This is exactly what Ted is
> > suggesting.
> 
> Are you planning on creating a DataCue for each individual frame in an ID3
> tag? I was assuming that a single ID3Cue would contain all the values in a
> single tag. I was expecting ID3Cue to expose a map<DOMString, any> type
> interface. 
> 
> Was your plan for ID3 in DataCue to have .type be "ID3" and .value return an
> Object with keys representing the frame name and the values being the frame
> contents?
> 
  Exactly: I was thinking .type would be "ID3" (or maybe "org.id3") and .value
would return an Object with .key containing the literal frame name and .data
containing an Object with the frame contents.

> At the end of the day, I'd like there to be a way to force agreement on how
> particular metadata is exposed so we don't end up with multiple ways for
> exposing stuff like ID3. I'd also like provide a clear way to differentiate
> between the UA having no clue what the data is vs it has parsed the data
> into the agreed standardized structure for the application.
> 
  Agreed

> Do we actually need .data AND .value? Couldn't we just represent this as
> something like .type = "unknown" (or "application/octet-stream" or "") and
> .value = an ArrayBuffer() w/ the data? It seems like that would be better
> than having everything optional.
> 
  That was our original idea, but when we presented it at the F2F last week
Maciej pointed out that that would make it difficult for a UA to return a typed
value for a key after shipping a version where it returned it as an
ArrayBuffer.

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

Received on Wednesday, 16 April 2014 20:47:38 UTC