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

Alexander Shalamov via GitHub

Closed: [sensors] SensorOptions.frequency is not suitable for sensors that require high sampling rate. (Tuesday, 17 May)
[sensors] SensorOptions.frequency is not suitable for sensors that require high sampling rate. (Tuesday, 17 May)

Anssi Kostiainen via GitHub

Re: [sensors] Should the enum SensorState have nosensor ? (Monday, 16 May)

Device and Sensors Working Group Issue Tracker

DAP-ACTION-758: Follow up with giri re tpac (Thursday, 26 May)
DAP-ACTION-757: Send email to lukasz asking re next steps for privacy or call participation (Thursday, 26 May)
DAP-ACTION-756: Start discussion on wide review of generic sensor & ambient lights (Thursday, 12 May)

Dominique Hazael-Massieux

Network Info: incubation in WICG (Thursday, 26 May)
icalendar of upcoming teleconferences (Wednesday, 25 May)
Re: CfC: change meeting week for Devices and Sensors Call, please respond by 6 May (next Friday) (Wednesday, 25 May)
Re: [battery] Spec update tests ready for review (Friday, 13 May)
Starting wide review of Generic Sensor & Ambient Light (Thursday, 12 May)
[minutes] May 12 teleconf (Thursday, 12 May)
Reminder [admin] Agenda - DAS Distributed Meeting 12 May 2016 (Wednesday, 11 May)
TPAC 2016 Registration Now Open (Wednesday, 11 May)

François Daoust via GitHub

Re: [sensors] WebIDL ref label is "Level 1" but links to "Level 2" (Friday, 13 May)
[sensors] WebIDL ref label is "Level 1" but links to "Level 2" (Friday, 13 May)

Frederick Hirsch

Update on privacy work (Thursday, 26 May)
Sensor questions (Thursday, 26 May)
Draft Minutes from today's call 26 May 2016 (Thursday, 26 May)
Re: CfC: change meeting week for Devices and Sensors Call, please respond by 6 May (next Friday) (Wednesday, 25 May)
Re: CfC: change meeting week for Devices and Sensors Call, please respond by 6 May (next Friday) (Wednesday, 25 May)
Re: CfC: change meeting week for Devices and Sensors Call, please respond by 6 May (next Friday) (Wednesday, 25 May)
Re: CfC: change meeting week for Devices and Sensors Call, please respond by 6 May (next Friday) (Wednesday, 25 May)
[admin] Agenda tomorrow, 26 May 2016 - DAS Distributed Meeting (Wednesday, 25 May)
Call for Consensus: Start wide review of Generic Sensor API and Ambient Light Specification: CfC Deadline 27 May 2016 (Friday, 13 May)
Reminder: DAP call tomorrow, Dom chairing (Wednesday, 11 May)

Kostiainen, Anssi

Re: [sensors][ambient-light] Initial implementation reports (Thursday, 19 May)

Lukasz Olejnik (W3C)

Re: Update on privacy work (Saturday, 28 May)
Re: [sensors][ambient-light] Initial implementation reports (Friday, 20 May)

Marijn Kruisselbrink via GitHub

Re: [sensors] Exposing sensors in service workers (Tuesday, 10 May)

Mats Wichmann via GitHub

Re: [sensors] Does SensorReading always need a timeStamp ? (Saturday, 14 May)
[sensors] What is the plan for actuators? (Saturday, 14 May)
[sensors] nit: Implementations instead of Browser implementations? (Wednesday, 11 May)
Re: [sensors] Clarify terminology (Wednesday, 11 May)

Philip Ackermann via GitHub

[sensors] Event object in error callback (Tuesday, 17 May)

Rick Waldron via GitHub

Re: [sensors] Should SensorReadingEvent carry reading payload? (Monday, 16 May)
Re: [sensors] Should SensorReadingEvent carry reading payload? (Monday, 16 May)

Rijubrata Bhaumik via GitHub

Re: [sensors] Does SensorReading always need a timeStamp ? (Wednesday, 11 May)
Re: [sensors] Does SensorReading always need a timeStamp ? (Wednesday, 11 May)
Re: [sensors] Does SensorReading always need a timeStamp ? (Wednesday, 11 May)
[sensors] Does SensorReading always need a timeStamp ? (Monday, 9 May)
[sensors] Should the enum SensorState have nosensor ? (Monday, 9 May)
Re: [sensors] Should the enum SensorState have nosensor ? (Monday, 9 May)

Tim Volodine via GitHub

Re: [sensors] Should SensorReadingEvent carry reading payload? (Thursday, 19 May)
Re: [sensors] Clarify terminology (Monday, 16 May)
Re: [sensors] Should SensorReadingEvent carry reading payload? (Monday, 16 May)
Re: [sensors] Does SensorReading always need a timeStamp ? (Monday, 16 May)
Re: [sensors] Should the enum SensorState have nosensor ? (Monday, 16 May)
[sensors] Should SensorReadingEvent carry reading payload? (Friday, 6 May)
[sensors] SensorState "idle" (Friday, 6 May)
Re: [sensors] Eventually rename the SensorReading timeStamp attribute for consistency with DOM events. (Friday, 6 May)

Tobie Langel via GitHub

Re: [sensors] Should SensorReadingEvent carry reading payload? (Friday, 20 May)
Re: [sensors] Should SensorReadingEvent carry reading payload? (Friday, 20 May)
Re: [sensors] Should the enum SensorState have nosensor ? (Friday, 20 May)
Re: [sensors] Does SensorReading always need a timeStamp ? (Monday, 16 May)
Re: [sensors] Should the enum SensorState have nosensor ? (Monday, 16 May)
Re: [sensors] Clarify terminology (Monday, 16 May)
Re: [sensors] Should SensorReadingEvent carry reading payload? (Monday, 16 May)
Re: [sensors] Should SensorReadingEvent carry reading payload? (Monday, 16 May)
Re: [sensors] Should SensorReadingEvent carry reading payload? (Monday, 16 May)
Re: [sensors] Does SensorReading always need a timeStamp ? (Saturday, 14 May)
Closed: [sensors] What is the plan for actuators? (Saturday, 14 May)
Re: [sensors] What is the plan for actuators? (Saturday, 14 May)
Re: [sensors] WebIDL ref label is "Level 1" but links to "Level 2" (Friday, 13 May)
Re: [sensors] WebIDL ref label is "Level 1" but links to "Level 2" (Friday, 13 May)
Closed: [sensors] nit: Implementations instead of Browser implementations? (Wednesday, 11 May)
Re: [sensors] Does SensorReading always need a timeStamp ? (Wednesday, 11 May)
Re: [sensors] Does SensorReading always need a timeStamp ? (Wednesday, 11 May)
Re: [sensors] Does SensorReading always need a timeStamp ? (Wednesday, 11 May)
Re: [sensors] Does SensorReading always need a timeStamp ? (Wednesday, 11 May)
Re: [sensors] Exposing sensors in workers and service workers (Tuesday, 10 May)
[sensors] Exposing sensors in service workers (Tuesday, 10 May)
Re: [sensors] Does SensorReading always need a timeStamp ? (Monday, 9 May)
Re: [sensors] Eventually rename the SensorReading timeStamp attribute for consistency with DOM events. (Monday, 9 May)
Re: [sensors] SensorState "idle" (Monday, 9 May)
Closed: [sensors] SensorState "idle" (Monday, 9 May)
Re: [sensors] Clarify terminology (Monday, 9 May)
Re: [sensors] Should the enum SensorState have nosensor ? (Monday, 9 May)
Re: [sensors] Does SensorReading always need a timeStamp ? (Monday, 9 May)
Re: [sensors] Eventually rename the SensorReading timeStamp attribute for consistency with DOM events. (Friday, 6 May)
Re: [sensors] SensorState "idle" (Friday, 6 May)
Re: [sensors] Should SensorReadingEvent carry reading payload? (Friday, 6 May)

Yossi Oren via GitHub

[sensors] Malicious use of the phone's Gyroscope (Saturday, 28 May)

Zhang, Zhiqiang

[sensors][ambient-light] Initial implementation reports (Thursday, 19 May)
RE: [battery] Spec update tests ready for review (Friday, 13 May)
[battery] Spec update tests ready for review (Tuesday, 10 May)

Zoltan Kis via GitHub

Re: [sensors] Should SensorReadingEvent carry reading payload? (Friday, 20 May)
Re: [sensors] Should SensorReadingEvent carry reading payload? (Friday, 20 May)
Re: [sensors] Should SensorReadingEvent carry reading payload? (Friday, 20 May)

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