W3C home > Mailing lists > Public > public-script-coord@w3.org > April to June 2013

Re: [Alarm API] Time zone handling

From: Norbert Lindenberg <w3@norbertlindenberg.com>
Date: Fri, 10 May 2013 07:37:05 +0900
Cc: Norbert Lindenberg <w3@norbertlindenberg.com>, public-sysapps <public-sysapps@w3.org>, Marcos Caceres <w3c@marcosc.com>, public-script-coord <public-script-coord@w3.org>
Message-Id: <A3004C17-9E9F-4CB5-903B-5B69086819FB@norbertlindenberg.com>
To: Robin Berjon <robin@w3.org>

On May 9, 2013, at 22:01 , Robin Berjon wrote:

> On 09/05/2013 03:15 , Norbert Lindenberg wrote:
>> The time zone behavior in the spec seems to be based on a
>> misunderstanding of how JavaScript handles time zones. In particular,
>> there's a reference to "the timezone information of that [ECMASCRIPT]
>> Date object".
> 
> Wasn't TC39 working on a TZ-aware variant of Date? I thought that there was something but I can't seem to dig it up. It would come in handy, and not just here.

The TC39 internationalization ad hoc has recognized the need for better time zone support and is looking at proposals to provide API that lets callers specify the time zone used in constructing or interpreting Date objects, e.g. [1]. These proposals don't involve adding time zone information to the objects themselves. There has been a suggestion on es-discuss to do so, but this has found no support in the ad hoc [2].

It would help if we had a list of use cases that the Alarm API has to address, with their requirements for time zone support. Does such a list exist?

[1] http://wiki.ecmascript.org/doku.php?id=globalization:timezoneoffsets
[2] https://mail.mozilla.org/pipermail/es-discuss/2013-February/thread.html#28847

Norbert
Received on Thursday, 9 May 2013 22:37:33 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:37:49 UTC