Re: HTML5 TV Profile versus CEA2014

On Wed, 18 Jan 2012 23:29:27 +0100, GAUSMAN, PAUL <pg2483@att.com> wrote:

> A thought or two about "WebTV" issues in HTML5:
> •       Someone commented that "TV" is often confused with a device  
> instead of being thought of as a service. Additionally, I believe that  
> "WebTV" is being at times confused with an emulation of traditional TV  
> services with the addition of recent features like VoD, trick modes,  
> interaction, etc. To me, WebTV may be best thought of as a potential for  
> not only legacy and recent TV service instances, but anything which  
> includes digital media with a temporal aspect.

In the contest of the profile (and of this IG I would say) TV is for sure  
not the device (TV set) but any offer of commercial video services or as  
you say digital media with a temporal aspect.

> •       Creating a profile which lays out the support for legacy and  
> recent TV service features is very useful but if that's all it is, then  
> it is limiting. Folks who want to expand or morph TV in the future into  
> new experiences will not be supported by such a profile, unless it  
> includes methods for these extensions.
>

As I envision it we should aim to cover both. People will then use only  
what they need.
The profile should be regularly updated to avoid obsolescence.

/g


> Perhaps this concern is already addressed in the vision of the TV  
> Profile in the minds of the IG. Does anyone agree or disagree with my  
> observations here?
>
> Thanks!
> -Paul
>
> Q me
>
>
>
> -----Original Message-----
> From: Giuseppe Pascale [mailto:giuseppep@opera.com]
> Sent: Wednesday, January 18, 2012 7:29 AM
> To: public-web-and-tv@w3.org; Jacques DUMAREST
> Subject: Re: HTML5 TV Profile versus CEA2014
>
> Dear Jacques,
> is difficult to give a full reply to the first part of your question (if
> CEA or any other group is working on html5 profile) without violating
> confidentiality of such groups.
>
> What I can "observe" is that some organizations like OIPF have already
> referenced parts of HTML5 (& co) in their published specifications; it is
> expected that some others are working on HTML5 profiles as well.
> The risk once again is that each group comes up with similar but slightly
> different solutions. That is why I believe would be beneficial to get W3C
> involved in such activities (and this IG to act as the first contact
> point).
>
> This is the reason why we started to discuss the possibility of a TV
> profile in this group, as announced in [1], with latest draft available  
> in
> [2]
>
> My proposal would be for this group to reach out to other relevant
> industry groups once we have reached a critical mass.
> Anyway since this forum is public, individuals can already promote this
> activity externally.
>
> Note that IMO we should not /cannot replace what groups like the ones you
> mention have done and will do. Our aim should be to help such groups to
> correctly reference and use a set of web technology in a way that do not
> disrupt the web ecosystem.
>
> The final goal should be to minimize differences between all these
> profiles.
>
>
> [1] http://www.w3.org/mid/op.v6ffoua66ugkrk@giuseppep-x220
> [2] http://dvcs.w3.org/hg/webtv/raw-file/tip/tvprofile/tv.html
>
>
> On Wed, 18 Jan 2012 09:48:04 +0100, Jacques DUMAREST
> <jacques.dumarest@st.com> wrote:
>
>> Current standards such as DLNA, DTG, HbbTV are relying on CEA2014B for
>> Remote UI, and CEA2014 is based on HTML4.01. OTT standards evolution
>> will definitively want to take advantage of HTML5 new features:
>> Audio/Video tag, graphic, .... Do you know if CEA is planning to propose
>> an evolution of CEA2014/CE-HTML based on HTML5, or do you think it is up
>> to W3C & Web & TV IG to propose such a profile / standard?
>>
>> Thanks and Best Regards
>>
>> Jacques Dumarest
>
>
> --
> Giuseppe Pascale
> TV & Connected Devices
> Opera Software
>
>


-- 
Giuseppe Pascale
TV & Connected Devices
Opera Software

Received on Thursday, 19 January 2012 08:16:16 UTC