- From: Wayne Carr <wayne.carr@linux.intel.com>
- Date: Thu, 07 Nov 2013 14:06:00 -0800
- To: David Singer <singer@apple.com>, Marie-Jose Montpetit <marie@mjmontpetit.com>
- CC: public-new-work@w3.org, olivier Thereaux <Olivier.Thereaux@bbc.co.uk>, Pablo Cesar <P.S.Cesar@cwi.nl>, Dominik <dominik.rottsches@intel.com>, "Kostiainen, Anssi" <anssi.kostiainen@intel.com>, Wayne Carr <wayne.carr@linux.intel.com>
This CG is specifically about using a second monitor, on purpose. Primary use case is a laptop has Miracast support and a nearby big display on a wall knows nothing about web pages but does support Miracast. The user has a slide show web page that shows controls and a small version of the slides on their tablet. They want to show a different web page designed for the screen characteristics of the second display. The new api is used to ask to display the slides on the second display, user says ok. the browser creates two display contexts, showing the second one on the second screen (using the devices Miracast support to translate the output to video). So, this CG is meant to be a simple API to enable already existing means of attaching multiple displays where the user specifically wants to place some content on a second display. On 11/5/2013 5:16 PM, David Singer wrote: > At least in some bodies, such as MPEG, I have argued that the number of physical screens, or indeed how many physical devices, that are used, is really something that is out of scope (i.e. MPEG expresses the characteristics of the content). > > I think we should be careful not to constrain implementations in our assumptions. It might be better to speak of ancillary content, and so on. > > How I design a 'distributed client' that uses multiple devices to present an experience is probably up to me. The most we may need to say is to have some way of saying that these two pieces of visual content should be presented "together" but their layup is up to the client (i.e. they haev no pre-defined spatial relationship). > > On Nov 5, 2013, at 23:24 , Marie-Jose Montpetit <marie@mjmontpetit.com> wrote: > >> Re-send of a reply to the web and TV IG. >> >>> I would support such a group and would like to participate but the vocable "second screen" is now a misnomer as a the tablet is becoming the first screen. How about the "companion screen" instead. In any case good idea as the demands of the non traditional screening devices require new APIs. I would probably be interesting to link this work to some of the webrtc work as well as to some of the "acceleration" mechanisms proposed in the IETF which while not directly related to the "how the device is connected" is inherently linked to user experience. >> /mjm >> Marie-Jose Montpetit >> mariejo@mit.edu >> >> >> > David Singer > Multimedia and Software Standards, Apple Inc. > > >
Received on Thursday, 7 November 2013 22:06:44 UTC