Re: <meter> and <progress> (was RE: Implementor feedback on new elements in HTML5)

On Wed, Sep 2, 2009 at 3:25 PM, Leif Halvard Silli wrote:
> Thomas Broyer On 09-09-02 10.50:
>
>> (as said by Jonas, the temperature use case doesn't comply with
>> <meter>'s requirements, unless in a particular context the author
>> defines a lower and upper bound; for example, when listing current
>> temperatures of several cities, <meter> could be used with the lower,
>> resp. higher, bound being the lowest, resp. highest, current measured
>> temperature; to make it easier to compare city temperatures and for
>> example immediately if where you live will be hotter than where your
>> parents live)
>
>
> Not that one should force <meter> on things. But what is the difference from
> the hotness tags? The hotness of the tags varies over time - may be they
> only represent the last month's hotness.
>
> Likewise, if a newspaper display the summer temperature using an image of a
> thermometer, then it will usually only display the temperature ranges that
> are expectable for that period - and over all, on earth, for human beings.
>
> What is hot and what is cold varies through the year - at least where I
> live.

In this case, in this particular context, the author has chosen
(arbitrary) bounds and thus can use a <meter>:
<p>Today's temperature in Dijon, France: <meter min=-20 max=40
value=21>21°C</meter></p>
In this case, low="" and high="" could even be used to denote the
minimum and maximum forecasted temperatures in the whole country (or
region) and optimum="" could denote the average temperature for the
same day-of-year over the last 10 years (in French, we call it
"température normale de saison", I couldn't find the English
equivalent)

...this only applies to the particular context of a particular weather
forecast (other forecasts could use different bounds); you cannot use
it for any temperature, like the temperature of your CPU ship (which
would need other bounds)

-- 
Thomas Broyer

Received on Wednesday, 2 September 2009 13:46:03 UTC