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

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

Silvia Pfeiffer <silviapfeiffer1@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED

--- Comment #17 from Silvia Pfeiffer <silviapfeiffer1@gmail.com> ---
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are
satisfied with this response, please change the state of this bug to CLOSED. If
you have additional information and would like the Editor to reconsider, please
reopen this bug. If you would like to escalate the issue to the full HTML
Working Group, please add the TrackerRequest keyword to this bug, and suggest
title and text for the Tracker Issue; or you may create a Tracker Issue
yourself, if you are able to do so. For more details, see this document:

   http://dev.w3.org/html5/decision-policy/decision-policy.html

Status: Partially Accepted
Change Description:
https://github.com/w3c/html/commit/d5ec35198fea01e56b0ec38eedce58a57a013138

Rationale:
It is true that DataCue with both a .data and .text attribute is overdefined.
DataCue is not defined for exposing parsed metadata such as ID3 tags, but for
exposing random timed data that may well be in binary format.

It would be useful if somebody started writing a ID3Cue extension spec for the
parsed metadata case. For interoperability reasons it would likely make more
sense to actually list valid metadata name-value pairs rather than a generic
JSONCue as proposed in bug 25353.

Since this bug is about the DataCue, the committed patch resolves this bug.

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

Received on Sunday, 1 June 2014 04:01:54 UTC