W3C home > Mailing lists > Public > public-web-and-tv@w3.org > April 2014

Re: Call for Volunteer to Drive the Initiative of Tuner API (or Channel Control API) Community Group

From: Jean-Charles (JC) Verdiť <jicheu@yahoo.fr>
Date: Thu, 03 Apr 2014 09:19:46 +0200
Message-ID: <533D0B92.5010202@yahoo.fr>
To: "HU, BIN" <bh526r@att.com>
CC: "Web and TV Interest Group (public-web-and-tv@w3.org)" <public-web-and-tv@w3.org>
Hi Bin & all,

Looks like I missed the meeting I shoudn't have :(

Anyway, having strongly promoted this until now, I'm obviously in :)

>
> -Name of the Group: there are several suggestions, such as TV Control
> API, TV Channel API, Channel Control API, etc. Considering the scope of
> API is not limited to broadcasting but also needs to cover all types of
> media sources, Channel Control API seems more appropriate. But it needs
> to be discussed and finalized
>

Channel can be confusing as we now have LCN for instance but Service is 
probably too DVB-centric. So Channel Control might do the job...

Given how many CG exist (hint: four figures number), shouldn't we make 
it more focused such as "tv channel control api"?


> -Scope of Work: an initial scope of work is highly encouraged
>
> -A Chair to lead the group and drive the result for the sake of quick
> time-to-market as Giri indicated above.

HbbTV is *not* developing its own specs (HbbTV does not define specs, it 
gathers technologies and orchestrate them). And it's too late for HbbTV 
v2 anyway :(

However, we need to consider feedback from the HbbTV Steering committee 
during the web and tv workshop in Munich: if we want this to get wide 
adoption we'll need to provide a comprehensive coverage of what other 
specs provide. No one's going to switch to a spec with less capabilities.

I would like to propose as a starter that the group declares that:
* it will gather existing specs (using liaison if necessary, is it 
possible in a CG?) and summarize them in the feature/api matrix the way 
the Media API TF did
* Orchestrate this result as a clear requirement for a future WG

There's no way we can reduce any "time to market". Our output will have 
to go to a WG and live its own life. But we can speed-up the 
requirements creation and propose some solutions so that the WG has a 
shorter lifespan.

>
> Thus we are calling for volunteer to drive the initiative of this Tuner
> API (or Channel Control) CG, i.e.:

I can't drive it alone due to all my other activities, but I'd happily 
co-chair it

Regards
JC

>
> -To finalize the name of the group
>
> -To drive the initial scope of work; and
>
> -To assume the leadership and drive the result of the Channel Control
> API Specification for the quick time-to-market
>
> Please let the group know if you are interested in driving this initiative.
>
> This closes my action item 191.
>
> Thank you
>
> Bin Hu | Service Standards | AT&T
>
> +1-650-946-8317
>
> [1] http://www.webinos.org/
>
> [2] http://dev.webinos.org/specifications/api/tv.html
>
> [3] http://www.w3.org/2011/webtv/wiki/Media_APIs/Tuner_API
>
Received on Thursday, 3 April 2014 07:20:20 UTC

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