AW: Draft Charter of Proposed Channel Control API Community Group

The name change to TV Control is welcome (we used the same name in webinos ;)

I’d like to comment on the EPG topic in the charter as well. I agree with Giuseppe that EPG is one valid use case among others and therefor maybe adapt the points about EPG and make them a bit less prominent. For instance how about:


·         control and switch the TV sourcing based on channel identifiers

·         provide EPG information, including the list of TV programs and related information

Just as a thought, I see that the proposed CG already has more than the required number of supporters.

Kind regards
Alex

Von: HU, BIN [mailto:bh526r@att.com]

Giuseppe,

Thank you very much for the comment. I revised the charter based on your first comment. See attachment.

Regarding your 2nd comment on API being agnostic, I meant it being agnostic of underlying video sourcing technologies, e.g. multicast, broadcast, HTTP Live Streaming, etc. The metadata format is certainly for discussion as part of the work.

Hope it helps

Thank you
Bin

From: Giuseppe Pascale [mailto:giuseppep@opera.com]
Sent: Wednesday, April 23, 2014 4:46 AM
To: Gene Lian
Cc: HU, BIN; Jean-Charles (JC) Verdié; Alexander Futasz; mohammed dadas; Louay Bassbouss; Mark Vickers; Glenn Adams; Sung Hei Kim; Cyril Rickelton-Abdi; Gina Yeh; Marco Chen; Gary Chen; Evelyn Hung; public-web-and-tv; Daniel Davis (ddavis@w3.org<mailto:ddavis@w3.org>); Kazuyuki Ashimura; SULLIVAN, BRYAN L
Subject: Re: Draft Charter of Proposed Channel Control API Community Group

+1 on the name change, TV control sounds good to me.

About the charter, it looks good, just few comments:

* although EPG type of apps is one of the use cases, I don't think is the only one. The "hybrid" scenario is also quite relevant (app that overlay/control the linear TV video). In other words is OK to list EPG in the "scope of work" but I would rephrase the introduction to be more generic e.g.

"The technology gap between web apps and native apps is rapidly narrowing. Web-based application controlling various TV channels with detailed information regarding TV programs is becoming a more and more main stream channel control application for the integrated video service. Furthermore in many regions TV broadcasters are developing web applications that can overlay their channel in an hybrid broadcast/broadband environment"

* About the API being agnostic to the underlying format, I assume it should be part of the discussion we will have in the group to clarify what we mean by agnostic. E.g. we could have a low level API which exposes metadata coming from the broadcast stream, but NOT standardize the actual metadata format (not in this group, I mean) or you could have a more high level API which describes various concepts in an abstract way (that then needs to be mapped on the various formats. I don't think the charter should exclude any approach at this point, although I feel it would be better to start with a low level API along the lines of HTML5 media API and consider any further extension as a second step

* (Bin) I think you can go ahead and start the CG right away (http://www.w3.org/community/groups/propose_cg/). During next call we can discuss how CG members intend to run the group, so we make sure everybody knows how to get involved.

/g


On Wed, Apr 23, 2014 at 10:23 AM, Gene Lian <clian@mozilla.com<mailto:clian@mozilla.com>> wrote:
Hi Bin,

This is greeting from Mozilla and we'd like to let you know we've been
cooperating with our partners to work out an initiative version of our
own TV Manager API:

  http://airpingu.github.io/tv-tuner-api/index.html


, which seems to be matching the work scope of this group. You can also
find it on the GitHub about our previous discussions on the API design:

  https://github.com/airpingu/tv-tuner-api/issues


In short, this API spec is aimed to manage some general TV behaviours,
including scanning channel, switching channel and controlling tuners.
Actually, this API is not pretty much mature and is not yet supervised
by any existing W3C working groups.

Some of us are interested in this group and the following Mozillians
hope to be copied in this thread in the future:

  "Marco Chen" <mchen@mozilla.com<mailto:mchen@mozilla.com>>
  "Gina Yeh" <gyeh@mozilla.com<mailto:gyeh@mozilla.com>>
  "Evelyn Hung" <ehung@mozilla.com<mailto:ehung@mozilla.com>>
  "Gary Chen" <gchen@mozilla.com<mailto:gchen@mozilla.com>>
  "Gene Lian" <clian@mozilla.com<mailto:clian@mozilla.com>>

One personal thought about the name of this group. Based on the work
scope, it seems to me the API is not only related to the channel stuff,
but also some general TV functionalities. How about naming it as:

  "TV Manager API" or
  "TV Control API"

Looking forward to cooperating with you guys!

Regards,
Gene

----- Original Message -----
> From: "BIN HU" <bh526r@att.com<mailto:bh526r@att.com>>
> To: "Giuseppe Pascale (giuseppep@opera.com<mailto:giuseppep@opera.com>)" <giuseppep@opera.com<mailto:giuseppep@opera.com>>, "Jean-Charles (JC) Verdié" <jicheu@yahoo.fr<mailto:jicheu@yahoo.fr>>,
> "Alexander Futasz" <alexander.futasz@fokus.fraunhofer.de<mailto:alexander.futasz@fokus.fraunhofer.de>>, "mohammed dadas" <mohammed.dadas@orange.com<mailto:mohammed.dadas@orange.com>>, "Louay
> Bassbouss" <louay.bassbouss@fokus.fraunhofer.de<mailto:louay.bassbouss@fokus.fraunhofer.de>>, "Mark Vickers" <Mark_Vickers@cable.comcast.com<mailto:Mark_Vickers@cable.comcast.com>>, "Glenn Adams"
> <glenn@skynav.com<mailto:glenn@skynav.com>>, shkim@etri.re.kr<mailto:shkim@etri.re.kr>, "Cyril Rickelton-Abdi" <Cyril.Rickelton-Abdi@turner.com<mailto:Cyril.Rickelton-Abdi@turner.com>>
> Cc: public-web-and-tv@w3.org<mailto:public-web-and-tv@w3.org>, "Daniel Davis (ddavis@w3.org<mailto:ddavis@w3.org>)" <ddavis@w3.org<mailto:ddavis@w3.org>>, ashimura@w3.org<mailto:ashimura@w3.org>, "BRYAN L SULLIVAN"
> <bs3131@att.com<mailto:bs3131@att.com>>
> Sent: Wednesday, April 23, 2014 1:24:26 PM
> Subject: Draft Charter of Proposed Channel Control API Community Group
>
> Those on the “To” line: you have expressed interest in participating in this
> CG
> “Cc”: Web and TV IG, and related resources
>
> Hello my friends,
>
> In order to move forward this momentum, I drafted a simple charter of the
> Channel Control API Community Group in attachment. Please:
>
> -          Review this charter, and give any comments for improvement
>
> -          Give a suggestion if you are not happy with the name of the group
>
> -          Let us know if you are NOT in the “To” line, but is interested in
> participating in the group
>
> -          Let us know if you are in the “To” line, but I may have captured
> your name by mistake and you are NOT interested in participating in the
> group
>
> Thank you
>
> Bin
>
>