Timezone / recurrence scheduling discussion for Kolab

Bernhard Reiter bernhard at intevation.de
Thu Nov 4 17:44:39 CET 2010

On Wednesday 03 November 2010 16:41:58 Hendrik Helwich wrote:
> my suggestion is to add an optional timezone XML element. The start and end
> time of an event could anyway be stored in UTC format. If the timezone
> element is available, the start and end time of the event could be
> transformed in a local time with the stored timezone information. If the
> timezone element is missing, the UTC timezone will be used.
> So this would be compatible with the old format.
> With a missing timezone element it will have the same semantic like in the
> old format. 

Sounds better than using two subrecurrances, as explained in my post
a few minutes ago. Now we need to know how that XML element would look

> If the timezone element is available and a recurring event does
> not cross a DST border, it also would be shown correctly in clients which
> only support the old format version.

This is not correct, though as long as DST deltas are the same and on the same 
day, it will even work across DST borders. (Also explained in my post a few 
minutes ago.) To be compatible with other clients, your client will have to 
implement that behaviour that Tobias and Joon explained.

Managing Director - Owner: www.intevation.net       (Free Software Company)
Deputy Germany Coordinator: fsfeurope.org. Coordinator: Kolab-Konsortium.com.
Intevation GmbH, Neuer Graben 17, Osnabrück, DE; AG Osnabrück, HRB 18998
Geschäftsführer Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.kolab.org/pipermail/format/attachments/20101104/6c07155a/attachment.sig>

More information about the format mailing list