- From: Dominique Hazael-Massieux <dom@w3.org>
- Date: Tue, 09 Nov 2010 12:03:37 +0100
- To: Arve Bersvendsen <arveb@opera.com>
- Cc: W3C Device APIs and Policy WG <public-device-apis@w3.org>
Le mardi 09 novembre 2010 à 11:54 +0100, Arve Bersvendsen a écrit : > 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. But this breaks as soon as you start looking at recurring events and daylight changes. To put another perspective on this, any serious calendaring application (and the iCalendar spec that most support) supports timezones at the individual date level, not at the event level, for this very reason. Given that we want to interoperate with them, I'm not sure how we could afford not to do the same. Dom (Tracker, this very much relates to ISSUE-81)
Received on Tuesday, 9 November 2010 11:03:54 UTC