I am a system administrator at a german university's computer science institute. We are currently taking a closer look at various groupware and calendaring systems, because we have a strong user demand for a working solution so that people can manage personal and public calendars and arrange apointments (as a first step for staff members, but in the future hopefully also with external partners).
As far as I can tell, it is widely accepted that iCalendar (RFC 2445) is the right choice as the data format for calendars, apointments, tasks, and journals (although implementations greatly vary regarding the supported subset, e.g. related to recursion rules or timezone support, for example). Similarly, exchanging ICS snippets through email seems to be an acceptable and accepted solution, and CalDAV (RFC 4791) support is getting better - slowly but constantly.
Another proof that this architecture is making good progress is the fact, that RFCs 2445bis and 2446bis are close to being published. If you look into it, you'll see that the architecture is really complex :-/ but on the other hand it brings standards specifications for a couple of features that are really, really cool. :-)
Yet another proof is that the CalConnect consortium is growing and the outcome so far looks promising.
Now, I would really like to know, whether there are plans on taking the bitter pill to switch to these IETF standards (full iCalendar support, CalDAV client and CalDAV server support), or whether there are no such plans at this time. I can imagine, that such a switch would be anything but trivial, but in the long term, it seems to be the right choice, I guess. I found an indefinite statement on the OX roadmap for 6.10, but it is says nothing about concrete standards support.
To be honest, at this point in time, I would prefer using the Darwin calendar server which is quite cool, but there seem to be no Web/AJAX clients as cool as the OX UI (in fact, I cannot find any CalDAV Web client at all worth mentioning).
(Similary, I wonder why OX does not use LDAP for users and groups, but that's another quesiton.)
Thanks,
-frank
As far as I can tell, it is widely accepted that iCalendar (RFC 2445) is the right choice as the data format for calendars, apointments, tasks, and journals (although implementations greatly vary regarding the supported subset, e.g. related to recursion rules or timezone support, for example). Similarly, exchanging ICS snippets through email seems to be an acceptable and accepted solution, and CalDAV (RFC 4791) support is getting better - slowly but constantly.
Another proof that this architecture is making good progress is the fact, that RFCs 2445bis and 2446bis are close to being published. If you look into it, you'll see that the architecture is really complex :-/ but on the other hand it brings standards specifications for a couple of features that are really, really cool. :-)
Yet another proof is that the CalConnect consortium is growing and the outcome so far looks promising.
Now, I would really like to know, whether there are plans on taking the bitter pill to switch to these IETF standards (full iCalendar support, CalDAV client and CalDAV server support), or whether there are no such plans at this time. I can imagine, that such a switch would be anything but trivial, but in the long term, it seems to be the right choice, I guess. I found an indefinite statement on the OX roadmap for 6.10, but it is says nothing about concrete standards support.
To be honest, at this point in time, I would prefer using the Darwin calendar server which is quite cool, but there seem to be no Web/AJAX clients as cool as the OX UI (in fact, I cannot find any CalDAV Web client at all worth mentioning).
(Similary, I wonder why OX does not use LDAP for users and groups, but that's another quesiton.)
Thanks,
-frank
Comment