KEP2: Modification of datetime type, introduction of 'tz' sub-tag (wiki revision 10645 of 2010-11-19)

[Jeroen van Meeuwen (Kolab Systems)]

Christian Hilberg wrote:
> Hi everyone,
> 

Hi Christian ;-)

> Reading through the KEP2 discussions (as much as time permits), it appears
> to me that not every argument has been considered with equal weight. I
> would very much like to see the Kolab format succeed and the next release
> of the format spec to be a good and solid successor to the present one,
> which, though it has it's limitations, has proven it's ground to day.
> 

Your points hold some truth, no doubt about it. Thanks for providing, sorry to 
have stripped them from my reply ;-)

I think the potential confusion wrt. to changes required to any current Kolab 
client may lay within the assumption that any current Kolab client is required 
to be able to parse RFC3339 datetimes already - as this format is used in 
RFC2822 headers.

From where I'm sitting, should all these clients already be capable of parsing 
anything RFC3339, then it is the restriction to Zulu-format that is the 
addition, and duplication - insert the very wise quote here. I think we merely 
have a different perspective ;-)

The former notwithstanding, a change of pace wrt. which notation formats would 
be allowed in the standard naturally impacts all clients - exceptions 
notwithstanding.

That said, however, like I've been suggesting before, maybe a timely 
implementation of the <tz> sub-tag in combination with a fruitful discussion 
on datetime notation format changes (if any), justifies the current KEP be 
split.

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/20101207/4e37af8e/attachment.html>