W3C home > Mailing lists > Public > public-sysapps@w3.org > June 2012

Re: System Level API spec editors

From: Dave Raggett <dsr@w3.org>
Date: Tue, 05 Jun 2012 15:18:06 +0100
Message-ID: <4FCE151E.60404@w3.org>
To: public-sysapps@w3.org
On 05/06/12 14:48, Mounir Lamouri wrote:
> On 06/05/2012 03:38 PM, Dave Raggett wrote:
>> On 05/06/12 13:47, Mounir Lamouri wrote:
>>> On 06/01/2012 09:16 PM, Carr, Wayne wrote:
>>>> Sensors API. Examples: No sample draft, but previous work was done in
>>>> DAP, likely Web Intents based and including sensors in local network.
>>> I think using Web Intents would be an abuse of the API.
>> The DAP WG discussion on this led to working on separate simple specs
>> for each sensor, starting with proximity. Web Intents is still
>> interesting when there is more than one instance of a sensor on a device
>> or you want to access sensors across the local network or even remote
>> sensors.
> So if there is more instance of a sensor the user will have to pick the
> sensor he/she wants to use? And I'm not sure how using a remote sensor
> would make sense...

One use case is sensing the temperature in different rooms, your garage
and garden green house. Today, you can buy wireless sensors for this,
and why shouldn't they become part of the Web tomorrow, as part of the
Web of Things?  This is already starting to happen, see e.g.


> In addition, I was assuming only applications were able to handle an intent.
> IMO, the API should whether provide a way to access the multiple sensors
> or just provide an unified value.

The sensor API applies to sensors you have identified (implicitly if
there is only one). Web Intents provides a framework for identifying
which sensor you want to use, or do we want to create a separate
discovery mechanism just for sensors, but if so, why?

> Cheers,
> --
> Mounir

Dave Raggett <dsr@w3.org> http://www.w3.org/People/Raggett
Received on Tuesday, 5 June 2012 14:18:36 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:36:09 UTC