W3C home > Mailing lists > Public > public-sysapps@w3.org > August 2013

Re: [Task Scheduler API ]: Timezone handling

From: Christophe Dumez <ch.dumez@sta.samsung.com>
Date: Fri, 23 Aug 2013 03:05:47 -0500
To: Xin Sun(联通集团技术部) <sunx5@chinaunicom.cn>
CC: "'public-sysapps@w3.org'" <public-sysapps@w3.org>
Message-ID: <C057847DC2553B44AFF9651526E2332F068326EFBF@staEX7mb4.telecom.sna.samsung.com>
Hi,

On Fri, 2013-08-23 at 15:50 +0800, Xin Sun(联通集团技术部) wrote:
> Hi, All
> 
>  
> 
> We’d like to propose some ideas regarding to Timezone handling issue
> in Task Scheduler API.
> 
>  
> 
> A typical use case of invoking Task Scheduling API -- Assuming a
> telephone conference will be hold at 10 o’clock a.m. in Beijing, the
> alarm would be awaked at night time if the attendee travels to United
> States. This is a timezone-aware situation.

I disagree, this would be a Calendar Alarm use case (Phase 2), not a
Task Scheduling one.

My personal opinion is that we don't need complex timezone handling in
the Task Scheduling API. Common use cases are:
- Use the current system timezone upon scheduling the task (Waking up an
application at a specific date/time, e.g. to check for updates).
- Use the provided time in whatever timezone in the current one (Alarm
clock use case).

I am really not sure there are strong valid use cases for being able to
pass a specific timezone identifier when registering an alarm (outside
of calendar alarms of course which are out of scope).

Also note that having a timezone offset is not sufficient. What you
really need is the exact timezone identifier to be able to account for
daylight savings (which you probably don't have in China but are common
in other countries).

Kr,

-- 
Christophe Dumez - Samsung Telecommunications America
Received on Sunday, 25 August 2013 18:01:03 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:36:14 UTC