RFC Compliance
From DAViCal Wiki
Up to release 0.5.x the development of DAViCal was largely following the needs of the publicly available client software. At that point there was fairly complete interoperability with the publicly available software at the time with support for CalDAV (Mulberry, Mozilla Calendar, Evolution and Chandler).
In later releases we have put some focus into ensuring that DAViCal communication is compliant with the relevant RFCs, regardless of whether the client software requires RFC compliance. In general, however, our intention is to pragmatically implement support for specification areas which are in actual use, prior to implementation of specification areas which might become used in the future.
From 0.9.8 there is significant advancement in spec implementation due to changes in the underlying structure for generating responses.
Related RFCs and Drafts
- RFC4791: CalDAV (Calendaring Extensions to WebDAV) (IETF Proposed Standard)
- CalDAV Scheduling Extensions to WebDAV (draft) (Internet-Draft, expires February, 2010)
- Defines the "calendar-schedule" feature of CalDAV.
- Changes from draft four are considerable (1)
- version 6 -> 7 changes are also significant, but hopefully this is close to the final one.
- RFC2446: iCalendar Transport-Independent Interoperability Protocol (iTIP) (IETF Proposed Standard)
- Scheduling Events, Free Busy, To-do's and Journal Entries
- Docs about implementation in Mozilla lightning and source code of the JS implementation.
- RFC3744: WebDAV Access Control Protocol (IETF Proposed Standard)
- RFC4918: WebDAV (IETF Proposed Standard)
- RFC5545: iCalendar (IETF Proposed Standard)
- RFC3253: Versioning Extensions to WebDAV (IETF Proposed Standard)
- S3.6 is referred to in RFC4791 S7.8
- The expand-property report and supported-report-set and supported-method-set properties are supported by DAViCal from 0.9.8 onwards.
- RFC4324 "Calendar Access Protocol" (Experimental Protocol)
- Similar to WCAP from Sun.
- Ticket-Based Access Control Extension to WebDAV (expired draft) - interesting nonetheless.
- RFC2616: HTTP 1.1 (Standards Track)
- RFC5397: WebDAV Current User Principal (IETF Proposed Standard) - supported from 0.9.6.2 onwards.
- RFC5689: Extended MKCOL for WebDAV (IETF Proposed Standard) - supported from 0.9.8 onwards.
- vCard Extensions to WebDAV (CardDAV) - Draft - not supported as at 0.9.8
- WebDAV Sync RFC (draft) - supported from 0.9.8 onwards.
- Defining Well-known URIs RFC - not supported as at 0.9.8
Interpreted Documentation
There has been some effort to break down the elements of a number of these RFCs into a broader structure within this wiki. This is best seen by starting at the DAV page, which it is hoped will evolve to be the root of a hierarchy of useful interlinked documentation, and may ultimately replace this page.
Current Status of DAViCal Compliance
As at 0.9.7 significant parts of the CalDAV specification are supported, along with substantial portions of DAV. Some initial elements of WebDAV access control are supported, but this area needs expansion. Similarly, the scheduling extensions to CalDAV (draft RFC) need to be developed further. Both of these two are expected to be a focus through the coming releases, with Permissions Redesign describing some of the changes in order to better follow RFC3744.
Further detail may be in these occasionally maintained pages covering specific important RFCs:
