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

Re: ACTION-129: Expressing timezones in the Calendar API

From: Philip Gladstone <pgladstone@cisco.com>
Date: Wed, 24 Mar 2010 17:37:01 -0400
Message-ID: <4BAA85FD.1040206@cisco.com>
CC: public-device-apis@w3.org

On 24-Mar-10 11:00, Dominique Hazael-Massieux wrote:
> Thanks for looking into this! 2 comments:
> - I think we should choose either the Olson identifier, or the URI one,
> but not mix them both up in a single field; I would personally suggest
> using the Olson identifier for v1
> - I'm slightly uncomfortable with binding the whole event to a timezone
> rather than to the specific dates that are defined in it (start, end,
> reminders, and recurrence limits); use cases that require binding to the
> dates rather than events are somewhat convoluted, but it seems like bad
> design to separate a datetime from its timezone in general. Also, since
> we mentioned other cases where we would need a "timezoned" datetime
> (e.g. reception times for messages), I still think we should work on
> TimezoneDate object rather than adding this on the side for events
> Dom
There are certainly calendar events that make sense with differing
starting and ending timezones. For example, United 177 leaves Boston at
11:15 America/New_York and arrives in San Francisco at 15:00
America/Los_Angeles -- and this is how the flight will appear in your
reservation. This is the 'obvious' form of the calendar event that
corresponds to my flight.

Thus I support having a timezoned datetime object rather than trying to
split out the timezone into a separate field.


Philip Gladstone
Distinguished Engineer
Product Development
Phone: +1 978-ZEN-TOAD (+1 978 936 8623)
Google: +1 978 800 1010
Ham radio: N1DQ

Cisco.com - http://www.cisco.com

This email may contain confidential and privileged material for the sole use of the intended recipient. Any review, use, distribution or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive for the recipient), please contact the sender by reply email and delete all copies of this message.

For corporate legal information go to:

Received on Wednesday, 24 March 2010 21:37:36 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:32:18 UTC