- From: Francois Daoust <fd@w3.org>
- Date: Mon, 06 Jun 2011 12:14:10 +0200
- To: Russell Berkoff <r.berkoff@sisa.samsung.com>
- CC: public-web-and-tv@w3.org
Hi, On 06/06/2011 10:17 AM, Russell Berkoff wrote: [...] > I’ve repeated the Justification section since the W3 tools do not allow comments to be attached to submitted document. It's certainly good practice to use the mailing-list for discussions, so repeating here is de facto a good idea, but the wiki page could be directly updated as well to incorporate changes and comments. The tool would track all changes, allowing to highlight the changes and rollback if needed through the history tab. For comments, one simple solution would be to prefix the text with the name of the person who makes the change. Using wiki markup, one could actually simply start his comment with ~~~ (3 tildes) and the tool would replace that with the username when the page gets updated. See: http://www.mediawiki.org/wiki/Help:Signatures Francois. > > *Justification:* > > * Allows the creation of user interfaces utilizing companion device features, such as touch screens. Such interfaces may have greater usability than can be achieved with a traditional infra-red button based remote control and on-television interface. > > UPnP allows any device to act as an external control point. This device can determine the current state of the rendering device as well as control the device. > > * Standardisation could facilitate a new ecosystem of interfaces. > * Existing standards for home network communication are not available from the browser context > > Actually CEA-2014-B has a web-binding for UPnP devices. PHP has a binding for UPnP Devices (GUPnP). A desirable goal of this TF is to have W3C also publish these (or similar bindings). > > * Existing standards (UPnP?) do not support query and control of content playback where the content is not being streamed between devices > > UPnP embodies no such restriction. There is nothing in UPnP that precludes a MediaRenderer from publishing locally based changes of device state. If anything this would be encouraged to provide a consistent user experience. > > Regards, > > Russell Berkoff > > Samsung >
Received on Monday, 6 June 2011 10:14:35 UTC