Re: [dap-charter] DASWG: Drop Proximity sensor API for privacy and lack of implementer support (#99)

All privacy issues brought up to the group's attention have been documented [1] and reviewed with privacy experts [2] with additional mitigations specified [1] on top of the mitigations inherited from the Generic Sensor API [3]. The implementation of these mitigations is work in progress alongside user studies to understand requirements of real-world use cases in terms of accuracy and sampling frequency.

The latest version of the Proximity Sensor API has implementer support [4] with shipping decision awaiting the above-mentioned work items to conclude satisfactorily. Multiple experimental implementations of the earlier version of the API [5] informed the development of the additional mitigations in place in the latest version of the API.

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/proximity/#security-and-privacy
[2] https://github.com/w3c/proximity/issues/17
[3] https://w3c.github.io/sensors/#mitigation-strategies
[4] https://crbug.com/897317
[5] https://caniuse.com/#feat=proximity

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

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