Editing CalDAV (section)

==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 [[Access control list|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" ([https://datatracker.ietf.org/doc/html/rfc3744 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.