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

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

From: Futasz, Alexander <alexander.futasz@fokus.fraunhofer.de>
Date: Thu, 3 Apr 2014 11:13:23 +0000
To: "jicheu@yahoo.fr" <jicheu@yahoo.fr>, "HU, BIN" <bh526r@att.com>
CC: "Web and TV Interest Group (public-web-and-tv@w3.org)" <public-web-and-tv@w3.org>
Message-ID: <4DE253E69D52FC499E11742FBB8BECF18680B73A@CURIE.fokus.fraunhofer.de>
Hi again,

See inline..

> -----Ursprüngliche Nachricht-----
> Von: "Jean-Charles (JC) Verdié" [mailto:jicheu@yahoo.fr]
> 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 :(

While it might be too late for that, it would good to have them as part of the CG if they are interested. I've reached out to a colleague to try and contact them.

> 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

I like the proposal. We can start with the parts from the DAE spec from OIPF/HbbTV that are related to this.

Best Regards
Received on Thursday, 3 April 2014 13:41:27 UTC

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