draft-ietf-calsch-ical-07.txt   draft-ietf-calsch-ical-08.txt 
Network Working Group Frank Dawson, Lotus Network Working Group Frank Dawson, Lotus
Internet Draft Derik Stenerson, Microsoft Internet Draft Derik Stenerson, Microsoft
<draft-ietf-calsch-ical-07.txt <draft-ietf-calsch-ical-08.txt>
Expires six months after May 11, 1998 Expires six months after: June 29, 1998
Internet Calendaring and Scheduling Core Object Specification Internet Calendaring and Scheduling Core Object Specification
(iCalendar) (iCalendar)
Status of this Memo Status of this Memo
This memo is an Internet-Draft. Internet-Drafts are working documents This memo is an Internet-Draft. Internet-Drafts are working documents
of the Internet Engineering Task Force (IETF), its areas, and its of the Internet Engineering Task Force (IETF), its areas, and its
working groups. Note that other groups can also distribute working working groups. Note that other groups can also distribute working
documents as Internet-Drafts. documents as Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six Internet-Drafts are draft documents valid for a maximum of six
months. Internet-Drafts can be updated, replaced, or made obsolete by months. Internet-Drafts can be updated, replaced, or made obsolete by
other documents at any time. It is not appropriate to use Internet- other documents at any time. It is not appropriate to use Internet-
Drafts as reference material or to cite them other than as a "working Drafts as reference material or to cite them other than as a "working
draft" or "work in progress". draft" or "work in progress".
To view the entire list of current Internet-Drafts, please check To view the entire list of current Internet-Drafts, please check the
the "1id-abstracts.txt" listing contained in the Internet-Drafts "1id-abstracts.txt" listing contained in the Internet-Drafts Shadow
Shadow Directories on ftp.is.co.za (Africa), ftp.nordu.net Directories on ftp.is.co.za (Africa), ftp.nordu.net (Northern
(Northern Europe), ftp.nis.garr.it (Southern Europe), munnari.oz.au Europe), ftp.nis.garr.it (Southern Europe), munnari.oz.au (Pacific
(Pacific Rim), ftp.ietf.org (US East Coast), or ftp.isi.edu Rim), ftp.ietf.org (US East Coast), or ftp.isi.edu (US West Coast).
(US West Coast).
Distribution of this memo is unlimited. Distribution of this memo is unlimited.
Copyright (C) The Internet Society 1997. All Rights Reserved. Copyright (C) The Internet Society 1997. All Rights Reserved.
Abstract Abstract
There is a clear need to provide and deploy interoperable calendaring There is a clear need to provide and deploy interoperable calendaring
and scheduling services for the Internet. Current group scheduling and scheduling services for the Internet. Current group scheduling
and Personal Information Management (PIM) products are being extended and Personal Information Management (PIM) products are being extended
skipping to change at line 58 skipping to change at line 57
The proposed media type value is 'text/calendar'. This string would The proposed media type value is 'text/calendar'. This string would
label a media type containing calendaring and scheduling information label a media type containing calendaring and scheduling information
encoded as text characters formatted in a manner outlined below. encoded as text characters formatted in a manner outlined below.
This MIME media type provides a standard content type for capturing This MIME media type provides a standard content type for capturing
calendar event, to-do and journal entry information. It also can be calendar event, to-do and journal entry information. It also can be
used to convey free/busy time information. The content type is used to convey free/busy time information. The content type is
suitable as a MIME message entity that can be transferred over MIME suitable as a MIME message entity that can be transferred over MIME
based email systems, using HTTP or some other Internet transport. In based email systems, using HTTP or some other Internet transport. In
Dawson/Stenerson 1 Expires November 1998 Dawson/Stenerson 1 Expires January 1999
addition, the content type is useful as an object for interactions addition, the content type is useful as an object for interactions
between desktop applications using the operating system clipboard, between desktop applications using the operating system clipboard,
drag/drop or file systems capabilities. drag/drop or file systems capabilities.
This memo is based on the earlier work of the vCalendar specification This memo is based on the earlier work of the vCalendar specification
for the exchange of personal calendaring and scheduling information. for the exchange of personal calendaring and scheduling information.
In order to avoid confusion with this referenced work, this memo is In order to avoid confusion with this referenced work, this memo is
to be known as the iCalendar specification. to be known as the iCalendar specification.
Readers may also refer to the calendaring and scheduling model Readers may also refer to the calendaring and scheduling model
skipping to change at line 84 skipping to change at line 83
messages that request an event be scheduled, reply to an event messages that request an event be scheduled, reply to an event
request, send a cancellation notice for an event, modify or replace request, send a cancellation notice for an event, modify or replace
the definition of an event, provide a counter proposal for an the definition of an event, provide a counter proposal for an
original event request, delegate an event request to another original event request, delegate an event request to another
individual, request free or busy time, reply to a free or busy time individual, request free or busy time, reply to a free or busy time
request, or provide similar scheduling messages for a to-do or request, or provide similar scheduling messages for a to-do or
journal entry calendar component. The iCalendar Transport-indendent journal entry calendar component. The iCalendar Transport-indendent
Interoperability Protocol (iTIP) defined in [ITIP] is one such Interoperability Protocol (iTIP) defined in [ITIP] is one such
scheduling protocol. scheduling protocol.
Dawson/Stenerson 2 Expires November 1998 Dawson/Stenerson 2 Expires January 1999
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 Registration Information.............................................8 3 Registration Information.............................................8
3.1 Content Type .....................................................9 3.1 Content Type .....................................................9
3.2 Parameters .......................................................9 3.2 Parameters .......................................................9
skipping to change at line 115 skipping to change at line 114
3.13 Authors/Change Controllers .....................................12 3.13 Authors/Change Controllers .....................................12
4 iCalendar Object Specification......................................12 4 iCalendar Object Specification......................................12
4.1 Content Lines ...................................................12 4.1 Content Lines ...................................................12
4.1.1 List and Field Separators ....................................15 4.1.1 List and Field Separators ....................................15
4.1.2 Multiple Values ..............................................15 4.1.2 Multiple Values ..............................................15
4.1.3 Binary Content ...............................................16 4.1.3 Binary Content ...............................................16
4.1.4 Character Set ................................................16 4.1.4 Character Set ................................................16
4.2 Property Parameters .............................................16 4.2 Property Parameters .............................................16
4.2.1 Alternate Text Representation ................................17 4.2.1 Alternate Text Representation ................................17
4.2.2 Common Name ..................................................18 4.2.2 Common Name ..................................................18
4.2.3 Calendar User Type ...........................................19 4.2.3 Calendar User Type ...........................................18
4.2.4 Delegators ...................................................19 4.2.4 Delegators ...................................................19
4.2.5 Delegatees ...................................................20 4.2.5 Delegatees ...................................................20
4.2.6 Directory Entry Reference ....................................20 4.2.6 Directory Entry Reference ....................................20
4.2.7 Inline Encoding ..............................................20 4.2.7 Inline Encoding ..............................................20
4.2.8 Free/Busy Time Type ..........................................21 4.2.8 Format Type ..................................................21
4.2.9 Language .....................................................22 4.2.9 Free/Busy Time Type ..........................................22
4.2.10 Group or List Membership ....................................22 4.2.10 Language ....................................................22
4.2.11 Participation Status ........................................23 4.2.11 Group or List Membership ....................................23
4.2.12 Recurrence Identifier Range .................................24 4.2.12 Participation Status ........................................23
4.2.13 Alarm Trigger Relationship ..................................25 4.2.13 Recurrence Identifier Range .................................25
4.2.14 Relationship Type ...........................................25 4.2.14 Alarm Trigger Relationship ..................................25
4.2.15 Participation Role ..........................................26 4.2.15 Relationship Type ...........................................26
4.2.16 RSVP Expectation ............................................27 4.2.16 Participation Role ..........................................26
4.2.17 Sent By .....................................................27 4.2.17 RSVP Expectation ............................................27
4.2.18 Time Zone Identifier ........................................27 4.2.18 Sent By .....................................................27
4.2.19 Value Data Types ............................................28 4.2.19 Time Zone Identifier ........................................28
4.3 Property Value Data Types .......................................29 4.2.20 Value Data Types ............................................29
4.3.1 Binary .......................................................29 4.3 Property Value Data Types .......................................30
4.3.1 Binary .......................................................30
4.3.2 Boolean ......................................................30 4.3.2 Boolean ......................................................30
4.3.3 Calendar User Address ........................................30 4.3.3 Calendar User Address ........................................31
4.3.4 Date .........................................................31
Dawson/Stenerson 3 Expires November 1998 Dawson/Stenerson 3 Expires January 1999
4.3.5 Date-Time ....................................................31 4.3.4 Date .........................................................31
4.3.6 Duration .....................................................33 4.3.5 Date-Time ....................................................32
4.3.6 Duration .....................................................34
4.3.7 Float ........................................................34 4.3.7 Float ........................................................34
4.3.8 Integer ......................................................34 4.3.8 Integer ......................................................35
4.3.9 Period of Time ...............................................35 4.3.9 Period of Time ...............................................35
4.3.10 Recurrence Rule .............................................36 4.3.10 Recurrence Rule .............................................36
4.3.11 Text ........................................................40 4.3.11 Text ........................................................41
4.3.12 Time ........................................................41 4.3.12 Time ........................................................42
4.3.13 URI .........................................................43 4.3.13 URI .........................................................44
4.3.14 UTC Offset ..................................................44 4.3.14 UTC Offset ..................................................44
4.4 iCalendar Object ................................................45 4.4 iCalendar Object ................................................45
4.5 Property ........................................................45 4.5 Property ........................................................45
4.6 Calendar Components .............................................45 4.6 Calendar Components .............................................46
4.6.1 Event Component ..............................................46 4.6.1 Event Component ..............................................47
4.6.2 To-do Component ..............................................48 4.6.2 To-do Component ..............................................48
4.6.3 Journal Component ............................................49 4.6.3 Journal Component ............................................49
4.6.4 Free/Busy Component ..........................................50 4.6.4 Free/Busy Component ..........................................50
4.6.5 Time Zone Component ..........................................52 4.6.5 Time Zone Component ..........................................53
4.6.6 Alarm Component ..............................................58 4.6.6 Alarm Component ..............................................58
4.7 Calendar Properties .............................................61 4.7 Calendar Properties .............................................62
4.7.1 Calendar Scale ...............................................61 4.7.1 Calendar Scale ...............................................62
4.7.2 Method .......................................................62 4.7.2 Method .......................................................62
4.7.3 Product Identifier ...........................................63 4.7.3 Product Identifier ...........................................63
4.7.4 Version ......................................................63 4.7.4 Version ......................................................64
4.8 Component Properties ............................................64 4.8 Component Properties ............................................65
4.8.1 Descriptive Component Properties .............................64 4.8.1 Descriptive Component Properties .............................65
4.8.1.1 Attachment ...............................................64 4.8.1.1 Attachment ...............................................65
4.8.1.2 Categories ...............................................65 4.8.1.2 Categories ...............................................66
4.8.1.3 Classification ...........................................66 4.8.1.3 Classification ...........................................66
4.8.1.4 Comment ..................................................67 4.8.1.4 Comment ..................................................67
4.8.1.5 Description ..............................................67 4.8.1.5 Description ..............................................68
4.8.1.6 Geographic Position ......................................68 4.8.1.6 Geographic Position ......................................69
4.8.1.7 Location .................................................69 4.8.1.7 Location .................................................69
4.8.1.8 Percent Complete .........................................69 4.8.1.8 Percent Complete .........................................70
4.8.1.9 Priority .................................................70 4.8.1.9 Priority .................................................71
4.8.1.10 Resources ...............................................72 4.8.1.10 Resources ...............................................72
4.8.1.11 Status ..................................................72 4.8.1.11 Status ..................................................73
4.8.1.12 Summary .................................................73 4.8.1.12 Summary .................................................74
4.8.2 Date and Time Component Properties ...........................74 4.8.2 Date and Time Component Properties ...........................75
4.8.2.1 Date/Time Completed ......................................74 4.8.2.1 Date/Time Completed ......................................75
4.8.2.2 Date/Time End ............................................75 4.8.2.2 Date/Time End ............................................75
4.8.2.3 Date/Time Due ............................................75 4.8.2.3 Date/Time Due ............................................76
4.8.2.4 Date/Time Start ..........................................76 4.8.2.4 Date/Time Start ..........................................77
4.8.2.5 Duration .................................................77 4.8.2.5 Duration .................................................77
4.8.2.6 Free/Busy Time ...........................................78 4.8.2.6 Free/Busy Time ...........................................78
4.8.2.7 Time Transparency ........................................79 4.8.2.7 Time Transparency ........................................79
4.8.3 Time Zone Component Properties ...............................79 4.8.3 Time Zone Component Properties ...............................80
4.8.3.1 Time Zone Identifier .....................................79 4.8.3.1 Time Zone Identifier .....................................80
4.8.3.2 Time Zone Name ...........................................80 4.8.3.2 Time Zone Name ...........................................81
4.8.3.3 Time Zone Offset From ....................................81 4.8.3.3 Time Zone Offset From ....................................82
4.8.3.4 Time Zone Offset To ......................................82 4.8.3.4 Time Zone Offset To ......................................82
4.8.3.5 Time Zone URL ............................................82 4.8.3.5 Time Zone URL ............................................83
4.8.4 Relationship Component Properties ............................83 4.8.4 Relationship Component Properties ............................84
4.8.4.1 Attendee .................................................83
Dawson/Stenerson 4 Expires November 1998 Dawson/Stenerson 4 Expires January 1999
4.8.4.2 Contact ..................................................85 4.8.4.1 Attendee .................................................84
4.8.4.3 Organizer ................................................86 4.8.4.2 Contact ..................................................86
4.8.4.4 Recurrence ID ............................................87 4.8.4.3 Organizer ................................................87
4.8.4.5 Related To ...............................................88 4.8.4.4 Recurrence ID ............................................88
4.8.4.6 Uniform Resource Locator .................................89 4.8.4.5 Related To ...............................................89
4.8.4.7 Unique Identifier ........................................90 4.8.4.6 Uniform Resource Locator .................................90
4.8.5 Recurrence Component Properties ..............................91 4.8.4.7 Unique Identifier ........................................91
4.8.5.1 Exception Date/Times .....................................91 4.8.5 Recurrence Component Properties ..............................92
4.8.5.2 Exception Rule ...........................................92 4.8.5.1 Exception Date/Times .....................................92
4.8.5.3 Recurrence Date/Times ....................................93 4.8.5.2 Exception Rule ...........................................93
4.8.5.3 Recurrence Date/Times ....................................94
4.8.5.4 Recurrence Rule ..........................................95 4.8.5.4 Recurrence Rule ..........................................95
4.8.6 Alarm Component Properties ..................................102 4.8.6 Alarm Component Properties ..................................103
4.8.6.1 Action ..................................................103 4.8.6.1 Action ..................................................103
4.8.6.2 Repeat Count ............................................103 4.8.6.2 Repeat Count ............................................104
4.8.6.3 Trigger .................................................104 4.8.6.3 Trigger .................................................105
4.8.7 Change Management Component Properties ......................105 4.8.7 Change Management Component Properties ......................106
4.8.7.1 Date/Time Created .......................................105 4.8.7.1 Date/Time Created .......................................106
4.8.7.2 Date/Time Stamp .........................................106 4.8.7.2 Date/Time Stamp .........................................107
4.8.7.3 Last Modified ...........................................107 4.8.7.3 Last Modified ...........................................107
4.8.7.4 Sequence Number .........................................107 4.8.7.4 Sequence Number .........................................108
4.8.8 Miscellaneous Component Properties ..........................109 4.8.8 Miscellaneous Component Properties ..........................110
4.8.8.1 Non-standard Properties .................................109 4.8.8.1 Non-standard Properties .................................110
4.8.8.2 Request Status ..........................................110 4.8.8.2 Request Status ..........................................110
5 iCalendar Object Examples..........................................111 5 iCalendar Object Examples..........................................112
6 Recommended Practices..............................................115 6 Recommended Practices..............................................116
7 Registration of Content Type Elements..............................116 7 Registration of Content Type Elements..............................117
7.1 Registration of New and Modified iCalendar Object Methods ......116 7.1 Registration of New and Modified iCalendar Object Methods ......117
7.2 Registration of New Properties .................................116 7.2 Registration of New Properties .................................117
7.2.1 Define the property .........................................116 7.2.1 Define the property .........................................117
7.2.2 Post the Property definition ................................117 7.2.2 Post the Property definition ................................118
7.2.3 Allow a comment period ......................................117 7.2.3 Allow a comment period ......................................118
7.2.4 Submit the property for approval ............................117 7.2.4 Submit the property for approval ............................118
7.3 Property Change Control ........................................118 7.3 Property Change Control ........................................119
8 References.........................................................118 8 References.........................................................119
9 Acknowledgments....................................................120 9 Acknowledgments....................................................121
10 Author's Address..................................................120 10 Author's Address..................................................121
11 Full Copyright Statement..........................................121 11 Full Copyright Statement..........................................122
Dawson/Stenerson 5 Expires November 1998 Dawson/Stenerson 5 Expires January 1999
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
skipping to change at line 287 skipping to change at line 287
the Internet ABNF defined in [RFC 2234]. This ABNF is required for the Internet ABNF defined in [RFC 2234]. This ABNF is required for
the implementation of parsers and to serve as the definitive the implementation of parsers and to serve as the definitive
reference when ambiguities or questions arise in interpreting the reference when ambiguities or questions arise in interpreting the
descriptive prose definition of the memo. descriptive prose definition of the memo.
2 Basic Grammar and Conventions 2 Basic Grammar and Conventions
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
Dawson/Stenerson 6 Expires November 1998 Dawson/Stenerson 6 Expires January 1999
"OPTIONAL" in this document are to be interoperated as described in "OPTIONAL" in this document are to be interoperated as described in
[RFC 2119]. [RFC 2119].
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 [RFC 2234]. The notation used in this memo is the ABNF notation of [RFC 2234].
Readers intending on implementing this format defined in this memo Readers intending on implementing this 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.
skipping to change at line 342 skipping to change at line 342
All calendar components start with the letter "V". For example, All calendar components start with the letter "V". For example,
"VEVENT" refers to the event calendar component, "VTODO" refers to "VEVENT" refers to the event calendar component, "VTODO" refers to
the to-do calendar component and "VJOURNAL" refers to the daily the to-do calendar component and "VJOURNAL" refers to the daily
journal calendar component. Scheduling methods defined by [ITIP] are journal calendar component. Scheduling methods defined by [ITIP] are
referred to with capitalized, quoted-strings of text. For example, referred to with capitalized, quoted-strings of text. For example,
"REQUEST" refers to the method for requesting a scheduling calendar "REQUEST" refers to the method for requesting a scheduling calendar
component be created or modified, "REPLY" refers to the method a component be created or modified, "REPLY" refers to the method a
recipient of a request uses to update their status with the recipient of a request uses to update their status with the
"Organizer" of the calendar component. "Organizer" of the calendar component.
Dawson/Stenerson 7 Expires November 1998 Dawson/Stenerson 7 Expires January 1999
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 example, quoted-strings of text, followed by the word "property". For example,
"ATTENDEE" property refers to the iCalendar property used to convey "ATTENDEE" property refers to the iCalendar property used to convey
the calendar address of a calendar user. Property parameters defined the calendar address of a calendar user. Property parameters defined
by this memo are referred to with lowercase, quoted-strings of text, by this memo are referred to with lowercase, quoted-strings of text,
followed by the word "parameter". For example, "value" parameter followed by the word "parameter". For example, "value" parameter
refers to the iCalendar property parameter used to override the refers to the iCalendar property parameter used to override the
default data type for a property value. Enumerated values defined by default data type for a property value. Enumerated values defined by
this memo are referred to with capitalized text, either alone or this memo are referred to with capitalized text, either alone or
followed by the word "value". For example, the "MINUTELY" value can followed by the word "value". For example, the "MINUTELY" value can
skipping to change at line 384 skipping to change at line 384
concepts or definitions. concepts or definitions.
2.3 International Considerations 2.3 International Considerations
In the rest of this document, descriptions of characters are of the In the rest of this document, descriptions of characters are of the
form "character name (codepoint)", where "codepoint" is from the US- form "character name (codepoint)", where "codepoint" is from the US-
ASCII character set. The "character name" is the authoritative ASCII character set. The "character name" is the authoritative
description; (codepoint) is a reference to that character in US- description; (codepoint) is a reference to that character in US-
ASCII or US-ASCII compatible sets (for example the ISO-8859-x family, ASCII or US-ASCII compatible sets (for example the ISO-8859-x family,
UTF-8, ISO-2022-xx, KOI8-R). If a non-US-ASCII compatible character UTF-8, ISO-2022-xx, KOI8-R). If a non-US-ASCII compatible character
set is used, appropriate code-point from that character set must be set is used, appropriate code-point from that character set MUST be
chosen instead. Use of non-US-ASCII-compatible character sets is NOT chosen instead. Use of non-US-ASCII-compatible character sets is NOT
recommended. recommended.
3 Registration Information 3 Registration Information
The Calendaring and Scheduling Core Object Specification is intended The Calendaring and Scheduling Core Object Specification is intended
for use as a MIME content type. However, the implementation of the for use as a MIME content type. However, the implementation of the
memo is in no way limited solely as a MIME content type. memo is in no way limited solely as a MIME content type.
Dawson/Stenerson 8 Expires November 1998 Dawson/Stenerson 8 Expires January 1999
3.1 Content Type 3.1 Content Type
The following text is intended to register this memo as the MIME The following text is intended to register this memo as the MIME
content type "text/calendar". content type "text/calendar".
To: ietf-types@uninett.no To: ietf-types@uninett.no
Subject: Registration of MIME content type text/calendar. Subject: Registration of MIME content type text/calendar.
skipping to change at line 432 skipping to change at line 432
properties and values that the iCalendar object consists of. The properties and values that the iCalendar object consists of. The
parameter is to be used as a guide for applications interpreting the parameter is to be used as a guide for applications interpreting the
information contained within the body part. It SHOULD NOT be used to information contained within the body part. It SHOULD NOT be used to
exclude or require particular pieces of information unless the exclude or require particular pieces of information unless the
identified method definition specifically calls for this behavior. identified method definition specifically calls for this behavior.
Unless specifically forbidden by a particular method definition, a Unless specifically forbidden by a particular method definition, a
text/calendar content type can contain any set of properties text/calendar content type can contain any set of properties
permitted by the Calendaring and Scheduling Core Object permitted by the Calendaring and Scheduling Core Object
Specification. The "method" parameter MUST be the same value as that Specification. The "method" parameter MUST be the same value as that
specified in the "METHOD" component property in the iCalendar object. specified in the "METHOD" component property in the iCalendar object.
If one is present, the other must also be present. If one is present, the other MUST also be present.
The value for the "method" parameter is defined as follows: The value for the "method" parameter is defined as follows:
method = 1*(ALPHA / DIGIT / "-") method = 1*(ALPHA / DIGIT / "-")
; IANA registered iCalendar object method ; IANA registered iCalendar object method
The "component" parameter conveys the type of iCalendar calendar The "component" parameter conveys the type of iCalendar calendar
component within the body part. If the iCalendar object contains more component within the body part. If the iCalendar object contains more
than one calendar component type, then multiple component parameters than one calendar component type, then multiple component parameters
MUST be specified. MUST be specified.
The value for the "component" parameter is defined as follows: The value for the "component" parameter is defined as follows:
component = ("VEVENT" / "VTODO" / "VJOURNAL" / "VFREEBUSY" component = ("VEVENT" / "VTODO" / "VJOURNAL" / "VFREEBUSY"
/ "VTIMEZONE" / x-name / iana-token) / "VTIMEZONE" / x-name / iana-token)
Dawson/Stenerson 9 Expires November 1998 Dawson/Stenerson 9 Expires January 1999
The "optinfo" parameter conveys optional information about the The "optinfo" parameter conveys optional information about the
iCalendar object within the body part. This parameter can only iCalendar object within the body part. This parameter can only
specify semantics already specified by the iCalendar object and that specify semantics already specified by the iCalendar object and that
can be otherwise determined by parsing the body part. In addition, can be otherwise determined by parsing the body part. In addition,
the optional information specified by this parameter MUST be the optional information specified by this parameter MUST be
consistent with that information specified by the iCalendar object. consistent with that information specified by the iCalendar object.
For example, it can be used to convey the "Attendee" response status For example, it can be used to convey the "Attendee" response status
to a meeting request. The parameter value consists of a string value. to a meeting request. The parameter value consists of a string value.
The parameter can be specified multiple times. The parameter can be specified multiple times.
skipping to change at line 504 skipping to change at line 504
an existing "VEVENT", "VTODO" or "VJOURNAL" or "VFREEBUSY" calendar an existing "VEVENT", "VTODO" or "VJOURNAL" or "VFREEBUSY" calendar
component might be constructed by someone other than the "Organizer" component might be constructed by someone other than the "Organizer"
and sent to the "Attendees". In addition in this memo, other than the and sent to the "Attendees". In addition in this memo, other than the
"Organizer", an "Attendee" of a "VEVENT", "VTODO", "VJOURNAL" "Organizer", an "Attendee" of a "VEVENT", "VTODO", "VJOURNAL"
calendar component is the only other person authorized to update any calendar component is the only other person authorized to update any
parameter associated with their "ATTENDEE" property and send it to parameter associated with their "ATTENDEE" property and send it to
the "Organizer". An iCalendar object that maliciously changes the the "Organizer". An iCalendar object that maliciously changes the
"ATTENDEE" parameters can be constructed by someone other than the "ATTENDEE" parameters can be constructed by someone other than the
real "Attendee" and sent to the "Organizer". real "Attendee" and sent to the "Organizer".
Dawson/Stenerson 10 Expires November 1998 Dawson/Stenerson 10 Expires January 1999
PROCEDURAL ALARMS - - An iCalendar object can be created that PROCEDURAL ALARMS - - An iCalendar object can be created that
contains a "VEVENT" and "VTODO" calendar component with "VALARM" contains a "VEVENT" and "VTODO" calendar component with "VALARM"
calendar components. The "VALARM" calendar component can be of type calendar components. The "VALARM" calendar component can be of type
PROCEDURE and can have an attachment containing some sort of PROCEDURE and can have an attachment containing some sort of
executable program. Implementations that incorporate these types of executable program. Implementations that incorporate these types of
alarms are subject to any virus or malicious attack that might occur alarms are subject to any virus or malicious attack that might occur
as a result of executing the attachment. as a result of executing the attachment.
ATTACHMENTS - - An iCalendar object can include references to Uniform ATTACHMENTS - - An iCalendar object can include references to Uniform
Resource Locators that can be programmed resources. Resource Locators that can be programmed resources.
skipping to change at line 560 skipping to change at line 560
The file extension of "ifb" is to be used to designate a file The file extension of "ifb" is to be used to designate a file
containing free or busy time information consistent with this MIME containing free or busy time information consistent with this MIME
content type. content type.
Macintosh file type codes: The file type code of "iCal" is to be used Macintosh file type codes: The file type code of "iCal" is to be used
in Apple MacIntosh operating system environments to designate a file in Apple MacIntosh operating system environments to designate a file
containing calendaring and scheduling information consistent with containing calendaring and scheduling information consistent with
this MIME media type. this MIME media type.
Dawson/Stenerson 11 Expires November 1998 Dawson/Stenerson 11 Expires January 1999
The file type code of "iFBf" is to be used in Apple MacIntosh The file type code of "iFBf" is to be used in Apple MacIntosh
operating system environments to designate a file containing free or operating system environments to designate a file containing free or
busy time information consistent with this MIME media type. busy time information consistent with this MIME media type.
3.11 Contact for Further Information: 3.11 Contact for Further Information:
Frank Dawson Frank Dawson
6544 Battleford Drive 6544 Battleford Drive
Raleigh, NC 27613-3502 Raleigh, NC 27613-3502
919-676-9515 (Telephone) 919-676-9515 (Telephone)
skipping to change at line 616 skipping to change at line 616
addition, this information can be used independent of such content addition, this information can be used independent of such content
registration. In particular, this memo has direct applicability for registration. In particular, this memo has direct applicability for
use as a calendaring and scheduling exchange format in file-, memory- use as a calendaring and scheduling exchange format in file-, memory-
or network-based transport mechanisms. or network-based transport mechanisms.
4.1 Content Lines 4.1 Content Lines
The iCalendar object is organized into individual lines of text, The iCalendar object is organized into individual lines of text,
called content lines. Content lines are delimited by a line break, called content lines. Content lines are delimited by a line break,
Dawson/Stenerson 12 Expires November 1998 Dawson/Stenerson 12 Expires January 1999
which is a CRLF sequence (US-ASCII decimal 13, followed by US-ASCII which is a CRLF sequence (US-ASCII decimal 13, followed by US-ASCII
decimal 10). decimal 10).
Lines of text SHOULD NOT be longer than 75 octets, excluding the line Lines of text SHOULD NOT be longer than 75 octets, excluding the line
break. Long content lines SHOULD be split into a multiple line break. Long content lines SHOULD be split into a multiple line
representations using a line "folding" technique. That is, a long representations using a line "folding" technique. That is, a long
line can be split between any two characters by inserting a CRLF line can be split between any two characters by inserting a CRLF
immediately followed by a single linear white space character (i.e., immediately followed by a single linear white space character (i.e.,
SPACE, US-ASCII decimal 32 or HTAB, US-ASCII decimal 9). Any sequence SPACE, US-ASCII decimal 32 or HTAB, US-ASCII decimal 9). Any sequence
of CRLF followed immediately by a single linear white space character of CRLF followed immediately by a single linear white space character
skipping to change at line 644 skipping to change at line 644
DESCRIPTION:This is a lo DESCRIPTION:This is a lo
ng description ng description
that exists on a long line. that exists on a long line.
The process of moving from this folded multiple line representation The process of moving from this folded multiple line representation
to its single line representation is called "unfolding". Unfolding is to its single line representation is called "unfolding". Unfolding is
accomplished by removing the CRLF character and the linear white accomplished by removing the CRLF character and the linear white
space character that immediately follows. space character that immediately follows.
When parsing a content line, folded lines must first be unfolded When parsing a content line, folded lines MUST first be unfolded
according to the unfolding procedure described above. When generating according to the unfolding procedure described above. When generating
a content line, lines longer than 75 octets SHOULD be folded a content line, lines longer than 75 octets SHOULD be folded
according to the folding procedure described above. according to the folding procedure described above.
The content information associated with an iCalendar object is The content information associated with an iCalendar object is
formatted using a syntax similar to that defined by [MIME DIR]. That formatted using a syntax similar to that defined by [MIME DIR]. That
is, the content information consists of one or more CRLF-separated is, the content information consists of CRLF-separated content lines.
content lines.
The following notation defines the defines the lines of content in an The following notation defines the lines of content in an iCalendar
iCalendar object: object:
contentline = name *(";" param ) ":" value CRLF contentline = name *(";" param ) ":" value CRLF
; 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 = x-name / iana-token
Dawson/Stenerson 13 Expires November 1998
iana-token = 1*(ALPHA / DIGIT / "-") iana-token = 1*(ALPHA / DIGIT / "-")
; iCalendar identifier registered with IANA ; iCalendar identifier registered with IANA
Dawson/Stenerson 13 Expires January 1999
x-name = "X-" [vendorid "-"] 1*(ALPHA / DIGIT / "-") x-name = "X-" [vendorid "-"] 1*(ALPHA / DIGIT / "-")
; Reservered for experimental use. Not intended for use in ; Reservered for experimental use. Not intended for use in
; released products. ; released products.
vendorid = 3*(ALPHA / DIGIT) ;Vendor identification vendorid = 3*(ALPHA / DIGIT) ;Vendor identification
param = param-name "=" param-value param = param-name "=" param-value
*("," param-value) *("," param-value)
; Each property defines the specific ABNF for the parameters ; Each property defines the specific ABNF for the parameters
; allowed on the property. Refer to specific properties for ; allowed on the property. Refer to specific properties for
skipping to change at line 724 skipping to change at line 723
; line feed ; line feed
CRLF = CR LF CRLF = CR LF
; Internet standard newline ; Internet standard newline
CTL = %x00-08 / %x0A-1F / %x7F CTL = %x00-08 / %x0A-1F / %x7F
; Controls ; Controls
ALPHA = %x41-5A / %x61-7A ; A-Z / a-z ALPHA = %x41-5A / %x61-7A ; A-Z / a-z
Dawson/Stenerson 14 Expires November 1998
DIGIT = %x30-39 DIGIT = %x30-39
; 0-9 ; 0-9
Dawson/Stenerson 14 Expires January 1999
DQUOTE = %x22 DQUOTE = %x22
; Quotation Mark ; Quotation Mark
WSP = SPACE / HTAB WSP = SPACE / HTAB
SPACE = %x20 SPACE = %x20
HTAB = %x09 HTAB = %x09
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.
4.1.1 List and Field Separators 4.1.1 List and Field Separators
Some properties and parameters allow a list of values. Each value in Some properties and parameters allow a list of values. Values in a
a list of values MUST be separated by a COMMA character (US-ASCII list of values MUST be separated by a COMMA character (US-ASCII
decimal 44). There is no significance to the ordering of values in a decimal 44). There is no significance to the order of values in a
list. For those parameter values (such as those that specify URI list. For those parameter values (such as those that specify URI
values) that are specified in quoted-strings, the individual quoted- values) that are specified in quoted-strings, the individual quoted-
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, a SEMICOLON or a
COMMA character MUST be placed in quoted text. COMMA character 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 and property value fields. A COMMA is separate property parameters from each other, and a COMMA is used to
used to separate values. separate property values in a value list.
ATTENDEE;RSVP=TRUE;ROLE=REQ-PARTICIPANT:MAILTO: ATTENDEE;RSVP=TRUE;ROLE=REQ-PARTICIPANT:MAILTO:
jsmith@host.com jsmith@host.com
RDATE;VALUE=DATE:19970304,19970504,19970704,19970904 RDATE;VALUE=DATE:19970304,19970504,19970704,19970904
4.1.2 Multiple Values 4.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 simply values. The general rule for encoding multi-valued items is to simply
Dawson/Stenerson 15 Expires November 1998
create a new content line for each value, including the property create a new content line for each value, including the property
name. However, it should be noted that some properties support name. However, it should be noted that some properties support
encoding multiple values in a single property by separating the encoding multiple values in a single property by separating the
Dawson/Stenerson 15 Expires January 1999
values with a COMMA character (US-ASCII decimal 44). Individual values with a COMMA character (US-ASCII decimal 44). Individual
property definitions should be consulted for determining whether a property definitions should be consulted for determining whether a
specific property allows multiple values and in which of these two specific property allows multiple values and in which of these two
forms. forms.
4.1.3 Binary Content 4.1.3 Binary Content
Binary content information in an iCalendar object SHOULD be Binary content information in an iCalendar object SHOULD be
referenced using a URI within a property value. That is the binary referenced using a URI within a property value. That is the binary
content information SHOULD be placed in an external MIME entity that content information SHOULD be placed in an external MIME entity that
can be referenced by a URI from within the iCalendar object. In can be referenced by a URI from within the iCalendar object. In
applications where this is not feasible, binary content information applications where this is not feasible, binary content information
can be included within an iCalendar object, but only after first can be included within an iCalendar object, but only after first
encoding it into text using the "BASE64" encoding method defined in encoding it into text using the "BASE64" encoding method defined in
[RFC 2045]. Support for inline binary content SHOULD be restricted to [RFC 2045]. Inline binary contact SHOULD only be used in applications
those applications requirements that necessitate conveying the whose special circumstances demand that an iCalendar object be
complete calendaring and scheduling information within a single expressed as a single entity. A property containing inline binary
iCalendar object. A property containing inline binary content content information MUST specify the "ENCODING" property parameter.
information MUST specify the "ENCODING" property parameter. Binary Binary content information placed external to the iCalendar object
content information placed external to the iCalendar object MUST be MUST be referenced by a uniform resource identifier (URI).
referenced by a uniform resource identifier (URI).
The following example specifies an "ATTACH" property that references The following example specifies an "ATTACH" property that references
an attachment external to the iCalendar object with a URI reference: an attachment external to the iCalendar object with a URI reference:
ATTACH:http://xyz.com/public/quarterly-report.doc ATTACH:http://xyz.com/public/quarterly-report.doc
The following example specifies an "ATTACH" property with inline The following example specifies an "ATTACH" property with inline
binary encoded content information: binary encoded content information:
ATTACH;ENCODING=BASE64;VALUE=BINARY:MIICajCCAdOgAwIBAgICBEUwD ATTACH;FMTTYPE=image/basic;ENCODING=BASE64;VALUE=BINARY:
QYJKoZIhvcNAQEEBQAwdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05ldHNjY MIICajCCAdOgAwIBAgICBEUwDQYJKoZIhvcNAQEEBQAwdzELMAkGA1U
XBlIENvbW11bmljYXRpb25zIENvcnBvcmF0aW9uMRwwGgYDVQQLExNJbmZvc EBhMCVVMxLDAqBgNVBAoTI05ldHNjYXBlIENvbW11bmljYXRpb25zIE
<...remainder of "BASE64" encoded binary data...> <...remainder of "BASE64" encoded binary data...>
4.1.4 Character Set 4.1.4 Character Set
There is not a property parameter to declare the character set used There is not a property parameter to declare the character set used
in a property value. The default character set for an iCalendar in a property value. The default character set for an iCalendar
object is UTF-8 as defined in [RFC 2279]. object is UTF-8 as defined in [RFC 2279].
The "charset" Content-Type parameter can be used in MIME transports The "charset" Content-Type parameter can be used in MIME transports
to specify any other IANA registered character set. to specify any other IANA registered character set.
4.2 Property Parameters 4.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
Dawson/Stenerson 16 Expires November 1998
property value, the language of a text property value, the data type property value, the language of a text property value, the data 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)
Dawson/Stenerson 16 Expires January 1999
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 DOUBLE-QUOTE (US-ASCII Property parameter values MUST NOT contain the DOUBLE-QUOTE (US-ASCII
decimal 22) character. The DOUBLE-QUOTE (US-ASCII decimal 22) decimal 22) character. The DOUBLE-QUOTE (US-ASCII decimal 22)
character is used as a delimiter for parameter values that contain character is used as a delimiter for parameter values that contain
restricted characters or URI text. For example: restricted characters or URI text. For example:
DESCRIPTION;ALTREP="http://www.wiz.org":The Fall'98 Wild Wizards DESCRIPTION;ALTREP="http://www.wiz.org":The Fall'98 Wild Wizards
Conference - - Las Vegas, NV, USA Conference - - Las Vegas, NV, USA
Property parameter values that are not in quoted strings are case Property parameter values that are not in quoted strings are case
skipping to change at line 863 skipping to change at line 861
The general property parameters defined by this memo are defined by The general property parameters defined by this memo are defined by
the following notation: the following notation:
parameter = altrepparam ; Alternate text representation parameter = altrepparam ; Alternate text representation
/ cnparam ; Common name / cnparam ; Common name
/ 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
/ 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 / 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
skipping to change at line 891 skipping to change at line 890
xparam =x-name "=" param-value *("," param-value) xparam =x-name "=" param-value *("," param-value)
4.2.1 Alternate Text Representation 4.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 property
value. value.
Dawson/Stenerson 17 Expires November 1998
Format Definition: The property parameter is defined by the following Format Definition: The property parameter is defined by the following
notation: notation:
Dawson/Stenerson 17 Expires January 1999
altrepparam = "ALTREP" "=" DQUOTE uri DQUOTE altrepparam = "ALTREP" "=" DQUOTE uri DQUOTE
Description: The parameter specifies a URI that points to an Description: The 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 the specifying this parameter MUST also include a value that reflects the
default representation of the text value. The individual URI default representation of the text value. The individual URI
parameter values MUST be specified in a quoted-string. parameter values MUST each be specified in a quoted-string.
Example: Example:
DESCRIPTION;ALTREP="CID:<part3.msg.970415T083000@host.com>":Project DESCRIPTION;ALTREP="CID:<part3.msg.970415T083000@host.com>":Project
XYZ Review Meeting will include the following agenda items: (a) XYZ Review Meeting will include the following agenda items: (a)
Market Overview, (b) Finances, (c) Project Management Market Overview, (b) Finances, (c) Project Management
The "ALTREP" property parameter value might point to a "text/html" The "ALTREP" property parameter value might point to a "text/html"
content portion. content portion.
skipping to change at line 944 skipping to change at line 943
CAL-ADDRESS value type. The parameter specifies the common name to be CAL-ADDRESS value type. The parameter specifies the common name to be
associated with the calendar user specified by the property. The associated with the calendar user specified by the property. The
parameter value is text. The parameter value can be used for display parameter value is text. The parameter value can be used for display
text to be associated with the calendar address specified by the text to be associated with the calendar address specified by the
property. property.
Example: Example:
ORGANIZER;CN="John Smith":MAILTO:jsmith@host.com ORGANIZER;CN="John Smith":MAILTO:jsmith@host.com
Dawson/Stenerson 18 Expires November 1998
4.2.3 Calendar User Type 4.2.3 Calendar User Type
Parameter Name: CUTYPE Parameter Name: CUTYPE
Dawson/Stenerson 18 Expires January 1999
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: The property parameter is defined by the following
notation: 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
skipping to change at line 995 skipping to change at line 993
delfromparam = "DELEGATED-FROM" "=" DQUOTE cal-address DQUOTE delfromparam = "DELEGATED-FROM" "=" 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 can be specified on a property CAL-ADDRESS value type. This parameter can be specified on a property
that has a value type of calendar address. This parameter specifies that has a value type of calendar address. This parameter specifies
those calendar uses that have delegated their participation in a those calendar uses that have delegated their participation in a
group scheduled event or to-do to the calendar user specified by the group scheduled event or to-do to the calendar user specified by the
property. The value MUST be a MAILTO URI as defined in [RFC 1738]. property. The value MUST be a MAILTO URI as defined in [RFC 1738].
The individual URI parameter values MUST be specified in a quoted- The individual calendar address parameter values MUST each be
string. specified in a quoted-string.
Example: Example:
Dawson/Stenerson 19 Expires November 1998
ATTENDEE;DELEGATED-FROM="MAILTO:jsmith@host.com":MAILTO: ATTENDEE;DELEGATED-FROM="MAILTO:jsmith@host.com":MAILTO:
jdoe@host.com jdoe@host.com
Dawson/Stenerson 19 Expires January 1999
4.2.5 Delegatees 4.2.5 Delegatees
Parameter Name: DELEGATED-TO Parameter Name: DELEGATED-TO
Purpose: To specify the calendar users whom the calendar user Purpose: To specify the calendar users to whom the calendar user
specified by the property has delegated participation to. specified by the property has delegated participation.
Format Definition: The property parameter is defined by the following Format Definition: The property parameter is defined by the following
notation: 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 users CAL-ADDRESS value type. This parameter specifies those calendar users
whom have been delegated participation in a group scheduled event or whom have been delegated participation in a group scheduled event or
to-do by the calendar user specified by the property. The value MUST to-do by the calendar user specified by the property. The value MUST
be a MAILTO URI as defined in [RFC 1738]. The individual URI be a MAILTO URI as defined in [RFC 1738]. The individual calendar
parameter values MUST be specified in a quoted-string. address parameter values MUST each be specified in a quoted-string.
Example: Example:
ATTENDEE;DELEGATED-TO="MAILTO:jdoe@host.com","MAILTO:jqpublic@ ATTENDEE;DELEGATED-TO="MAILTO:jdoe@host.com","MAILTO:jqpublic@
host.com":MAILTO:jsmith@host.com host.com":MAILTO:jsmith@host.com
4.2.6 Directory Entry Reference 4.2.6 Directory Entry Reference
Parameter Name: DIR Parameter Name: DIR
skipping to change at line 1045 skipping to change at line 1044
Format Definition: The property parameter is defined by the following Format Definition: The property parameter is defined by the following
notation: 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 the 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 individual URI parameter property. The parameter value is a URI. The individual URI parameter
values MUST be specified in a quoted-string. values MUST each be specified in a quoted-string.
Example: Example:
ORGANIZER;DIR="ldap://host.com:6666/o=eDABC%20Industries,c=3DUS?? ORGANIZER;DIR="ldap://host.com:6666/o=eDABC%20Industries,c=3DUS??
(cn=3DBJim%20Dolittle)":MAILTO:jimdo@host1.com (cn=3DBJim%20Dolittle)":MAILTO:jimdo@host1.com
4.2.7 Inline Encoding 4.2.7 Inline Encoding
Parameter Name: ENCODING Parameter Name: ENCODING
Dawson/Stenerson 20 Expires November 1998
Purpose: To specify an alternate inline encoding for the property Purpose: To specify an alternate inline encoding for the property
value. value.
Dawson/Stenerson 20 Expires January 1999
Format Definition: The property parameter is defined by the following Format Definition: The property parameter is defined by the following
notation: notation:
encodingparam = "ENCODING" "=" encodingparam = "ENCODING" "="
("8BIT" ("8BIT"
; "8bit" text encoding is defined in [RFC 2045] ; "8bit" text encoding is defined in [RFC 2045]
/ "BASE64" / "BASE64"
; "BASE64" binary encoding format is defined in [RFC 2045] ; "BASE64" binary encoding format is defined in [RFC 2045]
/ iana-token / iana-token
; Some other IANA registered iCalendar encoding type ; Some other IANA registered iCalendar encoding type
skipping to change at line 1085 skipping to change at line 1084
corresponding to a property value consisting of text. The "BASE64" corresponding to a property value consisting of text. The "BASE64"
encoding type corresponds to a property value encoded using the encoding type corresponds to a property value encoded using the
"BASE64" encoding defined in [RFC 2045]. "BASE64" encoding defined in [RFC 2045].
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:
ATTACH;ENCODING=BASE64;VALUE=BINARY:MIICajCCAdOgAwIBAgICBEUwD ATTACH;FMTYPE=IMAGE/JPEG;ENCODING=BASE64;VALUE=BINARY:MIICajC
QYJKoZIhvcNAQEEBQAwdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05ldHNjY CAdOgAwIBAgICBEUwDQYJKoZIhvcNAQEEBQAwdzELMAkGA1UEBhMCVVMxLDA
XBlIENvbW11bmljYXRpb25zIENvcnBvcmF0aW9uMRwwGgYDVQQLExNJbmZvc qBgNVBAoTI05ldHNjYXBlIENvbW11bmljYXRpb25zIENvcnBvcmF0aW9uMRw
<...remainder of "BASE64" encoded binary data...> <...remainder of "BASE64" encoded binary data...>
4.2.8 Free/Busy Time Type 4.2.8 Format Type
Parameter Name: FMTTYPE
Purpose: To specify the content type of a referenced object.
Format Definition: The property parameter is defined by the following
notation:
fmttypeparam = "FMTTYPE" "=" iana-token
; A IANA registered content type
/ x-name
; A non-standard content type
Description: This parameter can be specified on properties that are
used to reference an object. The parameter specifies the content type
of the referenced object. For example, on the "ATTACH" property, a
FTP type URI value does not, by itself, necessarily convey the type
of content associated with the resource. The parameter value MUST be
the TEXT for either an IANA registered content type or a non-standard
content type.
Example:
Dawson/Stenerson 21 Expires January 1999
ATTACH;FMTTYPE=application/binary:ftp://domain.com/pub/docs/
agenda.doc
4.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: The property parameter is defined by the following
notation: 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 data type.
/ iana-token) / iana-token)
; Some other IANA registered iCalendar data type. ; Some other IANA registered iCalendar data type.
Description: The parameter specifies the free or busy time type. The Description: The parameter specifies the free or busy time type. The
value FREE indicates that the time interval is free for scheduling. value FREE indicates that the time interval is free for scheduling.
The value BUSY indicates that the time interval is busy because one The value BUSY indicates that the time interval is busy because one
or more events have been scheduled for that interval. The value BUSY- or more events have been scheduled for that interval. The value BUSY-
UNAVAILABLE indicates that the time interval is busy and that the UNAVAILABLE indicates that the time interval is busy and that the
Dawson/Stenerson 21 Expires November 1998
interval can not be scheduled. The value BUSY-TENTATIVE indicates interval can not be scheduled. The value BUSY-TENTATIVE indicates
that the time interval is busy because one or more events have been that the time interval is busy because one or more events have been
tentatively scheduled for that interval. If not specified on a tentatively scheduled for that interval. If not specified on a
property that allows this parameter, the default is BUSY. property that allows this 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 FREEBUSY
property. property.
FREEBUSY;FBTYPE=BUSY:19980415T133000Z/19980415T170000Z FREEBUSY;FBTYPE=BUSY:19980415T133000Z/19980415T170000Z
4.2.9 Language 4.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: The property parameter is defined by the following
notation: notation:
languageparam = "LANGUAGE" "=" language languageparam = "LANGUAGE" "=" language
language = <Text identifying a language, as defined in [RFC 1766]> language = <Text identifying a language, as defined in [RFC 1766]>
Description: This parameter can be specified on properties with a Description: This parameter can be specified on properties with a
text value type. The parameter identifies the language of the text in text value type. The parameter identifies the language of the text in
the property or property parameter value. The value of the "language" the property or property parameter value. The value of the "language"
property parameter is that defined in [RFC 1766]. property parameter is that defined in [RFC 1766].
Dawson/Stenerson 22 Expires January 1999
For transport in a MIME entity, the Content-Language header field can For transport in a MIME entity, the Content-Language header field can
be used to set the default language for the entire body part. 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 in The following example makes use of the Quoted-Printable encoding in
order to represent non-ASCII characters. order to represent non-ASCII characters.
LOCATION;LANGUAGE=da:K=F8benhavn LOCATION;LANGUAGE=da:K=F8benhavn
LOCATION;LANGUAGE=en:Copenhagen LOCATION;LANGUAGE=en:Copenhagen
4.2.10 Group or List Membership 4.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 user
specified by the property. specified by the property.
Dawson/Stenerson 22 Expires November 1998
Format Definition: The property parameter is defined by the following Format Definition: The property parameter is defined by the following
notation: 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 list CAL-ADDRESS value type. The parameter identifies the groups or list
membership for the calendar user specified by the property. The membership for the calendar user specified by the property. The
parameter value either a single calendar address in a quoted-string parameter value either a single calendar address in a quoted-string
or a COMMA character (US-ASCII decimal 44) list of calendar or a COMMA character (US-ASCII decimal 44) list of calendar
addresses, each in a quoted-string. The individual calendar address addresses, each in a quoted-string. The individual calendar address
parameter values MUST be specified in a quoted-string. parameter values MUST each be specified in a quoted-string.
Example: Example:
ATTENDEE;MEMBER="MAILTO:ietf-calsch@imc.org":MAILTO:jsmith@host.com ATTENDEE;MEMBER="MAILTO:ietf-calsch@imc.org":MAILTO:jsmith@host.com
ATTENDEE;MEMBER="MAILTO:projectA@host.com","MAILTO:projectB@host. ATTENDEE;MEMBER="MAILTO:projectA@host.com","MAILTO:projectB@host.
com":MAILTO:janedoe@host.com com":MAILTO:janedoe@host.com
4.2.11 Participation Status 4.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: The property parameter is defined by the following
notation: notation:
Dawson/Stenerson 23 Expires January 1999
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
; status ; status
skipping to change at line 1221 skipping to change at line 1247
partstatparam /= "PARTSTAT" "=" partstatparam /= "PARTSTAT" "="
("NEEDS-ACTION" ; To-do needs action ("NEEDS-ACTION" ; To-do needs action
/ "ACCEPTED" ; To-do accepted / "ACCEPTED" ; To-do accepted
/ "DECLINED" ; To-do declined / "DECLINED" ; To-do declined
/ "TENTATIVE" ; To-do tentatively / "TENTATIVE" ; To-do tentatively
; accepted ; accepted
/ "DELEGATED" ; To-do delegated / "DELEGATED" ; To-do delegated
/ "COMPLETED" ; To-do completed. / "COMPLETED" ; To-do completed.
; COMPLETED property has ; COMPLETED property has
;date/time completed. ;date/time completed.
Dawson/Stenerson 23 Expires November 1998
/ "IN-PROCESS" ; To-do in process of / "IN-PROCESS" ; To-do in process of
; being completed ; being completed
/ x-name ; Experimental status / x-name ; Experimental status
/ iana-token) ; Other IANA registered / iana-token) ; Other IANA registered
; status ; status
; These are the participation statuses for a "VTODO". Default is ; These are the participation statuses for a "VTODO". Default is
; NEEDS-ACTION ; NEEDS-ACTION
partstatparam /= "PARTSTAT" "=" partstatparam /= "PARTSTAT" "="
("NEEDS-ACTION" ; Journal needs action ("NEEDS-ACTION" ; Journal needs action
/ "ACCEPTED" ; Journal accepted / "ACCEPTED" ; Journal accepted
/ "DECLINED" ; Journal declined / "DECLINED" ; Journal declined
/ x-name ; Experimental status / x-name ; Experimental status
/ iana-token) ; Other IANA registered / iana-token) ; Other IANA registered
; status ; status
; These are the participation statuses for a "VJOURNAL". Default is ; These are the participation statuses for a "VJOURNAL". Default is
; NEEDS-ACTION ; NEEDS-ACTION
4.2.12 Recurrence Identifier Range Description: This parameter can be specified on properties with a
CAL-ADDRESS value type. The parameter identifies the participation
status for the calendar user specified by the property value. The
parameter values differ depending on whether they are associated with
a group scheduled "VEVENT", "VTODO" or "VJOURNAL". The values MUST
match one of the values allowed for the given calendar component. If
not specified on a property that allows this parameter, the default
value is NEEDS-ACTION.
Example:
ATTENDEE;PARTSTAT=DECLINED:MAILTO:jsmith@host.com
Dawson/Stenerson 24 Expires January 1999
4.2.13 Recurrence Identifier Range
Parameter Name: RANGE Parameter Name: RANGE
Purpose: To specify the effective range of recurrence instances from Purpose: To specify the effective range of recurrence instances from
the instance specified by the recurrence identifier specified by the the instance specified by the recurrence identifier specified by the
property. property.
Format Definition: The property parameter is defined by the following Format Definition: The property parameter is defined by the following
notation: notation:
skipping to change at line 1275 skipping to change at line 1314
parameter value can be "THISANDPRIOR" to indicate a range defined by parameter value can be "THISANDPRIOR" to indicate a range defined by
the recurrence identified value of the property and all prior the recurrence identified value of the property and all prior
instances. The parameter value can also be "THISANDFUTURE" to instances. The parameter value can also be "THISANDFUTURE" to
indicate a range defined by the recurrence identifier and all indicate a range defined by the recurrence identifier and all
subsequent instances. subsequent instances.
Example: Example:
RECURRENCE-ID;RANGE=THISANDPRIOR:19980401T133000Z RECURRENCE-ID;RANGE=THISANDPRIOR:19980401T133000Z
Dawson/Stenerson 24 Expires November 1998 4.2.14 Alarm Trigger Relationship
4.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: The property parameter is defined by the following
notation: 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: The parameter can be specified on properties that
specify an alarm trigger with a DURATION value type. The parameter specify an alarm trigger with a DURATION value type. The parameter
specifies whether the alarm will trigger relative to the start or end specifies whether the alarm will trigger relative to the start or end
of the calendar component. The parameter value START will set the of the calendar component. The parameter value START will set the
alarm to trigger off the start of the calendar component; the alarm to trigger off the start of the calendar component; the
parameter value END will set the alarm to trigger off the end of the parameter value END will set the alarm to trigger off the end of the
Dawson/Stenerson 25 Expires January 1999
calendar component. If the parameter is not specified on an allowable calendar component. If the parameter is not specified on an allowable
property, then the default is START. property, then the default is START.
Example: Example:
TRIGGER;RELATED=END:PT5M TRIGGER;RELATED=END:PT5M
4.2.14 Relationship Type 4.2.15 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: The property parameter is defined by the following
notation: notation:
reltypeparam = "RELTYPE" "=" reltypeparam = "RELTYPE" "="
skipping to change at line 1331 skipping to change at line 1370
; relationship type ; relationship type
Description: This parameter can be specified on a property that Description: This parameter can be specified on a property that
references another related calendar. The parameter specifies the references another related calendar. The parameter specifies the
hierarchical relationship type of the calendar component referenced hierarchical relationship type of the calendar component referenced
by the property. The parameter value can be PARENT, to indicate that by the property. The parameter value can be PARENT, to indicate that
the referenced calendar component is a superior of calendar the referenced calendar component is a superior of calendar
component; CHILD to indicate that the referenced calendar component component; CHILD to indicate that the referenced calendar component
is a subordinate of the calendar component; SIBLING to indicate that is a subordinate of the calendar component; SIBLING to indicate that
the referenced calendar component is a peer of the calendar the referenced calendar component is a peer of the calendar
Dawson/Stenerson 25 Expires November 1998
component. If this parameter is not specified on an allowable component. If this parameter is not specified on an allowable
property, the default relationship type is PARENT. property, the default relationship type is PARENT.
Example: Example:
RELATED-TO;RELTYPE=SIBLING:<19960401-080045-4000F192713@host.com> RELATED-TO;RELTYPE=SIBLING:<19960401-080045-4000F192713@host.com>
Description: This parameter can be specified on properties with a 4.2.16 Participation Role
CAL-ADDRESS value type. The parameter identifies the participation
status for the calendar user specified by the property value. The
parameter values differ depending on whether they are associated with
a group scheduled "VEVENT", "VTODO" or "VJOURNAL". The values MUST
match one of the values allowed for the given calendar component. If
not specified on a property that allows this parameter, the default
value is NEEDS-ACTION.
Example:
ATTENDEE;PARTSTAT=DECLINED:MAILTO:jsmith@host.com
4.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: The property parameter is defined by the following
notation: notation:
roleparam = "ROLE" "=" roleparam = "ROLE" "="
("CHAIR" ; Indicates chair of the ("CHAIR" ; Indicates chair of the
; calendar entity ; calendar entity
Dawson/Stenerson 26 Expires January 1999
/ "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 is / "NON-PARTICIPANT" ; Indicates a participant who is
; copied for information ; 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
skipping to change at line 1387 skipping to change at line 1413
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@host.com ATTENDEE;ROLE=CHAIR:MAILTO:mrbig@host.com
Dawson/Stenerson 26 Expires November 1998 4.2.17 RSVP Expectation
4.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: The property parameter is defined by the following
notation: notation:
rsvpparam = "RSVP" "=" ("TRUE" / "FALSE") rsvpparam = "RSVP" "=" ("TRUE" / "FALSE")
skipping to change at line 1414 skipping to change at line 1438
reply from the calendar user specified by the property value. This reply from the calendar user specified by the property value. This
parameter is used by the "Organizer" to request a participation parameter is used by the "Organizer" to request a participation
status reply from an "Attendee" of a group scheduled event or to-do. status reply from an "Attendee" of a group scheduled event or to-do.
If not specified on a property that allows this parameter, the If not specified on a property that allows this parameter, the
default value is FALSE. default value is FALSE.
Example: Example:
ATTENDEE;RSVP=TRUE:MAILTO:jsmith@host.com ATTENDEE;RSVP=TRUE:MAILTO:jsmith@host.com
4.2.17 Sent By 4.2.18 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 the
calendar user specified by the property. calendar user specified by the property.
Dawson/Stenerson 27 Expires January 1999
Format Definition: The property parameter is defined by the following Format Definition: The property parameter is defined by the following
notation: 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 [RFC property. The parameter value MUST be a MAILTO URI as defined in [RFC
1738]. The individual URI parameter values MUST be specified in a 1738]. The individual calendar address parameter values MUST each be
quoted-string. specified in a quoted-string.
Example: Example:
ORGANIZER;SENT-BY:"MAILTO:sray@host.com":MAILTO:jsmith@host.com ORGANIZER;SENT-BY:"MAILTO:sray@host.com":MAILTO:jsmith@host.com
4.2.18 Time Zone Identifier 4.2.19 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 a
time component in the property value. time component in the property value.
Dawson/Stenerson 27 Expires November 1998
Format Definition: This property parameter is defined by the Format Definition: This property parameter is defined by the
following notation: following notation:
tzidparam = "TZID" "=" [tzidprefix] paramtext CRLF tzidparam = "TZID" "=" [tzidprefix] paramtext CRLF
tzidprefix = "/" tzidprefix = "/"
Description: The parameter MUST be specify on the "DTSTART", "DTEND", Description: The parameter MUST be specified on the "DTSTART",
"DUE", "EXDATE" and "RDATE" properties when either a DATE-TIME or "DTEND", "DUE", "EXDATE" and "RDATE" properties when either a DATE-
TIME value type is specified and when the value is not either a UTC TIME or TIME value type is specified and when the value is not either
or a "floating" time. This property parameter specifies a text value a UTC or a "floating" time. Refer to the DATE-TIME or TIME value type
which uniquely identifies the "VTIMEZONE" calendar component to be definition for a description of UTC and "floating time" formats. This
used when evaluating the time portion of the property. The value of property parameter specifies a text value which uniquely identifies
the TZID property parameter will be equal to the value of the TZID the "VTIMEZONE" calendar component to be used when evaluating the
property for the matching time zone definition. An individual time portion of the property. The value of the TZID property
"VTIMEZONE" calendar component MUST be specified for each unique parameter will be equal to the value of the TZID property for the
"TZID" parameter value specified in the iCalendar object. matching time zone definition. An individual "VTIMEZONE" calendar
component MUST be specified for each unique "TZID" parameter value
specified in the iCalendar object.
The parameter MUST be specified on properties with a DATE-TIME value 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. 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 globally prefix, indicates that this TZID represents a unique ID in a globally
defined time zone registry (when such registry is defined). defined time zone registry (when such registry is defined).
The following are examples of this property parameter: The following are examples of this property parameter:
DTSTART;TZID=America-New_York:19980119T020000 DTSTART;TZID=America-New_York:19980119T020000
Dawson/Stenerson 28 Expires January 1999
DTEND;TZID=America-New_York:19980119T030000 DTEND;TZID=America-New_York:19980119T030000
The TZID property parameter MUST NOT be applied to DATE-TIME or TIME The TZID property parameter MUST NOT be applied to DATE-TIME or TIME
properties whose time values are specified in UTC. properties whose time values are specified in UTC.
The use of local time in a DATE-TIME or TIME value without the TZID 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 value, property parameter is to be interpreted as a local time value,
regardless of the existence of "VTIMEZONE" calendar components in the regardless of the existence of "VTIMEZONE" calendar components in the
iCalendar object. iCalendar object.
For more information see the sections on the data types DATE-TIME and For more information see the sections on the data types DATE-TIME and
TIME. TIME.
4.2.19 Value Data Types 4.2.20 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 data type format for a property
value. value.
Format Definition: The "VALUE" property parameter is defined by the Format Definition: The "VALUE" property parameter is defined by the
following notation: following notation:
valuetypeparam = "VALUE" "=" valuetype valuetypeparam = "VALUE" "=" valuetype
Dawson/Stenerson 28 Expires November 1998
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"
skipping to change at line 1529 skipping to change at line 1555
Description: The parameter specifies the data type and format of the Description: The parameter specifies the data type and format of the
property value. The property values MUST be of a single value type. property value. The property values MUST be of a single value type.
For example, a "RDATE" property cannot have a combination of DATE- For example, a "RDATE" property cannot have a combination of DATE-
TIME and TIME value types. 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 default parameter need not be specified. However, if the property's default
value type is overridden by some other allowable value type, then value type is overridden by some other allowable value type, then
this parameter MUST be specified. this parameter MUST be specified.
Dawson/Stenerson 29 Expires January 1999
4.3 Property Value Data Types 4.3 Property Value Data Types
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. The 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 "VALUE" default value type or will be explicitly specified with the "VALUE"
parameter. If the value type of a property is one of the alternate parameter. If the value type of a property is one of the alternate
valid types, then it MUST be explicitly specified with the "VALUE" valid types, then it MUST be explicitly specified with the "VALUE"
parameter. parameter.
skipping to change at line 1555 skipping to change at line 1583
a character encoding of inline binary data. For example, an inline a character encoding of inline binary data. For example, an inline
attachment of an object code might be included in an iCalendar attachment of an object code might be included in an iCalendar
object. object.
Formal Definition: The value type is defined by the following Formal Definition: The 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 [RFC 2045]. ; A "BASE64" encoded character string, as defined by [RFC 2045].
Dawson/Stenerson 29 Expires November 1998
b-end = (2b-char "==") / (3b-char "=") b-end = (2b-char "==") / (3b-char "=")
b-char = ALPHA / DIGIT / "+" / "/" 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". That the inline encoding parameter sequence of ";ENCODING=BASE64". That
is, all inline binary data MUST first be character encoded using the is, all inline binary data MUST first be character encoded using the
"BASE64" encoding method defined in [RFC 2045]. No additional content "BASE64" encoding method defined in [RFC 2045]. No additional content
value encoding (i.e., BACKSLASH character encoding) is defined for value encoding (i.e., BACKSLASH character encoding) is defined for
this value type. this value type.
skipping to change at line 1582 skipping to change at line 1609
ENvbW11bmljYXRpb25zIENvcnBvcmF0aW9uMRwwGgYDVQQLExNJbmZv ENvbW11bmljYXRpb25zIENvcnBvcmF0aW9uMRwwGgYDVQQLExNJbmZv
<...remainder of "BASE64" encoded binary data...> <...remainder of "BASE64" encoded binary data...>
4.3.2 Boolean 4.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.
Formal Definition: The value type is defind by the following Formal Definition: The value type is defined by the following
notation: notation:
Dawson/Stenerson 30 Expires January 1999
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 GIBBERISH:TRUE
skipping to change at line 1610 skipping to change at line 1638
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.
Formal Definition: The value type is as defined by the following Formal Definition: The value type is as defined by the following
notation: notation:
cal-address = uri cal-address = uri
Description: The value is a URI as defined by [RFC 1738] or any other Description: The value is a URI as defined by [RFC 1738] 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
Dawson/Stenerson 30 Expires November 1998
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 [RFC 1738]. No additional content value MAILTO URI, as defined by [RFC 1738]. 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@host.com ATTENDEE:MAILTO:jane_doe@host.com
4.3.4 Date 4.3.4 Date
skipping to change at line 1639 skipping to change at line 1665
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
Description: If the property permits, multiple "date" values can be Description: If the property permits, multiple "date" values are
specified using a COMMA character (US-ASCII decimal 44) separator specified as a COMMA character (US-ASCII decimal 44) separated list
character. The format for the value type is expressed as the [ISO
Dawson/Stenerson 31 Expires January 1999
of values. The format for the value type is expressed as the [ISO
8601] complete representation, basic format for a calendar date. The 8601] complete representation, basic format for a calendar date. The
textual format specifies a four-digit year, two-digit month, and two- textual format specifies a four-digit year, two-digit month, and two-
digit day of the month. There are no separator characters between the digit day of the month. There are no separator characters between the
year, month and day component text. year, month and day component text.
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 represents July 14, 1997: Example: The following represents July 14, 1997:
skipping to change at line 1667 skipping to change at line 1695
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.
Formal Definition: The value type is defined by the following Formal Definition: The 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
Dawson/Stenerson 31 Expires November 1998 Description: If the property permits, multiple "date-time" values are
Description: If the property permits, multiple "date-time" values MAY specified as a COMMA character (US-ASCII decimal 44) separated list
be specified using a COMMA character (US-ASCII decimal 44) separator 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. character encoding) is defined for this value type.
The "DATE-TIME" data type is used to identify values that contain a The "DATE-TIME" data type is used to identify values that contain a
precise calendar date and time of day. The format is based on the precise calendar date and time of day. The format is based on the
[ISO 8601] complete representation, basic format for a calendar date [ISO 8601] complete representation, basic format for a calendar date
and time of day. The text format is a concatenation of the "date", and time of day. The text format is a concatenation of the "date",
followed by the LATIN CAPITAL LETTER T character (US-ASCII decimal followed by the LATIN CAPITAL LETTER T character (US-ASCII decimal
84) time designator, followed by the "time" format. 84) time designator, followed by the "time" format.
The "DATE-TIME" data type expresses time values in three forms: The "DATE-TIME" data type expresses time values in three forms:
skipping to change at line 1695 skipping to change at line 1722
DTSTART:19980119T230000-0800 ;Invalid time format DTSTART: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 does 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 zone. For not contain the UTC designator nor does it reference a time zone. For
example, the following represents Janurary 18, 1998, at 11 PM: example, the following represents Janurary 18, 1998, at 11 PM:
DTSTART:19980118T230000 DTSTART:19980118T230000
Dawson/Stenerson 32 Expires January 1999
Date-time values of this type are said to be "floating" and are not 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 represent the bound to any time zone in particular. They are used to represent the
same hour, minute, and second value regardless of which time zone is same hour, minute, and second value regardless of which time zone is
currently being observed. For example, an event can be defined that currently being observed. For example, an event can be defined that
indicates that an individual will be busy from 11:00 AM to 1:00 PM 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 in. In these every day, no matter which time zone the person is in. In these
cases, a local time can be specified. The recipient of an iCalendar cases, a local time can be specified. The recipient of an iCalendar
object with a property value consisting of a local time, without any object with a property value consisting of a local time, without any
relative time zone information, should interpret the value as being relative time zone information, SHOULD interpret the value as being
fixed to whatever time zone the ATTENDEE is in at any given moment. fixed to whatever time zone the ATTENDEE is in at any given moment.
This means that two ATTENDEEs, in different time zones, receiving the This means that two ATTENDEEs, in different time zones, receiving the
same event definition as a floating time, may be participating in the same event definition as a floating time, may be participating in the
event at different actual times. Floating time should only be used event at different actual times. Floating time SHOULD only be used
where that is the reasonable behavior. 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 property The use of local time in a DATE-TIME value without the TZID property
parameter is to be interpreted as floating time, regardless of the parameter is to be interpreted as floating time, regardless of the
existence of "VTIMEZONE" calendar components in the iCalendar object. existence of "VTIMEZONE" calendar components in 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
Dawson/Stenerson 32 Expires November 1998
designator, appended to the time value. For example, the following designator, appended to the time value. For example, the following
represents January 19, 1998, at 0700 UTC: represents January 19, 1998, at 0700 UTC:
DTSTART:19980119T070000Z DTSTART: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
skipping to change at line 1751 skipping to change at line 1777
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=America-NYC:19970714T133000 ;Local time and time DTSTART;TZID=America-NYC:19970714T133000 ;Local time and time
; zone reference ; zone reference
Dawson/Stenerson 33 Expires January 1999
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 COMPLETED:19970630T235960Z
4.3.6 Duration 4.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.
Formal Definition: The value type is defined by the following Formal Definition: The value type is defined by the following
notation: notation:
duration = (["+"] / "-") "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"
dur-day = 1*DIGIT "D" dur-day = 1*DIGIT "D"
Description: If the property permits, multiple "duration" values can Description: If the property permits, multiple "duration" values are
be specified using a COMMA character (US-ASCII decimal 44) separator specified by a COMMA character (US-ASCII decimal 44) separated list
of values. The format is expressed as the [ISO 8601] basic format for
Dawson/Stenerson 33 Expires November 1998
character. The format is expressed as the [ISO 8601] basic format for
the duration of time. The format can represent durations in terms of the duration of time. The format can represent durations in terms of
weeks, days, hours, minutes, and seconds. weeks, days, hours, minutes, and seconds.
No additional content value encoding (i.e., BACKSLASH character No additional content value encoding (i.e., BACKSLASH character
encoding) are defined for this value type. encoding) are defined for this value type.
Example: A duration of 15 days, 5 hours and 20 seconds would be: Example: A duration of 15 days, 5 hours and 20 seconds would be:
P15DT5H0M20S P15DT5H0M20S
A duration of 7 weeks would be: A duration of 7 weeks would be:
P7W P7W
4.3.7 Float 4.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 value number value. a real number value.
Formal Definition: The value type is defined by the following Formal Definition: The 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 can be Dawson/Stenerson 34 Expires January 1999
specified using a COMMA character (US-ASCII decimal 44) separator Description: If the property permits, multiple "float" values are
character. specified by a COMMA character (US-ASCII decimal 44) separated 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
1.333 1.333
-3.14 -3.14
skipping to change at line 1832 skipping to change at line 1858
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.
Formal Definition: The value type is defined by the following Formal Definition: The value type is defined by the following
notation: notation:
integer = (["+"] / "-") 1*DIGIT integer = (["+"] / "-") 1*DIGIT
Description: If the property permits, multiple "integer" values can Description: If the property permits, multiple "integer" values are
be specified using a COMMA character (US-ASCII decimal 44) separator specified by a COMMA character (US-ASCII decimal 44) separated list
of values. The valid range for "integer" is -2147483648 to
Dawson/Stenerson 34 Expires November 1998
character. The valid range for "integer" is -2147483648 to
2147483647. If the sign is not specified, then the value is assumed 2147483647. If the sign is not specified, then the value is assumed
to be positive. If the property permits, multiple "integer" values to be positive.
can be specified using a COMMA character (US-ASCII decimal 44)
separator character.
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:
1234567890 1234567890
-1234567890 -1234567890
+1234567890 +1234567890
432109876 432109876
skipping to change at line 1864 skipping to change at line 1886
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.
Formal Definition: The data type is defined by the following Formal Definition: The data type is defined by the following
notation: notation:
period = period-explicit / period-start period = period-explicit / period-start
Dawson/Stenerson 35 Expires January 1999
period-explicit = date-time "/" date-time period-explicit = date-time "/" date-time
; [ISO 8601] complete representation basic format for a period of ; [ISO 8601] complete representation basic format for a period of
; time consisting of a start and end. The start MUST be before the ; time consisting of a start and end. The start MUST be before the
; end. ; end.
period-start = date-time "/" duration period-start = date-time "/" dur-value
; [ISO 8601] complete representation basic format for a period of ; [ISO 8601] complete representation basic format for a period of
; time consisting of a start and positive duration of time. ; time consisting of a start and positive duration of time.
Description: If the property permits, multiple "period" values can be Description: If the property permits, multiple "period" values are
specified using a COMMA character (US-ASCII decimal 44) separator specified by a COMMA character (US-ASCII decimal 44) separated list
character. There are two forms of a period of time. A period of time of values. There are two forms of a period of time. First, a period
is identified by its start and its end. This format is expressed as of time is identified by its start and its end. This format is
the [ISO 8601] complete representation, basic format for "DATE-TIME" expressed as the [ISO 8601] complete representation, basic format for
start of the period, followed by a SOLIDUS character (US-ASCII "DATE-TIME" start of the period, followed by a SOLIDUS character (US-
decimal 47), followed by the "DATE-TIME" of the end of the period. ASCII decimal 47), followed by the "DATE-TIME" of the end of the
The start of the period MUST be before the end of the period. A period. The start of the period MUST be before the end of the period.
period of time can also be defined by a start and a positive duration Second, a period of time can also be defined by a start and a
of time. The format is expressed as the [ISO 8601] complete positive duration of time. The format is expressed as the [ISO 8601]
representation, basic format for the "DATE-TIME" start of the period, complete representation, basic format for the "DATE-TIME" start of
followed by a SOLIDUS character (US-ASCII decimal 47), followed by the period, followed by a SOLIDUS character (US-ASCII decimal 47),
the [ISO 8601] basic format for "DURATION" of the period. followed by the [ISO 8601] basic format for "DURATION" of the period.
Example: The period starting at 18:00:00 UTC, on January 1, 1997 and Example: The period starting at 18:00:00 UTC, on January 1, 1997 and
ending at 07:00:00 UTC on January 2, 1997 would be: ending at 07:00:00 UTC on January 2, 1997 would be:
Dawson/Stenerson 35 Expires November 1998
19970101T180000Z/19970102T070000Z 19970101T180000Z/19970102T070000Z
The period start at 18:00:00 on January 1, 1997 and lasting 5 hours The period start at 18:00:00 on January 1, 1997 and lasting 5 hours
and 30 minutes would be: and 30 minutes would be:
19970101T180000Z/PT5H30M 19970101T180000Z/PT5H30M
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.
skipping to change at line 1919 skipping to change at line 1941
notation: notation:
recur = "FREQ"=freq recur = "FREQ"=freq
[(";" "UNTIL" "=" enddate) / (";" "COUNT" "=" 1*DIGIT)] [(";" "UNTIL" "=" enddate) / (";" "COUNT" "=" 1*DIGIT)]
[";" "INTERVAL" "=" 1*DIGIT] [";" "INTERVAL" "=" 1*DIGIT]
[";" "BYSECOND" "=" byseclist] [";" "BYSECOND" "=" byseclist]
[";" "BYMINUTE" "=" byminlist] [";" "BYMINUTE" "=" byminlist]
[";" "BYHOUR" "=" byhrlist] [";" "BYHOUR" "=" byhrlist]
[";" "BYDAY" "=" bywdaylist] [";" "BYDAY" "=" bywdaylist]
[";" "BYMONTHDAY" "=" bymodaylist] [";" "BYMONTHDAY" "=" bymodaylist]
Dawson/Stenerson 36 Expires January 1999
[";" "BYYEARDAY" "=" byyrdaylist] [";" "BYYEARDAY" "=" byyrdaylist]
[";" "BYWEEKNO" "=" bywknolist] [";" "BYWEEKNO" "=" bywknolist]
[";" "BYMONTH" "=" bymolist] [";" "BYMONTH" "=" bymolist]
[";" "BYSETPOS" "=" bysplist] [";" "BYSETPOS" "=" bysplist]
[";" "WKST" "=" weekday)] [";" "WKST" "=" weekday)]
*(";" x-name "=" text) *(";" x-name "=" text)
;Individual rule parts MUST only be specified once. ;Individual rule parts MUST only be specified once.
;Rule parts need not be specified in particular any order. ;Rule parts need not be specified in particular any order.
freq = "SECONDLY" / "MINUTELY" / "HOURLY" / "DAILY" freq = "SECONDLY" / "MINUTELY" / "HOURLY" / "DAILY"
skipping to change at line 1946 skipping to change at line 1970
seconds = 1DIGIT / 2DIGIT ;0 to 59 seconds = 1DIGIT / 2DIGIT ;0 to 59
byminlist = minutes / ( minutes *("," minutes) ) byminlist = minutes / ( minutes *("," minutes) )
minutes = 1DIGIT / 2DIGIT ;0 to 59 minutes = 1DIGIT / 2DIGIT ;0 to 59
byhrlist = hour / ( hour *("," hour) ) byhrlist = hour / ( hour *("," hour) )
hour = 1DIGIT / 2DIGIT ;0 to 23 hour = 1DIGIT / 2DIGIT ;0 to 23
Dawson/Stenerson 36 Expires November 1998
bywdaylist = weekdaynum / ( weekdaynum *("," weekdaynum) ) bywdaylist = weekdaynum / ( weekdaynum *("," weekdaynum) )
weekdaynum = [([plus] ordwk / minus ordwk)] weekday weekdaynum = [([plus] ordwk / minus ordwk)] weekday
plus = "+" plus = "+"
minus = "-" minus = "-"
ordwk = 1DIGIT / 2DIGIT ;1 to 53 ordwk = 1DIGIT / 2DIGIT ;1 to 53
skipping to change at line 1975 skipping to change at line 1998
ordmoday = 1DIGIT / 2DIGIT ;1 to 31 ordmoday = 1DIGIT / 2DIGIT ;1 to 31
byyrdaylist = yeardaynum / ( yeardaynum *("," yeardaynum) ) byyrdaylist = yeardaynum / ( yeardaynum *("," yeardaynum) )
yeardaynum = ([plus] ordyrday) / (minus ordyrday) yeardaynum = ([plus] ordyrday) / (minus ordyrday)
ordyrday = 1DIGIT / 2DIGIT / 3DIGIT ;1 to 366 ordyrday = 1DIGIT / 2DIGIT / 3DIGIT ;1 to 366
bywknolist = weeknum / ( weeknum *("," weeknum) ) bywknolist = weeknum / ( weeknum *("," weeknum) )
Dawson/Stenerson 37 Expires January 1999
weeknum = ([plus] ordwk) / (minus ordwk) weeknum = ([plus] ordwk) / (minus ordwk)
bymolist = monthnum / ( monthnum *("," monthnum) ) bymolist = monthnum / ( monthnum *("," monthnum) )
monthnum = 1DIGIT / 2DIGIT ;1 to 12 monthnum = 1DIGIT / 2DIGIT ;1 to 12
bysplist = setposday / ( setposday *("," setposday) ) bysplist = setposday / ( setposday *("," setposday) )
setposday = yeardaynum setposday = yeardaynum
Description: If the property permits, multiple "recur" values can be Description: If the property permits, multiple "recur" values are
specified using a COMMA character (US-ASCII decimal 44) separator specified by a COMMA character (US-ASCII decimal 44) separated list
character. The value type is a structured value consisting of a list of values. The value type is a structured value consisting of a list
of one or more recurrence grammar parts. Each rule part is defined by of one or more recurrence grammar parts. Each rule part is defined by
a NAME=VALUE pair. The rule parts are separated from each other by a NAME=VALUE pair. The rule parts are separated from each other by
the SEMICOLON character (US-ASCII decimal 59). The rule parts are not the SEMICOLON character (US-ASCII decimal 59). The rule parts are not
ordered in any particular sequence. Individual rule parts MUST only ordered in any particular sequence. Individual rule parts MUST only
be specified once. be specified once.
The FREQ rule part identifies the type of recurrence rule. This rule The FREQ rule part identifies the type of recurrence rule. This rule
part MUST be specified in the recurrence rule. Valid values include part MUST be specified in the recurrence rule. Valid values include
SECONDLY, to specify repeating events based on an interval of a SECONDLY, to specify repeating events based on an interval of a
second or more; MINUTELY, to specify repeating events based on an second or more; MINUTELY, to specify repeating events based on an
interval of a minute or more; HOURLY, to specify repeating events interval of a minute or more; HOURLY, to specify repeating events
based on an interval of an hour or more; DAILY, to specify repeating based on an interval of an hour or more; DAILY, to specify repeating
events based on an interval of a day or more; WEEKLY, to specify events based on an interval of a day or more; WEEKLY, to specify
Dawson/Stenerson 37 Expires November 1998
repeating events based on an interval of a week or more; MONTHLY, to repeating events based on an interval of a week or more; MONTHLY, to
specify repeating events based on an interval of a month or more; and specify repeating events based on an interval of a month or more; and
YEARLY, to specify repeating events based on an interval of a year or YEARLY, to specify repeating events based on an interval of a year or
more. more.
The INTERVAL rule part contains a positive integer representing how The INTERVAL rule part contains a positive integer representing how
often the recurrence rule repeats. The default value is "1" or every often the recurrence rule repeats. The default value is "1", meaning
second for a SECONDLY rule, or every minute for a MINUTELY rule, every second for a SECONDLY rule, or every minute for a MINUTELY
every hour for an HOURLY rule, every day for a DAILY rule, every week rule, every hour for an HOURLY rule, every day for a DAILY rule,
for a WEEKLY rule, every month for a MONTHLY rule and every year for every week for a WEEKLY rule, every month for a MONTHLY rule and
a YEARLY rule. 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 specified date-time becomes the last instance of the recurrence. If specified
as a date-time value, then it MUST be specified in an UTC time as a date-time value, then it MUST be specified in an UTC time
format. If not present, and the COUNT rule part is also not present, format. If not present, and the COUNT rule part is also not present,
the RRULE is considered to repeat forever. 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, if range-bound the recurrence. The "DTSTART" property value, if
specified, counts as the first occurrence. specified, counts as the first occurrence.
The BYSECOND rule part specifies a COMMA character (US-ASCII decimal The BYSECOND rule part specifies a COMMA character (US-ASCII decimal
44) separated list of seconds within a minute. Valid values are 0 to 44) separated list of seconds within a minute. Valid values are 0 to
59. The BYMINUTE rule part specifies a COMMA character (US-ASCII 59. The BYMINUTE rule part specifies a COMMA character (US-ASCII
decimal 44) separated list of minutes within an hour. Valid values decimal 44) separated list of minutes within an hour. Valid values
Dawson/Stenerson 38 Expires January 1999
are 0 to 59. The BYHOUR rule part specifies a COMMA character (US- are 0 to 59. The BYHOUR rule part specifies a COMMA character (US-
ASCII decimal 44) separated list of hours of the day. Valid values ASCII decimal 44) separated list of hours of the day. Valid values
are 0 to 23. are 0 to 23.
The BYDAY rule part specifies a COMMA character (US-ASCII decimal 44) The BYDAY rule part specifies a COMMA character (US-ASCII decimal 44)
separated list of days of the week; MO, indicates Monday; TU, separated list of days of the week; MO indicates Monday; TU indicates
indicates Tuesday; WE, indicates Wednesday; TH, indicates Thursday; Tuesday; WE indicates Wednesday; TH indicates Thursday; FR indicates
FR, indicates Friday; SA, indicates Saturday; SU, indicates Sunday. Friday; SA indicates Saturday; SU indicates Sunday.
Each BYDAY value can also be preceded by a positive (+n) or negative Each BYDAY value can also be preceded by a positive (+n) or negative
(-n) integer. If present, this indicates the nth occurrence of the (-n) integer. If present, this indicates the nth occurrence of the
specific day within the MONTHLY or YEARLY RRULE. For example, within specific day within the MONTHLY or YEARLY RRULE. For example, within
a MONTHLY rule, +1MO (or simply 1MO) represents the first Monday a MONTHLY rule, +1MO (or simply 1MO) represents the first Monday
within the month, whereas -1MO represents the last Monday of the within the month, whereas -1MO represents the last Monday of the
month. If an integer modifier is not present, it means all days of month. If an integer modifier is not present, it means all days of
this type within the specified frequency. For example, within a this type within the specified frequency. For example, within a
MONTHLY rule, MO represents all Mondays within the month. MONTHLY rule, MO represents all Mondays within the month.
The BYMONTHDAY rule part specifies a COMMA character (ASCII decimal The BYMONTHDAY rule part specifies a COMMA character (ASCII decimal
44) separated list of days of the month. Valid values are 1 to 31 or 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 the last day of -31 to -1. For example, -10 represents the tenth to the last day of
the month. the month.
The BYYEARDAY rule part specifies a COMMA character (US-ASCII The BYYEARDAY rule part specifies a COMMA character (US-ASCII
decimal 44) separated list of days of the year. Valid values are 1 to decimal 44) separated list of days of the year. Valid values are 1 to
366 or -366 to -1. For example, -1 represents the last day of the 366 or -366 to -1. For example, -1 represents the last day of the
Dawson/Stenerson 38 Expires November 1998
year (December 31st) and -306 represents the 306th to the last day of year (December 31st) and -306 represents the 306th to the last day of
the year (March 1st). the year (March 1st).
The BYWEEKNO rule part specifies a COMMA character (US-ASCII decimal The BYWEEKNO rule part specifies a COMMA character (US-ASCII decimal
44) separated list of ordinals specifying weeks of the year. Valid 44) separated list of ordinals specifying weeks of the year. Valid
values are 1 to 53 or -53 to -1. This corresponds to weeks according values are 1 to 53 or -53 to -1. This corresponds to weeks according
to week numbering as defined in [ISO 8601]. The first calendar week to week numbering as defined in [ISO 8601]. A week is defined as a
of the year is the one that includes the first 4 days of the year. A seven day period, starting on the day of the week defined to be the
week is defined as a seven day period, starting on the day of the week start (see WKST). Week number one of the calendar year is the
week defined to be the week start (see WKST). This rule part is only first week which contains at least four (4) days in that calendar
valid for YEARLY rules. For example, 3 represents the third week of year. This rule part is only valid for YEARLY rules. For example, 3
the year. represents the third week of the year.
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 decimal The BYMONTH rule part specifies a COMMA character (US-ASCII decimal
44) separated list of months of the year. Valid values are 1 to 12. 44) separated list of months of the year. Valid values 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 significant Valid values are MO, TU, WE, TH, FR, SA and SU. This is significant
when a WEEKLY RRULE has an interval greater than 1, and a BYDAY rule when a WEEKLY RRULE has an interval greater than 1, and a BYDAY rule
part is specified. This is also significant when in a YEARLY RRULE part is specified. This is also significant when in a YEARLY RRULE
when a BYWEEKNO rule part is specified. The default value is MO. when a BYWEEKNO rule part is specified. The default value is MO.
The BYSETPOS rule part specifies a COMMA character (US-ASCII decimal The BYSETPOS rule part specifies a COMMA character (US-ASCII decimal
44) separated list of values which corresponds to the nth occurrence 44) separated list of values which corresponds to the nth occurrence
Dawson/Stenerson 39 Expires January 1999
within the set of events specified by the rule. Valid values are 1 to 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 conjunction with another 366 or -366 to -1. It MUST only be used in conjunction with another
Byxxx rule part. For example "the last work day of the month" could BYxxx rule part. For example "the last work day of the month" could
be represented as: be represented as:
RRULE:FREQ=MONTHLY;BYDAY=MO,TU,WE,TH,FR;BYSETPOS=-1 RRULE: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 events specified by the rule. specific occurrence within the set of events specified by the rule.
If BYxxx rule part values are found which are beyond the available If BYxxx rule part values are found which are beyond the available
scope (ie, BYMONTHDAY=30 in February), they are simply ignored. scope (ie, BYMONTHDAY=30 in February), they are simply ignored.
skipping to change at line 2113 skipping to change at line 2137
Start Time (DTSTART) entry attribute. For example, Start Time (DTSTART) entry 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 the frequency generally reduce or limit the number of occurrences of the
recurrence generated. For example, "FREQ=DAILY;BYMONTH=1" reduces the recurrence generated. For example, "FREQ=DAILY;BYMONTH=1" reduces the
number of recurrence instances from all days (if BYMONTH tag is not number of recurrence instances from all days (if BYMONTH tag is not
Dawson/Stenerson 39 Expires November 1998
present) to all days in January. BYxxx rule parts for a period of present) to all days in January. BYxxx rule parts for a period of
time less than the frequency generally increase or expand the number time less than the frequency generally increase or expand the number
of occurrences of the recurrence. For example, of occurrences of the recurrence. For example,
"FREQ=YEARLY;BYMONTH=1,2" increases the number of days within the "FREQ=YEARLY;BYMONTH=1,2" increases the number of days within the
yearly recurrence set from 1 (if BYMONTH tag is not present) to 2. yearly recurrence set from 1 (if BYMONTH tag is not present) to 2.
If multiple BYxxx rule parts are specified, then after evaluating the If multiple BYxxx rule parts are specified, then after evaluating the
specified FREQ and INTERVAL rule parts, the BYxxx rule parts are specified FREQ and INTERVAL rule parts, the BYxxx rule parts are
applied to the current set of evaluated occurrences in the following applied to the current set of evaluated occurrences in the following
order: BYMONTH, BYWEEKNO, BYYEARDAY, BYMONTHDAY, BYDAY, BYHOUR, order: BYMONTH, BYWEEKNO, BYYEARDAY, BYMONTHDAY, BYDAY, BYHOUR,
skipping to change at line 2143 skipping to change at line 2165
First, the "INTERVAL=2" would be applied to "FREQ=YEARLY" to arrive First, the "INTERVAL=2" would be applied to "FREQ=YEARLY" to arrive
at "every other year". Then, "BYMONTH=1" would be applied to arrive at "every other year". Then, "BYMONTH=1" would be applied to arrive
at "every January, every other year". Then, "BYDAY=SU" would be at "every January, every other year". Then, "BYDAY=SU" would be
applied to arrive at "every Sunday in January, every other year". applied to arrive at "every Sunday in January, every other year".
Then, "BYHOUR=8,9" would be applied to arrive at "every Sunday in Then, "BYHOUR=8,9" would be applied to arrive at "every Sunday in
January at 8 AM and 9 AM, every other year". Then, "BYMINUTE=30" January at 8 AM and 9 AM, every other year". Then, "BYMINUTE=30"
would be applied to arrive at "every Sunday in January at 8:30 AM and would be applied to arrive at "every Sunday in January at 8:30 AM and
9:30 AM, every other year". Then, lacking information from RRULE, the 9:30 AM, every other year". Then, lacking information from RRULE, the
second is derived from DTSTART, to end up in "every day in January at second is derived from DTSTART, to end up in "every day in January at
8:30:00 AM and 9:30:00 AM, every other year". Similarly, if the 8:30:00 AM and 9:30:00 AM, every other year". Similarly, if the
Dawson/Stenerson 40 Expires January 1999
BYMINUTE, BYHOUR, BYDAY, BYMONTHDAY or BYMONTH rule part were BYMINUTE, BYHOUR, BYDAY, BYMONTHDAY or BYMONTH rule part were
missing, the appropriate minute, hour, day or month would have been missing, the appropriate minute, hour, day or month would have been
retrieved from the "DTSTART" property. retrieved from the "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 meetings which Example: The following is a rule which specifies 10 meetings which
occur every other day: occur every other day:
skipping to change at line 2165 skipping to change at line 2189
There are other examples specified in the "RRULE" specification. There are other examples specified in the "RRULE" specification.
4.3.11 Text 4.3.11 Text
Value Name: TEXT Value Name: TEXT
Purpose This value type is used to identify values that contain human Purpose This value type is used to identify values that contain human
readable text. readable text.
Formal Definition: If the character set is UTF-8, the value type is Formal Definition: If the character set is UTF-8, the value type is
defined by the following notation. This must be modified depending on defined by the following notation. This MUST be modified depending on
character sets. For example, the definition of TSAFE-CHAR includes character sets. For example, the definition of TSAFE-CHAR includes
ESC for character sets that use ISO 2022 character set switching and ESC for character sets that use ISO 2022 character set switching and
Dawson/Stenerson 40 Expires November 1998
TSAFE-CHAR should not include NON-US-ASCII when the character set is TSAFE-CHAR should not include NON-US-ASCII when the character set is
US-ASCII. US-ASCII.
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, ";", ":", "\", ","
Description: If the property permits, multiple "text" values can be Description: If the property permits, multiple "text" values are
specified using a COMMA character (US-ASCII decimal 44) separator specified by a COMMA character (US-ASCII decimal 44) separated list
character. 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 a An intentional formatted text line break MUST only be included in a
"TEXT" property value by representing the line break with the "TEXT" property value by representing the line break with the
character sequence of BACKSLASH (US-ASCII decimal 92), followed by a character sequence of BACKSLASH (US-ASCII decimal 92), followed by a
LATIN SMALL LETTER N (US-ASCII decimal 110) or a LATIN CAPITAL LETTER LATIN SMALL LETTER N (US-ASCII decimal 110) or a LATIN CAPITAL LETTER
N (US-ASCII decimal 78), that is "\n" or "\N". N (US-ASCII decimal 78), that is "\n" or "\N".
Dawson/Stenerson 41 Expires January 1999
The "TEXT" property values may also contain special characters that The "TEXT" property values may also contain special characters that
are used to signify delimiters, such as a COMMA character for lists are used to signify delimiters, such as a COMMA character for lists
of values or a SEMICOLON character for structured values. In order to of values or a SEMICOLON character for structured values. In order to
support the inclusion of these special characters in "TEXT" property support the inclusion of these special characters in "TEXT" property
values, they need to be escaped with a BACKSLASH character. A values, they MUST be escaped with a BACKSLASH character. A BACKSLASH
BACKSLASH character (US-ASCII decimal 92) in a "TEXT" property value character (US-ASCII decimal 92) in a "TEXT" property value MUST be
MUST be escaped with another BACKSLASH character. A COMMA character escaped with another BACKSLASH character. A COMMA character in a
in a "TEXT" property value MUST be escaped with a BACKSLASH character "TEXT" property value MUST be escaped with a BACKSLASH character (US-
(US-ASCII decimal 92). A SEMICOLON character in a "TEXT" property ASCII decimal 92). A SEMICOLON character in a "TEXT" property value
value MUST be escaped with a BACKSLASH character (US-ASCII decimal MUST be escaped with a BACKSLASH character (US-ASCII decimal 92).
92). However, a COLON character in a "TEXT" property value SHALL NOT However, a COLON character in a "TEXT" property value SHALL NOT be
be escaped with a BACKSLASH character.Example: A multiple line value escaped with a BACKSLASH character.Example: A multiple line value of:
of:
Project XYZ Final Review Project XYZ Final Review
Conference Room - 3B Conference Room - 3B
Come Prepared. Come Prepared.
would be represented as: would be represented as:
Project XYZ Final Review\n Conference Room - 3B\nCome Prepared. Project XYZ Final Review\n Conference Room - 3B\nCome Prepared.
4.3.12 Time 4.3.12 Time
Value Name: TIME Value Name: TIME
Dawson/Stenerson 41 Expires November 1998
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.
Formal Definition: The data type is defined by the following Formal Definition: The data 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 "leap" seconds.
time-utc = "Z" time-utc = "Z"
Description: If the property permits, multiple "time" values can be Description: If the property permits, multiple "time" values are
specified using a COMMA character (US-ASCII decimal 44) separator specified by a COMMA character (US-ASCII decimal 44) separated list
character. No additional content value encoding (i.e., BACKSLASH of values. No additional content value encoding (i.e., BACKSLASH
character encoding) is defined for this value type. character encoding) is defined for this value type.
The "TIME" data type is used to identify values that contain a time The "TIME" data type is used to identify values that contain a time
of day. The format is based on the [ISO 8601] complete of day. The format is based on the [ISO 8601] 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), two- consists of a two-digit 24-hour of the day (i.e., values 0-23), two-
digit minute in the hour (i.e., values 0-59), and two-digit seconds digit minute in the hour (i.e., values 0-59), and two-digit seconds
in the minute (i.e., values 0-60). The seconds value of 60 is only to in the minute (i.e., values 0-60). The seconds value of 60 MUST only
be used to account for "leap" seconds. Fractions of a second are not to be used to account for "leap" seconds. Fractions of a second are
supported by this format. not supported by this format.
Dawson/Stenerson 42 Expires January 1999
In parallel to the "DATE-TIME" definition above, the "TIME" data type In parallel to the "DATE-TIME" definition above, the "TIME" data type
expresses time values in three forms: expresses time values in three forms:
The form of time with UTC offset MUST NOT be used. For example, the The form of time with UTC offset MUST NOT be used. For example, the
following is NOT VALID for a time value: 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
skipping to change at line 2278 skipping to change at line 2300
230000 230000
Time values of this type are said to be "floating" and are not bound 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 the same to any time zone in particular. They are used to represent the same
hour, minute, and second value regardless of which time zone is hour, minute, and second value regardless of which time zone is
currently being observed. For example, an event can be defined that currently being observed. For example, an event can be defined that
indicates that an individual will be busy from 11:00 AM to 1:00 PM 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 in. In these every day, no matter which time zone the person is in. In these
cases, a local time can be specified. The recipient of an iCalendar cases, a local time can be specified. The recipient of an iCalendar
object with a property value consisting of a local time, without any object with a property value consisting of a local time, without any
relative time zone information, should interpret the value as being relative time zone information, SHOULD interpret the value as being
Dawson/Stenerson 42 Expires November 1998
fixed to whatever time zone the ATTENDEE is in at any given moment. fixed to whatever time zone the ATTENDEE is in at any given moment.
This means that two ATTENDEEs may participate in the same event at This means that two ATTENDEEs may participate in the same event at
different UTC times; floating time should only be used where that is different UTC times; floating time SHOULD only be used where that is
reasonable behavior. 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 of parameter is to be interpreted as a local time value, regardless of
the existence of "VTIMEZONE" calendar components in the iCalendar the existence of "VTIMEZONE" calendar components in the iCalendar
object. object.
skipping to change at line 2309 skipping to change at line 2329
to the time value. For example, the following represents 07:00 AM to the time value. For example, the following represents 07:00 AM
UTC: UTC:
070000Z 070000Z
The TZID property parameter MUST NOT be applied to TIME properties The TZID property parameter MUST NOT be applied to TIME properties
whose time values are specified in UTC. whose time values are specified in UTC.
FORM #3: LOCAL TIME AND TIME ZONE REFERENCE FORM #3: LOCAL TIME AND TIME ZONE REFERENCE
Dawson/Stenerson 43 Expires January 1999
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 the
appropriate time zone definition. TZID is discussed in detail in the appropriate time zone definition. TZID is discussed in detail in the
section on Time Zone. section on Time Zone.
Example: The following represents 8:30 AM in New York in Winter, five 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- hours behind UTC, in each of the three formats using the "X-
TIMEOFDAY" non-standard property: TIMEOFDAY" non-standard property:
X-TIMEOFDAY:083000 X-TIMEOFDAY:083000
skipping to change at line 2335 skipping to change at line 2356
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 property uniform resource identifier (URI) type of reference to the property
value. value.
Formal Definition: The data type is defined by the following Formal Definition: The data type is defined by the following
notation: notation:
Dawson/Stenerson 43 Expires November 1998
uri = <As defined by any IETF RFC> uri = <As defined by any IETF RFC>
Description: This data type might be used to reference binary Description: This data type might be used to reference binary
information, for values that are large, or otherwise undesirable to information, for values that are large, or otherwise undesirable to
include directly in the iCalendar object. include directly in the iCalendar object.
The URI value formats in RFC 1738, RFC 2111 and any other IETF The URI value formats in RFC 1738, RFC 2111 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 are Any IANA registered URI format can be used. These include, but are
not limited to, those defined in RFC 1738 and RFC 2111. not limited to, those defined in RFC 1738 and RFC 2111.
When a property parameter value is a URI value type, the URI must be When a property parameter value is a URI value type, the URI MUST be
specified as a quoted-string value. 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://host1.com/my-report.txt http://host1.com/my-report.txt
4.3.14 UTC Offset 4.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.
Dawson/Stenerson 44 Expires January 1999
Formal Definition: The data type is defined by the following Formal Definition: The data type is defined by the following
notation: notation:
utc-offset = time-numzone ;As defined above in time data type utc-offset = time-numzone ;As defined above in time data type
time-numzone = ("+" / "-") time-hour time-minute time-numzone = ("+" / "-") time-hour time-minute
Description: The PLUS SIGN character MUST be specified for positive Description: The PLUS SIGN character MUST be specified for positive
UTC offsets (i.e., ahead of UTC). The value of "-0000" is not UTC offsets (i.e., ahead of UTC). The value of "-0000" is not
allowed. allowed.
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 are UTC offsets are given for standard time Example: The following UTC offsets are given for standard time for
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
Dawson/Stenerson 44 Expires November 1998
4.4 iCalendar Object 4.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 a single iCalendar object. However, multiple
iCalendar objects can be sequentially grouped together. The first iCalendar objects can be sequentially grouped together. The first
line and last line of the iCalendar object MUST contain a pair of line and last line of the iCalendar object MUST contain a pair of
iCalendar object delimiter strings. The syntax for an iCalendar iCalendar object delimiter strings. The syntax for an iCalendar
object is as follows: object is as follows:
icalobject = "BEGIN" ":" "VCALENDAR" CRLF icalobject = 1*("BEGIN" ":" "VCALENDAR" CRLF
icalbody icalbody
"END" ":" "VCALENDAR" CRLF [icalobject] "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
DTSTART:19970714T170000Z DTSTART:19970714T170000Z
DTEND:19970715T035959Z DTEND:19970715T035959Z
SUMMARY:Bastille Day Party SUMMARY:Bastille Day Party
END:VEVENT END:VEVENT
END:VCALENDAR END:VCALENDAR
4.5 Property 4.5 Property
A property is the definition of an individual attribute describing a A property is the definition of an individual attribute describing a
calendar property or a calendar component. A property takes the form calendar or a calendar component. A property takes the form defined
defined by the "contentline" notation defined in section 4.1.1. by the "contentline" notation defined in section 4.1.1.
The following is an example of a property: The following is an example of a property:
Dawson/Stenerson 45 Expires January 1999
DTSTART:19960415T133000Z DTSTART:19960415T133000Z
This memo places no imposed ordering of properties within an This memo imposes no ordering of properties within an iCalendar
iCalendar object. object.
Property names, parameter names and enumerated parameter values are Property names, parameter names and enumerated parameter values are
case insensitive. For example, the property name "DUE" is the same as case insensitive. For example, the property name "DUE" is the same as
"due" and "Due", DTSTART;TZID=Eastern:19980714T120000 is the same as "due" and "Due", DTSTART;TZID=Eastern:19980714T120000 is the same as
DtStart;TzID=Eastern:19980714T120000. DtStart;TzID=Eastern:19980714T120000.
4.6 Calendar Components 4.6 Calendar Components
The body of the iCalendar object consists of a sequence of calendar The body of the iCalendar object consists of a sequence of calendar
properties and one or more calendar components. The calendar properties and one or more calendar components. The calendar
properties are attributes that apply to the calendar as a whole. The properties are attributes that apply to the calendar as a whole. The
calendar components are collections of properties that express a calendar components are collections of properties that express a
particular calendar semantic. For example, the calendar component can particular calendar semantic. For example, the calendar component can
specify an event, a to-do, a journal entry, time zone information, or specify an event, a to-do, a journal entry, time zone information, or
free/busy time information, or an alarm. free/busy time information, or an alarm.
Dawson/Stenerson 45 Expires November 1998 The body of the iCalendar object is defined by the following
The body of the iCalenar object is defined by the following notation: notation:
icalbody = calprops component icalbody = calprops component
calprops = [calscale] [method] prodid version *x-prop calprops = [calscale] [method] prodid version *x-prop
component = 1*(eventc / todoc / journalc / freebusyc / component = 1*(eventc / todoc / journalc / freebusyc /
/ timezonec / iana-comp / x-comp) / timezonec / iana-comp / x-comp)
iana-comp = "BEGIN" ":" iana-token CRLF iana-comp = "BEGIN" ":" iana-token CRLF
1*contentline 1*contentline
"END" ":" iana-token CRLF "END" ":" iana-token CRLF
x-comp = "BEGIN" ":" x-name CRLF x-comp = "BEGIN" ":" x-name CRLF
1*contentline 1*contentline
"END" ":" x-name CRLF "END" ":" x-name CRLF
An iCalendar object must include the "PRODID" and "VERSION" calendar An iCalendar object MUST include the "PRODID" and "VERSION" calendar
properties. In addition, it must include at least one calendar properties. In addition, it MUST include at least one calendar
component. Special forms of iCalendar objects are possible to publish component. Special forms of iCalendar objects are possible to publish
just busy time (i.e., only a "VFREEBUSY" calendar component) or time just busy time (i.e., only a "VFREEBUSY" calendar component) or time
zone (i.e., only a "VTIMEZONE" calendar component) information. In zone (i.e., only a "VTIMEZONE" calendar component) information. In
addition, a complex iCalendar object is possible that is used to addition, a complex iCalendar object is possible that is used to
capture a complete snapshot of the contents of a calendar (e.g., capture a complete snapshot of the contents of a calendar (e.g.,
composite of many different calendar components). More commonly, an composite of many different calendar components). More commonly, an
iCalendar object will consist of just a single "VEVENT", "VTODO" or iCalendar object will consist of just a single "VEVENT", "VTODO" or
"VJOURNAL" calendar component. "VJOURNAL" calendar component.
Dawson/Stenerson 46 Expires January 1999
4.6.1 Event Component 4.6.1 Event Component
Component Name: "VEVENT" Component Name: "VEVENT"
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:
skipping to change at line 2497 skipping to change at line 2518
eventprop *alarmc eventprop *alarmc
"END" ":" "VEVENT" CRLF "END" ":" "VEVENT" CRLF
eventprop = *attach *attendee *categories [class] *comment eventprop = *attach *attendee *categories [class] *comment
*contact [created] [description] [dtend / duration] *contact [created] [description] [dtend / duration]
[dtstart] *exdate *exrule [geo] [last-mod] [location] [dtstart] *exdate *exrule [geo] [last-mod] [location]
[organizer] [priority] *rstatus *related *resources [organizer] [priority] *rstatus *related *resources
*rdate *rrule [dtstamp] [seq] [status] [summary] *rdate *rrule [dtstamp] [seq] [status] [summary]
[transp] [uid] [url] [recurid] *x-prop [transp] [uid] [url] [recurid] *x-prop
Dawson/Stenerson 46 Expires November 1998
Description: A "VEVENT" calendar component is a grouping of component Description: A "VEVENT" calendar component is a grouping of component
properties, and possibly including "VALARM" calendar components, that properties, and possibly including "VALARM" calendar components, that
represents a scheduled amount of time on a calendar. For example, it represents a scheduled amount of time on a calendar. For example, it
can be an activity; such as a one-hour long, department meeting from can be an activity; such as a one-hour long, department meeting from
8:00 AM to 9:00 AM, tomorrow. Generally, an event will take up time 8:00 AM to 9:00 AM, tomorrow. Generally, an event will take up time
on an individual calendar. Hence, the event will appear as an opaque on an individual calendar. Hence, the event will appear as an opaque
interval in a search for busy time. Alternately, the event can have interval in a search for busy time. Alternately, the event can have
its Time Transparency set to "TRANSPARENT" in order to prevent its Time Transparency set to "TRANSPARENT" in order to prevent
blocking of the event in searches for busy time. blocking of the event in searches for busy time.
skipping to change at line 2530 skipping to change at line 2550
cases where a "VEVENT" calendar component specifies a "DTSTART" cases where a "VEVENT" calendar component specifies a "DTSTART"
property with a DATE data type but no "DTEND" property, the events property with a DATE data type but no "DTEND" property, the events
non-inclusive end is the end of the calendar date specified by the non-inclusive end is the end of the calendar date specified by the
"DTSTART" property. For cases where a "VEVENT" calendar component "DTSTART" property. For cases where a "VEVENT" calendar component
specifies a "DTSTART" property with a DATE-TIME data type but no specifies a "DTSTART" property with a DATE-TIME data type but no
"DTEND" property, the event ends on the same calendar date and time "DTEND" property, the event ends on the same calendar date and time
of day specified by the "DTSTART" property. of day specified by the "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
Dawson/Stenerson 47 Expires January 1999
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:
BEGIN:VEVENT BEGIN:VEVENT
UID:19970901T130000Z-123401@host.com UID:19970901T130000Z-123401@host.com
DTSTAMP:19970901T1300Z DTSTAMP:19970901T1300Z
skipping to change at line 2551 skipping to change at line 2573
DTEND:19970903T190000Z DTEND:19970903T190000Z
SUMMARY:Annual Employee Review SUMMARY:Annual Employee Review
CLASS:PRIVATE CLASS:PRIVATE
CATEGORIES:BUSINESS,HUMAN RESOURCES CATEGORIES:BUSINESS,HUMAN RESOURCES
END:VEVENT END:VEVENT
The following is an example of the "VEVENT" calendar component used The following is an example of the "VEVENT" calendar component used
to represent a reminder that will not be opaque, but rather to represent a reminder that will not be opaque, but rather
transparent, to searches for busy time: transparent, to searches for busy time:
Dawson/Stenerson 47 Expires November 1998
BEGIN:VEVENT BEGIN:VEVENT
UID:19970901T130000Z-123402@host.com UID:19970901T130000Z-123402@host.com
DTSTAMP:19970901T1300Z DTSTAMP:19970901T1300Z
DTSTART:19970401T163000Z DTSTART:19970401T163000Z
DTEND:19970402T010000Z DTEND:19970402T010000Z
SUMMARY:Laurel is in sensitivity awareness class. SUMMARY:Laurel is in sensitivity awareness class.
CLASS:PUBLIC CLASS:PUBLIC
CATEGORIES:BUSINESS,HUMAN RESOURCES CATEGORIES:BUSINESS,HUMAN RESOURCES
TRANSP:TRANSPARENT TRANSP:TRANSPARENT
END:VEVENT END:VEVENT
skipping to change at line 2585 skipping to change at line 2606
RRULE:FREQ=YEARLY RRULE:FREQ=YEARLY
END:VEVENT END:VEVENT
4.6.2 To-do Component 4.6.2 To-do Component
Component Name: VTODO Component Name: VTODO
Purpose: Provide a grouping of calendar properties that describe a Purpose: Provide a grouping of calendar properties that describe a
to-do. to-do.
Dawson/Stenerson 48 Expires January 1999
Formal Definition: A "VTODO" calendar component is defined by the Formal 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 = *attach *attendee *categories [class] *comment todoprop = *attach *attendee *categories [class] *comment
[completed] *contact [created] [description] [dtstamp] [completed] *contact [created] [description] [dtstamp]
[dtstart] [due / duration] *exdate *exrule [geo] [dtstart] [due / duration] *exdate *exrule [geo]
skipping to change at line 2606 skipping to change at line 2628
*rstatus *related *resources *rdate *rrule *rstatus *related *resources *rdate *rrule
[recurid] [seq] [status] [summary] [uid] [url] [recurid] [seq] [status] [summary] [uid] [url]
*x-prop *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 represent properties and possibly "VALARM" calendar components that represent
an action-item or assignment. For example, it can be used to an action-item or assignment. For example, it can be used to
represent an item of work assigned to an individual; such as "turn in represent an item of work assigned to an individual; such as "turn in
travel expense today". travel expense today".
Dawson/Stenerson 48 Expires November 1998
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 "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.
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 with "DURATION") properties specifies a to-do that will be associated with
each successive calendar date, until it is completed. 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:
skipping to change at line 2640 skipping to change at line 2661
4.6.3 Journal Component 4.6.3 Journal Component
Component Name: VJOURNAL Component Name: VJOURNAL
Purpose: Provide a grouping of component properties that describe a Purpose: Provide a grouping of component properties that describe a
journal entry. journal entry.
Formal Definition: A "VJOURNAL" calendar component is defined by the Formal Definition: A "VJOURNAL" calendar component is defined by the
following notation: following notation:
Dawson/Stenerson 49 Expires January 1999
journalc = "BEGIN" ":" "VJOURNAL" CRLF journalc = "BEGIN" ":" "VJOURNAL" CRLF
jourprop jourprop
"END" ":" "VJOURNAL" CRLF "END" ":" "VJOURNAL" CRLF
jourprop = *attach *attendee *categories [class] *comment jourprop = *attach *attendee *categories [class] *comment
*contact [created] [description] [dtstart] [dtstamp] *contact [created] [description] [dtstart] [dtstamp]
*exdate *exrule [last-mod] [organizer] [recurid] *exdate *exrule [last-mod] [organizer] [recurid]
*related *rdate *rrule *rstatus [seq] [status] *related *rdate *rrule *rstatus [seq] [status]
[summary] [uid] [url] *x-prop [summary] [uid] [url] *x-prop
skipping to change at line 2662 skipping to change at line 2684
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 entry property is used to specify the calendar date that the journal entry
is associated with. Generally, it will have a DATE value data type, 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 a legislative Examples of a journal entry include a daily record of a legislative
body or a journal entry of individual telephone contacts for the day body or a journal entry of individual telephone contacts for the day
or an ordered list of accomplishments for the day. The "VJOURNAL" or an ordered list of accomplishments for the day. The "VJOURNAL"
calendar component can also be used to associate a document with a calendar component can also be used to associate a document with a
calendar date. calendar date.
Dawson/Stenerson 49 Expires November 1998
The "VJOURNAL" calendar component does not take up time on a The "VJOURNAL" calendar component does not take up time on a
calendar. Hence, it does not play a role in free or busy time calendar. Hence, it does not play a role in free or busy time
searches - - it is as though it has a time transparency value of searches - - it is as though it has a time transparency value of
TRANSPARENT. It is transparent to any such searches. TRANSPARENT. It is transparent to any such searches.
The "VJOURNAL" calendar component cannot be nested within another The "VJOURNAL" calendar component cannot be nested within another
calendar component. However, "VJOURNAL" calendar components can be calendar component. However, "VJOURNAL" calendar components can be
related to each other or to a "VEVENT" or to a "VTODO" calendar related to each other or to a "VEVENT" or to a "VTODO" calendar
component, with the "RELATED-TO" property. component, with the "RELATED-TO" property.
skipping to change at line 2695 skipping to change at line 2716
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. 654-2323 (tel).
END:VJOURNAL END:VJOURNAL
4.6.4 Free/Busy Component 4.6.4 Free/Busy Component
Component Name: VFREEBUSY Component Name: VFREEBUSY
Dawson/Stenerson 50 Expires January 1999
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 request either a request for free/busy time, describe a response to a request
for free/busy time or describe a published set of busy time. for free/busy time or describe a published set of busy time.
Formal Definition: A "VFREEBUSY" calendar component is defined by the Formal Definition: A "VFREEBUSY" calendar component is defined by the
following notation: following notation:
freebusyc = "BEGIN" ":" "VFREEBUSY" CRLF freebusyc = "BEGIN" ":" "VFREEBUSY" CRLF
fbprop fbprop
"END" ":" "VFREEBUSY" CRLF "END" ":" "VFREEBUSY" CRLF
skipping to change at line 2717 skipping to change at line 2739
[duration] [dtstamp] *freebusy [organizer] *rstatus [duration] [dtstamp] *freebusy [organizer] *rstatus
[uid] [url] *x-prop [uid] [url] *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 to component properties that represents either a request for, a reply to
a request for free or busy time information or a published set of a request for free or busy time information or a published set of
busy time information. busy time information.
When used to request free/busy time information, the "ATTENDEE" When used to request free/busy time information, the "ATTENDEE"
property specifies the calendar users whose free/busy time is being property specifies the calendar users whose free/busy time is being
Dawson/Stenerson 50 Expires November 1998
requested; the "ORGANIZER" property specifies the calendar user who requested; the "ORGANIZER" property specifies the calendar user who
is requesting the free/busy time; the "DTSTART" and "DTEND" is requesting the free/busy time; the "DTSTART" and "DTEND"
properties specify the window of time that the free/busy time is properties specify the window of time for which the free/busy time is
being requested; the "UID" and "DTSTAMP" properties are specified to being requested; the "UID" and "DTSTAMP" properties are specified to
assist in proper sequencing of multiple free/busy time requests. assist in proper sequencing of multiple free/busy time requests.
When used to reply to a request for free/busy time, the "ATTENDEE" When used to reply to a request for free/busy time, the "ATTENDEE"
property specifies the calendar user responding to the free/busy time property specifies the calendar user responding to the free/busy time
request; the "ORGANIZER" property specifies the calendar user that request; the "ORGANIZER" property specifies the calendar user that
originally requested the free/busy time; the "FREEBUSY" property originally requested the free/busy time; the "FREEBUSY" property
specifies the free/busy time information; and the "UID" and "DTSTAMP" specifies the free/busy time information (if it exists); and the
properties are specified to assist in proper sequencing of multiple "UID" and "DTSTAMP" properties are specified to assist in proper
free/busy time replies. sequencing of multiple free/busy time replies.
When used to publish busy time, the "ORGANIZER" property specifies When used to publish busy time, the "ORGANIZER" property specifies
the calendar user associated with the published busy time; the the calendar user associated with the published busy time; the
"DTSTART" and "DTEND" properties specify an inclusive time window "DTSTART" and "DTEND" properties specify an inclusive time window
that surrounds the busy time information; the "FREEBUSY" property that surrounds the busy time information; the "FREEBUSY" property
specifies the published busy time information; and the "DTSTAMP" specifies the published busy time information; and the "DTSTAMP"
property specifies the date/time that iCalendar object was created. property specifies the date/time that iCalendar object was created.
The "VFREEBUSY" calendar component cannot be nested within another The "VFREEBUSY" calendar component cannot be nested within another
calendar component. Multiple "VFREEBUSY" calendar components can be calendar component. Multiple "VFREEBUSY" calendar components can be
specified within an iCalendar object. This permits the grouping of specified within an iCalendar object. This permits the grouping of
Free/Busy information into logical collections, such as monthly Free/Busy information into logical collections, such as monthly
groups of busy time information. groups of busy time information.
The "VFREEBUSY" calendar component is intended for use in iCalendar The "VFREEBUSY" calendar component is intended for use in iCalendar
object methods involving requests for free time, requests for busy object methods involving requests for free time, requests for busy
time, requests for both free and busy, and the associated replies. time, requests for both free and busy, and the associated replies.
Free/Busy information is represented with the "FREEBBUSY" property. Dawson/Stenerson 51 Expires January 1999
Free/Busy information is represented with the "FREEBUSY" property.
This property provides a terse representation of time periods. One or This property provides a terse representation of time periods. One or
more "FREEBUSY" properties can be specified in the "VFREEBUSY" more "FREEBUSY" properties can be specified in the "VFREEBUSY"
calendar component. calendar component.
When present in a "VFREEBUSY" calendar component, the "DTSTART" and When present in a "VFREEBUSY" calendar component, the "DTSTART" and
"DTEND" properties SHOULD be specified prior to any "FREEBUSY" "DTEND" properties SHOULD be specified prior to any "FREEBUSY"
properties. In a free time request, these properties can be used in properties. In a free time request, these properties can be used in
combination with the "DURATION" property to represent a request for a combination with the "DURATION" property to represent a request for a
duration of free time within a specified window of time. duration of free time within a specified window of time.
skipping to change at line 2773 skipping to change at line 2794
events are resolved into their individual busy time periods using the events are resolved into their individual busy time periods using the
"FREEBUSY" property. "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@host1.com ORGANIZER:MAILTO:jane_doe@host1.com
ATTENDEE:MAILTO:john_public@host2.com ATTENDEE:MAILTO:john_public@host2.com
DTSTART:19971015T050000Z DTSTART:19971015T050000Z
Dawson/Stenerson 51 Expires November 1998
DTEND:19971016T050000Z DTEND:19971016T050000Z
DTSTAMP:19970901T083000Z DTSTAMP:19970901T083000Z
END:VFREEBUSY END:VFREEBUSY
The following is an example of a "VFREEBUSY" calendar component used The following is an example of a "VFREEBUSY" calendar component used
to reply to the request with busy time information: to reply to the request with busy time information:
BEGIN:VFREEBUSY BEGIN:VFREEBUSY
ORGANIZER:MAILTO:jane_doe@host1.com ORGANIZER:MAILTO:jane_doe@host1.com
ATTENDEE:MAILTO:john_public@host2.com ATTENDEE:MAILTO:john_public@host2.com
DTSTAMP:19970901T100000Z DTSTAMP:19970901T100000Z
FREEBUSY;VALUE=PERIOD:19971015T050000Z/PT8H30M, FREEBUSY;VALUE=PERIOD:19971015T050000Z/PT8H30M,
19971015T160000Z/PT5H30M,19971015T223000Z/PT6H30M 19971015T160000Z/PT5H30M,19971015T223000Z/PT6H30M
URL:http://host2.com/pub/busy/jpublic-01.ifb URL:http://host2.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 used The following is an example of a "VFREEBUSY" calendar component used
to published busy time information. to publish busy time information.
BEGIN:VFREEBUSY BEGIN:VFREEBUSY
ORGANIZER:jsmith@host.com ORGANIZER:jsmith@host.com
DTSTART:19980313T141711Z DTSTART:19980313T141711Z
DTEND:19980410T141711Z DTEND:19980410T141711Z
FREEBUSY:19980314T233000Z/19980315T003000Z FREEBUSY:19980314T233000Z/19980315T003000Z
FREEBUSY:19980316T153000Z/19980316T163000Z FREEBUSY:19980316T153000Z/19980316T163000Z
FREEBUSY:19980318T030000Z/19980318T040000Z FREEBUSY:19980318T030000Z/19980318T040000Z
URL:http://www.host.com/calendar/busytime/jsmith.ifb URL:http://www.host.com/calendar/busytime/jsmith.ifb
END:VFREEBUSY END:VFREEBUSY
Dawson/Stenerson 52 Expires January 1999
4.6.5 Time Zone Component 4.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.
Formal Definition: A "VTIMEZONE" calendar component is defined by the Formal Definition: A "VTIMEZONE" calendar component is defined by the
following notation: following notation:
skipping to change at line 2829 skipping to change at line 2850
*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
Dawson/Stenerson 52 Expires November 1998
daylightc = "BEGIN" ":" "DAYLIGHT" CRLF daylightc = "BEGIN" ":" "DAYLIGHT" CRLF
tzprop tzprop
"END" ":" "DAYLIGHT" CRLF "END" ":" "DAYLIGHT" CRLF
tzprop = *comment dtstart (*rdate / *rrule) tzprop = *comment dtstart (*rdate / *rrule)
*tzname tzoffsetto tzoffsetfrom *x-prop *tzname tzoffsetto tzoffsetfrom *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
skipping to change at line 2861 skipping to change at line 2881
or rule for a particular observance. or rule for a particular observance.
Effective Observance Rule Effective Observance Rule
Date (Date/Time) Offset Abbreviation Date (Date/Time) Offset Abbreviation
1967-* lastSun in Oct, 02:00 -0500 EST 1967-* lastSun 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
Dawson/Stenerson 53 Expires January 1999
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
Interoperability between two calendaring and scheduling applications, Interoperability between two calendaring and scheduling applications,
especially for recurring events, to-dos or journal entries, is especially for recurring events, to-dos or journal entries, is
skipping to change at line 2885 skipping to change at line 2906
If present, the "VTIMEZONE" calendar component defines the set of If present, the "VTIMEZONE" calendar component defines the set of
Standard Time and Daylight Saving Time observances (or rules) for a Standard Time and Daylight Saving Time observances (or rules) for a
particular time zone for a given interval of time. The "VTIMEZONE" particular time zone for a given interval of time. The "VTIMEZONE"
calendar component cannot be nested within other calendar components. calendar component cannot be nested within other calendar components.
Multiple "VTIMEZONE" calendar components can exist in an iCalendar Multiple "VTIMEZONE" calendar components can exist in an iCalendar
object. In this situation, each "VTIMEZONE" MUST represent a unique object. In this situation, each "VTIMEZONE" MUST represent a unique
time zone definition. This is necessary for some classes of events, time zone definition. This is necessary for some classes of events,
such as airline flights, that start in one time zone and end in such as airline flights, that start in one time zone and end in
another. another.
Dawson/Stenerson 53 Expires November 1998
The "VTIMEZONE" calendar component MUST be present if the iCalendar The "VTIMEZONE" calendar component MUST be present if the iCalendar
object contains an RRULE that generates dates on both sides of a time object contains an RRULE that generates dates on both sides of a time
zone shift (e.g. both in Standard Time and Daylight Saving Time) zone shift (e.g. both in Standard Time and Daylight Saving Time)
unless the iCalendar object intends to convey a floating time (See unless the iCalendar object intends to convey a floating time (See
the section "4.1.10.11 Time" for proper interpretation of floating the section "4.1.10.11 Time" for proper interpretation of floating
time). It can be present if the iCalendar object does not contain time). It can be present if the iCalendar object does not contain
such a RRULE. In addition, if a RRULE is present, there must be valid such a RRULE. In addition, if a RRULE is present, there MUST be valid
time zone information for all recurrence instances. time zone information for all recurrence instances.
The "VTIMEZONE" calendar component MUST include the "TZID" property The "VTIMEZONE" calendar component MUST include the "TZID" property
and at least one definition of a standard or daylight component. The and at least one definition of a standard or daylight component. The
standard or daylight component MUST include the "DTSTART", standard or daylight component MUST include the "DTSTART",
"TZOFFSETFROM" and "TZOFFSETTO" properties. "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 object. each unique "TZID" parameter value specified in the iCalendar object.
skipping to change at line 2916 skipping to change at line 2936
observance). The "STANDARD" sub-component consists of a collection of observance). The "STANDARD" sub-component consists of a collection of
properties that describe Standard Time. The "DAYLIGHT" sub-component properties that describe Standard Time. The "DAYLIGHT" sub-component
consists of a collection of properties that describe Daylight Saving consists of a collection of properties that describe Daylight Saving
Time. In general this collection of properties consists of: Time. In general this collection 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 - the last onset date-time for the observance, if a last onset
is known. is known.
Dawson/Stenerson 54 Expires January 1999
- 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 described the observances over a period of time. Each observance is described
using either a "STANDARD" or "DAYLIGHT" sub-component. The collection using either a "STANDARD" or "DAYLIGHT" sub-component. The collection
skipping to change at line 2941 skipping to change at line 2962
The top-level properties in a "VTIMEZONE" calendar component are: The top-level properties in a "VTIMEZONE" calendar component are:
The mandatory "TZID" property is a text value that uniquely The mandatory "TZID" property is a text value that uniquely
identifies the VTIMZONE calendar component within the scope of an identifies the VTIMZONE calendar component within the scope of an
iCalendar object. iCalendar object.
The optional "LAST-MODIFIED" property is a UTC value that specifies The optional "LAST-MODIFIED" property is a UTC value that specifies
the date and time that this time zone definition was last updated. the date and time that this time zone definition was last updated.
Dawson/Stenerson 54 Expires November 1998
The optional "TZURL" property is url value that points to a published The optional "TZURL" property is url value that points to a published
VTIMEZONE definition. VTIMEZONE definition.
The collection of properties that are used to define the STANDARD and The collection of properties that are used to define the STANDARD and
DAYLIGHT sub-components include: DAYLIGHT sub-components include:
The mandatory "DTSTART" property gives the effective onset date and The mandatory "DTSTART" property gives the effective onset date and
local time for the time zone sub-component definition. "DTSTART" in local time for the time zone sub-component definition. "DTSTART" in
this usage MUST be specified as a local DATE-TIME value. this usage MUST be specified as a local DATE-TIME value.
skipping to change at line 2972 skipping to change at line 2992
The mandatory "TZOFFSETTO " property gives the UTC offset for the The mandatory "TZOFFSETTO " property gives the UTC offset for the
time zone sub-component (Standard Time or Daylight Saving Time) when time zone sub-component (Standard Time or Daylight Saving Time) when
this observance is in use. this observance is in use.
The optional "TZNAME" property is the customary name for the time The optional "TZNAME" property is the customary name for the time
zone. It may be specified multiple times, to allow for specifying zone. It may be specified multiple times, to allow for specifying
multiple language variants of the time zone names. This could be used multiple language variants of the time zone names. This could be used
for displaying dates. for displaying dates.
Dawson/Stenerson 55 Expires January 1999
If specified, the onset for the observance defined by the time zone If specified, the onset for the observance defined by the time zone
sub-component is defined by either the "RRULE" or "RDATE" property. sub-component is defined by either the "RRULE" or "RDATE" property.
If neither are specified, only one sub-component can be specified in If neither is specified, only one sub-component can be specified in
the "VTIMEZONE" calendar component and it is assumed that the single the "VTIMEZONE" calendar component and it is assumed that the single
observance specified is always in effect. observance specified is always in effect.
The "RRULE" property defines the recurrence rule for the onset of the The "RRULE" property defines the recurrence rule for the onset of the
observance defined by this time zone sub-component. Some specific observance defined by this time zone sub-component. Some specific
requirements for the usage of RRULE for this purpose include: requirements for the usage of RRULE for this purpose 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
skipping to change at line 2997 skipping to change at line 3018
- The "DTSTART" and the "TZOFFSETTO" properties MUST be used - The "DTSTART" and the "TZOFFSETTO" properties MUST be used
when generating the onset date-time values (instances) from the when generating the onset date-time values (instances) from the
RRULE. RRULE.
Alternatively, the "RDATE" property can be used to define the onset Alternatively, the "RDATE" property can be used to define the onset
of the observance by giving the individual onset date and times. of the observance by giving the individual onset date and times.
"RDATE" in this usage MUST be specified as a local DATE-TIME value in "RDATE" in this usage MUST be specified as a local DATE-TIME value in
UTC time. UTC time.
Dawson/Stenerson 55 Expires November 1998
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 suitable United States using "RDATE" property. Note that this is only suitable
for a recurring event that starts on or later than April 6, 1997 at for a recurring event that starts on or later than April 6, 1997 at
03:00:00 EDT (i.e., the earliest effective transition date and time) 03:00:00 EDT (i.e., the earliest effective transition date and time)
skipping to change at line 3027 skipping to change at line 3047
DTSTART:19971026T020000 DTSTART:19971026T020000
RDATE:19971026T020000 RDATE:19971026T020000
TZOFFSETFROM:-0400 TZOFFSETFROM:-0400
TZOFFSETTO:-0500 TZOFFSETTO:-0500
TZNAME:EST TZNAME:EST
END:STANDARD END:STANDARD
BEGIN:DAYLIGHT BEGIN:DAYLIGHT
DTSTART:19971026T020000 DTSTART:19971026T020000
RDATE:19970406T020000 RDATE:19970406T020000
TZOFFSETFROM:-0500 TZOFFSETFROM:-0500
Dawson/Stenerson 56 Expires January 1999
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 the This is a simple example showing the current time zone rules for the
Eastern United States using a RRULE recurrence pattern. Note that Eastern United States using a RRULE recurrence pattern. Note that
there is no effective end date to either of the Standard Time or there is no effective end date to either of the Standard Time or
Daylight Time rules. This information would be valid for a recurring Daylight Time rules. This information would be valid for a recurring
event starting today and continuing on into the known future. event starting today and continuing indefinitely.
BEGIN:VTIMEZONE BEGIN:VTIMEZONE
TZID:America-New_York TZID:America-New_York
LAST-MODIFIED:19870101T000000Z LAST-MODIFIED:19870101T000000Z
TZURL:http://zones.stds_r_us.net/tz/America-New_York TZURL:http://zones.stds_r_us.net/tz/America-New_York
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
TZNAME:EST TZNAME:EST
END:STANDARD END:STANDARD
BEGIN:DAYLIGHT BEGIN:DAYLIGHT
DTSTART:19870405T020000 DTSTART:19870405T020000
RRULE:FREQ=YEARLY;BYDAY=1SU;BYMONTH=4 RRULE:FREQ=YEARLY;BYDAY=1SU;BYMONTH=4
Dawson/Stenerson 56 Expires November 1998
TZOFFSETFROM:-0500 TZOFFSETFROM:-0500
TZOFFSETTO:-0400 TZOFFSETTO:-0400
TZNAME:EDT TZNAME:EDT
END:DAYLIGHT END:DAYLIGHT
END:VTIMEZONE END:VTIMEZONE
This is an example showing a fictitious set of rules for the Eastern This is an example showing a fictitious set of rules for the Eastern
United States, where the Daylight Time rule has an effective end date United States, where the Daylight Time rule has an effective end date
(i.e., after that date, Daylight Time is no longer observed). (i.e., after that date, Daylight Time is no longer observed).
skipping to change at line 3083 skipping to change at line 3103
END:STANDARD END:STANDARD
BEGIN:DAYLIGHT BEGIN:DAYLIGHT
DTSTART:19870405T020000 DTSTART:19870405T020000
RRULE:FREQ=YEARLY;BYDAY=1SU;BYMONTH=4;UNTIL=19980404T070000Z RRULE:FREQ=YEARLY;BYDAY=1SU;BYMONTH=4;UNTIL=19980404T070000Z
TZOFFSETFROM:-0500 TZOFFSETFROM:-0500
TZOFFSETTO:-0400 TZOFFSETTO:-0400
TZNAME:EDT TZNAME:EDT
END:DAYLIGHT END:DAYLIGHT
END:VTIMEZONE END:VTIMEZONE
Dawson/Stenerson 57 Expires January 1999
This is an example showing a fictitious set of rules for the Eastern This is an example showing a fictitious set of rules for the Eastern
United States, where the first Daylight Time rule has an effective United States, where the first Daylight Time rule has an effective
end date. There is a second Daylight Time rule that picks up where end date. There is a second Daylight Time rule that picks up where
the other left off. the other left off.
BEGIN:VTIMEZONE BEGIN:VTIMEZONE
TZID:America-New_York TZID:America-New_York
LAST-MODIFIED:19870101T000000Z LAST-MODIFIED:19870101T000000Z
BEGIN:STANDARD BEGIN:STANDARD
DTSTART:19671029T020000 DTSTART:19671029T020000
skipping to change at line 3108 skipping to change at line 3129
BEGIN:DAYLIGHT BEGIN:DAYLIGHT
DTSTART:19870405T020000 DTSTART:19870405T020000
RRULE:FREQ=YEARLY;BYDAY=1SU;BYMONTH=4;UNTIL=19980404T070000Z RRULE:FREQ=YEARLY;BYDAY=1SU;BYMONTH=4;UNTIL=19980404T070000Z
TZOFFSETFROM:-0500 TZOFFSETFROM:-0500
TZOFFSETTO:-0400 TZOFFSETTO:-0400
TZNAME:EDT TZNAME:EDT
END:DAYLIGHT END:DAYLIGHT
BEGIN:DAYLIGHT BEGIN:DAYLIGHT
DTSTART:19990424T020000 DTSTART:19990424T020000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=4 RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=4
Dawson/Stenerson 57 Expires November 1998
TZOFFSETFROM:-0500 TZOFFSETFROM:-0500
TZOFFSETTO:-0400 TZOFFSETTO:-0400
TZNAME:EDT TZNAME:EDT
END:DAYLIGHT END:DAYLIGHT
END:VTIMEZONE END:VTIMEZONE
4.6.6 Alarm Component 4.6.6 Alarm Component
Component Name: VALARM Component Name: VALARM
skipping to change at line 3138 skipping to change at line 3157
"END" ":" "VALARM" CRLF "END" ":" "VALARM" CRLF
audioprop = action trigger [duration repeat] [attach] *x-prop audioprop = action trigger [duration repeat] [attach] *x-prop
dispprop = action description trigger [duration dispprop = action description trigger [duration
repeat] *x-prop repeat] *x-prop
emailprop = action 1*attendee *attach description emailprop = action 1*attendee *attach description
trigger [duration repeat] summary *x-prop trigger [duration repeat] summary *x-prop
Dawson/Stenerson 58 Expires January 1999
procprop = action attach [description] trigger [duration procprop = action attach [description] trigger [duration
repeat] *x-prop repeat] *x-prop
Description: A "VALARM" calendar component is a grouping of component Description: A "VALARM" calendar component is a grouping of component
properties that is a reminder or alarm for an event or a to-do. For properties that is a reminder or alarm for an event or a to-do. For
example, it may be used to define a reminder for a pending event or example, it may be used to define a reminder for a pending event or
an overdue to-do. 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 the "TRIGGER" properties. The "ACTION" property further constrains the
skipping to change at line 3164 skipping to change at line 3184
When the action is "DISPLAY", the alarm MUST also include a When the action is "DISPLAY", the alarm MUST also include a
"DESCRIPTION" property, which contains the text to be displayed when "DESCRIPTION" property, which contains the text to be displayed when
the alarm is triggered. the alarm is triggered.
When the action is "EMAIL", the alarm MUST include a "DESCRIPTION" When the action is "EMAIL", the alarm MUST include a "DESCRIPTION"
property, which contains the text to be used as the message body, a property, which contains the text to be used as the message body, a
"SUMMARY" property, which contains the text to be used as the message "SUMMARY" property, which contains the text to be used as the message
subject, and one or more "ATTENDEE" properties, which contain the subject, and one or more "ATTENDEE" properties, which contain the
email address of attendees to receive the message. It can also email address of attendees to receive the message. It can also
include one or more "ATTACH" properties, which are intended to be include one or more "ATTACH" properties, which are intended to be
Dawson/Stenerson 58 Expires November 1998
sent as message attachments. When the alarm is triggered, the email sent as message attachments. When the alarm is triggered, the email
message is sent. message is sent.
When the action is "PROCEDURE", the alarm MUST include one and only When the action is "PROCEDURE", the alarm MUST include one and only
one "ATTACH" property, which MUST point to a procedure resource, one "ATTACH" property, which MUST point to a procedure resource,
which is invoked when the alarm is triggered. which is invoked when the alarm is triggered.
The "VALARM" calendar component MUST only appear within either a The "VALARM" calendar component MUST only appear within either a
"VEVENT" or "VTODO" calendar component. "VALARM" calendar components "VEVENT" or "VTODO" calendar component. "VALARM" calendar components
cannot be nested. Multiple mutually independent "VALARM" calendar cannot be nested. Multiple mutually independent "VALARM" calendar
skipping to change at line 3193 skipping to change at line 3211
"RELATED" parameter of the "TRIGGER" property. The "TRIGGER" property "RELATED" parameter of the "TRIGGER" property. The "TRIGGER" property
value type can alternatively be set to an absolute calendar date and value type can alternatively be set to an absolute calendar date and
time of day value. time of day value.
In an alarm set to trigger on the "START" of an event or to-do, the 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 to-do. "DTSTART" property MUST be present in the associated event or to-do.
In an alarm in a "VEVENT" calendar component set to trigger on the In an alarm in a "VEVENT" calendar component set to trigger on the
"END" of the event, either the "DTEND" property MUST be present, or "END" of the event, either the "DTEND" property MUST be present, or
the "DTSTART" and "DURATION" properties MUST both be present. In an the "DTSTART" and "DURATION" properties MUST both be present. In an
alarm in a "VTODO" calendar component set to trigger on the "END" of alarm in a "VTODO" calendar component set to trigger on the "END" of
Dawson/Stenerson 59 Expires January 1999
the to-do, either the "DUE" property MUST be present, or the the to-do, either the "DUE" property MUST be present, or the
"DTSTART" and "DURATION" properties MUST both be present. "DTSTART" and "DURATION" properties MUST both be present.
The alarm can be defined such that it triggers repeatedly. A The alarm can be defined such that it triggers repeatedly. A
definition of an alarm with a repeating trigger MUST include both the definition of an alarm with a repeating trigger MUST include both the
"DURATION" and "REPEAT" properties. The "DURATION" property specifies "DURATION" and "REPEAT" properties. The "DURATION" property specifies
the delay period, after which the alarm will repeat. The "REPEAT" the delay period, after which the alarm will repeat. The "REPEAT"
property specifies the number of additional repetitions that the property specifies the number of additional repetitions that the
alarm will triggered. This repitition count is in addition to the alarm will triggered. This repitition count is in addition to the
initial triggering of the alarm. Both of these properties must be initial triggering of the alarm. Both of these properties MUST be
present in order to specify a repeating alarm. If one of these two present in order to specify a repeating alarm. If one of these two
properties is absent, then the alarm will not repeat beyond the properties is absent, then the alarm will not repeat beyond the
initial trigger. initial trigger.
The "ACTION" property is used within the "VALARM" calendar component The "ACTION" property is used within the "VALARM" calendar component
to specify the type of action invoked when the alarm is triggered. to specify the type of action invoked when the alarm is triggered.
The "VALARM" properties provide enough information for a specific The "VALARM" properties provide enough information for a specific
action to be invoked. It is typically the responsibility of a action to be invoked. It is typically the responsibility of a
"Calendar User Agent" (CUA) to deliver the alarm in the specified "Calendar User Agent" (CUA) to deliver the alarm in the specified
fashion. An "ACTION" property value of AUDIO specifies an alarm that fashion. An "ACTION" property value of AUDIO specifies an alarm that
causes a sound to be played to alert the user; DISPLAY specifies an causes a sound to be played to alert the user; DISPLAY specifies an
alarm that causes a text message to be displayed to the user; EMAIL alarm that causes a text message to be displayed to the user; EMAIL
specifies an alarm that causes an electronic email message to be specifies an alarm that causes an electronic email message to be
delivered to one or more email addresses; and PROCEDURE specifies an delivered to one or more email addresses; and PROCEDURE specifies an
alarm that causes a procedure to be executed. The "ACTION" property alarm that causes a procedure to be executed. The "ACTION" property
MUST specify one and only one of these values. MUST specify one and only one of these values.
Dawson/Stenerson 59 Expires November 1998
In an AUDIO alarm, if the optional "ATTACH" property is included, it In an AUDIO alarm, if the optional "ATTACH" property is included, it
MUST specify an audio sound resource. The intention is that the sound MUST specify an audio sound resource. The intention is that the sound
will be played as the alarm effect. If an "ATTACH" property is will be played as the alarm effect. If an "ATTACH" property is
specified that does not refer to a sound resource, or if the specified that does not refer to a sound resource, or if the
specified sound resource cannot be rendered (because its format is specified sound resource cannot be rendered (because its format is
unsupported, or because it cannot be retrieved), then the CUA or unsupported, or because it cannot be retrieved), then the CUA or
other entity responsible for playing the sound may choose a fallback other entity responsible for playing the sound may choose a fallback
action, such as playing a built-in default sound, or playing no sound action, such as playing a built-in default sound, or playing no sound
at all. at all.
skipping to change at line 3248 skipping to change at line 3267
used as the body text of the message, and the "SUMMARY" property MUST used as the body text of the message, and the "SUMMARY" property MUST
be used as the subject text. Any "ATTACH" properties in the "VALARM" be used as the subject text. Any "ATTACH" properties in the "VALARM"
calendar component SHOULD be sent as attachments to the message. calendar component SHOULD be sent as attachments to the message.
In a PROCEDURE alarm, the "ATTACH" property in the "VALARM" calendar In a PROCEDURE alarm, the "ATTACH" property in the "VALARM" calendar
component MUST specify a procedure or program that is intended to be component MUST specify a procedure or program that is intended to be
invoked as the alarm effect. If the procedure or program is in a invoked as the alarm effect. If the procedure or program is in a
format that cannot be rendered, then no procedure alarm will be format that cannot be rendered, then no procedure alarm will be
invoked. If the "DESCRIPTION" property is present, its value invoked. If the "DESCRIPTION" property is present, its value
specifies the argument string to be passed to the procedure or specifies the argument string to be passed to the procedure or
Dawson/Stenerson 60 Expires January 1999
program. "Calendar User Agents" that receive an iCalendar object with program. "Calendar User Agents" that receive an iCalendar object with
this category of alarm, can disable or allow the "Calendar User" to this category of alarm, can disable or allow the "Calendar User" to
disable, or otherwise ignore this type of alarm. While a very useful disable, or otherwise ignore this type of alarm. While a very useful
alarm capability, the PROCEDURE type of alarm should be treated by alarm capability, the PROCEDURE type of alarm SHOULD be treated by
the "Calendar User Agent" as a potential security risk. the "Calendar User Agent" as a potential security risk.
Example: The following example is for a "VALARM" calendar component Example: The following example is for a "VALARM" calendar component
that specifies an audio alarm that will sound at a precise time and that specifies an audio alarm that will sound at a precise time and
repeat 4 more times at 15 minute intervals: repeat 4 more times at 15 minute intervals:
BEGIN:VALARM BEGIN:VALARM
TRIGGER;VALUE=DATE-TIME:19970317T133000Z TRIGGER;VALUE=DATE-TIME:19970317T133000Z
REPEAT:4 REPEAT:4
DURATION:PT15M DURATION:PT15M
ACTION:AUDIO ACTION:AUDIO
ATTACH:ftp://host.com/pub/sounds/bell-01.wav ATTACH;FMTTYPE=audio/basic:ftp://host.com/pub/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 is scheduled start of the event or the due date/time of the to-do it is
associated with and will repeat 2 more times at 15 minute intervals: associated with and will repeat 2 more times at 15 minute intervals:
BEGIN:VALARM BEGIN:VALARM
TRIGGER:PT30M TRIGGER:-PT30M
REPEAT:2 REPEAT:2
DURATION:PT15M DURATION:PT15M
Dawson/Stenerson 60 Expires November 1998
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 not 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. repeat. The email has a subject, body and attachment link.
BEGIN:VALARM BEGIN:VALARM
TRIGGER:P2D TRIGGER:-P2D
ACTION:EMAIL ACTION:EMAIL
ATTENDEE:MAILTO:john_doe@host.com ATTENDEE:MAILTO:john_doe@host.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:http://host.com/templates/agenda.doc ATTACH;FMTTYPE=application/binary:http://host.com/templates/agen
da.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/time specifies a procedural alarm that will trigger at a precise date/time
and will repeat 23 more times at one hour intervals. The alarm will and will repeat 23 more times at one hour intervals. The alarm will
invoke a procedure file. invoke a procedure file.
Dawson/Stenerson 61 Expires January 1999
BEGIN:VALARM BEGIN:VALARM
TRIGGER;VALUE=DATE-TIME:19980101T050000Z TRIGGER;VALUE=DATE-TIME:19980101T050000Z
REPEAT:23 REPEAT:23
DURATION:PT1H DURATION:PT1H
ACTION:PROCEDURE ACTION:PROCEDURE
ATTACH:ftp://host.com/novo-procs/felizano.exe ATTACH;FMTTYPE=application/binary:ftp://host.com/novo-
procs/felizano.exe
END:VALARM END:VALARM
4.7 Calendar Properties 4.7 Calendar Properties
The Calendar Properties are attributes that apply to the iCalendar The Calendar Properties are attributes that apply to the iCalendar
object, as a whole. These properties do not appear within a calendar object, as a whole. These properties do not appear within a calendar
component. They should be specified after the "BEGIN:VCALENDAR" component. They SHOULD be specified after the "BEGIN:VCALENDAR"
property and prior to any calendar component. property and prior to any calendar component.
4.7.1 Calendar Scale 4.7.1 Calendar Scale
Property Name: CALSCALE Property Name: CALSCALE
Purpose: This property defines the calendar scale used for the Purpose: This property defines the calendar scale used for the
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.
Dawson/Stenerson 61 Expires November 1998
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. The
Gregorian calendar scale is assumed if this property is not specified Gregorian calendar scale is assumed if this property is not specified
in the iCalendar object. It is expected that other calendar scales in the iCalendar object. It is expected that other calendar scales
will be defined in other specifications or by future versions of this will be defined in other specifications or by future versions of this
memo. memo.
Format Definition: The property is defined by the following notation: Format Definition: The property is defined by the following notation:
skipping to change at line 3356 skipping to change at line 3377
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
4.7.2 Method 4.7.2 Method
Property Name: METHOD Property Name: METHOD
Dawson/Stenerson 62 Expires January 1999
Purpose: This property defines the iCalendar object method associated Purpose: This property defines the iCalendar object method associated
with the calendar object. 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 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. This property can only appear once within the iCalendar
object. If either the "METHOD" property or the Content-Type "method" object. If either the "METHOD" property or the Content-Type "method"
parameter is specified, then the other must also be specified. parameter is specified, then the other MUST also be specified.
No methods are defined by this specification. This is the subject of No methods are defined by this specification. This is the subject of
other specifications, such as the iCalendar Transport-independent other specifications, such as the iCalendar Transport-independent
Interoperability Protocol (iTIP) defined by [ITIP]. Interoperability Protocol (iTIP) defined by [ITIP].
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 some iCalendar object is merely being used to transport a snapshot of some
calendar information; without the intention of conveying a scheduling calendar information; without the intention of conveying a scheduling
semantic. semantic.
Format Definition: The property is defined by the following notation: Format Definition: The property is defined by the following notation:
method = "METHOD" metparam ":" metvalue CRLF method = "METHOD" metparam ":" metvalue CRLF
Dawson/Stenerson 62 Expires November 1998
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 request for a meeting:
METHOD:REQUEST METHOD:REQUEST
4.7.3 Product Identifier 4.7.3 Product Identifier
skipping to change at line 3411 skipping to change at line 3432
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 Dawson/Stenerson 63 Expires January 1999
Description: The vendor of the implementation SHOULD assure that this
is a globally unique identifier; using some technique such as an FPI is a globally unique identifier; using some technique such as an FPI
value, as defined in [ISO 9070]. value, as defined in [ISO 9070].
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: The property is defined by the following notation:
prodid = "PRODID" pidparam ":" pidvalue CRLF prodid = "PRODID" pidparam ":" pidvalue CRLF
pidparam = *(";" xparam) pidparam = *(";" xparam)
skipping to change at line 3441 skipping to change at line 3463
imply that English is the default language. imply that English is the default language.
PRODID:-//ABC Corporation//NONSGML My Product//EN PRODID:-//ABC Corporation//NONSGML My Product//EN
4.7.4 Version 4.7.4 Version
Property Name: VERSION Property Name: VERSION
Purpose: This property specifies the identifier corresponding to the Purpose: This property specifies the identifier corresponding to the
highest version number or the minimum and maximum range of the highest version number or the minimum and maximum range of the
Dawson/Stenerson 63 Expires November 1998
iCalendar specification that is required in order to interpret the iCalendar specification that is required in order to interpret the
iCalendar object. 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: 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.
skipping to change at line 3466 skipping to change at line 3486
Format Definition: The property is defined by the following notation: Format Definition: The 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)
Dawson/Stenerson 64 Expires January 1999
minver = <A IANA registered iCalendar version identifier> minver = <A IANA registered iCalendar version identifier>
;Minimum iCalendar version needed to parse the iCalendar object ;Minimum iCalendar version needed to parse the iCalendar object
maxver = <A IANA registered iCalendar version identifier> maxver = <A IANA registered iCalendar version identifier>
;Maximum iCalendar version needed to parse the iCalendar object ;Maximum iCalendar version needed to parse the iCalendar object
Example: The following is an example of this property: Example: The following is an example of this property:
VERSION:2.0 VERSION:2.0
skipping to change at line 3494 skipping to change at line 3515
calendar components. calendar components.
4.8.1.1 Attachment 4.8.1.1 Attachment
Property Name: ATTACH Property Name: ATTACH
Purpose: The property provides the capability to associate a document Purpose: The property provides the capability to associate a document
object with a calendar component. 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 reset to BINARY in order to include inline value type can also be set to BINARY to indicate inline binary
binary encoded content information. encoded content information.
Dawson/Stenerson 64 Expires November 1998 Property Parameters: Non-standard, inline encoding, format type and
Property Parameters: Non-standard, inline encoding, value data type value data type property parameters can be specified on this
property parameters can be specified on this property. property.
Conformance: The property can be specified in an iCalendar object. Conformance: The property can be specified in a "VEVENT", "VTODO",
"VJOURNAL" or "VALARM" calendar components.
Description: The property can be specified within "VEVENT", "VTODO", Description: The property can be specified within "VEVENT", "VTODO",
"VJOURNAL", or "VALARM" calendar components. This property can be "VJOURNAL", or "VALARM" calendar components. This property can be
specified multiple times within an iCalendar object. specified multiple times within an iCalendar object.
Format Definition: The property is defined by the following notation: Format Definition: The property is defined by the following notation:
attach = "ATTACH" attparam ":" uri CRLF attach = "ATTACH" attparam ":" uri CRLF
attach =/ "ATTACH" attparam ";" "ENCODING" "=" "BASE64" attach =/ "ATTACH" attparam ";" "ENCODING" "=" "BASE64"
";" "VALUE" "=" "BINARY" ":" binary ";" "VALUE" "=" "BINARY" ":" binary
attparam = *(";" xparam) attparam = [";" fmttypeparam] *(";" xparam)
Example: The following are examples of this property: Example: The following are examples of this property:
ATTACH:CID:jsmith.part3.960817T083000.xyzMail@host1.com ATTACH:CID:jsmith.part3.960817T083000.xyzMail@host1.com
ATTACH:FTP://xyzCorp.com/pub/reports/r-960812.ps Dawson/Stenerson 65 Expires January 1999
ATTACH;FMTTYPE=application/postscript:ftp://xyzCorp.com/pub/
reports/r-960812.ps
4.8.1.2 Categories 4.8.1.2 Categories
Property Name: CATEGORIES Property Name: CATEGORIES
Purpose: This property defines the categories for a calendar Purpose: This property defines the categories for a calendar
component. component.
Value Type: TEXT Value Type: TEXT
skipping to change at line 3552 skipping to change at line 3576
COMMA character (US-ASCII decimal 44). COMMA character (US-ASCII decimal 44).
Format Definition: The property is defined by the following notation: Format Definition: The property is defined by the following notation:
categories = "CATEGORIES" catparam ":" text *("," text) categories = "CATEGORIES" catparam ":" text *("," text)
CRLF CRLF
catparam = [";" languageparam] catparam = [";" languageparam]
*(";" xparam) *(";" xparam)
Dawson/Stenerson 65 Expires November 1998
Example: The following are examples of this property: Example: The following are examples of this property:
CATEGORIES:APPOINTMENT,EDUCATION CATEGORIES:APPOINTMENT,EDUCATION
CATEGORIES:MEETING CATEGORIES:MEETING
4.8.1.3 Classification 4.8.1.3 Classification
Property Name: CLASS Property Name: CLASS
skipping to change at line 3574 skipping to change at line 3597
calendar component. 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 can be specified once in a "VEVENT", Conformance: The property can be specified once in a "VEVENT",
"VTODO" or "VJOURNAL" calendar components. "VTODO" or "VJOURNAL" calendar components.
Dawson/Stenerson 66 Expires January 1999
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 provides a general security system within a calendar application. It provides a
method of capturing the scope of the access the calendar owner method of capturing the scope of the access the calendar owner
intends for information within an individual calendar entry. The intends for information within an individual calendar entry. The
access classification of an individual iCalendar component is useful access classification of an individual iCalendar component is useful
when measured along with the other security components of a calendar when measured along with the other security components of a calendar
system (e.g., calendar user authentication, authorization, access system (e.g., calendar user authentication, authorization, access
rights, access role, etc.). Hence, the semantics of the individual rights, access role, etc.). Hence, the semantics of the individual
access classifications cannot be completely defined by this memo access classifications cannot be completely defined by this memo
alone. Additionally, due to the "blind" nature of most exchange alone. Additionally, due to the "blind" nature of most exchange
skipping to change at line 3605 skipping to change at line 3629
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:
CLASS:PUBLIC CLASS:PUBLIC
Dawson/Stenerson 66 Expires November 1998
4.8.1.4 Comment 4.8.1.4 Comment
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 an iCalendar object. Conformance: This property can be specified in "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: The property is defined by the following notation:
comment = "COMMENT" commparam ":" text CRLF comment = "COMMENT" commparam ":" text CRLF
commparam = [";" altrepparam ] [";" languageparam] commparam = [";" altrepparam ] [";" languageparam]
*(";" xparam) *(";" xparam)
Dawson/Stenerson 67 Expires January 1999
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.
As a matter of fact\, the venue for the meeting ought to be at As a matter of fact\, the venue for the meeting ought to be at
their site. - - John their site. - - John
The data type for this property is TEXT. The data type for this property is TEXT.
4.8.1.5 Description 4.8.1.5 Description
skipping to change at line 3652 skipping to change at line 3676
Purpose: This property provides a more complete description of the Purpose: This property provides a more complete description of the
calendar component, than that provided by the "SUMMARY" property. calendar component, than that provided by the "SUMMARY" property.
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 the "VEVENT", "VTODO", Conformance: The property can be specified in the "VEVENT", "VTODO",
"VJOURNAL" and "VALARM" calendar components. The property can be "VJOURNAL" or "VALARM" calendar components. The property can be
specified multiple times only within a "VJOURNAL" calendar component. specified multiple times only within a "VJOURNAL" calendar component.
Description: This property is used in the "VEVENT" and "VTODO" to Description: This property is used in the "VEVENT" and "VTODO" to
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 capture This property is used in the "VJOURNAL" calendar component to capture
one more textual journal entries. one more textual journal entries.
Dawson/Stenerson 67 Expires November 1998
This property is used in the "VALARM" calendar component to capture This property is used in the "VALARM" calendar component to capture
the display text for a DISPLAY category of alarm, to capture the body the display text for a DISPLAY category of alarm, to capture the body
text for an EMAIL category of alarm and to capture the arguement text for an EMAIL category of alarm and to capture the argument
string for a PROCEDURE category of alarm. string for a PROCEDURE category of alarm.
Format Definition: The property is defined by the following notation: Format Definition: The property is defined by the following notation:
description = "DESCRIPTION" descparam ":" text CRLF description = "DESCRIPTION" descparam ":" text CRLF
descparam = [";" altrepparam] [";" languageparam] descparam = [";" altrepparam] [";" languageparam]
*(";" 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.\n Happy Face Conference Room. Phoenix design team design.\n Happy Face Conference Room. Phoenix design team
MUST attend this meeting.\n RSVP to team leader. MUST attend this meeting.\n RSVP to team leader.
The following is an example of the property with folding of long The following is an example of the property with folding of long
lines: lines:
Dawson/Stenerson 68 Expires January 1999
DESCRIPTION:Last draft of the new novel is to be completed DESCRIPTION:Last draft of the new novel is to be completed
for the editor's proof today. for the editor's proof today.
4.8.1.6 Geographic Position 4.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 an iCalendar object. Conformance: This property can be specified in "VEVENT" or "VTODO"
calendar components..
Description: The property value specifies latitude and longitude, in Description: The property value specifies latitude and longitude, in
that order (i.e., "LAT LON" ordering). The longitude represents the that order (i.e., "LAT LON" ordering). The longitude represents the
location east and west of the prime meridian as a positive or location east or west of the prime meridian as a positive or negative
negative real number, respectively. The latitude represents the real number, respectively. The latitude represents the location north
location north and south of the equator as a positive or negative and south of the equator as a positive or negative real number,
real number, respectively. The longitude and latitude values MUST be respectively. The longitude and latitude values MUST be specified as
specified as decimal degrees and should be specified to six decimal decimal degrees and SHOULD be specified to six decimal places. This
places. This will allow for granularity within a meter of the will allow for granularity within a meter of the geographical
geographical position. The simple formula for converting degrees- position. The simple formula for converting degrees-minutes-seconds
minutes-seconds into decimal degrees is: into 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: The property is defined by the following notation:
Dawson/Stenerson 68 Expires November 1998
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
4.8.1.7 Location 4.8.1.7 Location
Property Name: LOCATION Property Name: LOCATION
Purpose: The property defines the intended venue for the activity Purpose: The property defines the intended venue for the activity
defined by a calendar component. defined by a calendar component.
Value Type: TEXT Value Type: TEXT
Dawson/Stenerson 69 Expires January 1999
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 the "VEVENT" or Conformance: This property can be specified in "VEVENT" or "VTODO"
"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 for the location. pointing to a MIME body part containing a vCard for the location.
Format Definition: The property is defined by the following notation: Format Definition: The property is defined by the following notation:
skipping to change at line 3773 skipping to change at line 3798
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
4.8.1.8 Percent Complete 4.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-do
to convey the percent completion of a to-do to the Organizer. to convey the percent completion of a to-do to the Organizer.
Dawson/Stenerson 69 Expires November 1998
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
and one hundred. A value of "0" indicates the to-do has not yet been and one hundred. A value of "0" indicates the to-do has not yet been
started. A value of "100" indicates that the to-do has been started. A value of "100" indicates that the to-do has been
completed. Integer values in between indicate the percent partially completed. Integer values in between indicate the percent partially
complete. complete.
When a to-do is assigned to multiple individuals, the property value When a to-do is assigned to multiple individuals, the property value
indicates the percent complete for that portion of the to-do assigned 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 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 percent both individuals "A" and "B". A reply from "A" with a percent
complete of "70" indicates that "A" has completed 70% of the to-do complete of "70" indicates that "A" has completed 70% of the to-do
Dawson/Stenerson 70 Expires January 1999
assigned to them. A reply from "B" with a percent complete of "50" assigned to them. A reply from "B" with a percent complete of "50"
indicates "B" has completed 50% of the to-do assigned to them. indicates "B" has completed 50% of the to-do assigned to them.
Format Definition: The property is defined by the following notation: Format Definition: The 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%
skipping to change at line 3827 skipping to change at line 3853
specified on this property. specified on this property.
Conformance: The property can be specified in a "VEVENT" or "VTODO" Conformance: The 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: The 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 second highest priority. A value of two (US-ASCII decimal 50) is the second
highest priority. Subsequent numbers specify a decreasing ordinal highest priority. Subsequent numbers specify a decreasing ordinal
Dawson/Stenerson 70 Expires November 1998
priority. A value of nine (US-ASCII decimal 58) is the lowest priority. A value of nine (US-ASCII decimal 58) is the lowest
priority. 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 the "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 52) range of one (US-ASCII decimal 49) to four (US-ASCII decimal 52)
specifies "HIGH" priority. A value of five (US-ASCII decimal 53) is specifies "HIGH" priority. A value of five (US-ASCII decimal 53) is
the normal or "MEDIUM" priority. A value in the range of six (US- the normal or "MEDIUM" priority. A value in the range of six (US-
ASCII decimal 54) to nine (US-ASCII decimal 58) is "LOW" priority. ASCII decimal 54) to nine (US-ASCII decimal 58) is "LOW" priority.
A CUA with a priority schema of "A1", "A2", "A3", "B1", "B2", ..., A CUA with a priority schema of "A1", "A2", "A3", "B1", "B2", ...,
"C3" is mapped into this property such that a property value of one "C3" is mapped into this property such that a property value of one
(US-ASCII decimal 49) specifies "A1", a property value of two (US- (US-ASCII decimal 49) specifies "A1", a property value of two (US-
ASCII decimal 50) specifies "A2", a property value of three (US-ASCII ASCII decimal 50) specifies "A2", a property value of three (US-ASCII
decimal 51) specifies "A3", and so forth up to a property value of 9 decimal 51) specifies "A3", and so forth up to a property value of 9
(US-ASCII decimal 58) specifies "C3". (US-ASCII decimal 58) specifies "C3".
Other integer values are reserved for future use. Other integer values are reserved for future use.
Dawson/Stenerson 71 Expires January 1999
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 than priority for the event. This property may be useful when more than
one event is scheduled for a given time period. 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 specified by the following Format Definition: The property is specified by the following
notation: notation:
skipping to change at line 3877 skipping to change at line 3902
The following is an example of a property with the highest priority: The following is an example of a property with the highest 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:
PRIORITY:2 PRIORITY:2
Example: The following is an example of a property with no priority. Example: The following is an example of a property with no priority.
This is equivalent to not specifying the "PRIORITY" property.: This is equivalent to not specifying the "PRIORITY" property:
PRIORITY:0 PRIORITY:0
Dawson/Stenerson 71 Expires November 1998
4.8.1.10 Resources 4.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 anticipated
for an activity specified by a calendar entity.. for an activity specified by a calendar entity..
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 a "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: The property is defined by the following notation:
Dawson/Stenerson 72 Expires January 1999
resources = "RESOURCES" resrcparam ":" text *("," text) CRLF resources = "RESOURCES" resrcparam ":" text *("," text) CRLF
resrcparam = [";" altrepparam] [";" languageparam] resrcparam = [";" altrepparam] [";" languageparam]
*(";" 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
RESOURCES;LANGUAGE=fr:1 raton-laveur RESOURCES;LANGUAGE=fr:1 raton-laveur
skipping to change at line 3927 skipping to change at line 3951
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 for
the calendar component. 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 the "VEVENT", "VTODO" Conformance: This property can be specified in "VEVENT", "VTODO" or
and "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 is
used by the "Organizer" to provide a confirmation of the event to the used by the "Organizer" to provide a confirmation of the event to the
"Attendees". For example in a "VEVENT" calendar component, the "Attendees". For example in a "VEVENT" calendar component, the
"Organizer" can indicate that a meeting is tentative, confirmed or "Organizer" can indicate that a meeting is tentative, confirmed or
cancelled. In a "VTODO" calendar component, the "Organizer" can cancelled. In a "VTODO" calendar component, the "Organizer" can
indicate that an action item needs action, is completed, is in indicate that an action item needs action, is completed, is in
process or being worked on, or has been cancelled. In a "VJOURNAL" process or being worked on, or has been cancelled. In a "VJOURNAL"
Dawson/Stenerson 72 Expires November 1998
calendar component, the "Organizer" can indicate that a journal entry calendar component, the "Organizer" can indicate that a journal entry
is draft, final or has been cancelled or removed. is draft, final or has been cancelled or removed.
Format Definition: The property is defined by the following notation: Format Definition: The 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 statvalue = "TENTATIVE" ;Indicates event is
;tentative. ;tentative.
/ "CONFIRMED" ;Indicates event is / "CONFIRMED" ;Indicates event is
;definite. ;definite.
/ "CANCELLED" ;Indicates event was / "CANCELLED" ;Indicates event was
;cancelled. ;cancelled.
;Status values for a "VEVENT" ;Status values for a "VEVENT"
statvalue =/ "NEEDS-ACTION" ;Indicates to-do needs action. statvalue =/ "NEEDS-ACTION" ;Indicates to-do needs action.
/ "COMPLETED" ;Indicates to-do completed. / "COMPLETED" ;Indicates to-do completed.
/ "IN-PROCESS" ;Indicates to-do in process of / "IN-PROCESS" ;Indicates to-do in process of
Dawson/Stenerson 73 Expires January 1999
/ "CANCELLED" ;Indicates to-do was cancelled. / "CANCELLED" ;Indicates to-do was cancelled.
;Status values for "VTODO". ;Status values for "VTODO".
statvalue =/ "DRAFT" ;Indicates journal is draft. statvalue =/ "DRAFT" ;Indicates journal is draft.
/ "FINAL" ;Indicates journal is final. / "FINAL" ;Indicates journal is final.
/ "CANCELLED" ;Indicates journal is removed. / "CANCELLED" ;Indicates journal is removed.
;Status values for "VJOURNAL". ;Status values for "VJOURNAL".
Example: The following is an example of this property for a "VEVENT" Example: The following is an example of this property for a "VEVENT"
calendar component: calendar component:
skipping to change at line 3994 skipping to change at line 4018
Property Name: SUMMARY Property Name: SUMMARY
Purpose: This property defines a short summary or subject for the Purpose: This property defines a short summary or subject for 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.
Dawson/Stenerson 73 Expires November 1998 Conformance: The property can be specified in "VEVENT", "VTODO",
Conformance: The property can be specified in the "VEVENT", "VTODO", "VJOURNAL" or "VALARM" calendar components.
"VJOURNAL" and "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 summary "VJOURNAL" calendar components to capture a short, one line summary
about the activity or journal entry. about the activity or journal entry.
This property is used in the "VALARM" calendar component to capture This property is used in the "VALARM" calendar component to capture
the subject of an EMAIL category of alarm. the subject of an EMAIL category of alarm.
Format Definition: The property is defined by the following notation: Format Definition: The property is defined by the following notation:
summary = "SUMMARY" summparam ":" text CRLF summary = "SUMMARY" summparam ":" text CRLF
summparam = [";" altrepparam] [";" languageparam] summparam = [";" altrepparam] [";" languageparam]
*(";" xparam) *(";" xparam)
Example: The following is an example of this property: Example: The following is an example of this property:
Dawson/Stenerson 74 Expires January 1999
SUMMARY:Department Party SUMMARY:Department Party
4.8.2 Date and Time Component Properties 4.8.2 Date and Time Component Properties
The following properties specify date and time related information in The following properties specify date and time related information in
calendar components. calendar components.
4.8.2.1 Date/Time Completed 4.8.2.1 Date/Time Completed
Property Name: COMPLETED Property Name: COMPLETED
skipping to change at line 4036 skipping to change at line 4060
actually completed. actually completed.
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: The 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
Dawson/Stenerson 74 Expires November 1998
4.8.2.2 Date/Time End 4.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.
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 reset 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: This property can be specified within the "VEVENT" and Conformance: This property can be specified in "VEVENT" or
"VFREEBUSY" calendar components. "VFREEBUSY" calendar components.
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 be defines the date and time by which the event ends. The value MUST be
later in time than the value of the "DTSTART" property. later in time than the value of the "DTSTART" property.
Dawson/Stenerson 75 Expires January 1999
Within the "VFREEBUSY" calendar component, this property defines the Within the "VFREEBUSY" calendar component, this property defines the
end date and time for the free or busy time information. The time end date and time for the free or busy time information. The time
MUST be specified as in the UTC time format. The value MUST be later MUST be specified in the UTC time format. The value MUST be later in
in time than the value of the "DTSTART" property. time than the value of the "DTSTART" property.
Format Definition: The property is defined by the following notation: Format Definition: The property is defined by the following notation:
dtend = "DTEND" dtendparam":" dtendval CRLF dtend = "DTEND" dtendparam":" dtendval CRLF
dtendparam = [";" "VALUE" "=" ("DATE-TIME" / "DATE")] dtendparam = [";" "VALUE" "=" ("DATE-TIME" / "DATE")]
[";" tzidparam] [";" tzidparam]
*(";" xparam) *(";" xparam)
dtendval = date-time / date dtendval = date-time / date
skipping to change at line 4100 skipping to change at line 4123
DTEND;VALUE=DATE:19980704 DTEND;VALUE=DATE:19980704
4.8.2.3 Date/Time Due 4.8.2.3 Date/Time Due
Property Name: DUE Property Name: DUE
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 reset 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.
Dawson/Stenerson 75 Expires November 1998 Conformance: The property can be specified once in a "VTODO" calendar
Conformance: The property can be specified once within 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: The property is defined by the following notation:
due = "DUE" dueparam":" dueval CRLF due = "DUE" dueparam":" dueval CRLF
dueparam = [";" "VALUE" "=" ("DATE-TIME" / "DATE")] dueparam = [";" "VALUE" "=" ("DATE-TIME" / "DATE")]
[";" tzidparam] [";" tzidparam]
*(";" 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:
Dawson/Stenerson 76 Expires January 1999
DUE:19980430T235959Z DUE:19980430T235959Z
4.8.2.4 Date/Time Start 4.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 MUST
be one of the forms defined for the DATE-TIME value type. The value be one of the forms defined for the DATE-TIME value type. The value
type can be reset to a DATE value type. 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 within the "VEVENT", Conformance: This property can be specified in the "VEVENT", "VTODO",
"VTODO", "VFREEBUSY", and "VTIMEZONE" calendar components. "VFREEBUSY", or "VTIMEZONE" 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. The property is defines the start date and time for the event. The property is
REQUIRED in "VEVENT" calendar components. Events can have a start REQUIRED in "VEVENT" calendar components. Events can have a start
date/time but no end date/time. In that case, the event does not take date/time but no end date/time. In that case, the event does not take
up any time. up any time.
Within the "VFREEBUSY" calendar component, this property defines the Within the "VFREEBUSY" calendar component, this property defines the
start date and time for the free or busy time information. The time start date and time for the free or busy time information. The time
MUST be specified in UTC time. MUST be specified in UTC time.
Within the "VTIMEZONE" calendar component, this property defines the Within the "VTIMEZONE" calendar component, this property defines the
effective start date and time for a time zone specification. This effective start date and time for a time zone specification. This
property is REQUIRED within each STANDARD and DAYLIGHT part included property is REQUIRED within each STANDARD and DAYLIGHT part included
in "VTIMEZONE" calendar components and MUST be specified as a local in "VTIMEZONE" calendar components and MUST be specified as a local
DATE-TIME without the "TZID" property parameter. DATE-TIME without the "TZID" property parameter.
Format Definition: The property is defined by the following notation: Format Definition: The property is defined by the following notation:
Dawson/Stenerson 76 Expires November 1998
dtstart = "DTSTART" dtstparam ":" dtstval CRLF dtstart = "DTSTART" dtstparam ":" dtstval CRLF
dtstparam = [";" "VALUE" "=" ("DATE-TIME" / "DATE")] dtstparam = [";" "VALUE" "=" ("DATE-TIME" / "DATE")]
[";" tzidparam] [";" tzidparam]
*(";" 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
4.8.2.5 Duration 4.8.2.5 Duration
Property Name: DURATION Property Name: DURATION
Purpose: The property specifies a positive duration of time . Purpose: The property specifies a positive duration of time .
Dawson/Stenerson 77 Expires January 1999
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 a "VEVENT", "VTODO", Conformance: The property can be specified in "VEVENT", "VTODO",
"VFREEBUSY" and "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 end used to specify a duration of the event, instead of an explicit end
date/time. In a "VTODO" calendar component the property may be used date/time. In a "VTODO" calendar component the property may be used
to specify a duration for the to-do, instead of an explicit due to specify a duration for the to-do, instead of an explicit due
date/time. In a "VFREEBUSY" calendar component the property may be date/time. In a "VFREEBUSY" calendar component the property may be
used to specify the interval of free time being requested. In a used to specify the interval of free time being requested. In a
"VALARM" calendar component the property may be used to specify the "VALARM" calendar component the property may be used to specify the
delay period prior to repeating an alarm. delay period prior to repeating an alarm.
Format Definition: The property is defined by the following notation: Format Definition: The property is defined by the following notation:
duration = "DURATION" durparam ":" duration 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
Dawson/Stenerson 77 Expires November 1998
4.8.2.6 Free/Busy Time 4.8.2.6 Free/Busy Time
Property Name: FREEBUSY Property Name: FREEBUSY
Purpose: The property defines one or more free or busy time Purpose: The property defines one or more free or busy time
intervals. intervals.
Value Type: PERIOD. The date and time values MUST be in an UTC time Value Type: PERIOD. The date and time values MUST be in an UTC time
format. 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.
Property Parameter: "FBTYPE" and non-standard parameters can be Property Parameter: "FBTYPE" and non-standard parameters can be
specified on this property. specified on this property.
Dawson/Stenerson 78 Expires January 1999
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.
"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 end SHOULD be sorted in ascending order, based on start time and then end
time, with the earliest periods first. time, with the earliest periods first.
The "FREEBUSY" property can specify more than one value, separated by The "FREEBUSY" property can specify more than one value, separated by
the COMMA character (US-ASCII decimal 44). In such cases, the 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: The property is defined by the following notation:
freebusy = "FREEBUSY" fbparam ":" fbvalue freebusy = "FREEBUSY" fbparam ":" fbvalue
CRLF CRLF
fbparam = [";" fbtypeparam] *(";" xparam) fbparam = [";" fbtypeparam] *(";" xparam)
skipping to change at line 4269 skipping to change at line 4291
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
Dawson/Stenerson 78 Expires November 1998
4.8.2.7 Time Transparency 4.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 not
to busy time searches. 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 within a "VEVENT" Conformance: This property can be specified once in a "VEVENT"
calendar component. calendar component.
Description: Transparency is the state that determines whether an Description: Time Transparency is the characteristic of an event that
event takes up time on a calendar, and with be reflected as "busy determines whether it appears to consume time on a calendar. Events
time", or is just "penciled in" to the calendar, and will not be that consume actual time for the individual or resource associated
reflected as "busy time". If the event is transparent, then other with the calendar SHOULD be recorded as OPAQUE, allowing them to be
events can be scheduled in the same time period without there being a detected by free-busy time searches. Other events, which do not take
time period conflict. If not specified, the default state is OPAQUE.
Dawson/Stenerson 79 Expires January 1999
up the individual's (or resource's) time SHOULD be recorded as
TRANSPARENT, making them invisible to free-busy time searches.
Format Definition: The property is specified by the following Format Definition: The property is specified by the following
notation: notation:
transp = "TRANSP" tranparam ":" transvalue CRLF transp = "TRANSP" tranparam ":" transvalue CRLF
tranparam = *(";" xparam) tranparam = *(";" xparam)
transvalue = "OPAQUE" ;Blocks or opaque on busy time searches. transvalue = "OPAQUE" ;Blocks or opaque on busy time searches.
/ "TRANSPARENT" ;Transparent on busy time searches. / "TRANSPARENT" ;Transparent on busy time searches.
skipping to change at line 4326 skipping to change at line 4349
The following properties specify time zone information in calendar The following properties specify time zone information in calendar
components. components.
4.8.3.1 Time Zone Identifier 4.8.3.1 Time Zone Identifier
Property Name: TZID Property Name: TZID
Purpose: This property specifies the text value that uniquely Purpose: This property specifies the text value that uniquely
identifies the "VTIMEZONE" calendar component. identifies the "VTIMEZONE" calendar component.
Dawson/Stenerson 79 Expires November 1998
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 type component is referenced by any iCalendar properties whose data type
is either DATE-TIME or TIME and not intended to specify a UTC or is either DATE-TIME or TIME and not intended to specify a UTC or a
a"floating" time. The presence of the SOLIDUS character (US-ASCII "floating" time. The presence of the SOLIDUS character (US-ASCII
decimal 47) as a prefix, indicates that this TZID represents an decimal 47) as a prefix, indicates that this TZID represents an
unique ID in a globally defined time zone registry (when such unique ID in a globally defined time zone registry (when such
registry is defined). registry is defined).
Format Definition: This property is defined by the following Format Definition: This property is defined by the following
notation: notation:
Dawson/Stenerson 80 Expires January 1999
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 line 4377 skipping to change at line 4400
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 time
zone description. 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 the "VTIMEZONE" Conformance: This property can be specified in a "VTIMEZONE" calendar
calendar component. component.
Dawson/Stenerson 80 Expires November 1998
Description: This property may be specified in multiple languages; in Description: This property may be specified in multiple languages; in
order to provide for different language requirements. order to provide for different language requirements.
Format Definition: This property is defined by the following Format Definition: This property is defined by the following
notation: notation:
tzname = "TZNAME" tznparam ":" text CRLF tzname = "TZNAME" tznparam ":" text CRLF
tznparam = [";" languageparm] tznparam = [";" languageparm]
*(";" xparam) *(";" xparam)
skipping to change at line 4402 skipping to change at line 4424
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
Dawson/Stenerson 81 Expires January 1999
4.8.3.3 Time Zone Offset From 4.8.3.3 Time Zone Offset From
Property Name: TZOFFSETFROM Property Name: TZOFFSETFROM
Purpose: This property specifies the offset which is in use prior to Purpose: This property specifies the offset which is in use prior to
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
skipping to change at line 4423 skipping to change at line 4447
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 prior
to this time observance. It is used to calculate the absolute time at to this time observance. It is used to calculate the absolute time at
which the transition to a given observance takes place. This property which the transition to a given observance takes place. This property
MUST only be specified in a "VTIMEZONE" calendar component. A MUST only be specified in a "VTIMEZONE" calendar component. A
"VTIMEZONE" calendar component MUST include this property. The "VTIMEZONE" calendar component MUST include this property. The
property value is a signed numeric indicating the number of hours and property value is a signed numeric indicating the number of hours and
possibly minutes from UTC. Positive numbers represents time zones possibly minutes from UTC. Positive numbers represent time zones east
east of the prime meridian, or ahead of UTC. Negative numbers of the prime meridian, or ahead of UTC. Negative numbers represent
represents time zones west of the prime meridian, or behind UTC. time zones west of the prime meridian, or behind UTC.
Format Definition: The property is defined by the following notation: Format Definition: The 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:
Dawson/Stenerson 81 Expires November 1998
TZOFFSETFROM:-0500 TZOFFSETFROM:-0500
TZOFFSETFROM:+1345 TZOFFSETFROM:+1345
4.8.3.4 Time Zone Offset To 4.8.3.4 Time Zone Offset To
Property Name: TZOFFSETTO Property Name: TZOFFSETTO
Purpose: This property specifies the offset which is in use in this Purpose: This property specifies the offset which is in use in this
time zone observance. 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.
Dawson/Stenerson 82 Expires January 1999
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 time this time zone observance. It is used to calculate the absolute time
for the new observance. The property value is a signed numeric for the new observance. The property value is a signed numeric
indicating the number of hours and possibly minutes from UTC. indicating the number of hours and possibly minutes from UTC.
Positive numbers represents time zones east of the prime meridian, or Positive numbers represent time zones east of the prime meridian, or
ahead of UTC. Negative numbers represents time zones west of the ahead of UTC. Negative numbers represent time zones west of the prime
prime meridian, or behind UTC. meridian, or behind UTC.
Format Definition: The property is defined by the following notation: Format Definition: The 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
skipping to change at line 4492 skipping to change at line 4516
date version of itself. 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" calendar
component. component.
Dawson/Stenerson 82 Expires November 1998
Description: The TZURL provides a means for a VTIMEZONE component to Description: The TZURL provides a means for a VTIMEZONE component to
point to a network location that can be used to retrieve an up-to- point to a network location that can be used to retrieve an up-to-
date version of itself. This provides a hook to handle changes date version of itself. This provides a hook to handle changes
government bodies impose upon time zone definitions. Retrieval of government bodies impose upon time zone definitions. Retrieval of
this resource results in an iCalendar object containing a single this resource results in an iCalendar object containing a single
VTIMEZONE component and a METHOD property set to PUBLISH. VTIMEZONE component and a METHOD property set to PUBLISH.
Format Definition: The property is defined by the following notation: Format Definition: The 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 TZURL:http://timezones.r.us.net/tz/US-California-Los_Angeles
Dawson/Stenerson 83 Expires January 1999
4.8.4 Relationship Component Properties 4.8.4 Relationship Component Properties
The following properties specify relationship information in calendar The following properties specify relationship information in calendar
components. components.
4.8.4.1 Attendee 4.8.4.1 Attendee
Property Name: ATTENDEE Property Name: ATTENDEE
Purpose: The property defines an "Attendee" within a calendar Purpose: The property defines an "Attendee" within a calendar
skipping to change at line 4540 skipping to change at line 4565
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 MUST that specifies a group scheduled calendar entity. This property MUST
NOT be specified in an iCalendar object when publishing the calendar NOT be specified in an iCalendar object when publishing the calendar
information (e.g., NOT in an iCalendar object that specifies the information (e.g., NOT in an iCalendar object that specifies the
publication of a calendar user's busy time, event, to-do or journal). publication of a calendar user's busy time, event, to-do or journal).
This property is not specified in an iCalendar object that specifies This property is not specified in an iCalendar object that specifies
only a time zone definition or that defines calendar entities that only a time zone definition or that defines calendar entities that
are not group scheduled entities, but are entities only on a single are not group scheduled entities, but are entities only on a single
user's calendar. user's calendar.
Description: The property is MUST only be specified within calendar Description: The property MUST only be specified within calendar
components to specify participants, non-participants and the chair of components to specify participants, non-participants and the chair of
a group scheduled calendar entity. The property is specified within a group scheduled calendar entity. The property is specified within
an "EMAIL" category of the "VALARM" calendar component to specify an an "EMAIL" category of the "VALARM" calendar component to specify an
email address that is to receive the email type of iCalendar alarm. email address that is to receive the email type of iCalendar alarm.
Dawson/Stenerson 83 Expires November 1998 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 role
that the attendee will have in the calendar component; PARTSTAT, for that the attendee will have in the calendar component; PARTSTAT, for
the status of the attendee's participation; RSVP, for indicating the status of the attendee's participation; RSVP, for indicating
whether the favor of a reply is requested; CUTYPE, to indicate the whether the favor of a reply is requested; CUTYPE, to indicate the
type of calendar user; MEMBER, to indicate the groups that the type of calendar user; MEMBER, to indicate the groups that the
attendee belongs to; DELEGATED-TO, to indicate the calendar users attendee belongs to; DELEGATED-TO, to indicate the calendar users
that the original request was delegated to; and DELEGATED-FROM, to that the original request was delegated to; and DELEGATED-FROM, to
indicate whom the request was delegated from; SENT-BY, to indicate indicate whom the request was delegated from; SENT-BY, to indicate
whom is acting on behalf of the ATTENDEE; and DIR, to indicate the whom is acting on behalf of the ATTENDEE; and DIR, to indicate the
URI that points to the directory information corresponding to the URI that points to the directory information corresponding to the
attendee. These property parameters can be specified on an "ATTENDEE" attendee. These property parameters can be specified on an "ATTENDEE"
property in either a "VEVENT", "VTODO" or "VJOURNAL" calendar property in either a "VEVENT", "VTODO" or "VJOURNAL" calendar
component. They MUST not be specified in an "ATTENDEE" property in a component. They MUST not be specified in an "ATTENDEE" property in a
"VFREEBUSY" or "VALARM" calendar component. If the LANGUAGE property "VFREEBUSY" or "VALARM" calendar component. If the LANGUAGE property
parameter is specified, the identified language applies to the CN parameter is specified, the identified language applies to the CN
parameter. parameter.
Dawson/Stenerson 84 Expires January 1999
A recipient delegated a request MUST inherit the RSVP and ROLE values A recipient delegated a request MUST inherit the RSVP and ROLE values
from the attendee that delegated the request to them. from the attendee that delegated the request to them.
Multiple attendees can be specified by including multiple "ATTENDEE" Multiple attendees can be specified by including multiple "ATTENDEE"
properties within the calendar component. properties within the calendar component.
Format Definition: The property is defined by the following notation: Format Definition: The property is defined by the following notation:
attendee = "ATTENDEE" attparam ":" cal-address CRLF attendee = "ATTENDEE" attparam ":" cal-address CRLF
skipping to change at line 4601 skipping to change at line 4626
ORGANIZER:MAILTO:jsmith@host1.com ORGANIZER:MAILTO:jsmith@host1.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=TENTATIVE;CN=Henry Cabot ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=TENTATIVE;CN=Henry Cabot
:MAILTO:hcabot@host2.com :MAILTO:hcabot@host2.com
ATTENDEE;ROLE=REQ-PARTICIPANT;DELEGATED-FROM="MAILTO:bob@host.com" ATTENDEE;ROLE=REQ-PARTICIPANT;DELEGATED-FROM="MAILTO:bob@host.com"
;PARTSTAT=ACCEPTED;CN=Jane Doe:MAILTO:jdoe@host1.com ;PARTSTAT=ACCEPTED;CN=Jane Doe:MAILTO:jdoe@host1.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:
Dawson/Stenerson 84 Expires November 1998
ATTENDEE;CN=John Smith;DIR="ldap://host.com:6666/o=eDABC% ATTENDEE;CN=John Smith;DIR="ldap://host.com:6666/o=eDABC%
20Industries,c=3DUS??(cn=3DBJim%20Dolittle)":MAILTO:jimdo@ 20Industries,c=3DUS??(cn=3DBJim%20Dolittle)":MAILTO:jimdo@
host1.com host1.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@host.com ORGANIZER;CN=John Smith:MAILTO:jsmith@host.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=TENTATIVE;DELEGATED-FROM= ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=TENTATIVE;DELEGATED-FROM=
"MAILTO:iamboss@host2.com";CN=Henry Cabot:MAILTO:hcabot@ "MAILTO:iamboss@host2.com";CN=Henry Cabot:MAILTO:hcabot@
host2.com host2.com
ATTENDEE;ROLE=NON-PARTICIPANT;PARTSTAT=DELEGATED;DELEGATED-TO= ATTENDEE;ROLE=NON-PARTICIPANT;PARTSTAT=DELEGATED;DELEGATED-TO=
"MAILTO:hcabot@host2.com";CN=The Big Cheese:MAILTO:iamboss "MAILTO:hcabot@host2.com";CN=The Big Cheese:MAILTO:iamboss
@host2.com @host2.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=ACCEPTED;CN=Jane Doe ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=ACCEPTED;CN=Jane Doe
:MAILTO:jdoe@host1.com :MAILTO:jdoe@host1.com
Dawson/Stenerson 85 Expires January 1999
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@host1.com;CN=John Smith:MAILTO: ATTENDEE;SENT-BY=MAILTO:jan_doe@host1.com;CN=John Smith:MAILTO:
jsmith@host1.com jsmith@host1.com
4.8.4.2 Contact 4.8.4.2 Contact
Property Name: CONTACT Property Name: CONTACT
Purpose: The property is used to represent contact information or Purpose: The 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: The property can be specified in a "VEVENT", "VTODO",
"VJOURNAL" and "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 can information. An alternative representation for the property value can
also be specified that refers to a URI pointing to an alternate form, also be specified that refers to a URI pointing to an alternate form,
such as a vCard, for the contact information. such as a vCard, for the contact information.
Format Definition: The property is defined by the following notation: Format Definition: The property is defined by the following notation:
contact = "CONTACT" contparam ":" text CRLF contact = "CONTACT" contparam ":" text CRLF
contparam = [";" altrepparam] [";" languageparam] contparam = [";" altrepparam] [";" languageparam]
*(";" 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:
Dawson/Stenerson 85 Expires November 1998
CONTACT:Jim Dolittle\, ABC Industries\, +1-919-555-1234 CONTACT:Jim Dolittle\, ABC Industries\, +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 LDAP URI to a directory entry containing the representation of a LDAP URI to a directory entry containing the
contact information: contact information:
CONTACT;ALTREP="ldap://host.com:6666/o=3DABC%20Industries\, CONTACT;ALTREP="ldap://host.com:6666/o=3DABC%20Industries\,
c=3DUS??(cn=3DBJim%20Dolittle)":Jim Dolittle\, ABC Industries\, c=3DUS??(cn=3DBJim%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 embedded in a [MIME-DIR] content-type: information, such as a vCard embedded in a [MIME-DIR] content-type:
CONTACT;ALTREP="CID=<part3.msg970930T083000SILVER@host.com>":Jim CONTACT;ALTREP="CID=<part3.msg970930T083000SILVER@host.com>":Jim
Dolittle\, ABC Industries\, +1-919-555-1234 Dolittle\, ABC Industries\, +1-919-555-1234
Dawson/Stenerson 86 Expires January 1999
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 object containing the contact information: resource, such as a vCard object containing the contact information:
CONTACT;ALTREP="http://host.com/pdi/jdoe.vcf":Jim CONTACT;ALTREP="http://host.com/pdi/jdoe.vcf":Jim
Dolittle\, ABC Industries\, +1-919-555-1234 Dolittle\, ABC Industries\, +1-919-555-1234
4.8.4.3 Organizer 4.8.4.3 Organizer
Property Name: ORGANIZER Property Name: ORGANIZER
skipping to change at line 4711 skipping to change at line 4736
"VJOURNAL calendar components to specify the organizer of a group "VJOURNAL calendar components to specify the organizer of a group
scheduled calendar entity. The property is specified within the scheduled calendar entity. The property is specified within the
"VFREEBUSY" calendar component to specify the calendar user "VFREEBUSY" calendar component to specify the calendar user
requesting the free or busy time. When publishing a "VFREEBUSY" requesting the free or busy time. When publishing a "VFREEBUSY"
calendar component, the property is used to specify the calendar that calendar component, the property is used to specify the calendar that
the published busy time came from. 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 the specifying a pointer to the directory information associated with the
Dawson/Stenerson 86 Expires November 1998
"Organizer", SENT-BY, for specifying another calendar user that is "Organizer", SENT-BY, for specifying another calendar user that is
acting on behalf of the "Organizer". The non-standard parameters may acting on behalf of the "Organizer". The non-standard parameters may
also be specified on this property. If the LANGUAGE property also be specified on this property. If the LANGUAGE property
parameter is specified, the identified language applies to the CN parameter is specified, the identified language applies to the CN
parameter value. parameter value.
Format Definition: The property is defined by the following notation: Format Definition: The property is defined by the following notation:
organizer = "ORGANIZER" orgparam ":" organizer = "ORGANIZER" orgparam ":"
cal-address CRLF cal-address CRLF
orgparam = [";" cnparam] [";" dirparam] [";" sentbyparam] orgparam = [";" cnparam] [";" dirparam] [";" sentbyparam]
[";" languageparam] *(";" xparam) [";" languageparam] *(";" 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@host1.com ORGANIZER;CN=John Smith:MAILTO:jsmith@host1.com
Dawson/Stenerson 87 Expires January 1999
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://host.com:6666/o=3DDC%20Associ ORGANIZER;CN=JohnSmith;DIR="ldap://host.com:6666/o=3DDC%20Associ
ates,c=3DUS??(cn=3DJohn%20Smith)":MAILTO:jsmith@host1.com ates,c=3DUS??(cn=3DJohn%20Smith)":MAILTO:jsmith@host1.com
The following is an example of this property used by another calendar The following is an example of this property used by another calendar
user who is acting on behalf of the organizer, with responses user who is acting on behalf of the organizer, with responses
intended to be sent back to the organizer, not the other calendar intended to be sent back to the organizer, not the other calendar
user: user:
skipping to change at line 4758 skipping to change at line 4782
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-TIME 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 value type. See DATE-TIME value type definition for specific
interpretations of the various forms. The value type can be reset to interpretations of the various forms. The value type can be set to
DATE. DATE.
Property Parameters: Non-standard property, value data type, time Property Parameters: Non-standard property, value data type, time
zone identifier and recurrence identifier range parameters can be zone identifier and recurrence identifier range 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.
Dawson/Stenerson 87 Expires November 1998
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" property recurrence set is referenced by referring to just the "UID" property
value corresponding to the calendar component. The "RECURRENCE-ID" value corresponding to the calendar component. The "RECURRENCE-ID"
property allows the reference to an individual instance within the property allows the reference to an individual instance within the
recurrence set. recurrence set.
If the value of the "DTSTART" property is a DATE type value, then the If the value of the "DTSTART" property is a DATE type value, then the
value MUST be the calendar date for the recurrence instance. value MUST be the calendar date for the recurrence instance.
The date/time value is set to the time when the original recurrence The date/time value is set to the time when the original recurrence
instance would occur - - meaning that if the intent is to change a instance would occur; meaning that if the intent is to change a
Friday meeting to Thursday, the date/time is still set to the Friday meeting to Thursday, the date/time is still set to the
original Friday meeting. 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
Dawson/Stenerson 88 Expires January 1999
"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 recurrence instance is fixed. When the definition of the recurrence
set for a calendar component changes, and hence the "SEQUENCE" set for a calendar component changes, and hence the "SEQUENCE"
property value changes, the "RECURRENCE-ID" for a given recurrence property value changes, the "RECURRENCE-ID" for a given recurrence
instance might also change.The "RANGE" parameter is used to specify instance might also change.The "RANGE" parameter is used to specify
the effective range of recurrence instances from the instance the effective range of recurrence instances from the instance
specified by the "RECURRENCE-ID" property value. The default value specified by the "RECURRENCE-ID" property value. The default value
for the range parameter is the single recurrence instance only. The for the range parameter is the single recurrence instance only. The
value can also be "THISANDPRIOR" to indicate a range defined by 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 given recurrence instance and all prior instances or the value can be
skipping to change at line 4823 skipping to change at line 4848
RECURRENCE-ID;RANGE=THISANDFUTURE:19960120T120000Z RECURRENCE-ID;RANGE=THISANDFUTURE:19960120T120000Z
4.8.4.5 Related To 4.8.4.5 Related To
Property Name: RELATED-TO Property Name: RELATED-TO
Purpose: The property is used to represent a relationship or Purpose: The property is used to represent a relationship or
reference between one calendar component and another. reference between one calendar component and another.
Dawson/Stenerson 88 Expires November 1998
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 once in the "VEVENT", Conformance: The property can be specified once in the "VEVENT",
"VTODO" and "VJOURNAL" calendar components. "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 be unique identifier of another calendar component. This value would be
represented in a calendar component by the "UID" property. represented in a calendar component by the "UID" property.
By default, the property value points to another calendar component By default, the property value points to another calendar component
that has a PARENT relationship to the referencing object. The that has a PARENT relationship to the referencing object. The
"RELTYPE" property parameter is used to either explicitly state the "RELTYPE" property parameter is used to either explicitly state the
default PARENT relationship type to the referenced calendar component default PARENT relationship type to the referenced calendar component
or to override the default PARENT relationship type and specify or to override the default PARENT relationship type and specify
Dawson/Stenerson 89 Expires January 1999
either a CHILD or SIBLING relationship. The PARENT relationship either a CHILD or SIBLING relationship. The PARENT relationship
indicates that the calendar component is a subordinate of the indicates that the calendar component is a subordinate of the
referenced calendar component. The CHILD relationship indicates that referenced calendar component. The CHILD relationship indicates that
the calendar component is a superior of the referenced calendar the calendar component is a superior of the referenced calendar
component. The SIBLING relationship indicates that the calendar component. The SIBLING relationship indicates that the calendar
component is a peer of the referenced calendar component. component is a peer of the referenced calendar component.
Changes to a calendar component referenced by this property can have Changes to a calendar component referenced by this property can have
an implicit impact on the related calendar component. For example, if an implicit impact on the related calendar component. For example, if
a group event changes its start or end date or time, then the a group event changes its start or end date or time, then the
skipping to change at line 4879 skipping to change at line 4905
RELATED-TO:<19960401-080045-4000F192713-0052@host1.com> RELATED-TO:<19960401-080045-4000F192713-0052@host1.com>
4.8.4.6 Uniform Resource Locator 4.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.
Dawson/Stenerson 89 Expires November 1998
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 once in the "VEVENT", Conformance: This property can be specified once in the "VEVENT",
"VTODO", "VJOURNAL" and "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. This information associated with the calendar component can be found. This
memo does not attempt to standardize the form of the URI, nor the 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 URL format of the resource pointed to by the property value. If the URL
property and Content-Location MIME header are both specified, they property and Content-Location MIME header are both specified, they
MUST point to the same resource. MUST point to the same resource.
Dawson/Stenerson 90 Expires January 1999
Format Definition: The property is defined by the following notation: Format Definition: The 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
skipping to change at line 4919 skipping to change at line 4945
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", "VTODO",
"VJOURNAL" and "VFREEBUSY" calendar components. "VJOURNAL" or "VFREEBUSY" calendar components.
Description: The UID itself MUST be a globally unique identifier. The Description: The UID itself MUST be a globally unique identifier. The
generator of the identifier MUST guarantee that the identifier is generator of the identifier MUST guarantee that the identifier is
unique. There are several algorithms that can be used to accomplish unique. There are several algorithms that can be used to accomplish
this. The identifier is RECOMMENDED to be the identical syntax to the this. The identifier is RECOMMENDED to be the identical syntax to the
[RFC 822] addr-spec. A good method to assure uniqueness is to put the [RFC 822] addr-spec. A good method to assure uniqueness is to put the
domain name or a domain literal IP address of the host on which the domain name or a domain literal IP address of the host on which the
identifier was created on the right hand side of the "@", and on the identifier was created on the right hand side of the "@", and on the
left hand side, put a combination of the current calendar date and left hand side, put a combination of the current calendar date and
time of day (i.e., formatted in as a DATE-TIME value) along with some time of day (i.e., formatted in as a DATE-TIME value) along with some
other currently unique (perhaps sequential) identifier available on other currently unique (perhaps sequential) identifier available on
the system (for example, a process id number). Using a date/time the system (for example, a process id number). Using a date/time
value on the left hand side and a domain name or domain literal on value on the left hand side and a domain name or domain literal on
the right hand side makes it possible to guarantee uniqueness since the right hand side makes it possible to guarantee uniqueness since
Dawson/Stenerson 90 Expires November 1998
no two hosts should be using the same domain name or IP address at no two hosts should be using the same domain name or IP address at
the same time. Though other algorithms will work, it is RECOMMENDED the same time. Though other algorithms will work, it is RECOMMENDED
that the right hand side contain some domain identifier (either of that the right hand side contain some domain identifier (either of
the host itself or otherwise) such that the generator of the message the host itself or otherwise) such that the generator of the message
identifier can guarantee the uniqueness of the left hand side within identifier can guarantee the uniqueness of the left hand side within
the scope of that domain. the scope of that domain.
This is the method for correlating scheduling messages with the This is the method for correlating scheduling messages with the
referenced "VEVENT", "VTODO", or "VJOURNAL" calendar component. referenced "VEVENT", "VTODO", or "VJOURNAL" calendar component.
The full range of calendar components specified by a recurrence set The full range of calendar components specified by a recurrence set
is referenced by referring to just the "UID" property value is referenced by referring to just the "UID" property value
corresponding to the calendar component. The "RECURRENCE-ID" property corresponding to the calendar component. The "RECURRENCE-ID" property
allows the reference to an individual instance within the recurrence allows the reference to an individual instance within the recurrence
set. set.
Dawson/Stenerson 91 Expires January 1999
This property is an important method for group scheduling This property is an important method for group scheduling
applications to match requests with later replies, modifications or applications to match requests with later replies, modifications or
deletion requests. Calendaring and scheduling applications MUST deletion requests. Calendaring and scheduling applications MUST
generate this property in "VEVENT", "VTODO" and "VJOURNAL" calendar generate this property in "VEVENT", "VTODO" and "VJOURNAL" calendar
components to assure interoperability with other group scheduling components to assure interoperability with other group scheduling
applications. This identifier is created by the calendar system that applications. This identifier is created by the calendar system that
generates an iCalendar object. 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 characters for this property. least 255 characters for this property.
skipping to change at line 4986 skipping to change at line 5011
components. components.
4.8.5.1 Exception Date/Times 4.8.5.1 Exception Date/Times
Property Name: EXDATE Property Name: EXDATE
Purpose: This property defines the list of date/time exceptions for a Purpose: This property defines the list of date/time exceptions for a
recurring calendar component. recurring calendar component.
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 value type can be reset 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.
Dawson/Stenerson 91 Expires November 1998
Conformance: This property can be specified in an iCalendar object Conformance: This property can be specified in an iCalendar object
that includes a recurring calendar component. that includes a recurring calendar component.
Description: The exception dates, if specified, is used in computing Description: The exception dates, if specified, are used in computing
the recurrence set. The recurrence set is the complete set of the recurrence set. The recurrence set is the complete set of
recurrence instances for a calendar component. The recurrence set is recurrence instances for a calendar component. The recurrence set is
generated by considering the initial "DTSTART" property along with generated by considering the initial "DTSTART" property along with
the "RRULE", "RDATE", "EXDATE" and "EXRULE" properties contained the "RRULE", "RDATE", "EXDATE" and "EXRULE" properties contained
within the iCalendar object. The "DTSTART" property defines the first within the iCalendar object. The "DTSTART" property defines the first
instance in the recurrence set. Multiple instances of the "RRULE" and instance in the recurrence set. Multiple instances of the "RRULE" and
"EXRULE" properties can also be specified to define more "EXRULE" properties can also be specified to define more
sophisticated recurrence sets. The final recurrence set is generated sophisticated recurrence sets. The final recurrence set is generated
by gathering all of the start date-times generated by any of the by gathering all of the start date-times generated by any of the
specified "RRULE" and "RDATE" properties, and then excluding any specified "RRULE" and "RDATE" properties, and then excluding any
start date and times which fall within the union of start date and start date and times which fall within the union of start date and
Dawson/Stenerson 92 Expires January 1999
times generated by any specified "EXRULE" and "EXDATE" properties. times generated by any specified "EXRULE" and "EXDATE" properties.
This implies that start date and times within exclusion related This implies that start date and times within exclusion related
properties (i.e., "EXDATE" and "EXRULE") take precedence over those properties (i.e., "EXDATE" and "EXRULE") take precedence over those
specified by inclusion properties (i.e., "RDATE" and "RRULE"). Where specified by inclusion properties (i.e., "RDATE" and "RRULE"). Where
duplicate instances are generated by the "RRULE" and "RDATE" duplicate instances are generated by the "RRULE" and "RDATE"
properties, only one recurrence is considered. Duplicate instances properties, only one recurrence is considered. Duplicate instances
are ignored. are ignored.
The "EXDATE" property can be used to exclude the value specified in The "EXDATE" property can be used to exclude the value specified in
"DTSTART". However, in such cases the original "DTSTART" date MUST "DTSTART". However, in such cases the original "DTSTART" date MUST
skipping to change at line 5045 skipping to change at line 5071
4.8.5.2 Exception Rule 4.8.5.2 Exception Rule
Property Name: EXRULE Property Name: EXRULE
Purpose: This property defines a rule or repeating pattern for an Purpose: This property defines a rule or repeating pattern for an
exception to a recurrence set. exception to a recurrence set.
Value Type: RECUR Value Type: RECUR
Dawson/Stenerson 92 Expires November 1998
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 the "VEVENT", "VTODO" Conformance: This property can be specified in "VEVENT", "VTODO" or
or "VJOURNAL" calendar components. "VJOURNAL" calendar components.
Description: The exception rule, if specified, is used in computing Description: The exception rule, if specified, is used in computing
the recurrence set. The recurrence set is the complete set of the recurrence set. The recurrence set is the complete set of
recurrence instances for a calendar component. The recurrence set is recurrence instances for a calendar component. The recurrence set is
generated by considering the initial "DTSTART" property along with generated by considering the initial "DTSTART" property along with
the "RRULE", "RDATE", "EXDATE" and "EXRULE" properties contained the "RRULE", "RDATE", "EXDATE" and "EXRULE" properties contained
within the iCalendar object. The "DTSTART" defines the first instance within the iCalendar object. The "DTSTART" defines the first instance
in the recurrence set. Multiple instances of the "RRULE" and "EXRULE" in the recurrence set. Multiple instances of the "RRULE" and "EXRULE"
properties can also be specified to define more sophisticated properties can also be specified to define more sophisticated
recurrence sets. The final recurrence set is generated by gathering recurrence sets. The final recurrence set is generated by gathering
all of the start date-times generated by any of the specified "RRULE" all of the start date-times generated by any of the specified "RRULE"
Dawson/Stenerson 93 Expires January 1999
and "RDATE" properties, and excluding any start date and times which and "RDATE" properties, and excluding any start date and times which
fall within the union of start date and times generated by any fall within the union of start date and times generated by any
specified "EXRULE" and "EXDATE" properties. This implies that start specified "EXRULE" and "EXDATE" properties. This implies that start
date and times within exclusion related properties (i.e., "EXDATE" date and times within exclusion related properties (i.e., "EXDATE"
and "EXRULE") take precedence over those specified by inclusion and "EXRULE") take precedence over those specified by inclusion
properties (i.e., "RDATE" and "RRULE"). Where du