W3C home > Mailing lists > Public > public-device-apis@w3.org > March 2012

Re: web intents version of sensor api

From: <jeanfrancois.moy@orange.com>
Date: Mon, 26 Mar 2012 19:15:19 +0200
Message-ID: <F45661E8FBC74F4EB7E1E0386B562A75011608CC@ftrdmel0.rd.francetelecom.fr>
To: <mounir@lamouri.fr>
Cc: <public-device-apis@w3.org>
I agree with Mounir when he says that web intents should be limited to application to application interaction. We agree that it would be useful for some very specific use cases but it would be overkill for more common and popular use cases.

Oliver Don; Jean-Francois Moy

On 26 Mar 2012, at 17:34, Mounir Lamouri wrote:

> On 03/24/2012 09:36 AM, Carr, Wayne wrote:
>> Before dropping the sensor API I think it would be useful to consider
>> what a sensor API spec would look like if changed to using WebIntents. 
> The idea behind Web Intents is to have APP A requesting an activity to
> be done and APP B doing the requested activity. That means APP B will
> have to be able to *do* what is requested. If there is no Sensor API, I
> wonder how APP B would be able to do that...
> Also, I don't think "GetSomeValue" would be a really appropriate use
> cases. Web Intents should stay activities which mean the user will have
> to do some action. Here, the value is known by the system, it's all
> about retrieving the value, nothing else.
> --
> Mounir
Received on Monday, 26 March 2012 17:16:19 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:32:35 UTC