A Glossary of Calendaring and Scheduling Terms.

This document, developed by the XML Technical Committee, specifies a SOAP web services Protocol for calendaring operations. This protocol has been contributed to OASIS WS-CALENDAR as a component of the WS-CALENDAR Specification under development by OASIS. CalConnect and OASIS have agreed that any future work by CalConnect TC XML or OASIS WS-Calendar (or other committees in CalConnect and OASIS) on their respective versions of CalWS will be harmonized to maintain consistency between the versions. CalConnect and OASIS reserve the right to jointly and formally agree to fork the specifications at some point in the future if need arises.

This CalConnect guide introduces internet calendaring and the major standards and specifications related to calendaring and scheduling.

This document, developed by the XML Technical Committee, specifies a RESTful web services Protocol for calendaring operations. This protocol has been contributed to OASIS WS-CALENDAR as a component of the WS-CALENDAR Specification under development by OASIS. CalConnect and OASIS have agreed that any future work by CalConnect TC XML or OASIS WS-Calendar (or other committees in CalConnect and OASIS) on their respective versions of CalWS will be harmonized to maintain consistency between the versions. CalConnect and OASIS reserve the right to jointly and formally agree to fork the specifications at some point in the future if need arises.

This document was created by the USECASE Technical Committee of the Calendaring and Scheduling Consortium. The document lists use cases that utilize resources within the calendaring and scheduling application domain. We realize that some of the use cases presented may include workflow or ideas beyond what is offered by current calendaring and scheduling applications.

This document was created by the USECASE Technical Committee of the Calendaring and Scheduling Consortium. The document presents a recommendation for enhancing inter-operability of resources within the calendaring and scheduling application domain. Minimum interoperability is the basic level of functionality our collective experience tells us is necessary to have a useful system. The thrust of this effort is to enable resource inter-operability such that, when a described event contains resources, the recipient of that event is able to make practical use of the described resources; ideally the recipient should be so enabled regardless of whether the recipient is within the same calendaring domain. The resulting recommendations rely in part upon adoption of standards revisions that are in draft as of this writing.

This document was created by the USECASE Technical Committee of the Calendaring and Scheduling Consortium. This document is a survey of the present state of resource interoperability for a representative sample of calendaring, groupware, and project management applications. \"Interoperability of resources\" within the domains surveyed is a level of functionality that allows the communication of resource information between applications that is humanly useful though not necessarily identical for both systems.

This document, developed by the Freebusy Technical Committee, 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.

This document was created by the CalDAV Technical Committee of the Calendaring and Scheduling Consortium. It presents a list of features in the form of requirements for the scheduling extensions to CalDAV [RFC 4791], that is, the extensions to the Web Distributed Authoring and Versioning (WebDAV) [RFC 2518] protocol to specify a standard way of exchanging and processing scheduling messages based on the iCalendar Transport-Independent Interoperability Protocol (iTIP) [RFC 2446].

This document was created by the Use Case Technical Committee of the Calendaring and Scheduling Consortium and defines the use cases for minimum interoperablity for tasks support (VTODO) for calendaring and scheduling. Minimum interoperability is the basic level of functionality our collective experience tells us is necessary to have a useful system. We realize that in some cases it may be more than is currently offered by 'basic' calendaring and scheduling applications.

This document, prepared by the Mobile Technical Committee, discusses the benefits and value of converting to the iCalendar specification from its early predecessor, vCalendar, still widely in use in the mobile and travel industries. The document draws upon results from the Mobile Calendaring Questionnaires conducted earlier this year by TC Mobile; see Mobile Calendaring Questionnaire V2 Results: CD 0609.

The goal of this questionnaire was to determine how and to what extent Calendaring is being used on mobile devices, with a view to using those results to aid in the development of recommendations on how to address any problem areas. A number of responses were received to the online questionnaire, and a summary and brief conclusion of these results is presented, along with the raw results themselves. Respondents to the questionnaire answered based on the capabilities of their device. The results show an aggregate of these results.

This document contains technical recommendations on implementing a time zone registry and a time zone service. Standardized time zones are needed for improved interoperability to avoid some common problems, and to allow using time zones by reference rather than value.

This document contains information about recurrence implementation issues and recommendations on how to resolve these issues. We first explain what recurrences are, justify the need for recurrences, identify recurrence implementation problems and ambiguities, and then offer some guidelines and recommendations to solve these issues.

This document was created by the Use Case Technical Committee of the Calendaring and Scheduling Consortium. The document defines the use cases for minimum interoperability of calendaring and scheduling. Minimum interoperability is the basic level of functionality our collective experience tells us is necessary to have a useful system. We realize that in some cases it may be more than is currently offered by 'basic' calendaring and scheduling applications.

This document was created by the TIMEZONE Technical Committee of the Calendaring and Scheduling Consortium. It contains information about common time zone implementation issues and recommendations on how to resolve these issues. We first justify the need for time zones, then we identify time zone implementation problems, and then offer some guidelines and recommendations. Take note that the listed recommendations often describe what vendors are currently doing to solve the problems.

This document is one in a series of documents summarizing the results of questionnaires that the Calendaring and Scheduling Consortium has conducted to help better understand the requirements, problems and needs for calendaring and scheduling solutions. It is expected that the results of these questionnaires will be used to help define requirements and recommendations for calendaring and scheduling products. This particular document summarizes the results of the Timezone Technical Committee's questionnaire on Timezone support in iCalendar products. Other questionnaire summary documents will cover different areas of calendaring and scheduling, and will be made available by the Consortium.

This document is one in a series of use case documents that the Calendaring and Scheduling Consortium is developing to help better define the needs of different calendaring and scheduling user groups. As such, this document provides a list of use cases for a calendar access protocol only. Other use case documents will cover different areas of calendaring and scheduling, and will be made available by the Consortium in the usual manner. While this list of use cases was developed to assist in the development of the CalDAV protocol, none of the use cases are specific to CalDAV, that is, this list of use cases should apply to any calendar access protocol. It is expected that this document will be used as a basis to further develop technical requirements for a calendar access protocol such as CalDAV.

The Recurrence Technical Committee of The Calendaring and Scheduling Consortium has collected specific information on how Calendaring and Scheduling implementations have, or have not, implemented the Recurrence Rules of RFCs 2445 and 2446, iCalendar and iTIP. This document is part of the committee's work to compile actual usage information and interoperability issues. The Recurrence Committee recently collected information in the form of a Recurrence Questionnaire, which allowed vendors and other producers and consumers of iCalendar recurrences to list the features of iCalendar that they implemented. The questionnaire also contained space for comments about each line item in the RFCs and also overall issues with recurrences. The Recurrence Technical Committee has since analyzed the results of the questionnaire into this document.