martin.konold at erfrakon.de
Wed Jun 16 10:38:08 CEST 2004
Am Mittwoch, 16. Juni 2004 04:34 schrieb Joon Radley:
Please let me know if the following explaination is nit sufficient.
> > No, we require the explicit time zone as we otherwise cannot
> > model several cases. IMHO the explicit time zone does not
> > hurt performance wise.
> It was aggreed that the Date/Time will always be UTC.
> Could you please provide us with your use cases (models) where you need
> explicit time zone information.
Yes, here is an excerpt from 20040604:
> > Am Friday 04 June 2004 09:48 pm schrieb Martin Konold:
> > Hi Bo,
> > > > Does not give anything and complicates the format.
> > Just for completeness: The rfc 2445 defines three kinds of datetime
> > values.
> > - local time zone
> > - utc time zone
> > - explicit time zone
> > The first kind is required in order to represent case like the following:
> > Imagine a global entity called church of emacs ;-)
> > There is a big shared calendar used globally by all members. The event is
> > defined as every morning from 7 am to 8 am is time to pray to RMS.
> > Such events are explicitly allowed by rfc 2445.
> > Please be aware of the fact that even though we are defining our own
> > storage
> > format we are _not_ free to restrict arbitrarily what can be represented
> > in
> > our new format. If we would do so we will not be able to represent cases
> > like
> > the above in Kolab and we will not be interoperable with many iTIP/iMIP
> > clients anymore. The later leads to _major_ problems with clients not
> > under
> > our control but _required_ by our customer e.g. 3Com Palm PDAs.
> > A similar problem arises with recurring events. In this case we also
> > require
> > the time zone value.
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
More information about the format