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

Re: Web Intents - Suggested Deliverables (part 2)

From: Paul Kinlan <paulkinlan@google.com>
Date: Tue, 22 Nov 2011 01:23:55 +0000
Message-ID: <CADGdg3CYfKLBZ-mDqvMdm6QTv=DOdoqkx7omtb9pKA_HqEOp7w@mail.gmail.com>
To: timeless <timeless@gmail.com>
Cc: public-web-intents@w3.org
On Tue, Nov 22, 2011 at 12:46 AM, timeless <timeless@gmail.com> wrote:

> I believe the terms in this email were introduced in my previous email
> [1], if not, hopefully they'll be further explained in subsequent
> messages.
>
> 1 On Deliverables.
>
> My hope is that this TF produces:
>
> A. Best Practices.
>
> Basic Audiences: Clients, User Agents, Partner Providers, and Users.
>
> Possibly one per audience or one unified document.
>
> It's unfortunately likely that each of these will be externally superseded.
>
> B. Provider Description Definition For Discovery.
>
> The Business Card definition. This could be an HTTP header, a mime
> defined file, and/or an html link notation. Its purpose is to
> advertise that a given URI supports a given Action. This enables
> Discovery of Partner Providers by User Agents.
>

I want to ensure that an custom intent tag is not excluded from this
discussion.  We should also scope out areas where discovery is not included
but provided for, in the case of esoteric devices not considered in this
scope that might have network discovery mechanisms etc.


>
> C. User Agent Bindings.
>
> How one requests an Action and how it is delivered (and how additional
> data is included) to a Partner Provider.
>
> D. Action Description Framework.
>
> How one defines an Action so that Clients know what to give as input
> and what Partners need to Provide for that Action.
>
> E. Basic Actions
>
> According to this Action Description Framework.
>
> Probably one per Action (Share, Call, Print, Location, ...).
>

I would say that we need to define that actions that we want under the
scope of the working group and thus managed by the spec.  Or we may decided
that no actions should be included in the spec other than for examples and
usecases.


>
>
> Now that could be one document, but I expect at least Five.
> Probably 3 + n  (Best Practices) + m  (Basic Actions).
>
> [1]
> http://lists.w3.org/Archives/Public/public-web-intents/2011Nov/0000.html
>
>


-- 
Paul Kinlan
Developer Advocate @ Google for Chrome and HTML5
G+: http://plus.ly/paul.kinlan
t: +447730517944
tw: @Paul_Kinlan
LinkedIn: http://uk.linkedin.com/in/paulkinlan
Blog: http://paul.kinlan.me
Skype: paul.kinlan
Received on Tuesday, 22 November 2011 01:24:30 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 22 November 2011 01:24:30 GMT