W3C home > Mailing lists > Public > public-web-and-tv@w3.org > December 2011

Re: A profile for TV

From: Giuseppe Pascale <giuseppep@opera.com>
Date: Thu, 15 Dec 2011 16:30:08 +0100
To: public-web-and-tv@w3.org, david.corvoysier@orange.com
Message-ID: <op.v6jeoinx6ugkrk@giuseppep-x220>
On Thu, 15 Dec 2011 14:47:22 +0100, <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.

Totally agree, that is why I started this discussion. Is important to  
discuss on this list and have a common understanding before rushing into  
specification.

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

Agree, see other reply I sent where I talk of a meta-profile.
My proposal for this group is to work on a document that provides a guide  
on how to integrate an html5 (end co.) based environment with the layer  
right below it, to be able to support common use cases typical of TV  
services.

I suspect that many groups are looking or will be looking into this. And I  
thought that making the common part together in this group will bring  
several benefits:
- better interoperability
- save time by making the effort in one place and reusing it
- get involvement from the web community

The document (in my view) will still need to be "profiled" by business  
fora to adapt it to their business models, with the advantage of having  
already a pretty advanced starting point.

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

Yes, this is what I'm proposing, not a focus on a single set-up but on the  
overall architecture. Those points where a generic enough decision cannot  
be made will have to be documented and the "variables" be identified so  
that business groups can limit their work on defining the value of such  
"variables"


As mentioned in some other places, I'm not sure the word profile is  
appropriate for what I'm proposing. Would be probably better to talk about  
"Guidelines" for integration of tv services in a browser based environment  
(or something like this)

/g


-- 
Giuseppe Pascale
TV & Connected Devices
Opera Software
Received on Thursday, 15 December 2011 15:30:52 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:44:06 UTC