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

Re: TZDate (formerly TimezonedDate) F2F notes

From: Arve Bersvendsen <arveb@opera.com>
Date: Tue, 09 Nov 2010 11:54:13 +0100
To: "Dominique Hazael-Massieux" <dom@w3.org>
Cc: "W3C Device APIs and Policy WG" <public-device-apis@w3.org>
Message-ID: <op.vlwgkndwbyn2jm@galactica>
On Tue, 09 Nov 2010 11:47:17 +0100, Dominique Hazael-Massieux <dom@w3.org>  

> Le mardi 09 novembre 2010 à 11:43 +0100, Arve Bersvendsen a écrit :
>> If preserving the originating time zone for an event has interest, then
>> that could just as well be an attribute on CalendarEventProperties.
> But as discussed previously, the timezone needs to be associated with
> all dates in an event, not the event as a whole.
> (typical example: registering an event matching a flight who leaves in a
> given timezone and arrives in a different one)

That's a type of event that starts and ends in different locations, and is  
a property of the event, not the absolute time it takes place - the plane  
won't land before it takes off.  THis is one of those cases where you  
really just want to work with the start and end date in UTC, and convert  
to local timezones for the start and end locations.
Arve Bersvendsen

Opera Software ASA, http://www.opera.com/
Received on Tuesday, 9 November 2010 10:54:50 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 14:53:46 UTC