- From: Rottsches, Dominik <dominik.rottsches@intel.com>
- Date: Wed, 21 May 2014 06:26:58 +0000
- To: "public-webscreens@w3.org" <public-webscreens@w3.org>, Mark Watson <watsonm@netflix.com>
- CC: "Kostiainen, Anssi" <anssi.kostiainen@intel.com>, "Bassbouss, Louay" <louay.bassbouss@fokus.fraunhofer.de>, "mark a. foltz" <mfoltz@google.com>, Philipp Hoschka <ph@w3.org>, Daniel Davis <ddavis@w3.org>
Hi MarkW, >> All - do you agree that what is described above is a reasonable scope for the API? > > No. User Agents should be able to support protocols such as DIAL which > enable discovery of apps on remote devices which are capable of > rendering particular content types or services. In such a case the UA > can hand off rendering of URLs that do not resolve to html documents > to such apps. > > The messaging protocol with such an app would be app-specific, but > this is no different than the case of one web page communicating with > another rendered on a remote UA. This might be a desirable functionality for a user agent and it is in scope and actually already defined for the Network Service Discovery API: https://dvcs.w3.org/hg/dap/raw-file/tip/discovery-api/Overview.html#discovery-and-launch-protocol-dial Because of this, in my opinion, we should not extend the scope of Presentation API to expose a specific discovery protocol in order to avoid overlap with other ongoing W3C spec efforts, as well as keeping acceptance for Presentation API by implementors high. Dominik
Received on Wednesday, 21 May 2014 06:27:31 UTC