- From: Mandyam, Giridhar <mandyam@qti.qualcomm.com>
- Date: Thu, 1 Oct 2015 15:58:53 +0000
- To: W3C Device APIs WG <public-device-apis@w3.org>
- CC: "public-geolocation@w3.org" <public-geolocation@w3.org>
Apologies for cross posting, but this topic impacts both DAP and Geoloc. WG. The DAP WG is developing the Generic Sensor API, and would like to "rebuild" Geolocation [1] and DeviceOrientation [2] using this API as two of the target use cases. These specs are widespread in terms of browser implementation, but there are outstanding issues with them that will likely not get resolved within the current specification context. Therefore, as the Generic Sensor API work goes forward, it would be good to consider known issues with these two specifications during the "rebuilding" efforts. The W3C has transitioned to Github repositories, and as a result there are now mechanisms in GH for declaring issues even against mature specs. The Geolocation issues list may be found at [3] (although there are not any technical issues currently listed), and DeviceOrientation in [4]. I will also point to a thorough review of the Geolocation spec provided by Josh Soref [5], which was unfortunately not addressed during the last errata fix. Thanks, -Giri Mandyam, Geolocation Working Group Chair [1] http://www.w3.org/TR/geolocation-API/ [2] http://www.w3.org/TR/orientation-event/ [3] https://github.com/w3c/geolocation-api/issues [4] https://github.com/w3c/deviceorientation/issues [5] http://lists.w3.org/Archives/Public/public-geolocation/2015Jun/0000.html
Received on Thursday, 1 October 2015 15:59:35 UTC