Re: RfC: wide review of WebDriver extensions for Sensor APIs

Hi Anssi,

Thank you for reaching out.  I read through the modifications / spec-additions, and since they only affect automated use cases (e.g. would never effect standard browser users) I think there is no PING relevant privacy issues.

However, I do see a variety of other privacy sensitive issues in the specs, unrelated to WebDriver.  Is there a point where the WG could work through some of these with PING during a regular PING call?

Thank you again for taking the time to reach out!
Pete


> On Oct 14, 2019, at 3:46 AM, Kostiainen, Anssi <anssi.kostiainen@intel.com> wrote:
> 
> Hi Privacy IG,
> 
> The Devices and Sensors Working Group requests wide review of the
> following specs. The only substantial change since the last CR is the
> the addition of WebDriver extensions. Please provide your feedback
> by 2019-11-14.
> 
> WebDriver API and its extensions enable test automation and are not
> web-exposed in a normal browsing scenario. The extensions in scope of
> this review request are defined in the following Automation sections:
> 
>   Generic Sensor API
>   https://w3c.github.io/sensors/#automation
> 
>   Accelerometer
>   https://w3c.github.io/accelerometer/#automation
> 
>   Gyroscope
>   https://w3c.github.io/gyroscope/#automation
> 
>   Orientation Sensor
>   https://w3c.github.io/orientation-sensor/#automation
> 
>   Security and Privacy Self-Review Questionnaire results:
>   https://github.com/w3c/sensors/blob/master/security-questionnaire.md
> 
> The group requests feedback via the respective specifications' GitHub
> repositories, or via email to public-device-apis@w3.org.
> 
> The group is looking for confirmation that it has satisfied its relevant
> technical requirements and dependencies with other groups.
> 
> Thanks,
> 
> -Anssi (Devices and Sensors WG co-chair)
>

Received on Friday, 18 October 2019 23:46:23 UTC