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:50:14 +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: <6A1ADA52-B3E6-4AA4-9CEC-64911E804E1C@norbertlindenberg.com>
To: Jonas Sicking <jonas@sicking.cc>

On May 10, 2013, at 7:23 , Jonas Sicking wrote:

> On Wed, May 8, 2013 at 6:15 PM, Norbert Lindenberg
> <w3@norbertlindenberg.com> wrote:
>> In an API that's designed around a Date instance, time zone directives "respectTimezone" or "ignoreTimezone" are therefore meaningless. If the API is intended to interpret time zones (I don't know whether it is), it needs a different data type to represent field based time with time zone information [7].
> This isn't however accurate. The API does actually meaningfully work
> right now, it's just not described well as discussed above. The
> easiest way to describe how it works is through examples. There are a
> couple here:
> http://www.w3.org/2012/sysapps/web-alarms/#crossing-timezone-boundaries

How is the first example supposed to work? The Date object constructed has time value 1358780400000, which corresponds to 7:00 PST, but 10:00 EST. How does the implementation of the API know it should fire the alarm at time 1358769600000?

Received on Thursday, 9 May 2013 22:50:42 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:14:13 UTC