Foreword

This document incorporates by reference the CalConnect Intellectual Property Rights, Appropriate Usage, Trademarks and Disclaimer of Warranty for External (Public) Documents as located at

http://www.calconnect.org/documents/disclaimerpublic.pdf.

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.

1.  Terms and definitions

For the purposes of this document, the following terms and definitions apply.

The definitions below are taken from the “Calendaring and Scheduling Glossary of Terms,” version 1.0, October, 2006, from CalConnect. In accordance with previous comments, the term ‘task’ has replaced ‘todo’ whereever ‘todo’ was found.

1.1. Alarm

A reminder for an event or a task. Alarms may be used to define a reminder for a pending event or an overdue task.

1.2. Calendar

A collection of events, tasks, journal entries, etc. A calendar could be the content of a person or resource’s agenda; it could also be a collection of data serving a more specialized need. Calendars are the basic storage containers for calendaring information.

[SOURCE: IETF RFC 3283]

1.3. Calendar User (CU)

An entity (often a human) that accesses calendar information.

[SOURCE: IETF RFC 3283]

1.4. Calendaring

An application domain that covers systems that allow the interchange, access and management of calendar data.

1.5. CalConnect

The Calendaring and Scheduling Consortium consisting of vendors and user groups interested in promoting and improving calendaring and scheduling standards and interoperability.

1.6. Component

A piece of calendar data such as an event, a task, or an alarm. Information about components is stored as properties of those components.

[SOURCE: IETF RFC 3283]

1.7. Coordinated Universal Time (UTC)

An atomic realization of Universal Time (UT) or Greenwich Mean Time, the astronomical basis for civil time. Time zones around the world are expressed as positive and negative offsets from UT. UTC differs by an integral number of seconds from International Atomic Time (TAI), as measured by atomic clocks and a fractional number of seconds from UT.

[SOURCE: Wikipedia]

1.8. Counter

A counter-proposal request a participant may send to an event or task organizer to suggest a change to the event or task such as the scheduled date/time, list of participants, etc.

1.9. Daylight Saving Time (DST)

The period of the year in which the local time of a particular time zone is adjusted forward, most commonly by one hour, to account for the additional hours of daylight during summer months.

1.10. Event

A calendar object that usually takes up time on an individual calendar. Events are commonly used to represent meetings, appointments, anniversaries, and day events.

1.11. Free time search

(Bounded) Common free time. This is typically a search generated by an application to show time on a calendar that is available or open.

1.12. Freebusy

A database and/or listing of times when a potential attendee or resource is free or busy. Used when scheduling calendar events.

1.13. iCalendar

The Internet Calendaring and Scheduling Core Object Specification. An IETF standard (RFC 2445) for a text representation of calendar data ( VEVENT, VTODO, VALARM, etc.).

1.14. Instance

When used with recurrences, an instance refers to an item in the set of recurring items.

1.15. Invite

To request the attendance of someone to a calendar event.

1.16. Negotiation

Resource conflict resolution. Negotiation is the process of resolving conflicts either programmatically or via direct communication with the participants and invitees of meetings and events.

1.17. Notification

1.18. Organizer

The originator of a calendar event typically involving more than one attendee.

1.19. Property

A description of some element of an component, such as a start time, title, or location. Properties can have parameters associated with them to modify or add to their meaning.

1.20. Publish

Make known publicly calendar information such as freebusy times.

1.21. Recurring

Happening more than once over a specified interval, such as weekly, monthly, daily, etc. See Repeating (Clause 1.22).

1.22. Repeating

An event that happens more than once. You might want an event to occur on a regular basis. To do this you schedule a repeating event. Any changes you make to the event can automatically be made to all occurrences of the event. If necessary, changes can be made to individual events without affecting the others. For example, if you need to attend a weekly meeting, you can schedule a repeating event on your calendar. Using another example, if you want to schedule a five day vacation, schedule an all-day event that repeats daily for a total of five times. If you have to cancel one of the days, delete the one day without deleting the whole event.

1.23. Reminders

See Notification (Clause 1.17).

1.24. Task

A calendar object that is commonly used to represent work items.

1.25. Text/calendar

The MIME content type for encoding iCalendar objects. Example usage includes: email, web pages.

1.26. Time zone

Areas of the Earth that have adopted the same local time. Time zones are generally centered on meridians of a longitude, that is a multiple of $15°$, thus making neighboring time zones one hour apart. However, the one hour separation is not universal and the shapes of time zones can be quite irregular because they usually follow the boundaries of states, countries or other administrative areas. Time zones are calendar components that define the time of an event relative to UTC (see below).

1.27. To-do

See Task (Clause 1.24).

2.  Properties Used

We’re using the following properties of a Task in this draft (iCalendar VTODO specification property name is in square brackets []):

In the examples below, the Task property (as listed above) are indicated in square brackets []:

3.  Use Cases

Bibliography

[1]  IETF RFC 2445, F. DAWSON and D. STENERSON. Internet Calendaring and Scheduling Core Object Specification (iCalendar). 1998. RFC Publisher. https://www.rfc-editor.org/info/rfc2445.

[2]  IETF RFC 3283, B. MAHONEY, G. BABICS and A. TALER. Guide to Internet Calendaring. 2002. RFC Publisher. https://www.rfc-editor.org/info/rfc3283.

[3]  CC/R 0610:2006, Calendaring and Scheduling Glossary of Terms V1.0 (Obsoleted by CD1102) (CD 0610). https://standards.calconnect.org/pubdocs/CD0610%20Calendaring%20and%20Scheduling%20Glossary%20of%20Terms%20V1.0.pdf.

[4]  Wikipedia, https://www.wikipedia.org/