- From: mwatson2 via GitHub <sysbot+gh@w3.org>
- Date: Tue, 07 Jul 2015 14:21:05 +0000
- To: public-secondscreen@w3.org
A special URL format is presently the only way we can integrate with DIAL apps, for example. If the page is capable of communicating with a remote DIAL app (for example www.netflix.com communicating with a Netflix DIAL application on a TV) and the UA supports DIAL the page needs some way to tell the UA to filter screens to only those with the requested DIAL app. We could make this a first-class API feature, for example with 'Discovery protocol' and 'Discovery application name' fields, but so far people have preferred to leave it as something to be encoded in the URL. ...Mark Sent from my iPhone On Jul 7, 2015, at 6:56 AM, Philip Jägenstedt <notifications@github.com> wrote: Thanks, Anton! Is there something sensible that could be implemented around this? Putting a microsyntax in the URL or requiring the resource to be fetched and analyzed both seem like slightly odd APIs for detecting support for device capabilities. — Reply to this email directly or view it on GitHub <https://github.com/w3c/presentation-api/issues/138#issuecomment-119209213>. -- GitHub Notif of comment by mwatson2 See https://github.com/w3c/presentation-api/issues/138#issuecomment-119219557
Received on Tuesday, 7 July 2015 14:21:08 UTC