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

Re: Web Intent work scope

From: James Hawkins <jhawkins@google.com>
Date: Fri, 22 Jun 2012 12:58:49 -0700
Message-ID: <CAO800Sw0Aw4E9enUgAgDOvexx3qBmNKNNQiVfbyTCU-SR=KKpQ@mail.gmail.com>
To: Robin Berjon <robin@berjon.com>
Cc: "Sun, Dan" <Dan.Sun@verizonwireless.com>, "public-web-intents@w3.org" <public-web-intents@w3.org>, "Nilsson, Claes1" <Claes1.Nilsson@sonymobile.com>
On Fri, Jun 22, 2012 at 6:41 AM, Robin Berjon <robin@berjon.com> wrote:

> Hi Dan,
>
> On Jun 22, 2012, at 15:10 , Sun, Dan wrote:
> > Is Web Intent expected to work only between web apps on client or any
> services provided on the client, regardless it is implemented natively or
> not, could be in the discovery scope of Web Intent?
>
> In theory, absolutely anything could provide an intent service. The exact
> mechanics of how that would happen for solutions other than Web apps have
> not yet been defined though (that said, in Chrome it'll hit the Chrome
> Store for intents, and presumably stuff there could be native for instance
> — but of course that's not standardised).
>
>
A few examples:
* The browser could be both a client and a service for many different
scenarios, e.g. providing intents in a page context menu.
* Claes (CCed) is working on exposing UPnP devices (home networking) as
intent services.
* Hypothetically the browser could act as a proxy between a web page client
and a system-level application acting as an intent service (e.g. edit
images from a web page in Photoshop).

Thanks,
James


> --
> Robin Berjon - http://berjon.com/ - @robinberjon
>
>
>
Received on Friday, 22 June 2012 19:59:51 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 22 June 2012 19:59:53 GMT