- From: Robin Berjon <robin@berjon.com>
- Date: Thu, 3 Feb 2011 11:51:42 +0100
- To: "Dailey, David P." <david.dailey@sru.edu>
- Cc: "public-device-apis@w3.org" <public-device-apis@w3.org>, Doug Schepers <schepers@w3.org>, Anthony Grasso <anthony.grasso@cisra.canon.com.au>
Hi David,
On Feb 2, 2011, at 16:11 , Dailey, David P. wrote:
> Thanks for the message. It sounds like a good thing! The camera part of this sounds like some things I've heard members of the SVG WG discuss.
You can already get a taste for it and send us some feedback:
http://dev.w3.org/2009/dap/camera/
http://dev.w3.org/2009/dap/camera/Overview-API.html
> A question of clarification: would these API's include things like accessing accelerometers on things like cameras and cellular phones?
Last I heard accelerometre was in the remit of the Geolocation WG. I have no idea where they're at with that though, I haven't heard about it in a long time. It might be worth coordinating with them there.
> The distinction between the devices listed under 1. Goals (namely "camera, microphone, address book, calendar, or system information such as network connection and battery level") and 2. Scope ("desktop computers, laptop computers, mobile Internet devices (MIDs), cellular phones") isn't entirely clear to me, but is there may be a reason for including cellular phones in one category but not another?
The first list is about the functionality that is exposed, the second about actual terminals on which the code may be running. You can access the camera irrespective of whether you're on a laptop or a mobile phone. But I see how the confusion could arise, maybe we can refine the wording.
Either way perhaps should not say "cellular" but rather mobile.
Thanks for your feedback, keep it coming!
--
Robin Berjon - http://berjon.com/
Received on Thursday, 3 February 2011 10:52:08 UTC