RFC Specifications

Abstract

This document defines the iCalendar data format for representing and exchanging calendaring and scheduling information such as events, to-dos, journal entries, and free/busy information, independent of any particular calendar service or protocol.

RFC 5545 supercedes the original iCalendar specification , RFC 2445.

Author

B. Desruisseaux, Ed., Oracle, September 2009

Abstract

This document defines a set of new properties for iCalendar data and extends the use of some existing properties to the entire iCalendar object.

Author

C. Daboo, Apple, Inc., October 2016

Abstract

The currently existing iCalendar standard (RFC 2445) provides only a simple text field ("LOCATION" property) for specifying the location where an event (or "TODO" item) will occur. While this may be adequate for human readers, it is difficult for automated systems to make use of. With the recent advent of tools and services (event aggregators, for example) which would benefit greatly from structured location data, the need to specify detailed venue information has become apparent. This document describes a proposed method for addressing this need.

Author

C. Norris, Eventful; McCullough, UC Berkeley; August 1, 2007

Abstract

This document defines extensions to the Web Distributed Authoring and Versioning (WebDAV) protocol to specify a standard way of accessing, managing, and sharing calendaring and scheduling information based on the iCalendar format. This document defines the "calendar-access" feature of CalDAV.

Author

C. Daboo, Apple; B. Desruisseaux, Oracle; L. Dusseault, Commercenet; March 2007

Abstract

This document defines extensions to the Calendaring Extensions to WebDAV (CalDAV) "calendar-access" feature to specify a standard way of performing scheduling operations with iCalendar-based calendar components. This document defines the "calendar-auto-schedule" feature of CalDAV.

Author

C. Daboo, Apple, Inc.; B. Desruisseaux, Oracle; June 2012