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

Jeroen van Meeuwen (Kolab Systems) vanmeeuwen at kolabsys.com
Tue Mar 15 20:09:01 CET 2011

Bernhard Reiter wrote:
> Am Dienstag, 15. März 2011 14:05:26 schrieb Jeroen van Meeuwen (Kolab
> Systems):
> > The argument on whether or not the ability to foretell the future is a
> > client capability is completely moot with a UTC timestamp, as long as the
> > operations to be executed against it are specified; write out something
> > UTC only negating the baseline UTC offset, now everyone knows what they
> > are reading.
> > 
> > You store something that never changes, you interpret it according to the
> > specification of the format, and only then present it to the user.
> I am not entirely sure what you are proposing.

I made the argument to show Georg's initial statements on why or how UTC 
wouldn't work or was ambiguous were not as true as they showed to have been 
perceived to be, that's it.

Kind regards,

Jeroen van Meeuwen

Senior Engineer, Kolab Systems AG

e: vanmeeuwen at kolabsys.com
t: +316 42 801 403
w: http://www.kolabsys.com

pgp: 9342 BF08
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.kolab.org/pipermail/format/attachments/20110315/52e5b238/attachment.html>

More information about the format mailing list