W3C home > Mailing lists > Public > public-geolocation@w3.org > July 2020

Re: [geolocation-api] How to specify desired accuracy / resolution of data? (#49)

From: Anssi Kostiainen via GitHub <sysbot+gh@w3.org>
Date: Wed, 01 Jul 2020 18:41:37 +0000
To: public-geolocation@w3.org
Message-ID: <issue_comment.created-652584514-1593628895-sysbot+gh@w3.org>
@pes10k wrote:

>Thank you both for your notes above. I'm holding off adding comments to Geolocation Sensor since my understanding is the relevant WG charter has objections (including regarding geolocation). If those get resolved, or if ive misunderstood the situation, i'll happily move this issue over there.

@pes10k I think you may have slightly misunderstood how the W3C Process works. Let me try to clarify.

First, The Director has not announced any changes regarding this WG or the Geolocation Sensor work, so please feel free to submit your feedback to the https://github.com/w3c/geolocation-sensor repo where the context for your proposal is. In particular, please review the issues labeled with [geo-accuracy](https://github.com/w3c/geolocation-sensor/issues?q=label%3Ageo-accuracy+) and chime in.

Second, the WG is not aware of any technical arguments against the Geolocation Sensor spec that'd suggest changes to the direction. The WG acknowledges the historical context and that the problem is not easy to solve, but that's not a valid reason to disinvest. This, especially given the strong demand for the new geolocation features from the web developer community. As per the WG's commitment, we solve also this problem in a secure and privacy-preserving manner. As a WG, we also benefit from horizontal review from experts in privacy, security, others. Of course, we're lucky to have our resident privacy experts in this WG who are scrutinizing the WG's work closely. And we have you watching us!

Last but not least, the fact that you opened this issue adds to the pile of evidence we need to keep the Geolocation Sensor as its own separate WG deliverable as to allow discussion and development of new features for geolocation without interfering with the Geolocation API maintenance effort that is also important, but has its own timelines and priorities. These two APIs coexist.

I'll ping @samuelweiler to ensure this valuable feedback from @pes10k is considered by the W3M.

GitHub Notification of comment by anssiko
Please view or discuss this issue at https://github.com/w3c/geolocation-api/issues/49#issuecomment-652584514 using your GitHub account
Received on Wednesday, 1 July 2020 18:41:38 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 1 July 2020 18:41:39 UTC