The following work products are sets of use cases and requirements targeted at specifications to aid in the further development of those specifications and product implementations based upon them.
Use Cases for Resources (June 10, 2009).
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.
A Recommendation for Minimum Interoperability of Resource Information (June 10, 2009).
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.
CalDAV Scheduling Requirements (July 11, 2007).
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].
Min-IOP (Minimum Interoperable Subset) Use Cases for Tasks (VTODO) (April 19, 2007)
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.
Min-IOP (Minimum Interoperable Subset) Use Cases (January 24, 2006)
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.
CalDAV Use Cases (September 26, 2005):
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.