- From: Mandyam, Giridhar <mandyam@quicinc.com>
- Date: Thu, 21 Nov 2013 15:28:16 +0000
- To: Dominique Hazael-Massieux <dom@w3.org>, "public-geolocation@w3.org" <public-geolocation@w3.org>
There already has been a specific Android class extension for indoor location in existence: https://developer.qualcomm.com/docs/snapdragon-sdk/reference-api/com/qualcomm/snapdragon/sdk/location/QCLocationManager.html. -Giri -----Original Message----- From: Dominique Hazael-Massieux [mailto:dom@w3.org] Sent: Thursday, November 21, 2013 1:54 AM To: public-geolocation@w3.org Subject: Indoor API in new charter? Hi, The proposed new charter for the group currently has a deliverable for indoor location: http://lists.w3.org/Archives/Public/public-geolocation/2013Nov/att-0003/Proposed_Geolocation_Working_Group_Charter.htm#deliverables During discussions last week in TPAC, there was unclarity on: * whether indoor location needed anything special in the API (i.e. only required browsers to use whatever location technology is available indoors) * if it did, whether there was sufficient experience with these specificities to proceed with standardization; for instance, there doesn't seem be to an official iOS or Android indoor location API I would be interested in getting views on these two considerations. If any of the two is confirmed, I think including indoor location in the new charter as a Rec-track deliverable is probably premature; in which case, I would suggest we keep the topic on, but as "use case and requirements" deliverable, rather than for an API. Thanks, Dom
Received on Thursday, 21 November 2013 15:28:48 UTC