Jump to content

CalDAV

From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by By cath (talk | contribs) at 16:04, 21 April 2023 (fix grammar). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

CalDAV
Communication protocol
PurposeAccess remote scheduling information
IntroductionMarch 2007; 17 years ago (2007-03)
Based onWebDAV
OSI layerApplication
Port(s)Any
RFC(s)RFC 4791, 6638

Calendaring Extensions to WebDAV, or CalDAV, is an Internet standard allowing a client to access and manage calendar data along with the ability to schedule meetings with users on the same or on remote servers.[1][2] It lets multiple users in different locations share, search and synchronize calendar data.[3] It extends the WebDAV (HTTP-based protocol for data manipulation) specification and uses the iCalendar format for the calendar data.[2] The access protocol is defined by RFC 4791.[1] Extensions to CalDAV for scheduling are standardized as RFC 6638.[1] The protocol is used by many important open-source applications.[3]

History

The CalDAV specification was first published in 2003 as an Internet Draft submitted to the Internet Engineering Task Force (IETF) by Lisa Dusseault. In March 2007, the CalDAV specification was finished and published by the IETF as RFC 4791, authored by Cyrus Daboo (Apple), Bernard Desruissaux (Oracle), and Lisa Dusseault (CommerceNet). CalDAV is designed for implementation by any collaborative software, client or server, that needs to maintain, access or share collections of events. It is developed as an open standard to foster interoperability between software from different vendors.[clarification needed]

Specification

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 ACLs are used, so each operation (view, edit, delete etc.) can be denied or granted per user. Therefore, the specification requires that CalDAV servers must support "WebDAV Access Control Protocol" (RFC 3744). The calendar resources must use iCalendar format, which allows the 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 their 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.

Software

Client

The list of CalDAV clients includes:[4]

Server

The list of CalDAV servers includes:[19]

See also

References

RFCs

  • RFC 2616 – HTTP
  • RFC 3744 – WebDAV Access Control Protocol
  • RFC 4791 – CalDAV
  • RFC 4918 – WebDAV
  • RFC 5545 – iCalendar
  • RFC 5546 – iTIP