W3C home > Mailing lists > Public > public-device-apis@w3.org > November 2009

RE: Camera/Caputre API (was: DAP Roadmap, priorities)

From: Tran, Dzung D <dzung.d.tran@intel.com>
Date: Thu, 12 Nov 2009 07:09:00 -0800
To: Dominique Hazael-Massieux <dom@w3.org>, "Ingmar.Kliche@telekom.de" <Ingmar.Kliche@telekom.de>
CC: "public-device-apis@w3.org" <public-device-apis@w3.org>
Message-ID: <753F67ADE6F5094C9F1DBA00D1BAA8D312C81D35D5@orsmsx501.amr.corp.intel.com>
I sent this message earlier, but didn't see it, so sorry if this is a repeat.

We should take a look at Gears Camera API:

http://code.google.com/p/gears/wiki/CameraAPI

I also have extensive experience with camera system level libraries on Linux with LibV4L(x) which should give some insights into requirements and API.

Dzung Tran


-----Original Message-----
From: public-device-apis-request@w3.org [mailto:public-device-apis-request@w3.org] On Behalf Of Dominique Hazael-Massieux
Sent: Thursday, November 12, 2009 05:01 AM
To: Ingmar.Kliche@telekom.de
Cc: public-device-apis@w3.org
Subject: Camera/Caputre API (was: DAP Roadmap, priorities)

Hi Ingmar,

Le mercredi 11 novembre 2009 à 12:08 +0100, Ingmar.Kliche@telekom.de a
écrit :
> I would like to support the effort around photo/audio/video capture and
> help editing this spec in particular. I could also come up with a
> strawman proposal.

If you could do that, it would certainly help getting the ball rolling
and would make it more likely we could adopt it as one of the "priority
APIs".

In terms of the security around it, I think there is a pretty large
agreement that access to the API should be granted through the user
interaction with the device (e.g. hitting the shutter button for a
camera, including the camera's visor as part of the requesting page,
etc.), so it would be nice if the draft API took that idea in
consideration, and if this was described (probably informatively) in a
"security considerations" section.

A few people have suggested that the API be made available through a
refinement of <input type='file' > with a type attribute set to an
audio, image, or video mime type or set of mime types; maybe something
to take into consideration as well. In any case, the interactions with
the <video>, <audio> and <img> elements will need to be considered.

Dom
Received on Thursday, 12 November 2009 15:10:15 GMT

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