W3C home > Mailing lists > Public > public-device-apis@w3.org > January 2010

Re: Thermometer API (Re: [sysinfo] draft ready for review)

From: Max Froumentin <maxfro@opera.com>
Date: Wed, 06 Jan 2010 11:42:51 +0100
Message-ID: <4B44692B.7040304@opera.com>
To: Thomas Roessler <tlr@w3.org>
CC: "public-device-apis@w3.org" <public-device-apis@w3.org>
On 05/01/2010 17:28, Thomas Roessler wrote:
> What's the use case for having the 0-1 state value?  What are
> "allowed" values, and how are they different from the minimum and
> maximum values the system "can report"?

It's a simple way to make it easy for the webapp author to find out if 
the global thermal state of the system is normal, or getting near 
dangerous levels. The author then doesn't need to perform 
hardware-dependent calculations to try and average out the different 
temperatures reported by the system: you can't really provide a single 
temperature for the system, since you can have many thermometers 
reporting values collected at different locations in your system.

> Also, are you assuming that
>
> currentTemperature = min + state * (max - min)
>
> (i.e., you interpolate in a linear fashion, as opposed to having,
> say, state^2 up there)?

No, I'm not assuming any relationship between current temperatures and 
the general thermal state. It's left to the API implementation.

> Editorial:
>
> s/Celcius/Celsius/g

Fixed, thanks.

Max.
Received on Wednesday, 6 January 2010 10:43:24 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 14:53:41 UTC