- From: Christian Timmerer (ITEC) <christian.timmerer@itec.uni-klu.ac.at>
- Date: Mon, 28 Nov 2011 12:25:08 +0100
- To: Dominique Hazael-Massieux <dom@w3.org>
- Cc: public-device-apis@w3.org
Dear Dominique, all, 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. Best regards, -Christian [1] http://selab.itec.aau.at/ :-- :- Dr. Christian Timmerer :- Ass.-Prof., Multimedia Communication, Alpen-Adria-Universität Klagenfurt -------------------------------------------- Q: Why is this email three sentences or less? A: http://three.sentenc.es On Nov 28, 2011, at 12:10 PM, Dominique Hazael-Massieux wrote: > Hi, > > During our TPAC F2F, I took an action item (ACTION-467) to make a > concrete proposal for accessing information about the current ambient > light for a given device. > > Part of the discussion during TPAC was that particular item might be > better served by a CSS media query feature rather than an JavaScript API > — at least, the use cases that involved adapting e.g. the colors of the > user interface would be more logically served via such an approach. > > This would mean adding a "ambientlight" feature with min/max prefixes, > that would take values in SI lux units. > > <link rel="stylesheet" media="screen" href="default.css"> > <link rel="stylesheet" media="screen and (min-ambientlight: > 30000)" href="high-contrast.css"> > > If the group thinks that's a reasonable approach, DAP could propose to > start a joint WD with the CSS WG. > > Dom >
Received on Monday, 28 November 2011 11:25:52 UTC