Standards
Standards, specifications, reports, amendments, and technical corrigenda defining normative requirements and technical protocols for calendar and scheduling interoperability.
<p>This document provides a reference lightweight document model called BasicDocument for generic documents, intended as an interoperable basis that allows systems to interchange generic document content while preserving semantics.</p>
<p>This document provides a reference lightweight document model called BasicDocument for generic documents, intended as an interoperable basis that allows systems to interchange generic document content while preserving semantics.</p>
<p>The Internet Calendaring and Scheduling Core Object Specification (iCalendar) (RFC5545) VTODO calendar component has seen limited adoption and use, mainly for personal reminders and to-do lists.</p> <p>This document updates and defines extensions to VTODO to provide improved status tracking, scheduling and specification of tasks to allow its use in other contexts, such as process control and project management.</p> <p>It also defines how Calendaring Extensions to WebDAV (CalDAV) (RFC 4791) servers can be extended to support certain automated task management behaviours.</p> <p>The Calendaring and Scheduling Consortium ("<tt>CalConnect</tt>") is a global non-profit organization with the aim to facilitate interoperability of collaborative technologies and tools through open standards.</p> <p>CalConnect works closely with international and regional partners, of which the full list is available on our website ().</p> <p>The procedures used to develop this document and those intended for its further maintenance are described in the CalConnect Directives.</p> <p>In particular the different approval criteria needed for the different types of CalConnect documents should be noted. This document was drafted in accordance with the editorial rules of the CalConnect Directives.</p> <p>Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. CalConnect shall not be held responsible for identifying any or all such patent rights. Details of any patent rights identified during the development of the document will be provided in the Introduction.</p> <p>Any trade name used in this document is information given for the convenience of users and does not constitute an endorsement.</p> <p>This document was prepared by Technical Committee <em>CALENDAR</em>.</p>
<p>This document defines a set of extensions to the iCalendar VALARM component to enhance use of alarms and improve interoperability between clients and servers.</p>
<p>This specification defines an extension to Web Distributed Authoring and Versioning (WebDAV) to search for WebDAV collections based upon a set of client-supplied criteria.</p>
<p>This document provides a mechanism to allow subscribers to calendar feeds to upgrade to a more performant protocol.</p>
<p>This document provides a mechanism in iCalendar for consensus scheduling of events, using the PARTICIPANT calendar component. It also defines new properties for use within the PARTICIPANT calendar component.</p>
<p>This document provides a mechanism in iCalendar for consensus scheduling, through the VPOLL calendar component.</p>
<p>This document specifies a protocol that uses calendar objects to provide scheduling interoperability between different calendaring systems. This is done without reference to a specific transport protocol so as to allow multiple methods of communication between systems. Other documents define profiles of this protocol that use specific, interoperable methods of communication between systems.</p> <p>The iCalendar Transport-Independent Interoperability Protocol (iTIP) complements the calendar object specifications by adding semantics for group scheduling methods commonly available in current calendaring systems. These scheduling methods permit two or more calendaring systems to perform transactions such as publishing, scheduling, rescheduling, responding to scheduling requests, negotiating changes, or canceling.</p>
<p>This specification provides a mechanism whereby subscriptions to external resources can be handled by the server.</p> <p>This specification updates <eref type="inline" bibitemid="RFC4791" citeas="IETF RFC 4791"/> to add new properties for the MKCOL request.</p>
<p>This document provides principles for establishing codes for the representation of written language conversion systems, including transliteration and romanization systems, in coded form, for use in any application requiring their expression.</p>
<p>This document defines methods for internationalization of vObject-compliant standards, such as vCard 4.0 (RFC 6350) and iCalendar (RFC 5545).</p>
<p>This specification updates <eref type="inline" bibitemid="RFC5545" citeas="IETF RFC 5545"/> by introducing a number of new iCalendar properties and components which are of particular use for event publishers and in social networking.</p> <p>This specification also defines a new STRUCTURED-DATA property for iCalendar <eref type="inline" bibitemid="RFC5545" citeas="IETF RFC 5545"/> to allow for data that is directly pertinent to an event or task to be included with the calendar data.</p>
<p>This document provides a list of codes to represent calendar systems, metadata to support the usage of those codes, and the corresponding maintenance procedures. The codes were devised for usage in any application requiring the expression of calendar systems in coded form, including for data interchange.</p>
<p>This document provides information models in support of the guidelines specified in ISO 690, including models for the citation of information resources, bibliographic references to information resources, and bibliographic reference lists. The models are intended to facilitate data encoding and interchange of citation and bibliographic information, and machine-readable bibliographic references and citations.</p>
<p>This document provides a reference lightweight document model called BasicDocument for generic documents, intended as an interoperable basis that allows systems to interchange generic document content while preserving semantics. This is the working draft (2019) edition; the model was subsequently published as CC 36010:2026.</p>
<p>This document describes the alignment of CalConnect practices and processes to the WTO TBT principles stated in the Decision of the Committee on Principles for the Development of International Standards, Guides and Recommendations. Actual practices in the CalConnect standardization process are described in CalConnect directives.</p>
<p>This document describes the concepts and definitions related to time scales and time scale authorities, and establishes codes representing their names, current or in the past, on the basis of data obtained from official sources. It specifies a registration authority that manages and disseminates the required code lists.</p>
<p>This document describes the agreement between CalConnect and ISO for the cooperation of standards development and publication. It provides the principles and necessary processes for collaborative cases between the parties: co-development of a standardization work item proposed by either party, and submission of a CalConnect document to ISO for its standardization process.</p>
<p>This document specifies guidelines for calendar and mail system operators to detect the occurrence of calendar abuse, to consider processes and procedures to mitigate calendar abuse, and to suggest acceptable (non-abusive) practices with calendar usage.</p>
<p>This document provides a concept system and a standard set of terminology related to date and time, from basic concepts to those of their representation. The scope of the vocabulary corresponds to that of ISO/TC 154/WG 5: Representation of dates and times.</p>
<p>This specification defines an extension to the calendar access protocol (CalDAV) to allow attachments associated with iCalendar data to be stored and managed on the server.</p> <p>This specification documents existing code deployed by multiple vendors. It is published as an Informational specification rather than Standards Track due to its noncompliance with multiple best current practices of HTTP.</p>
<p>This document specifies an integrity checking mechanism and related properties for:</p> <p>vObject (I-D.calconnect-vobject-vformat)</p> <p>vCard version 4 (vCard v4) (RFC 6350); and</p> <p>iCalendar (Internet Calendaring and Scheduling Core Object Specification) (RFC 5545)</p> <p>This work is produced by the CalConnect TC-VCARD and TC-CALENDAR committees.</p>
<p>This document updates RFC 5545 by defining a new repeating set of events known as a series. Unlike recurrences, each instance is a separate entity with a parent relationship to a specified template entity.</p>
<p>This specification updates the RELATED-TO property defined in RFC 5545 and introduces the new iCalendar properties LINK, CONCEPT and REFID, to allow better linking and grouping of iCalendar components and related data.</p>
<p>This document provides a standard, declarative representation of date and time and time scale components called the explicit form, a grouped time scale unit mechanism for grouping of date and time, and new duration representations and mechanics for the calculation of date time formulas involving duration. Only date elements from the Gregorian calendar and times from the 24-hour clock are supported.</p>
<p>This document provides a generalized representation of selection rules and recurring time intervals with repeat rules, in line with the time scale components and date and time representations of ISO 8601-1. The representations describe a superset of the RECUR recurrence rules of RFC 5545 while aiming to maintain compatibility with them. Only date elements from the Gregorian calendar and times from the 24-hour clock are supported.</p> <p>== Introduction</p> <p>The iCalendar standard (<eref type="inline" bibitemid="RFC5545" citeas="IETF RFC 5545"/>) has defined the de-facto standard for specifying recurring time intervals.</p> <p>However, its syntax is tightly bound to the syntax and assumptions of <eref type="inline" bibitemid="RFC5545" citeas="IETF RFC 5545"/>, requiring a data model representation that assumes a hierarchy of properties, parameters and data types that are not necessarily provided in other date and time representations, such as the International Standard for date and time representation, <eref type="inline" bibitemid="ISO8601" citeas="ISO 8601:2004"/>.</p> <p><eref type="inline" bibitemid="RFC5545" citeas="IETF RFC 5545"/> also relies on a number of indirect data inheritance rules that are not clearly specified and therefore not easily reproduced in other representations outside of iCalendar.</p> <p>This document describes a method to specify recurring time intervals with repeat rules in representation in line with those of the time scale components and date and time representations described in <eref type="inline" bibitemid="ISO8601" citeas="ISO 8601:2004"/>.</p>
<p>This specification defines a model for streaming calendar and contact data. This allows for a more efficient method for synchronizing collections of data and may be used to augment existing protocols such as CalDAV.</p>
<p>This document defines an extension to CalDAV that allows clients and servers that audit data on the server, to provide feedback based on the results of such audits. This can be used to signal clients about junk events, or other inappropriate content. It can also be used by clients to provide feedback about junk events, or other inappropriate content, that the server can act on in a manner that prevents the originator of the data from knowing it was discarded.</p>
<p>This memo lists specifications and resources available to developers of calendaring and scheduling applications.</p>
<p>This specification defines a framework and protocols for a push notification system that allows clients, application servers and push notification servers to interact with each other in a standardized manner.</p> <p>The Calendaring and Scheduling Consortium ("<tt>CalConnect</tt>") is a global non-profit organization with the aim to facilitate interoperability of collaborative technologies and tools through open standards.</p> <p>CalConnect works closely with international and regional partners, of which the full list is available on our website ().</p> <p>The procedures used to develop this document and those intended for its further maintenance are described in the CalConnect Directives.</p> <p>In particular the different approval criteria needed for the different types of CalConnect documents should be noted. This document was drafted in accordance with the editorial rules of the CalConnect Directives.</p> <p>Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. CalConnect shall not be held responsible for identifying any or all such patent rights. Details of any patent rights identified during the development of the document will be provided in the Introduction.</p> <p>Any trade name used in this document is information given for the convenience of users and does not constitute an endorsement.</p> <p>This document was prepared by Technical Committee <em>PUSH</em>.</p>
<p>This document defines new protocol features for CalDAV (<eref type="inline" bibitemid="RFC4791" citeas="IETF RFC 4791"/>) to improve the efficiency of synchronizing data changes between a client and server.</p>
<p>This document defines the Internet Calendar Scheduling Protocol (iSchedule), which is a binding from the iCalendar Transport-independent Interoperability Protocol (iTIP) to the Hypertext Transfer Protocol (HTTP) to enable interoperability between calendaring and scheduling systems over the Internet.</p>
<p>This document defines a new iCalendar (RFC 5545) component that allows small patches to be applied to large iCalendar data objects, allowing efficient data updates. It also describes how the new component can be used with the CalDAV calendar data access protocol (RFC 4791).</p>
<p>This document updates the iCalendar (<eref type="inline" bibitemid="RFC5545" citeas="IETF RFC 5545"/>) specification to allow a more compact representation of overridden recurrence instances.</p>
<p>This document defines a new iCalendar <eref type="inline" bibitemid="RFC5545" citeas="IETF RFC 5545"/> component that allows small "patches" to be applied to large iCalendar data objects, to allow for efficient data updates. It also describes how this new component can be used with the CalDAV calendar data access protocol <eref type="inline" bibitemid="RFC4791" citeas="IETF RFC 4791"/>.</p>
<p>This specification describes a new XML object that can be retrieved from hosts to discover applications, features and limits for that host or domain.</p>
<p>This document defines the format of Uniform Resource Identifiers (URIs) for calendar events, allowing users to add these events to their calendar application from any source that defines them, like web sites and printed QR codes</p>
<p>This document describes standard messages and interactions for service interactions with a system that hosts calendar-based information using SOAP. Hosted information can be either traditional personal and enterprise calendar information or services that support XML payloads developed in conformance with the WS-Calendar specification.</p>
<p>This specification describes a new property objectclass value for the vcard objectclass property defined in [REF] allowing schedulable entities to be marked as such.</p>
<p>This specification describes the vCard representation of resources.</p>
<p>This specification describes a new property for vCard Format Specification <eref type="inline" bibitemid="RFC6350" citeas="IETF RFC 6350"/> to allow the specification of objectclasses.</p>
<p>This document describes standard messages and interactions for service interactions with a system that hosts calendar-based information using SOAP. Hosted information can be either traditional personal and enterprise calendar information or services that support XML payloads developed in conformance with the WS-Calendar specification.</p>
<p>This document describes a RESTful web service for calendar access and update.</p>
<p>Index to Calendaring and Scheduling Standards.</p>
<p>An Introduction to Internet Calendaring.</p>
<p>An Introduction to Internet Calendaring.</p>
<p>This document describes a RESTful web service for calendar access and update.</p>
<p>Cal-WS Web Services API for Calendaring and Scheduling.</p>
<p>State of Resource Interoperability for Calendaring, Groupware, and Project Management.</p>
<p>This document is a recommendation from the CalConnect USECASE Technical Committee regarding the minimum interoperability of resources in the calendaring and scheduling domain.</p>
<p>This document lists use cases that utilize resources within the calendaring and scheduling application domain.</p>
<p>xCal - The XML Format for iCalendar.</p>
<p>This document defines a standardized form of Freebusy read URL to improve interoperability between client and server implementations, while extending the functionality and utility through the use of optional parameters.</p>
<p>Mobile Calendar Interoperability Test Suite.</p>
<p>Mobile Recurrence Interoperability Recommendations.</p>
<p>Mobile Calendar Interoperability Test Suite.</p>
<p>Min-IOP (Minimum Interoperable Subset) Use Cases for Tasks (VTODO).</p>
<p>Extended Daylight Savings Time Review and Considerations.</p>
<p>iCalendar Recurrence Problems and Recommendations.</p>
<p>iCalendar Timezone Problems and Recommendations.</p>
<p>Min-IOP (Minimum Interoperable Subset) Use Cases.</p>
<p>Min-IOP (Minimum Interoperable Subset) Use Cases.</p>
<p>Results from First Recurrence Questionnaire.</p>