Calendaring and Scheduling Glossary of Terms
This page is an effort to compile, in one location, a common set of terminology with respect to calendaring and scheduling applications and standards. The document incorporates terminology already existing in calendaring standards such as RFC5545 (Internet Calendaring and Scheduling Core Object Specification (iCalendar)), RFC5546 (iCalendar Transport-Independent Interoperability Protocol (iTIP)), RFC6047 (iCalendar Message-Based Interoperability Protocol (iMIP)), RFC4791 (Calendaring Extensions to WebDAV (CalDAV)), RFC6638 (Scheduling Extensions to CalDAV (CalDAV)), as well as input from members of the Calendaring and Scheduling Consortium (CalConnect).
Some glossary terms may not appear in published standards today. These are common calendaring terms that are included so that everyone refers to components in the same manner.
As new standards evolve, the glossary will serve as a resource for those creating documents so that all the standards share a common set of terms.
Calendaring and scheduling implementers will be able to utilize the glossary to assist them as they read and decipher calendaring standards. Calendaring and scheduling users will be able to use the glossary to help them better understand the terminology deployed by applications written using calendaring standards.
Access control is a system which enables an authority (e.g., user or resource administrator) to control access to different entities in a calendar system. Typically vendors create Preference/Settings options to instantiate access control. Terminology varies considerably across products but broadly speaking access control is usually broken into two areas, read access and write access. Vendor terminology used for read access includes: ‘read’, ‘reviewer’, ‘proxy read’, ‘viewer’, ‘see all’, and ‘see only freebusy’. Vendor terminology for write access includes: ‘write’, ‘editor’, ‘proxy write’, ‘proxy’, ‘manager’, ‘administrator’, ‘designate’, ‘read/create/edit’, ‘make changes’, ‘manage’, and ‘edit’. (Cp. Delegate and Designate below.)
A list of access control elements that define access control to a particular calendar system entity. (Reference: RFC3744 for its use in a WebDAV context.)
Information pertaining to access to a resource by the physically disabled. This applies to Location Resources.
All information required to gain access to a resource. It applies to Location Resources.
Use of the terms alarm, reminder, alert, and notifications vary by implementation and can represent several things. They can represent a setting applied to an event by which a user indicates they want a ‘notification’ to be triggered to ‘remind’ them about some event or action (cp. VALARM in RFC5545. They can also be used to designate the type of ‘alert’ that serves as the notification (e.g., email message, audible sound, pop-up window). (Reference RFC4791 (CalDAV), RFC5545, RFC5546 (iTip).)
The MIME content type that indicates an iCalendar object expressed in XML.
A document object associated with a calendar component.
Specifies the participants or non-participants (e.g., room or resources) for an event. This property in iCalendar can contain multiple attributes specifying additional information, i.e., role, participation status, group membership, delegation, etc. (Reference: RFC5545.)
The process of configuring clients such as mobile devices or desktop applications to access a service, or class of service, with a minimum of input from the user of the device. See also Autodiscovery.
The process used to determine the services provided by a host, or for a domain, including retrieval of the recommended configuration values for those services. The autodiscovery functionality requires the service provider to declare in a standard way which services are available and what their configuration looks like for the requesting user. See also Autoconfiguration. (Reference: draft-daboo-aggregated-service-discovery.)
Accept scheduling invitations automatically with no human intervention.
The window of time in which a resource can be booked, relative to the start time of the event.
Extensions to the Web Distributed Authoring and Versioning (WebDAV) protocol to specify a standard way of accessing, managing and sharing calendar data based on the iCalendar format. Defined by two specifications, the first, RFC4791 (CalDAV), specifies a calendar access protocol that allows Calendar User Agents to access and manage calendar data. The second specification, RFC 6638, specifies a standard way of performing scheduling transactions with iCalendar-based calendar components. This document defines the “calendar-auto-schedule” feature of CalDAV. (Reference: RFC 4791, and RFC 6638.)
A collection of calendar items such as events, tasks, journal entries, etc. Examples include a person’s or group’s schedule, resource availability, and event listings. Typically an individual may own multiple calendars based on the same or different services.
A WebDAV resource representing an iCalendar component typically stored inside a Calendar Collection (cp. Component). (Reference: RFC4791.)
A server application that provides calendar user agents access to calendar stores.
A person who accesses or modifies calendar information.
- Software with which the calendar user communicates with a calendar service or local calendar store to access calendar information.
- Software that gathers calendar data on the Calendar User’s behalf.
A way to represent dates as a combination of eras, years, months, weeks, and days in formats used in many different parts of the world. A calendar system also defines the limits for those different quantities and how “date arithmetic” can be done to implement repeating dates. (See Wikipedia:Calendar for a description of many different calendar systems.)
The Calendaring and Scheduling Consortium is a non-for-profit partnership between vendors of calendaring and scheduling systems and tools, and users of those tools. Our purpose is to improve all aspects of calendaring and scheduling, in particular interoperability. We do this by improving existing standards, developing new standards, offering interoperability testing for calendaring and scheduling systems and tools, collaborating with other organizations with similar goals, and conducting periodic conferences where engineers and customers meet and interact in a collegial atmosphere. Virtually every important calendaring or calendaring-related standard since the late 2000s has been authored, edited and/or coedited by members of a CalConnect Technical Committee.
The IETF mailing list most commonly used for calendaring and scheduling standards development. See the page at https://www.ietf.org/mailman/listinfo/calsify to join.
An iCalendar property used to identify the calendar system used to represent dates and times within an iCalendar object. iCalendar currently only defines the GREGORIAN calendar system.
CalWS-REST is a CalConnect Proposal and CalWS-SOAP will be a parallel CalConnect Proposal which define an API of basic operations which allow creation, retrieval, update and deletion of calendar objects. In addition, query and freebusy operations are defined to allow efficient, partial retrieval of calendar data. (Reference: CalWS-REST Restful Web Services Protocol for Calendaring.)
Capacity of a resource, expressed as a numerical quantity. This applies to a Location Resource.
Extensions to the Web Distributed Authoring and Versioning (WebDAV) protocol to specify a standard way of accessing, managing, and sharing contact information based on the vCard format. (Reference: RFC6352
The process whereby a group comes to agreement on when and perhaps where to hold a meeting or carry out a task, by identifying the “best” time or location to help maximize participation and minimize inconvenience. For more information see 7 Things You Should Know About Consensus Scheduling. (See VPOLL.)
A response sent by an Attendee of an event to the event Organizer to propose a change to the event or task such as the scheduled date/time, list of participants, etc. (Reference: RFC5546)
In common usage ‘delegate’ may mean either a person who acts for someone else (cp. Designate) or refer to the act of appointing someone as a representative. The term has very specific meaning in the iCalendar and iTIP RFCs. In iCalendar, delegate means to specify that another individual, rather than oneself, should attend an event (cp. Delegator and Delegatee). In iTIP, delegate means to assign ownership of a task to another individual. (Reference: RFC5545 and RFC5546)
The attribute in iCalendar that specifies the calendar user(s) to whom a calendar user has delegated participation in an event. The actual attribute name is DELEGATED-TO. (Reference: RFC5545.)
The attribute in iCalendar that specifies the calendar user(s) that have delegated their participation in an event to another calendar user. The actual attribute name is DELEGATED-FROM. (Reference: RFC5545.)
The DTEND property for a VEVENT calendar component specifies the non-inclusive end of the event. (Reference: RFC5545.)
The DTEND property for a VEVENT calendar component specifies the non-inclusive end of the event. (Reference: RFC5545.)
The DTSTART property for a VEVENT specifies the inclusive start of the event. For recurring events, it also specifies the very first instance in the recurrence set. (Reference: RFC5545.)
A calendar object that is commonly used to represent things that mark time or use time. Examples include meetings, appointments, anniversaries, start times, arrival times, closing times.
The process by which public event data is gathered, formatted and distributed to calendar users. Often this takes the form of public, unauthenticated clients and/or feeds. See Public Event.
A list of free and busy periods for a particular calendar user or resource. Primarily used for scheduling resources or meetings with other people. Time periods may be marked as busy, free, busy-unavailable (sometimes referred to as out of office) and busy-tentative.
The most common civil calendar system in use today, recognized by many international bodies
The name of Apple, Inc’s desktop calendar user agent. Often used as an abbreviation for the iCalendar standard.
According to IETF RFC3935, “The IETF has traditionally been a community for experimentation with things that are not fully understood, standardization of protocols for which some understanding has been reached, and publication of (and refinement of) protocols originally specified outside the IETF process …The mission of the IETF is to produce high quality, relevant technical and engineering documents that influence the way people design, use, and manage the Internet in such a way as to make the Internet work better. These documents include protocol standards, best current practices, and informational documents of various kinds.”
An IETF standard (RFC6047) that describes how iTIP messages are exchanged via email.
An IETF Standard (RFC5546) that specifies a protocol that uses the iCalendar object specification to provide scheduling interoperability between different calendar systems without reference to a specific transport protocol so as to allow multiple methods of communication between systems (see iMIP, iSchedule).
A draft specification that describes how iTIP messages are exchanged via HTTP (Reference: Internet Calendar Scheduling Protocol (iSchedule) draft-desruisseaux-ischedule.)
All information on other resources available as part of a resource.
A general term from common usage to convey a request for an attendee’s participation in an event. In RFC documents the more specific term is request (cp. Request).
A draft specification that defines a JSON representation of vCard data. Reference: jCard - The JSON format for vCard
From RFC5545, one or more descriptive text notes associated with a particular calendar date. Examples of a journal entry include a daily record of a legislative body or a journal entry of individual telephone contacts for the day or an ordered list of accomplishments for the day.
An attachment associated with a calendar component that is stored and managed on a CalDAV server. (Reference draft-daboo-caldav-attachments.)
Maximum number of instances of an event a resource can be scheduled for from a given point in time.
An Internet media type, sometimes a Content-type after the name of a header in several protocols whose value is such a type, is a two-part identifier for file formats on the Internet. The identifiers were originally defined in RFC2046 for use in e-mail sent through SMTP, but their use has expanded to other protocols such as HTTP, RTP and SIP and for other uses (e.g., OS-level file type identification for application/file association).
Number of simultaneous bookings allowed by a resource, during scheduling.
Any calendar system that is not a Gregorian Calendar (e.g., Chinese, Hebrew, Islamic). See Wikipedia for a description of many different calendar systems.
A Standards Development Organization primarily focused on web services standards. OASIS and CalConnect have reciprocal memberships for joint work on WS-Calendar.
A calendar user who creates a calendar item, requests free/busy information, or published free/busy information. It is an Organizer who invites Attendees. (Reference: RFC5545.)
A calendar containing events for one calendar user (the owner), and typically only accessible to the owner, or others authorized by the owner (cp. Calendar, Public Calendar, Shared Calendar).
A level of importance and/or urgency calendar users can apply to Tasks and Events. (Reference: RFC5545.)
RFCs define the objects and components of their subject which in turn have properties which have values (sometimes referred to as ‘property parameters’ or ‘property attributes’). These “property parameters” contain meta-information about the property or the property value. Property parameters are provided to specify such information as the location of an alternate text representation for a property value, the language of a text property value, the value type of the property value, and other attributes. Throughout this glossary are references to component, property, and attribute following this usage. (Reference: RFC5545.)
A calendar containing primarily public events and accessible to anyone or a specific group of calendar users (cp. Calendar, Personal Calendar, Shared Calendar). See Public Event.
An event meant to be published to or distributed to anyone or a specific group of calendar users. These generally differ from personal events in that they contain much more detail about the event, its location, categories and other properties. See Event Publication and Publish.
Generally, to make calendar information, such as freebusy time, available to a select group or to the public. From the RFC for iTIP, “The ‘PUBLISH’ method in a ‘VEVENT’ calendar component is an unsolicited posting of an iCalendar object.”
An iCalendar property used to define a repeating pattern for events or tasks.
An iCalendar RRULE parameter indicating which calendar system to use for expanding this RRULE.
This property is used to identify a specific instance of a recurring VEVENT, VTODO, or VJOURNAL calendar component.
An event or task that happens more than once either with a regular interval (ex. daily, weekly, monthly) that can be expressed by a rule or with an explicit series of dates/times.
A broadly used term in multiple RFCs to represent an action. That action may be a query for property values from a client to a server (cp. RFC4791, a query between a client and a server that results in object creation, modification, or deletion (cp. RFC4791 and RFC5545), and it is the name of a method in iTIP that makes “an explicit invitation to one or more attendees” (among other things, cp. RFC5546). (Reference: RFC4791, RFC5545, RFC5546, and Internet Calendar Scheduling Protocol (iSchedule).)
A resource in the scheduling context is any shared entity, that can be scheduled by a calendar user, but does not control its own attendance status. Resources can be of “Location”, “Equipment”, or “Role” type.
Specifies whether there is an expectation of a reply from a specific calendar user (Reference: RFC5545.)
Briefly, the process by which organizers and attendees plan events or assign tasks. More specifically the term encompasses the exchange of request/invitations and responses between organizers and attendees of scheduled events, tasks or journal entries.
An attribute that contains contact information for the scheduling approvers, if approval is required.
A calendar that has been published, typically on an HTTP server. See Publish.
A representation of an item of work assigned to an individual. In RFC5545, these are “VTODO” calendar components, which are groupings of component properties and possibly “VALARM” calendar components that represent an action-item or assignment.
The MIME content type for encoding iCalendar objects. Example usage includes: email, web pages.
Areas of the Earth that have adopted the same local time. Time zones are generally centered on meridians of a longitude, that is a multiple of 15, thus making neighbouring time zones one hour apart. However, the one hour separation is not universal and the shapes of time zones can be quite irregular because they usually follow the boundaries of states, countries or other administrative areas. In RFC5545, time zones are represented using “VTIMEZONE” calendar components, each with a Time Zone Identifier (TZID) that can be used to tie a particular date and time to a specific timezone.
A client/server protocol used for distributing Timezone data. The protocol improves the accuracy and speed of distributing timezone data to ensure clients are kept up to date with sometimes rapidly changing definitions. It also allows clients to avoid having a complete database of all timezones - instead they can download timezone data on a case-by-case basis. (Reference draft-douglass-timezone-service.)
A property of an event that defines whether it will appear free or busy in free/busy time searches.
A VALARM calendar component is a grouping of component properties that is a reminder or alarm for an event or a to-do. For example, it may be used to define a reminder for a pending event or an overdue to-do. VALARMs will thus be included within VEVENT and VTODO components. VAVAILABILITY - An iCalendar component that is used to describe periods of time for which a calendar user is available for scheduling of events. (Reference: draft-daboo-calendar-availability
A VEVENT calendar component represents a scheduled amount of time on a calendar. For example, it can be an activity; such as a one-hour long, department meeting from 8:00 AM to 9:00 AM, tomorrow. Generally, an event will take up time on an individual calendar. The VEVENT is also the calendar component used to specify an anniversary or daily reminder within a calendar.
A grouping of component properties that represents either a request for free or busy time information, a reply to a request for free or busy time information, or a published set of busy time information.
A VJOURNAL calendar component is a grouping of component properties that represent one or more descriptive text notes associated with a particular calendar date. The DTSTART property is used to specify the calendar date with which the journal entry is associated. Examples of a journal entry include a daily record of a legislative body or a journal entry of individual telephone contacts for the day or an ordered list of accomplishments for the day. The VJOURNAL calendar component can also be used to associate a document with a calendar date.
A proposed extension to iCalendar. VPOLL is a new component which allows conducting a “poll” via iTIP exchanges to accomplish consensus scheduling for an event or appointment. See Consensus Scheduling. (Reference: draft-york-vpoll.)
A VTODO calendar component is a grouping of component properties and possibly VALARM calendar components that represent an action-item or assignment. For example, it can be used to represent an item of work assigned to an individual; such as “turn in travel expense today”.
An extension to Web Distributed Authoring and Versioning (WebDAV) that allows efficient synchronization of the contents of a WebDAV collection. (Reference: RFC6578.)
An OASIS (Organization for the Advancement of Structured Information Standards) working group tasked with defining a cross-domain standard for passing schedule and interval information between and within services built around CalWS. The product of the working group will be a standard also named WS-Calendar incorporating the CalWS proposal. See CalWS.
A standard that defines an XML representation of iCalendar data. (Reference: xCal: The XML format for iCalendar - RFC6321.)