- From: Tobie Langel via GitHub <sysbot+gh@w3.org>
- Date: Wed, 27 May 2015 21:53:33 +0000
- To: public-device-apis@w3.org
WoT IG invited me to come and present the Generic Sensor API work during their weekly call. You can find the [minutes][1] online. Very productive call which confirms the need to focus on primitives thinking in terms of the [Extensible Web Manifesto][1]. This pushes us to consider the `Sensor` constructor as a very basic building block: an `EventTarget` which takes an input, or--paving the path for sensor fusion--multiple inputs, a processor (probably just a JS function) and some basic options (frequency, etc.). In turn, this lets us move the spec forward whatever the results of the performance constraint research AND allows for future extensions of the spec in currently out of scope areas (sensor fusion, WoT, and low-level, raw sensors). Next steps are: 1) advise the WoT IG about the first publication of the Generic Sensor API ED through their mailing list, 2) rewrite some of the [example sketches][3] found on the WoT's GitHub repository using the Generic Sensor API and send them through GitHub pull requests, 3) have follow-up conversations on the topic, probably through the WoT IG's mailing list or on this issue tracker. [1]: https://extensiblewebmanifesto.org/ [2]: http://www.w3.org/2015/05/27-wot-ap-minutes.html#item02 [3]: https://github.com/w3c/wot/blob/master/TF-AP/Example_sketch.md#example-scriting-api-mappings -- GitHub Notif of comment by tobie See https://github.com/w3c/sensors/issues/18#issuecomment-106089177
Received on Wednesday, 27 May 2015 21:53:35 UTC