- From: Vickers, Mark <Mark_Vickers@cable.comcast.com>
- Date: Mon, 2 Jan 2012 19:25:11 +0000
- To: "<david.corvoysier@orange.com> <david.corvoysier@orange.com>" <david.corvoysier@orange.com>
- CC: "<public-web-and-tv@w3.org>" <public-web-and-tv@w3.org>
I agree that any profile work needs to target any device that can receive a service. TVs, mobile, PCs and TVs should all use the same spec. The meaning of "TV" to me in the context of "TV Profile" refers to a profile capable of receiving a video (i.e. "TV") service, not the TV device. The "TV" term is, unfortunately, consistently confusing in this regard. Thanks, mav On Dec 15, 2011, at 5:47 AM, <david.corvoysier@orange.com> <david.corvoysier@orange.com> wrote: > Hi, > > I am not opposed to the definition of a TV profile, but before starting > the discussions, I also think we need to agree on the objectives. >> From a service provider point of view, the main driver of a W3C TV > profile has to be interoperability accross a wide range of devices, and > not compatibility with devices typically used in a specific ecosystem > (that is in my opinion up to dedicated business fora to define these). > Said differently, I am very interested in defining a W3C profile for TV > services, ie identifying what would prevent a service provider from > deploying the same TV web application on TVs, tablets, mobile phones and > desktops, but I am not really interested in defining a W3C profile for > TV devices, ie deciding on which subset of the specifications an > implementation on a specific range of TV devices can be tagged as HTML5 > compliant (because this kind of profile increases fragmentation instead > of reducing it). > > David Corvoysier > Orange Labs Networks & Carriers >
Received on Monday, 2 January 2012 19:43:27 UTC