Re: [DRAFT] Web Intents Task Force Charter

The api to be defined wouldn't define how native apps would participate or register to participate, that's beyond scope for W3/DAP/WebApps and is an implementation detail.

It might be better to list the data sharing before registration as the primary goal is the sharing and registration is merely a means to that end.

----- Original Message -----
From: JOSE MANUEL CANTERA FONSECA [mailto:jmcf@tid.es]
Sent: Thursday, November 10, 2011 09:26 AM
To: Robin Berjon <robin@berjon.com>; public-webapps Group WG <public-webapps@w3.org>; public-device-apis@w3.org public-device-apis@w3.org <public-device-apis@w3.org>
Subject: Re: [DRAFT] Web Intents Task Force Charter

Hi Robin,

Thanks for setting this up.

My understanding is that intents could be used as a mechanism that will
allow the web browser to talk to other apps on the device, and those apps
can  be web or native ... From your description it seems it is only web
app to web app communication ...

best

El 10/11/11 14:54, "Robin Berjon" <robin@berjon.com> escribió:

>Hi all,
>
>here is a draft of the Intents joint Task Force charter for comments from
>WebApps and Device APIs. A TF charter is nothing formal and requires no
>overhead ‹ it can live as an email in a mailing list, it just documents
>the existence of the TF, and gives a few indications as to how it works.
>
>I've added some notes below about the points that may be contentious. If
>no one screams bloody murder by Monday I'll ask the Team to set things
>up. It's short but we've discussed this together last week, and DAP
>intends (no pun, err, intended) to rely rather heavily on Intents so we'd
>rather move fast rather than wait for WebApps to recharter, which could
>take a few months.
>
>
>"""
>The Web Intents Task Force works on a joint deliverable of the WebApps
>and Device APIs WGs that aims to produce a way for web applications to
>register themselves as handlers for services, and for other web
>applications to interact with these through simple requests brokered by
>the user agent (a system commonly known as Intents, or Activities).
>
>The mailing list on which the TF's discussions take place is
>public-intents@w3.org. The chair is Robin Berjon.
>
>Operational modalities such as whether or not to have phone and/or face
>to face meetings, as well as where to store the draft document are left
>to the TF to decide for itself. Decisions are made by consensus inside of
>the task force and do not require separate ratification by the wider
>groups.
>
>It is important to note that until such a time as the WebApps WG is
>rechartered with Intents in its list of deliverables, it will be
>necessary for participants in WebApps who are not in Device APIs and wish
>to make substantive contributions (just joining the discussion and
>providing comments is always fine) to make an RF commitment for this
>deliverable (not necessarily for other DAP deliverables, naturally). For
>more details on this, please contact the W3C Team.
>"""
>
>
>ISSUES:
>  € The description isn't terribly precise, but I think it works
>
>  € As I've said before, I am only putting myself forward as chair
>because so far no one else stepped up. I don't mind doing it, but I
>equally don't mind letting someone else do it. I don't expect it to be a
>very demanding position.
>
>WDYT?
>
>--
>Robin Berjon - http://berjon.com/ - @robinberjon
>
>


Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra política de envío y recepción de correo electrónico en el enlace situado más abajo.
This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at.
http://www.tid.es/ES/PAGINAS/disclaimer.aspx



---------------------------------------------------------------------
This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.

Received on Thursday, 10 November 2011 14:47:24 UTC