W3C home > Mailing lists > Public > public-web-intents@w3.org > December 2011

Re: Web Intents and Home Networking Scenarios

From: Greg Billock <gbillock@google.com>
Date: Wed, 21 Dec 2011 10:11:13 -0800
Message-ID: <CAAxVY9crN=x4iVGujjcdanGRMzeYf1FgKeBodv_5JORcQnY4zQ@mail.gmail.com>
To: "Nilsson, Claes1" <Claes1.Nilsson@sonyericsson.com>
Cc: WebIntents <public-web-intents@w3.org>
On Wed, Dec 21, 2011 at 8:49 AM, Nilsson, Claes1
<Claes1.Nilsson@sonyericsson.com> wrote:
>> -----Original Message-----
>> From: Greg Billock [mailto:gbillock@google.com]
>> Sent: den 20 december 2011 20:21
>> To: WebIntents
>> Subject: Re: Web Intents and Home Networking Scenarios
>> What's your view of the relative importance of the use cases, and
>> whether it makes sense to separate them like this? (I suspect the
>> user-facing impact would be that some simple apps wouldn't make use of
>> it at all, or that for more sophisticated apps users might face an
>> additional permission-granting step for advanced functionality.)
> I think that the type of use cases you describe, for example discover a TV or stereo gear on your mobile phone and use it as a remote control, are important. Your suggested approach on including "control actions" for common use cases in Web Intents is tasteful in the sense that it is a way to make it easy for application developers to implement common tasks according to the principle "make it easy for developers to do things they often do and make more seldom tasks possible".  However, it is a big decision if we want to break the architectural principle that Web Intents is a pure service discovery mechanism.

Using it purely for discovery in the home networking use case may be
the way to go. For web intents as a whole, we certainly intend the
feature to do more than service discovery. In fact, for many common
use cases (i.e. share, edit, view), service discovery is hidden within
the user agent - user interaction and the client would likely not get
any information at all about what service was used to handle the
Received on Wednesday, 21 December 2011 18:11:51 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:14:45 UTC