Standards
CalConnect Standards, Specifications, Reports, Amendments, and Technical Corrigenda — formally approved deliverables defining normative requirements and technical protocols for calendar and scheduling interoperability.
<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 defines a set of extensions to the iCalendar VALARM component to enhance use of alarms and improve interoperability between clients and servers.</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 (<link target="https://www.calconnect.org/about/liaisons-and-relationships"/>).</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 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 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 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 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 (<link target="https://www.calconnect.org/about/liaisons-and-relationships"/>).</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 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 the vCard representation of resources.</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 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>This document describes a RESTful web service for calendar access and update.</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>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>