public-device-apis@w3.org from March 2016 by date

Thursday, 31 March 2016

• [admin] Reminder: no DAP call today Dominique Hazael-Massieux
• New charter approved; rejoin the group Dominique Hazael-Massieux

Wednesday, 30 March 2016

• Re: [sensors] Setup echidna for continuous deployment Dominique Hazael-Massieux via GitHub
• Re: [sensors] Setup echidna for continuous deployment Dominique Hazael-Massieux via GitHub

Tuesday, 29 March 2016

• Re: Privacy report on sensors, for generic sensors API. Lukasz Olejnik (W3C)
• Re: Privacy report on sensors, for generic sensors API. Greg Norcie
• Re: Battery API is a W3C Proposed Recommendation Kostiainen, Anssi
• Privacy report on sensors, for generic sensors API. Lukasz Olejnik (W3C)
• New WD of Ambient Light API Dominique Hazael-Massieux
• Battery API is a W3C Proposed Recommendation Dominique Hazael-Massieux

Thursday, 24 March 2016

• Re: New generic sensor API WD out Frederick Hirsch
• Re: New generic sensor API WD out Kostiainen, Anssi
• New generic sensor API WD out Dominique Hazael-Massieux
• Re: [ambient-light] Add bikeshed index file. Dominique Hazael-Massieux via GitHub

Wednesday, 23 March 2016

• Re: [ambient-light] Add bikeshed index file. Tobie Langel via GitHub
• Re: [ambient-light] Add bikeshed index file. Anssi Kostiainen via GitHub
• Re: [ambient-light] Add bikeshed index file. Tobie Langel via GitHub
• Re: [ambient-light] Add bikeshed index file. Anssi Kostiainen via GitHub

Tuesday, 22 March 2016

• Closed: [sensors] Spec should allow user agents to reduce or disable sensor read for power saving purposes Tobie Langel via GitHub
• Re: [sensors] Spec should allow user agents to reduce or disable sensor read for power saving purposes Tobie Langel via GitHub
• Closed: [sensors] Define behavior when visibilityState != "visible" Tobie Langel via GitHub
• Re: [sensors] Define behavior when visibilityState != "visible" Tobie Langel via GitHub
• Closed: [sensors] Discreet sensors must fire an event with their current state on instantiation Tobie Langel via GitHub
• Re: [sensors] Discreet sensors must fire an event with their current state on instantiation Tobie Langel via GitHub
• Closed: [sensors] Discrete vs continuous reporting modes Tobie Langel via GitHub
• Re: [sensors] Discrete vs continuous reporting modes Tobie Langel via GitHub
• Closed: [sensors] What if requested polling frequency is > time it takes to read data out of the sensor? Tobie Langel via GitHub
• Re: [sensors] What if requested polling frequency is > time it takes to read data out of the sensor? Tobie Langel via GitHub
• Closed: [sensors] Allow for async permission request when first accessing sensor data Tobie Langel via GitHub
• Re: [sensors] Define behavior when multiple instances of a sensor set different settings Tobie Langel via GitHub
• Closed: [sensors] Define behavior when multiple instances of a sensor set different settings Tobie Langel via GitHub
• Closed: [sensors] Clarify terminology Tobie Langel via GitHub
• Re: [sensors] Clarify terminology Tobie Langel via GitHub
• Re: [sensors] API must allow Web devs to easily create fused sensors in JS with an API consistant with native sensors Tobie Langel via GitHub
• Closed: [sensors] API must allow Web devs to easily create fused sensors in JS with an API consistant with native sensors Tobie Langel via GitHub
• Re: [sensors] Should sensors be singleton? Tobie Langel via GitHub
• Closed: [sensors] Should sensors be singleton? Tobie Langel via GitHub
• Closed: [sensors] Handling fatal vs. transient errors Tobie Langel via GitHub
• Re: [sensors] Typos. Anssi Kostiainen via GitHub
• Re: [sensors] Allow for async permission request when first accessing sensor data Tobie Langel via GitHub

Monday, 21 March 2016

• Re: [sensors] Adding a sensor.activated attribute Zoltan Kis via GitHub
• Re: [sensors] Adding a sensor.activated attribute Tobie Langel via GitHub
• Re: [sensors] Adding a sensor.activated attribute Marcos Caceres via GitHub
• Re: [sensors] Adding a sensor.activated attribute Marcos Caceres via GitHub

Sunday, 20 March 2016

• [sensors] Adding a sensor.activated attribute Tobie Langel via GitHub
• [sensors] start() to return a cancellable promise that resolves on first reading Tobie Langel via GitHub

Friday, 18 March 2016

• Re: [sensors] Handling fatal vs. transient errors Anssi Kostiainen via GitHub
• [sensors] Handling fatal vs. transient errors Tobie Langel via GitHub

Thursday, 17 March 2016

• Re: Call for Consensus to transition Battery API to Proposed Recommendation (PR) completed successfully Kostiainen, Anssi
• [minutes] DAP Distributed Meeting 17 March 2016 Dominique Hazael-Massieux
• Re: [sensors] Is there a need for a oncalibrationneeded event Tobie Langel via GitHub
• Re: [sensors] Is there a need for a oncalibrationneeded event Dominique Hazael-Massieux via GitHub
• [sensors] Is there a need for a oncalibrationneeded event Tobie Langel via GitHub

Wednesday, 16 March 2016

• Re: [sensors] Prepare licensing change in spec Tobie Langel via GitHub
• [sensors] Prepare licensing change in spec Dominique Hazael-Massieux via GitHub
• Summer Time! (was: [admin] Agenda - DAP Distributed Meeting 17 March 2016) Dominique Hazael-Massieux
• Re: [sensors] Add solution for one-shot readings Marcos Caceres via GitHub

Tuesday, 15 March 2016

• Re: Exiting CR Re: [wake-lock] Wake Lock API status update Chaals McCathie Nevile
• Re: [wake-lock] Wake Lock API status update Marcos Caceres

Monday, 14 March 2016

• DAP-ACTION-753: Update Web IDL Level 1 reference to reference new WebIDL CR publication in editors draft and PR draft Device APIs Working Group Issue Tracker
• Re: [sensors] Clarify terminology Anssi Kostiainen via GitHub
• [admin] Agenda - DAP Distributed Meeting 17 March 2016 Frederick Hirsch
• Call for Consensus to transition Battery API to Proposed Recommendation (PR) completed successfully Frederick Hirsch
• Re: Wake Lock API Security & Privacy Questionnaire self-review Frederick Hirsch
• Re: Wake Lock API Security & Privacy Questionnaire self-review Frederick Hirsch
• Re: [wake-lock] Wake Lock API status update Chaals McCathie Nevile
• Re: Exiting CR Re: [wake-lock] Wake Lock API status update Marcos Caceres
• Re: [wake-lock] Wake Lock API status update Marcos Caceres

Thursday, 10 March 2016

• Re: [sensors] Add solution for one-shot readings Tobie Langel via GitHub
• Re: [sensors] Add solution for one-shot readings Anne van Kesteren via GitHub
• Re: [sensors] Add solution for one-shot readings Tobie Langel via GitHub
• Re: [sensors] Add solution for one-shot readings Tobie Langel via GitHub
• Re: [sensors] Add solution for one-shot readings Tobie Langel via GitHub

Wednesday, 9 March 2016

• Re: [wake-lock] Wake Lock API Security & Privacy Questionnaire self-review Dominique Hazael-Massieux
• [wake-lock] Wake Lock API Security & Privacy Questionnaire self-review Andrey Logvinov
• Wake Lock API Security & Privacy Questionnaire self-review Andrey Logvinov

Monday, 7 March 2016

• Re: [sensors] Add solution for one-shot readings Domenic Denicola via GitHub
• Re: [sensors] Add solution for one-shot readings Anne van Kesteren via GitHub
• Re: [sensors] Add solution for one-shot readings Robin Berjon via GitHub

Sunday, 6 March 2016

• Re: [sensors] Add solution for one-shot readings Tobie Langel via GitHub
• Re: [sensors] Add solution for one-shot readings Rick Waldron via GitHub
• Re: [sensors] Add solution for one-shot readings Tobie Langel via GitHub
• Re: [sensors] Add solution for one-shot readings Tobie Langel via GitHub
• Re: [sensors] Add solution for one-shot readings Robin Berjon via GitHub
• Re: [sensors] Add solution for one-shot readings Rick Waldron via GitHub
• Re: [sensors] Add solution for one-shot readings Tobie Langel via GitHub
• Re: DAP-ACTION-750: Create draft security and privacy considerations section for vibration api Lukasz Olejnik (W3C)
• Re: [sensors] Add solution for one-shot readings Tobie Langel via GitHub
• Re: [sensors] Add solution for one-shot readings Tobie Langel via GitHub
• Re: [sensors] Add solution for one-shot readings Anssi Kostiainen via GitHub
• Re: [sensors] Add solution for one-shot readings Rick Waldron via GitHub
• Re: [sensors] Add solution for one-shot readings Tobie Langel via GitHub
• Re: [sensors] Add solution for one-shot readings Tobie Langel via GitHub
• [sensors] Add solution for cached value readings Tobie Langel via GitHub
• [sensors] Add solution for one-shot readings Tobie Langel via GitHub

Friday, 4 March 2016

• CfC: Call for Consensus to transition Battery API to Proposed Recommendation (PR) : deadline 10 March Frederick Hirsch

Thursday, 3 March 2016

• Draft minutes 3 March 2016 and Action summary Frederick Hirsch
• DAP-ACTION-752: to review wake lock with respect to privacy and security https://w3ctag.github.io/security-questionnaire/ Device APIs Working Group Issue Tracker
• DAP-ACTION-751: Prepare new vibration editors draft including errata and security and privacy consideration material from lukasz and others Device APIs Working Group Issue Tracker
• DAP-ACTION-750: Create draft security and privacy considerations section for vibration api Device APIs Working Group Issue Tracker
• DAP-ACTION-749: Send transition request Device APIs Working Group Issue Tracker
• DAP-ACTION-748: Put tentative date of 3 may 2016 in battery pr draft Device APIs Working Group Issue Tracker
• DAP-ACTION-747: Create pr publication draft, updating status section to note that there were no new issues since cr, that there were no features marked as at risk Device APIs Working Group Issue Tracker
• DAP-ACTION-746: Update pr draft to change link from implementation report to https://w3c.github.io/test-results/battery-status/20160226.html Device APIs Working Group Issue Tracker
• ISSUE-174: Anssik to put tentative date of 3 may 2016 in battery pr draft Device APIs Working Group Issue Tracker
• ISSUE-173: Anssik to create pr publication draft, updating status section to note that there were no new issues since cr, that there were no features marked as at risk Device APIs Working Group Issue Tracker
• ISSUE-172: Anssik update pr draft to change link from implementation report to https://w3c.github.io/test-results/battery-status/20160226.html Device APIs Working Group Issue Tracker

Wednesday, 2 March 2016

• [wake-lock] Wide review of Wake Lock API Dominique Hazael-Massieux
• Exiting CR Re: [wake-lock] Wake Lock API status update Chaals McCathie Nevile
• Re: [wake-lock] Wake Lock API status update Andrey Logvinov
• Re: [wake-lock] Wake Lock API status update timeless
• RE: [battery] implementation testing report Zhang, Zhiqiang

Tuesday, 1 March 2016

• [admin] Agenda - DAP Distributed Meeting 3 March 2016 Frederick Hirsch
• [battery] Next steps to PR (was: implementation testing report) Frederick Hirsch

Last message date: Thursday, 31 March 2016 10:59:33 UTC