For Firefox OS we needed to define a lot of new WebAPI's [1] to expose device capabilities like calling, sms'ing, bluetooth, etc. to the standard Web stack (DOM, JS). We used a "ship it first, get experience with the problem, standardize later" approach.
But the goal always was and still is to get all these new API's to be standard Web API's like everything else the W3C (or WHATWG) did. And I think this route is also the only one that will work for a GPS WebAPI. Make a new completely independent API first, implement it in Firefox OS, propose it for standardization later. Don't wait on the W3C or mix this into the existing geolocation or geofencing API's. Hanno [1] https://wiki.mozilla.org/WebAPI On 09.07.2015, at 10:35, André Fiedler <[email protected]> wrote: > Mozilla want's to drive the web forward ... not only Firefox or Firefox OS. ;) > > greetings, > André > > Am 09. Juli 2015 um 09:34 schrieb Felix Baumann <[email protected]>: > >> Why do you need an API standardized by the W3C? >> This is Firefox OS and not a web browser after all :/ >> >> Regards, >> Felix >> >> Am 08.07.2015 um 22:51 schrieb Garvan Keeley: >>> I raised this with the W3C geo group and was soundly rebuffed. With zero >>> support from the group, I can't see how to accomplish this. >>> https://lists.w3.org/Archives/Public/public-geolocation/2014Aug/0008.html >>> >>> There are dozens of popular apps, comprising hundreds of thousands of users >>> -millions perhaps- that we are eliminating by not providing the APIs >>> required. _______________________________________________ dev-geolocation mailing list [email protected] https://lists.mozilla.org/listinfo/dev-geolocation
