- From: Christine Runnegar <runnegar@isoc.org>
- Date: Mon, 17 Aug 2020 22:47:01 +0000
- To: public-privacy <public-privacy@w3.org>
Hi everyone, Our agenda for the call on Thursday is below. I have also included links to the draft specs and other useful background information. Christine ==== Privacy reviews a. Request from the WebRTC WG of its MediaStreamTrack Content Hint spec (Kris) Explainer: https://github.com/w3c/mst-content-hint/blob/gh-pages/explainer.md Specification URL: https://www.w3.org/TR/2020/WD-mst-content-hint-20200728/ Security and Privacy Considerations: https://w3c.github.io/mst-content-hint/#security-and-privacy-considerations Security and Privacy self-review: https://github.com/w3c/mst-content-hint/blob/gh-pages/security-privacy-questionnaire.md GitHub repo (for any feedback) https://github.com/w3c/mst-content-hint/ b. Request from the Devices and Sensors API WG for Screen Wake Lock API (Pranjal) Current ED: https://w3c.github.io/screen-wake-lock/ This document specifies an API that allows web applications to request a screen wake lock. Under the right conditions, and if allowed, the screen wake lock prevents the system from turning off a device's screen. Substantive changes since the last CR is documented here: https://w3c.github.io/screen-wake-lock/#changes-20171214 Link to the Security and privacy considerations section: https://w3c.github.io/screen-wake-lock/#security-and-privacy-considerations Request for issues to be filed at https://github.com/w3c/screen-wake-lock c. Request from the Immersive Web WG for WebRX Device API (Pete) Current ED: https://immersive-web.github.io/webxr/ This specification describes support for accessing virtual reality (VR) and augmented reality (AR) devices, including sensors and head-mounted displays, on the Web. Security and Privacy considerations: https://immersive-web.github.io/webxr/#security Explainer: https://github.com/immersive-web/webxr/blob/master/privacy-security-explainer.md
Received on Monday, 17 August 2020 22:47:26 UTC