W3C home > Mailing lists > Public > public-device-apis@w3.org > March 2010

RE: CaptureAPI initial comments

From: Tran, Dzung D <dzung.d.tran@intel.com>
Date: Fri, 26 Mar 2010 21:10:19 -0700
To: Philip Gladstone <pgladstone@cisco.com>, Rik Sagar <org.whatwg@sagar.org>
CC: Ilkka Oksanen <Ilkka.Oksanen@nokia.com>, "public-device-apis@w3.org" <public-device-apis@w3.org>
Message-ID: <753F67ADE6F5094C9F1DBA00D1BAA8D32550AFEBC2@orsmsx501.amr.corp.intel.com>
Yes, the initial intent was that a separate app such as camera app is launched. We had discussion on the WG about that this model might not be sufficient for some of the use cases.  There were also discussions on embedded viewfinder, which has its own implication of security/privacy issues.

Dzung Tran

From: public-device-apis-request@w3.org [mailto:public-device-apis-request@w3.org] On Behalf Of Philip Gladstone
Sent: Friday, March 26, 2010 12:56 PM
To: Rik Sagar
Cc: Ilkka Oksanen; public-device-apis@w3.org
Subject: Re: CaptureAPI initial comments

On 26-Mar-10 15:05, Rik Sagar wrote:

I have the impression - after re-reading this CaptureAPI spec. - that it's targeting an model where an application is 'cross-launching' a separate camcorder or audio recording application.  Is that a valid assumption?  In contrast, I was capture objects would be something included in the app, similar to how we now embed a HTMLAudioElement , via new Audio(), or HTMLVideoElement.   That may be why I have a longer list of events I want to expose.  In my scenario, specifying a callback for each when calling captureVideo() does not seem feasible.

Yes, the model is that a separate app is launched -- and this is a huge limitation of the current approach. It means that you cannot do things like build a video phone app (or even voice only phone app) or any augmented reality apps.



Philip Gladstone

Distinguished Engineer

Product Development


Phone: +1 978-ZEN-TOAD (+1 978 936 8623)

Google: +1 978 800 1010

Ham radio: N1DQ

Cisco.com - http://www.cisco.com

This email may contain confidential and privileged material for the sole use of the intended recipient. Any review, use, distribution or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive for the recipient), please contact the sender by reply email and delete all copies of this message.

For corporate legal information go to:


Received on Saturday, 27 March 2010 04:10:59 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:32:18 UTC