draft-ietf-calsify-rfc2445bis-03.txt   draft-ietf-calsify-rfc2445bis-04.txt 
Network Working Group B. Desruisseaux, Ed. Network Working Group B. Desruisseaux, Ed.
Internet-Draft Oracle Internet-Draft Oracle
Obsoletes: 2445 (if approved) October 23, 2006 Obsoletes: 2445 (if approved) January 17, 2007
Expires: April 26, 2007 Intended status: Standards Track
Expires: July 21, 2007
Internet Calendaring and Scheduling Core Object Specification Internet Calendaring and Scheduling Core Object Specification
(iCalendar) (iCalendar)
draft-ietf-calsify-rfc2445bis-03 draft-ietf-calsify-rfc2445bis-04
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 1, line 35 skipping to change at page 1, line 36
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on April 26, 2007. This Internet-Draft will expire on July 21, 2007.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2006). Copyright (C) The Internet Society (2007).
Abstract Abstract
There is a clear need to provide and deploy interoperable calendaring This document defines a MIME media type for representing and
and scheduling services for the Internet. Current group scheduling exchanging calendaring and scheduling information such as events, to-
and Personal Information Management (PIM) products are being extended dos, journal entries and free/busy information. The definition of
for use across the Internet, today, in proprietary ways. This memo the text/calendar media type, known as iCalendar, is independent of
has been defined to provide the definition of a common format for any particular calendar service or protocol.
openly exchanging calendaring and scheduling information across the
Internet.
This memo is formatted as a registration for a MIME media type .
However, the format in this memo is equally applicable for use
outside of a MIME message content type.
The proposed media type value is 'text/calendar'. This string would
label a media type containing calendaring and scheduling information
encoded as text characters formatted in a manner outlined below.
This MIME media type provides a standard content type for capturing
calendar event, to-do and journal entry information. It also can be
used to convey free/busy time information. The content type is
suitable as a MIME message entity that can be transferred over MIME
based email systems, using HTTP or some other Internet transport. In
addition, the content type is useful as an object for interactions
between desktop applications using the operating system clipboard,
drag/drop or file systems capabilities.
This memo is based on the earlier work of the vCalendar specification
for the exchange of personal calendaring and scheduling information.
In order to avoid confusion with this referenced work, this memo is
to be known as the iCalendar specification.
This memo defines the format for specifying iCalendar object methods.
An iCalendar object method is a set of usage constraints for the
iCalendar object. For example, these methods might define scheduling
messages that request an event be scheduled, reply to an event
request, send a cancellation notice for an event, modify or replace
the definition of an event, provide a counter proposal for an
original event request, delegate an event request to another
individual, request free or busy time, reply to a free or busy time
request, or provide similar scheduling messages for a to-do or
journal entry calendar component. The iCalendar Transport-indendent
Interoperability Protocol (iTIP) is one such scheduling protocol.
Editorial Note (To be removed by RFC Editor before publication) Editorial Note (To be removed by RFC Editor before publication)
This document is a product of the Calendaring and Scheduling This document is a product of the Calendaring and Scheduling
Standards Simplification (Calsify) working group of the Internet Standards Simplification (Calsify) working group of the Internet
Engineering Task Force. Comments on this draft are welcomed, and Engineering Task Force. Comments on this draft are welcomed, and
should be addressed to the ietf-calsify@osafoundation.org [1] mailing should be addressed to the ietf-calsify@osafoundation.org [1] mailing
list. The issues raised on this mailing list are being tracked at list. The issues raised on this mailing list are being tracked at
the following web site: the following web site:
http://www.ofcourseimright.com/cgi-bin/roundup/calsify. http://www.ofcourseimright.com/cgi-bin/roundup/calsify.
skipping to change at page 3, line 15 skipping to change at page 2, line 25
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 6 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 6
2. Basic Grammar and Conventions . . . . . . . . . . . . . . . . 6 2. Basic Grammar and Conventions . . . . . . . . . . . . . . . . 6
2.1. Formatting Conventions . . . . . . . . . . . . . . . . . 7 2.1. Formatting Conventions . . . . . . . . . . . . . . . . . 7
2.2. Related Memos . . . . . . . . . . . . . . . . . . . . . . 8 2.2. Related Memos . . . . . . . . . . . . . . . . . . . . . . 8
2.3. International Considerations . . . . . . . . . . . . . . 8 2.3. International Considerations . . . . . . . . . . . . . . 8
3. iCalendar Object Specification . . . . . . . . . . . . . . . 9 3. iCalendar Object Specification . . . . . . . . . . . . . . . 9
3.1. Content Lines . . . . . . . . . . . . . . . . . . . . . . 9 3.1. Content Lines . . . . . . . . . . . . . . . . . . . . . . 9
3.1.1. List and Field Separators . . . . . . . . . . . . . . 12 3.1.1. List and Field Separators . . . . . . . . . . . . . . 12
3.1.2. Multiple Values . . . . . . . . . . . . . . . . . . . 12 3.1.2. Multiple Values . . . . . . . . . . . . . . . . . . . 13
3.1.3. Binary Content . . . . . . . . . . . . . . . . . . . 12 3.1.3. Binary Content . . . . . . . . . . . . . . . . . . . 13
3.1.4. Character Set . . . . . . . . . . . . . . . . . . . . 13 3.1.4. Character Set . . . . . . . . . . . . . . . . . . . . 14
3.2. Property Parameters . . . . . . . . . . . . . . . . . . . 13 3.2. Property Parameters . . . . . . . . . . . . . . . . . . . 14
3.2.1. Alternate Text Representation . . . . . . . . . . . . 14 3.2.1. Alternate Text Representation . . . . . . . . . . . . 15
3.2.2. Common Name . . . . . . . . . . . . . . . . . . . . . 15 3.2.2. Common Name . . . . . . . . . . . . . . . . . . . . . 16
3.2.3. Calendar User Type . . . . . . . . . . . . . . . . . 16 3.2.3. Calendar User Type . . . . . . . . . . . . . . . . . 17
3.2.4. Delegators . . . . . . . . . . . . . . . . . . . . . 17 3.2.4. Delegators . . . . . . . . . . . . . . . . . . . . . 17
3.2.5. Delegatees . . . . . . . . . . . . . . . . . . . . . 17 3.2.5. Delegatees . . . . . . . . . . . . . . . . . . . . . 18
3.2.6. Directory Entry Reference . . . . . . . . . . . . . . 18 3.2.6. Directory Entry Reference . . . . . . . . . . . . . . 18
3.2.7. Inline Encoding . . . . . . . . . . . . . . . . . . . 18 3.2.7. Inline Encoding . . . . . . . . . . . . . . . . . . . 19
3.2.8. Format Type . . . . . . . . . . . . . . . . . . . . . 19 3.2.8. Format Type . . . . . . . . . . . . . . . . . . . . . 20
3.2.9. Free/Busy Time Type . . . . . . . . . . . . . . . . . 20 3.2.9. Free/Busy Time Type . . . . . . . . . . . . . . . . . 20
3.2.10. Language . . . . . . . . . . . . . . . . . . . . . . 21 3.2.10. Language . . . . . . . . . . . . . . . . . . . . . . 21
3.2.11. Group or List Membership . . . . . . . . . . . . . . 21 3.2.11. Group or List Membership . . . . . . . . . . . . . . 22
3.2.12. Participation Status . . . . . . . . . . . . . . . . 22 3.2.12. Participation Status . . . . . . . . . . . . . . . . 23
3.2.13. Recurrence Identifier Range . . . . . . . . . . . . . 24 3.2.13. Alarm Trigger Relationship . . . . . . . . . . . . . 25
3.2.14. Alarm Trigger Relationship . . . . . . . . . . . . . 24 3.2.14. Relationship Type . . . . . . . . . . . . . . . . . . 25
3.2.15. Relationship Type . . . . . . . . . . . . . . . . . . 25 3.2.15. Participation Role . . . . . . . . . . . . . . . . . 26
3.2.16. Participation Role . . . . . . . . . . . . . . . . . 26 3.2.16. RSVP Expectation . . . . . . . . . . . . . . . . . . 27
3.2.17. RSVP Expectation . . . . . . . . . . . . . . . . . . 26 3.2.17. Sent By . . . . . . . . . . . . . . . . . . . . . . . 27
3.2.18. Sent By . . . . . . . . . . . . . . . . . . . . . . . 27 3.2.18. Time Zone Identifier . . . . . . . . . . . . . . . . 28
3.2.19. Time Zone Identifier . . . . . . . . . . . . . . . . 28 3.2.19. Value Data Types . . . . . . . . . . . . . . . . . . 29
3.2.20. Value Data Types . . . . . . . . . . . . . . . . . . 29
3.3. Property Value Data Types . . . . . . . . . . . . . . . . 30 3.3. Property Value Data Types . . . . . . . . . . . . . . . . 30
3.3.1. Binary . . . . . . . . . . . . . . . . . . . . . . . 30 3.3.1. Binary . . . . . . . . . . . . . . . . . . . . . . . 30
3.3.2. Boolean . . . . . . . . . . . . . . . . . . . . . . . 31 3.3.2. Boolean . . . . . . . . . . . . . . . . . . . . . . . 31
3.3.3. Calendar User Address . . . . . . . . . . . . . . . . 31 3.3.3. Calendar User Address . . . . . . . . . . . . . . . . 32
3.3.4. Date . . . . . . . . . . . . . . . . . . . . . . . . 32 3.3.4. Date . . . . . . . . . . . . . . . . . . . . . . . . 32
3.3.5. Date-Time . . . . . . . . . . . . . . . . . . . . . . 32 3.3.5. Date-Time . . . . . . . . . . . . . . . . . . . . . . 33
3.3.6. Duration . . . . . . . . . . . . . . . . . . . . . . 35 3.3.6. Duration . . . . . . . . . . . . . . . . . . . . . . 35
3.3.7. Float . . . . . . . . . . . . . . . . . . . . . . . . 35 3.3.7. Float . . . . . . . . . . . . . . . . . . . . . . . . 36
3.3.8. Integer . . . . . . . . . . . . . . . . . . . . . . . 36 3.3.8. Integer . . . . . . . . . . . . . . . . . . . . . . . 36
3.3.9. Period of Time . . . . . . . . . . . . . . . . . . . 36 3.3.9. Period of Time . . . . . . . . . . . . . . . . . . . 37
3.3.10. Recurrence Rule . . . . . . . . . . . . . . . . . . . 38 3.3.10. Recurrence Rule . . . . . . . . . . . . . . . . . . . 38
3.3.11. Text . . . . . . . . . . . . . . . . . . . . . . . . 43 3.3.11. Text . . . . . . . . . . . . . . . . . . . . . . . . 44
3.3.12. Time . . . . . . . . . . . . . . . . . . . . . . . . 45 3.3.12. Time . . . . . . . . . . . . . . . . . . . . . . . . 45
3.3.13. URI . . . . . . . . . . . . . . . . . . . . . . . . . 47 3.3.13. URI . . . . . . . . . . . . . . . . . . . . . . . . . 48
3.3.14. UTC Offset . . . . . . . . . . . . . . . . . . . . . 48 3.3.14. UTC Offset . . . . . . . . . . . . . . . . . . . . . 48
3.4. iCalendar Object . . . . . . . . . . . . . . . . . . . . 48 3.4. iCalendar Object . . . . . . . . . . . . . . . . . . . . 49
3.5. Property . . . . . . . . . . . . . . . . . . . . . . . . 49 3.5. Property . . . . . . . . . . . . . . . . . . . . . . . . 50
3.6. Calendar Components . . . . . . . . . . . . . . . . . . . 49 3.6. Calendar Components . . . . . . . . . . . . . . . . . . . 50
3.6.1. Event Component . . . . . . . . . . . . . . . . . . . 50 3.6.1. Event Component . . . . . . . . . . . . . . . . . . . 51
3.6.2. To-do Component . . . . . . . . . . . . . . . . . . . 53 3.6.2. To-do Component . . . . . . . . . . . . . . . . . . . 54
3.6.3. Journal Component . . . . . . . . . . . . . . . . . . 55 3.6.3. Journal Component . . . . . . . . . . . . . . . . . . 56
3.6.4. Free/Busy Component . . . . . . . . . . . . . . . . . 57 3.6.4. Free/Busy Component . . . . . . . . . . . . . . . . . 58
3.6.5. Time Zone Component . . . . . . . . . . . . . . . . . 60 3.6.5. Time Zone Component . . . . . . . . . . . . . . . . . 61
3.6.6. Alarm Component . . . . . . . . . . . . . . . . . . . 68 3.6.6. Alarm Component . . . . . . . . . . . . . . . . . . . 69
3.7. Calendar Properties . . . . . . . . . . . . . . . . . . . 74 3.7. Calendar Properties . . . . . . . . . . . . . . . . . . . 75
3.7.1. Calendar Scale . . . . . . . . . . . . . . . . . . . 74 3.7.1. Calendar Scale . . . . . . . . . . . . . . . . . . . 75
3.7.2. Method . . . . . . . . . . . . . . . . . . . . . . . 75 3.7.2. Method . . . . . . . . . . . . . . . . . . . . . . . 76
3.7.3. Product Identifier . . . . . . . . . . . . . . . . . 76 3.7.3. Product Identifier . . . . . . . . . . . . . . . . . 77
3.7.4. Version . . . . . . . . . . . . . . . . . . . . . . . 77 3.7.4. Version . . . . . . . . . . . . . . . . . . . . . . . 78
3.8. Component Properties . . . . . . . . . . . . . . . . . . 78 3.8. Component Properties . . . . . . . . . . . . . . . . . . 79
3.8.1. Descriptive Component Properties . . . . . . . . . . 78 3.8.1. Descriptive Component Properties . . . . . . . . . . 79
3.8.1.1. Attachment . . . . . . . . . . . . . . . . . . . 78 3.8.1.1. Attachment . . . . . . . . . . . . . . . . . . . 79
3.8.1.2. Categories . . . . . . . . . . . . . . . . . . . 79 3.8.1.2. Categories . . . . . . . . . . . . . . . . . . . 80
3.8.1.3. Classification . . . . . . . . . . . . . . . . . 80 3.8.1.3. Classification . . . . . . . . . . . . . . . . . 81
3.8.1.4. Comment . . . . . . . . . . . . . . . . . . . . . 81 3.8.1.4. Comment . . . . . . . . . . . . . . . . . . . . . 82
3.8.1.5. Description . . . . . . . . . . . . . . . . . . . 82 3.8.1.5. Description . . . . . . . . . . . . . . . . . . . 83
3.8.1.6. Geographic Position . . . . . . . . . . . . . . . 83 3.8.1.6. Geographic Position . . . . . . . . . . . . . . . 84
3.8.1.7. Location . . . . . . . . . . . . . . . . . . . . 85 3.8.1.7. Location . . . . . . . . . . . . . . . . . . . . 86
3.8.1.8. Percent Complete . . . . . . . . . . . . . . . . 86 3.8.1.8. Percent Complete . . . . . . . . . . . . . . . . 87
3.8.1.9. Priority . . . . . . . . . . . . . . . . . . . . 87 3.8.1.9. Priority . . . . . . . . . . . . . . . . . . . . 88
3.8.1.10. Resources . . . . . . . . . . . . . . . . . . . . 89 3.8.1.10. Resources . . . . . . . . . . . . . . . . . . . . 90
3.8.1.11. Status . . . . . . . . . . . . . . . . . . . . . 89 3.8.1.11. Status . . . . . . . . . . . . . . . . . . . . . 91
3.8.1.12. Summary . . . . . . . . . . . . . . . . . . . . . 91 3.8.1.12. Summary . . . . . . . . . . . . . . . . . . . . . 92
3.8.2. Date and Time Component Properties . . . . . . . . . 92 3.8.2. Date and Time Component Properties . . . . . . . . . 93
3.8.2.1. Date/Time Completed . . . . . . . . . . . . . . . 92 3.8.2.1. Date/Time Completed . . . . . . . . . . . . . . . 93
3.8.2.2. Date/Time End . . . . . . . . . . . . . . . . . . 93 3.8.2.2. Date/Time End . . . . . . . . . . . . . . . . . . 94
3.8.2.3. Date/Time Due . . . . . . . . . . . . . . . . . . 94 3.8.2.3. Date/Time Due . . . . . . . . . . . . . . . . . . 95
3.8.2.4. Date/Time Start . . . . . . . . . . . . . . . . . 95 3.8.2.4. Date/Time Start . . . . . . . . . . . . . . . . . 96
3.8.2.5. Duration . . . . . . . . . . . . . . . . . . . . 96 3.8.2.5. Duration . . . . . . . . . . . . . . . . . . . . 97
3.8.2.6. Free/Busy Time . . . . . . . . . . . . . . . . . 97 3.8.2.6. Free/Busy Time . . . . . . . . . . . . . . . . . 98
3.8.2.7. Time Transparency . . . . . . . . . . . . . . . . 98 3.8.2.7. Time Transparency . . . . . . . . . . . . . . . . 100
3.8.3. Time Zone Component Properties . . . . . . . . . . . 99 3.8.3. Time Zone Component Properties . . . . . . . . . . . 101
3.8.3.1. Time Zone Identifier . . . . . . . . . . . . . . 100 3.8.3.1. Time Zone Identifier . . . . . . . . . . . . . . 101
3.8.3.2. Time Zone Name . . . . . . . . . . . . . . . . . 101 3.8.3.2. Time Zone Name . . . . . . . . . . . . . . . . . 102
3.8.3.3. Time Zone Offset From . . . . . . . . . . . . . . 102 3.8.3.3. Time Zone Offset From . . . . . . . . . . . . . . 103
3.8.3.4. Time Zone Offset To . . . . . . . . . . . . . . . 103 3.8.3.4. Time Zone Offset To . . . . . . . . . . . . . . . 104
3.8.3.5. Time Zone URL . . . . . . . . . . . . . . . . . . 103 3.8.3.5. Time Zone URL . . . . . . . . . . . . . . . . . . 105
3.8.4. Relationship Component Properties . . . . . . . . . . 104 3.8.4. Relationship Component Properties . . . . . . . . . . 105
3.8.4.1. Attendee . . . . . . . . . . . . . . . . . . . . 104 3.8.4.1. Attendee . . . . . . . . . . . . . . . . . . . . 106
3.8.4.2. Contact . . . . . . . . . . . . . . . . . . . . . 107 3.8.4.2. Contact . . . . . . . . . . . . . . . . . . . . . 108
3.8.4.3. Organizer . . . . . . . . . . . . . . . . . . . . 108 3.8.4.3. Organizer . . . . . . . . . . . . . . . . . . . . 110
3.8.4.4. Recurrence ID . . . . . . . . . . . . . . . . . . 110 3.8.4.4. Recurrence ID . . . . . . . . . . . . . . . . . . 111
3.8.4.5. Related To . . . . . . . . . . . . . . . . . . . 112 3.8.4.5. Related To . . . . . . . . . . . . . . . . . . . 113
3.8.4.6. Uniform Resource Locator . . . . . . . . . . . . 114 3.8.4.6. Uniform Resource Locator . . . . . . . . . . . . 115
3.8.4.7. Unique Identifier . . . . . . . . . . . . . . . . 114 3.8.4.7. Unique Identifier . . . . . . . . . . . . . . . . 115
3.8.5. Recurrence Component Properties . . . . . . . . . . . 116 3.8.5. Recurrence Component Properties . . . . . . . . . . . 117
3.8.5.1. Exception Date/Times . . . . . . . . . . . . . . 116 3.8.5.1. Exception Date/Times . . . . . . . . . . . . . . 117
3.8.5.2. Recurrence Date/Times . . . . . . . . . . . . . . 117 3.8.5.2. Recurrence Date/Times . . . . . . . . . . . . . . 119
3.8.5.3. Recurrence Rule . . . . . . . . . . . . . . . . . 119 3.8.5.3. Recurrence Rule . . . . . . . . . . . . . . . . . 120
3.8.6. Alarm Component Properties . . . . . . . . . . . . . 128 3.8.6. Alarm Component Properties . . . . . . . . . . . . . 130
3.8.6.1. Action . . . . . . . . . . . . . . . . . . . . . 129 3.8.6.1. Action . . . . . . . . . . . . . . . . . . . . . 130
3.8.6.2. Repeat Count . . . . . . . . . . . . . . . . . . 129 3.8.6.2. Repeat Count . . . . . . . . . . . . . . . . . . 131
3.8.6.3. Trigger . . . . . . . . . . . . . . . . . . . . . 130 3.8.6.3. Trigger . . . . . . . . . . . . . . . . . . . . . 132
3.8.7. Change Management Component Properties . . . . . . . 132 3.8.7. Change Management Component Properties . . . . . . . 134
3.8.7.1. Date/Time Created . . . . . . . . . . . . . . . . 133 3.8.7.1. Date/Time Created . . . . . . . . . . . . . . . . 135
3.8.7.2. Date/Time Stamp . . . . . . . . . . . . . . . . . 133 3.8.7.2. Date/Time Stamp . . . . . . . . . . . . . . . . . 135
3.8.7.3. Last Modified . . . . . . . . . . . . . . . . . . 134 3.8.7.3. Last Modified . . . . . . . . . . . . . . . . . . 136
3.8.7.4. Sequence Number . . . . . . . . . . . . . . . . . 135 3.8.7.4. Sequence Number . . . . . . . . . . . . . . . . . 137
3.8.8. Miscellaneous Component Properties . . . . . . . . . 136 3.8.8. Miscellaneous Component Properties . . . . . . . . . 139
3.8.8.1. Non-standard Properties . . . . . . . . . . . . . 137 3.8.8.1. Non-standard Properties . . . . . . . . . . . . . 139
3.8.8.2. Request Status . . . . . . . . . . . . . . . . . 138 3.8.8.2. Request Status . . . . . . . . . . . . . . . . . 140
4. iCalendar Object Examples . . . . . . . . . . . . . . . . . . 141 4. iCalendar Object Examples . . . . . . . . . . . . . . . . . . 143
5. Recommended Practices . . . . . . . . . . . . . . . . . . . . 145 5. Recommended Practices . . . . . . . . . . . . . . . . . . . . 147
6. Registration of Content Type Elements . . . . . . . . . . . . 146 6. Registration of Content Type Elements . . . . . . . . . . . . 148
6.1. Registration of New and Modified iCalendar Object 6.1. Registration of New and Modified iCalendar Object
Methods . . . . . . . . . . . . . . . . . . . . . . . . . 146 Methods . . . . . . . . . . . . . . . . . . . . . . . . . 148
6.2. Registration of New Properties . . . . . . . . . . . . . 147 6.2. Registration of New Properties . . . . . . . . . . . . . 149
6.2.1. Define the property . . . . . . . . . . . . . . . . . 147 6.2.1. Define the property . . . . . . . . . . . . . . . . . 149
6.2.2. Post the Property definition . . . . . . . . . . . . 148 6.2.2. Post the Property definition . . . . . . . . . . . . 150
6.2.3. Allow a comment period . . . . . . . . . . . . . . . 148 6.2.3. Allow a comment period . . . . . . . . . . . . . . . 150
6.2.4. Submit the property for approval . . . . . . . . . . 148 6.2.4. Submit the property for approval . . . . . . . . . . 150
6.3. Property Change Control . . . . . . . . . . . . . . . . . 149 6.3. Property Change Control . . . . . . . . . . . . . . . . . 151
7. Internationalization Considerations . . . . . . . . . . . . . 149 7. Internationalization Considerations . . . . . . . . . . . . . 151
8. Security Considerations . . . . . . . . . . . . . . . . . . . 149 8. Security Considerations . . . . . . . . . . . . . . . . . . . 151
9. IANA Consideration . . . . . . . . . . . . . . . . . . . . . 150 9. IANA Consideration . . . . . . . . . . . . . . . . . . . . . 152
9.1. Media Type Registration Information . . . . . . . . . . . 150 9.1. Media Type Registration Information . . . . . . . . . . . 152
10. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 153 10. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 155
11. References . . . . . . . . . . . . . . . . . . . . . . . . . 154 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 156
11.1. Normative References . . . . . . . . . . . . . . . . . . 154 11.1. Normative References . . . . . . . . . . . . . . . . . . 156
11.2. Informative References . . . . . . . . . . . . . . . . . 155 11.2. Informative References . . . . . . . . . . . . . . . . . 157
Appendix A. Differences from RFC 2445 . . . . . . . . . . . . . 155 Appendix A. Differences from RFC 2445 . . . . . . . . . . . . . 157
A.1. New restrictions . . . . . . . . . . . . . . . . . . . . 155 A.1. New restrictions . . . . . . . . . . . . . . . . . . . . 158
A.2. Deprecated features . . . . . . . . . . . . . . . . . . . 156 A.2. Deprecated features . . . . . . . . . . . . . . . . . . . 158
Appendix B. Change Log (to be removed by RFC Editor before Appendix B. Change Log (to be removed by RFC Editor before
publication) . . . . . . . . . . . . . . . . . . . . 156 publication) . . . . . . . . . . . . . . . . . . . . 158
B.1. Changes in -03 . . . . . . . . . . . . . . . . . . . . . 156 B.1. Changes in -04 . . . . . . . . . . . . . . . . . . . . . 158
B.2. Changes in -02 . . . . . . . . . . . . . . . . . . . . . 156 B.2. Changes in -03 . . . . . . . . . . . . . . . . . . . . . 159
B.3. Changes in -01 . . . . . . . . . . . . . . . . . . . . . 157 B.3. Changes in -02 . . . . . . . . . . . . . . . . . . . . . 160
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 158 B.4. Changes in -01 . . . . . . . . . . . . . . . . . . . . . 161
Intellectual Property and Copyright Statements . . . . . . . . . 159 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 161
Intellectual Property and Copyright Statements . . . . . . . . . 162
1. Introduction 1. Introduction
The use of calendaring and scheduling has grown considerably in the The use of calendaring and scheduling has grown considerably in the
last decade. Enterprise and inter-enterprise business has become last decade. Enterprise and inter-enterprise business has become
dependent on rapid scheduling of events and actions using this dependent on rapid scheduling of events and actions using this
information technology. However, the longer term growth of information technology. However, the longer term growth of
calendaring and scheduling, is currently limited by the lack of calendaring and scheduling is currently limited by the lack of
Internet standards for the message content types that are central to Internet standards for the message content types that are central to
these knowledgeware applications. This memo is intended to progress these knowledgeware applications. This memo is intended to progress
the level of interoperability possible between dissimilar calendaring the level of interoperability possible between dissimilar calendaring
and scheduling applications. This memo defines a MIME content type and scheduling applications. This memo defines a MIME content type
for exchanging electronic calendaring and scheduling information. for exchanging electronic calendaring and scheduling information.
The Internet Calendaring and Scheduling Core Object Specification, or The Internet Calendaring and Scheduling Core Object Specification, or
iCalendar, allows for the capture and exchange of information iCalendar, allows for the capture and exchange of information
normally stored within a calendaring and scheduling application; such normally stored within a calendaring and scheduling application; such
as a Personal Information Manager (PIM) or a Group Scheduling as a Personal Information Manager (PIM) or a Group Scheduling
product. product.
skipping to change at page 7, line 11 skipping to change at page 7, line 11
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY" and "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY" and
"OPTIONAL" in this document are to be interpreted as described in "OPTIONAL" in this document are to be interpreted as described in
[RFC2119]. [RFC2119].
This memo makes use of both a descriptive prose and a more formal This memo makes use of both a descriptive prose and a more formal
notation for defining the calendaring and scheduling format. notation for defining the calendaring and scheduling format.
The notation used in this memo is the ABNF notation of [RFC4234] . The notation used in this memo is the ABNF notation of [RFC4234] .
Readers intending on implementing this format defined in this memo Readers intending on implementing the format defined in this memo
should be familiar with this notation in order to properly interpret should be familiar with this notation in order to properly interpret
the specifications of this memo. the specifications of this memo.
All numeric values used in this memo are given in decimal notation. All numeric values used in this memo are given in decimal notation.
All names of properties, property parameters, enumerated property All names of properties, property parameters, enumerated property
values and property parameter values are case-insensitive. However, values and property parameter values are case-insensitive. However,
all other property values are case-sensitive, unless otherwise all other property values are case-sensitive, unless otherwise
stated. stated.
Note: All indented editorial notes, such as this one, are intended Note: All indented editorial notes, such as this one, are intended
to provide the reader with additional information. The to provide the reader with additional information. The
information is not essential to the building of an implementation information is not essential to the building of an implementation
conformant with this memo. The information is provided to conformant with this memo. The information is provided to
highlight a particular feature or characteristic of the memo. highlight a particular feature or characteristic of the memo.
The format for the iCalendar object is based on the syntax of the The format for the iCalendar object is based on the syntax of the
[RFC2425] content type. While the iCalendar object is not a profile text/directory media type [RFC2425]. While the iCalendar object is
of the [RFC2425] content type, it does reuse a number of the elements not a profile of the text/directory media type [RFC2425], it does
from the [RFC2425] specification. reuse a number of the elements from the [RFC2425] specification.
2.1. Formatting Conventions 2.1. Formatting Conventions
The mechanisms defined in this memo are defined in prose. Many of The mechanisms defined in this memo are defined in prose. Many of
the terms used to describe these have common usage that is different the terms used to describe these have common usage that is different
than the standards usage of this memo. In order to reference within than the standards usage of this memo. In order to reference within
this memo elements of the calendaring and scheduling model, core this memo elements of the calendaring and scheduling model, core
object (this memo) or interoperability protocol [I-D.ietf-calsify- object (this memo) or interoperability protocol
2446bis] some formatting conventions have been used. Calendaring and [I-D.ietf-calsify-2446bis] some formatting conventions have been
scheduling roles are referred to in quoted-strings of text with the used. Calendaring and scheduling roles are referred to in quoted-
first character of each word in upper case. For example, "Organizer" strings of text with the first character of each word in upper case.
refers to a role of a "Calendar User" within the scheduling protocol For example, "Organizer" refers to a role of a "Calendar User" within
defined by [I-D.ietf-calsify-2446bis]. Calendar components defined the scheduling protocol defined by [I-D.ietf-calsify-2446bis].
by this memo are referred to with capitalized, quoted-strings of Calendar components defined by this memo are referred to with
text. All calendar components start with the letter "V". For capitalized, quoted-strings of text. All calendar components start
example, "VEVENT" refers to the event calendar component, "VTODO" with the letter "V". For example, "VEVENT" refers to the event
refers to the to-do calendar component and "VJOURNAL" refers to the calendar component, "VTODO" refers to the to-do calendar component
daily journal calendar component. Scheduling methods defined by iTIP and "VJOURNAL" refers to the daily journal calendar component.
[I-D.ietf-calsify-2446bis] are referred to with capitalized, quoted- Scheduling methods defined by iTIP [I-D.ietf-calsify-2446bis] are
strings of text. For example, "REQUEST" refers to the method for referred to with capitalized, quoted-strings of text. For example,
requesting a scheduling calendar component be created or modified, "REQUEST" refers to the method for requesting a scheduling calendar
"REPLY" refers to the method a recipient of a request uses to update component be created or modified, "REPLY" refers to the method a
their status with the "Organizer" of the calendar component. recipient of a request uses to update their status with the
"Organizer" of the calendar component.
The properties defined by this memo are referred to with capitalized, The properties defined by this memo are referred to with capitalized,
quoted-strings of text, followed by the word "property". For quoted-strings of text, followed by the word "property". For
example, "ATTENDEE" property refers to the iCalendar property used to example, "ATTENDEE" property refers to the iCalendar property used to
convey the calendar address of a calendar user. Property parameters convey the calendar address of a calendar user. Property parameters
defined by this memo are referred to with lowercase, quoted-strings defined by this memo are referred to with lowercase, quoted-strings
of text, followed by the word "parameter". For example, "value" of text, followed by the word "parameter". For example, "value"
parameter refers to the iCalendar property parameter used to override parameter refers to the iCalendar property parameter used to override
the default data type for a property value. Enumerated values the default value type for a property value. Enumerated values
defined by this memo are referred to with capitalized text, either defined by this memo are referred to with capitalized text, either
alone or followed by the word "value". For example, the "MINUTELY" alone or followed by the word "value". For example, the "MINUTELY"
value can be used with the "FREQ" component of the "RECUR" data type value can be used with the "FREQ" component of the "RECUR" value type
to specify repeating components based on an interval of one minute or to specify repeating components based on an interval of one minute or
more. more.
2.2. Related Memos 2.2. Related Memos
Implementers will need to be familiar with several other memos that, Implementers will need to be familiar with several other memos that,
along with this memo, form a framework for Internet calendaring and along with this memo, form a framework for Internet calendaring and
scheduling standards. This memo specifies a core specification of scheduling standards. This memo specifies a core specification of
objects, data types, properties and property parameters. objects, value types, properties and property parameters.
o iTIP [I-D.ietf-calsify-2446bis] specifies an interoperability o iTIP [I-D.ietf-calsify-2446bis] specifies an interoperability
protocol for scheduling between different implementations; protocol for scheduling between different implementations;
o iMIP [I-D.ietf-calsify-rfc2447bis] specifies an Internet email o iMIP [I-D.ietf-calsify-rfc2447bis] specifies an Internet email
binding for [I-D.ietf-calsify-2446bis]. binding for [I-D.ietf-calsify-2446bis].
This memo does not attempt to repeat the specification of concepts or This memo does not attempt to repeat the specification of concepts or
definitions from these other memos. Where possible, references are definitions from these other memos. Where possible, references are
made to the memo that provides for the specification of these made to the memo that provides for the specification of these
skipping to change at page 10, line 24 skipping to change at page 10, line 24
; This ABNF is just a general definition for an initial parsing ; This ABNF is just a general definition for an initial parsing
; of the content line into its property name, parameter list, ; of the content line into its property name, parameter list,
; and value string ; and value string
; When parsing a content line, folded lines MUST first ; When parsing a content line, folded lines MUST first
; be unfolded according to the unfolding procedure ; be unfolded according to the unfolding procedure
; described above. When generating a content line, lines ; described above. When generating a content line, lines
; longer than 75 octets SHOULD be folded according to ; longer than 75 octets SHOULD be folded according to
; the folding procedure described above. ; the folding procedure described above.
name = x-name / iana-token name = iana-token / x-name
iana-token = 1*(ALPHA / DIGIT / "-") iana-token = 1*(ALPHA / DIGIT / "-")
; iCalendar identifier registered with IANA ; iCalendar identifier registered with IANA
x-name = "X-" [vendorid "-"] 1*(ALPHA / DIGIT / "-") x-name = "X-" [vendorid "-"] 1*(ALPHA / DIGIT / "-")
; Reserved for experimental use. ; Reserved for experimental use.
vendorid = 3*(ALPHA / DIGIT) ;Vendor identification vendorid = 3*(ALPHA / DIGIT) ;Vendor identification
param = param-name "=" param-value param = param-name "=" param-value
skipping to change at page 11, line 14 skipping to change at page 11, line 14
QSAFE-CHAR = WSP / %x21 / %x23-7E / NON-US-ASCII QSAFE-CHAR = WSP / %x21 / %x23-7E / NON-US-ASCII
; Any character except CTLs and DQUOTE ; Any character except CTLs and DQUOTE
SAFE-CHAR = WSP / %x21 / %x23-2B / %x2D-39 / %x3C-7E SAFE-CHAR = WSP / %x21 / %x23-2B / %x2D-39 / %x3C-7E
/ NON-US-ASCII / NON-US-ASCII
; Any character except CTLs, DQUOTE, ";", ":", "," ; Any character except CTLs, DQUOTE, ";", ":", ","
VALUE-CHAR = WSP / %x21-7E / NON-US-ASCII VALUE-CHAR = WSP / %x21-7E / NON-US-ASCII
; Any textual character ; Any textual character
NON-US-ASCII = %x80-F8 NON-US-ASCII = UTF8-2 / UTF8-3 / UTF8-4
; Use restricted by charset parameter ; UTF8-2, UTF8-3, and UTF8-4 are defined in
; on outer MIME object (UTF-8 preferred) [RFC3629]
CR = %x0D contentline = name *(";" param ) ":" value CRLF
; carriage return ; This ABNF is just a general definition for an initial parsing
; of the content line into its property name, parameter list,
; and value string
LF = %x0A ; When parsing a content line, folded lines MUST first
; line feed ; be unfolded according to the unfolding procedure
; described above. When generating a content line, lines
; longer than 75 octets SHOULD be folded according to
; the folding procedure described above.
CRLF = CR LF name = iana-token / x-name
; Internet standard newline
CTL = %x00-08 / %x0A-1F / %x7F iana-token = 1*(ALPHA / DIGIT / "-")
; Controls ; iCalendar identifier registered with IANA
ALPHA = %x41-5A / %x61-7A ; A-Z / a-z x-name = "X-" [vendorid "-"] 1*(ALPHA / DIGIT / "-")
; Reserved for experimental use.
DIGIT = %x30-39 vendorid = 3*(ALPHA / DIGIT) ;Vendor identification
; 0-9
DQUOTE = %x22 param = param-name "=" param-value
; Quotation Mark *("," param-value)
; Each property defines the specific ABNF for the parameters
; allowed on the property. Refer to specific properties for
; precise parameter ABNF.
WSP = SPACE / HTAB param-name = iana-token / x-name
SPACE = %x20 param-value = paramtext / quoted-string
HTAB = %x09 paramtext = *SAFE-CHAR
value = *VALUE-CHAR
quoted-string = DQUOTE *QSAFE-CHAR DQUOTE
QSAFE-CHAR = WSP / %x21 / %x23-7E / NON-US-ASCII
; Any character except CTLs and DQUOTE
SAFE-CHAR = WSP / %x21 / %x23-2B / %x2D-39 / %x3C-7E
/ NON-US-ASCII
; Any character except CTLs, DQUOTE, ";", ":", ","
VALUE-CHAR = WSP / %x21-7E / NON-US-ASCII
; Any textual character
NON-US-ASCII = UTF8-2 / UTF8-3 / UTF8-4
; UTF8-2, UTF8-3, and UTF8-4 are defined in
The property value component of a content line has a format that is The property value component of a content line has a format that is
property specific. Refer to the section describing each property for property specific. Refer to the section describing each property for
a definition of this format. a definition of this format.
All names of properties, property parameters, enumerated property All names of properties, property parameters, enumerated property
values and property parameter values are case-insensitive. However, values and property parameter values are case-insensitive. However,
all other property values are case-sensitive, unless otherwise all other property values are case-sensitive, unless otherwise
stated. stated.
skipping to change at page 12, line 22 skipping to change at page 12, line 45
strings are separated by a COMMA character (US-ASCII decimal 44). strings are separated by a COMMA character (US-ASCII decimal 44).
Some property values are defined in terms of multiple parts. These Some property values are defined in terms of multiple parts. These
structured property values MUST have their value parts separated by a structured property values MUST have their value parts separated by a
SEMICOLON character (US-ASCII decimal 59). SEMICOLON character (US-ASCII decimal 59).
Some properties allow a list of parameters. Each property parameter Some properties allow a list of parameters. Each property parameter
in a list of property parameters MUST be separated by a SEMICOLON in a list of property parameters MUST be separated by a SEMICOLON
character (US-ASCII decimal 59). character (US-ASCII decimal 59).
Property parameters with values containing a COLON, a SEMICOLON or a Property parameters with values containing a COLON character (US-
COMMA character MUST be placed in quoted text. ASCII decimal 58) , a SEMICOLON character (US-ASCII decimal 59) or a
COMMA character (US-ASCII decimal 44) MUST be placed in quoted text.
For example, in the following properties a SEMICOLON is used to For example, in the following properties a SEMICOLON is used to
separate property parameters from each other, and a COMMA is used to separate property parameters from each other, and a COMMA is used to
separate property values in a value list. separate property values in a value list.
ATTENDEE;RSVP=TRUE;ROLE=REQ-PARTICIPANT:MAILTO: ATTENDEE;RSVP=TRUE;ROLE=REQ-PARTICIPANT:mailto:
jsmith@example.com jsmith@example.com
RDATE;VALUE=DATE:19970304,19970504,19970704,19970904 RDATE;VALUE=DATE:19970304,19970504,19970704,19970904
3.1.2. Multiple Values 3.1.2. Multiple Values
Some properties defined in the iCalendar object can have multiple Some properties defined in the iCalendar object can have multiple
values. The general rule for encoding multi-valued items is to values. The general rule for encoding multi-valued items is to
simply create a new content line for each value, including the simply create a new content line for each value, including the
property name. However, it should be noted that some properties property name. However, it should be noted that some properties
skipping to change at page 13, line 42 skipping to change at page 14, line 21
The "charset" Content-Type parameter MUST be used in MIME transports The "charset" Content-Type parameter MUST be used in MIME transports
to specify the charset being used . to specify the charset being used .
3.2. Property Parameters 3.2. Property Parameters
A property can have attributes associated with it. These "property A property can have attributes associated with it. These "property
parameters" contain meta-information about the property or the parameters" contain meta-information about the property or the
property value. Property parameters are provided to specify such property value. Property parameters are provided to specify such
information as the location of an alternate text representation for a information as the location of an alternate text representation for a
property value, the language of a text property value, the data type property value, the language of a text property value, the value type
of the property value and other attributes. of the property value and other attributes.
Property parameter values that contain the COLON (US-ASCII decimal Property parameter values that contain the COLON (US-ASCII decimal
58), SEMICOLON (US-ASCII decimal 59) or COMMA (US-ASCII decimal 44) 58), SEMICOLON (US-ASCII decimal 59) or COMMA (US-ASCII decimal 44)
character separators MUST be specified as quoted-string text values. character separators MUST be specified as quoted-string text values.
Property parameter values MUST NOT contain the DQUOTE (US-ASCII Property parameter values MUST NOT contain the DQUOTE (US-ASCII
decimal 22) character. The DQUOTE (US-ASCII decimal 22) character is decimal 22) character. The DQUOTE (US-ASCII decimal 22) character is
used as a delimiter for parameter values that contain restricted used as a delimiter for parameter values that contain restricted
characters or URI text. For example: characters or URI text. For example:
skipping to change at page 14, line 26 skipping to change at page 15, line 17
/ cutypeparam ; Calendar user type / cutypeparam ; Calendar user type
/ delfromparam ; Delegator / delfromparam ; Delegator
/ deltoparam ; Delegatee / deltoparam ; Delegatee
/ dirparam ; Directory entry / dirparam ; Directory entry
/ encodingparam ; Inline encoding / encodingparam ; Inline encoding
/ fmttypeparam ; Format type / fmttypeparam ; Format type
/ fbtypeparam ; Free/busy time type / fbtypeparam ; Free/busy time type
/ languageparam ; Language for text / languageparam ; Language for text
/ memberparam ; Group or list membership / memberparam ; Group or list membership
/ partstatparam ; Participation status / partstatparam ; Participation status
/ rangeparam ; Recurrence identifier range
/ trigrelparam ; Alarm trigger relationship / trigrelparam ; Alarm trigger relationship
/ reltypeparam ; Relationship type / reltypeparam ; Relationship type
/ roleparam ; Participation role / roleparam ; Participation role
/ rsvpparam ; RSVP expectation / rsvpparam ; RSVP expectation
/ sentbyparam ; Sent by / sentbyparam ; Sent by
/ tzidparam ; Reference to time zone object / tzidparam ; Reference to time zone object
/ valuetypeparam ; Property value data type / valuetypeparam ; Property value data type
/ ianaparam / ianaparam
; Some other IANA registered iCalendar parameter. ; Some other IANA registered iCalendar parameter.
/ xparam / xparam
; A non-standard, experimental parameter. ; A non-standard, experimental parameter.
ianaparam = iana-token "=" param-value *("," param-value) ianaparam = iana-token "=" param-value *("," param-value)
xparam = x-name "=" param-value *("," param-value) xparam = x-name "=" param-value *("," param-value)
3.2.1. Alternate Text Representation 3.2.1. Alternate Text Representation
Parameter Name: ALTREP Parameter Name: ALTREP
Purpose: To specify an alternate text representation for the property Purpose: To specify an alternate text representation for the
value. property value.
Format Definition: The property parameter is defined by the following Format Definition: This property parameter is defined by the
notation: following notation:
altrepparam = "ALTREP" "=" DQUOTE uri DQUOTE altrepparam = "ALTREP" "=" DQUOTE uri DQUOTE
Description: The parameter specifies a URI that points to an Description: This parameter specifies a URI that points to an
alternate representation for a textual property value. A property alternate representation for a textual property value. A property
specifying this parameter MUST also include a value that reflects specifying this parameter MUST also include a value that reflects
the default representation of the text value. The individual URI the default representation of the text value. The individual URI
parameter values MUST each be specified in a quoted-string. parameter values MUST each be specified in a quoted-string.
Example: Example:
DESCRIPTION;ALTREP="CID:part3.msg.970415T083000@example.com": DESCRIPTION;ALTREP="CID:part3.msg.970415T083000@example.com":
Project XYZ Review Meeting will include the following agenda Project XYZ Review Meeting will include the following agenda
items: (a) Market Overview\, (b) Finances\, (c) Project Man items: (a) Market Overview\, (b) Finances\, (c) Project Man
skipping to change at page 16, line 4 skipping to change at page 16, line 38
<li>Finances</li> <li>Finances</li>
<li>Project Management</li> <li>Project Management</li>
</ol> </ol>
</p> </p>
</body> </body>
</html> </html>
3.2.2. Common Name 3.2.2. Common Name
Parameter Name: CN Parameter Name: CN
Purpose: To specify the common name to be associated with the Purpose: To specify the common name to be associated with the
calendar user specified by the property. calendar user specified by the property.
Format Definition: The property parameter is defined by the following Format Definition: This property parameter is defined by the
notation: following notation:
cnparam = "CN" "=" param-value cnparam = "CN" "=" param-value
Description: This parameter can be specified on properties with a Description: This parameter can be specified on properties with a
CAL-ADDRESS value type. The parameter specifies the common name CAL-ADDRESS value type. The parameter specifies the common name
to be associated with the calendar user specified by the property. to be associated with the calendar user specified by the property.
The parameter value is text. The parameter value can be used for The parameter value is text. The parameter value can be used for
display text to be associated with the calendar address specified display text to be associated with the calendar address specified
by the property. by the property.
Example: Example:
ORGANIZER;CN="John Smith":MAILTO:jsmith@example.com ORGANIZER;CN="John Smith":mailto:jsmith@example.com
3.2.3. Calendar User Type 3.2.3. Calendar User Type
Parameter Name: CUTYPE Parameter Name: CUTYPE
Purpose: To specify the type of calendar user specified by the Purpose: To specify the type of calendar user specified by the
property. property.
Format Definition: The property parameter is defined by the following Format Definition: This property parameter is defined by the
notation: following notation:
cutypeparam = "CUTYPE" "=" cutypeparam = "CUTYPE" "="
("INDIVIDUAL" ; An individual ("INDIVIDUAL" ; An individual
/ "GROUP" ; A group of individuals / "GROUP" ; A group of individuals
/ "RESOURCE" ; A physical resource / "RESOURCE" ; A physical resource
/ "ROOM" ; A room resource / "ROOM" ; A room resource
/ "UNKNOWN" ; Otherwise not known / "UNKNOWN" ; Otherwise not known
/ x-name ; Experimental type / x-name ; Experimental type
/ iana-token) ; Other IANA registered / iana-token) ; Other IANA registered
; type ; type
; Default is INDIVIDUAL ; Default is INDIVIDUAL
Description: This parameter can be specified on properties with a Description: This parameter can be specified on properties with a
CAL-ADDRESS value type. The parameter identifies the type of CAL-ADDRESS value type. The parameter identifies the type of
calendar user specified by the property. If not specified on a calendar user specified by the property. If not specified on a
property that allows this parameter, the default is INDIVIDUAL. property that allows this parameter, the default is INDIVIDUAL.
Example: Example:
ATTENDEE;CUTYPE=GROUP:MAILTO:ietf-calsch@imc.org ATTENDEE;CUTYPE=GROUP:mailto:ietf-calsch@example.org
3.2.4. Delegators 3.2.4. Delegators
Parameter Name: DELEGATED-FROM Parameter Name: DELEGATED-FROM
Purpose: To specify the calendar users that have delegated their Purpose: To specify the calendar users that have delegated their
participation to the calendar user specified by the property. participation to the calendar user specified by the property.
Format Definition: The property parameter is defined by the following Format Definition: This property parameter is defined by the
notation: following notation:
delfromparam = "DELEGATED-FROM" "=" DQUOTE cal-address delfromparam = "DELEGATED-FROM" "=" DQUOTE cal-address
DQUOTE *("," DQUOTE cal-address DQUOTE) DQUOTE *("," DQUOTE cal-address DQUOTE)
Description: This parameter can be specified on properties with a Description: This parameter can be specified on properties with a
CAL-ADDRESS value type. This parameter can be specified on a CAL-ADDRESS value type. This parameter specifies those calendar
property that has a value type of calendar address. This users that have delegated their participation in a group scheduled
parameter specifies those calendar users that have delegated their event or to-do to the calendar user specified by the property.
participation in a group scheduled event or to-do to the calendar The value MUST be a mailto URI as defined in [RFC2368] . The
user specified by the property. The value MUST be a MAILTO URI as individual calendar address parameter values MUST each be
defined in [RFC2368] . The individual calendar address parameter specified in a quoted-string.
values MUST each be specified in a quoted-string.
Example: Example:
ATTENDEE;DELEGATED-FROM="MAILTO:jsmith@example.com":MAILTO: ATTENDEE;DELEGATED-FROM="mailto:jsmith@example.com":mailto:
jdoe@example.com jdoe@example.com
3.2.5. Delegatees 3.2.5. Delegatees
Parameter Name: DELEGATED-TO Parameter Name: DELEGATED-TO
Purpose: To specify the calendar users to whom the calendar user Purpose: To specify the calendar users to whom the calendar user
specified by the property has delegated participation. specified by the property has delegated participation.
Format Definition: The property parameter is defined by the following Format Definition: This property parameter is defined by the
notation: following notation:
deltoparam = "DELEGATED-TO" "=" DQUOTE cal-address DQUOTE deltoparam = "DELEGATED-TO" "=" DQUOTE cal-address DQUOTE
*("," DQUOTE cal-address DQUOTE) *("," DQUOTE cal-address DQUOTE)
Description: This parameter can be specified on properties with a Description: This parameter can be specified on properties with a
CAL-ADDRESS value type. This parameter specifies those calendar CAL-ADDRESS value type. This parameter specifies those calendar
users whom have been delegated participation in a group scheduled users whom have been delegated participation in a group scheduled
event or to-do by the calendar user specified by the property. event or to-do by the calendar user specified by the property.
The value MUST be a MAILTO URI as defined in [RFC2368] . The The value MUST be a mailto URI as defined in [RFC2368] . The
individual calendar address parameter values MUST each be individual calendar address parameter values MUST each be
specified in a quoted-string. specified in a quoted-string.
Example: Example:
ATTENDEE;DELEGATED-TO="MAILTO:jdoe@example.com","MAILTO:jqpublic ATTENDEE;DELEGATED-TO="mailto:jdoe@example.com","mailto:jqpublic
@example.com":MAILTO:jsmith@example.com @example.com":mailto:jsmith@example.com
3.2.6. Directory Entry Reference 3.2.6. Directory Entry Reference
Parameter Name: DIR Parameter Name: DIR
Purpose: To specify reference to a directory entry associated with Purpose: To specify reference to a directory entry associated with
the calendar user specified by the property. the calendar user specified by the property.
Format Definition: The property parameter is defined by the following Format Definition: This property parameter is defined by the
notation: following notation:
dirparam = "DIR" "=" DQUOTE uri DQUOTE dirparam = "DIR" "=" DQUOTE uri DQUOTE
Description: This parameter can be specified on properties with a Description: This parameter can be specified on properties with a
CAL-ADDRESS value type. The parameter specifies a reference to CAL-ADDRESS value type. The parameter specifies a reference to
the directory entry associated with the calendar user specified by the directory entry associated with the calendar user specified by
the property. The parameter value is a URI. The URI parameter the property. The parameter value is a URI. The URI parameter
value MUST be specified in a quoted-string. value MUST be specified in a quoted-string.
Example: Example:
ORGANIZER;DIR="ldap://example.com:6666/o=ABC%20Industries, ORGANIZER;DIR="ldap://example.com:6666/o=ABC%20Industries,
c=US???(cn=Jim%20Dolittle)":MAILTO:jimdo@example.com c=US???(cn=Jim%20Dolittle)":mailto:jimdo@example.com
3.2.7. Inline Encoding 3.2.7. Inline Encoding
Parameter Name: ENCODING Parameter Name: ENCODING
Purpose: To specify an alternate inline encoding for the property Purpose: To specify an alternate inline encoding for the property
value. value.
Format Definition: The property parameter is defined by the following Format Definition: This property parameter is defined by the
notation: following notation:
encodingparam = "ENCODING" "=" encodingparam = "ENCODING" "="
("8BIT" ("8BIT"
; "8bit" text encoding is defined in ; "8bit" text encoding is defined in
[RFC2045] [RFC2045]
/ "BASE64" encodingparam = "ENCODING" "="
; "BASE64" binary encoding format is defined in ("8BIT"
; "8bit" text encoding is defined in
[RFC4648] [RFC4648]
/ iana-token encodingparam = "ENCODING" "="
; Some other IANA registered iCalendar encoding type ("8BIT"
/ x-name) ; "8bit" text encoding is defined in
; A non-standard, experimental encoding type
Description: The property parameter identifies the inline encoding Description: This property parameter identifies the inline encoding
used in a property value. The default encoding is "8BIT", used in a property value. The default encoding is "8BIT",
corresponding to a property value consisting of text. The corresponding to a property value consisting of text. The
"BASE64" encoding type corresponds to a property value encoded "BASE64" encoding type corresponds to a property value encoded
using the "BASE64" encoding defined in [RFC2045]. using the "BASE64" encoding defined in [RFC2045].
If the value type parameter is ";VALUE=BINARY", then the inline If the value type parameter is ";VALUE=BINARY", then the inline
encoding parameter MUST be specified with the value encoding parameter MUST be specified with the value
";ENCODING=BASE64". ";ENCODING=BASE64".
Example: Example:
skipping to change at page 19, line 42 skipping to change at page 20, line 22
CAdOgAwIBAgICBEUwDQYJKoZIhvcNAQEEBQAwdzELMAkGA1UEBhMCVVMxLDA CAdOgAwIBAgICBEUwDQYJKoZIhvcNAQEEBQAwdzELMAkGA1UEBhMCVVMxLDA
qBgNVBAoTI05ldHNjYXBlIENvbW11bmljYXRpb25zIENvcnBvcmF0aW9uMRw qBgNVBAoTI05ldHNjYXBlIENvbW11bmljYXRpb25zIENvcnBvcmF0aW9uMRw
<...remainder of "BASE64" encoded binary data...> <...remainder of "BASE64" encoded binary data...>
3.2.8. Format Type 3.2.8. Format Type
Parameter Name: FMTTYPE Parameter Name: FMTTYPE
Purpose: To specify the content type of a referenced object. Purpose: To specify the content type of a referenced object.
Format Definition: The property parameter is defined by the following Format Definition: This property parameter is defined by the
notation: following notation:
fmttypeparam = "FMTTYPE" "=" iana-token fmttypeparam = "FMTTYPE" "=" iana-token
; A IANA registered content type ; A IANA registered media type
/ x-name / x-name
; A non-standard content type ; A non-standard media type
Description: This parameter can be specified on properties that are Description: This parameter can be specified on properties that are
used to reference an object. The parameter specifies the content used to reference an object. The parameter specifies the content
type of the referenced object. For example, on the "ATTACH" type of the referenced object. For example, on the "ATTACH"
property, a FTP type URI value does not, by itself, necessarily property, a FTP type URI value does not, by itself, necessarily
convey the type of content associated with the resource. The convey the type of content associated with the resource. The
parameter value MUST be the TEXT for either an IANA registered parameter value MUST be the text for either an IANA registered
content type or a non-standard content type. media type or a non-standard media type.
Example: Example:
ATTACH;FMTTYPE=application/msword:ftp://example.com/pub/docs/ ATTACH;FMTTYPE=application/msword:ftp://example.com/pub/docs/
agenda.doc agenda.doc
3.2.9. Free/Busy Time Type 3.2.9. Free/Busy Time Type
Parameter Name: FBTYPE Parameter Name: FBTYPE
Purpose: To specify the free or busy time type. Purpose: To specify the free or busy time type.
Format Definition: The property parameter is defined by the following Format Definition: This property parameter is defined by the
notation: following notation:
fbtypeparam = "FBTYPE" "=" ("FREE" / "BUSY" fbtypeparam = "FBTYPE" "=" ("FREE" / "BUSY"
/ "BUSY-UNAVAILABLE" / "BUSY-TENTATIVE" / "BUSY-UNAVAILABLE" / "BUSY-TENTATIVE"
/ x-name / x-name
; Some experimental iCalendar data type. ; Some experimental iCalendar free busy type.
/ iana-token) / iana-token)
; Some other IANA registered iCalendar data type. ; Some other IANA registered iCalendar free busy type.
Description: The parameter specifies the free or busy time type. The Description: This parameter specifies the free or busy time type.
value FREE indicates that the time interval is free for The value FREE indicates that the time interval is free for
scheduling. The value BUSY indicates that the time interval is scheduling. The value BUSY indicates that the time interval is
busy because one or more events have been scheduled for that busy because one or more events have been scheduled for that
interval. The value BUSY-UNAVAILABLE indicates that the time interval. The value BUSY-UNAVAILABLE indicates that the time
interval is busy and that the interval can not be scheduled. The interval is busy and that the interval can not be scheduled. The
value BUSY-TENTATIVE indicates that the time interval is busy value BUSY-TENTATIVE indicates that the time interval is busy
because one or more events have been tentatively scheduled for because one or more events have been tentatively scheduled for
that interval. If not specified on a property that allows this that interval. If not specified on a property that allows this
parameter, the default is BUSY. parameter, the default is BUSY.
Example: The following is an example of this parameter on a FREEBUSY Example: The following is an example of this parameter on a
property. "FREEBUSY" property.
FREEBUSY;FBTYPE=BUSY:19980415T133000Z/19980415T170000Z FREEBUSY;FBTYPE=BUSY:19980415T133000Z/19980415T170000Z
3.2.10. Language 3.2.10. Language
Parameter Name: LANGUAGE Parameter Name: LANGUAGE
Purpose: To specify the language for text values in a property or Purpose: To specify the language for text values in a property or
property parameter. property parameter.
Format Definition: The property parameter is defined by the following Format Definition: This property parameter is defined by the
notation: following notation:
languageparam = "LANGUAGE" "=" language languageparam = "LANGUAGE" "=" language
language = <Text identifying a language, as defined in language = Language-Tag
[RFC3066] ; As defined in
> [RFC4646]
Description: The parameter identifies the language of the text in the languageparam = "LANGUAGE" "=" language
property or property parameter value. The value of the "language"
property parameter is that defined in [RFC3066] . language = Language-Tag
; As defined in
Description: This parameter identifies the language of the text in
the property or property parameter value. The value of the
"language" property parameter is that defined in [RFC4646] .
For transport in a MIME entity, the Content-Language header field For transport in a MIME entity, the Content-Language header field
can be used to set the default language for the entire body part. can be used to set the default language for the entire body part.
Otherwise, no default language is assumed. Otherwise, no default language is assumed.
Example: Example:
SUMMARY;LANGUAGE=us-EN:Company Holiday Party SUMMARY;LANGUAGE=us-EN:Company Holiday Party
LOCATION;LANGUAGE=en:Germany LOCATION;LANGUAGE=en:Germany
LOCATION;LANGUAGE=no:Tyskland LOCATION;LANGUAGE=no:Tyskland
The following example makes use of the Quoted-Printable encoding The following example makes use of the Quoted-Printable encoding
in order to represent non-ASCII characters. in order to represent NON-US-ASCII characters.
LOCATION;LANGUAGE=3Dda:K=C3=B8benhavn LOCATION;LANGUAGE=3Dda:K=C3=B8benhavn
LOCATION;LANGUAGE=en:Copenhagen LOCATION;LANGUAGE=en:Copenhagen
3.2.11. Group or List Membership 3.2.11. Group or List Membership
Parameter Name: MEMBER Parameter Name: MEMBER
Purpose: To specify the group or list membership of the calendar user Purpose: To specify the group or list membership of the calendar
specified by the property. user specified by the property.
Format Definition: The property parameter is defined by the following Format Definition: This property parameter is defined by the
notation: following notation:
memberparam = "MEMBER" "=" DQUOTE cal-address DQUOTE memberparam = "MEMBER" "=" DQUOTE cal-address DQUOTE
*("," DQUOTE cal-address DQUOTE) *("," DQUOTE cal-address DQUOTE)
Description: This parameter can be specified on properties with a Description: This parameter can be specified on properties with a
CAL-ADDRESS value type. The parameter identifies the groups or CAL-ADDRESS value type. The parameter identifies the groups or
list membership for the calendar user specified by the property. list membership for the calendar user specified by the property.
The parameter value either a single calendar address in a quoted- The parameter value is either a single calendar address in a
string or a COMMA character (US-ASCII decimal 44) list of calendar quoted-string or a COMMA character (US-ASCII decimal 44) separated
addresses, each in a quoted-string. The individual calendar list of calendar addresses, each in a quoted-string. The
address parameter values MUST each be specified in a quoted- individual calendar address parameter values MUST each be
string. specified in a quoted-string.
Example: Example:
ATTENDEE;MEMBER="MAILTO:ietf-calsch@example.org":MAILTO: ATTENDEE;MEMBER="mailto:ietf-calsch@example.org":mailto:
jsmith@example.com jsmith@example.com
ATTENDEE;MEMBER="MAILTO:projectA@example.com","MAILTO:pr ATTENDEE;MEMBER="mailto:projectA@example.com","mailto:pr
ojectB@example.com":MAILTO:janedoe@example.com ojectB@example.com":mailto:janedoe@example.com
3.2.12. Participation Status 3.2.12. Participation Status
Parameter Name: PARTSTAT Parameter Name: PARTSTAT
Purpose: To specify the participation status for the calendar user Purpose: To specify the participation status for the calendar user
specified by the property. specified by the property.
Format Definition: The property parameter is defined by the following Format Definition: This property parameter is defined by the
notation: following notation:
partstatparam = "PARTSTAT" "=" partstatparam = "PARTSTAT" "="
("NEEDS-ACTION" ; Event needs action ("NEEDS-ACTION" ; Event needs action
/ "ACCEPTED" ; Event accepted / "ACCEPTED" ; Event accepted
/ "DECLINED" ; Event declined / "DECLINED" ; Event declined
/ "TENTATIVE" ; Event tentatively / "TENTATIVE" ; Event tentatively
; accepted ; accepted
/ "DELEGATED" ; Event delegated / "DELEGATED" ; Event delegated
/ x-name ; Experimental status / x-name ; Experimental status
/ iana-token) ; Other IANA registered / iana-token) ; Other IANA registered
skipping to change at page 24, line 8 skipping to change at page 25, line 8
CAL-ADDRESS value type. The parameter identifies the CAL-ADDRESS value type. The parameter identifies the
participation status for the calendar user specified by the participation status for the calendar user specified by the
property value. The parameter values differ depending on whether property value. The parameter values differ depending on whether
they are associated with a group scheduled "VEVENT", "VTODO" or they are associated with a group scheduled "VEVENT", "VTODO" or
"VJOURNAL". The values MUST match one of the values allowed for "VJOURNAL". The values MUST match one of the values allowed for
the given calendar component. If not specified on a property that the given calendar component. If not specified on a property that
allows this parameter, the default value is NEEDS-ACTION. allows this parameter, the default value is NEEDS-ACTION.
Example: Example:
ATTENDEE;PARTSTAT=DECLINED:MAILTO:jsmith@example.com ATTENDEE;PARTSTAT=DECLINED:mailto:jsmith@example.com
3.2.13. Recurrence Identifier Range
Parameter Name: RANGE
Purpose: To specify the effective range of recurrence instances from
the instance specified by the recurrence identifier specified by
the property.
Format Definition: The property parameter is defined by the following
notation:
rangeparam = "RANGE" "=" ("THISANDPRIOR"
; To specify all instances prior to the recurrence identifier
/ "THISANDFUTURE")
; To specify the instance specified by the recurrence identifier
; and all subsequent recurrence instances
Description: The parameter can be specified on a property that
specifies a recurrence identifier. The parameter specifies the
effective range of recurrence instances that is specified by the
property. The effective range is from the recurrence identified
specified by the property. If this parameter is not specified an
allowed property, then the default range is the single instance
specified by the recurrence identifier value of the property. The
parameter value can be "THISANDPRIOR" to indicate a range defined
by the recurrence identified value of the property and all prior
instances. The parameter value can also be "THISANDFUTURE" to
indicate a range defined by the recurrence identifier and all
subsequent instances.
Example:
RECURRENCE-ID;RANGE=THISANDPRIOR:19980401T133000Z
3.2.14. Alarm Trigger Relationship 3.2.13. Alarm Trigger Relationship
Parameter Name: RELATED Parameter Name: RELATED
Purpose: To specify the relationship of the alarm trigger with Purpose: To specify the relationship of the alarm trigger with
respect to the start or end of the calendar component. respect to the start or end of the calendar component.
Format Definition: The property parameter is defined by the following Format Definition: This property parameter is defined by the
notation: following notation:
trigrelparam = "RELATED" "=" trigrelparam = "RELATED" "="
("START" ; Trigger off of start ("START" ; Trigger off of start
/ "END") ; Trigger off of end / "END") ; Trigger off of end
Description: The parameter can be specified on properties that Description: This parameter can be specified on properties that
specify an alarm trigger with a DURATION value type. The specify an alarm trigger with a "DURATION" value type. The
parameter specifies whether the alarm will trigger relative to the parameter specifies whether the alarm will trigger relative to the
start or end of the calendar component. The parameter value START start or end of the calendar component. The parameter value START
will set the alarm to trigger off the start of the calendar will set the alarm to trigger off the start of the calendar
component; the parameter value END will set the alarm to trigger component; the parameter value END will set the alarm to trigger
off the end of the calendar component. If the parameter is not off the end of the calendar component. If the parameter is not
specified on an allowable property, then the default is START. specified on an allowable property, then the default is START.
Example: Example:
TRIGGER;RELATED=END:PT5M TRIGGER;RELATED=END:PT5M
3.2.15. Relationship Type 3.2.14. Relationship Type
Parameter Name: RELTYPE Parameter Name: RELTYPE
Purpose: To specify the type of hierarchical relationship associated Purpose: To specify the type of hierarchical relationship associated
with the calendar component specified by the property. with the calendar component specified by the property.
Format Definition: The property parameter is defined by the following Format Definition: This property parameter is defined by the
notation: following notation:
reltypeparam = "RELTYPE" "=" reltypeparam = "RELTYPE" "="
("PARENT" ; Parent relationship. Default. ("PARENT" ; Parent relationship. Default.
/ "CHILD" ; Child relationship / "CHILD" ; Child relationship
/ "SIBLING" ; Sibling relationship / "SIBLING" ; Sibling relationship
/ iana-token ; Some other IANA registered / iana-token ; Some other IANA registered
; iCalendar relationship type ; iCalendar relationship type
/ x-name) ; A non-standard, experimental / x-name) ; A non-standard, experimental
; relationship type ; relationship type
skipping to change at page 26, line 11 skipping to change at page 26, line 30
component is a subordinate of the calendar component; SIBLING to component is a subordinate of the calendar component; SIBLING to
indicate that the referenced calendar component is a peer of the indicate that the referenced calendar component is a peer of the
calendar component. If this parameter is not specified on an calendar component. If this parameter is not specified on an
allowable property, the default relationship type is PARENT. allowable property, the default relationship type is PARENT.
Example: Example:
RELATED-TO;RELTYPE=SIBLING:19960401-080045-4000F192713@ RELATED-TO;RELTYPE=SIBLING:19960401-080045-4000F192713@
example.com example.com
3.2.16. Participation Role 3.2.15. Participation Role
Parameter Name: ROLE Parameter Name: ROLE
Purpose: To specify the participation role for the calendar user Purpose: To specify the participation role for the calendar user
specified by the property. specified by the property.
Format Definition: The property parameter is defined by the following Format Definition: This property parameter is defined by the
notation: following notation:
roleparam = "ROLE" "=" roleparam = "ROLE" "="
("CHAIR" ; Indicates chair of the ("CHAIR" ; Indicates chair of the
; calendar entity ; calendar entity
/ "REQ-PARTICIPANT" ; Indicates a participant whose / "REQ-PARTICIPANT" ; Indicates a participant whose
; participation is required ; participation is required
/ "OPT-PARTICIPANT" ; Indicates a participant whose / "OPT-PARTICIPANT" ; Indicates a participant whose
; participation is optional ; participation is optional
/ "NON-PARTICIPANT" ; Indicates a participant who / "NON-PARTICIPANT" ; Indicates a participant who
; is copied for information ; is copied for information
skipping to change at page 26, line 34 skipping to change at page 27, line 4
/ "REQ-PARTICIPANT" ; Indicates a participant whose / "REQ-PARTICIPANT" ; Indicates a participant whose
; participation is required ; participation is required
/ "OPT-PARTICIPANT" ; Indicates a participant whose / "OPT-PARTICIPANT" ; Indicates a participant whose
; participation is optional ; participation is optional
/ "NON-PARTICIPANT" ; Indicates a participant who / "NON-PARTICIPANT" ; Indicates a participant who
; is copied for information ; is copied for information
; purposes only ; purposes only
/ x-name ; Experimental role / x-name ; Experimental role
/ iana-token) ; Other IANA role / iana-token) ; Other IANA role
; Default is REQ-PARTICIPANT ; Default is REQ-PARTICIPANT
Description: This parameter can be specified on properties with a Description: This parameter can be specified on properties with a
CAL-ADDRESS value type. The parameter specifies the participation CAL-ADDRESS value type. The parameter specifies the participation
role for the calendar user specified by the property in the group role for the calendar user specified by the property in the group
schedule calendar component. If not specified on a property that schedule calendar component. If not specified on a property that
allows this parameter, the default value is REQ-PARTICIPANT. allows this parameter, the default value is REQ-PARTICIPANT.
Example: Example:
ATTENDEE;ROLE=CHAIR:MAILTO:mrbig@example.com ATTENDEE;ROLE=CHAIR:mailto:mrbig@example.com
3.2.17. RSVP Expectation 3.2.16. RSVP Expectation
Parameter Name: RSVP Parameter Name: RSVP
Purpose: To specify whether there is an expectation of a favor of a Purpose: To specify whether there is an expectation of a favor of a
reply from the calendar user specified by the property value. reply from the calendar user specified by the property value.
Format Definition: The property parameter is defined by the following Format Definition: This property parameter is defined by the
notation: following notation:
rsvpparam = "RSVP" "=" ("TRUE" / "FALSE") rsvpparam = "RSVP" "=" ("TRUE" / "FALSE")
; Default is FALSE ; Default is FALSE
Description: This parameter can be specified on properties with a Description: This parameter can be specified on properties with a
CAL-ADDRESS value type. The parameter identifies the expectation CAL-ADDRESS value type. The parameter identifies the expectation
of a reply from the calendar user specified by the property value. of a reply from the calendar user specified by the property value.
This parameter is used by the "Organizer" to request a This parameter is used by the "Organizer" to request a
participation status reply from an "Attendee" of a group scheduled participation status reply from an "Attendee" of a group scheduled
event or to-do. If not specified on a property that allows this event or to-do. If not specified on a property that allows this
parameter, the default value is FALSE. parameter, the default value is FALSE.
Example: Example:
ATTENDEE;RSVP=TRUE:MAILTO:jsmith@example.com ATTENDEE;RSVP=TRUE:mailto:jsmith@example.com
3.2.18. Sent By 3.2.17. Sent By
Parameter Name: SENT-BY Parameter Name: SENT-BY
Purpose: To specify the calendar user that is acting on behalf of the Purpose: To specify the calendar user that is acting on behalf of
calendar user specified by the property. the calendar user specified by the property.
Format Definition: The property parameter is defined by the following Format Definition: This property parameter is defined by the
notation: following notation:
sentbyparam = "SENT-BY" "=" DQUOTE cal-address DQUOTE sentbyparam = "SENT-BY" "=" DQUOTE cal-address DQUOTE
Description: This parameter can be specified on properties with a Description: This parameter can be specified on properties with a
CAL-ADDRESS value type. The parameter specifies the calendar user CAL-ADDRESS value type. The parameter specifies the calendar user
that is acting on behalf of the calendar user specified by the that is acting on behalf of the calendar user specified by the
property. The parameter value MUST be a MAILTO URI as defined in property. The parameter value MUST be a mailto URI as defined in
[RFC2368] . The individual calendar address parameter values MUST [RFC2368] . The individual calendar address parameter values MUST
each be specified in a quoted-string. each be specified in a quoted-string.
Example: Example:
ORGANIZER;SENT-BY="MAILTO:sray@example.com":MAILTO: ORGANIZER;SENT-BY="mailto:sray@example.com":mailto:
jsmith@example.com jsmith@example.com
3.2.19. Time Zone Identifier 3.2.18. Time Zone Identifier
Parameter Name: TZID Parameter Name: TZID
Purpose: To specify the identifier for the time zone definition for a Purpose: To specify the identifier for the time zone definition for
time component in the property value. a time component in the property value.
Format Definition: The property parameter is defined by the following Format Definition: This property parameter is defined by the
notation: following notation:
tzidparam = "TZID" "=" [tzidprefix] paramtext tzidparam = "TZID" "=" [tzidprefix] paramtext
tzidprefix = "/" tzidprefix = "/"
Description: The parameter MUST be specified on the "DTSTART", Description: This parameter MUST be specified on the "DTSTART",
"DTEND", "DUE", "EXDATE" and "RDATE" properties when either a "DTEND", "DUE", "EXDATE" and "RDATE" properties when either a
DATE- TIME or TIME value type is specified and when the value is DATE- TIME or TIME value type is specified and when the value is
not either a UTC or a "floating" time. Refer to the DATE-TIME or not either a UTC or a "floating" time. Refer to the DATE-TIME or
TIME value type definition for a description of UTC and "floating TIME value type definition for a description of UTC and "floating
time" formats. This property parameter specifies a text value time" formats. This property parameter specifies a text value
which uniquely identifies the "VTIMEZONE" calendar component to be which uniquely identifies the "VTIMEZONE" calendar component to be
used when evaluating the time portion of the property. The value used when evaluating the time portion of the property. The value
of the TZID property parameter will be equal to the value of the of the "TZID" property parameter will be equal to the value of the
TZID property for the matching time zone definition. An "TZID" property for the matching time zone definition. An
individual "VTIMEZONE" calendar component MUST be specified for individual "VTIMEZONE" calendar component MUST be specified for
each unique "TZID" parameter value specified in the iCalendar each unique "TZID" parameter value specified in the iCalendar
object. object.
The parameter MUST be specified on properties with a DATE-TIME The parameter MUST be specified on properties with a DATE-TIME
value if the DATE-TIME is not either a UTC or a "floating" time. value if the DATE-TIME is not either a UTC or a "floating" time.
The presence of the SOLIDUS character (US-ASCII decimal 47) as a The presence of the SOLIDUS character (US-ASCII decimal 47) as a
prefix, indicates that this TZID represents a unique ID in a prefix, indicates that this "TZID" represents a unique ID in a
globally defined time zone registry (when such registry is globally defined time zone registry (when such registry is
defined). defined).
Note: This document does not define a naming convention for Note: This document does not define a naming convention for
time zone identifiers. Implementers may want to use the naming time zone identifiers. Implementers may want to use the naming
conventions defined in existing time zone specifications such conventions defined in existing time zone specifications such
as the public-domain Olson database [TZDB]. The specification as the public-domain TZ Database [TZDB]. The specification of
of globally unique time zone identifiers is not addressed by globally unique time zone identifiers is not addressed by this
this document and is left for future study. document and is left for future study.
The following are examples of this property parameter: The following are examples of this property parameter:
DTSTART;TZID=US-Eastern:19980119T020000 DTSTART;TZID=US-Eastern:19980119T020000
DTEND;TZID=US-Eastern:19980119T030000 DTEND;TZID=US-Eastern:19980119T030000
The TZID property parameter MUST NOT be applied to DATE-TIME or
The "TZID" property parameter MUST NOT be applied to DATE-TIME or
TIME properties whose time values are specified in UTC. TIME properties whose time values are specified in UTC.
The use of local time in a DATE-TIME or TIME value without the The use of local time in a DATE-TIME or TIME value without the
TZID property parameter is to be interpreted as a local time "TZID" property parameter is to be interpreted as a local time
value, regardless of the existence of "VTIMEZONE" calendar value, regardless of the existence of "VTIMEZONE" calendar
components in the iCalendar object. components in the iCalendar object.
For more information see the sections on the data types DATE-TIME For more information see the sections on the value types DATE-TIME
and TIME. and TIME.
3.2.20. Value Data Types 3.2.19. Value Data Types
Parameter Name: VALUE Parameter Name: VALUE
Purpose: To explicitly specify the data type format for a property Purpose: To explicitly specify the value type format for a property
value. value.
Format Definition: The property parameter is defined by the following Format Definition: This property parameter is defined by the
notation: following notation:
valuetypeparam = "VALUE" "=" valuetype valuetypeparam = "VALUE" "=" valuetype
valuetype = ("BINARY" valuetype = ("BINARY"
/ "BOOLEAN" / "BOOLEAN"
/ "CAL-ADDRESS" / "CAL-ADDRESS"
/ "DATE" / "DATE"
/ "DATE-TIME" / "DATE-TIME"
/ "DURATION" / "DURATION"
/ "FLOAT" / "FLOAT"
/ "INTEGER" / "INTEGER"
/ "PERIOD" / "PERIOD"
/ "RECUR" / "RECUR"
/ "TEXT" / "TEXT"
/ "TIME" / "TIME"
/ "URI" / "URI"
/ "UTC-OFFSET" / "UTC-OFFSET"
/ x-name / x-name
; Some experimental iCalendar data type. ; Some experimental iCalendar value type.
/ iana-token) / iana-token)
; Some other IANA registered iCalendar data type. ; Some other IANA registered iCalendar value type.
Description: The parameter specifies the data type and format of the Description: This parameter specifies the value type and format of
property value. The property values MUST be of a single value the property value. The property values MUST be of a single value
type. For example, a "RDATE" property cannot have a combination type. For example, a "RDATE" property cannot have a combination
of DATE- TIME and TIME value types. of DATE- TIME and TIME value types.
If the property's value is the default value type, then this If the property's value is the default value type, then this
parameter need not be specified. However, if the property's parameter need not be specified. However, if the property's
default value type is overridden by some other allowable value default value type is overridden by some other allowable value
type, then this parameter MUST be specified. type, then this parameter MUST be specified.
3.3. Property Value Data Types 3.3. Property Value Data Types
skipping to change at page 30, line 22 skipping to change at page 31, line 4
The properties in an iCalendar object are strongly typed. The The properties in an iCalendar object are strongly typed. The
definition of each property restricts the value to be one of the definition of each property restricts the value to be one of the
value data types, or simply value types, defined in this section. value data types, or simply value types, defined in this section.
The value type for a property will either be specified implicitly as The value type for a property will either be specified implicitly as
the default value type or will be explicitly specified with the the default value type or will be explicitly specified with the
"VALUE" parameter. If the value type of a property is one of the "VALUE" parameter. If the value type of a property is one of the
alternate valid types, then it MUST be explicitly specified with the alternate valid types, then it MUST be explicitly specified with the
"VALUE" parameter. "VALUE" parameter.
3.3.1. Binary 3.3.1. Binary
Value Name: BINARY Value Name: BINARY
Purpose: This value type is used to identify properties that contain Purpose: This value type is used to identify properties that contain
a character encoding of inline binary data. For example, an a character encoding of inline binary data. For example, an
inline attachment of an object code might be included in an inline attachment of an object code might be included in an
iCalendar object. iCalendar object.
Format Definition: The value type is defined by the following Format Definition: This value type is defined by the following
notation: notation:
binary = *(4b-char) [b-end] binary = *(4b-char) [b-end]
; A "BASE64" encoded character string, as defined by ; A "BASE64" encoded character string, as defined by
[RFC4648] [RFC4648]
.
b-end = (2b-char "==") / (3b-char "=") binary = *(4b-char) [b-end]
; A "BASE64" encoded character string, as defined by
b-char = ALPHA / DIGIT / "+" / "/"
Description: Property values with this value type MUST also include Description: Property values with this value type MUST also include
the inline encoding parameter sequence of ";ENCODING=BASE64". the inline encoding parameter sequence of ";ENCODING=BASE64".
That is, all inline binary data MUST first be character encoded That is, all inline binary data MUST first be character encoded
using the "BASE64" encoding method defined in [RFC2045]. No using the "BASE64" encoding method defined in [RFC2045]. No
additional content value encoding (i.e., BACKSLASH character additional content value encoding (i.e., BACKSLASH character
encoding) is defined for this value type. encoding) is defined for this value type.
Example: The following is an abridged example of a "BASE64" encoded Example: The following is an abridged example of a "BASE64" encoded
binary value data. binary value data.
ATTACH;VALUE=BINARY;ENCODING=BASE64:MIICajCCAdOgAwIBAgICBEUwDQY
JKoZIhvcNAQEEBQAwdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05ldHNjYXBlI JKoZIhvcNAQEEBQAwdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05ldHNjYXBlI
ENvbW11bmljYXRpb25zIENvcnBvcmF0aW9uMRwwGgYDVQQLExNJbmZv ENvbW11bmljYXRpb25zIENvcnBvcmF0aW9uMRwwGgYDVQQLExNJbmZv
<...remainder of "BASE64" encoded binary data...> <...remainder of "BASE64" encoded binary data...>
3.3.2. Boolean 3.3.2. Boolean
Value Name: BOOLEAN Value Name: BOOLEAN
Purpose: This value type is used to identify properties that contain Purpose: This value type is used to identify properties that contain
either a "TRUE" or "FALSE" Boolean value. either a "TRUE" or "FALSE" Boolean value.
Format Definition: The value type is defined by the following Format Definition: This value type is defined by the following
notation: notation:
boolean = "TRUE" / "FALSE" boolean = "TRUE" / "FALSE"
Description: These values are case insensitive text. No additional Description: These values are case insensitive text. No additional
content value encoding (i.e., BACKSLASH character encoding) is content value encoding (i.e., BACKSLASH character encoding) is
defined for this value type. defined for this value type.
Example: The following is an example of a hypothetical property that Example: The following is an example of a hypothetical property that
has a BOOLEAN value type: has a BOOLEAN value type:
GIBBERISH:TRUE TRUE
3.3.3. Calendar User Address 3.3.3. Calendar User Address
Value Name: CAL-ADDRESS Value Name: CAL-ADDRESS
Purpose: This value type is used to identify properties that contain Purpose: This value type is used to identify properties that contain
a calendar user address. a calendar user address.
Format Definition: The value type is defined by the following Format Definition: This value type is defined by the following
notation: notation:
cal-address = uri cal-address = uri
Description: The value is a URI as defined by [RFC3986] or any other Description: The value is a URI as defined by [RFC3986] or any other
IANA registered form for a URI. When used to address an Internet IANA registered form for a URI. When used to address an Internet
email transport address for a calendar user, the value MUST be a email transport address for a calendar user, the value MUST be a
MAILTO URI, as defined by [RFC2368] . No additional content value mailto URI, as defined by [RFC2368] . No additional content value
encoding (i.e., BACKSLASH character encoding) is defined for this encoding (i.e., BACKSLASH character encoding) is defined for this
value type. value type.
Example: Example:
ATTENDEE:MAILTO:jane_doe@example.com mailto:jane_doe@example.com
3.3.4. Date 3.3.4. Date
Value Name: DATE Value Name: DATE
Purpose: This value type is used to identify values that contain a Purpose: This value type is used to identify values that contain a
calendar date. calendar date.
Format Definition: The value type is defined by the following Format Definition: This value type is defined by the following
notation: notation:
date = date-value date = date-value
date-value = date-fullyear date-month date-mday date-value = date-fullyear date-month date-mday
date-fullyear = 4DIGIT date-fullyear = 4DIGIT
date-month = 2DIGIT ;01-12 date-month = 2DIGIT ;01-12
date-mday = 2DIGIT ;01-28, 01-29, 01-30, 01-31 date-mday = 2DIGIT ;01-28, 01-29, 01-30, 01-31
;based on month/year ;based on month/year
skipping to change at page 33, line 5 skipping to change at page 33, line 29
19970714 19970714
3.3.5. Date-Time 3.3.5. Date-Time
Value Name: DATE-TIME Value Name: DATE-TIME
Purpose: This value type is used to identify values that specify a Purpose: This value type is used to identify values that specify a
precise calendar date and time of day. precise calendar date and time of day.
Format Definition: The value type is defined by the following Format Definition: This value type is defined by the following
notation: notation:
date-time = date "T" time ;As specified in the date and time date-time = date "T" time ;As specified in the date and time
;value definitions ;value definitions
Description: If the property permits, multiple "date-time" values are Description: If the property permits, multiple "date-time" values
specified as a COMMA character (US-ASCII decimal 44) separated are specified as a COMMA character (US-ASCII decimal 44) separated
list of values. No additional content value encoding (i.e., list of values. No additional content value encoding (i.e.,
BACKSLASH character encoding) is defined for this value type. BACKSLASH character encoding) is defined for this value type.
The "DATE-TIME" data type is used to identify values that contain The "DATE-TIME" value type is used to identify values that contain
a precise calendar date and time of day. The format is based on a precise calendar date and time of day. The format is based on
the [ISO.8601.1988] complete representation, basic format for a the [ISO.8601.1988] complete representation, basic format for a
calendar date and time of day. The text format is a concatenation calendar date and time of day. The text format is a concatenation
of the "date", followed by the LATIN CAPITAL LETTER T character of the "date", followed by the LATIN CAPITAL LETTER T character
(US-ASCII decimal 84) time designator, followed by the "time" (US-ASCII decimal 84) time designator, followed by the "time"
format. format.
The "DATE-TIME" data type expresses time values in three forms: The "DATE-TIME" value type expresses time values in three forms:
The form of date and time with UTC offset MUST NOT be used. For The form of date and time with UTC offset MUST NOT be used. For
example, the following is not valid for a date-time value: example, the following is not valid for a date-time value:
DTSTART:19980119T230000-0800 ;Invalid time format 19980119T230000-0800 ;Invalid time format
FORM #1: DATE WITH LOCAL TIME FORM #1: DATE WITH LOCAL TIME
The date with local time form is simply a date-time value that The date with local time form is simply a date-time value that
does not contain the UTC designator nor does it reference a time does not contain the UTC designator nor does it reference a time
zone. For example, the following represents January 18, 1998, at zone. For example, the following represents January 18, 1998, at
11 PM: 11 PM:
DTSTART:19980118T230000 19980118T230000
Date-time values of this type are said to be "floating" and are Date-time values of this type are said to be "floating" and are
not bound to any time zone in particular. They are used to not bound to any time zone in particular. They are used to
represent the same hour, minute, and second value regardless of represent the same hour, minute, and second value regardless of
which time zone is currently being observed. For example, an which time zone is currently being observed. For example, an
event can be defined that indicates that an individual will be event can be defined that indicates that an individual will be
busy from 11:00 AM to 1:00 PM every day, no matter which time zone busy from 11:00 AM to 1:00 PM every day, no matter which time zone
the person is in. In these cases, a local time can be specified. the person is in. In these cases, a local time can be specified.
The recipient of an iCalendar object with a property value The recipient of an iCalendar object with a property value
consisting of a local time, without any relative time zone consisting of a local time, without any relative time zone
information, SHOULD interpret the value as being fixed to whatever information, SHOULD interpret the value as being fixed to whatever
time zone the ATTENDEE is in at any given moment. This means that time zone the "ATTENDEE" is in at any given moment. This means
two ATTENDEEs, in different time zones, receiving the same event that two "Attendees", in different time zones, receiving the same
definition as a floating time, may be participating in the event event definition as a floating time, may be participating in the
at different actual times. Floating time SHOULD only be used event at different actual times. Floating time SHOULD only be
where that is the reasonable behavior. used where that is the reasonable behavior.
In most cases, a fixed time is desired. To properly communicate a In most cases, a fixed time is desired. To properly communicate a
fixed time in a property value, either UTC time or local time with fixed time in a property value, either UTC time or local time with
time zone reference MUST be specified. time zone reference MUST be specified.
The use of local time in a DATE-TIME value without the TZID The use of local time in a DATE-TIME value without the "TZID"
property parameter is to be interpreted as floating time, property parameter is to be interpreted as floating time,
regardless of the existence of "VTIMEZONE" calendar components in regardless of the existence of "VTIMEZONE" calendar components in
the iCalendar object. the iCalendar object.
FORM #2: DATE WITH UTC TIME FORM #2: DATE WITH UTC TIME
The date with UTC time, or absolute time, is identified by a LATIN The date with UTC time, or absolute time, is identified by a LATIN
CAPITAL LETTER Z suffix character (US-ASCII decimal 90), the UTC CAPITAL LETTER Z suffix character (US-ASCII decimal 90), the UTC
designator, appended to the time value. For example, the designator, appended to the time value. For example, the
following represents January 19, 1998, at 0700 UTC: following represents January 19, 1998, at 0700 UTC:
DTSTART:19980119T070000Z 19980119T070000Z
The "TZID" property parameter MUST NOT be applied to DATE-TIME
The TZID property parameter MUST NOT be applied to DATE-TIME
properties whose time values are specified in UTC. properties whose time values are specified in UTC.
FORM #3: DATE WITH LOCAL TIME AND TIME ZONE REFERENCE FORM #3: DATE WITH LOCAL TIME AND TIME ZONE REFERENCE
The date and local time with reference to time zone information is The date and local time with reference to time zone information is
identified by the use the TZID property parameter to reference the identified by the use the "TZID" property parameter to reference
appropriate time zone definition. TZID is discussed in detail in the appropriate time zone definition. "TZID" is discussed in
Section 3.2.19 . For example, the following represents 2 AM in detail in Section 3.2.18 . For example, the following represents
New York on Janurary 19, 1998: 2 AM in New York on Janurary 19, 1998:
DTSTART;TZID=US-Eastern:19980119T020000 TZID=US-Eastern:19980119T020000
Example: The following represents July 14, 1997, at 1:30 PM in New Example: The following represents July 14, 1997, at 1:30 PM in New
York City in each of the three time formats, using the "DTSTART" York City in each of the three time formats, using the "DTSTART"
property. property.
DTSTART:19970714T133000 ;Local time DTSTART:19970714T133000 ;Local time
DTSTART:19970714T173000Z ;UTC time DTSTART:19970714T173000Z ;UTC time
DTSTART;TZID=US-Eastern:19970714T133000 ;Local time and time DTSTART;TZID=US-Eastern:19970714T133000 ;Local time and time
; zone reference ; zone reference
A time value MUST ONLY specify 60 seconds when specifying the A time value MUST ONLY specify 60 seconds when specifying the
periodic "leap second" in the time value. For example: periodic "leap second" in the time value. For example:
COMPLETED:19970630T235960Z 19970630T235960Z
3.3.6. Duration 3.3.6. Duration
Value Name: DURATION Value Name: DURATION
Purpose: This value type is used to identify properties that contain Purpose: This value type is used to identify properties that contain
a duration of time. a duration of time.
Format Definition: The value type is defined by the following Format Definition: This value type is defined by the following
notation: notation:
dur-value = (["+"] / "-") "P" (dur-date / dur-time / dur-week) dur-value = (["+"] / "-") "P" (dur-date / dur-time / dur-week)
dur-date = dur-day [dur-time] dur-date = dur-day [dur-time]
dur-time = "T" (dur-hour / dur-minute / dur-second) dur-time = "T" (dur-hour / dur-minute / dur-second)
dur-week = 1*DIGIT "W" dur-week = 1*DIGIT "W"
dur-hour = 1*DIGIT "H" [dur-minute] dur-hour = 1*DIGIT "H" [dur-minute]
dur-minute = 1*DIGIT "M" [dur-second] dur-minute = 1*DIGIT "M" [dur-second]
dur-second = 1*DIGIT "S" dur-second = 1*DIGIT "S"
skipping to change at page 35, line 49 skipping to change at page 36, line 28
P7W P7W
3.3.7. Float 3.3.7. Float
Value Name: FLOAT Value Name: FLOAT
Purpose: This value type is used to identify properties that contain Purpose: This value type is used to identify properties that contain
a real number value. a real number value.
Format Definition: The value type is defined by the following Format Definition: This value type is defined by the following
notation: notation:
float = (["+"] / "-") 1*DIGIT ["." 1*DIGIT] float = (["+"] / "-") 1*DIGIT ["." 1*DIGIT]
Description: If the property permits, multiple "float" values are Description: If the property permits, multiple "float" values are
specified by a COMMA character (US-ASCII decimal 44) separated specified by a COMMA character (US-ASCII decimal 44) separated
list of values. list of values.
No additional content value encoding (i.e., BACKSLASH character No additional content value encoding (i.e., BACKSLASH character
encoding) is defined for this value type. encoding) is defined for this value type.
Example: Example:
1000000.0000001 1000000.0000001
skipping to change at page 36, line 18 skipping to change at page 37, line 4
No additional content value encoding (i.e., BACKSLASH character No additional content value encoding (i.e., BACKSLASH character
encoding) is defined for this value type. encoding) is defined for this value type.
Example: Example:
1000000.0000001 1000000.0000001
1.333 1.333
-3.14 -3.14
3.3.8. Integer 3.3.8. Integer
Value Name: INTEGER Value Name: INTEGER
Purpose: This value type is used to identify properties that contain Purpose: This value type is used to identify properties that contain
a signed integer value. a signed integer value.
Format Definition: The value type is defined by the following Format Definition: This value type is defined by the following
notation: notation:
integer = (["+"] / "-") 1*DIGIT integer = (["+"] / "-") 1*DIGIT
Description: If the property permits, multiple "integer" values are Description: If the property permits, multiple "integer" values are
specified by a COMMA character (US-ASCII decimal 44) separated specified by a COMMA character (US-ASCII decimal 44) separated
list of values. The valid range for "integer" is -2147483648 to list of values. The valid range for "integer" is -2147483648 to
2147483647. If the sign is not specified, then the value is 2147483647. If the sign is not specified, then the value is
assumed to be positive. assumed to be positive.
skipping to change at page 37, line 4 skipping to change at page 37, line 33
Example: Example:
1234567890 1234567890
-1234567890 -1234567890
+1234567890 +1234567890
432109876 432109876
3.3.9. Period of Time 3.3.9. Period of Time
Value Name: PERIOD Value Name: PERIOD
Purpose: This value type is used to identify values that contain a Purpose: This value type is used to identify values that contain a
precise period of time. precise period of time.
Format Definition: The value type is defined by the following Format Definition: This value type is defined by the following
notation: notation:
period = period-explicit / period-start period = period-explicit / period-start
period-explicit = date-time "/" date-time period-explicit = date-time "/" date-time
; [ISO.8601.1988] complete representation basic format for a ; [ISO.8601.1988] complete representation basic format for a
; period of time consisting of a start and end. The start MUST ; period of time consisting of a start and end. The start MUST
; be before the end. ; be before the end.
period-start = date-time "/" dur-value period-start = date-time "/" dur-value
skipping to change at page 38, line 12 skipping to change at page 38, line 41
No additional content value encoding (i.e., BACKSLASH character No additional content value encoding (i.e., BACKSLASH character
encoding) is defined for this value type. encoding) is defined for this value type.
3.3.10. Recurrence Rule 3.3.10. Recurrence Rule
Value Name: RECUR Value Name: RECUR
Purpose: This value type is used to identify properties that contain Purpose: This value type is used to identify properties that contain
a recurrence rule specification. a recurrence rule specification.
Format Definition: The value type is defined by the following Format Definition: This value type is defined by the following
notation: notation:
recur = "FREQ" "=" freq *( recur = recur-rule-part *( ";" recur-rule-part )
;
; either UNTIL or COUNT may appear in a 'recur', ; The rule parts are not ordered in any
; but UNTIL and COUNT MUST NOT occur in the same ; particular sequence
; 'recur' ;
; The FREQ rule part is REQUIRED,
( ";" "UNTIL" "=" enddate ) / ; but MUST NOT occur more than once
( ";" "COUNT" "=" 1*DIGIT ) / ;
; The UNTIL or COUNT rule parts are OPTIONAL,
; the rest of these keywords are optional, ; but they MUST NOT occur in the same 'recur'
;
; The other rule parts are OPTIONAL,
; but MUST NOT occur more than once ; but MUST NOT occur more than once
( ";" "INTERVAL" "=" 1*DIGIT ) / recur-rule-part = ( "FREQ" "=" freq )
( ";" "BYSECOND" "=" byseclist ) / / ( "UNTIL" "=" enddate )
( ";" "BYMINUTE" "=" byminlist ) / / ( "COUNT" "=" 1*DIGIT )
( ";" "BYHOUR" "=" byhrlist ) / / ( "INTERVAL" "=" 1*DIGIT )
( ";" "BYDAY" "=" bywdaylist ) / / ( "BYSECOND" "=" byseclist )
( ";" "BYMONTHDAY" "=" bymodaylist ) / / ( "BYMINUTE" "=" byminlist )
( ";" "BYYEARDAY" "=" byyrdaylist ) / / ( "BYHOUR" "=" byhrlist )
( ";" "BYWEEKNO" "=" bywknolist ) / / ( "BYDAY" "=" bywdaylist )
( ";" "BYMONTH" "=" bymolist ) / / ( "BYMONTHDAY" "=" bymodaylist )
( ";" "BYSETPOS" "=" bysplist ) / / ( "BYYEARDAY" "=" byyrdaylist )
( ";" "WKST" "=" weekday ) / / ( "BYWEEKNO" "=" bywknolist )
( ";" x-name "=" text ) / ( "BYMONTH" "=" bymolist )
) / ( "BYSETPOS" "=" bysplist )
/ ( "WKST" "=" weekday )
freq = "SECONDLY" / "MINUTELY" / "HOURLY" / "DAILY" freq = "SECONDLY" / "MINUTELY" / "HOURLY" / "DAILY"
/ "WEEKLY" / "MONTHLY" / "YEARLY" / "WEEKLY" / "MONTHLY" / "YEARLY"
enddate = date enddate = date / date-time ;A UTC value
/ date-time ;A UTC value
byseclist = seconds / ( seconds *("," seconds) ) byseclist = seconds / ( seconds *("," seconds) )
seconds = DIGIT / 2DIGIT ;0 to 59 seconds = DIGIT / 2DIGIT ;0 to 60
byminlist = minutes / ( minutes *("," minutes) ) byminlist = minutes / ( minutes *("," minutes) )
minutes = DIGIT / 2DIGIT ;0 to 59 minutes = DIGIT / 2DIGIT ;0 to 59
byhrlist = hour / ( hour *("," hour) ) byhrlist = hour / ( hour *("," hour) )
hour = DIGIT / 2DIGIT ;0 to 23 hour = DIGIT / 2DIGIT ;0 to 23
bywdaylist = weekdaynum / ( weekdaynum *("," weekdaynum) ) bywdaylist = weekdaynum / ( weekdaynum *("," weekdaynum) )
weekdaynum = [([plus] ordwk / minus ordwk)] weekday weekdaynum = [([plus] ordwk / minus ordwk)] weekday
skipping to change at page 40, line 4 skipping to change at page 40, line 30
weeknum = ([plus] ordwk) / (minus ordwk) weeknum = ([plus] ordwk) / (minus ordwk)
bymolist = monthnum / ( monthnum *("," monthnum) ) bymolist = monthnum / ( monthnum *("," monthnum) )
monthnum = DIGIT / 2DIGIT ;1 to 12 monthnum = DIGIT / 2DIGIT ;1 to 12
bysplist = setposday / ( setposday *("," setposday) ) bysplist = setposday / ( setposday *("," setposday) )
setposday = yeardaynum setposday = yeardaynum
Description: The value type is a structured value consisting of a
Description: This value type is a structured value consisting of a
list of one or more recurrence grammar parts. Each rule part is list of one or more recurrence grammar parts. Each rule part is
defined by a NAME=VALUE pair. The rule parts are separated from defined by a NAME=VALUE pair. The rule parts are separated from
each other by the SEMICOLON character (US-ASCII decimal 59). The each other by the SEMICOLON character (US-ASCII decimal 59). The
rule parts are not ordered in any particular sequence. Individual rule parts are not ordered in any particular sequence. Individual
rule parts MUST only be specified once. rule parts MUST only be specified once.
The FREQ rule part identifies the type of recurrence rule. This The FREQ rule part identifies the type of recurrence rule. This
rule part MUST be specified in the recurrence rule. Valid values rule part MUST be specified in the recurrence rule. Valid values
include SECONDLY, to specify repeating events based on an interval include SECONDLY, to specify repeating events based on an interval
of a second or more; MINUTELY, to specify repeating events based of a second or more; MINUTELY, to specify repeating events based
skipping to change at page 40, line 36 skipping to change at page 41, line 18
MINUTELY rule, every hour for an HOURLY rule, every day for a MINUTELY rule, every hour for an HOURLY rule, every day for a
DAILY rule, every week for a WEEKLY rule, every month for a DAILY rule, every week for a WEEKLY rule, every month for a
MONTHLY rule and every year for a YEARLY rule. MONTHLY rule and every year for a YEARLY rule.
The UNTIL rule part defines a date-time value which bounds the The UNTIL rule part defines a date-time value which bounds the
recurrence rule in an inclusive manner. If the value specified by recurrence rule in an inclusive manner. If the value specified by
UNTIL is synchronized with the specified recurrence, this date or UNTIL is synchronized with the specified recurrence, this date or
date-time becomes the last instance of the recurrence. If date-time becomes the last instance of the recurrence. If
specified as a date-time value, then it MUST be specified in a UTC specified as a date-time value, then it MUST be specified in a UTC
time format. If not present, and the COUNT rule part is also not time format. If not present, and the COUNT rule part is also not
present, the RRULE is considered to repeat forever. present, the "RRULE" is considered to repeat forever.
The COUNT rule part defines the number of occurrences at which to The COUNT rule part defines the number of occurrences at which to
range-bound the recurrence. The "DTSTART" property value always range-bound the recurrence. The "DTSTART" property value always
counts as the first occurrence. counts as the first occurrence.
The BYSECOND rule part specifies a COMMA character (US-ASCII The BYSECOND rule part specifies a COMMA character (US-ASCII
decimal 44) separated list of seconds within a minute. Valid decimal 44) separated list of seconds within a minute. Valid
values are 0 to 59. The BYMINUTE rule part specifies a COMMA values are 0 to 60. The BYMINUTE rule part specifies a COMMA
character (US-ASCII decimal 44) separated list of minutes within character (US-ASCII decimal 44) separated list of minutes within
an hour. Valid values are 0 to 59. The BYHOUR rule part an hour. Valid values are 0 to 59. The BYHOUR rule part
specifies a COMMA character (US-ASCII decimal 44) separated list specifies a COMMA character (US-ASCII decimal 44) separated list
of hours of the day. Valid values are 0 to 23. of hours of the day. Valid values are 0 to 23. The BYSECOND,
BYMINUTE and BYHOUR rule parts MUST NOT be specified when the
associated "DTSTART" property has a DATE value type. These rule
parts MUST be ignored in RECUR value that violate the above
requirement (e.g., generated by applications that pre-date this
revision of iCalendar).
The BYDAY rule part specifies a COMMA character (US-ASCII decimal The BYDAY rule part specifies a COMMA character (US-ASCII decimal
44) separated list of days of the week; MO indicates Monday; TU 44) separated list of days of the week; SU indicates Sunday; MO
indicates Tuesday; WE indicates Wednesday; TH indicates Thursday; indicates Monday; TU indicates Tuesday; WE indicates Wednesday; TH
FR indicates Friday; SA indicates Saturday; SU indicates Sunday. indicates Thursday; FR indicates Friday; SA indicates Saturday.
Each BYDAY value can also be preceded by a positive (+n) or Each BYDAY value can also be preceded by a positive (+n) or
negative (-n) integer. If present, this indicates the nth negative (-n) integer. If present, this indicates the nth
occurrence of the specific day within the MONTHLY or YEARLY RRULE. occurrence of the specific day within the MONTHLY or YEARLY
For example, within a MONTHLY rule, +1MO (or simply 1MO) "RRULE". For example, within a MONTHLY rule, +1MO (or simply 1MO)
represents the first Monday within the month, whereas -1MO represents the first Monday within the month, whereas -1MO
represents the last Monday of the month. If an integer modifier represents the last Monday of the month. If an integer modifier
is not present, it means all days of this type within the is not present, it means all days of this type within the
specified frequency. For example, within a MONTHLY rule, MO specified frequency. For example, within a MONTHLY rule, MO
represents all Mondays within the month. represents all Mondays within the month.
The BYMONTHDAY rule part specifies a COMMA character (US-ASCII The BYMONTHDAY rule part specifies a COMMA character (US-ASCII
decimal 44) separated list of days of the month. Valid values are decimal 44) separated list of days of the month. Valid values are
1 to 31 or -31 to -1. For example, -10 represents the tenth to 1 to 31 or -31 to -1. For example, -10 represents the tenth to
the last day of the month. the last day of the month.
skipping to change at page 42, line 7 skipping to change at page 42, line 37
Note: Assuming a Monday week start, week 53 can only occur when Note: Assuming a Monday week start, week 53 can only occur when
Thursday is January 1 or if it is a leap year and Wednesday is Thursday is January 1 or if it is a leap year and Wednesday is
January 1. January 1.
The BYMONTH rule part specifies a COMMA character (US-ASCII The BYMONTH rule part specifies a COMMA character (US-ASCII
decimal 44) separated list of months of the year. Valid values decimal 44) separated list of months of the year. Valid values
are 1 to 12. are 1 to 12.
The WKST rule part specifies the day on which the workweek starts. The WKST rule part specifies the day on which the workweek starts.
Valid values are MO, TU, WE, TH, FR, SA and SU. This is Valid values are MO, TU, WE, TH, FR, SA and SU. This is
significant when a WEEKLY RRULE has an interval greater than 1, significant when a WEEKLY "RRULE" has an interval greater than 1,
and a BYDAY rule part is specified. This is also significant when and a BYDAY rule part is specified. This is also significant when
in a YEARLY RRULE when a BYWEEKNO rule part is specified. The in a YEARLY "RRULE" when a BYWEEKNO rule part is specified. The
default value is MO. default value is MO.
The BYSETPOS rule part specifies a COMMA character (US-ASCII The BYSETPOS rule part specifies a COMMA character (US-ASCII
decimal 44) separated list of values which corresponds to the nth decimal 44) separated list of values which corresponds to the nth
occurrence within the set of events specified by the rule. Valid occurrence within the set of events specified by the rule. Valid
values are 1 to 366 or -366 to -1. It MUST only be used in values are 1 to 366 or -366 to -1. It MUST only be used in
conjunction with another BYxxx rule part. For example "the last conjunction with another BYxxx rule part. For example "the last
work day of the month" could be represented as: work day of the month" could be represented as:
RRULE:FREQ=MONTHLY;BYDAY=MO,TU,WE,TH,FR;BYSETPOS=-1 FREQ=MONTHLY;BYDAY=MO,TU,WE,TH,FR;BYSETPOS=-1
Each BYSETPOS value can include a positive (+n) or negative (-n) Each BYSETPOS value can include a positive (+n) or negative (-n)
integer. If present, this indicates the nth occurrence of the integer. If present, this indicates the nth occurrence of the
specific occurrence within the set of occurences specified by the specific occurrence within the set of occurences specified by the
rule. rule.
If BYxxx rule part values are found which are beyond the available Recurrence rules may generate recurrence instances with invalid
scope (ie, BYMONTHDAY=30 in February), they are simply ignored. date (e.g., February 30) or nonexistent local time (e.g., 1:30 AM
on a day where the local time is moved forward by an hour at 1:00
AM). Such recurrence instances MUST be ignored and MUST NOT be
counted as part of the recurrence set.
Information, not contained in the rule, necessary to determine the Information, not contained in the rule, necessary to determine the
various recurrence instance start time and dates are derived from various recurrence instance start time and dates are derived from
the Start Time (DTSTART) entry attribute. For example, the Start Time ("DTSTART") component attribute. For example,
"FREQ=YEARLY;BYMONTH=1" doesn't specify a specific day within the "FREQ=YEARLY;BYMONTH=1" doesn't specify a specific day within the
month or a time. This information would be the same as what is month or a time. This information would be the same as what is
specified for DTSTART. specified for "DTSTART".
BYxxx rule parts modify the recurrence in some manner. BYxxx rule BYxxx rule parts modify the recurrence in some manner. BYxxx rule
parts for a period of time which is the same or greater than the parts for a period of time which is the same or greater than the
frequency generally reduce or limit the number of occurrences of frequency generally reduce or limit the number of occurrences of
the recurrence generated. For example, "FREQ=DAILY;BYMONTH=1" the recurrence generated. For example, "FREQ=DAILY;BYMONTH=1"
reduces the number of recurrence instances from all days (if reduces the number of recurrence instances from all days (if
BYMONTH rule part is not present) to all days in January. BYxxx BYMONTH rule part is not present) to all days in January. BYxxx
rule parts for a period of time less than the frequency generally rule parts for a period of time less than the frequency generally
increase or expand the number of occurrences of the recurrence. increase or expand the number of occurrences of the recurrence.
For example, "FREQ=YEARLY;BYMONTH=1,2" increases the number of For example, "FREQ=YEARLY;BYMONTH=1,2" increases the number of
skipping to change at page 43, line 20 skipping to change at page 44, line 5
BYMINUTE=30 BYMINUTE=30
First, the "INTERVAL=2" would be applied to "FREQ=YEARLY" to First, the "INTERVAL=2" would be applied to "FREQ=YEARLY" to
arrive at "every other year". Then, "BYMONTH=1" would be applied arrive at "every other year". Then, "BYMONTH=1" would be applied
to arrive at "every January, every other year". Then, "BYDAY=SU" to arrive at "every January, every other year". Then, "BYDAY=SU"
would be applied to arrive at "every Sunday in January, every would be applied to arrive at "every Sunday in January, every
other year". Then, "BYHOUR=8,9" would be applied to arrive at other year". Then, "BYHOUR=8,9" would be applied to arrive at
"every Sunday in January at 8 AM and 9 AM, every other year". "every Sunday in January at 8 AM and 9 AM, every other year".
Then, "BYMINUTE=30" would be applied to arrive at "every Sunday in Then, "BYMINUTE=30" would be applied to arrive at "every Sunday in
January at 8:30 AM and 9:30 AM, every other year". Then, lacking January at 8:30 AM and 9:30 AM, every other year". Then, lacking
information from RRULE, the second is derived from DTSTART, to end information from "RRULE", the second is derived from "DTSTART", to
up in "every Sunday in January at 8:30:00 AM and 9:30:00 AM, every end up in "every Sunday in January at 8:30:00 AM and 9:30:00 AM,
other year". Similarly, if the BYMINUTE, BYHOUR, BYDAY, every other year". Similarly, if the BYMINUTE, BYHOUR, BYDAY,
BYMONTHDAY or BYMONTH rule part were missing, the appropriate BYMONTHDAY or BYMONTH rule part were missing, the appropriate
minute, hour, day or month would have been retrieved from the minute, hour, day or month would have been retrieved from the
"DTSTART" property. "DTSTART" property.
No additional content value encoding (i.e., BACKSLASH character No additional content value encoding (i.e., BACKSLASH character
encoding) is defined for this value type. encoding) is defined for this value type.
Example: The following is a rule which specifies 10 occurences which Example: The following is a rule which specifies 10 occurences which
occur every other day: occur every other day:
FREQ=DAILY;COUNT=10;INTERVAL=2 FREQ=DAILY;COUNT=10;INTERVAL=2
There are other examples specified in the "RRULE" specification. There are other examples specified in Section 3.8.5.3.
3.3.11. Text 3.3.11. Text
Value Name: TEXT Value Name: TEXT
Purpose: This value type is used to identify values that contain Purpose: This value type is used to identify values that contain
human readable text. human readable text.
Format Definition: The value type is defined by the following Format Definition: This value type is defined by the following
notation. notation.
text = *(TSAFE-CHAR / ":" / DQUOTE / ESCAPED-CHAR) text = *(TSAFE-CHAR / ":" / DQUOTE / ESCAPED-CHAR)
; Folded according to description above ; Folded according to description above
ESCAPED-CHAR = ("\\" / "\;" / "\," / "\N" / "\n") ESCAPED-CHAR = ("\\" / "\;" / "\," / "\N" / "\n")
; \\ encodes \, \N or \n encodes newline ; \\ encodes \, \N or \n encodes newline
; \; encodes ;, \, encodes , ; \; encodes ;, \, encodes ,
TSAFE-CHAR = %x20-21 / %x23-2B / %x2D-39 / %x3C-5B / TSAFE-CHAR = %x20-21 / %x23-2B / %x2D-39 / %x3C-5B /
%x5D-7E / NON-US-ASCII %x5D-7E / NON-US-ASCII
; Any character except CTLs not needed by the current ; Any character except CTLs not needed by the current
; character set, DQUOTE, ";", ":", "\", "," ; character set, DQUOTE, ";", ":", "\", ","
Note: Certain other character sets may require modification of Note: Certain other character sets may require modification of
the above definitions, but this is beyond the scope of this the above definitions, but this is beyond the scope of this
document. document.
Description: If the property permits, multiple "text" values are Description: If the property permits, multiple TEXT values are
specified by a COMMA character (US-ASCII decimal 44) separated specified by a COMMA character (US-ASCII decimal 44) separated
list of values. list of values.
The language in which the text is represented can be controlled by The language in which the text is represented can be controlled by
the "LANGUAGE" property parameter. the "LANGUAGE" property parameter.
An intentional formatted text line break MUST only be included in An intentional formatted text line break MUST only be included in
a "TEXT" property value by representing the line break with the a "TEXT" property value by representing the line break with the
character sequence of BACKSLASH (US-ASCII decimal 92), followed by character sequence of BACKSLASH (US-ASCII decimal 92), followed by
a LATIN SMALL LETTER N (US-ASCII decimal 110) or a LATIN CAPITAL a LATIN SMALL LETTER N (US-ASCII decimal 110) or a LATIN CAPITAL
skipping to change at page 45, line 16 skipping to change at page 45, line 49
Project XYZ Final Review\nConference Room - 3B\nCome Prepared. Project XYZ Final Review\nConference Room - 3B\nCome Prepared.
3.3.12. Time 3.3.12. Time
Value Name: TIME Value Name: TIME
Purpose: This value type is used to identify values that contain a Purpose: This value type is used to identify values that contain a
time of day. time of day.
Format Definition: The data type is defined by the following Format Definition: This value type is defined by the following
notation: notation:
time = time-hour time-minute time-second [time-utc] time = time-hour time-minute time-second [time-utc]
time-hour = 2DIGIT ;00-23 time-hour = 2DIGIT ;00-23
time-minute = 2DIGIT ;00-59 time-minute = 2DIGIT ;00-59
time-second = 2DIGIT ;00-60 time-second = 2DIGIT ;00-60
;The "60" value is used to account for "leap" seconds. ;The "60" value is used to account for positive "leap" seconds.
time-utc = "Z" time-utc = "Z"
Description: If the property permits, multiple "time" values are Description: If the property permits, multiple "time" values are
specified by a COMMA character (US-ASCII decimal 44) separated specified by a COMMA character (US-ASCII decimal 44) separated
list of values. No additional content value encoding (i.e., list of values. No additional content value encoding (i.e.,
BACKSLASH character encoding) is defined for this value type. BACKSLASH character encoding) is defined for this value type.
The "TIME" data type is used to identify values that contain a The "TIME" value type is used to identify values that contain a
time of day. The format is based on the [ISO.8601.1988] complete time of day. The format is based on the [ISO.8601.1988] complete
representation, basic format for a time of day. The text format representation, basic format for a time of day. The text format
consists of a two-digit 24-hour of the day (i.e., values 0-23), consists of a two-digit 24-hour of the day (i.e., values 00-23),
two- digit minute in the hour (i.e., values 0-59), and two-digit two-digit minute in the hour (i.e., values 00-59), and two-digit
seconds in the minute (i.e., values 0-60). The seconds value of seconds in the minute (i.e., values 00-60). The seconds value of
60 MUST only be used to account for "leap" seconds. Fractions of 60 MUST only be used to account for positive "leap" seconds.
a second are not supported by this format. Fractions of a second are not supported by this format.
In parallel to the "DATE-TIME" definition above, the "TIME" data In parallel to the "DATE-TIME" definition above, the "TIME" value
type expresses time values in three forms: type expresses time values in three forms:
The form of time with UTC offset MUST NOT be used. For example, The form of time with UTC offset MUST NOT be used. For example,
the following is NOT VALID for a time value: the following is not valid for a time value:
230000-0800 ;Invalid time format 230000-0800 ;Invalid time format
FORM #1 LOCAL TIME FORM #1 LOCAL TIME
The local time form is simply a time value that does not contain The local time form is simply a time value that does not contain
the UTC designator nor does it reference a time zone. For the UTC designator nor does it reference a time zone. For
example, 11:00 PM: example, 11:00 PM:
230000 230000
Time values of this type are said to be "floating" and are not Time values of this type are said to be "floating" and are not
bound to any time zone in particular. They are used to represent bound to any time zone in particular. They are used to represent
skipping to change at page 46, line 21 skipping to change at page 47, line 8
Time values of this type are said to be "floating" and are not Time values of this type are said to be "floating" and are not
bound to any time zone in particular. They are used to represent bound to any time zone in particular. They are used to represent
the same hour, minute, and second value regardless of which time the same hour, minute, and second value regardless of which time
zone is currently being observed. For example, an event can be zone is currently being observed. For example, an event can be
defined that indicates that an individual will be busy from 11:00 defined that indicates that an individual will be busy from 11:00
AM to 1:00 PM every day, no matter which time zone the person is AM to 1:00 PM every day, no matter which time zone the person is
in. In these cases, a local time can be specified. The recipient in. In these cases, a local time can be specified. The recipient
of an iCalendar object with a property value consisting of a local of an iCalendar object with a property value consisting of a local
time, without any relative time zone information, SHOULD interpret time, without any relative time zone information, SHOULD interpret
the value as being fixed to whatever time zone the ATTENDEE is in the value as being fixed to whatever time zone the "ATTENDEE" is
at any given moment. This means that two ATTENDEEs may in at any given moment. This means that two "Attendees", may
participate in the same event at different UTC times; floating participate in the same event at different UTC times; floating
time SHOULD only be used where that is reasonable behavior. time SHOULD only be used where that is reasonable behavior.
In most cases, a fixed time is desired. To properly communicate a In most cases, a fixed time is desired. To properly communicate a
fixed time in a property value, either UTC time or local time with fixed time in a property value, either UTC time or local time with
time zone reference MUST be specified. time zone reference MUST be specified.
The use of local time in a TIME value without the TZID property The use of local time in a TIME value without the "TZID" property
parameter is to be interpreted as a local time value, regardless parameter is to be interpreted as a local time value, regardless
of the existence of "VTIMEZONE" calendar components in the of the existence of "VTIMEZONE" calendar components in the
iCalendar object. iCalendar object.
FORM #2: UTC TIME FORM #2: UTC TIME
UTC time, or absolute time, is identified by a LATIN CAPITAL UTC time, or absolute time, is identified by a LATIN CAPITAL
LETTER Z suffix character (US-ASCII decimal 90), the UTC LETTER Z suffix character (US-ASCII decimal 90), the UTC
designator, appended to the time value. For example, the designator, appended to the time value. For example, the
following represents 07:00 AM UTC: following represents 07:00 AM UTC:
070000Z 070000Z
The TZID property parameter MUST NOT be applied to TIME properties
whose time values are specified in UTC. The "TZID" property parameter MUST NOT be applied to TIME
properties whose time values are specified in UTC.
FORM #3: LOCAL TIME AND TIME ZONE REFERENCE FORM #3: LOCAL TIME AND TIME ZONE REFERENCE
The local time with reference to time zone information form is The local time with reference to time zone information form is
identified by the use the TZID property parameter to reference the identified by the use the "TZID" property parameter to reference
appropriate time zone definition. TZID is discussed in detail in the appropriate time zone definition. "TZID" is discussed in
Section 3.2.19 . detail in Section 3.2.18 .
Example: The following represents 8:30 AM in New York in Winter, five
hours behind UTC, in each of the three formats using the "X-ABC-
TIMEOFDAY" non-standard property:
X-ABC-TIMEOFDAY:083000 Example: The following represents 8:30 AM in New York in Winter,
five hours behind UTC, in each of the three formats :
X-ABC-TIMEOFDAY:133000Z 083000
133000Z
X-ABC-TIMEOFDAY;TZID=US-Eastern:083000 TZID=US-Eastern:083000
3.3.13. URI 3.3.13. URI
Value Name: URI Value Name: URI
Purpose: This value type is used to identify values that contain a Purpose: This value type is used to identify values that contain a
uniform resource identifier (URI) type of reference to the uniform resource identifier (URI) type of reference to the
property value. property value.
Format Definition: The data type is defined by the following Format Definition: This value type is defined by the following
notation: notation:
uri = <As defined by any IETF RFC> uri = URI ; As defined in
[RFC3986]
Description: This data type might be used to reference binary uri = URI ; As defined in
Description: This value type might be used to reference binary
information, for values that are large, or otherwise undesirable information, for values that are large, or otherwise undesirable
to include directly in the iCalendar object. to include directly in the iCalendar object.
The URI value formats in RFC 1738, RFC 2111 and any other IETF The URI value formats in [RFC3986], [RFC-XXXX] and any other IETF
registered value format can be specified. registered value format can be specified.
Any IANA registered URI format can be used. These include, but Any IANA registered URI format can be used. These include, but
are not limited to, those defined in RFC 1738 and RFC 2111. are not limited to, those defined in [RFC3986] and [RFC-XXXX].
When a property parameter value is a URI value type, the URI MUST When a property parameter value is a URI value type, the URI MUST
be specified as a quoted-string value. be specified as a quoted-string value.
No additional content value encoding (i.e., BACKSLASH character No additional content value encoding (i.e., BACKSLASH character
encoding) is defined for this value type. encoding) is defined for this value type.
Example: The following is a URI for a network file: Example: The following is a URI for a network file:
http://example.com/my-report.txt http://example.com/my-report.txt
3.3.14. UTC Offset 3.3.14. UTC Offset
Value Name: UTC-OFFSET Value Name: UTC-OFFSET
Purpose: This value type is used to identify properties that contain Purpose: This value type is used to identify properties that contain
an offset from UTC to local time. an offset from UTC to local time.
Format Definition: The data type is defined by the following Format Definition: This value type is defined by the following
notation: notation:
utc-offset = time-numzone ;As defined above in time data type utc-offset = time-numzone
time-numzone = ("+" / "-") time-hour time-minute [time-second] time-numzone = ("+" / "-") time-hour time-minute [time-second]
Description: The PLUS SIGN (US-ASCII decimal 43) character MUST be Description: The PLUS SIGN (US-ASCII decimal 43) character MUST be
specified for positive UTC offsets (i.e., ahead of UTC). The specified for positive UTC offsets (i.e., ahead of UTC). The
HYPHEN-MINUS character (US-ASCII decimal 45) MUST be specified for HYPHEN-MINUS character (US-ASCII decimal 45) MUST be specified for
negative UTC offsets (i.e., behind of UTC). The value of "-0000" negative UTC offsets (i.e., behind of UTC). The value of "-0000"
and "-000000" are not allowed. The time-second, if present, may and "-000000" are not allowed. The time-second, if present, MUST
not be 60; if absent, it defaults to zero. NOT be 60; if absent, it defaults to zero.
No additional content value encoding (i.e., BACKSLASH character No additional content value encoding (i.e., BACKSLASH character
encoding) is defined for this value type. encoding) is defined for this value type.
Example: The following UTC offsets are given for standard time for Example: The following UTC offsets are given for standard time for
New York (five hours behind UTC) and Geneva (one hour ahead of New York (five hours behind UTC) and Geneva (one hour ahead of
UTC): UTC):
-0500 -0500
+0100 +0100
3.4. iCalendar Object 3.4. iCalendar Object
The Calendaring and Scheduling Core Object is a collection of The Calendaring and Scheduling Core Object is a collection of
calendaring and scheduling information. Typically, this information calendaring and scheduling information. Typically, this information
will consist of a single iCalendar object. However, multiple will consist of an iCalendar stream with a single iCalendar object.
iCalendar objects can be sequentially grouped together. The first However, multiple iCalendar objects can be sequentially grouped
line and last line of the iCalendar object MUST contain a pair of together in an iCalendar stream. The first line and last line of the
iCalendar object delimiter strings. The syntax for an iCalendar iCalendar object MUST contain a pair of iCalendar object delimiter
object is as follows: strings. The syntax for an iCalendar stream is as follows:
icalobject = 1*("BEGIN" ":" "VCALENDAR" CRLF icalstream = 1*icalobject
icalobject = "BEGIN" ":" "VCALENDAR" CRLF
icalbody icalbody
"END" ":" "VCALENDAR" CRLF) "END" ":" "VCALENDAR" CRLF
The following is a simple example of an iCalendar object: The following is a simple example of an iCalendar object:
BEGIN:VCALENDAR BEGIN:VCALENDAR
VERSION:2.0 VERSION:2.0
PRODID:-//hacksw/handcal//NONSGML v1.0//EN PRODID:-//hacksw/handcal//NONSGML v1.0//EN
BEGIN:VEVENT BEGIN:VEVENT
UID:19970610T172345Z-AF23B2@example.com UID:19970610T172345Z-AF23B2@example.com
DTSTAMP:19970610T172345Z DTSTAMP:19970610T172345Z
DTSTART:19970714T170000Z DTSTART:19970714T170000Z
skipping to change at page 50, line 14 skipping to change at page 51, line 14
icalbody = calprops component icalbody = calprops component
calprops = 2*( calprops = 2*(
; 'prodid' and 'version' are both REQUIRED, ; 'prodid' and 'version' are both REQUIRED,
; but MUST NOT occur more than once ; but MUST NOT occur more than once
prodid / version / prodid / version /
; 'calscale' and 'method' are optional, ; 'calscale' and 'method' are OPTIONAL,
; but MUST NOT occur more than once ; but MUST NOT occur more than once
calscale / calscale /
method / method /
; 'x-prop' is OPTIONAL, ; 'x-prop' is OPTIONAL,
; and MAY occur more than once ; and MAY occur more than once
x-prop x-prop
) )
skipping to change at page 51, line 16 skipping to change at page 52, line 16
Purpose: Provide a grouping of component properties that describe an Purpose: Provide a grouping of component properties that describe an
event. event.
Format Definition: A "VEVENT" calendar component is defined by the Format Definition: A "VEVENT" calendar component is defined by the
following notation: following notation:
eventc = "BEGIN" ":" "VEVENT" CRLF eventc = "BEGIN" ":" "VEVENT" CRLF
eventprop *alarmc eventprop *alarmc
"END" ":" "VEVENT" CRLF "END" ":" "VEVENT" CRLF
eventprop = 3*( eventprop = *(
; the following are REQUIRED, ; the following are REQUIRED,
; but MUST NOT occur more than once ; but MUST NOT occur more than once
dtstamp / dtstart / uid / dtstamp / dtstart / uid /
; the following are optional, ; the following are OPTIONAL,
; but MUST NOT occur more than once ; but MUST NOT occur more than once
class / created / description / geo / class / created / description / geo /
last-mod / location / organizer / priority / last-mod / location / organizer / priority /
seq / status / summary / transp / seq / status / summary / transp /
url / recurid / url / recurid /
; the following is OPTIONAL, ; the following is OPTIONAL,
; but SHOULD NOT occur more than once ; but SHOULD NOT occur more than once
rrule / rrule /
; either 'dtend' or 'duration' may appear in ; either 'dtend' or 'duration' MAY appear in
; a 'eventprop', but 'dtend' and 'duration' ; a 'eventprop', but 'dtend' and 'duration'
; MUST NOT occur in the same 'eventprop' ; MUST NOT occur in the same 'eventprop'
dtend / duration / dtend / duration /
; the following are optional, ; the following are OPTIONAL,
; and MAY occur more than once ; and MAY occur more than once
attach / attendee / categories / comment / attach / attendee / categories / comment /
contact / exdate / rstatus / related / contact / exdate / rstatus / related /
resources / rdate / x-prop resources / rdate / x-prop
) )
Description: A "VEVENT" calendar component is a grouping of component Description: A "VEVENT" calendar component is a grouping of
properties, and possibly including "VALARM" calendar components, component properties, and possibly including "VALARM" calendar
that represents a scheduled amount of time on a calendar. For components, that represents a scheduled amount of time on a
example, it can be an activity; such as a one-hour long, calendar. For example, it can be an activity; such as a one-hour
department meeting from 8:00 AM to 9:00 AM, tomorrow. Generally, long, department meeting from 8:00 AM to 9:00 AM, tomorrow.
an event will take up time on an individual calendar. Hence, the Generally, an event will take up time on an individual calendar.
event will appear as an opaque interval in a search for busy time. Hence, the event will appear as an opaque interval in a search for
Alternately, the event can have its Time Transparency set to busy time. Alternately, the event can have its Time Transparency
"TRANSPARENT" in order to prevent blocking of the event in set to "TRANSPARENT" in order to prevent blocking of the event in
searches for busy time. searches for busy time.
The "VEVENT" is also the calendar component used to specify an The "VEVENT" is also the calendar component used to specify an
anniversary or daily reminder within a calendar. These events anniversary or daily reminder within a calendar. These events
have a DATE value type for the "DTSTART" property instead of the have a DATE value type for the "DTSTART" property instead of the
default data type of DATE-TIME. If such a "VEVENT" has a "DTEND" default value type of DATE-TIME. If such a "VEVENT" has a "DTEND"
property, it MUST be specified as a DATE value also. The property, it MUST be specified as a DATE value also. The
anniversary type of "VEVENT" can span more than one date (i.e, anniversary type of "VEVENT" can span more than one date (i.e,
"DTEND" property value is set to a calendar date after the "DTEND" property value is set to a calendar date after the
"DTSTART" property value). "DTSTART" property value). If such a "VEVENT" has a "DURATION"
property, it MUST be specified as a "dur-day" or "dur-week" value.
The "DTSTART" property for a "VEVENT" specifies the inclusive The "DTSTART" property for a "VEVENT" specifies the inclusive
start of the event. For recurring events, it also specifies the start of the event. For recurring events, it also specifies the
very first instance in the recurrence set. The "DTEND" property very first instance in the recurrence set. The "DTEND" property
for a "VEVENT" calendar component specifies the non-inclusive end for a "VEVENT" calendar component specifies the non-inclusive end
of the event. For cases where a "VEVENT" calendar component of the event. For cases where a "VEVENT" calendar component
specifies a "DTSTART" property with a DATE data type but no specifies a "DTSTART" property with a DATE value type but no
"DTEND" property, the events non-inclusive end is the end of the "DTEND" nor DURATION property, the event's duration is taken to be
calendar date specified by the "DTSTART" property. For cases one day. For cases where a "VEVENT" calendar component specifies
where a "VEVENT" calendar component specifies a "DTSTART" property a "DTSTART" property with a DATE-TIME value type but no "DTEND"
with a DATE-TIME data type but no "DTEND" property, the event ends property, the event ends on the same calendar date and time of day
on the same calendar date and time of day specified by the specified by the "DTSTART" property.
"DTSTART" property.
The "VEVENT" calendar component cannot be nested within another The "VEVENT" calendar component cannot be nested within another
calendar component. However, "VEVENT" calendar components can be calendar component. However, "VEVENT" calendar components can be
related to each other or to a "VTODO" or to a "VJOURNAL" calendar related to each other or to a "VTODO" or to a "VJOURNAL" calendar
component with the "RELATED-TO" property. component with the "RELATED-TO" property.
Example: The following is an example of the "VEVENT" calendar Example: The following is an example of the "VEVENT" calendar
component used to represent a meeting that will also be opaque to component used to represent a meeting that will also be opaque to
searches for busy time: searches for busy time:
skipping to change at page 54, line 14 skipping to change at page 55, line 14
Purpose: Provide a grouping of calendar properties that describe a Purpose: Provide a grouping of calendar properties that describe a
to-do. to-do.
Format Definition: A "VTODO" calendar component is defined by the Format Definition: A "VTODO" calendar component is defined by the
following notation: following notation:
todoc = "BEGIN" ":" "VTODO" CRLF todoc = "BEGIN" ":" "VTODO" CRLF
todoprop *alarmc todoprop *alarmc
"END" ":" "VTODO" CRLF "END" ":" "VTODO" CRLF
todoprop = 2*( todoprop = *(
; the following are REQUIRED, ; the following are REQUIRED,
; but MUST NOT occur more than once ; but MUST NOT occur more than once
dtstamp / uid / dtstamp / uid /
; the following are optional, ; the following are OPTIONAL,
; but MUST NOT occur more than once ; but MUST NOT occur more than once
class / completed / created / description / class / completed / created / description /
dtstart / geo / last-mod / location / organizer / dtstart / geo / last-mod / location / organizer /
percent / priority / recurid / seq / status / percent / priority / recurid / seq / status /
summary / url / summary / url /
; the following is OPTIONAL, ; the following is OPTIONAL,
; but SHOULD NOT occur more than once ; but SHOULD NOT occur more than once
rrule / rrule /
; either 'due' or 'duration' may appear in ; either 'due' or 'duration' MAY appear in
; a 'todoprop', but 'due' and 'duration' ; a 'todoprop', but 'due' and 'duration'
; MUST NOT occur in the same 'todoprop' ; MUST NOT occur in the same 'todoprop'
due / duration / due / duration /
; the following are optional, ; the following are OPTIONAL,
; and MAY occur more than once ; and MAY occur more than once
attach / attendee / categories / comment / contact / attach / attendee / categories / comment / contact /
exdate / rstatus / related / resources / exdate / rstatus / related / resources /
rdate / x-prop rdate / x-prop
) )
Description: A "VTODO" calendar component is a grouping of component Description: A "VTODO" calendar component is a grouping of component
properties and possibly "VALARM" calendar components that properties and possibly "VALARM" calendar components that
represent an action-item or assignment. For example, it can be represent an action-item or assignment. For example, it can be
skipping to change at page 55, line 19 skipping to change at page 56, line 19
The "VTODO" calendar component cannot be nested within another The "VTODO" calendar component cannot be nested within another
calendar component. However, "VTODO" calendar components can be calendar component. However, "VTODO" calendar components can be
related to each other or to a "VEVENT" or to a "VJOURNAL" calendar related to each other or to a "VEVENT" or to a "VJOURNAL" calendar
component with the "RELATED-TO" property. component with the "RELATED-TO" property.
A "VTODO" calendar component without the "DTSTART" and "DUE" (or A "VTODO" calendar component without the "DTSTART" and "DUE" (or
"DURATION") properties specifies a to-do that will be associated "DURATION") properties specifies a to-do that will be associated
with each successive calendar date, until it is completed. with each successive calendar date, until it is completed.
Example: The following is an example of a "VTODO" calendar component: Example: The following is an example of a "VTODO" calendar
component:
BEGIN:VTODO BEGIN:VTODO
UID:19970901T130000Z-123404@example.com UID:19970901T130000Z-123404@example.com
DTSTAMP:19970901T130000Z DTSTAMP:19970901T130000Z
DTSTART:19970415T133000Z DTSTART:19970415T133000Z
DUE:19970416T045959Z DUE:19970416T045959Z
SUMMARY:1996 Income Tax Preparation SUMMARY:1996 Income Tax Preparation
CLASS:CONFIDENTIAL CLASS:CONFIDENTIAL
CATEGORIES:FAMILY,FINANCE CATEGORIES:FAMILY,FINANCE
PRIORITY:1 PRIORITY:1
skipping to change at page 56, line 9 skipping to change at page 57, line 9
Purpose: Provide a grouping of component properties that describe a Purpose: Provide a grouping of component properties that describe a
journal entry. journal entry.
Format Definition: A "VJOURNAL" calendar component is defined by the Format Definition: A "VJOURNAL" calendar component is defined by the
following notation: following notation:
journalc = "BEGIN" ":" "VJOURNAL" CRLF journalc = "BEGIN" ":" "VJOURNAL" CRLF
jourprop jourprop
"END" ":" "VJOURNAL" CRLF "END" ":" "VJOURNAL" CRLF
jourprop = 1*( jourprop = *(
; the following are REQUIRED, ; the following are REQUIRED,
; but MUST NOT occur more than once ; but MUST NOT occur more than once
dtstamp / uid / dtstamp / uid /
; the following are optional, ; the following are OPTIONAL,
; but MUST NOT occur more than once ; but MUST NOT occur more than once
class / created / description / dtstart / class / created / dtstart /
last-mod / organizer / recurid / seq / last-mod / organizer / recurid / seq /
status / summary / url / status / summary / url /
; the following is OPTIONAL, ; the following is OPTIONAL,
; but SHOULD NOT occur more than once ; but SHOULD NOT occur more than once
rrule / rrule /
; the following are optional, ; the following are OPTIONAL,
; and MAY occur more than once ; and MAY occur more than once
attach / attendee / categories / comment / attach / attendee / categories / comment /
contact / exdate / related / rdate / contact / description / exdate / related / rdate /
rstatus / x-prop rstatus / x-prop
) )
Description: A "VJOURNAL" calendar component is a grouping of Description: A "VJOURNAL" calendar component is a grouping of
component properties that represent one or more descriptive text component properties that represent one or more descriptive text
notes associated with a particular calendar date. The "DTSTART" notes associated with a particular calendar date. The "DTSTART"
property is used to specify the calendar date that the journal property is used to specify the calendar date that the journal
entry is associated with. Generally, it will have a DATE value entry is associated with. Generally, it will have a DATE value
data type, but it can also be used to specify a DATE-TIME value data type, but it can also be used to specify a DATE-TIME value
data type. Examples of a journal entry include a daily record of data type. Examples of a journal entry include a daily record of
skipping to change at page 57, line 25 skipping to change at page 58, line 25
DTSTAMP:19970901T130000Z DTSTAMP:19970901T130000Z
DTSTART;VALUE=DATE:19970317 DTSTART;VALUE=DATE:19970317
SUMMARY:Staff meeting minutes SUMMARY:Staff meeting minutes
DESCRIPTION:1. Staff meeting: Participants include Joe\, Lisa DESCRIPTION:1. Staff meeting: Participants include Joe\, Lisa
and Bob. Aurora project plans were reviewed. There is currentl and Bob. Aurora project plans were reviewed. There is currentl
y no budget reserves for this project. Lisa will escalate to y no budget reserves for this project. Lisa will escalate to
management. Next meeting on Tuesday.\n management. Next meeting on Tuesday.\n
2. Telephone Conference: ABC Corp. sales representative called 2. Telephone Conference: ABC Corp. sales representative called
to discuss new printer. Promised to get us a demo by Friday.\n to discuss new printer. Promised to get us a demo by Friday.\n
3. Henry Miller (Handsoff Insurance): Car was totaled by tree. 3. Henry Miller (Handsoff Insurance): Car was totaled by tree.
Is looking into a loaner car. 654-2323 (tel). Is looking into a loaner car. 555-2323 (tel).
END:VJOURNAL END:VJOURNAL
3.6.4. Free/Busy Component 3.6.4. Free/Busy Component
Component Name: VFREEBUSY Component Name: VFREEBUSY
Purpose: Provide a grouping of component properties that describe Purpose: Provide a grouping of component properties that describe
either a request for free/busy time, describe a response to a either a request for free/busy time, describe a response to a
request for free/busy time or describe a published set of busy request for free/busy time or describe a published set of busy
time. time.
Format Definition: A "VFREEBUSY" calendar component is defined by the Format Definition: A "VFREEBUSY" calendar component is defined by
following notation: the following notation:
freebusyc = "BEGIN" ":" "VFREEBUSY" CRLF freebusyc = "BEGIN" ":" "VFREEBUSY" CRLF
fbprop fbprop
"END" ":" "VFREEBUSY" CRLF "END" ":" "VFREEBUSY" CRLF
fbprop = *( fbprop = *(
; the following are optional, ; the following are REQUIRED,
; but MUST NOT occur more than once
dtstamp / uid /
; the following are OPTIONAL,
; but MUST NOT occur more than once ; but MUST NOT occur more than once
contact / dtstart / dtend / duration / dtstamp / contact / dtstart / dtend / duration / dtstamp /
organizer / uid / url / organizer / uid / url /
; the following are optional, ; the following are OPTIONAL,
; and MAY occur more than once ; and MAY occur more than once
attendee / comment / freebusy / rstatus / x-prop attendee / comment / freebusy / rstatus / x-prop
) )
Description: A "VFREEBUSY" calendar component is a grouping of Description: A "VFREEBUSY" calendar component is a grouping of
component properties that represents either a request for, a reply component properties that represents either a request for, a reply
to a request for free or busy time information or a published set to a request for free or busy time information or a published set
of busy time information. of busy time information.
skipping to change at page 59, line 36 skipping to change at page 60, line 44
The recurrence properties ("RRULE", "RDATE", "EXDATE") are not The recurrence properties ("RRULE", "RDATE", "EXDATE") are not
permitted within a "VFREEBUSY" calendar component. Any recurring permitted within a "VFREEBUSY" calendar component. Any recurring
events are resolved into their individual busy time periods using events are resolved into their individual busy time periods using
the "FREEBUSY" property. the "FREEBUSY" property.
Example: The following is an example of a "VFREEBUSY" calendar Example: The following is an example of a "VFREEBUSY" calendar
component used to request free or busy time information: component used to request free or busy time information:
BEGIN:VFREEBUSY BEGIN:VFREEBUSY
ORGANIZER:MAILTO:jane_doe@example.com ORGANIZER:mailto:jane_doe@example.com
ATTENDEE:MAILTO:john_public@example.com ATTENDEE:mailto:john_public@example.com
DTSTART:19971015T050000Z DTSTART:19971015T050000Z
DTEND:19971016T050000Z DTEND:19971016T050000Z
DTSTAMP:19970901T083000Z DTSTAMP:19970901T083000Z
END:VFREEBUSY END:VFREEBUSY
The following is an example of a "VFREEBUSY" calendar component The following is an example of a "VFREEBUSY" calendar component
used to reply to the request with busy time information: used to reply to the request with busy time information:
BEGIN:VFREEBUSY BEGIN:VFREEBUSY
ORGANIZER:MAILTO:jane_doe@example.com ORGANIZER:mailto:jane_doe@example.com
ATTENDEE:MAILTO:john_public@example.com ATTENDEE:mailto:john_public@example.com
DTSTAMP:19970901T100000Z DTSTAMP:19970901T100000Z
FREEBUSY:19971015T050000Z/PT8H30M, FREEBUSY:19971015T050000Z/PT8H30M,
19971015T160000Z/PT5H30M,19971015T223000Z/PT6H30M 19971015T160000Z/PT5H30M,19971015T223000Z/PT6H30M
URL:http://example.com/pub/busy/jpublic-01.ifb URL:http://example.com/pub/busy/jpublic-01.ifb
COMMENT:This iCalendar file contains busy time information for COMMENT:This iCalendar file contains busy time information for
the next three months. the next three months.
END:VFREEBUSY END:VFREEBUSY
The following is an example of a "VFREEBUSY" calendar component The following is an example of a "VFREEBUSY" calendar component
skipping to change at page 60, line 37 skipping to change at page 61, line 39
URL:http://www.example.com/calendar/busytime/jsmith.ifb URL:http://www.example.com/calendar/busytime/jsmith.ifb
END:VFREEBUSY END:VFREEBUSY
3.6.5. Time Zone Component 3.6.5. Time Zone Component
Component Name: VTIMEZONE Component Name: VTIMEZONE
Purpose: Provide a grouping of component properties that defines a Purpose: Provide a grouping of component properties that defines a
time zone. time zone.
Format Definition: A "VTIMEZONE" calendar component is defined by the Format Definition: A "VTIMEZONE" calendar component is defined by
following notation: the following notation:
timezonec = "BEGIN" ":" "VTIMEZONE" CRLF timezonec = "BEGIN" ":" "VTIMEZONE" CRLF
2*( 2*(
; 'tzid' is required, but MUST NOT occur more ; 'tzid' is REQUIRED, but MUST NOT occur more
; than once ; than once
tzid / tzid /
; 'last-mod' and 'tzurl' are optional, ; 'last-mod' and 'tzurl' are OPTIONAL,
; but MUST NOT occur more than once ; but MUST NOT occur more than once
last-mod / tzurl / last-mod / tzurl /
; one of 'standardc' or 'daylightc' MUST occur ; one of 'standardc' or 'daylightc' MUST occur
; and each MAY occur more than once. ; and each MAY occur more than once.
standardc / daylightc / standardc / daylightc /
; the following is optional, ; the following is OPTIONAL,
; and MAY occur more than once ; and MAY occur more than once
x-prop x-prop
) )
"END" ":" "VTIMEZONE" CRLF "END" ":" "VTIMEZONE" CRLF
standardc = "BEGIN" ":" "STANDARD" CRLF standardc = "BEGIN" ":" "STANDARD" CRLF
tzprop tzprop
"END" ":" "STANDARD" CRLF "END" ":" "STANDARD" CRLF
daylightc = "BEGIN" ":" "DAYLIGHT" CRLF daylightc = "BEGIN" ":" "DAYLIGHT" CRLF
tzprop tzprop
"END" ":" "DAYLIGHT" CRLF "END" ":" "DAYLIGHT" CRLF
tzprop = 3*( tzprop = *(
; the following are each REQUIRED, ; the following are each REQUIRED,
; but MUST NOT occur more than once ; but MUST NOT occur more than once
dtstart / tzoffsetto / tzoffsetfrom / dtstart / tzoffsetto / tzoffsetfrom /
; the following is OPTIONAL, ; the following is OPTIONAL,
; but SHOULD NOT occur more than once ; but SHOULD NOT occur more than once
rrule / rrule /
; the following are optional, ; the following are OPTIONAL,
; and MAY occur more than once ; and MAY occur more than once
comment / rdate / tzname / x-prop comment / rdate / tzname / x-prop
) )
Description: A time zone is unambiguously defined by the set of time Description: A time zone is unambiguously defined by the set of time
measurement rules determined by the governing body for a given measurement rules determined by the governing body for a given
geographic area. These rules describe at a minimum the base geographic area. These rules describe at a minimum the base
offset from UTC for the time zone, often referred to as the offset from UTC for the time zone, often referred to as the
skipping to change at page 62, line 27 skipping to change at page 63, line 29
| 1967-* | last Sun in Oct, 02:00 | -0500 | EST | | 1967-* | last Sun in Oct, 02:00 | -0500 | EST |
| 1967-1973 | last Sun in Apr, 02:00 | -0400 | EDT | | 1967-1973 | last Sun in Apr, 02:00 | -0400 | EDT |
| 1974-1974 | Jan 6, 02:00 | -0400 | EDT | | 1974-1974 | Jan 6, 02:00 | -0400 | EDT |
| 1975-1975 | Feb 23, 02:00 | -0400 | EDT | | 1975-1975 | Feb 23, 02:00 | -0400 | EDT |
| 1976-1986 | last Sun in Apr, 02:00 | -0400 | EDT | | 1976-1986 | last Sun in Apr, 02:00 | -0400 | EDT |
| 1987-* | first Sun in Apr, 02:00 | -0400 | EDT | | 1987-* | first Sun in Apr, 02:00 | -0400 | EDT |
+-----------+-------------------------+--------+--------------+ +-----------+-------------------------+--------+--------------+
Note: The specification of a global time zone registry is not Note: The specification of a global time zone registry is not
addressed by this document and is left for future study. addressed by this document and is left for future study.
However, implementers may find the Olson time zone database However, implementers may find the TZ Database [TZDB] a useful
[TZDB] a useful reference. It is an informal, public-domain reference. It is an informal, public-domain collection of time
collection of time zone information, which is currently being zone information, which is currently being maintained by
maintained by volunteer Internet participants, and is used in volunteer Internet participants, and is used in several
several operating systems. This database contains current and operating systems. This database contains current and
historical time zone information for a wide variety of historical time zone information for a wide variety of
locations around the globe; it provides a time zone identifier locations around the globe; it provides a time zone identifier
for every unique time zone rule set in actual use since 1970, for every unique time zone rule set in actual use since 1970,
with historical data going back to the introduction of standard with historical data going back to the introduction of standard
time. time.
Interoperability between two calendaring and scheduling Interoperability between two calendaring and scheduling
applications, especially for recurring events, to-dos or journal applications, especially for recurring events, to-dos or journal
entries, is dependent on the ability to capture and convey date entries, is dependent on the ability to capture and convey date
and time information in an unambiguous format. The specification and time information in an unambiguous format. The specification
skipping to change at page 63, line 7 skipping to change at page 64, line 9
Standard Time and Daylight Saving Time observances (or rules) for Standard Time and Daylight Saving Time observances (or rules) for
a particular time zone for a given interval of time. The a particular time zone for a given interval of time. The
"VTIMEZONE" calendar component cannot be nested within other "VTIMEZONE" calendar component cannot be nested within other
calendar components. Multiple "VTIMEZONE" calendar components can calendar components. Multiple "VTIMEZONE" calendar components can
exist in an iCalendar object. In this situation, each "VTIMEZONE" exist in an iCalendar object. In this situation, each "VTIMEZONE"
MUST represent a unique time zone definition. This is necessary MUST represent a unique time zone definition. This is necessary
for some classes of events, such as airline flights, that start in for some classes of events, such as airline flights, that start in
one time zone and end in another. one time zone and end in another.
The "VTIMEZONE" calendar component MUST be present if the The "VTIMEZONE" calendar component MUST be present if the
iCalendar object contains an RRULE that generates dates on both iCalendar object contains an "RRULE" that generates dates on both
sides of a time zone shift (e.g., both in Standard Time and sides of a time zone shift (e.g., both in Standard Time and
Daylight Saving Time) unless the iCalendar object intends to Daylight Saving Time) unless the iCalendar object intends to
convey a floating time ( see Section 3.3.12 for proper convey a floating time ( see Section 3.3.12 for proper
interpretation of floating time). It can be present if the interpretation of floating time). It can be present if the
iCalendar object does not contain such a RRULE. In addition, if a iCalendar object does not contain such a "RRULE". In addition, if
RRULE is present, there MUST be valid time zone information for a "RRULE" is present, there MUST be valid time zone information
all recurrence instances. for all recurrence instances.
The "VTIMEZONE" calendar component MUST include the "TZID" The "VTIMEZONE" calendar component MUST include the "TZID"
property and at least one definition of a standard or daylight property and at least one definition of a "STANDARD" or "DAYLIGHT"
component. The standard or daylight component MUST include the subcomponent. The "STANDARD" or "DAYLIGHT" subcomponent. MUST
"DTSTART", "TZOFFSETFROM" and "TZOFFSETTO" properties. include the "DTSTART", "TZOFFSETFROM" and "TZOFFSETTO" properties.
An individual "VTIMEZONE" calendar component MUST be specified for An individual "VTIMEZONE" calendar component MUST be specified for
each unique "TZID" parameter value specified in the iCalendar each unique "TZID" parameter value specified in the iCalendar
object. object.
Each "VTIMEZONE" calendar component consists of a collection of Each "VTIMEZONE" calendar component consists of a collection of
one or more sub-components that describe the rule for a particular one or more sub-components that describe the rule for a particular
observance (either a Standard Time or a Daylight Saving Time observance (either a Standard Time or a Daylight Saving Time
observance). The "STANDARD" sub-component consists of a observance). The "STANDARD" sub-component consists of a
collection of properties that describe Standard Time. The collection of properties that describe Standard Time. The
"DAYLIGHT" sub-component consists of a collection of properties "DAYLIGHT" sub-component consists of a collection of properties
that describe Daylight Saving Time. In general this collection of that describe Daylight Saving Time. In general this collection of
properties consists of: properties consists of:
* the first onset date-time for the observance * the first onset date-time for the observance;
* the last onset date-time for the observance, if a last onset is * the last onset date-time for the observance, if a last onset is
known. known;
* the offset to be applied for the observance * the offset to be applied for the observance;
* a rule that describes the day and time when the observance * a rule that describes the day and time when the observance
takes effect takes effect;
* an optional name for the observance * an optional name for the observance.
For a given time zone, there may be multiple unique definitions of For a given time zone, there may be multiple unique definitions of
the observances over a period of time. Each observance is the observances over a period of time. Each observance is
described using either a "STANDARD" or "DAYLIGHT" sub-component. described using either a "STANDARD" or "DAYLIGHT" sub-component.
The collection of these sub-components is used to describe the The collection of these sub-components is used to describe the
time zone for a given period of time. The offset to apply at any time zone for a given period of time. The offset to apply at any
given time is found by locating the observance that has the last given time is found by locating the observance that has the last
onset date and time before the time in question, and using the onset date and time before the time in question, and using the
offset value from that observance. offset value from that observance.
skipping to change at page 64, line 18 skipping to change at page 65, line 25
The mandatory "TZID" property is a text value that uniquely The mandatory "TZID" property is a text value that uniquely
identifies the "VTIMEZONE" calendar component within the scope of identifies the "VTIMEZONE" calendar component within the scope of
an iCalendar object. an iCalendar object.
The optional "LAST-MODIFIED" property is a UTC value that The optional "LAST-MODIFIED" property is a UTC value that
specifies the date and time that this time zone definition was specifies the date and time that this time zone definition was
last updated. last updated.
The optional "TZURL" property is a url value that points to a The optional "TZURL" property is a url value that points to a
published VTIMEZONE definition. TZURL SHOULD refer to a resource published "VTIMEZONE" definition. "TZURL" SHOULD refer to a
that is accessible by anyone who might need to interpret the resource that is accessible by anyone who might need to interpret
object. This SHOULD NOT normally be a "file" URL or other URL the object. This SHOULD NOT normally be a "file" URL or other URL
that is not widely-accessible. that is not widely-accessible.
The collection of properties that are used to define the STANDARD The collection of properties that are used to define the
and DAYLIGHT sub-components include: "STANDARD" and "DAYLIGHT" sub-components include:
The mandatory "DTSTART" property gives the effective onset date The mandatory "DTSTART" property gives the effective onset date
and local time for the time zone sub-component definition. and local time for the time zone sub-component definition.
"DTSTART" in this usage MUST be specified as a local DATE-TIME "DTSTART" in this usage MUST be specified as a local DATE-TIME
value. value.
The mandatory "TZOFFSETFROM" property gives the UTC offset which The mandatory "TZOFFSETFROM" property gives the UTC offset which
is in use when the onset of this time zone observance begins. is in use when the onset of this time zone observance begins.
"TZOFFSETFROM" is combined with "DTSTART" to define the effective "TZOFFSETFROM" is combined with "DTSTART" to define the effective
onset for the time zone sub-component definition. For example, onset for the time zone sub-component definition. For example,
skipping to change at page 65, line 13 skipping to change at page 66, line 18
used for displaying dates. used for displaying dates.
If specified, the onset for the observance defined by the time If specified, the onset for the observance defined by the time
zone sub-component is defined by either the "RRULE" or "RDATE" zone sub-component is defined by either the "RRULE" or "RDATE"
property. If neither is specified, only one sub-component can be property. If neither is specified, only one sub-component can be
specified in the "VTIMEZONE" calendar component and it is assumed specified in the "VTIMEZONE" calendar component and it is assumed
that the single observance specified is always in effect. that the single observance specified is always in effect.
The "RRULE" property defines the recurrence rule for the onset of The "RRULE" property defines the recurrence rule for the onset of
the observance defined by this time zone sub-component. Some the observance defined by this time zone sub-component. Some
specific requirements for the usage of RRULE for this purpose specific requirements for the usage of "RRULE" for this purpose
include: include:
* If observance is known to have an effective end date, the * If observance is known to have an effective end date, the
"UNTIL" recurrence rule parameter MUST be used to specify the "UNTIL" recurrence rule parameter MUST be used to specify the
last valid onset of this observance (i.e., the UNTIL date-time last valid onset of this observance (i.e., the UNTIL date-time
will be equal to the last instance generated by the recurrence will be equal to the last instance generated by the recurrence
pattern). It MUST be specified in UTC time. pattern). It MUST be specified in UTC time.
* The "DTSTART" and the "TZOFFSETTO" properties MUST be used when * The "DTSTART" and the "TZOFFSETTO" properties MUST be used when
generating the onset date-time values (instances) from the generating the onset date-time values (instances) from the
RRULE. "RRULE".
Alternatively, the "RDATE" property can be used to define the Alternatively, the "RDATE" property can be used to define the
onset of the observance by giving the individual onset date and onset of the observance by giving the individual onset date and
times. "RDATE" in this usage MUST be specified as a local DATE- times. "RDATE" in this usage MUST be specified as a local DATE-
TIME value in UTC time. TIME value .
The optional "COMMENT" property is also allowed for descriptive The optional "COMMENT" property is also allowed for descriptive
explanatory text. explanatory text.
Example: The following are examples of the "VTIMEZONE" calendar Example: The following are examples of the "VTIMEZONE" calendar
component: component:
This is an example showing time zone information for the Eastern This is an example showing time zone information for the Eastern
United States using "RDATE" property. Note that this is only United States using "RDATE" property. Note that this is only
suitable for a recurring event that starts on or later than April suitable for a recurring event that starts on or later than April
skipping to change at page 66, line 25 skipping to change at page 67, line 25
BEGIN:DAYLIGHT BEGIN:DAYLIGHT
DTSTART:19970406T020000 DTSTART:19970406T020000
RDATE:19970406T020000 RDATE:19970406T020000
TZOFFSETFROM:-0500 TZOFFSETFROM:-0500
TZOFFSETTO:-0400 TZOFFSETTO:-0400
TZNAME:EDT TZNAME:EDT
END:DAYLIGHT END:DAYLIGHT
END:VTIMEZONE END:VTIMEZONE
This is a simple example showing the current time zone rules for This is a simple example showing the current time zone rules for
the Eastern United States using a RRULE recurrence pattern. Note the Eastern United States using a "RRULE" recurrence pattern.
that there is no effective end date to either of the Standard Time Note that there is no effective end date to either of the Standard
or Daylight Time rules. This information would be valid for a Time or Daylight Time rules. This information would be valid for
recurring event starting today and continuing indefinitely. a recurring event starting today and continuing indefinitely.
BEGIN:VTIMEZONE BEGIN:VTIMEZONE
TZID:US-Eastern TZID:US-Eastern
LAST-MODIFIED:19870101T000000Z LAST-MODIFIED:19870101T000000Z
TZURL:http://zones.example.com/tz/US-Eastern.ics TZURL:http://zones.example.com/tz/US-Eastern.ics
BEGIN:STANDARD BEGIN:STANDARD
DTSTART:19671029T020000 DTSTART:19671029T020000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10 RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10
TZOFFSETFROM:-0400 TZOFFSETFROM:-0400
TZOFFSETTO:-0500 TZOFFSETTO:-0500
skipping to change at page 68, line 45 skipping to change at page 69, line 45
Purpose: Provide a grouping of component properties that define an Purpose: Provide a grouping of component properties that define an
alarm. alarm.
Format Definition: A "VALARM" calendar component is defined by the Format Definition: A "VALARM" calendar component is defined by the
following notation: following notation:
alarmc = "BEGIN" ":" "VALARM" CRLF alarmc = "BEGIN" ":" "VALARM" CRLF
(audioprop / dispprop / emailprop / procprop) (audioprop / dispprop / emailprop / procprop)
"END" ":" "VALARM" CRLF "END" ":" "VALARM" CRLF
audioprop = 2*( audioprop = *(
; 'action' and 'trigger' are both REQUIRED, ; 'action' and 'trigger' are both REQUIRED,
; but MUST NOT occur more than once ; but MUST NOT occur more than once
action / trigger / action / trigger /
; 'duration' and 'repeat' are both optional, ; 'duration' and 'repeat' are both OPTIONAL,
; and MUST NOT occur more than once each, ; and MUST NOT occur more than once each,
; but if one occurs, so MUST the other ; but if one occurs, so MUST the other
duration / repeat / duration / repeat /
; the following is optional, ; the following is OPTIONAL,
; but MUST NOT occur more than once ; but MUST NOT occur more than once
attach / attach /
; the following is optional, ; the following is OPTIONAL,
; and MAY occur more than once ; and MAY occur more than once
x-prop x-prop
) )
dispprop = 3*( dispprop = *(
; the following are all REQUIRED, ; the following are all REQUIRED,
; but MUST NOT occur more than once ; but MUST NOT occur more than once
action / description / trigger / action / description / trigger /
; 'duration' and 'repeat' are both optional, ; 'duration' and 'repeat' are both OPTIONAL,
; and MUST NOT occur more than once each, ; and MUST NOT occur more than once each,
; but if one occurs, so MUST the other ; but if one occurs, so MUST the other
duration / repeat / duration / repeat /
; the following is optional, ; the following is OPTIONAL,
; and MAY occur more than once ; and MAY occur more than once
x-prop x-prop
) )
emailprop = 5*( emailprop = *(
; the following are all REQUIRED, ; the following are all REQUIRED,
; but MUST NOT occur more than once ; but MUST NOT occur more than once
action / description / trigger / summary / action / description / trigger / summary /
; the following is REQUIRED, ; the following is REQUIRED,
; and MAY occur more than once ; and MAY occur more than once
attendee / attendee /
; 'duration' and 'repeat' are both optional, ; 'duration' and 'repeat' are both OPTIONAL,
; and MUST NOT occur more than once each, ; and MUST NOT occur more than once each,
; but if one occurs, so MUST the other ; but if one occurs, so MUST the other
duration / repeat / duration / repeat /
; the following are optional, ; the following are OPTIONAL,
; and MAY occur more than once ; and MAY occur more than once
attach / x-prop attach / x-prop
) )
procprop = 3*( procprop = *(
; the following are all REQUIRED, ; the following are all REQUIRED,
; but MUST NOT occur more than once ; but MUST NOT occur more than once
action / attach / trigger / action / attach / trigger /
; 'duration' and 'repeat' are both optional, ; 'duration' and 'repeat' are both OPTIONAL,
; and MUST NOT occur more than once each, ; and MUST NOT occur more than once each,
; but if one occurs, so MUST the other ; but if one occurs, so MUST the other
duration / repeat / duration / repeat /
; 'description' is optional, ; 'description' is OPTIONAL,
; and MUST NOT occur more than once ; and MUST NOT occur more than once
description / description /
; the following is optional, ; the following is OPTIONAL,
; and MAY occur more than once ; and MAY occur more than once
x-prop x-prop
) )
Description: A "VALARM" calendar component is a grouping of component Description: A "VALARM" calendar component is a grouping of
properties that is a reminder or alarm for an event or a to-do. component properties that is a reminder or alarm for an event or a
For example, it may be used to define a reminder for a pending to-do. For example, it may be used to define a reminder for a
event or an overdue to-do. pending event or an overdue to-do.
The "VALARM" calendar component MUST include the "ACTION" and The "VALARM" calendar component MUST include the "ACTION" and
"TRIGGER" properties. The "ACTION" property further constrains "TRIGGER" properties. The "ACTION" property further constrains
the "VALARM" calendar component in the following ways: the "VALARM" calendar component in the following ways:
When the action is "AUDIO", the alarm can also include one and When the action is "AUDIO", the alarm can also include one and
only one "ATTACH" property, which MUST point to a sound resource, only one "ATTACH" property, which MUST point to a sound resource,
which is rendered when the alarm is triggered. which is rendered when the alarm is triggered.
When the action is "DISPLAY", the alarm MUST also include a When the action is "DISPLAY", the alarm MUST also include a
skipping to change at page 71, line 38 skipping to change at page 72, line 38
components cannot be nested. Multiple mutually independent components cannot be nested. Multiple mutually independent
"VALARM" calendar components can be specified for a single "VALARM" calendar components can be specified for a single
"VEVENT" or "VTODO" calendar component. "VEVENT" or "VTODO" calendar component.
The "TRIGGER" property specifies when the alarm will be triggered. The "TRIGGER" property specifies when the alarm will be triggered.
The "TRIGGER" property specifies a duration prior to the start of The "TRIGGER" property specifies a duration prior to the start of
an event or a to-do. The "TRIGGER" edge may be explicitly set to an event or a to-do. The "TRIGGER" edge may be explicitly set to
be relative to the "START" or "END" of the event or to-do with the be relative to the "START" or "END" of the event or to-do with the
"RELATED" parameter of the "TRIGGER" property. The "TRIGGER" "RELATED" parameter of the "TRIGGER" property. The "TRIGGER"
property value type can alternatively be set to an absolute property value type can alternatively be set to an absolute
calendar date and time of day value. calendar date with UTC time.
In an alarm set to trigger on the "START" of an event or to-do, In an alarm set to trigger on the "START" of an event or to-do,
the "DTSTART" property MUST be present in the associated event or the "DTSTART" property MUST be present in the associated event or
to-do. In an alarm in a "VEVENT" calendar component set to to-do. In an alarm in a "VEVENT" calendar component set to
trigger on the "END" of the event, either the "DTEND" property trigger on the "END" of the event, either the "DTEND" property
MUST be present, or the "DTSTART" and "DURATION" properties MUST MUST be present, or the "DTSTART" and "DURATION" properties MUST
both be present. In an alarm in a "VTODO" calendar component set both be present. In an alarm in a "VTODO" calendar component set
to trigger on the "END" of the to-do, either the "DUE" property to trigger on the "END" of the to-do, either the "DUE" property
MUST be present, or the "DTSTART" and "DURATION" properties MUST MUST be present, or the "DTSTART" and "DURATION" properties MUST
both be present. both be present.
skipping to change at page 73, line 33 skipping to change at page 74, line 33
TRIGGER;VALUE=DATE-TIME:19970317T133000Z TRIGGER;VALUE=DATE-TIME:19970317T133000Z
REPEAT:4 REPEAT:4
DURATION:PT15M DURATION:PT15M
ACTION:AUDIO ACTION:AUDIO
ATTACH;FMTTYPE=audio/basic:ftp://example.com/pub/ ATTACH;FMTTYPE=audio/basic:ftp://example.com/pub/
sounds/bell-01.aud sounds/bell-01.aud
END:VALARM END:VALARM
The following example is for a "VALARM" calendar component that The following example is for a "VALARM" calendar component that
specifies a display alarm that will trigger 30 minutes before the specifies a display alarm that will trigger 30 minutes before the
scheduled start of the event or the due date/time of the to-do it scheduled start of the event or of the to-do it is associated with
is associated with and will repeat 2 more times at 15 minute and will repeat 2 more times at 15 minute intervals:
intervals:
BEGIN:VALARM BEGIN:VALARM
TRIGGER:-PT30M TRIGGER:-PT30M
REPEAT:2 REPEAT:2
DURATION:PT15M DURATION:PT15M
ACTION:DISPLAY ACTION:DISPLAY
DESCRIPTION:Breakfast meeting with executive\n DESCRIPTION:Breakfast meeting with executive\n
team at 8:30 AM EST. team at 8:30 AM EST.
END:VALARM END:VALARM
The following example is for a "VALARM" calendar component that The following example is for a "VALARM" calendar component that
specifies an email alarm that will trigger 2 days before the specifies an email alarm that will trigger 2 days before the
scheduled due date/time of a to-do it is associated with. It does scheduled due date/time of a to-do it is associated with. It does
not repeat. The email has a subject, body and attachment link. not repeat. The email has a subject, body and attachment link.
BEGIN:VALARM BEGIN:VALARM
TRIGGER:-P2D TRIGGER;RELATED=END:-P2D
ACTION:EMAIL ACTION:EMAIL
ATTENDEE:MAILTO:john_doe@example.com ATTENDEE:mailto:john_doe@example.com
SUMMARY:*** REMINDER: SEND AGENDA FOR WEEKLY STAFF MEETING *** SUMMARY:*** REMINDER: SEND AGENDA FOR WEEKLY STAFF MEETING ***
DESCRIPTION:A draft agenda needs to be sent out to the attendees DESCRIPTION:A draft agenda needs to be sent out to the attendees
to the weekly managers meeting (MGR-LIST). Attached is a to the weekly managers meeting (MGR-LIST). Attached is a
pointer the document template for the agenda file. pointer the document template for the agenda file.
ATTACH;FMTTYPE=application/msword:http://example.com/ ATTACH;FMTTYPE=application/msword:http://example.com/
templates/agenda.doc templates/agenda.doc
END:VALARM END:VALARM
The following example is for a "VALARM" calendar component that The following example is for a "VALARM" calendar component that
specifies a procedural alarm that will trigger at a precise date/ specifies a procedural alarm that will trigger at a precise date/
skipping to change at page 75, line 8 skipping to change at page 76, line 8
calendar information specified in the iCalendar object. calendar information specified in the iCalendar object.
Value Type: TEXT Value Type: TEXT
Property Parameters: Non-standard property parameters can be Property Parameters: Non-standard property parameters can be
specified on this property. specified on this property.
Conformance: Property can be specified in an iCalendar object. The Conformance: Property can be specified in an iCalendar object. The
default value is "GREGORIAN". default value is "GREGORIAN".
Description: This memo is based on the Gregorian calendar scale. The Description: This memo is based on the Gregorian calendar scale.
Gregorian calendar scale is assumed if this property is not The Gregorian calendar scale is assumed if this property is not
specified in the iCalendar object. It is expected that other specified in the iCalendar object. It is expected that other
calendar scales will be defined in other specifications or by calendar scales will be defined in other specifications or by
future versions of this memo. future versions of this memo.
Format Definition: The property is defined by the following notation: Format Definition: This property is defined by the following
notation:
calscale = "CALSCALE" calparam ":" calvalue CRLF calscale = "CALSCALE" calparam ":" calvalue CRLF
calparam = *(";" xparam) calparam = *(";" xparam)
calvalue = "GREGORIAN" / iana-token calvalue = "GREGORIAN" / iana-token
Example: The following is an example of this property: Example: The following is an example of this property:
CALSCALE:GREGORIAN CALSCALE:GREGORIAN
3.7.2. Method 3.7.2. Method
Property Name: METHOD Property Name: METHOD
Purpose: This property defines the iCalendar object method associated Purpose: This property defines the iCalendar object method
with the calendar object. associated with the calendar object.
Value Type: TEXT Value Type: TEXT
Property Parameters: Non-standard property parameters can be Property Parameters: Non-standard property parameters can be
specified on this property. specified on this property.
Conformance: The property can be specified in an iCalendar object. Conformance: The property can be specified once in an iCalendar
object.
Description: When used in a MIME message entity, the value of this Description: When used in a MIME message entity, the value of this
property MUST be the same as the Content-Type "method" parameter property MUST be the same as the Content-Type "method" parameter
value. This property can only appear once within the iCalendar value. If either the "METHOD" property or the Content-Type
object. If either the "METHOD" property or the Content-Type
"method" parameter is specified, then the other MUST also be "method" parameter is specified, then the other MUST also be
specified. specified.
No methods are defined by this specification. This is the subject No methods are defined by this specification. This is the subject
of other specifications, such as the iCalendar Transport- of other specifications, such as the iCalendar Transport-
independent Interoperability Protocol (iTIP) defined by [I-D.ietf- independent Interoperability Protocol (iTIP) defined by
calsify-2446bis]. [I-D.ietf-calsify-2446bis].
If this property is not present in the iCalendar object, then a If this property is not present in the iCalendar object, then a
scheduling transaction MUST NOT be assumed. In such cases, the scheduling transaction MUST NOT be assumed. In such cases, the
iCalendar object is merely being used to transport a snapshot of iCalendar object is merely being used to transport a snapshot of
some calendar information; without the intention of conveying a some calendar information; without the intention of conveying a
scheduling semantic. scheduling semantic.
Format Definition: The property is defined by the following notation: Format Definition: This property is defined by the following
notation:
method = "METHOD" metparam ":" metvalue CRLF method = "METHOD" metparam ":" metvalue CRLF
metparam = *(";" xparam) metparam = *(";" xparam)
metvalue = iana-token metvalue = iana-token
Example: The following is a hypothetical example of this property to Example: The following is a hypothetical example of this property to
convey that the iCalendar object is a request for a meeting: convey that the iCalendar object is a scheduling request :
METHOD:REQUEST METHOD:REQUEST
3.7.3. Product Identifier 3.7.3. Product Identifier
Property Name: PRODID Property Name: PRODID
Purpose: This property specifies the identifier for the product that Purpose: This property specifies the identifier for the product that
created the iCalendar object. created the iCalendar object.
Value Type: TEXT Value Type: TEXT
Property Parameters: Non-standard property parameters can be Property Parameters: Non-standard property parameters can be
specified on this property. specified on this property.
Conformance: The property MUST be specified once in an iCalendar Conformance: The property MUST be specified once in an iCalendar
object. object.
Description: The vendor of the implementation SHOULD assure that this Description: The vendor of the implementation SHOULD assure that
is a globally unique identifier; using some technique such as an this is a globally unique identifier; using some technique such as
FPI value, as defined in [ISO.9070.1991]. an FPI value, as defined in [ISO.9070.1991].
This property SHOULD not be used to alter the interpretation of an This property SHOULD not be used to alter the interpretation of an
iCalendar object beyond the semantics specified in this memo. For iCalendar object beyond the semantics specified in this memo. For
example, it is not to be used to further the understanding of non- example, it is not to be used to further the understanding of non-
standard properties. standard properties.
Format Definition: The property is defined by the following notation: Format Definition: This property is defined by the following
notation:
prodid = "PRODID" pidparam ":" pidvalue CRLF prodid = "PRODID" pidparam ":" pidvalue CRLF
pidparam = *(";" xparam) pidparam = *(";" xparam)
pidvalue = text pidvalue = text
;Any text that describes the product and version ;Any text that describes the product and version
;and that is generally assured of being unique. ;and that is generally assured of being unique.
Example: The following is an example of this property. It does not Example: The following is an example of this property. It does not
skipping to change at page 77, line 37 skipping to change at page 78, line 37
Value Type: TEXT Value Type: TEXT
Property Parameters: Non-standard property parameters can be Property Parameters: Non-standard property parameters can be
specified on this property. specified on this property.
Conformance: This property MUST be specified by an iCalendar object, Conformance: This property MUST be specified by an iCalendar object,
but MUST only be specified once. but MUST only be specified once.
Description: A value of "2.0" corresponds to this memo. Description: A value of "2.0" corresponds to this memo.
Format Definition: The property is defined by the following notation: Format Definition: This property is defined by the following
notation:
version = "VERSION" verparam ":" vervalue CRLF version = "VERSION" verparam ":" vervalue CRLF
verparam = *(";" xparam) verparam = *(";" xparam)
vervalue = "2.0" ;This memo vervalue = "2.0" ;This memo
/ maxver / maxver
/ (minver ";" maxver) / (minver ";" maxver)
minver = <A IANA registered iCalendar version identifier> minver = <A IANA registered iCalendar version identifier>
skipping to change at page 78, line 22 skipping to change at page 79, line 22
3.8.1. Descriptive Component Properties 3.8.1. Descriptive Component Properties
The following properties specify descriptive information about The following properties specify descriptive information about
calendar components. calendar components.
3.8.1.1. Attachment 3.8.1.1. Attachment
Property Name: ATTACH Property Name: ATTACH
Purpose: The property provides the capability to associate a document Purpose: This property provides the capability to associate a
object with a calendar component. document object with a calendar component.
Value Type: The default value type for this property is URI. The Value Type: The default value type for this property is URI. The
value type can also be set to BINARY to indicate inline binary value type can also be set to BINARY to indicate inline binary
encoded content information. encoded content information.
Property Parameters: Non-standard, inline encoding, format type and Property Parameters: Non-standard, inline encoding, format type and
value data type property parameters can be specified on this value data type property parameters can be specified on this
property. property.
Conformance: The property can be specified in a "VEVENT", "VTODO", Conformance: The property can be specified in a "VEVENT", "VTODO",
"VJOURNAL" or "VALARM" calendar components. "VJOURNAL" or "VALARM" calendar components.
Description: The property can be specified within "VEVENT", "VTODO", Description: This property can be specified within "VEVENT",
"VJOURNAL", or "VALARM" calendar components. This property can be "VTODO", "VJOURNAL", or "VALARM" calendar components. This
specified multiple times within an iCalendar object. property can be specified multiple times within an iCalendar
object.
Format Definition: The property is defined by the following notation: Format Definition: This property is defined by the following
notation:
attach = "ATTACH" attachparam ":" uri CRLF attach = "ATTACH" attachparam ":" uri CRLF
/ "ATTACH" attparam ";" "ENCODING" "=" "BASE64" / "ATTACH" attachparam ";" "ENCODING" "=" "BASE64"
";" "VALUE" "=" "BINARY" ":" binary ";" "VALUE" "=" "BINARY" ":" binary
attachparam = *( attachparam = *(
; the following is optional, ; the following is OPTIONAL,
; but MUST NOT occur more than once ; but MUST NOT occur more than once
(";" fmttypeparam) / (";" fmttypeparam) /
; the following is optional, ; the following is OPTIONAL,
; and MAY occur more than once ; and MAY occur more than once
(";" xparam) (";" xparam)
) )
Example: The following are examples of this property: Example: The following are examples of this property:
ATTACH:CID:jsmith.part3.960817T083000.xyzMail@example.com ATTACH:CID:jsmith.part3.960817T083000.xyzMail@example.com
skipping to change at page 80, line 5 skipping to change at page 81, line 5
Conformance: The property can be specified within "VEVENT", "VTODO" Conformance: The property can be specified within "VEVENT", "VTODO"
or "VJOURNAL" calendar components. or "VJOURNAL" calendar components.
Description: This property is used to specify categories or subtypes Description: This property is used to specify categories or subtypes
of the calendar component. The categories are useful in searching of the calendar component. The categories are useful in searching
for a calendar component of a particular type and category. for a calendar component of a particular type and category.
Within the "VEVENT", "VTODO" or "VJOURNAL" calendar components, Within the "VEVENT", "VTODO" or "VJOURNAL" calendar components,
more than one category can be specified as a list of categories more than one category can be specified as a list of categories
separated by the COMMA character (US-ASCII decimal 44). separated by the COMMA character (US-ASCII decimal 44).
Format Definition: The property is defined by the following notation: Format Definition: This property is defined by the following
notation:
categories = "CATEGORIES" catparam ":" text *("," text) categories = "CATEGORIES" catparam ":" text *("," text)
CRLF CRLF
catparam = *( catparam = *(
; the following is optional, ; the following is OPTIONAL,
; but MUST NOT occur more than once ; but MUST NOT occur more than once
(";" languageparam ) / (";" languageparam ) /
; the following is optional, ; the following is OPTIONAL,
; and MAY occur more than once ; and MAY occur more than once
(";" xparam) (";" xparam)
) )
Example: The following are examples of this property: Example: The following are examples of this property:
CATEGORIES:APPOINTMENT,EDUCATION CATEGORIES:APPOINTMENT,EDUCATION
skipping to change at page 81, line 4 skipping to change at page 82, line 5
"VTODO" or "VJOURNAL" calendar components. "VTODO" or "VJOURNAL" calendar components.
Description: An access classification is only one component of the Description: An access classification is only one component of the
general security system within a calendar application. It general security system within a calendar application. It
provides a method of capturing the scope of the access the provides a method of capturing the scope of the access the
calendar owner intends for information within an individual calendar owner intends for information within an individual
calendar entry. The access classification of an individual calendar entry. The access classification of an individual
iCalendar component is useful when measured along with the other iCalendar component is useful when measured along with the other
security components of a calendar system (e.g., calendar user security components of a calendar system (e.g., calendar user
authentication, authorization, access rights, access role, etc.). authentication, authorization, access rights, access role, etc.).
Hence, the semantics of the individual access classifications Hence, the semantics of the individual access classifications
cannot be completely defined by this memo alone. Additionally, cannot be completely defined by this memo alone. Additionally,
due to the "blind" nature of most exchange processes using this due to the "blind" nature of most exchange processes using this
memo, these access classifications cannot serve as an enforcement memo, these access classifications cannot serve as an enforcement
statement for a system receiving an iCalendar object. Rather, statement for a system receiving an iCalendar object. Rather,
they provide a method for capturing the intention of the calendar they provide a method for capturing the intention of the calendar
owner for the access to the calendar component. owner for the access to the calendar component.
Format Definition: The property is defined by the following notation: Format Definition: This property is defined by the following
notation:
class = "CLASS" classparam ":" classvalue CRLF class = "CLASS" classparam ":" classvalue CRLF
classparam = *(";" xparam) classparam = *(";" xparam)
classvalue = "PUBLIC" / "PRIVATE" / "CONFIDENTIAL" / iana-token classvalue = "PUBLIC" / "PRIVATE" / "CONFIDENTIAL" / iana-token
/ x-name / x-name
;Default is PUBLIC ;Default is PUBLIC
Example: The following is an example of this property: Example: The following is an example of this property:
skipping to change at page 81, line 39 skipping to change at page 82, line 40
Property Name: COMMENT Property Name: COMMENT
Purpose: This property specifies non-processing information intended Purpose: This property specifies non-processing information intended
to provide a comment to the calendar user. to provide a comment to the calendar user.
Value Type: TEXT Value Type: TEXT
Property Parameters: Non-standard, alternate text representation and Property Parameters: Non-standard, alternate text representation and
language property parameters can be specified on this property. language property parameters can be specified on this property.
Conformance: This property can be specified in "VEVENT", "VTODO", Conformance: This property can be specified one or more times in
"VJOURNAL", "VTIMEZONE" or "VFREEBUSY" calendar components. "VEVENT", "VTODO", "VJOURNAL", "VTIMEZONE" or "VFREEBUSY" calendar
components.
Description: The property can be specified multiple times. Description: The property can be specified multiple times.
Format Definition: The property is defined by the following notation: Format Definition: This property is defined by the following
notation:
comment = "COMMENT" commparam ":" text CRLF comment = "COMMENT" commparam ":" text CRLF
commparam = *( commparam = *(
; the following are optional, ; the following are OPTIONAL,
; but MUST NOT occur more than once ; but MUST NOT occur more than once
(";" altrepparam) / (";" languageparam) / (";" altrepparam) / (";" languageparam) /
; the following is optional, ; the following is OPTIONAL,
; and MAY occur more than once ; and MAY occur more than once
(";" xparam) (";" xparam)
) )
Example: The following is an example of this property: Example: The following is an example of this property:
COMMENT:The meeting really needs to include both ourselves COMMENT:The meeting really needs to include both ourselves
and the customer. We can't hold this meeting without them. and the customer. We can't hold this meeting without them.
skipping to change at page 83, line 10 skipping to change at page 84, line 10
capture lengthy textual decriptions associated with the activity. capture lengthy textual decriptions associated with the activity.
This property is used in the "VJOURNAL" calendar component to This property is used in the "VJOURNAL" calendar component to
capture one more textual journal entries. capture one more textual journal entries.
This property is used in the "VALARM" calendar component to This property is used in the "VALARM" calendar component to
capture the display text for a DISPLAY category of alarm, to capture the display text for a DISPLAY category of alarm, to
capture the body text for an EMAIL category of alarm and to capture the body text for an EMAIL category of alarm and to
capture the argument string for a PROCEDURE category of alarm. capture the argument string for a PROCEDURE category of alarm.
Format Definition: The property is defined by the following notation: Format Definition: This property is defined by the following
notation:
description = "DESCRIPTION" descparam ":" text CRLF description = "DESCRIPTION" descparam ":" text CRLF
descparam = *( descparam = *(
; the following are optional, ; the following are OPTIONAL,
; but MUST NOT occur more than once ; but MUST NOT occur more than once
(";" altrepparam) / (";" languageparam) / (";" altrepparam) / (";" languageparam) /
; the following is optional, ; the following is OPTIONAL,
; and MAY occur more than once ; and MAY occur more than once
(";" xparam) (";" xparam)
) )
Example: The following is an example of the property with formatted Example: The following is an example of the property with formatted
line breaks in the property value: line breaks in the property value:
DESCRIPTION:Meeting to provide technical review for "Phoenix" DESCRIPTION:Meeting to provide technical review for "Phoenix"
design.\nHappy Face Conference Room. Phoenix design team design.\nHappy Face Conference Room. Phoenix design team
MUST attend this meeting.\nRSVP to team leader. MUST attend this meeting.\nRSVP to team leader.
The following is an example of the property with folding of long
lines:
DESCRIPTION:Last draft of the new novel is to be completed
for the editor's proof today.
3.8.1.6. Geographic Position 3.8.1.6. Geographic Position
Property Name: GEO Property Name: GEO
Purpose: This property specifies information related to the global Purpose: This property specifies information related to the global
position for the activity specified by a calendar component. position for the activity specified by a calendar component.
Value Type: FLOAT. The value MUST be two SEMICOLON separated FLOAT Value Type: FLOAT. The value MUST be two SEMICOLON separated FLOAT
values. values.
Property Parameters: Non-standard property parameters can be Property Parameters: Non-standard property parameters can be
specified on this property. specified on this property.
Conformance: This property can be specified in "VEVENT" or "VTODO" Conformance: This property can be specified in "VEVENT" or "VTODO"
calendar components. calendar components.
Description: The property value specifies latitude and longitude, in Description: This property value specifies latitude and longitude,
that order (i.e., "LAT LON" ordering). The longitude represents in that order (i.e., "LAT LON" ordering). The longitude
the location east or west of the prime meridian as a positive or represents the location East or West of the prime meridian as a
negative real number, respectively. The longitude and latitude positive or negative real number, respectively. The longitude and
values MAY be specified up to six decimal places, which will allow latitude values MAY be specified up to six decimal places, which
for accuracy to within one meter of geographical position. will allow for accuracy to within one meter of geographical
Receiving applications MUST accept values of this precision and position. Receiving applications MUST accept values of this
MAY truncate values of greater precision. precision and MAY truncate values of greater precision.
Values for latitude and longitude shall be expressed as decimal Values for latitude and longitude shall be expressed as decimal
fractions of degrees. Whole degrees of latitude shall be fractions of degrees. Whole degrees of latitude shall be
represented by a two-digit decimal number ranging from 0 through represented by a two-digit decimal number ranging from 0 through
90. Whole degrees of longitude shall be represented by a decimal 90. Whole degrees of longitude shall be represented by a decimal
number ranging from 0 through 180. When a decimal fraction of a number ranging from 0 through 180. When a decimal fraction of a
degree is specified, it shall be separated from the whole number degree is specified, it shall be separated from the whole number
of degrees by a decimal point. of degrees by a decimal point.
Latitudes north of the equator shall be specified by a plus sign Latitudes north of the equator shall be specified by a plus sign
skipping to change at page 85, line 16 skipping to change at page 86, line 10
form is specified in Department of Commerce, 1986, Representation form is specified in Department of Commerce, 1986, Representation
of geographic point locations for information interchange (Federal of geographic point locations for information interchange (Federal
Information Processing Standard 70-1): Washington, Department of Information Processing Standard 70-1): Washington, Department of
Commerce, National Institute of Standards and Technology. Commerce, National Institute of Standards and Technology.
The simple formula for converting degrees-minutes-seconds into The simple formula for converting degrees-minutes-seconds into
decimal degrees is: decimal degrees is:
decimal = degrees + minutes/60 + seconds/3600. decimal = degrees + minutes/60 + seconds/3600.
Format Definition: The property is defined by the following notation: Format Definition: This property is defined by the following
notation:
geo = "GEO" geoparam ":" geovalue CRLF geo = "GEO" geoparam ":" geovalue CRLF
geoparam = *(";" xparam) geoparam = *(";" xparam)
geovalue = float ";" float geovalue = float ";" float
;Latitude and Longitude components ;Latitude and Longitude components
Example: The following is an example of this property: Example: The following is an example of this property:
GEO:37.386013;-122.082932 GEO:37.386013;-122.082932
3.8.1.7. Location 3.8.1.7. Location
Property Name: LOCATION Property Name: LOCATION
Purpose: The property defines the intended venue for the activity Purpose: This property defines the intended venue for the activity
defined by a calendar component. defined by a calendar component.
Value Type: TEXT Value Type: TEXT
Property Parameters: Non-standard, alternate text representation and Property Parameters: Non-standard, alternate text representation and
language property parameters can be specified on this property. language property parameters can be specified on this property.
Conformance: This property can be specified in "VEVENT" or "VTODO" Conformance: This property can be specified in "VEVENT" or "VTODO"
calendar component. calendar component.
Description: Specific venues such as conference or meeting rooms may Description: Specific venues such as conference or meeting rooms may
be explicitly specified using this property. An alternate be explicitly specified using this property. An alternate
representation may be specified that is a URI that points to representation may be specified that is a URI that points to
directory information with more structured specification of the directory information with more structured specification of the
location. For example, the alternate representation may specify location. For example, the alternate representation may specify
either an LDAP URI pointing to an LDAP server entry or a CID URI either an LDAP URI pointing to an LDAP server entry or a CID URI
pointing to a MIME body part containing a vCard [RFC2426] for the pointing to a MIME body part containing a vCard [RFC2426] for the
location. location.
Format Definition: The property is defined by the following notation: Format Definition: This property is defined by the following
notation:
location = "LOCATION" locparam ":" text CRLF location = "LOCATION" locparam ":" text CRLF
locparam = *( locparam = *(
; the following are optional, ; the following are OPTIONAL,
; but MUST NOT occur more than once ; but MUST NOT occur more than once
(";" altrepparam) / (";" languageparam) / (";" altrepparam) / (";" languageparam) /
; the following is optional, ; the following is OPTIONAL,
; and MAY occur more than once ; and MAY occur more than once
(";" xparam) (";" xparam)
) )
Example: The following are some examples of this property: Example: The following are some examples of this property:
LOCATION:Conference Room - F123\, Bldg. 002 LOCATION:Conference Room - F123\, Bldg. 002
LOCATION;ALTREP="http://xyzcorp.com/conf-rooms/f123.vcf": LOCATION;ALTREP="http://xyzcorp.com/conf-rooms/f123.vcf":
Conference Room - F123\, Bldg. 002 Conference Room - F123\, Bldg. 002
3.8.1.8. Percent Complete 3.8.1.8. Percent Complete
Property Name: PERCENT-COMPLETE Property Name: PERCENT-COMPLETE
Purpose: This property is used by an assignee or delegatee of a to-do Purpose: This property is used by an assignee or delegatee of a
to convey the percent completion of a to-do to the Organizer. to-do to convey the percent completion of a to-do to the
"Organizer".
Value Type: INTEGER Value Type: INTEGER
Property Parameters: Non-standard property parameters can be Property Parameters: Non-standard property parameters can be
specified on this property. specified on this property.
Conformance: This property can be specified in a "VTODO" calendar Conformance: This property can be specified in a "VTODO" calendar
component. component.
Description: The property value is a positive integer between zero Description: The property value is a positive integer between zero
skipping to change at page 87, line 14 skipping to change at page 88, line 14
When a to-do is assigned to multiple individuals, the property When a to-do is assigned to multiple individuals, the property
value indicates the percent complete for that portion of the to-do value indicates the percent complete for that portion of the to-do
assigned to the assignee or delegatee. For example, if a to-do is assigned to the assignee or delegatee. For example, if a to-do is
assigned to both individuals "A" and "B". A reply from "A" with a assigned to both individuals "A" and "B". A reply from "A" with a
percent complete of "70" indicates that "A" has completed 70% of percent complete of "70" indicates that "A" has completed 70% of
the to-do assigned to them. A reply from "B" with a percent the to-do assigned to them. A reply from "B" with a percent
complete of "50" indicates "B" has completed 50% of the to-do complete of "50" indicates "B" has completed 50% of the to-do
assigned to them. assigned to them.
Format Definition: The property is defined by the following notation: Format Definition: This property is defined by the following
notation:
percent = "PERCENT-COMPLETE" pctparam ":" integer CRLF percent = "PERCENT-COMPLETE" pctparam ":" integer CRLF
pctparam = *(";" xparam) pctparam = *(";" xparam)
Example: The following is an example of this property to show 39% Example: The following is an example of this property to show 39%
completion: completion:
PERCENT-COMPLETE:39 PERCENT-COMPLETE:39
3.8.1.9. Priority 3.8.1.9. Priority
Property Name: PRIORITY Property Name: PRIORITY
Purpose: The property defines the relative priority for a calendar Purpose: This property defines the relative priority for a calendar
component. component.
Value Type: INTEGER Value Type: INTEGER
Property Parameters: Non-standard property parameters can be Property Parameters: Non-standard property parameters can be
specified on this property. specified on this property.
Conformance: The property can be specified in a "VEVENT" or "VTODO" Conformance: This property can be specified in a "VEVENT" or "VTODO"
calendar component. calendar component.
Description: The priority is specified as an integer in the range Description: This priority is specified as an integer in the range
zero to nine. A value of zero (US-ASCII decimal 48) specifies an zero to nine. A value of zero (US-ASCII decimal 48) specifies an
undefined priority. A value of one (US-ASCII decimal 49) is the undefined priority. A value of one (US-ASCII decimal 49) is the
highest priority. A value of two (US-ASCII decimal 50) is the highest priority. A value of two (US-ASCII decimal 50) is the
second highest priority. Subsequent numbers specify a decreasing second highest priority. Subsequent numbers specify a decreasing
ordinal priority. A value of nine (US-ASCII decimal 57 ) is the ordinal priority. A value of nine (US-ASCII decimal 57 ) is the
lowest priority. lowest priority.
A CUA with a three-level priority scheme of "HIGH", "MEDIUM" and A CUA with a three-level priority scheme of "HIGH", "MEDIUM" and
"LOW" is mapped into this property such that a property value in "LOW" is mapped into this property such that a property value in
the range of one (US-ASCII decimal 49) to four (US-ASCII decimal the range of one (US-ASCII decimal 49) to four (US-ASCII decimal
skipping to change at page 88, line 24 skipping to change at page 89, line 25
Other integer values are reserved for future use. Other integer values are reserved for future use.
Within a "VEVENT" calendar component, this property specifies a Within a "VEVENT" calendar component, this property specifies a
priority for the event. This property may be useful when more priority for the event. This property may be useful when more
than one event is scheduled for a given time period. than one event is scheduled for a given time period.
Within a "VTODO" calendar component, this property specified a Within a "VTODO" calendar component, this property specified a
priority for the to-do. This property is useful in prioritizing priority for the to-do. This property is useful in prioritizing
multiple action items for a given time period. multiple action items for a given time period.
Format Definition: The property is defined by the following notation: Format Definition: This . property is defined by the following
notation:
priority = "PRIORITY" prioparam ":" privalue CRLF priority = "PRIORITY" prioparam ":" priovalue CRLF
;Default is zero ;Default is zero (i.e., undefined)
prioparam = *(";" xparam) prioparam = *(";" xparam)
privalue = integer ;Must be in the range [0..9] priovalue = integer ;Must be in the range [0..9]
; All other values are reserved for future use ; All other values are reserved for future use
Example: The following is an example of a property with the highest Example: The following is an example of a property with the highest
priority: priority:
PRIORITY:1 PRIORITY:1
The following is an example of a property with a next highest The following is an example of a property with a next highest
priority: priority:
skipping to change at page 89, line 9 skipping to change at page 90, line 9
The following is an example of a property with no priority. This The following is an example of a property with no priority. This
is equivalent to not specifying the "PRIORITY" property: is equivalent to not specifying the "PRIORITY" property:
PRIORITY:0 PRIORITY:0
3.8.1.10. Resources 3.8.1.10. Resources
Property Name: RESOURCES Property Name: RESOURCES
Purpose: This property defines the equipment or resources anticipated Purpose: This property defines the equipment or resources
for an activity specified by a calendar entity.. anticipated for an activity specified by a calendar component.
Value Type: TEXT Value Type: TEXT
Property Parameters: Non-standard, alternate text representation and Property Parameters: Non-standard, alternate text representation and
language property parameters can be specified on this property. language property parameters can be specified on this property.
Conformance: This property can be specified in "VEVENT" or "VTODO" Conformance: This property can be specified in "VEVENT" or "VTODO"
calendar component. calendar component.
Description: The property value is an arbitrary text. More than one Description: The property value is an arbitrary text. More than one
resource can be specified as a list of resources separated by the resource can be specified as a list of resources separated by the
COMMA character (US-ASCII decimal 44). COMMA character (US-ASCII decimal 44).
Format Definition: The property is defined by the following notation: Format Definition: This property is defined by the following
notation:
resources = "RESOURCES" resrcparam ":" text *("," text) CRLF resources = "RESOURCES" resrcparam ":" text *("," text) CRLF
resrcparam = *( resrcparam = *(
; the following are optional, ; the following are OPTIONAL,
; but MUST NOT occur more than once ; but MUST NOT occur more than once
(";" altrepparam) / (";" languageparam) / (";" altrepparam) / (";" languageparam) /
; the following is optional, ; the following is OPTIONAL,
; and MAY occur more than once ; and MAY occur more than once
(";" xparam) (";" xparam)
) )
Example: The following is an example of this property: Example: The following is an example of this property:
RESOURCES:EASEL,PROJECTOR,VCR RESOURCES:EASEL,PROJECTOR,VCR
skipping to change at page 90, line 4 skipping to change at page 91, line 6
) )
Example: The following is an example of this property: Example: The following is an example of this property:
RESOURCES:EASEL,PROJECTOR,VCR RESOURCES:EASEL,PROJECTOR,VCR
RESOURCES;LANGUAGE=fr:1 raton-laveur RESOURCES;LANGUAGE=fr:1 raton-laveur
3.8.1.11. Status 3.8.1.11. Status
Property Name: STATUS Property Name: STATUS
Purpose: This property defines the overall status or confirmation for Purpose: This property defines the overall status or confirmation
the calendar component. for the calendar component.
Value Type: TEXT Value Type: TEXT
Property Parameters: Non-standard property parameters can be Property Parameters: Non-standard property parameters can be
specified on this property. specified on this property.
Conformance: This property can be specified in "VEVENT", "VTODO" or Conformance: This property can be specified in "VEVENT", "VTODO" or
"VJOURNAL" calendar components. "VJOURNAL" calendar components.
Description: In a group scheduled calendar component, the property is Description: In a group scheduled calendar component, the property
used by the "Organizer" to provide a confirmation of the event to is used by the "Organizer" to provide a confirmation of the event
the "Attendees". For example in a "VEVENT" calendar component, to the "Attendees". For example in a "VEVENT" calendar component,
the "Organizer" can indicate that a meeting is tentative, the "Organizer" can indicate that a meeting is tentative,
confirmed or cancelled. In a "VTODO" calendar component, the confirmed or cancelled. In a "VTODO" calendar component, the
"Organizer" can indicate that an action item needs action, is "Organizer" can indicate that an action item needs action, is
completed, is in process or being worked on, or has been completed, is in process or being worked on, or has been
cancelled. In a "VJOURNAL" calendar component, the "Organizer" cancelled. In a "VJOURNAL" calendar component, the "Organizer"
can indicate that a journal entry is draft, final or has been can indicate that a journal entry is draft, final or has been
cancelled or removed. cancelled or removed.
Format Definition: The property is defined by the following notation: Format Definition: This property is defined by the following
notation:
status = "STATUS" statparam ":" statvalue CRLF status = "STATUS" statparam ":" statvalue CRLF
statparam = *(";" xparam) statparam = *(";" xparam)
statvalue = ( "TENTATIVE" ;Indicates event is tentative. statvalue = ( "TENTATIVE" ;Indicates event is tentative.
/ "CONFIRMED" ;Indicates event is definite. / "CONFIRMED" ;Indicates event is definite.
/ "CANCELLED" ) ;Indicates event was cancelled. / "CANCELLED" ) ;Indicates event was cancelled.
;Status values for a "VEVENT" ;Status values for a "VEVENT"
skipping to change at page 91, line 42 skipping to change at page 93, line 17
Conformance: The property can be specified in "VEVENT", "VTODO", Conformance: The property can be specified in "VEVENT", "VTODO",
"VJOURNAL" or "VALARM" calendar components. "VJOURNAL" or "VALARM" calendar components.
Description: This property is used in the "VEVENT", "VTODO" and Description: This property is used in the "VEVENT", "VTODO" and
"VJOURNAL" calendar components to capture a short, one line "VJOURNAL" calendar components to capture a short, one line
summary about the activity or journal entry. summary about the activity or journal entry.
This property is used in the "VALARM" calendar component to This property is used in the "VALARM" calendar component to
capture the subject of an EMAIL category of alarm. capture the subject of an EMAIL category of alarm.
Format Definition: The property is defined by the following notation: Format Definition: This property is defined by the following
notation:
summary = "SUMMARY" summparam ":" text CRLF summary = "SUMMARY" summparam ":" text CRLF
summparam = *( summparam = *(
; the following are optional, ; the following are OPTIONAL,
; but MUST NOT occur more than once ; but MUST NOT occur more than once
(";" altrepparam) / (";" languageparam) / (";" altrepparam) / (";" languageparam) /
; the following is optional, ; the following is OPTIONAL,
; and MAY occur more than once ; and MAY occur more than once
(";" xparam) (";" xparam)
) )
Example: The following is an example of this property: Example: The following is an example of this property:
SUMMARY:Department Party SUMMARY:Department Party
skipping to change at page 92, line 47 skipping to change at page 94, line 17
Value Type: DATE-TIME Value Type: DATE-TIME
Property Parameters: Non-standard property parameters can be Property Parameters: Non-standard property parameters can be
specified on this property. specified on this property.
Conformance: The property can be specified in a "VTODO" calendar Conformance: The property can be specified in a "VTODO" calendar
component. component.
Description: The date and time MUST be in a UTC format. Description: The date and time MUST be in a UTC format.
Format Definition: The property is defined by the following notation: Format Definition: This property is defined by the following
notation:
completed = "COMPLETED" compparam ":" date-time CRLF completed = "COMPLETED" compparam ":" date-time CRLF
compparam = *(";" xparam) compparam = *(";" xparam)
Example: The following is an example of this property: Example: The following is an example of this property:
COMPLETED:19960401T235959Z COMPLETED:19960401T235959Z
3.8.2.2. Date/Time End 3.8.2.2. Date/Time End
Property Name: DTEND Property Name: DTEND
Purpose: This property specifies the date and time that a calendar Purpose: This property specifies the date and time that a calendar
component ends. component ends.
skipping to change at page 93, line 33 skipping to change at page 95, line 5
Description: Within the "VEVENT" calendar component, this property Description: Within the "VEVENT" calendar component, this property
defines the date and time by which the event ends. The value MUST defines the date and time by which the event ends. The value MUST
be later in time than the value of the "DTSTART" property. be later in time than the value of the "DTSTART" property.
Within the "VFREEBUSY" calendar component, this property defines Within the "VFREEBUSY" calendar component, this property defines
the end date and time for the free or busy time information. The the end date and time for the free or busy time information. The
time MUST be specified in the UTC time format. The value MUST be time MUST be specified in the UTC time format. The value MUST be
later in time than the value of the "DTSTART" property. later in time than the value of the "DTSTART" property.
Format Definition: The property is defined by the following notation: Format Definition: This property is defined by the following
notation:
dtend = "DTEND" dtendparam ":" dtendval CRLF dtend = "DTEND" dtendparam ":" dtendval CRLF
dtendparam = *( dtendparam = *(
; the following are optional, ; the following are OPTIONAL,
; but MUST NOT occur more than once ; but MUST NOT occur more than once
(";" "VALUE" "=" ("DATE-TIME" / "DATE")) / (";" "VALUE" "=" ("DATE-TIME" / "DATE")) /
(";" tzidparam) / (";" tzidparam) /
; the following is optional, ; the following is OPTIONAL,
; and MAY occur more than once ; and MAY occur more than once
(";" xparam) (";" xparam)
) )
dtendval = date-time / date dtendval = date-time / date
;Value MUST match value type ;Value MUST match value type
Example: The following is an example of this property: Example: The following is an example of this property:
skipping to change at page 94, line 44 skipping to change at page 95, line 47
Purpose: This property defines the date and time that a to-do is Purpose: This property defines the date and time that a to-do is
expected to be completed. expected to be completed.
Value Type: The default value type is DATE-TIME. The value type can Value Type: The default value type is DATE-TIME. The value type can
be set to a DATE value type. be set to a DATE value type.
Property Parameters: Non-standard, value data type, time zone Property Parameters: Non-standard, value data type, time zone
identifier property parameters can be specified on this property. identifier property parameters can be specified on this property.
Conformance: The property can be specified once in a "VTODO" calendar Conformance: The property can be specified once in a "VTODO"
component. calendar component.
Description: The value MUST be a date/time equal to or after the Description: The value MUST be a date/time equal to or after the
DTSTART value, if specified. "DTSTART" value, if specified.
Format Definition: The property is defined by the following notation: Format Definition: This property is defined by the following
notation:
due = "DUE" dueparam ":" dueval CRLF due = "DUE" dueparam ":" dueval CRLF
dueparam = *( dueparam = *(
; the following are optional,
; the following are OPTIONAL,
; but MUST NOT occur more than once ; but MUST NOT occur more than once
(";" "VALUE" "=" ("DATE-TIME" / "DATE")) / (";" "VALUE" "=" ("DATE-TIME" / "DATE")) /
(";" tzidparam) / (";" tzidparam) /
; the following is optional, ; the following is OPTIONAL,
; and MAY occur more than once ; and MAY occur more than once
*(";" xparam) (";" xparam)
) )
dueval = date-time / date dueval = date-time / date
;Value MUST match value type ;Value MUST match value type
Example: The following is an example of this property: Example: The following is an example of this property:
DUE:19980430T235959Z DUE:19980430T235959Z
3.8.2.4. Date/Time Start 3.8.2.4. Date/Time Start
Property Name: DTSTART Property Name: DTSTART
Purpose: This property specifies when the calendar component begins. Purpose: This property specifies when the calendar component begins.
Value Type: The default value type is DATE-TIME. The time value MUST Value Type: The default value type is DATE-TIME. The time value
be one of the forms defined for the DATE-TIME value type. The MUST be one of the forms defined for the DATE-TIME value type.
value type can be set to a DATE value type. The value type can be set to a DATE value type.
Property Parameters: Non-standard, value data type, time zone Property Parameters: Non-standard, value data type, time zone
identifier property parameters can be specified on this property. identifier property parameters can be specified on this property.
Conformance: This property can be specified in the "VEVENT", "VTODO", Conformance: This property can be specified in the "VEVENT",
"VFREEBUSY", or "VTIMEZONE" calendar components. This property is "VTODO", "VFREEBUSY", or "VTIMEZONE" calendar components. This
REQUIRED in "VEVENT" calendar components. property is REQUIRED in "VEVENT" calendar components and in all
types of recurring calendar components.
Description: Within the "VEVENT" calendar component, this property Description: Within the "VEVENT" calendar component, this property
defines the start date and time for the event. Events can have a defines the start date and time for the event. Events can have a
start date/time but no end date/time. In that case, the event start date/time but no end date/time. In that case, the event
does not take up any time. does not take up any time.
Within the "VFREEBUSY" calendar component, this property defines Within the "VFREEBUSY" calendar component, this property defines
the start date and time for the free or busy time information. the start date and time for the free or busy time information.
The time MUST be specified in UTC time. The time MUST be specified in UTC time.
Within the "VTIMEZONE" calendar component, this property defines Within the "VTIMEZONE" calendar component, this property defines
the effective start date and time for a time zone specification. the effective start date and time for a time zone specification.
This property is REQUIRED within each STANDARD and DAYLIGHT part This property is REQUIRED within each "STANDARD" and "DAYLIGHT"
included in "VTIMEZONE" calendar components and MUST be specified sub-components included in "VTIMEZONE" calendar components and
as a local DATE-TIME without the "TZID" property parameter. MUST be specified as a local DATE-TIME without the "TZID" property
parameter.
Format Definition: The property is defined by the following notation: Format Definition: This property is defined by the following
notation:
dtstart = "DTSTART" dtstparam ":" dtstval CRLF dtstart = "DTSTART" dtstparam ":" dtstval CRLF
dtstparam = *( dtstparam = *(
; the following are optional, ; the following are OPTIONAL,
; but MUST NOT occur more than once ; but MUST NOT occur more than once
(";" "VALUE" "=" ("DATE-TIME" / "DATE")) / (";" "VALUE" "=" ("DATE-TIME" / "DATE")) /
(";" tzidparam) / (";" tzidparam) /
; the following is optional, ; the following is OPTIONAL,
; and MAY occur more than once ; and MAY occur more than once
*(";" xparam) (";" xparam)
) )
dtstval = date-time / date dtstval = date-time / date
;Value MUST match value type ;Value MUST match value type
Example: The following is an example of this property: Example: The following is an example of this property:
DTSTART:19980118T073000Z DTSTART:19980118T073000Z
skipping to change at page 96, line 42 skipping to change at page 98, line 4
) )
dtstval = date-time / date dtstval = date-time / date
;Value MUST match value type ;Value MUST match value type
Example: The following is an example of this property: Example: The following is an example of this property:
DTSTART:19980118T073000Z DTSTART:19980118T073000Z
3.8.2.5. Duration 3.8.2.5. Duration
Property Name: DURATION Property Name: DURATION
Purpose: The property specifies a positive duration of time. Purpose: This property specifies a positive duration of time.
Value Type: DURATION Value Type: DURATION
Property Parameters: Non-standard property parameters can be Property Parameters: Non-standard property parameters can be
specified on this property. specified on this property.
Conformance: The property can be specified in "VEVENT", "VTODO", Conformance: This property can be specified in "VEVENT", "VTODO",
"VFREEBUSY" or "VALARM" calendar components. "VFREEBUSY" or "VALARM" calendar components.
Description: In a "VEVENT" calendar component the property may be Description: In a "VEVENT" calendar component the property may be
used to specify a duration of the event, instead of an explicit used to specify a duration of the event, instead of an explicit
end date/time. In a "VTODO" calendar component the property may end date/time. In a "VTODO" calendar component the property may
be used to specify a duration for the to-do, instead of an be used to specify a duration for the to-do, instead of an
explicit due date/time. In a "VFREEBUSY" calendar component the explicit due date/time. In a "VFREEBUSY" calendar component the
property may be used to specify the interval of free time being property may be used to specify the interval of free time being
requested. In a "VALARM" calendar component the property may be requested. In a "VALARM" calendar component the property may be
used to specify the delay period prior to repeating an alarm. used to specify the delay period prior to repeating an alarm.
Format Definition: The property is defined by the following notation: Format Definition: This property is defined by the following
notation:
duration = "DURATION" durparam ":" dur-value CRLF duration = "DURATION" durparam ":" dur-value CRLF
;consisting of a positive duration of time. ;consisting of a positive duration of time.
durparam = *(";" xparam) durparam = *(";" xparam)
Example: The following is an example of this property that specifies Example: The following is an example of this property that specifies
an interval of time of 1 hour and zero minutes and zero seconds: an interval of time of 1 hour and zero minutes and zero seconds:
DURATION:PT1H0M0S DURATION:PT1H0M0S
The following is an example of this property that specifies an The following is an example of this property that specifies an
interval of time of 15 minutes. interval of time of 15 minutes.
DURATION:PT15M DURATION:PT15M
3.8.2.6. Free/Busy Time 3.8.2.6. Free/Busy Time
Property Name: FREEBUSY Property Name: FREEBUSY
Purpose: The property defines one or more free or busy time Purpose: This property defines one or more free or busy time
intervals. intervals.
Value Type: PERIOD. The date and time values MUST be in a UTC time Value Type: PERIOD
format.
Property Parameters: Non-standard or free/busy time type property Property Parameters: Non-standard or free/busy time type property
parameters can be specified on this property. parameters can be specified on this property.
Conformance: The property can be specified in a "VFREEBUSY" calendar Conformance: The property can be specified in a "VFREEBUSY" calendar
component. component.
Description: These time periods can be specified as either a start Description: These time periods can be specified as either a start
and end date-time or a start date-time and duration. The date and and end date-time or a start date-time and duration. The date and
time MUST be a UTC time format. time MUST be a UTC time format.
skipping to change at page 98, line 19 skipping to change at page 99, line 27
"FREEBUSY" properties within the "VFREEBUSY" calendar component "FREEBUSY" properties within the "VFREEBUSY" calendar component
SHOULD be sorted in ascending order, based on start time and then SHOULD be sorted in ascending order, based on start time and then
end time, with the earliest periods first. end time, with the earliest periods first.
The "FREEBUSY" property can specify more than one value, separated The "FREEBUSY" property can specify more than one value, separated
by the COMMA character (US-ASCII decimal 44). In such cases, the by the COMMA character (US-ASCII decimal 44). In such cases, the
"FREEBUSY" property values SHOULD all be of the same "FBTYPE" "FREEBUSY" property values SHOULD all be of the same "FBTYPE"
property parameter type (e.g., all values of a particular "FBTYPE" property parameter type (e.g., all values of a particular "FBTYPE"
listed together in a single property). listed together in a single property).
Format Definition: The property is defined by the following notation: Format Definition: This property is defined by the following
notation:
freebusy = "FREEBUSY" fbparam ":" fbvalue CRLF freebusy = "FREEBUSY" fbparam ":" fbvalue CRLF
fbparam = *( fbparam = *(
; the following is optional, ; the following is OPTIONAL,
; but MUST NOT occur more than once ; but MUST NOT occur more than once
(";" fbtypeparam) / (";" fbtypeparam) /
; the following is optional, ; the following is OPTIONAL,
; and MAY occur more than once ; and MAY occur more than once
(";" xparam) (";" xparam)
) )
fbvalue = period *("," period) fbvalue = period *("," period)
;Time value MUST be in the UTC time format. ;Time value MUST be in the UTC time format.
Example: The following are some examples of this property: Example: The following are some examples of this property:
skipping to change at page 99, line 4 skipping to change at page 100, line 13
Example: The following are some examples of this property: Example: The following are some examples of this property:
FREEBUSY;FBTYPE=BUSY-UNAVAILABLE:19970308T160000Z/PT8H30M FREEBUSY;FBTYPE=BUSY-UNAVAILABLE:19970308T160000Z/PT8H30M
FREEBUSY;FBTYPE=FREE:19970308T160000Z/PT3H,19970308T200000Z/PT1H FREEBUSY;FBTYPE=FREE:19970308T160000Z/PT3H,19970308T200000Z/PT1H
FREEBUSY;FBTYPE=FREE:19970308T160000Z/PT3H,19970308T200000Z/PT1H FREEBUSY;FBTYPE=FREE:19970308T160000Z/PT3H,19970308T200000Z/PT1H
,19970308T230000Z/19970309T000000Z ,19970308T230000Z/19970309T000000Z
3.8.2.7. Time Transparency 3.8.2.7. Time Transparency
Property Name: TRANSP Property Name: TRANSP
Purpose: This property defines whether an event is transparent or not Purpose: This property defines whether an event is transparent or
to busy time searches. not to busy time searches.
Value Type: TEXT Value Type: TEXT
Property Parameters: Non-standard property parameters can be Property Parameters: Non-standard property parameters can be
specified on this property. specified on this property.
Conformance: This property can be specified once in a "VEVENT" Conformance: This property can be specified once in a "VEVENT"
calendar component. calendar component.
Description: Time Transparency is the characteristic of an event that Description: Time Transparency is the characteristic of an event
determines whether it appears to consume time on a calendar. that determines whether it appears to consume time on a calendar.
Events that consume actual time for the individual or resource Events that consume actual time for the individual or resource
associated with the calendar SHOULD be recorded as OPAQUE, associated with the calendar SHOULD be recorded as OPAQUE,
allowing them to be detected by free-busy time searches. Other allowing them to be detected by free-busy time searches. Other
events, which do not take up the individual's (or resource's) time events, which do not take up the individual's (or resource's) time
SHOULD be recorded as TRANSPARENT, making them invisible to free- SHOULD be recorded as TRANSPARENT, making them invisible to free-
busy time searches. busy time searches.
Format Definition: The property is defined by the following notation: Format Definition: This property is defined by the following
notation:
transp = "TRANSP" transparam ":" transvalue CRLF transp = "TRANSP" transparam ":" transvalue CRLF
transparam = *(";" xparam) transparam = *(";" xparam)
transvalue = "OPAQUE" transvalue = "OPAQUE"
;Blocks or opaque on busy time searches. ;Blocks or opaque on busy time searches.
/ "TRANSPARENT" / "TRANSPARENT"
;Transparent on busy time searches. ;Transparent on busy time searches.
;Default value is OPAQUE ;Default value is OPAQUE
skipping to change at page 100, line 21 skipping to change at page 101, line 35
Value Type: TEXT Value Type: TEXT
Property Parameters: Non-standard property parameters can be Property Parameters: Non-standard property parameters can be
specified on this property. specified on this property.
Conformance: This property MUST be specified in a "VTIMEZONE" Conformance: This property MUST be specified in a "VTIMEZONE"
calendar component. calendar component.
Description: This is the label by which a time zone calendar Description: This is the label by which a time zone calendar
component is referenced by any iCalendar properties whose data component is referenced by any iCalendar properties whose value
type is either DATE-TIME or TIME and not intended to specify a UTC type is either DATE-TIME or TIME and not intended to specify a UTC
or a "floating" time. The presence of the SOLIDUS character (US- or a "floating" time. The presence of the SOLIDUS character (US-
ASCII decimal 47) as a prefix, indicates that this TZID represents ASCII decimal 47) as a prefix, indicates that this "TZID"
an unique ID in a globally defined time zone registry (when such represents an unique ID in a globally defined time zone registry
registry is defined). (when such registry is defined).
Note: This document does not define a naming convention for Note: This document does not define a naming convention for
time zone identifiers. Implementers may want to use the naming time zone identifiers. Implementers may want to use the naming
conventions defined in existing time zone specifications such conventions defined in existing time zone specifications such
as the public-domain Olson database [TZDB]. The specification as the public-domain TZ Database [TZDB]. The specification of
of globally unique time zone identifiers is not addressed by globally unique time zone identifiers is not addressed by this
this document and is left for future study. document and is left for future study.
Format Definition: The property is defined by the following notation: Format Definition: This property is defined by the following
notation:
tzid = "TZID" tzidpropparam ":" [tzidprefix] text CRLF tzid = "TZID" tzidpropparam ":" [tzidprefix] text CRLF
tzidpropparam = *(";" xparam) tzidpropparam = *(";" xparam)
;tzidprefix = "/" ;tzidprefix = "/"
; Defined previously. Just listed here for reader convenience. ; Defined previously. Just listed here for reader convenience.
Example: The following are examples of non-globally unique time zone Example: The following are examples of non-globally unique time zone
identifiers: identifiers:
skipping to change at page 101, line 4 skipping to change at page 102, line 21
;tzidprefix = "/" ;tzidprefix = "/"
; Defined previously. Just listed here for reader convenience. ; Defined previously. Just listed here for reader convenience.
Example: The following are examples of non-globally unique time zone Example: The following are examples of non-globally unique time zone
identifiers: identifiers:
TZID:US-Eastern TZID:US-Eastern
TZID:California-Los_Angeles TZID:California-Los_Angeles
The following is an example of a fictitious globally unique time The following is an example of a fictitious globally unique time
zone identifier: zone identifier:
TZID:/US-New_York-New_York TZID:/US-New_York-New_York
3.8.3.2. Time Zone Name 3.8.3.2. Time Zone Name
Property Name: TZNAME Property Name: TZNAME
Purpose: This property specifies the customary designation for a time Purpose: This property specifies the customary designation for a
zone description. time zone description.
Value Type: TEXT Value Type: TEXT
Property Parameters: Non-standard and language property parameters Property Parameters: Non-standard and language property parameters
can be specified on this property. can be specified on this property.
Conformance: This property can be specified in a "VTIMEZONE" calendar Conformance: This property can be specified in a "VTIMEZONE"
component. calendar component.
Description: This property may be specified in multiple languages; in Description: This property may be specified in multiple languages;
order to provide for different language requirements. in order to provide for different language requirements.
Format Definition: The property is defined by the following notation: Format Definition: This property is defined by the following
notation:
tzname = "TZNAME" tznparam ":" text CRLF tzname = "TZNAME" tznparam ":" text CRLF
tznparam = *( tznparam = *(
; the following is optional, ; the following is OPTIONAL,
; but MUST NOT occur more than once ; but MUST NOT occur more than once
(";" languageparam) / (";" languageparam) /
; the following is optional, ; the following is OPTIONAL,
; and MAY occur more than once ; and MAY occur more than once
(";" xparam) (";" xparam)
) )
Example: The following are example of this property: Example: The following are example of this property:
TZNAME:EST TZNAME:EST
The following is an example of this property when two different The following is an example of this property when two different
languages for the time zone name are specified: languages for the time zone name are specified:
TZNAME;LANGUAGE=en:EST TZNAME;LANGUAGE=en:EST
TZNAME;LANGUAGE=fr-CA:HNE TZNAME;LANGUAGE=fr-CA:HNE
3.8.3.3. Time Zone Offset From 3.8.3.3. Time Zone Offset From
Property Name: TZOFFSETFROM Property Name: TZOFFSETFROM
skipping to change at page 102, line 25 skipping to change at page 103, line 46
this time zone observance. this time zone observance.
Value Type: UTC-OFFSET Value Type: UTC-OFFSET
Property Parameters: Non-standard property parameters can be Property Parameters: Non-standard property parameters can be
specified on this property. specified on this property.
Conformance: This property MUST be specified in a "VTIMEZONE" Conformance: This property MUST be specified in a "VTIMEZONE"
calendar component. calendar component.
Description: This property specifies the offset which is in use prior Description: This property specifies the offset which is in use
to this time observance. It is used to calculate the absolute prior to this time observance. It is used to calculate the
time at which the transition to a given observance takes place. absolute time at which the transition to a given observance takes
This property MUST only be specified in a "VTIMEZONE" calendar place. This property MUST only be specified in a "VTIMEZONE"
component. A "VTIMEZONE" calendar component MUST include this calendar component. A "VTIMEZONE" calendar component MUST include
property. The property value is a signed numeric indicating the this property. The property value is a signed numeric indicating
number of hours and possibly minutes from UTC. Positive numbers the number of hours and possibly minutes from UTC. Positive
represent time zones east of the prime meridian, or ahead of UTC. numbers represent time zones east of the prime meridian, or ahead
Negative numbers represent time zones west of the prime meridian, of UTC. Negative numbers represent time zones west of the prime
or behind UTC. meridian, or behind UTC.
Format Definition: The property is defined by the following notation: Format Definition: This property is defined by the following
notation:
tzoffsetfrom = "TZOFFSETFROM" frmparam ":" utc-offset tzoffsetfrom = "TZOFFSETFROM" frmparam ":" utc-offset
CRLF CRLF
frmparam = *(";" xparam) frmparam = *(";" xparam)
Example: The following are examples of this property: Example: The following are examples of this property:
TZOFFSETFROM:-0500 TZOFFSETFROM:-0500
skipping to change at page 103, line 28 skipping to change at page 104, line 45
calendar component. calendar component.
Description: This property specifies the offset which is in use in Description: This property specifies the offset which is in use in
this time zone observance. It is used to calculate the absolute this time zone observance. It is used to calculate the absolute
time for the new observance. The property value is a signed time for the new observance. The property value is a signed
numeric indicating the number of hours and possibly minutes from numeric indicating the number of hours and possibly minutes from
UTC. Positive numbers represent time zones east of the prime UTC. Positive numbers represent time zones east of the prime
meridian, or ahead of UTC. Negative numbers represent time zones meridian, or ahead of UTC. Negative numbers represent time zones
west of the prime meridian, or behind UTC. west of the prime meridian, or behind UTC.
Format Definition: The property is defined by the following notation: Format Definition: This property is defined by the following
notation:
tzoffsetto = "TZOFFSETTO" toparam ":" utc-offset CRLF tzoffsetto = "TZOFFSETTO" toparam ":" utc-offset CRLF
toparam = *(";" xparam) toparam = *(";" xparam)
Example: The following are examples of this property: Example: The following are examples of this property:
TZOFFSETTO:-0400 TZOFFSETTO:-0400
TZOFFSETTO:+1245 TZOFFSETTO:+1245
3.8.3.5. Time Zone URL 3.8.3.5. Time Zone URL
Property Name: TZURL Property Name: TZURL
skipping to change at page 103, line 44 skipping to change at page 105, line 14
Example: The following are examples of this property: Example: The following are examples of this property:
TZOFFSETTO:-0400 TZOFFSETTO:-0400
TZOFFSETTO:+1245 TZOFFSETTO:+1245
3.8.3.5. Time Zone URL 3.8.3.5. Time Zone URL
Property Name: TZURL Property Name: TZURL
Purpose: The TZURL provides a means for a VTIMEZONE component to Purpose: This property provides a means for a "VTIMEZONE" component
point to a network location that can be used to retrieve an up-to- to point to a network location that can be used to retrieve an up-
date version of itself. to-date version of itself.
Value Type: URI Value Type: URI
Property Parameters: Non-standard property parameters can be Property Parameters: Non-standard property parameters can be
specified on this property. specified on this property.
Conformance: This property can be specified in a "VTIMEZONE" calendar Conformance: This property can be specified in a "VTIMEZONE"
component. calendar component.
Description: The TZURL provides a means for a VTIMEZONE component to Description: This property provides a means for a "VTIMEZONE"
point to a network location that can be used to retrieve an up-to- component to point to a network location that can be used to
date version of itself. This provides a hook to handle changes retrieve an up-to-date version of itself. This provides a hook to
government bodies impose upon time zone definitions. Retrieval of handle changes government bodies impose upon time zone
this resource results in an iCalendar object containing a single definitions. Retrieval of this resource results in an iCalendar
VTIMEZONE component and a METHOD property set to PUBLISH. object containing a single "VTIMEZONE" component and a "METHOD"
property set to PUBLISH.
Format Definition: The property is defined by the following notation: Format Definition: This property is defined by the following
notation:
tzurl = "TZURL" tzurlparam ":" uri CRLF tzurl = "TZURL" tzurlparam ":" uri CRLF
tzurlparam = *(";" xparam) tzurlparam = *(";" xparam)
Example: The following is an example of this property: Example: The following is an example of this property:
TZURL:http://timezones.r.us.net/tz/US-California-Los_Angeles.ics TZURL:http://timezones.example.org/tz/US-California-Los_Angeles.ics
3.8.4. Relationship Component Properties 3.8.4. Relationship Component Properties
The following properties specify relationship information in calendar The following properties specify relationship information in calendar
components. components.
3.8.4.1. Attendee 3.8.4.1. Attendee
Property Name: ATTENDEE Property Name: ATTENDEE
Purpose: The property defines an "Attendee" within a calendar Purpose: This property defines an "Attendee" within a calendar
component. component.
Value Type: CAL-ADDRESS Value Type: CAL-ADDRESS
Property Parameters: Non-standard, language, calendar user type, Property Parameters: Non-standard, language, calendar user type,
group or list membership, participation role, participation group or list membership, participation role, participation
status, RSVP expectation, delegatee, delegator, sent by, common status, RSVP expectation, delegatee, delegator, sent by, common
name or directory entry reference property parameters can be name or directory entry reference property parameters can be
specified on this property. specified on this property.
Conformance: This property MUST be specified in an iCalendar object Conformance: This property MUST be specified in an iCalendar object
that specifies a group scheduled calendar entity. This property that specifies a group scheduled calendar entity. This property
MUST NOT be specified in an iCalendar object when publishing the MUST NOT be specified in an iCalendar object when publishing the
calendar information (e.g., NOT in an iCalendar object that calendar information (e.g., NOT in an iCalendar object that
specifies the publication of a calendar user's busy time, event, specifies the publication of a calendar user's busy time, event,
to-do or journal). This property is not specified in an iCalendar to-do or journal). This property is not specified in an iCalendar
object that specifies only a time zone definition or that defines object that specifies only a time zone definition or that defines
calendar entities that are not group scheduled entities, but are calendar components that are not group scheduled components, but
entities only on a single user's calendar. are components only on a single user's calendar.
Description: The property MUST only be specified within calendar Description: This property MUST only be specified within calendar
components to specify participants, non-participants and the chair components to specify participants, non-participants and the chair
of a group scheduled calendar entity. The property is specified of a group scheduled calendar entity. The property is specified
within an "EMAIL" category of the "VALARM" calendar component to within an "EMAIL" category of the "VALARM" calendar component to
specify an email address that is to receive the email type of specify an email address that is to receive the email type of
iCalendar alarm. iCalendar alarm.
The property parameter CN is for the common or displayable name The property parameter "CN" is for the common or displayable name
associated with the calendar address; ROLE, for the intended role associated with the calendar address; "ROLE", for the intended
that the attendee will have in the calendar component; PARTSTAT, role that the attendee will have in the calendar component;
for the status of the attendee's participation; RSVP, for "PARTSTAT", for the status of the attendee's participation;
indicating whether the favor of a reply is requested; CUTYPE, to "RSVP", for indicating whether the favor of a reply is requested;
indicate the type of calendar user; MEMBER, to indicate the groups "CUTYPE", to indicate the type of calendar user; "MEMBER", to
that the attendee belongs to; DELEGATED-TO, to indicate the indicate the groups that the attendee belongs to; "DELEGATED-TO",
calendar users that the original request was delegated to; and to indicate the calendar users that the original request was
DELEGATED-FROM, to indicate whom the request was delegated from; delegated to; and "DELEGATED-FROM", to indicate whom the request
SENT-BY, to indicate whom is acting on behalf of the ATTENDEE; and was delegated from; "SENT-BY", to indicate whom is acting on
DIR, to indicate the URI that points to the directory information behalf of the "ATTENDEE"; and "DIR", to indicate the URI that
corresponding to the attendee. These property parameters can be points to the directory information corresponding to the attendee.
specified on an "ATTENDEE" property in either a "VEVENT", "VTODO" These property parameters can be specified on an "ATTENDEE"
or "VJOURNAL" calendar component. They MUST NOT be specified in property in either a "VEVENT", "VTODO" or "VJOURNAL" calendar
an "ATTENDEE" property in a "VFREEBUSY" or "VALARM" calendar component. They MUST NOT be specified in an "ATTENDEE" property
component. If the LANGUAGE property parameter is specified, the in a "VFREEBUSY" or "VALARM" calendar component. If the
identified language applies to the CN parameter. "LANGUAGE" property parameter is specified, the identified
language applies to the "CN" parameter.
A recipient delegated a request MUST inherit the RSVP and ROLE A recipient delegated a request MUST inherit the "RSVP" and "ROLE"
values from the attendee that delegated the request to them. values from the attendee that delegated the request to them.
Multiple attendees can be specified by including multiple Multiple attendees can be specified by including multiple
"ATTENDEE" properties within the calendar component. "ATTENDEE" properties within the calendar component.
Format Definition: The property is defined by the following notation: Format Definition: This property is defined by the following
notation:
attendee = "ATTENDEE" attparam ":" cal-address CRLF attendee = "ATTENDEE" attparam ":" cal-address CRLF
attparam = *( attparam = *(
; the following are optional, ; the following are OPTIONAL,
; but MUST NOT occur more than once ; but MUST NOT occur more than once
(";" cutypeparam) / (";" memberparam) / (";" cutypeparam) / (";" memberparam) /
(";" roleparam) / (";" partstatparam) / (";" roleparam) / (";" partstatparam) /
(";" rsvpparam) / (";" deltoparam) / (";" rsvpparam) / (";" deltoparam) /
(";" delfromparam) / (";" sentbyparam) / (";" delfromparam) / (";" sentbyparam) /
(";" cnparam) / (";" dirparam) / (";" cnparam) / (";" dirparam) /
(";" languageparam) / (";" languageparam) /
; the following is optional, ; the following is OPTIONAL,
; and MAY occur more than once ; and MAY occur more than once
(";" xparam) (";" xparam)
) )
Example: The following are examples of this property's use for a Example: The following are examples of this property's use for a
to-do: to-do:
ORGANIZER:MAILTO:jsmith@example.com ORGANIZER:mailto:jsmith@example.com
ATTENDEE;MEMBER="MAILTO:DEV-GROUP@example.com": ATTENDEE;MEMBER="mailto:DEV-GROUP@example.com":
MAILTO:joecool@example.com mailto:joecool@example.com
ATTENDEE;DELEGATED-FROM="MAILTO:immud@example.com": ATTENDEE;DELEGATED-FROM="mailto:immud@example.com":
MAILTO:ildoit@example.com mailto:ildoit@example.com
The following is an example of this property used for specifying The following is an example of this property used for specifying
multiple attendees to an event: multiple attendees to an event:
ORGANIZER:MAILTO:jsmith@example.com ORGANIZER:mailto:jsmith@example.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=TENTATIVE;CN=Henry ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=TENTATIVE;CN=Henry
Cabot:MAILTO:hcabot@example.com Cabot:mailto:hcabot@example.com
ATTENDEE;ROLE=REQ-PARTICIPANT;DELEGATED-FROM="MAILTO:bob@ ATTENDEE;ROLE=REQ-PARTICIPANT;DELEGATED-FROM="mailto:bob@
example.com" example.com"
;PARTSTAT=ACCEPTED;CN=Jane Doe:MAILTO:jdoe@example.com ;PARTSTAT=ACCEPTED;CN=Jane Doe:mailto:jdoe@example.com
The following is an example of this property with a URI to the The following is an example of this property with a URI to the
directory information associated with the attendee: directory information associated with the attendee:
ATTENDEE;CN=John Smith;DIR="ldap://example.com:6666/o=ABC% ATTENDEE;CN=John Smith;DIR="ldap://example.com:6666/o=ABC%
20Industries,c=US???(cn=Jim%20Dolittle)":MAILTO:jimdo@ 20Industries,c=US???(cn=Jim%20Dolittle)":mailto:jimdo@
example.com example.com
The following is an example of this property with "delegatee" and The following is an example of this property with "delegatee" and
"delegator" information for an event: "delegator" information for an event:
ORGANIZER;CN=John Smith:MAILTO:jsmith@example.com ORGANIZER;CN=John Smith:mailto:jsmith@example.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=TENTATIVE;DELEGATED-FROM= ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=TENTATIVE;DELEGATED-FROM=
"MAILTO:iamboss@example.com";CN=Henry Cabot:MAILTO:hcabot@ "mailto:iamboss@example.com";CN=Henry Cabot:mailto:hcabot@
example.com example.com
ATTENDEE;ROLE=NON-PARTICIPANT;PARTSTAT=DELEGATED;DELEGATED-TO= ATTENDEE;ROLE=NON-PARTICIPANT;PARTSTAT=DELEGATED;DELEGATED-TO=
"MAILTO:hcabot@example.com";CN=The Big Cheese:MAILTO:iamboss "mailto:hcabot@example.com";CN=The Big Cheese:mailto:iamboss
@example.com @example.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=ACCEPTED;CN=Jane Doe ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=ACCEPTED;CN=Jane Doe
:MAILTO:jdoe@example.com :mailto:jdoe@example.com
Example: The following is an example of this property's use when Example: The following is an example of this property's use when
another calendar user is acting on behalf of the "Attendee": another calendar user is acting on behalf of the "Attendee":
ATTENDEE;SENT-BY=MAILTO:jan_doe@example.com;CN=John Smith:MAILTO: ATTENDEE;SENT-BY=mailto:jan_doe@example.com;CN=John Smith:
jsmith@example.com mailto:jsmith@example.com
3.8.4.2. Contact 3.8.4.2. Contact
Property Name: CONTACT Property Name: CONTACT
Purpose: The property is used to represent contact information or Purpose: This property is used to represent contact information or
alternately a reference to contact information associated with the alternately a reference to contact information associated with the
calendar component. calendar component.
Value Type: TEXT Value Type: TEXT
Property Parameters: Non-standard, alternate text representation and Property Parameters: Non-standard, alternate text representation and
language property parameters can be specified on this property. language property parameters can be specified on this property.
Conformance: The property can be specified in a "VEVENT", "VTODO", Conformance: This property can be specified in a "VEVENT", "VTODO",
"VJOURNAL" or "VFREEBUSY" calendar component. "VJOURNAL" or "VFREEBUSY" calendar component.
Description: The property value consists of textual contact Description: The property value consists of textual contact
information. An alternative representation for the property value information. An alternative representation for the property value
can also be specified that refers to a URI pointing to an can also be specified that refers to a URI pointing to an
alternate form, such as a vCard [RFC2426], for the contact alternate form, such as a vCard [RFC2426], for the contact
information. information.
Format Definition: The property is defined by the following notation: Format Definition: This property is defined by the following
notation:
contact = "CONTACT" contparam ":" text CRLF contact = "CONTACT" contparam ":" text CRLF
contparam = *( contparam = *(
; the following are optional, ; the following are OPTIONAL,
; but MUST NOT occur more than once ; but MUST NOT occur more than once
(";" altrepparam) / (";" languageparam) / (";" altrepparam) / (";" languageparam) /
; the following is optional, ; the following is OPTIONAL,
; and MAY occur more than once ; and MAY occur more than once
(";" xparam) (";" xparam)
) )
Example: The following is an example of this property referencing Example: The following is an example of this property referencing
textual contact information: textual contact information:
CONTACT:Jim Dolittle\, ABC Industries\, +1-919-555-1234 CONTACT:Jim Dolittle\, ABC Industries\, +1-919-555-1234
skipping to change at page 108, line 40 skipping to change at page 110, line 4
c=US???(cn=Jim%20Dolittle)":Jim Dolittle\, ABC Industries\, c=US???(cn=Jim%20Dolittle)":Jim Dolittle\, ABC Industries\,
+1-919-555-1234 +1-919-555-1234
The following is an example of this property with an alternate The following is an example of this property with an alternate
representation of a MIME body part containing the contact representation of a MIME body part containing the contact
information, such as a vCard [RFC2426] embedded in a text/ information, such as a vCard [RFC2426] embedded in a text/
directory media type [RFC2425]: directory media type [RFC2425]:
CONTACT;ALTREP="CID:part3.msg970930T083000SILVER@example.com": CONTACT;ALTREP="CID:part3.msg970930T083000SILVER@example.com":
Jim Dolittle\, ABC Industries\, +1-919-555-1234 Jim Dolittle\, ABC Industries\, +1-919-555-1234
The following is an example of this property referencing a network The following is an example of this property referencing a network
resource, such as a vCard [RFC2426] object containing the contact resource, such as a vCard [RFC2426] object containing the contact
information: information:
CONTACT;ALTREP="http://example.com/pdi/jdoe.vcf":Jim CONTACT;ALTREP="http://example.com/pdi/jdoe.vcf":Jim
Dolittle\, ABC Industries\, +1-919-555-1234 Dolittle\, ABC Industries\, +1-919-555-1234
3.8.4.3. Organizer 3.8.4.3. Organizer
Property Name: ORGANIZER Property Name: ORGANIZER
Purpose: The property defines the organizer for a calendar component. Purpose: This property defines the organizer for a calendar
component.
Value Type: CAL-ADDRESS Value Type: CAL-ADDRESS
Property Parameters: Non-standard, language, common name, directory Property Parameters: Non-standard, language, common name, directory
entry reference, sent by property parameters can be specified on entry reference, sent by property parameters can be specified on
this property. this property.
Conformance: This property MUST be specified in an iCalendar object Conformance: This property MUST be specified in an iCalendar object
that specifies a group scheduled calendar entity. This property that specifies a group scheduled calendar entity. This property
MUST be specified in an iCalendar object that specifies the MUST be specified in an iCalendar object that specifies the
publication of a calendar user's busy time. This property MUST publication of a calendar user's busy time. This property MUST
NOT be specified in an iCalendar object that specifies only a time NOT be specified in an iCalendar object that specifies only a time
zone definition or that defines calendar entities that are not zone definition or that defines calendar components that are not
group scheduled entities, but are entities only on a single user's group scheduled components, but are components only on a single
calendar. user's calendar.
Description: The property is specified within the "VEVENT", "VTODO", Description: This property is specified within the "VEVENT",
"VJOURNAL" calendar components to specify the organizer of a group "VTODO", "VJOURNAL" calendar components to specify the organizer
scheduled calendar entity. The property is specified within the of a group scheduled calendar entity. The property is specified
"VFREEBUSY" calendar component to specify the calendar user within the "VFREEBUSY" calendar component to specify the calendar
requesting the free or busy time. When publishing a "VFREEBUSY" user requesting the free or busy time. When publishing a
calendar component, the property is used to specify the calendar "VFREEBUSY" calendar component, the property is used to specify
that the published busy time came from. the calendar that the published busy time came from.
The property has the property parameters CN, for specifying the The property has the property parameters "CN", for specifying the
common or display name associated with the "Organizer", DIR, for common or display name associated with the "Organizer", "DIR", for
specifying a pointer to the directory information associated with specifying a pointer to the directory information associated with
the "Organizer", SENT-BY, for specifying another calendar user the "Organizer", "SENT-BY", for specifying another calendar user
that is acting on behalf of the "Organizer". The non-standard that is acting on behalf of the "Organizer". The non-standard
parameters may also be specified on this property. If the parameters may also be specified on this property. If the
LANGUAGE property parameter is specified, the identified language "LANGUAGE" property parameter is specified, the identified
applies to the CN parameter value. language applies to the "CN" parameter value.
Format Definition: The property is defined by the following notation: Format Definition: This property is defined by the following
notation:
organizer = "ORGANIZER" orgparam ":" organizer = "ORGANIZER" orgparam ":"
cal-address CRLF cal-address CRLF
orgparam = *( orgparam = *(
; the following are optional, ; the following are OPTIONAL,
; but MUST NOT occur more than once ; but MUST NOT occur more than once
(";" cnparam) / (";" dirparam) / (";" sentbyparam) / (";" cnparam) / (";" dirparam) / (";" sentbyparam) /
(";" languageparam) / (";" languageparam) /
; the following is optional, ; the following is OPTIONAL,
; and MAY occur more than once ; and MAY occur more than once
(";" xparam) (";" xparam)
) )
Example: The following is an example of this property: Example: The following is an example of this property:
ORGANIZER;CN=John Smith:MAILTO:jsmith@example.com ORGANIZER;CN=John Smith:mailto:jsmith@example.com
The following is an example of this property with a pointer to the The following is an example of this property with a pointer to the
directory information associated with the organizer: directory information associated with the organizer:
ORGANIZER;CN=JohnSmith;DIR="ldap://example.com:6666/o=DC%20Ass ORGANIZER;CN=JohnSmith;DIR="ldap://example.com:6666/o=DC%20Ass
ociates,c=US???(cn=John%20Smith)":MAILTO:jsmith@example.com ociates,c=US???(cn=John%20Smith)":mailto:jsmith@example.com
The following is an example of this property used by another The following is an example of this property used by another
calendar user who is acting on behalf of the organizer, with calendar user who is acting on behalf of the organizer, with
responses intended to be sent back to the organizer, not the other responses intended to be sent back to the organizer, not the other
calendar user: calendar user:
ORGANIZER;SENT-BY="MAILTO:jane_doe@example.com": ORGANIZER;SENT-BY="mailto:jane_doe@example.com":
MAILTO:jsmith@example.com mailto:jsmith@example.com
3.8.4.4. Recurrence ID 3.8.4.4. Recurrence ID
Property Name: RECURRENCE-ID Property Name: RECURRENCE-ID
Purpose: This property is used in conjunction with the "UID" and Purpose: This property is used in conjunction with the "UID" and
"SEQUENCE" property to identify a specific instance of a recurring "SEQUENCE" property to identify a specific instance of a recurring
"VEVENT", "VTODO" or "VJOURNAL" calendar component. The property "VEVENT", "VTODO" or "VJOURNAL" calendar component. The property
value is the effective value of the "DTSTART" property of the value is the effective value of the "DTSTART" property of the
recurrence instance. recurrence instance.
Value Type: The default value type for this property is DATE-TIME. Value Type: The default value type for this property is DATE-TIME.
The time format can be any of the valid forms defined for a DATE- The time format can be any of the valid forms defined for a DATE-
TIME value type. See DATE-TIME value type definition for specific TIME value type. See DATE-TIME value type definition for specific
interpretations of the various forms. The value type can be set interpretations of the various forms. The value type can be set
to DATE. to DATE.
Property Parameters: Non-standard property, value data type, time Property Parameters: Non-standard property, value data type, and
zone identifier and recurrence identifier range parameters can be time zone identifier parameters can be specified on this property.
specified on this property.
Conformance: This property can be specified in an iCalendar object Conformance: This property can be specified in an iCalendar object
containing a recurring calendar component. containing a recurring calendar component.
Description: The full range of calendar components specified by a Description: The full range of calendar components specified by a
recurrence set is referenced by referring to just the "UID" recurrence set is referenced by referring to just the "UID"
property value corresponding to the calendar component. The property value corresponding to the calendar component. The
"RECURRENCE-ID" property allows the reference to an individual "RECURRENCE-ID" property allows the reference to an individual
instance within the recurrence set. instance within the recurrence set.
skipping to change at page 111, line 39 skipping to change at page 112, line 38
change a Friday meeting to Thursday, the date/time is still set to change a Friday meeting to Thursday, the date/time is still set to
the original Friday meeting. the original Friday meeting.
The "RECURRENCE-ID" property is used in conjunction with the "UID" The "RECURRENCE-ID" property is used in conjunction with the "UID"
and "SEQUENCE" property to identify a particular instance of a and "SEQUENCE" property to identify a particular instance of a
recurring event, to-do or journal. For a given pair of "UID" and recurring event, to-do or journal. For a given pair of "UID" and
"SEQUENCE" property values, the "RECURRENCE-ID" value for a "SEQUENCE" property values, the "RECURRENCE-ID" value for a
recurrence instance is fixed. When the definition of the recurrence instance is fixed. When the definition of the
recurrence set for a calendar component changes, and hence the recurrence set for a calendar component changes, and hence the
"SEQUENCE" property value changes, the "RECURRENCE-ID" for a given "SEQUENCE" property value changes, the "RECURRENCE-ID" for a given
recurrence instance might also change.The "RANGE" parameter is recurrence instance might also change.
used to specify the effective range of recurrence instances from
the instance specified by the "RECURRENCE-ID" property value. The
default value for the range parameter is the single recurrence
instance only. The value can also be "THISANDPRIOR" to indicate a
range defined by the given recurrence instance and all prior
instances or the value can be "THISANDFUTURE" to indicate a range
defined by the given recurrence instance and all subsequent
instances.
Format Definition: The property is defined by the following notation: Format Definition: This property is defined by the following
notation:
recurid = "RECURRENCE-ID" ridparam ":" ridval CRLF recurid = "RECURRENCE-ID" ridparam ":" ridval CRLF
ridparam = *( ridparam = *(
; the following are optional, ; the following are OPTIONAL,
; but MUST NOT occur more than once ; but MUST NOT occur more than once
(";" "VALUE" "=" ("DATE-TIME" / "DATE")) / (";" "VALUE" "=" ("DATE-TIME" / "DATE")) /
(";" tzidparam) / (";" rangeparam) / (";" tzidparam) /
; the following is optional, ; the following is OPTIONAL,
; and MAY occur more than once ; and MAY occur more than once
(";" xparam) (";" xparam)
) )
ridval = date-time / date ridval = date-time / date
;Value MUST match value type ;Value MUST match value type
Example: The following are examples of this property: Example: The following are examples of this property:
RECURRENCE-ID;VALUE=DATE:19960401 RECURRENCE-ID;VALUE=DATE:19960401
RECURRENCE-ID;RANGE=THISANDFUTURE:19960120T120000Z RECURRENCE-ID:19960120T120000Z
3.8.4.5. Related To 3.8.4.5. Related To
Property Name: RELATED-TO Property Name: RELATED-TO
Purpose: The property is used to represent a relationship or Purpose: This property is used to represent a relationship or
reference between one calendar component and another. reference between one calendar component and another.
Value Type: TEXT Value Type: TEXT
Property Parameters: Non-standard and relationship type property Property Parameters: Non-standard and relationship type property
parameters can be specified on this property. parameters can be specified on this property.
Conformance: The property can be specified one or more times in the Conformance: This property can be specified one or more times in the
"VEVENT", "VTODO" or "VJOURNAL" calendar components. "VEVENT", "VTODO" or "VJOURNAL" calendar components.
Description: The property value consists of the persistent, globally Description: The property value consists of the persistent, globally
unique identifier of another calendar component. This value would unique identifier of another calendar component. This value would
be represented in a calendar component by the "UID" property. be represented in a calendar component by the "UID" property.
By default, the property value points to another calendar By default, the property value points to another calendar
component that has a PARENT relationship to the referencing component that has a PARENT relationship to the referencing
object. The "RELTYPE" property parameter is used to either object. The "RELTYPE" property parameter is used to either
explicitly state the default PARENT relationship type to the explicitly state the default PARENT relationship type to the
skipping to change at page 113, line 30 skipping to change at page 114, line 30
example, if a group event changes its start or end date or time, example, if a group event changes its start or end date or time,
then the related, dependent events will need to have their start then the related, dependent events will need to have their start
and end dates changed in a corresponding way. Similarly, if a and end dates changed in a corresponding way. Similarly, if a
PARENT calendar component is cancelled or deleted, then there is PARENT calendar component is cancelled or deleted, then there is
an implied impact to the related CHILD calendar components. This an implied impact to the related CHILD calendar components. This
property is intended only to provide information on the property is intended only to provide information on the
relationship of calendar components. It is up to the target relationship of calendar components. It is up to the target
calendar system to maintain any property implications of this calendar system to maintain any property implications of this
relationship. relationship.
Format Definition: The property is defined by the following notation: Format Definition: This property is defined by the following
notation:
related = "RELATED-TO" relparam ":" text CRLF related = "RELATED-TO" relparam ":" text CRLF
relparam = *( relparam = *(
; the following is optional, ; the following is OPTIONAL,
; but MUST NOT occur more than once ; but MUST NOT occur more than once
(";" reltypeparam) / (";" reltypeparam) /
; the following is optional, ; the following is OPTIONAL,
; and MAY occur more than once ; and MAY occur more than once
(";" xparam) (";" xparam)
) )
The following is an example of this property: The following is an example of this property:
RELATED-TO:jsmith.part7.19960817T083000.xyzMail@example.com RELATED-TO:jsmith.part7.19960817T083000.xyzMail@example.com
RELATED-TO:19960401-080045-4000F192713-0052@example.com RELATED-TO:19960401-080045-4000F192713-0052@example.com
3.8.4.6. Uniform Resource Locator 3.8.4.6. Uniform Resource Locator
Property Name: URL Property Name: URL
Purpose: This property defines a Uniform Resource Locator (URL) Purpose: This property defines a Uniform Resource Locator (URL)
associated with the iCalendar object. associated with the iCalendar object.
Value Type: URI Value Type: URI
skipping to change at page 114, line 28 skipping to change at page 115, line 33
"VTODO", "VJOURNAL" or "VFREEBUSY" calendar components. "VTODO", "VJOURNAL" or "VFREEBUSY" calendar components.
Description: This property may be used in a calendar component to Description: This property may be used in a calendar component to
convey a location where a more dynamic rendition of the calendar convey a location where a more dynamic rendition of the calendar
information associated with the calendar component can be found. information associated with the calendar component can be found.
This memo does not attempt to standardize the form of the URI, nor This memo does not attempt to standardize the form of the URI, nor
the format of the resource pointed to by the property value. If the format of the resource pointed to by the property value. If
the URL property and Content-Location MIME header are both the URL property and Content-Location MIME header are both
specified, they MUST point to the same resource. specified, they MUST point to the same resource.
Format Definition: The property is defined by the following notation: Format Definition: This property is defined by the following
notation:
url = "URL" urlparam ":" uri CRLF url = "URL" urlparam ":" uri CRLF
urlparam = *(";" xparam) urlparam = *(";" xparam)
Example: The following is an example of this property: Example: The following is an example of this property:
URL:http://abc.com/pub/calendars/jsmith/mytime.ics URL:http://abc.com/pub/calendars/jsmith/mytime.ics
3.8.4.7. Unique Identifier 3.8.4.7. Unique Identifier
skipping to change at page 115, line 5 skipping to change at page 116, line 10
Property Name: UID Property Name: UID
Purpose: This property defines the persistent, globally unique Purpose: This property defines the persistent, globally unique
identifier for the calendar component. identifier for the calendar component.
Value Type: TEXT Value Type: TEXT
Property Parameters: Non-standard property parameters can be Property Parameters: Non-standard property parameters can be
specified on this property. specified on this property.
Conformance: The property MUST be specified in the "VEVENT", "VTODO", Conformance: The property MUST be specified in the "VEVENT",
"VJOURNAL" or "VFREEBUSY" calendar components. "VTODO", "VJOURNAL" or "VFREEBUSY" calendar components.
Description: The UID itself MUST be a globally unique identifier. Description: The "UID" itself MUST be a globally unique identifier.
The generator of the identifier MUST guarantee that the identifier The generator of the identifier MUST guarantee that the identifier
is unique. There are several algorithms that can be used to is unique. There are several algorithms that can be used to
accomplish this. The identifier is RECOMMENDED to be the accomplish this. The identifier is RECOMMENDED to be the
identical syntax to the [RFC2822] addr-spec. A good method to identical syntax to the [RFC2822] addr-spec. A good method to
assure uniqueness is to put the domain name or a domain literal IP assure uniqueness is to put the domain name or a domain literal IP
address of the host on which the identifier was created on the address of the host on which the identifier was created on the
right hand side of the "@", and on the left hand side, put a right hand side of the "@", and on the left hand side, put a
combination of the current calendar date and time of day (i.e., combination of the current calendar date and time of day (i.e.,
formatted in as a DATE-TIME value) along with some other currently formatted in as a DATE-TIME value) along with some other currently
unique (perhaps sequential) identifier available on the system unique (perhaps sequential) identifier available on the system
skipping to change at page 116, line 5 skipping to change at page 117, line 9
or deletion requests. Calendaring and scheduling applications or deletion requests. Calendaring and scheduling applications
MUST generate this property in "VEVENT", "VTODO" and "VJOURNAL" MUST generate this property in "VEVENT", "VTODO" and "VJOURNAL"
calendar components to assure interoperability with other group calendar components to assure interoperability with other group
scheduling applications. This identifier is created by the scheduling applications. This identifier is created by the
calendar system that generates an iCalendar object. calendar system that generates an iCalendar object.
Implementations MUST be able to receive and persist values of at Implementations MUST be able to receive and persist values of at
least 255 octets for this property but MUST NOT truncate values in least 255 octets for this property but MUST NOT truncate values in
the middle of a UTF-8 multi-octet sequence . the middle of a UTF-8 multi-octet sequence .
Format Definition: The property is defined by the following notation: Format Definition: This property is defined by the following
notation:
uid = "UID" uidparam ":" text CRLF uid = "UID" uidparam ":" text CRLF
uidparam = *(";" xparam) uidparam = *(";" xparam)
Example: The following is an example of this property: Example: The following is an example of this property:
UID:19960401T080045Z-4000F192713-0052@example.com UID:19960401T080045Z-4000F192713-0052@example.com
3.8.5. Recurrence Component Properties 3.8.5. Recurrence Component Properties
skipping to change at page 116, line 39 skipping to change at page 117, line 44
The value type can be set to DATE. The value type can be set to DATE.
Property Parameters: Non-standard, value data type and time zone Property Parameters: Non-standard, value data type and time zone
identifier property parameters can be specified on this property. identifier property parameters can be specified on this property.
Conformance: This property can be specified in recurring "VEVENT", Conformance: This property can be specified in recurring "VEVENT",
"VTODO", and "VJOURNAL" calendar components as well as in the "VTODO", and "VJOURNAL" calendar components as well as in the
"STANDARD" and "DAYLIGHT" sub-components of the "VTIMEZONE" "STANDARD" and "DAYLIGHT" sub-components of the "VTIMEZONE"
calendar component. calendar component.
Description: The exception dates, if specified, are used in computing Description: The exception dates, if specified, are used in
the recurrence set. The recurrence set is the complete set of computing the recurrence set. The recurrence set is the complete
recurrence instances for a calendar component. The recurrence set set of recurrence instances for a calendar component. The
is generated by considering the initial "DTSTART" property along recurrence set is generated by considering the initial "DTSTART"
with the "RRULE", "RDATE", and "EXDATE" properties contained property along with the "RRULE", "RDATE", and "EXDATE" properties
within the recurring component. The "DTSTART" property defines contained within the recurring component. The "DTSTART" property
the first instance in the recurrence set. The "DTSTART" property defines the first instance in the recurrence set. The "DTSTART"
value SHOULD match the pattern of the recurrence rule, if property value SHOULD match the pattern of the recurrence rule, if
specified. The recurrence set generated with a "DTSTART" property specified. The recurrence set generated with a "DTSTART" property
value that doesn't match the pattern of the rule is undefined. value that doesn't match the pattern of the rule is undefined.
The final recurrence set is generated by gathering all of the The final recurrence set is generated by gathering all of the
start date-times generated by any of the specified "RRULE" and start date-times generated by any of the specified "RRULE" and
"RDATE" properties, and then excluding any start date and times "RDATE" properties, and then excluding any start date and times
specified by "EXDATE" properties. This implies that start date specified by "EXDATE" properties. This implies that start date
and times specified by "EXDATE" properties take precedence over and times specified by "EXDATE" properties take precedence over
those specified by inclusion properties (i.e., "RDATE" and those specified by inclusion properties (i.e., "RDATE" and
"RRULE"). Where duplicate instances are generated by the "RRULE" "RRULE"). Where duplicate instances are generated by the "RRULE"
and "RDATE" properties, only one recurrence is considered. and "RDATE" properties, only one recurrence is considered.
Duplicate instances are ignored. Duplicate instances are ignored.