CalDAV

Poll without page-refresh

	del.icio.us
	Digg
	Furl
	Reddit
	Rojo
	Add to OnlyWire

Calendaring Extensions to WebDAV, or CalDAV is a standard allowing a client to access scheduling information on a remote server. It extends WebDAV (HTTP-based protocol for data manipulation) specification and uses iCalendar format for the data. The protocol is defined by RFC 4791. It allows multiple client access to the same information thus allowing cooperative planning and information sharing. Currently there are already many server and client applications supporting the protocol.

1 History
2 Architecture
3 Popularity
4 References
5 See also
6 External links
- 6.1 RFCs
- 6.2 Websites

History

The CalDAV specification was first published in 2003 by Lisa Dusseault as an Internet Draft submitted to the Internet Engineering Task Force (IETF), and it quickly gained support from several calendaring software vendors. In January 2005 the first interoperability event was organized by the CalConnect consortium. Since March 2007, the CalDAV specification is described in the RFC 4791. CalDAV is designed for implementation by any collaborative software, client or server, that needs to maintain, access or share collections of events. It is being developed as an open standard to foster interoperability between software from different implementors.

Architecture

The architecture of CalDAV (partially inherited from the underlying specifications) organizes the data (events, tasks, free-busy info, notes) in directories (collections), where multiple items (resources) reside. The resources and collections can be accessed by one or more users, using standard HTTP and DAV semantics to detect conflicting changes, or to provide locking.

For access control the concept of ACL is used, so each operation (view, edit, delete etc.) can be denied or granted per user. Therefore specification requires that CalDAV server must support "WebDAV Access Control Protocol" (RFC 3744). The calendar resources must use iCalendar format, which allows server to understand and process the data. Parsing the iCalendar items is necessary, because the server has to support a number of calendaring-specific operations such as doing free-busy time reports and expansion of recurring events. With this functionality, a user may synchronize his or her own calendar to a CalDAV server, and share it among multiple devices or with other users. The protocol also supports non-personal calendars, such as calendars for sites or organizations.

Popularity

Some developers have criticized CalDAV's complexity, claiming that the difficulty of implementing it will lead to implementations that can exhibit small bugs when talking to each other, much as has happened with IMAP for mail. However, several developers who went ahead with implementations have said it is not hard to get something working quickly^{[citation needed]}, and many organizations have committed to providing CalDAV products and serious momentum is now building behind having it become a viable standard for calendaring and scheduling across the internet.

On August 7, 2006, Apple Computer announced that Mac OS X 10.5 "Leopard" would include iCal 3.0, an application that supports the CalDAV access and scheduling standards.^[1] Mac OS X Server 10.5 "Leopard Server" includes iCal Server, which implements the CalDAV access and scheduling protocols.^[2]. The iCal Server has been released under an open source license as the Darwin Calendar Server.^[3]

Google Calendar supports CalDAV using iCal 3.x ^[4].

The Mozilla Calendar Project applications (Lightning, a plugin for Thunderbird and Sunbird, a standalone version) also support CalDAV calendars. Other freely available client software includes Evolution, Mulberry and Chandler.

A variety of free CalDAV server software is also available, with varying levels of adherence to specifications, including Darwin Calendar Server, Cosmo (the server-side companion to Chandler), DAViCal, Zimbra and several others.