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

Re: Mapping WebIntents to Network Service Discovery API

From: KOMATSU Kensaku <kensaku.komatsu@gmail.com>
Date: Sat, 7 Jan 2012 09:40:30 +0900
Message-ID: <CAKopxYyWCph=jLT4gjoadH7_fVHtnZ7vD8Adm7yVMdxxHTwW3A@mail.gmail.com>
To: WebIntents <public-web-intents@w3.org>
HI, I'm new in this ML. Also, l apologize if there was similar proposal.

Doing collaboration between Network Service Discovery API and Web Intents
API,
I guess one solution is making use of 'suggested applications' in current
picker UI (http://webintents.org/picker.html).

If Web Intents API has a feature of appending arbitrary services in that
area,
a developer'll be able to display such HN services obtained via Discovery
API.

For example (one proposal), extending spec(invocation feature) to handle
"suggested applications" is shown below.

void startActivity(in Intent intent, in optional onSuccess, in optional
onFailure, in optional suggestedApps);

where "suggestedApps" means list of application.

  suggestedApps = [ { "title": <arbitrary text>, "url": <web apps url> },
... ]

My senario is that

1. Web site discovers HN services (such as printer) via Discover API
2. Obtain informations (title and url) with XHR or so.
3. Passed above information into "suggestedApps"

And picker UI shows intent list in "suggested application" area, people can
use those HN services.

Additionally to say, above feature'll be useful not only HN senario but
also others.
For example, web apps can recommend specific intent based on the people's
behavior ( it means personalized recommendation ).

I guess such extensibility is useful for developing.

---
Kensaku Komatsu
NTT Communications


2012/1/7 James Hawkins <jhawkins@chromium.org>

> On Fri, Jan 6, 2012 at 3:37 PM, Clarke Stevens <C.Stevens@cablelabs.com>
> wrote:
> > I'm attempting to map the existing Network Service Discovery API
> > (previously introduced to the DAP WG) to a WebIntents model. The existing
> > API is here:
> >
> > http://people.opera.com/richt/release/specs/discovery/Overview.html
> >
> > This API is very simple (one method) and only implements discovery.
> > Communication with discovered devices is out of scope. In prototypes, we
> > have implemented communication with XHR (with cross-origin restrictions
> > relaxed for white-listed devices).
> >
> > I think the mapping is fairly straightforward with one exception. For
> some
> > protocols (e.g. UPnP) it is necessary to support device-initiated events.
> >
> > Since I think this same requirement would exist for other frequently used
> > WebIntents examples (like printing documents), I think there must be a
> > common solution, but I'm having trouble finding one.
> >
> > Here's a scenario that has probably already been explored that
> illustrates
> > my question:
> >
> > 1) The client wishes to print a document.
> > 2) The client requests a "print" WebIntent with the document as the data.
> > 3) A handful of printers that can handle the "print" WebIntent respond.
> > 4) The client selects a printer to handle the print request.
> > 5) Printing begins.
> > 6) The printer runs out of paper before the document is completely
> > finished.
> > 7) The client is notified that the printer is out of paper *** This is
> the
> > step I don't understand how to do with WebIntents ***
>
> Since there is no backround disposition, the service must display some
> UI for the duration of the intent handling; this is where the service
> (the printer driver I imagine) notifies the user the printer is out of
> paper.
>
> > 8) The user adds paper to the printer.
> > 9) The print job is completed.
> >
> > If someone could explain how WebIntents would implement this scenario
> > (especially step 7), that would be extremely helpful. If there are
> > existing documented examples you can reference that would be even better.
> >
> > Thanks,
> > -Clarke
> >
> >
>
>
Received on Saturday, 7 January 2012 00:40:59 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 7 January 2012 00:40:59 GMT