Re: [dap-charter] DASWG: Drop Geolocation Sensor in favor of existing APIs (#103)

The Geolocation Sensor specification differs from the "existing specifications" in the following ways:

- [x] defines new features [1] that address new use cases [2] as opposed to the Geolocation API that is in maintenance and accepts no new features
- [x] addresses significant interoperability issues e.g. around accuracy and resolution [3],
- [x] improves API ergonomics, makes the API consistent with other similar APIs and extensible [4], and
- [x] defines modern privacy and security protections to address known privacy and security threats, and a model that is extensible with additional mitigations [5]

The DAS WG is [commitment](https://www.w3.org/2020/05/proposed-das-wg-charter.html#scope) to **security and privacy focused** and **use case-driven** specification development and believes ceasing this work would be considered harmful.

[1] https://w3c.github.io/geolocation-sensor/#intro
[2] https://w3c.github.io/geolocation-sensor/#use-cases
[3] https://github.com/w3c/geolocation-api/issues/49
[4] https://w3c.github.io/sensors/#concepts
[5] https://w3c.github.io/sensors/#security-and-privacy

-- 
GitHub Notification of comment by anssiko
Please view or discuss this issue at https://github.com/w3c/dap-charter/issues/103#issuecomment-654783933 using your GitHub account

Received on Tuesday, 7 July 2020 11:17:39 UTC