- From: Jean-Claude Dufourd <jean-claude.dufourd@telecom-paristech.fr>
- Date: Tue, 17 Apr 2012 18:52:39 +0200
- To: public-web-intents@w3.org
- Message-ID: <4F8D9FD7.5080403@telecom-paristech.fr>
Dear editors, In section 2.1, the following text seems to have a problem: /A Service is a web page which can handle an Intent, possibly returning a piece of data to the calling Client page. Again, the User Agent may have ways to deliver Intents to Services which are not web pages. /The first sentence says "a service is a web page..." The second sentence says "services which are not web pages". Seems like a contradiction to me. I suspect the first sentence should be "inverted": a web page which can handle an intent is a service Is that right ? In section 3.2 " The Intent object models a particular task which can be requested by handled by client pages." Would that be " The Intent object models a particular task which can be requested to be handled by client pages." ? Language in the last example and elsewhere makes me wonder about the "loading status" of page A defining an intent B. Page A is loaded. Then intent B is registered. Then page A is unloaded. What is the status of intent B ? If intent B is still "on", is page A reloaded upon a successful request to intent B ? Thanks 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
Received on Tuesday, 17 April 2012 16:53:13 UTC