- From: Tobie Langel <tobie@sensors.codespeaks.com>
- Date: Mon, 11 May 2015 16:59:34 +0200
- To: public-device-apis@w3.org
- Cc: rick Waldron <waldron.rick@gmail.com>, Rich Tibbett <richt@opera.com>, "boris@smus.com" <boris@smus.com>, domenic Denicola <domenic@domenicdenicola.com>, Mounir Lamouri <mounir@lamouri.fr>, Tim Volodine <timvolodine@google.com>
Hi all, Here's the long awaited status update on the Generic Sensor API. Please note that, as advised previously on this mailing list[1], I'm now representing Intel in this group and offer to co-edit the Generic Sensor API specification on Intel's behalf with Rick Waldron if he's still up to it. As agreed upon, the work mode has been essentially asynchronous and via Github issues[2], where we've had plenty of lively and productive conversations in late 2014. I went through all of those over the past couple of days, summarizing the conversation, suggesting resolutions were appropriate[3], and adding actions[4] when more work seemed necessary. I further split the work into what seemed essential to fit into a FPWD[5] and would could be handled at a later stage[6]. I invite all those of you who have specific interest in this work to peruse the issues and comment accordingly, but for the benefit of all, here's a TL;DR: Overall, there's broad consensus on the scope of the work. The purpose of the Generic Sensor API is to provide an API and framework for this group and others to quickly and easily edit specs for sensors with a consistant, performant, secure, and extensible API. The issues where there's contention (around API design) or where there's no clear cut solution for the time being (e.g. around discoverability and feature detection) all share a common trait: they need to be informed by a better understanding of performance constraints and how and when sensors register in the browser. Next steps involve liaising directly with engineers working on sensor implementations with the different vendors (intros are welcome) and working on a first draft of the spec in parallel. I'll be happy to go over your questions during our next call, through this mailing list or via the issue tracker[2. Thanks, --tobie --- [1]: https://lists.w3.org/Archives/Public/public-device-apis/2015May/0002.html [2]: https://github.com/w3c/sensors/issues [3]: https://github.com/w3c/sensors/labels/proposed-resolution [4]: https://github.com/w3c/sensors/labels/action [5]: https://github.com/w3c/sensors/milestones/FPWD [6]: https://github.com/w3c/sensors/milestones/Post-FPWD
Received on Monday, 11 May 2015 15:00:02 UTC