- From: Giuseppe Pascale <giuseppep@opera.com>
- Date: Wed, 23 Nov 2011 18:41:48 +0100
- To: "Jean-Claude Dufourd" <jean-claude.dufourd@telecom-paristech.fr>, "James Hawkins" <jhawkins@google.com>
- Cc: "Paul Kinlan" <paulkinlan@google.com>, public-web-intents@w3.org
On Wed, 23 Nov 2011 18:11:26 +0100, James Hawkins <jhawkins@google.com> wrote: > Not all interactions with the intents system must be registered using the > <intent> tag. For example in Chrome, an extension may register itself as > an intent service by adding the appropriate properties to its manifest. JC, all as I understand it, Web Intents is just a framework that allow application to "discover" other application via the mediation of the UA. Even though some "discovery" mechanisms are part of the spec itself (e.g. the mark-up elements) I don't think that is intended to be the only way. Furthermore, even if intents provide a way to discover a service, we also need to address the communication part to fully cover the requirements around communication with home network services. This last part needs to be done somewhere else (in DAP). > Perhaps I don't understand your use case though. Can you provide a > concrete example? > I was just going to send out an email on this topic, just hold on few secs :) /g > James > > On Wed, Nov 23, 2011 at 9:04 AM, Jean-Claude Dufourd < > jean-claude.dufourd@telecom-paristech.fr> wrote: > >> The user agent is not supposed to know the address of a service that is >> not yet discovered, so how does this sentence "Each service registers >> itself with the browser using <intent> tags that specify the action the >> service is capable of handling." get to happen ? >> How does the user agent get this intent tag ? It cannot be that the >> browser just reads a web page. >> Thanks >> JC >> >> >> On 23/11/11 17:26 , Paul Kinlan wrote: >> >>> The intent broker, the thing that resolves which services are >>> registered and which should be listed are managed by the user agent. >>> >>> Are you thinking there should be something else? >>> >>> P >>> >>> On Wed, Nov 23, 2011 at 4:14 PM, Jean-Claude Dufourd >>> <jean-claude.dufourd@telecom-**paristech.fr<jean-claude.dufourd@telecom-paristech.fr>> >>> wrote: >>> >>>> Dear all, >>>> >>>> From the discussion on this list, or the webintents.org site, or the >>>> chromium design document, I have not found an explicit mention of an >>>> intents >>>> broker entity, the entity that processes intents registrations and >>>> requests. >>>> Possibly the intents broker is assumed to be the user agent. >>>> Is that the only possibility, or just the most obvious of multiple >>>> possibilities ? >>>> >>>> Best regards >>>> JC >>>> >>>> -- >>>> JC Dufourd >>>> Directeur d'Etudes/Professor >>>> Groupe Multimedia/Multimedia Group >>>> Traitement du Signal et Images/Signal and Image Processing >>>> Telecom ParisTech, 37-39 rue Dareau, 75014 Paris, France >>>> Tel: +33145817733 - Mob: +33677843843 - Fax: +33145817144 >>>> >>>> >>> >>> >> >> -- >> JC Dufourd >> Directeur d'Etudes/Professor >> Groupe Multimedia/Multimedia Group >> Traitement du Signal et Images/Signal and Image Processing >> Telecom ParisTech, 37-39 rue Dareau, 75014 Paris, France >> Tel: +33145817733 - Mob: +33677843843 - Fax: +33145817144 >> >> >> -- Giuseppe Pascale TV & Connected Devices Opera Software
Received on Wednesday, 23 November 2011 17:42:21 UTC