[proximity/light] Way forward for Proximity/Light APIs

Currently we have the Proximity Events API [1] in CR and the Ambient Light API [2] in Last Call (following a return from CR). We have test cases and some implementations (but not enough to move forward) [3]. Let's call this v1. 

In addition we have work on a Generic Sensor API [3] that could be used as an alternative basis for creating specifications that offer the functionality offered by the Proximity Events API an Ambient Light API. This work is just beginning. Let's call this Alt.

The working group will have to make a choice of the way forward

(1) Progress v1 to Recommendation (with corresponding tests and implementations) and then consider whether we also need a new subsequent version based on the generic sensor API (Alt).

(2) Abandon/Shelve v.1 and focus on creating new specs based on the generic sensor API, Alt ,releasing this as the initial version.

The WG should consider this in light of current implementations and implementation plans, the timing for the generic sensor API, time frame requirements to have specifications, open issues and other concerns.

I suggest we discuss on the list and teleconference with the goal of making an explicit decision on the way forward, so we can communicate this clearly to ourselves and others.

Why don't we start with a list discussion?

regards, Frederick

Frederick Hirsch
Chair, W3C Device APIs WG (DAP)

www.fjhirsch.com
@fjhirsch

[1] http://www.w3.org/TR/2013/CR-proximity-20131001/

[2] http://www.w3.org/TR/2014/WD-ambient-light-20140619/

[3] http://www.w3.org/2009/dap/wiki/ImplementationStatus

Received on Tuesday, 23 June 2015 18:26:49 UTC