[sensors] Possibility to use "Readable Stream" as defined by the Streams API
[sensors] Addressing finger printing concerns for sensor APIs
[sensors] Sensors for continuously changing real valued properties
[sensors] Current draft links to tobie's github
- Re: [sensors] Current draft links to tobie's github
- Re: [sensors] Current draft links to tobie's github
- Closed: [sensors] Current draft links to tobie's github
- Re: [sensors] Current draft links to tobie's github
[sensors] Spec should allow user agents to reduce or disable polling for power saving purposes
Re: [sensors] Provide a way of tying sensor requests to animation frames
Re: Reviewing the Charter
Closed: [sensors] Add a threshold option
Re: [sensors] Add a threshold option
Closed: [sensors] Add a timeout property?
Closed: [sensors] Relation to REST APIs and W3C Web of Things activities
Closed: [sensors] Ability to lookup a cached SensorReading without polling the sensor
Re: [sensors] Ability to lookup a cached SensorReading without polling the sensor
Closed: [sensors] Should sensor EventTarget be immediately available or should they be accessed through a promise?
Re: [sensors] Should sensor EventTarget be immediately available or should they be accessed through a promise?
Closed: [sensors] What precisely, do we mean by "generic"?
Closed: [sensors] When there are multiple sensors of a given type, how do we identify which one to instantiate?
Re: [sensors] When there are multiple sensors of a given type, how do we identify which one to instantiate?
Re: [sensors] Relation to REST APIs and W3C Web of Things activities
Re: [sensors] Does `SensorObserver` need a stop() method?
Closed: [sensors] Does `SensorObserver` need a stop() method?
Re: [sensors] Is a Promise-returning, "oneshot" method useful?
Closed: [sensors] Is a Promise-returning, "oneshot" method useful?
Closed: [sensors] Address questions around exposing high-level, low-level, and uncalibrated sensors
Re: [sensors] Address questions around exposing high-level, low-level, and uncalibrated sensors
Call for Consensus (CfC) to close the Web Intents Task Force - Deadline October 29, 2015
- Re: Call for Consensus (CfC) to close the Web Intents Task Force - Deadline October 29, 2015
Draft minutes teleconference 15 October 2015
DAP-ACTION-740: Send cfc to close web intents tf
DAP-ACTION-739: Send cfc for 2 week approval of progressing with charter and name change
FPWD of Generic Sensor API available
Call for Exclusions: Generic Sensor API
[admin] Agenda - DAP Distributed Meeting 15 October 2015
Finalizing DAP new charter
Introduction of WebI2C and WebGPIO
- Re: Introduction of WebI2C and WebGPIO
- Re: Introduction of WebI2C and WebGPIO
- Re: Introduction of WebI2C and WebGPIO
- Re: Introduction of WebI2C and WebGPIO
- Re: Introduction of WebI2C and WebGPIO
- Re: Introduction of WebI2C and WebGPIO
- Re: Introduction of WebI2C and WebGPIO
Generic Sensor API Status update
CfC Generic Sensor API shortname - deadline Tue 13 October
[media capture] VOTE - Media Capture and Streams Constraints Registry; deadline 13 October 2015
CfC: Call for Consensus to publish FPWD of Generic Sensor API, deadline Friday 9 October
- Re: CfC: Call for Consensus to publish FPWD of Generic Sensor API, deadline Friday 9 October
- Re: CfC: Call for Consensus to publish FPWD of Generic Sensor API, deadline Friday 9 October
- Call for Consensus to publish FPWD of Generic Sensor API completed successfully