Re: A profile for TV

On Mon, 02 Jan 2012 20:25:11 +0100, Vickers, Mark  
<> wrote:

> 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.

Completely agree.
Unfortunately I cannot come up with a better term and I also note that  
other groups working in this area also use the term "TV", so I think we  
are better off keep using it. Hopefully the document itself will clarify  
what is really intended when talking about TV services.


> Thanks,
> mav
> On Dec 15, 2011, at 5:47 AM, <>
>  <> 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

Giuseppe Pascale
TV & Connected Devices
Opera Software

Received on Wednesday, 4 January 2012 08:21:57 UTC