libkolabxml: When setting a start/end/etc. ...

Jeroen van Meeuwen vanmeeuwen at kolabsys.com
Mon Jul 16 12:49:44 CEST 2012


On Saturday, July 14, 2012 03:44:25 PM Christian Mollekopf wrote:
> On Friday 13 July 2012 13.17:11 Jeroen van Meeuwen wrote:
> > Hi there,
> > 
> > For resource management, I'm starting to implement a certain level of
> > timezone support - actually quite important.
> 
> Something for libkolab, maybe?
> 
> > Is it fair to assume that if no specific timezone is specified, any
> > datetime is UTC?
> 
> Depends on the usecase.
> In cDateTime UTC is indicated by a boolean, and in a string UTC is usually
> indicated by a "Z" appended
> (http://wiki.kolab.org/User:Mollekopf/Drafts/KEP:17#Date-Time).
> 
> Without any timezone identifier, it should be treated as floating-time.
> 

Right - how does one treat a floating-time in scheduling (the Python 
equivalent is a naive datetime) - create a 48 hour margin of error?

Kind regards,

Jeroen van Meeuwen

-- 
Systems Architect, Kolab Systems AG

e: vanmeeuwen at kolabsys.com
m: +44 74 2516 3817
w: http://www.kolabsys.com

pgp: 9342 BF08
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.kolab.org/pipermail/format/attachments/20120716/3696700a/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.kolab.org/pipermail/format/attachments/20120716/3696700a/attachment.sig>


More information about the format mailing list