Why and when storing local time? (Re: Basic rationale of the KEP #2 design)

Georg C. F. Greve greve at kolabsys.com
Mon Mar 21 13:21:15 CET 2011

On Friday 18 March 2011 17.39:48 Florian v. Samson wrote:
> IMHU he proposed UTC + TZ-ID.

Actually Jeroen proposed UTCWND stored as RFC3339 + TZ-ID.

Where UTCWND = UTC With No DST, an artificial time zone that looks like UTC but 
ignores DST and maps the world as if DST did not exist.

But because DST exists, it is different to UTC and ultimately moves the 
ambiguity to the relationship between UTCWND and UTC.

> Ugh, I was reluctant to propose above due to its complexity, but proposing
> a wild mix of UTC and LocalTime date-times sounds pretty complex and
> error-prone as well.

Here we finally seem to agree on something. Hurrah! :-D

Best regards,

Georg C. F. Greve
Chief Executive Officer

Kolab Systems AG
Zürich, Switzerland

e: greve at kolabsys.com
t: +41 78 904 43 33
w: http://kolabsys.com

pgp: 86574ACA Georg C. F. Greve
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 308 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.kolab.org/pipermail/format/attachments/20110321/c4e3381d/attachment.sig>

More information about the format mailing list