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

Re: A profile for TV

From: Bob Lund <B.Lund@CableLabs.com>
Date: Wed, 14 Dec 2011 09:24:35 -0700
To: Giuseppe Pascale <giuseppep@opera.com>, "Mark Vickers @ Comcast" <mark_vickers@cable.comcast.com>, 이현재 <hj08.lee@lge.com>
CC: "public-web-and-tv@w3.org" <public-web-and-tv@w3.org>
Message-ID: <CB0E1998.5D10%b.lund@cablelabs.com>
I would also like to work on this.

I find the idea of trying to identify a meta-profile intriguing. In
addition to the superset and subset profile motives that Mark identifies,
it seems to me there is also the motive for defining profiles that
provided increased, or more predictable, interoperability. Inherent in
such a motive is the perception that industry segments, e.g. TV, demand
better interoperability than is achieved in the Web today. I'm not sure I
share this perception but it be useful to see if it could be quantified,
i.e. what are those specific areas.


On 12/14/11 6:45 AM, "Giuseppe Pascale" <giuseppep@opera.com> wrote:

>On Wed, 14 Dec 2011 06:31:44 +0100, 이현재 <hj08.lee@lge.com> wrote:
>> Hi Mark,
>> I generally agree to have a clear definition/boundary of HTML
>> for TV experience would be very beneficial to entire industry.
>> In doing this, several things need to be considered that profiling is a
>> little bit above scope of technical standard activities and rather
>> to
>> business model of stake holders, also as Mark mentioned in the previous
>> mail, it depends onto physical device's capabilities in the projected
>> time
>> frame. The device today will be far poorer than next year device.
>agree on this and indeed what I envision is something different from
>traditional "profiles".
>I'm thinking more about a "meta-profile" that can be used by vertical
>industry groups (or single companies) as base for their work.
>Such "meta-profile" will still help to minimize fragmentation suggesting
>how things could be combined togheter to make a product or a vertical
>If the variables are identified beforehand, and all different profiles
>following this meta-profile have the same structure, is probably easier
>for people to understand the differences and for implementers to follow
>> Moreover, for helping implementer's develop program without confusion,
>> this
>> work should do more than simply choosing which tags, attributes are used
>> but also suggest values of attributes/properties such as default, min
>> max.
>Also on this, sometimes is difficult to find values that fits every
>ecosystem, but if these variable are extracted in a common place, is
>immediately clear what people have to look at when reading one of the
>profiles generated by this meta-profile. Also there are mistakes that
>been done in the past when doing "profiling" and that hurts
>interoperability; this meta-profile should clearly highlight what such
>mistakes are and why they should not be done.
>Giuseppe Pascale
>TV & Connected Devices
>Opera Software

Received on Wednesday, 14 December 2011 16:25:45 UTC

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