W3C home > Mailing lists > Public > public-device-apis@w3.org > November 2011

Re: Proposal for ambient light

From: Christian Timmerer (ITEC) <christian.timmerer@itec.uni-klu.ac.at>
Date: Tue, 29 Nov 2011 12:59:07 +0100
Cc: "public-device-apis@w3.org public-device-apis@w3.org" <public-device-apis@w3.org>
Message-Id: <B17DB127-27EE-4207-9BCB-B34F26315DF8@itec.uni-klu.ac.at>
To: Robin Berjon <robin@berjon.com>

On Nov 28, 2011, at 5:53 PM, Robin Berjon wrote:

> Hi Christian,
> 
> On Nov 28, 2011, at 12:25 , Christian Timmerer (ITEC) wrote:
>> Regarding ambient light (and also some other devices/APIs you're discussing recently, e.g., vibrator) I'd like to draw your attention to [1] which provides comprehensive information about "sensory experience". The data formats which we're using are standardized in MPEG-V Part 3 referred to as "Sensory Information" (defining sensory effects) and we have also implementations (annotation tool, stand-alone player, Web browser plugin) and datasets. All details you can find at [1] but I'm also happy to provide further details if needed.
> 
> This certainly looks interesting, I'd be especially interested in looking at any JavaScript API you might expose and demos built on it.
We use existing HW which provides an SDK in order to control the devices based on the formats defined in MPEG-V. All is done within a plugin and the Web site only contains a link to the XML document comprising the sensory effect definitions. For ambient light we grab the frame content from the screen to automatically calculate the color for the individual lights, depending on which lights are available and which model shall be used.

Concerning demos, they're described and linked (YouTube videos) on our Web site (http://selab.itec.aau.at/)

> But before going there, I'm sorry to have to ask this question though: what kind of licensing terms is MPEG-V under? Altogether too often MPEG does highly interesting lab research which we then cannot deploy due to licensing restrictions :(
I'm aware about this issue and MPEG-V does not have any specific license other than the usual one.

I believe data formats (such as defined in MPEG-V) is one thing, APIs (like this group is defining) is another thing. For MPEG-V, MPEG defines the former but not the latter. However, an API shall neither mandate nor exclude a specific data format.

I thought it would be good to inform this group about these efforts because it's related to the topic discussed within this subject (ambient light) and others (e.g., vibration).

Best regards,
 -Christian

> 
> -- 
> Robin Berjon - http://berjon.com/ - @robinberjon
> 
Received on Tuesday, 29 November 2011 11:59:41 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:14:24 GMT