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

Saturday, 28 May 2016

• [sensors] Malicious use of the phone's Gyroscope Yossi Oren via GitHub
• Re: Update on privacy work Lukasz Olejnik (W3C)

Thursday, 26 May 2016

• Update on privacy work Frederick Hirsch
• Sensor questions Frederick Hirsch
• Draft Minutes from today's call 26 May 2016 Frederick Hirsch
• DAP-ACTION-758: Follow up with giri re tpac Device and Sensors Working Group Issue Tracker
• DAP-ACTION-757: Send email to lukasz asking re next steps for privacy or call participation Device and Sensors Working Group Issue Tracker
• Network Info: incubation in WICG Dominique Hazael-Massieux

Wednesday, 25 May 2016

• icalendar of upcoming teleconferences Dominique Hazael-Massieux
• Re: CfC: change meeting week for Devices and Sensors Call, please respond by 6 May (next Friday) Frederick Hirsch
• Re: CfC: change meeting week for Devices and Sensors Call, please respond by 6 May (next Friday) Frederick Hirsch
• Re: CfC: change meeting week for Devices and Sensors Call, please respond by 6 May (next Friday) Frederick Hirsch
• Re: CfC: change meeting week for Devices and Sensors Call, please respond by 6 May (next Friday) Dominique Hazael-Massieux
• Re: CfC: change meeting week for Devices and Sensors Call, please respond by 6 May (next Friday) Frederick Hirsch
• [admin] Agenda tomorrow, 26 May 2016 - DAS Distributed Meeting Frederick Hirsch

Friday, 20 May 2016

• Re: [sensors] Should SensorReadingEvent carry reading payload? Zoltan Kis via GitHub
• Re: [sensors] Should SensorReadingEvent carry reading payload? Tobie Langel via GitHub
• Re: [sensors] Should SensorReadingEvent carry reading payload? Zoltan Kis via GitHub
• Re: [sensors] Should SensorReadingEvent carry reading payload? Tobie Langel via GitHub
• Re: [sensors] Should the enum SensorState have nosensor ? Tobie Langel via GitHub
• Re: [sensors] Should SensorReadingEvent carry reading payload? Zoltan Kis via GitHub
• Re: [sensors][ambient-light] Initial implementation reports Lukasz Olejnik (W3C)

Thursday, 19 May 2016

• Re: [sensors] Should SensorReadingEvent carry reading payload? Tim Volodine via GitHub
• Re: [sensors][ambient-light] Initial implementation reports Kostiainen, Anssi
• [sensors][ambient-light] Initial implementation reports Zhang, Zhiqiang

Tuesday, 17 May 2016

• [sensors] Event object in error callback Philip Ackermann via GitHub
• Closed: [sensors] SensorOptions.frequency is not suitable for sensors that require high sampling rate. Alexander Shalamov via GitHub
• [sensors] SensorOptions.frequency is not suitable for sensors that require high sampling rate. Alexander Shalamov via GitHub

Monday, 16 May 2016

• Re: [sensors] Does SensorReading always need a timeStamp ? Tobie Langel via GitHub
• Re: [sensors] Should the enum SensorState have nosensor ? Tobie Langel via GitHub
• Re: [sensors] Clarify terminology Tobie Langel via GitHub
• Re: [sensors] Should SensorReadingEvent carry reading payload? Tobie Langel via GitHub
• Re: [sensors] Should SensorReadingEvent carry reading payload? Rick Waldron via GitHub
• Re: [sensors] Should SensorReadingEvent carry reading payload? Tobie Langel via GitHub
• Re: [sensors] Should SensorReadingEvent carry reading payload? Rick Waldron via GitHub
• Re: [sensors] Should SensorReadingEvent carry reading payload? Tobie Langel via GitHub
• Re: [sensors] Clarify terminology Tim Volodine via GitHub
• Re: [sensors] Should SensorReadingEvent carry reading payload? Tim Volodine via GitHub
• Re: [sensors] Does SensorReading always need a timeStamp ? Tim Volodine via GitHub
• Re: [sensors] Should the enum SensorState have nosensor ? Tim Volodine via GitHub
• Re: [sensors] Should the enum SensorState have nosensor ? Anssi Kostiainen via GitHub

Saturday, 14 May 2016

• Re: [sensors] Does SensorReading always need a timeStamp ? Tobie Langel via GitHub
• Closed: [sensors] What is the plan for actuators? Tobie Langel via GitHub
• Re: [sensors] What is the plan for actuators? Tobie Langel via GitHub
• Re: [sensors] Does SensorReading always need a timeStamp ? Mats Wichmann via GitHub
• [sensors] What is the plan for actuators? Mats Wichmann via GitHub

Friday, 13 May 2016

• Re: [sensors] WebIDL ref label is "Level 1" but links to "Level 2" Tobie Langel via GitHub
• Re: [sensors] WebIDL ref label is "Level 1" but links to "Level 2" François Daoust via GitHub
• Re: [sensors] WebIDL ref label is "Level 1" but links to "Level 2" Tobie Langel via GitHub
• Call for Consensus: Start wide review of Generic Sensor API and Ambient Light Specification: CfC Deadline 27 May 2016 Frederick Hirsch
• [sensors] WebIDL ref label is "Level 1" but links to "Level 2" François Daoust via GitHub
• Re: [battery] Spec update tests ready for review Dominique Hazael-Massieux
• RE: [battery] Spec update tests ready for review Zhang, Zhiqiang

Thursday, 12 May 2016

• Starting wide review of Generic Sensor & Ambient Light Dominique Hazael-Massieux
• [minutes] May 12 teleconf Dominique Hazael-Massieux
• DAP-ACTION-756: Start discussion on wide review of generic sensor & ambient lights Device and Sensors Working Group Issue Tracker

Wednesday, 11 May 2016

• Reminder: DAP call tomorrow, Dom chairing Frederick Hirsch
• Closed: [sensors] nit: Implementations instead of Browser implementations? Tobie Langel via GitHub
• [sensors] nit: Implementations instead of Browser implementations? Mats Wichmann via GitHub
• Re: [sensors] Clarify terminology Mats Wichmann via GitHub
• Reminder [admin] Agenda - DAS Distributed Meeting 12 May 2016 Dominique Hazael-Massieux
• TPAC 2016 Registration Now Open Dominique Hazael-Massieux
• Re: [sensors] Does SensorReading always need a timeStamp ? Tobie Langel via GitHub
• Re: [sensors] Does SensorReading always need a timeStamp ? Tobie Langel via GitHub
• Re: [sensors] Does SensorReading always need a timeStamp ? Rijubrata Bhaumik via GitHub
• Re: [sensors] Does SensorReading always need a timeStamp ? Tobie Langel via GitHub
• Re: [sensors] Does SensorReading always need a timeStamp ? Rijubrata Bhaumik via GitHub
• Re: [sensors] Does SensorReading always need a timeStamp ? Tobie Langel via GitHub
• Re: [sensors] Does SensorReading always need a timeStamp ? Rijubrata Bhaumik via GitHub

Tuesday, 10 May 2016

• Re: [sensors] Exposing sensors in service workers Marijn Kruisselbrink via GitHub
• [battery] Spec update tests ready for review Zhang, Zhiqiang
• Re: [sensors] Exposing sensors in workers and service workers Tobie Langel via GitHub
• [sensors] Exposing sensors in service workers Tobie Langel via GitHub

Monday, 9 May 2016

• Re: [sensors] Does SensorReading always need a timeStamp ? Tobie Langel via GitHub
• Re: [sensors] Eventually rename the SensorReading timeStamp attribute for consistency with DOM events. Tobie Langel via GitHub
• Re: [sensors] SensorState "idle" Tobie Langel via GitHub
• Closed: [sensors] SensorState "idle" Tobie Langel via GitHub
• Re: [sensors] Clarify terminology Tobie Langel via GitHub
• Re: [sensors] Should the enum SensorState have nosensor ? Tobie Langel via GitHub
• Re: [sensors] Does SensorReading always need a timeStamp ? Tobie Langel via GitHub
• [sensors] Does SensorReading always need a timeStamp ? Rijubrata Bhaumik via GitHub
• [sensors] Should the enum SensorState have nosensor ? Rijubrata Bhaumik via GitHub
• Re: [sensors] Should the enum SensorState have nosensor ? Rijubrata Bhaumik via GitHub

Friday, 6 May 2016

• Re: [sensors] Eventually rename the SensorReading timeStamp attribute for consistency with DOM events. Tobie Langel via GitHub
• Re: [sensors] SensorState "idle" Tobie Langel via GitHub
• Re: [sensors] Should SensorReadingEvent carry reading payload? Tobie Langel via GitHub
• [sensors] Should SensorReadingEvent carry reading payload? Tim Volodine via GitHub
• [sensors] SensorState "idle" Tim Volodine via GitHub
• Re: [sensors] Eventually rename the SensorReading timeStamp attribute for consistency with DOM events. Tim Volodine via GitHub

Last message date: Saturday, 28 May 2016 21:47:03 UTC