- From: Robin Berjon <robin@berjon.com>
- Date: Tue, 25 Aug 2009 18:32:02 +0200
- To: "Ennals, Robert" <robert.ennals@intel.com>
- Cc: "public-device-apis@w3.org" <public-device-apis@w3.org>, "Vick, CV" <cv.vick@intel.com>, "Robison, Clayne B" <clayne.b.robison@intel.com>, "Idsinga, Andy S" <andy.s.idsinga@intel.com>, "Carr, Wayne" <wayne.carr@intel.com>, "Tran, Dzung D" <dzung.d.tran@intel.com>
Hi Rob, sorry for taking a while to get back to you, I was on vacation. On Aug 15, 2009, at 02:18 , Ennals, Robert wrote: > We’ve been working internally on API’s to allow web applications to > access sensor information on mobile devices such as compass > direction, proximity, thermometer, ambient light, accelerometer etc. > > Do such APIs fall within the charter of this working group? (my > guess is yes, but I’m not sure) You can see our charter at: http://www.w3.org/2009/05/DeviceAPICharter.html I would expect that these *may* fit under the "System Information and Events API". I would like more information about your requirements (posting a link to your APIs would be useful too) before I can give you a more definitive answer. Do you think for instance that that information could be channelled through something that would look like BONDI's Device Status API: http://bondi.omtp.org/apis-current/namespaceorg_1_1omtp_1_1bondi_1_1devicestatus.html That API allows one to list which aspects of a device can be observed, and then to set callbacks that can track the updates. -- Robin Berjon - http://berjon.com/
Received on Tuesday, 25 August 2009 16:32:38 UTC