This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
* users want (and sometimes need) access to metadata stored within various media formats * often immanent metadata properties are better way to store metadata for authors and users so that these properties do not become separated from the file, but UAs often lack a mechanism to access that metadata stored in that way (see http://esw.w3.org/topic/HTML/UANormAndDOMForMediaPropeties for evolving solution proposals) [user issue, authoring issue]
Exposing media data in <video> and <audio> is an existing v3 feature proposal.
(in reply to comment #1) What is v3? How does that relate to this bug in the HTML5 draft?
v3 means "version 3" (as in, the third major version of the media feature). v1 was the original proposal with just play and pause. v2 is the current feature set, which is much bigger. Once all the major user agents implement that well, and once the risk of distracting them from other parts of the spec becomes lower than the risk of them just doing their own thing with video extensions, then we will go to v3 and add more features, such as this one. You can see the complete list of v3 requests in the spec (search for "v3" in the source). Marking a bug LATER doesn't mean it is rejected, it just means that I can't do anything with it right now, but will revisit it in future.
This bug predates the HTML Working Group Decision Policy. If you are satisfied with the resolution of this bug, 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 This bug is now being moved to VERIFIED. Please respond within two weeks. If this bug is not closed, reopened or escalated within two weeks, it may be marked as NoReply and will no longer be considered a pending comment.
No longer waiting for a reply on this bug.
This bug was cloned to create HTML WG bug 19056.
The current state of this is that Mozilla is intending to work on this as described here: http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2013-January/038705.html I'm not aware of any other browsers working on something like this. I propose to wait until at least one vendor has some implementation experience with this before doing anything in the spec.
Ralph, did your experimentations lead anywhere?
Not really. I couldn't get sufficient interest from other developers and stopped working on the project. Firefox OS uses parsers written in js. Firefox still exposes un-schema'd metadata for some file types as media.mozGetMetadata().
Please file a new issue at https://github.com/whatwg/html/issues/new if there's still interest.