|
| Home About Future Events Resources Work Products Members Area Contact Us |
|
|
Calendaring and Calendaring-Related StandardsLinks to calendaring and calendaring-related standards or specifications on the way to becoming standards. We would appreciate additions to the list; please send any recommendations to Standards Recommendations to CalConnect.
This page last updated February 26, 2010
Calendaring and Calendaring-Related Standards and Guideshttp://www.rfc-editor.org/rfc/rfc5545.txtRFC5545 Internet Calendaring and Scheduling Core Object Specification (iCalendar) This is the new version (previously called RFC2445bis) which obsoletes RFC2445 iCalendar is the core data schema for calendaring information http://tools.ietf.org/html/rfc5546 RFC 5546 iCalendar Transport-Independent Interoperability Protocol iTIP) - Scheduling Events, BusyTime, To-dos and Journal Entries This is the new version (previously called RFC 2446bis) which obsoletes RFC2446 Specifies the mechanisms for calendaring event interchange between calendar servers http://www.ietf.org/rfc/rfc2447.txt?number=2447 iCalendar Message-Based Interoperability Protocol (iMIP) Specifies how to exchange calendaring data via e-mail http://www.rfc-editor.org/rfc/rfc4791.txt Calendaring Extensions to WebDAV (CalDAV) 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. http://www.calconnect.org/publications/calendaringglossaryv1.0.pdf Calendaring and Scheduling Glossary of Terms, V1.0 A Glossary of Calendaring and Scheduling Terms developed by CalConnect. http://www.ietf.org/rfc/rfc3283.txt Guide to Internet Calendaring This document describes the various Internet calendaring and scheduling standards and works in progress, and the relationships between them, as of its publication date (2004). http://www.ietf.org/rfc/rfc2426.txt vCard MIME Directory Profile This memo defines the profile of the MIME Content-Type [MIME-DIR] for directory information for a white-pages person object, based on a vCard electronic business card. http://www.ietf.org/rfc/rfc2739.txt Calendar Attributes for vCard and LDAP This memo defines three mechanisms for obtaining a URI to a user's calendar and free/busy time. These include manual transfer of the information, personal data exchange using the vCard format, and directory lookup using the LDAP protocol. Drafts and In-Progress Specifications for Future Standardshttp://tools.ietf.org/html/draft-ietf-calsify-rfc2447bis-07.txt iCalendar Message-Based Interoperability Protocol (iMIP) Current draft of the proposed revision to RFC 2447 (iMIP), also called RFC2447bis, being developed by the IETF Calendaring and Scheduling Standards Simplification Working Group (CALSIFY). http://www.ietf.org/internet-drafts/draft-desruisseaux-caldav-sched-08.txt Scheduling Extensions to CalDAV This document defines extensions to the Web Distributed Authoring and Versioning (WebDAV) protocol to specify a standard way of exchanging and processing scheduling messages based on the iCalendar Transport-Independent Interoperability Protocol (iTIP). This document defines the "calendar-schedule" feature of CalDAV. http://www.ietf.org/internet-drafts/draft-daboo-calendar-availability-00.txt Calendar Availability This document specifies a new iCalendar calendar component that allows the publication of available and unavailable time periods associated with a calendar user. This component can be used in standard iCalendar free-busy lookups, including iTIP free-busy requests, to generate repeating blocks of available or busy time with exceptions as needed. http://www.ietf.org/internet-drafts/draft-norris-ical-venue-00.txt Internet Calendaring and Scheduling Venue Component Specification 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. Comments are solicited and should be addressed to the working group's mailing list at ietf-ical-extensions@eventful.com and/or the authors. Note: This document depends on RFC2445bis, currently in draft status, and should not proceed without RFC2445bis. http://tools.ietf.org/id/draft-resnick-vcarddav-vcardrev-01.txt vCard Format Specification This document defines the vCard data format for representing and exchanging a variety of information about an individual (e.g., formatted and structured name and delivery addresses, email address, multiple telephone numbers, photograph, logo, audio clips, etc.). http://www.ietf.org/internet-drafts/draft-ietf-vcarddav-carddav-09.txt vCard Extensions to WebDAV (CardDAV) This document defines 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. http://www.ietf.org/internet-drafts/draft-ietf-enum-calendar-service-01.txt A Telephone Number Mapping (ENUM) Service Registration for Internet Calendaring Services This document registers a Telephone Number Mapping (ENUM) service for Internet Calendaring Services. Specifically, this document focuses on provisioning 'mailto:' (iMIP) and 'http:' (CalDAV) URIs in ENUM. Experimental, Deprecated or Obsolete Standards and Specificationshttp://www.imc.org/pdi/vcal-10.txtvCalendar, The Electronic Calendaring and Scheduling Exchange Format vCalendar was the predecessor to iCalendar and is now obsolete, although the vCalendar format is still in use, in particular in the mobile and travel industries. http://www.rfc-editor.org/rfc/rfc4324.txt Calendar Access Protocol (CAP) This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard of any kind. The Calendar Access Protocol (CAP) described in this memo permits a Calendar User (CU) to utilize a Calendar User Agent (CUA) to access an iCAL-based Calendar Store (CS).
|