- From: François Daoust via GitHub <sysbot+gh@w3.org>
- Date: Fri, 21 Aug 2015 13:01:25 +0000
- To: public-secondscreen@w3.org
The 1-UA and 2-UA possibilities are described in the spec introduction, except they are not given specific names there. Given that we keep referring to them as 1-UA and 2-UA in the group and elsewhere, it makes sense to mention these terms in the spec. One quick and easy fix would be to add something along the lines of "(commonly referred to as the 1-UA case)" next to the relevant bits. For reference, the relevant bits are: - **1-UA**: "For example, when a presentation display device is attached using HDMI or Miracast, the same UA that acts as the controller renders the presentation. Instead of displaying the presentation in another window on the same device, however, it can use whatever means the operating system provides for using the external presentation displays. In such a case, both the controller and presentation run on the same UA and the operating system is used to route the presentation display output to the presentation display." - **2-UA**: "If the presentation display is able to render HTML documents and communicate with the controller, the controller does not need to render the presentation. In this case, the UA acts as a proxy that requests the presentation display to show and render the presentation itself." See: http://w3c.github.io/presentation-api/#introduction FWIW, the charter contains similar wording in the scope section as well: http://www.w3.org/2014/secondscreen/charter.html#scope -- GitHub Notif of comment by tidoust See https://github.com/w3c/presentation-api/issues/164#issuecomment-133420064
Received on Friday, 21 August 2015 13:01:26 UTC