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

Re: Webinos specification publicly available

From: Jean-Charles JC Verdié <jc.verdie@mstarsemi.com>
Date: Sat, 24 Sep 2011 16:58:30 +0200
Message-Id: <51306864-FAA7-4B96-848A-8BFC501D8BCC@mstarsemi.com>
Cc: "public-device-apis@w3.org" <public-device-apis@w3.org>, "Nilsson, Claes1" <Claes1.Nilsson@sonyericsson.com>, "public-web-and-tv@w3.org" <public-web-and-tv@w3.org>
To: Giuseppe Pascale <giuseppep@opera.com>
Hi Giuseppe and Claes

Le 24 sept. 2011 à 10:28, Giuseppe Pascale <giuseppep@opera.com> a écrit :

> Hi Claes,
> (CCing the web-and-tv public list)
> 
> On Fri, 02 Sep 2011 07:52:04 -0700, Nilsson, Claes1
> <Claes1.Nilsson@sonyericsson.com> wrote:
> 
>> FYI,
>> 
>> The Webinos EU research project has now made specifications publicly available: http://webinos.org/blog/2011/09/01/webinos-specifications-released/
>> 
>> For the DAP WG most relevant is the deliverable of API specifications, http://dev.webinos.org/deliverables/wp3/d32.html.
>> 
>> Where possible Webinos just refers to an existing API specification with first preference W3C. In some cases the existing specification does not fulfill Webinos requirements so modifications have been specified. For other requirements completely new API specifications have been specified. Examples of new APIs are:
> 
> [skip]
> 
>> 
>> TV Control API
>> 
> 
> As you may know, W3C have since April started a Web&TV IG.
> Since from what I can see these TV control APIs are at a very first stage,
> have you considered bringing your use cases and ideas to the Web&TV IG for
> feedbacks?
> If there are more people interested in this area (and I know there are,
> based on the discussion in the last IG F2F in Hollywood) could be a good
> chance to get the TV community to work together in this area.

> 
MStar is definitely interested in joining such an effort. Following my presentation in the web & tv event I had various feedback of other companies/people whom are also interested.

It would be interesting to work on how we can minimise the API overhead:
- using declarative approach (e.g. for channel list)
- using ssdp like mechanism 
- using messaging or any other approach 

Regards
JC
Received on Saturday, 24 September 2011 15:00:16 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 24 September 2011 15:00:18 GMT