Try out our new RRULE tool for creating RRULE compatible strings.

This specification reuses much of the same terminology as iCalendar [RFC5545], iTIP [RFC5546], WebDAV [RFC4918], and CalDAV [RFC4791]. Additional terms used by this specification are as follows:

Scheduling object resource: A calendar object resource contained in a calendar collection for which the server will take care of sending scheduling messages on behalf of the owner of the calendar collection.

Organizer scheduling object resource: A scheduling object resource owned by the "Organizer".

Attendee scheduling object resource: A scheduling object resource owned by an "Attendee".

Scheduling operation: Add, change, or remove operations on a scheduling object resource for which the server will deliver scheduling messages to other calendar users.

Scheduling message: A calendar object that describes a scheduling operation such as schedule, reschedule, reply, or cancel.

Scheduling Outbox collection: A resource at which busy time information requests are targeted.

Scheduling Inbox collection: A collection in which incoming scheduling messages are delivered.

This document was automatically converted to XHTML using an RFC to HTML converter with the original text document at the Internet Engineering Task Force web site at .  The original text document should be referred to if there are any errors or discrepancies found in this document.

Need to test your iCalendar feeds?

The iCalendar Validator provides developers and testers a method to validate their iCalendar feeds, which can take data from either a URL, file or text snippet and compare it against the RFC 5545 specification.  We believe we have one of the best iCalendar validation tools available on the internet. More information about the validator can be found here.