[Kolab-devel] KEP 2: Modification of datetime type, introduction of 'tz' sub-tag
Georg C. F. Greve
greve at kolabsys.com
Wed Nov 17 17:10:56 CET 2010
On Wednesday 17 November 2010 16.32:58 Hendrik Helwich wrote:
> Why not keep the established UTC time format like it is defined in the
> kolab specification? It holds all needed information and it would not be
> necessary to adapt the kolab specification on that point.
As you correctly pointed out, the specification is inconsistent in this point.
So right now the text says one thing, the equally authoritative clients
referred to in the document do something else, and apparently use just the
function based on RFC3339.
So sticking with the RFC means less code changed:
What old clients write is perfectly RFC compatible, and clients should not
implement their own parsers for this, but use the system function, which also
implements the RFC.
Best regards,
Georg
--
Georg C. F. Greve
Chief Executive Officer
Kolab Systems AG
Zürich, Switzerland
e: greve at kolabsys.com
t: +41 78 904 43 33
w: http://kolabsys.com
pgp: 86574ACA Georg C. F. Greve
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 308 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.kolab.org/pipermail/devel/attachments/20101117/5f0c5c67/attachment.sig>
More information about the devel
mailing list