public-device-apis@w3.org from October 2015 by subject

[admin] Agenda - DAP Distributed Meeting 15 October 2015

[media capture] Results of Vote on Media Capture and Streams Constraints Registry

[media capture] VOTE - Media Capture and Streams Constraints Registry; deadline 13 October 2015

[sensors] Ability to lookup a cached SensorReading without polling the sensor

[sensors] Add a threshold option

[sensors] Address questions around exposing high-level, low-level, and uncalibrated sensors

[sensors] Addressing finger printing concerns for sensor APIs

[sensors] Current draft links to tobie's github

[sensors] Does `SensorObserver` need a stop() method?

[sensors] Is a Promise-returning, "oneshot" method useful?

[sensors] Possibility to use "Readable Stream" as defined by the Streams API

[sensors] Provide a way of tying sensor requests to animation frames

[sensors] Relation to REST APIs and W3C Web of Things activities

[sensors] Sensors for continuously changing real valued properties

[sensors] Should sensor EventTarget be immediately available or should they be accessed through a promise?

[sensors] Spec should allow user agents to reduce or disable polling for power saving purposes

[sensors] When there are multiple sensors of a given type, how do we identify which one to instantiate?

Call for Consensus (CfC) to Approve revised DAP Charter and group name change - deadline 29 October 2015

Call for Consensus (CfC) to close the Web Intents Task Force - Deadline October 29, 2015

Call for Consensus to publish FPWD of Generic Sensor API completed successfully

Call for Exclusions: Generic Sensor API

CfC Generic Sensor API shortname - deadline Tue 13 October

CfC: Call for Consensus to publish FPWD of Generic Sensor API, deadline Friday 9 October

Closed: [sensors] Ability to lookup a cached SensorReading without polling the sensor

Closed: [sensors] Add a threshold option

Closed: [sensors] Add a timeout property?

Closed: [sensors] Address questions around exposing high-level, low-level, and uncalibrated sensors

Closed: [sensors] Agree on coarseness of frequency option

Closed: [sensors] Current draft links to tobie's github

Closed: [sensors] Does `SensorObserver` need a stop() method?

Closed: [sensors] Handle sensors with multiple values

Closed: [sensors] Have a good feature detection story

Closed: [sensors] Is a Promise-returning, "oneshot" method useful?

Closed: [sensors] Relation to REST APIs and W3C Web of Things activities

Closed: [sensors] Should sensor EventTarget be immediately available or should they be accessed through a promise?

Closed: [sensors] Should sensors require a privileged context?

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?

DAP-ACTION-739: Send cfc for 2 week approval of progressing with charter and name change

DAP-ACTION-740: Send cfc to close web intents tf

Draft minutes 2015-10-01

Draft minutes teleconference 15 October 2015

Finalizing DAP new charter

FPWD of Generic Sensor API available

Generic Sensor API Status update

Input to generic sensor API - current outstanding issues with respect to Geolocation and DeviceOrientation

Introduction of WebI2C and WebGPIO

Joint meeting: Geolocation and Automotive Working Groups, TPAC 2015, October 27, 2015

Reviewing the Charter

Summary of rationale for discontinuing the Web Intents work

TPAC ad hoc DAP Generic Sensor API meetings

Last message date: Friday, 30 October 2015 07:19:53 UTC