[cosmo-dev] CalDAV interoperability

[Jeffrey Harris]

Hi Matthieu,

> I am documenting myself on calendaring systems and implementations of 
> the CalDAV protocol; that is how I found out about Cosmo. From what I 
> have gathered, I understand that Cosmo provides at least a CalDAV 
> server; does this server provide any kind of interoperability with other 
> CalDAV servers such as Zimbra or Google Agenda ? In other words, is it 
> possible to use Cosmo as a central server synchronizing itself with 
> other CalDAV-compliant servers ?

Cosmo provides a server that implements a CalDAV draft that pre-dates
RFC4791, so for instance Cosmo doesn't support ACLs yet.

Cosmo also doesn't support draft-desruisseaux-caldav-sched, which
describes the mechanisms for scheduling attendees centrally using an
INBOX collection on the server.

Some CalDAV servers currently support scheduling attendees whose
calendar home *isn't* on that server (by sending an iMIP,
iTIP-over-email, requests).  The resulting request is handled by the
calendar client out-of-band, not by the client's CalDAV server.

Server federation (akin to SMTP) where servers handle cross-server
requests in-band isn't something supported by any CalDAV server that I
know of at the moment, but I think a spec for federation is in progress,
see http://www.calconnect.org/tc-ischedule.shtml.

Cosmo isn't under active development at the moment, but I'm sure the
Cosmo user community would be delighted if someone stepped forward to
implement more of the fast-emerging CalDAV specs.

Sincerely,
Jeffrey