list at codefusion.co.za
Wed Jun 30 08:48:37 CEST 2004
Then we are in agreement. I have also supported the inclusion of the Z from the
start. It is not just explicit, but is a widely used convention and should tell the
reader/paser programmer at a glance that he/she is working in UTC.
Have we reached quorum then? Can this issue be laid to rest?
On Wednesday 30 June 2004 08:38, Martin Konold wrote:
> Am Mittwoch, 30. Juni 2004 08:12 schrieb Stephan Buys:
> > Agreed. UTC is the one safe bet that we have. And with the least amount of
> > "what-ifs". Daylight-saving, etc, etc is controlled through the timezones
> > which are client-driven.
> Sorry, but this will simply not work. There is a fundamental semantic
> difference between time with explicit timezone and local times without
> The only thing I am asking for (last mail from me towards the timezone topic)
> is make the timezone (UTC) _explicit_ (using a Z) not implizit.
> Doing so allows for later (?) inclusion of "local timezone" events.
> A last example:
> When the timezone changes to Daylight saving my local bus leaves at the same
> time in the morning (in local time) while my telephone conference with people
> living in South America changes.
> -- martin
> Dipl.-Phys. Martin Konold
> e r f r a k o n
> Erlewein, Frank, Konold & Partner - Beratende Ingenieure und Physiker
> Nobelstrasse 15, 70569 Stuttgart, Germany
> fon: 0711 67400963, fax: 0711 67400959
> email: martin.konold at erfrakon.de
> Kolab-format mailing list
> Kolab-format at kolab.org
Code Fusion cc.
Tel: +27 11 391 1412
Mobile: +27 83 294 1876
Email: s.buys at codefusion.co.za
E-mail Solutions, Kolab Specialists.
More information about the format