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

Re: Systematic access to media/plugin metadata

From: Henri Sivonen <hsivonen@iki.fi>
Date: Wed, 13 Apr 2011 15:07:39 +0300
To: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
Cc: Danny Ayers <danny.ayers@gmail.com>, Leonard Rosenthol <lrosenth@adobe.com>, public-html@w3.org
Message-ID: <1302696459.2569.619.camel@shuttle>
On Wed, 2011-04-13 at 21:54 +1000, Silvia Pfeiffer wrote:
> > If the scenario is that someone puts a image with metadata on a server
> > and without the author doing anything else, the browser can alert the
> > user about stuff, then it's about a built-in browser feature that
> > doesn't have expose anything to JS.
> >
> > If the scenario is that someone puts an image with metadata on a server
> > *and* supplies a JavaScript program that uses DOM/HTML, canvas or SVG to
> > alert the user about the metadata, the author controls both the image
> > and the alert mechanism, so the author might as well extract the
> > metadata on the server side (like e.g. Flickr does) and transfer the
> > extracted data to the browser using whatever existing means.

> There are actually browser plugins that expose EXIF and similar image
> metadata, see https://addons.mozilla.org/en-us/firefox/search/?q=exif&cat=all&x=0&y=0
> . I don't think it's unreasonable to expect the same thing for video
> and audio.

Those appear to be extension-based implementations of the first
scenario--not of the second scenario.

-- 
Henri Sivonen
hsivonen@iki.fi
http://hsivonen.iki.fi/
Received on Wednesday, 13 April 2011 12:08:16 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:17:28 GMT