KEP 2: Modification of datetime type, introduction of 'tz' sub-tag
h.helwich at tarent.de
Tue Nov 23 10:33:13 CET 2010
Am Montag, 22. November 2010 18:30:26 schrieb Georg C. F. Greve:
> Hi Hendrik,
> On Monday 22 November 2010 16.54:06 Hendrik Helwich wrote:
> > i wanted to say that i dont think it is a good way to adapt the
> > specification if some clients do not stick to it.
> When you notice an incongruency between clients and specification, that is
> indeed true. In this case, the reference clients have the same level of
> authority, and behave inconsistently to the specification.
> In other words: You have two sources of identical authority in
> So one of them needs to be adjusted to the other, and my thought was to
> make that change as uninvasive as possible. So if all clients already know
> RFC3339, the change of the spec would be the simpler solution. If one
> client cannot do this for some reason, all other clients need to adjust.
> FWIW: We fully agree that it is suboptimal to have to do this re-aligning
> ex- post, but it does not change the fact that it needs to be done.
> One reason for starting the KEP process was also to communicate and
> document these things in more detail for the future, to have a reference
> library that we can all refer to.
This is a great idea :-) It will be much easier to develop a kolab client if a
reference library would be available to use.
> Building that and some interoperability testing based upon it will take
> some time, but is definitely something we are planning to do as the Kolab
> ecosystem grows.
Great to hear that!
> Best regards,
More information about the format