- From: timeless <timeless@gmail.com>
- Date: Wed, 23 Nov 2011 13:48:38 -0500
- To: WebIntents <public-web-intents@w3.org>
On Wed, Nov 23, 2011 at 12:41 PM, Giuseppe Pascale <giuseppep@opera.com> wrote: > 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. discover and communicate. > 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. correct > 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. There's a difference between ensuring that there's a way to communicate (which should be covered here), and ensuring a requirement for a specific transport. > This last part needs to be done somewhere else (in DAP). It doesn't necessarily have to be DAP. It might be that you will just end up with someone who writes UPnP<->Intents gatewaying code and delivers it. You might deliver it to OS vendors (Microsoft, Google, Apple), or you might deliver it to Device vendors (HP, Dell, Lenovo, IBM), or you might deliver it through Markets (Addons.mozilla.org, App World, Apple's Store, Google's Store, Amazon's Store), or you might include it on e.g. CDs (or USB sticks or via a link from a QR code) which you ship with your UPnP Devices.
Received on Wednesday, 23 November 2011 18:49:09 UTC