Hi Henri, > So different that I wonder if the cases belong in the same spec. The answer is yes. There are two cases to be covered by presentation API - One UA: 1. (having another screen to push pixels to) 2. ex: Local UA can display the video via HDMI / WiFi Display / Air Play to Remote Screen.
Two UAs: 1. There is also an UA on remote screen. 2. Local UA requests a Web Page to and is displayed by remote UA (ex: FxOS TV). > What's the relationship of the expected work of this new group to > DIAL? Has DIAL been abandoned? How is this work expected to improve on DIAL? Please refer to [1], one member from netflix suggested to extend DIAL for two UA case. [1] http://lists.w3.org/Archives/Public/public-webscreens/2014Aug/0079.html Sincerely yours. ----- Original Message ----- From: "Henri Sivonen" <hsivo...@hsivonen.fi> To: "dev-platform" <dev-platform@lists.mozilla.org> Sent: Wednesday, September 10, 2014 5:57:44 PM Subject: Re: Proposed W3C Charter: Second Screen Presentation WG On Wed, Sep 10, 2014 at 9:09 AM, L. David Baron <dba...@dbaron.org> wrote: > The W3C is proposing a revised charter for: > > Second Screen Presentation Working Group > http://lists.w3.org/Archives/Public/public-new-work/2014Jul/0001.html > http://www.w3.org/2014/secondscreen/charter-draft.html (At this point a question rather than a charter comment:) The charter says: "Alternatively, if the second screen device understands some other means of transmitting content to a display and a means of two-way message passing, the web content can be rendered by the remote device. In this scenario, a URL to the content to be displayed is sent to the secondary display to be rendered there. Because the content is rendered separately from the initiating user agent, pages hosted by other user agents may be authorized to control the remotely rendered content." This case seems technically totally different for the first case (having another screen to push pixels to). So different that I wonder if the cases belong in the same spec. In any case, the above-quoted use case seems to be the one DIAL was created to address. Yet, the charter, while listing numerous liaisons and dependencies, is silent about DIAL. Curiously, Wikipedia says DIAL was *formerly* used by Chromecast (https://en.wikipedia.org/wiki/DIscovery_And_Launch). What's the relationship of the expected work of this new group to DIAL? Has DIAL been abandoned? How is this work expected to improve on DIAL? -- Henri Sivonen hsivo...@hsivonen.fi https://hsivonen.fi/ _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
