W3C home > Mailing lists > Public > public-html@w3.org > April 2011

Re: Systematic access to media/plugin metadata

From: Danny Ayers <danny.ayers@gmail.com>
Date: Fri, 8 Apr 2011 14:48:24 +0200
Message-ID: <BANLkTinovY5WfPtKQiLtPD4g4RnxWYXyOQ@mail.gmail.com>
To: David Singer <singer@apple.com>
Cc: Silvia Pfeiffer <silviapfeiffer1@gmail.com>, Leonard Rosenthol <lrosenth@adobe.com>, "public-html@w3.org" <public-html@w3.org>
oops, sorry, I believe it was David who said:

>> I think that what the browsers should do for metadata should match what they do for tracks and media-data; be as format-agnostic as possible.  I don't see any reason why simple questions, such as "what is the title of this work?", "what is its copyright status, if any?", "what is the role of this track?" shouldn't be answerable without any assumption of the container or metadata format.

...

> Absolutely, you've succinctly put what I was trying say in my initial post!
>
> In the unlikely case that the application needs to know more about the
> container or metadata format, it has the resource and its media type
> to play with. Should it be deemed necessary, there's nothing to stop
> name-value pairs like e.g. video.meta("metadata-format") = "XMP" which
> could allow further out-of-band interpretation of the resource's
> representation.
>
> Cheers,
> Danny.
>
> --
> http://danny.ayers.name
>



-- 
http://danny.ayers.name
Received on Friday, 8 April 2011 12:48:52 UTC

This archive was generated by hypermail 2.3.1 : Monday, 29 September 2014 09:39:24 UTC