RFC Compliance/CalDAV

Covering the RFC4791: CalDAV points in detail and listing where DAViCal is believed to be in compliance with the specification.

Overview

From Section 2 of the RFC:

MUST support RFC5545: iCalendar as a media type for the calendar object resource format;
MUST support RFC4918: WebDAV Class 1;
MUST support RFC3744: WebDAV Access Control Protocol with the additional privilege defined in Section 6.1 of this document;
MUST support RFC4346: transport over TLS as defined in [RFC2818];
MUST support RFC2616: ETags with additional requirements specified in Section 5.3.4 of this document;
MUST support all calendaring reports defined in Section 7 of this document; and
MUST advertise support on all calendar collections and calendar object resources for the calendaring reports in the DAV::supported-report-set property, as defined in RFC3253: Versioning Extensions to WebDAV.

In addition, a server:

Section	Feature	Requirement	Status as at 0.9.8
2.	Expansion of repeated events	MUST	DAViCal now supports expansion of repeated events in HEAD, for release in 0.9.9.
2.	Support WebDAV ACLs	MUST	Partially supported. See RFC_Compliance/WebDAV ACL for full details
2.	Support for WebDAV Class 1.	MUST	(still to do: COPY is not yet supported).