draft-ietf-calsch-ical-08.txt   draft-ietf-calsch-ical-09.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-08.txt> <ietf-draft-calsch-ical-09.txt>
Expires six months after: June 29, 1998 Expires six months after: August 7, 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.
skipping to change at line 47 skipping to change at line 47
and Personal Information Management (PIM) products are being extended and Personal Information Management (PIM) products are being extended
for use across the Internet, today, in proprietary ways. This memo for use across the Internet, today, in proprietary ways. This memo
has been defined to provide the definition of a common format for has been defined to provide the definition of a common format for
openly exchanging calendaring and scheduling information across the openly exchanging calendaring and scheduling information across the
Internet. Internet.
This memo is formatted as a registration for a MIME media type per This memo is formatted as a registration for a MIME media type per
[RFC 2048]. However, the format in this memo is equally applicable [RFC 2048]. However, the format in this memo is equally applicable
for use outside of a MIME message content type. for use outside of a MIME message content type.
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 January 1999 Dawson/Stenerson 1 Expires February 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 83 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 January 1999 Dawson/Stenerson 2 Expires February 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 106 skipping to change at line 106
3.5 Security Considerations .........................................10 3.5 Security Considerations .........................................10
3.6 Interoperability Considerations .................................11 3.6 Interoperability Considerations .................................11
3.7 Applications Which Use This Media Type ..........................11 3.7 Applications Which Use This Media Type ..........................11
3.8 Additional Information ..........................................11 3.8 Additional Information ..........................................11
3.9 Magic Numbers ...................................................11 3.9 Magic Numbers ...................................................11
3.10 File Extensions ................................................11 3.10 File Extensions ................................................11
3.11 Contact for Further Information: ...............................12 3.11 Contact for Further Information: ...............................12
3.12 Intended Usage .................................................12 3.12 Intended Usage .................................................12
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...................................................13
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..............................................16
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.............................................17
4.2.1 Alternate Text Representation ................................17 4.2.1 Alternate Text Representation................................18
4.2.2 Common Name ..................................................18 4.2.2 Common Name ..................................................18
4.2.3 Calendar User Type ...........................................18 4.2.3 Calendar User Type...........................................19
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..............................................21
4.2.8 Format Type ..................................................21 4.2.8 Format Type ..................................................21
4.2.9 Free/Busy Time Type ..........................................22 4.2.9 Free/Busy Time Type ..........................................22
4.2.10 Language ....................................................22 4.2.10 Language ....................................................22
4.2.11 Group or List Membership ....................................23 4.2.11 Group or List Membership ....................................23
4.2.12 Participation Status ........................................23 4.2.12 Participation Status........................................24
4.2.13 Recurrence Identifier Range .................................25 4.2.13 Recurrence Identifier Range .................................25
4.2.14 Alarm Trigger Relationship ..................................25 4.2.14 Alarm Trigger Relationship..................................26
4.2.15 Relationship Type ...........................................26 4.2.15 Relationship Type ...........................................26
4.2.16 Participation Role ..........................................26 4.2.16 Participation Role..........................................27
4.2.17 RSVP Expectation ............................................27 4.2.17 RSVP Expectation ............................................27
4.2.18 Sent By .....................................................27 4.2.18 Sent By.....................................................28
4.2.19 Time Zone Identifier ........................................28 4.2.19 Time Zone Identifier ........................................28
4.2.20 Value Data Types ............................................29 4.2.20 Value Data Types ............................................29
4.3 Property Value Data Types .......................................30 4.3 Property Value Data Types .......................................30
4.3.1 Binary .......................................................30 4.3.1 Binary .......................................................30
4.3.2 Boolean ......................................................30 4.3.2 Boolean......................................................31
4.3.3 Calendar User Address ........................................31 4.3.3 Calendar User Address ........................................31
Dawson/Stenerson 3 Expires January 1999 Dawson/Stenerson 3 Expires February 1999
4.3.4 Date .........................................................31 4.3.4 Date.........................................................32
4.3.5 Date-Time ....................................................32 4.3.5 Date-Time ....................................................32
4.3.6 Duration .....................................................34 4.3.6 Duration .....................................................34
4.3.7 Float ........................................................34 4.3.7 Float........................................................35
4.3.8 Integer ......................................................35 4.3.8 Integer ......................................................35
4.3.9 Period of Time ...............................................35 4.3.9 Period of Time...............................................36
4.3.10 Recurrence Rule .............................................36 4.3.10 Recurrence Rule.............................................37
4.3.11 Text ........................................................41 4.3.11 Text........................................................42
4.3.12 Time ........................................................42 4.3.12 Time........................................................43
4.3.13 URI .........................................................44 4.3.13 URI.........................................................45
4.3.14 UTC Offset ..................................................44 4.3.14 UTC Offset..................................................45
4.4 iCalendar Object ................................................45 4.4 iCalendar Object................................................46
4.5 Property ........................................................45 4.5 Property........................................................46
4.6 Calendar Components .............................................46 4.6 Calendar Components.............................................47
4.6.1 Event Component ..............................................47 4.6.1 Event Component..............................................48
4.6.2 To-do Component ..............................................48 4.6.2 To-do Component..............................................50
4.6.3 Journal Component ............................................49 4.6.3 Journal Component............................................51
4.6.4 Free/Busy Component ..........................................50 4.6.4 Free/Busy Component..........................................53
4.6.5 Time Zone Component ..........................................53 4.6.5 Time Zone Component..........................................55
4.6.6 Alarm Component ..............................................58 4.6.6 Alarm Component..............................................61
4.7 Calendar Properties .............................................62 4.7 Calendar Properties.............................................67
4.7.1 Calendar Scale ...............................................62 4.7.1 Calendar Scale...............................................67
4.7.2 Method .......................................................62 4.7.2 Method.......................................................67
4.7.3 Product Identifier ...........................................63 4.7.3 Product Identifier...........................................68
4.7.4 Version ......................................................64 4.7.4 Version......................................................69
4.8 Component Properties ............................................65 4.8 Component Properties............................................70
4.8.1 Descriptive Component Properties .............................65 4.8.1 Descriptive Component Properties.............................70
4.8.1.1 Attachment ...............................................65 4.8.1.1 Attachment...............................................70
4.8.1.2 Categories ...............................................66 4.8.1.2 Categories...............................................71
4.8.1.3 Classification ...........................................66 4.8.1.3 Classification...........................................72
4.8.1.4 Comment ..................................................67 4.8.1.4 Comment..................................................72
4.8.1.5 Description ..............................................68 4.8.1.5 Description..............................................73
4.8.1.6 Geographic Position ......................................69 4.8.1.6 Geographic Position......................................74
4.8.1.7 Location .................................................69 4.8.1.7 Location.................................................76
4.8.1.8 Percent Complete .........................................70 4.8.1.8 Percent Complete.........................................77
4.8.1.9 Priority .................................................71 4.8.1.9 Priority.................................................77
4.8.1.10 Resources ...............................................72 4.8.1.10 Resources...............................................79
4.8.1.11 Status ..................................................73 4.8.1.11 Status..................................................80
4.8.1.12 Summary .................................................74 4.8.1.12 Summary.................................................81
4.8.2 Date and Time Component Properties ...........................75 4.8.2 Date and Time Component Properties...........................82
4.8.2.1 Date/Time Completed ......................................75 4.8.2.1 Date/Time Completed......................................82
4.8.2.2 Date/Time End ............................................75 4.8.2.2 Date/Time End............................................82
4.8.2.3 Date/Time Due ............................................76 4.8.2.3 Date/Time Due............................................83
4.8.2.4 Date/Time Start ..........................................77 4.8.2.4 Date/Time Start..........................................84
4.8.2.5 Duration .................................................77 4.8.2.5 Duration.................................................85
4.8.2.6 Free/Busy Time ...........................................78 4.8.2.6 Free/Busy Time...........................................86
4.8.2.7 Time Transparency ........................................79 4.8.2.7 Time Transparency........................................87
4.8.3 Time Zone Component Properties ...............................80 4.8.3 Time Zone Component Properties...............................88
4.8.3.1 Time Zone Identifier .....................................80 4.8.3.1 Time Zone Identifier.....................................88
4.8.3.2 Time Zone Name ...........................................81 4.8.3.2 Time Zone Name...........................................89
4.8.3.3 Time Zone Offset From ....................................82 4.8.3.3 Time Zone Offset From....................................90
4.8.3.4 Time Zone Offset To ......................................82 4.8.3.4 Time Zone Offset To......................................91
4.8.3.5 Time Zone URL ............................................83 4.8.3.5 Time Zone URL............................................91
4.8.4 Relationship Component Properties ............................84 4.8.4 Relationship Component Properties............................92
Dawson/Stenerson 4 Expires January 1999
4.8.4.1 Attendee .................................................84
4.8.4.2 Contact ..................................................86
4.8.4.3 Organizer ................................................87
4.8.4.4 Recurrence ID ............................................88
4.8.4.5 Related To ...............................................89
4.8.4.6 Uniform Resource Locator .................................90
4.8.4.7 Unique Identifier ........................................91
4.8.5 Recurrence Component Properties ..............................92
4.8.5.1 Exception Date/Times .....................................92
4.8.5.2 Exception Rule ...........................................93
4.8.5.3 Recurrence Date/Times ....................................94
4.8.5.4 Recurrence Rule ..........................................95
4.8.6 Alarm Component Properties ..................................103
4.8.6.1 Action ..................................................103
4.8.6.2 Repeat Count ............................................104
4.8.6.3 Trigger .................................................105
4.8.7 Change Management Component Properties ......................106
4.8.7.1 Date/Time Created .......................................106
4.8.7.2 Date/Time Stamp .........................................107
4.8.7.3 Last Modified ...........................................107
4.8.7.4 Sequence Number .........................................108
4.8.8 Miscellaneous Component Properties ..........................110
4.8.8.1 Non-standard Properties .................................110
4.8.8.2 Request Status ..........................................110
5 iCalendar Object Examples..........................................112
6 Recommended Practices..............................................116
7 Registration of Content Type Elements..............................117
7.1 Registration of New and Modified iCalendar Object Methods ......117
7.2 Registration of New Properties .................................117
7.2.1 Define the property .........................................117
7.2.2 Post the Property definition ................................118
7.2.3 Allow a comment period ......................................118
7.2.4 Submit the property for approval ............................118
7.3 Property Change Control ........................................119
8 References.........................................................119
9 Acknowledgments....................................................121
10 Author's Address..................................................121
11 Full Copyright Statement..........................................122
Dawson/Stenerson 5 Expires January 1999 Dawson/Stenerson 4 Expires February 1999
4.8.4.1 Attendee.................................................92
4.8.4.2 Contact..................................................94
4.8.4.3 Organizer................................................96
4.8.4.4 Recurrence ID............................................97
4.8.4.5 Related To...............................................98
4.8.4.6 Uniform Resource Locator................................100
4.8.4.7 Unique Identifier.......................................100
4.8.5 Recurrence Component Properties.............................102
4.8.5.1 Exception Date/Times....................................102
4.8.5.2 Exception Rule..........................................103
4.8.5.3 Recurrence Date/Times...................................104
4.8.5.4 Recurrence Rule.........................................105
4.8.6 Alarm Component Properties..................................113
4.8.6.1 Action..................................................113
4.8.6.2 Repeat Count............................................114
4.8.6.3 Trigger.................................................115
4.8.7 Change Management Component Properties......................117
4.8.7.1 Date/Time Created.......................................117
4.8.7.2 Date/Time Stamp.........................................117
4.8.7.3 Last Modified...........................................118
4.8.7.4 Sequence Number.........................................119
4.8.8 Miscellaneous Component Properties..........................120
4.8.8.1 Non-standard Properties.................................120
4.8.8.2 Request Status..........................................121
5 iCalendar Object Examples..........................................123
6 Recommended Practices..............................................126
7 Registration of Content Type Elements..............................128
7.1 Registration of New and Modified iCalendar Object Methods......128
7.2 Registration of New Properties.................................128
7.2.1 Define the property.........................................128
7.2.2 Post the Property definition................................129
7.2.3 Allow a comment period......................................129
7.2.4 Submit the property for approval............................129
7.3 Property Change Control........................................130
8 References.........................................................130
9 Acknowledgments....................................................132
10 Author's Address..................................................132
11 Full Copyright Statement..........................................133
Dawson/Stenerson 5 Expires February 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
the level of interoperability possible between dissimilar calendaring the level of interoperability possible between dissimilar calendaring
skipping to change at line 287 skipping to change at line 286
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 January 1999 Dawson/Stenerson 6 Expires February 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 341
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 January 1999 Dawson/Stenerson 7 Expires February 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 371 skipping to change at line 370
specification of objects, data types, properties and property specification of objects, data types, properties and property
parameters. parameters.
[ICMS] - specifies a common terminology and abstract model; [ICMS] - specifies a common terminology and abstract model;
[ITIP] - specifies an interoperability protocol for scheduling [ITIP] - specifies an interoperability protocol for scheduling
between different implementations; between different implementations;
[IMIP] specifies an Internet email binding for [ITIP]. [IMIP] specifies an Internet email binding for [ITIP].
[IRIP] - specifies an Internet real time protocol binding for [ITIP].
This memo does not attempt to repeat the specification of concepts or This memo does not attempt to repeat the specification of concepts or
definitions from these other memos. Where possible, references are definitions from these other memos. Where possible, references are
made to the memo that provides for the specification of these made to the memo that provides for the specification of these
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
skipping to change at line 394 skipping to change at line 395
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 January 1999 Dawson/Stenerson 8 Expires February 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.
MIME media type name: text MIME media type name: text
skipping to change at line 449 skipping to change at line 449
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 January 1999 Dawson/Stenerson 9 Expires February 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 January 1999 Dawson/Stenerson 10 Expires February 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 533 skipping to change at line 533
This MIME content type is intended to define a common format for This MIME content type is intended to define a common format for
conveying calendaring and scheduling information between different conveying calendaring and scheduling information between different
systems. It is heavily based on the earlier [VCAL] industry systems. It is heavily based on the earlier [VCAL] industry
specification. specification.
3.7 Applications Which Use This Media Type 3.7 Applications Which Use This Media Type
This content-type is designed for widespread use by Internet This content-type is designed for widespread use by Internet
calendaring and scheduling applications. In addition, applications in calendaring and scheduling applications. In addition, applications in
the workflow and document management area might find this content- the workflow and document management area might find this content-
type applicable. The [ITIP] and [IMIP] Internet protocols directly type applicable. The [ITIP] and [IMIP] and [IRIP] Internet protocols
use this content-type also. Future work on an Internet calendar directly use this content-type also. Future work on an Internet
access protocol will utilize this content-type too. calendar access protocol will utilize this content-type too.
3.8 Additional Information 3.8 Additional Information
This memo defines this content-type. This memo defines this content-type.
3.9 Magic Numbers 3.9 Magic Numbers
None. None.
3.10 File Extensions 3.10 File Extensions
skipping to change at line 557 skipping to change at line 557
The file extension of "ics" is to be used to designate a file The file extension of "ics" is to be used to designate a file
containing (an arbitrary set of) calendaring and scheduling containing (an arbitrary set of) calendaring and scheduling
information consistent with this MIME content type. information consistent with this MIME content type.
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
Dawson/Stenerson 11 Expires February 1999
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 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 611 skipping to change at line 612
4 iCalendar Object Specification 4 iCalendar Object Specification
The following sections define the details of a Calendaring and The following sections define the details of a Calendaring and
Scheduling Core Object Specification. This information is intended to Scheduling Core Object Specification. This information is intended to
be an integral part of the MIME content type registration. In be an integral part of the MIME content type registration. In
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.
Dawson/Stenerson 12 Expires February 1999
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 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 667 skipping to change at line 667
; 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.
Dawson/Stenerson 13 Expires February 1999
name = x-name / iana-token name = x-name / iana-token
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 723 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 February 1999
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
skipping to change at line 774 skipping to change at line 774
For example, in the following properties a SEMICOLON is used to For example, in the following properties a SEMICOLON is used to
separate property parameters from each other, and a COMMA is used to separate property parameters from each other, and a COMMA is used to
separate property values in a value list. separate property values in a value list.
ATTENDEE;RSVP=TRUE;ROLE=REQ-PARTICIPANT:MAILTO: ATTENDEE;RSVP=TRUE;ROLE=REQ-PARTICIPANT:MAILTO:
jsmith@host.com jsmith@host.com
RDATE;VALUE=DATE:19970304,19970504,19970704,19970904 RDATE;VALUE=DATE:19970304,19970504,19970704,19970904
Dawson/Stenerson 15 Expires February 1999
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
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
skipping to change at line 826 skipping to change at line 825
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.
Dawson/Stenerson 16 Expires February 1999
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
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 881 skipping to change at line 879
/ sentbyparam ; Sent by / sentbyparam ; Sent by
/ tzidparam ; Reference to time zone object / tzidparam ; Reference to time zone object
/ valuetypeparam ; Property value data type / valuetypeparam ; Property value data type
/ ianaparam / ianaparam
; Some other IANA registered iCalendar parameter. ; Some other IANA registered iCalendar parameter.
/ xparam / xparam
; A non-standard, experimental parameter. ; A non-standard, experimental parameter.
ianaparam = iana-token "=" param-value *("," param-value) ianaparam = iana-token "=" param-value *("," param-value)
Dawson/Stenerson 17 Expires February 1999
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.
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 each be specified in a quoted-string. parameter values MUST each be specified in a quoted-string.
Example: Example:
skipping to change at line 916 skipping to change at line 914
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.
Content-Type:text/html Content-Type:text/html
Content-Id:<part3.msg.970415T083000@host.com> Content-Id:<part3.msg.970415T083000@host.com>
<html><body> <html><body>
<p><b>Project XYZ Review Meeting</b> will include the following <p><b>Project XYZ Review Meeting</b> will include the following
agenda items:<li>Market agenda items:<ol><li>Market
Overview</li><li>Finances</li><li>Project Management</li></p> Overview</li><li>Finances</li><li>Project Management</li></ol></p>
</html></body> </body></html>
4.2.2 Common Name 4.2.2 Common Name
Parameter Name: CN Parameter Name: CN
Purpose: To specify the common name to be associated with the Purpose: To specify the common name to be associated with the
calendar user specified by the property. calendar user specified by the property.
Format Definition: The property parameter is defined by the following Format Definition: The property parameter is defined by the following
notation: notation:
cnparam = "CN" "=" param-value cnparam = "CN" "=" param-value
Description: This parameter can be specified on properties with a Description: This parameter can be specified on properties with a
CAL-ADDRESS value type. The parameter specifies the common name 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
Dawson/Stenerson 18 Expires February 1999
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
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 989 skipping to change at line 988
participation to the calendar user specified by the property. participation to the calendar user specified by the property.
Format Definition: The property parameter is defined by the following Format Definition: The property parameter is defined by the following
notation: notation:
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
Dawson/Stenerson 19 Expires February 1999
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 calendar address parameter values MUST each be The individual calendar address parameter values MUST each be
specified in a quoted-string. specified in a quoted-string.
Example: Example:
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 to whom the calendar user Purpose: To specify the calendar users to whom the calendar user
specified by the property has delegated participation. specified by the property has delegated participation.
Format Definition: The property parameter is defined by the following Format Definition: The property parameter is defined by the following
notation: notation:
skipping to change at line 1043 skipping to change at line 1042
the calendar user specified by the property. the calendar user specified by the property.
Format Definition: The property parameter is defined by the following Format Definition: 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
Dawson/Stenerson 20 Expires February 1999
property. The parameter value is a URI. The individual URI parameter property. The parameter value is a URI. The individual URI parameter
values MUST each 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
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 1098 skipping to change at line 1098
4.2.8 Format Type 4.2.8 Format Type
Parameter Name: FMTTYPE Parameter Name: FMTTYPE
Purpose: To specify the content type of a referenced object. Purpose: To specify the content type of a referenced object.
Format Definition: The property parameter is defined by the following Format Definition: The property parameter is defined by the following
notation: notation:
Dawson/Stenerson 21 Expires February 1999
fmttypeparam = "FMTTYPE" "=" iana-token fmttypeparam = "FMTTYPE" "=" iana-token
; A IANA registered content type ; A IANA registered content type
/ x-name / x-name
; A non-standard content type ; A non-standard content type
Description: This parameter can be specified on properties that are Description: This parameter can be specified on properties that are
used to reference an object. The parameter specifies the content type used to reference an object. The parameter specifies the content type
of the referenced object. For example, on the "ATTACH" property, a of the referenced object. For example, on the "ATTACH" property, a
FTP type URI value does not, by itself, necessarily convey the type FTP type URI value does not, by itself, necessarily convey the type
of content associated with the resource. The parameter value MUST be of content associated with the resource. The parameter value MUST be
the TEXT for either an IANA registered content type or a non-standard the TEXT for either an IANA registered content type or a non-standard
content type. content type.
Example: Example:
Dawson/Stenerson 21 Expires January 1999
ATTACH;FMTTYPE=application/binary:ftp://domain.com/pub/docs/ ATTACH;FMTTYPE=application/binary:ftp://domain.com/pub/docs/
agenda.doc agenda.doc
4.2.9 Free/Busy Time Type 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
skipping to change at line 1152 skipping to change at line 1152
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.10 Language 4.2.10 Language
Parameter Name: LANGUAGE Parameter Name: LANGUAGE
Dawson/Stenerson 22 Expires February 1999
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
skipping to change at line 1206 skipping to change at line 1206
*("," 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 each be specified in a quoted-string. parameter values MUST each be specified in a quoted-string.
Dawson/Stenerson 23 Expires February 1999
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.12 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 1260 skipping to change at line 1260
/ 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
Dawson/Stenerson 24 Expires February 1999
/ 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
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 participation CAL-ADDRESS value type. The parameter identifies the participation
status for the calendar user specified by the property value. The status for the calendar user specified by the property value. The
parameter values differ depending on whether they are associated with parameter values differ depending on whether they are associated with
a group scheduled "VEVENT", "VTODO" or "VJOURNAL". The values MUST a group scheduled "VEVENT", "VTODO" or "VJOURNAL". The values MUST
match one of the values allowed for the given calendar component. If match one of the values allowed for the given calendar component. If
not specified on a property that allows this parameter, the default not specified on a property that allows this parameter, the default
value is NEEDS-ACTION. value is NEEDS-ACTION.
Example: Example:
ATTENDEE;PARTSTAT=DECLINED:MAILTO:jsmith@host.com ATTENDEE;PARTSTAT=DECLINED:MAILTO:jsmith@host.com
Dawson/Stenerson 24 Expires January 1999
4.2.13 Recurrence Identifier Range 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 1314 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 25 Expires February 1999
4.2.14 Alarm Trigger Relationship 4.2.14 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.15 Relationship Type 4.2.15 Relationship Type
Parameter Name: RELTYPE Parameter Name: RELTYPE
skipping to change at line 1369 skipping to change at line 1368
/ x-name) ; A non-standard, experimental / x-name) ; A non-standard, experimental
; 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
Dawson/Stenerson 26 Expires February 1999
the referenced calendar component is a peer of the calendar the referenced calendar component is a peer of the calendar
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>
4.2.16 Participation Role 4.2.16 Participation Role
skipping to change at line 1390 skipping to change at line 1391
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 1423 skipping to change at line 1422
4.2.17 RSVP Expectation 4.2.17 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:
Dawson/Stenerson 27 Expires February 1999
rsvpparam = "RSVP" "=" ("TRUE" / "FALSE") rsvpparam = "RSVP" "=" ("TRUE" / "FALSE")
; Default is FALSE ; Default is FALSE
Description: This parameter can be specified on properties with a Description: This parameter can be specified on properties with a
CAL-ADDRESS value type. The parameter identifies the expectation of a CAL-ADDRESS value type. The parameter identifies the expectation of a
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.
skipping to change at line 1445 skipping to change at line 1445
ATTENDEE;RSVP=TRUE:MAILTO:jsmith@host.com ATTENDEE;RSVP=TRUE:MAILTO:jsmith@host.com
4.2.18 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 calendar address parameter values MUST each be 1738]. The individual calendar address parameter values MUST each be
skipping to change at line 1476 skipping to change at line 1475
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.
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 = "/"
Dawson/Stenerson 28 Expires February 1999
Description: The parameter MUST be specified on the "DTSTART", Description: The parameter MUST be specified on the "DTSTART",
"DTEND", "DUE", "EXDATE" and "RDATE" properties when either a DATE- "DTEND", "DUE", "EXDATE" and "RDATE" properties when either a DATE-
TIME or TIME value type is specified and when the value is not either TIME or TIME value type is specified and when the value is not either
a UTC or a "floating" time. Refer to the DATE-TIME or TIME value type a UTC or a "floating" time. Refer to the DATE-TIME or TIME value type
definition for a description of UTC and "floating time" formats. This definition for a description of UTC and "floating time" formats. This
property parameter specifies a text value which uniquely identifies property parameter specifies a text value which uniquely identifies
the "VTIMEZONE" calendar component to be used when evaluating the the "VTIMEZONE" calendar component to be used when evaluating the
time portion of the property. The value of the TZID property time portion of the property. The value of the TZID property
parameter will be equal to the value of the TZID property for the parameter will be equal to the value of the TZID property for the
matching time zone definition. An individual "VTIMEZONE" calendar matching time zone definition. An individual "VTIMEZONE" calendar
component MUST be specified for each unique "TZID" parameter value component MUST be specified for each unique "TZID" parameter value
specified in the iCalendar object. 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).
Note: This document does not define a naming convention for time
zone identifiers. Implementers may want to use the naming
conventions defined in existing time zone specifications such as
the public-domain Olson database [TZ]. The specification of
globally unique time zone identifiers is not addressed by this
document and is left for future study.
The following are examples of this property parameter: The following are examples of this property parameter:
DTSTART;TZID=America-New_York:19980119T020000 DTSTART;TZID=US-Eastern:19980119T020000
Dawson/Stenerson 28 Expires January 1999 DTEND;TZID=US-Eastern: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
skipping to change at line 1524 skipping to change at line 1530
4.2.20 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:
Dawson/Stenerson 29 Expires February 1999
valuetypeparam = "VALUE" "=" valuetype valuetypeparam = "VALUE" "=" valuetype
valuetype = ("BINARY" valuetype = ("BINARY"
/ "BOOLEAN" / "BOOLEAN"
/ "CAL-ADDRESS" / "CAL-ADDRESS"
/ "DATE" / "DATE"
/ "DATE-TIME" / "DATE-TIME"
/ "DURATION" / "DURATION"
/ "FLOAT" / "FLOAT"
/ "INTEGER" / "INTEGER"
skipping to change at line 1555 skipping to change at line 1562
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 1580 skipping to change at line 1585
Value Name: BINARY Value Name: BINARY
Purpose: This value type is used to identify properties that contain Purpose: This value type is used to identify properties that contain
a character encoding of inline binary data. For example, an 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:
Dawson/Stenerson 30 Expires February 1999
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].
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
skipping to change at line 1612 skipping to change at line 1618
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 defined 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 1634 skipping to change at line 1639
4.3.3 Calendar User Address 4.3.3 Calendar User Address
Value Name: CAL-ADDRESS Value Name: CAL-ADDRESS
Purpose: This value type is used to identify properties that contain Purpose: This value type is used to identify properties that contain
a calendar user address. a calendar user address.
Formal Definition: The value type is as defined by the following Formal Definition: The value type is as defined by the following
notation: notation:
Dawson/Stenerson 31 Expires February 1999
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
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:
skipping to change at line 1667 skipping to change at line 1673
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 are Description: If the property permits, multiple "date" values are
specified as a COMMA character (US-ASCII decimal 44) separated list specified as a COMMA character (US-ASCII decimal 44) separated list
Dawson/Stenerson 31 Expires January 1999
of values. The format for the value type is expressed as the [ISO 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:
19970714 19970714
4.3.5 Date-Time 4.3.5 Date-Time
Value Name: DATE-TIME Value Name: DATE-TIME
Purpose: This value type is used to identify values that specify a Purpose: This value type is used to identify values that specify a
precise calendar date and time of day. precise calendar date and time of day.
Dawson/Stenerson 32 Expires February 1999
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
Description: If the property permits, multiple "date-time" values are Description: If the property permits, multiple "date-time" values are
specified as a COMMA character (US-ASCII decimal 44) separated list specified as a COMMA character (US-ASCII decimal 44) separated list
of values. 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.
skipping to change at line 1722 skipping to change at line 1727
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.
Dawson/Stenerson 33 Expires February 1999
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
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:
skipping to change at line 1766 skipping to change at line 1771
properties whose time values are specified in UTC. properties whose time values are specified in UTC.
FORM #3: DATE WITH LOCAL TIME AND TIME ZONE REFERENCE FORM #3: DATE WITH LOCAL TIME AND TIME ZONE REFERENCE
The date and local time with reference to time zone information is The date and local time with reference to time zone information is
identified by the use the TZID property parameter to reference the identified by the use the TZID property parameter to reference 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. For example, the following represents 2 AM in section on Time Zone. For example, the following represents 2 AM in
New York on Janurary 19, 1998: New York on Janurary 19, 1998:
DTSTART;TZID=America-New_York:19980119T020000 DTSTART;TZID=US-Eastern:19980119T020000
Example: The following represents July 14, 1997, at 1:30 PM in New Example: The following represents July 14, 1997, at 1:30 PM in New
York City in each of the three time formats, using the "DTSTART" York City in each of the three time formats, using the "DTSTART"
property. property.
DTSTART:19970714T133000 ;Local time DTSTART:19970714T133000 ;Local time
DTSTART:19970714T173000Z ;UTC time DTSTART:19970714T173000Z ;UTC time
DTSTART;TZID=America-NYC:19970714T133000 ;Local time and time DTSTART;TZID=US-Eastern: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:
dur-value = (["+"] / "-") "P" (dur-date / dur-time / dur-week) dur-value = (["+"] / "-") "P" (dur-date / dur-time / dur-week)
Dawson/Stenerson 34 Expires February 1999
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 are Description: If the property permits, multiple "duration" values are
specified by a COMMA character (US-ASCII decimal 44) separated list specified by a COMMA character (US-ASCII decimal 44) separated list
skipping to change at line 1832 skipping to change at line 1837
Value Name: FLOAT Value Name: FLOAT
Purpose: This value type is used to identify properties that contain Purpose: This value type is used to identify properties that contain
a real number value. a real number value.
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]
Dawson/Stenerson 34 Expires January 1999
Description: If the property permits, multiple "float" values are Description: If the property permits, multiple "float" values are
specified by a COMMA character (US-ASCII decimal 44) separated list specified by a COMMA character (US-ASCII decimal 44) separated list
of values. 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
4.3.8 Integer 4.3.8 Integer
Value Name:INTEGER Value Name:INTEGER
Dawson/Stenerson 35 Expires February 1999
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 are Description: If the property permits, multiple "integer" values are
specified by a COMMA character (US-ASCII decimal 44) separated list specified by a COMMA character (US-ASCII decimal 44) separated list
skipping to change at line 1886 skipping to change at line 1891
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 "/" dur-value 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 are Description: If the property permits, multiple "period" values are
specified by a COMMA character (US-ASCII decimal 44) separated list specified by a COMMA character (US-ASCII decimal 44) separated list
of values. There are two forms of a period of time. First, a period of values. There are two forms of a period of time. First, a period
of time is identified by its start and its end. This format is of time is identified by its start and its end. This format is
expressed as the [ISO 8601] complete representation, basic format for expressed as the [ISO 8601] complete representation, basic format for
"DATE-TIME" start of the period, followed by a SOLIDUS character (US- "DATE-TIME" start of the period, followed by a SOLIDUS character (US-
ASCII decimal 47), followed by the "DATE-TIME" of the end of the ASCII decimal 47), followed by the "DATE-TIME" of the end of the
period. The start of the period MUST be before the end of the period. period. The start of the period MUST be before the end of the period.
Dawson/Stenerson 36 Expires February 1999
Second, a period of time can also be defined by a start and a Second, a period of time can also be defined by a start and a
positive duration of time. The format is expressed as the [ISO 8601] positive duration of time. The format is expressed as the [ISO 8601]
complete representation, basic format for the "DATE-TIME" start of complete representation, basic format for the "DATE-TIME" start of
the period, followed by a SOLIDUS character (US-ASCII decimal 47), the period, followed by a SOLIDUS character (US-ASCII decimal 47),
followed by 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:
19970101T180000Z/19970102T070000Z 19970101T180000Z/19970102T070000Z
skipping to change at line 1933 skipping to change at line 1939
4.3.10 Recurrence Rule 4.3.10 Recurrence Rule
Value Name: RECUR Value Name: RECUR
Purpose: This value type is used to identify properties that contain Purpose: This value type is used to identify properties that contain
a recurrence rule specification. a recurrence rule specification.
Formal Definition: The value type is defined by the following Formal Definition: The value type is defined by the following
notation: notation:
recur = "FREQ"=freq recur = "FREQ"=freq *(
[(";" "UNTIL" "=" enddate) / (";" "COUNT" "=" 1*DIGIT)]
[";" "INTERVAL" "=" 1*DIGIT]
[";" "BYSECOND" "=" byseclist]
[";" "BYMINUTE" "=" byminlist]
[";" "BYHOUR" "=" byhrlist]
[";" "BYDAY" "=" bywdaylist]
[";" "BYMONTHDAY" "=" bymodaylist]
Dawson/Stenerson 36 Expires January 1999 ; either UNTIL or COUNT may appear in a 'recur',
[";" "BYYEARDAY" "=" byyrdaylist] ; but UNTIL and COUNT MUST NOT occur in the same 'recur'
[";" "BYWEEKNO" "=" bywknolist]
[";" "BYMONTH" "=" bymolist]
[";" "BYSETPOS" "=" bysplist]
[";" "WKST" "=" weekday)]
*(";" x-name "=" text)
;Individual rule parts MUST only be specified once.
;Rule parts need not be specified in particular any order.
( ";" "UNTIL" "=" enddate ) /
( ";" "COUNT" "=" 1*DIGIT ) /
; the rest of these keywords are optional,
; but MUST NOT occur more than once
( ";" "INTERVAL" "=" 1*DIGIT ) /
( ";" "BYSECOND" "=" byseclist ) /
( ";" "BYMINUTE" "=" byminlist ) /
( ";" "BYHOUR" "=" byhrlist ) /
( ";" "BYDAY" "=" bywdaylist ) /
( ";" "BYMONTHDAY" "=" bymodaylist ) /
( ";" "BYYEARDAY" "=" byyrdaylist ) /
( ";" "BYWEEKNO" "=" bywknolist ) /
( ";" "BYMONTH" "=" bymolist ) /
( ";" "BYSETPOS" "=" bysplist ) /
( ";" "WKST" "=" weekday ) /
( ";" x-name "=" text )
)
Dawson/Stenerson 37 Expires February 1999
freq = "SECONDLY" / "MINUTELY" / "HOURLY" / "DAILY" freq = "SECONDLY" / "MINUTELY" / "HOURLY" / "DAILY"
/ "WEEKLY" / "MONTHLY" / "YEARLY" / "WEEKLY" / "MONTHLY" / "YEARLY"
enddate = date enddate = date
enddate =/ date-time ;An UTC value enddate =/ date-time ;An UTC value
byseclist = seconds / ( seconds *("," seconds) ) byseclist = seconds / ( seconds *("," seconds) )
seconds = 1DIGIT / 2DIGIT ;0 to 59 seconds = 1DIGIT / 2DIGIT ;0 to 59
skipping to change at line 1998 skipping to change at line 2011
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) )
Dawson/Stenerson 38 Expires February 1999
setposday = yeardaynum setposday = yeardaynum
Description: If the property permits, multiple "recur" values are Description: If the property permits, multiple "recur" values are
specified by a COMMA character (US-ASCII decimal 44) separated list specified by a COMMA character (US-ASCII decimal 44) separated list
of values. 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.
skipping to change at line 2053 skipping to change at line 2066
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 indicates separated list of days of the week; MO indicates Monday; TU indicates
Tuesday; WE indicates Wednesday; TH indicates Thursday; FR indicates Tuesday; WE indicates Wednesday; TH indicates Thursday; FR indicates
Friday; SA indicates Saturday; SU indicates Sunday. Friday; SA indicates Saturday; SU indicates Sunday.
Dawson/Stenerson 39 Expires February 1999
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
skipping to change at line 2109 skipping to change at line 2121
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
Dawson/Stenerson 40 Expires February 1999
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.
Information, not contained in the rule, necessary to determine the Information, not contained in the rule, necessary to determine the
various recurrence instance start time and dates are derived from the various recurrence instance start time and dates are derived from the
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
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
skipping to change at line 2163 skipping to change at line 2174
BYMINUTE=30 BYMINUTE=30
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 Sunday in January
8:30:00 AM and 9:30:00 AM, every other year". Similarly, if the at 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.
Dawson/Stenerson 41 Expires February 1999
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:
FREQ=DAILY;COUNT=10;INTERVAL=2 FREQ=DAILY;COUNT=10;INTERVAL=2
There are other examples specified in the "RRULE" specification. There are other examples specified in 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: The character set supported by this revision of
defined by the following notation. This MUST be modified depending on iCalendar is UTF-8 and the valid subsets thereof. The value type is
character sets. For example, the definition of TSAFE-CHAR includes defined by the following notation.
ESC for character sets that use ISO 2022 character set switching and
TSAFE-CHAR should not include NON-US-ASCII when the character set is
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, ";", ":", "\", ","
Note: Certain other character sets may require modification of the
above definitions, but this is beyond the scope of this document.
Description: If the property permits, multiple "text" values are Description: If the property permits, multiple "text" values are
specified by a COMMA character (US-ASCII decimal 44) separated list specified by a COMMA character (US-ASCII decimal 44) separated list
of values. 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 MUST be escaped with a BACKSLASH character. A BACKSLASH values, they MUST be escaped with a BACKSLASH character. A BACKSLASH
character (US-ASCII decimal 92) in a "TEXT" property value MUST be character (US-ASCII decimal 92) in a "TEXT" property value MUST be
escaped with another BACKSLASH character. A COMMA character in a escaped with another BACKSLASH character. A COMMA character in a
Dawson/Stenerson 42 Expires February 1999
"TEXT" property value MUST be escaped with a BACKSLASH character (US- "TEXT" property value MUST be escaped with a BACKSLASH character (US-
ASCII decimal 92). A SEMICOLON character in a "TEXT" property value ASCII decimal 92). A SEMICOLON character in a "TEXT" property value
MUST be escaped with a BACKSLASH character (US-ASCII decimal 92). MUST be escaped with a BACKSLASH character (US-ASCII decimal 92).
However, a COLON character in a "TEXT" property value SHALL NOT be However, a COLON character in a "TEXT" property value SHALL NOT be
escaped with a BACKSLASH character.Example: A multiple line value of: escaped with a BACKSLASH character.Example: A multiple line value of:
Project XYZ Final Review Project XYZ Final Review
Conference Room - 3B Conference Room - 3B
Come Prepared. Come Prepared.
skipping to change at line 2275 skipping to change at line 2286
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 MUST only in the minute (i.e., values 0-60). The seconds value of 60 MUST only
to be used to account for "leap" seconds. Fractions of a second are to be used to account for "leap" seconds. Fractions of a second are
not 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:
Dawson/Stenerson 43 Expires February 1999
230000-0800 ;Invalid time format 230000-0800 ;Invalid time format
FORM #1 LOCAL TIME FORM #1 LOCAL TIME
The local time form is simply a time value that does not contain the The local time form is simply a time value that does not contain the
UTC designator nor does it reference a time zone. For example, 11:00 UTC designator nor does it reference a time zone. For example, 11:00
PM: PM:
230000 230000
skipping to change at line 2329 skipping to change at line 2340
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.
Dawson/Stenerson 44 Expires February 1999
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
X-TIMEOFDAY:133000Z X-TIMEOFDAY:133000Z
X-TIMEOFDAY;TZID=America-New York:083000 X-TIMEOFDAY;TZID=US-Eastern:083000
4.3.13 URI 4.3.13 URI
Value Name: URI Value Name: URI
Purpose: This value type is used to identify values that contain a Purpose: This value type is used to identify values that contain a
uniform resource identifier (URI) type of reference to the 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
skipping to change at line 2385 skipping to change at line 2396
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:
Dawson/Stenerson 45 Expires February 1999
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 [time-
second]
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" and "-000000"
allowed. are not allowed. The time-second, if present, may not be 60; if
absent, it defaults to zero.
No additional content value encoding (i.e., BACKSLASH character No additional content value encoding (i.e., BACKSLASH character
encoding) is defined for this value type. encoding) is defined for this value type.
Example: The following UTC offsets are given for standard time for Example: The following UTC offsets are given for standard time for
New York (five hours behind UTC) and Geneva (one hour ahead of UTC): New York (five hours behind UTC) and Geneva (one hour ahead of UTC):
-0500 -0500
+0100 +0100
skipping to change at line 2441 skipping to change at line 2454
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 or a calendar component. A property takes the form defined calendar or a calendar component. A property takes the form 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 Dawson/Stenerson 46 Expires February 1999
DTSTART:19960415T133000Z DTSTART:19960415T133000Z
This memo imposes no ordering of properties within an iCalendar This memo imposes no ordering of properties within an 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=US-Eastern:19980714T120000 is the same
DtStart;TzID=Eastern:19980714T120000. as DtStart;TzID=US-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.
The body of the iCalendar object is defined by the following The body of the iCalendar object is defined by the following
notation: notation:
icalbody = calprops component icalbody = calprops component
calprops = [calscale] [method] prodid version *x-prop calprops = 2*(
; 'prodid' and 'version' are both REQUIRED,
; but MUST NOT occur more than once
prodid /version /
; 'calscale' and 'method' are optional,
; but MUST NOT occur more than once
calscale /
method /
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
Dawson/Stenerson 47 Expires February 1999
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:
eventc = "BEGIN" ":" "VEVENT" CRLF eventc = "BEGIN" ":" "VEVENT" CRLF
eventprop *alarmc eventprop *alarmc
"END" ":" "VEVENT" CRLF "END" ":" "VEVENT" CRLF
eventprop = *attach *attendee *categories [class] *comment eventprop = *(
*contact [created] [description] [dtend / duration]
[dtstart] *exdate *exrule [geo] [last-mod] [location] ; the following are optional,
[organizer] [priority] *rstatus *related *resources ; but MUST NOT occur more than once
*rdate *rrule [dtstamp] [seq] [status] [summary]
[transp] [uid] [url] [recurid] *x-prop class / created / description / dtstart / geo /
last-mod / location / organizer / priority /
dtstamp / seq / status / summary / transp /
uid / url / recurid /
; either 'dtend' or 'duration' may appear in
; a 'eventprop', but 'dtend' and 'duration'
; MUST NOT occur in the same 'eventprop'
dtend / duration /
; the following are optional,
; and MAY occur more than once
attach / attendee / categories / comment /
contact / exdate / exrule / rstatus / related /
resources / rdate / rrule / x-prop
)
Dawson/Stenerson 48 Expires February 1999
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 2550 skipping to change at line 2596
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 2573 skipping to change at line 2617
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 49 Expires February 1999
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 2606 skipping to change at line 2651
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 = *(
[completed] *contact [created] [description] [dtstamp]
[dtstart] [due / duration] *exdate *exrule [geo] ; the following are optional,
[last-mod] [location] [organizer] [percent] [priority] ; but MUST NOT occur more than once
*rstatus *related *resources *rdate *rrule
[recurid] [seq] [status] [summary] [uid] [url] class / completed / created / description / dtstamp /
*x-prop dtstart / geo / last-mod / location / organizer /
percent / priority / recurid / seq / status /
summary / uid / url /
; either 'due' or 'duration' may appear in
; a 'todoprop', but 'due' and 'duration'
; MUST NOT occur in the same 'todoprop'
Dawson/Stenerson 50 Expires February 1999
due / duration /
; the following are optional,
; and MAY occur more than once
attach / attendee / categories / comment / contact /
exdate / exrule / rstatus / related / resources /
rdate / rrule / 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".
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
skipping to change at line 2661 skipping to change at line 2723
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 Dawson/Stenerson 51 Expires February 1999
*contact [created] [description] [dtstart] [dtstamp] jourprop = *(
*exdate *exrule [last-mod] [organizer] [recurid]
*related *rdate *rrule *rstatus [seq] [status] ; the following are optional,
[summary] [uid] [url] *x-prop ; but MUST NOT occur more than once
class / created / description / dtstart / dtstamp /
last-mod / organizer / recurid / seq / status /
summary / uid / url /
; the following are optional,
; and MAY occur more than once
attach / attendee / categories / comment /
contact / exdate / exrule / related / rdate /
rrule / rstatus / x-prop
)
Description: A "VJOURNAL" calendar component is a grouping of Description: A "VJOURNAL" calendar component is a grouping of
component properties that represent one or more descriptive text component properties that represent one or more descriptive text
notes associated with a particular calendar date. The "DTSTART" notes associated with a particular calendar date. The "DTSTART"
property is used to specify the calendar date that the journal 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"
skipping to change at line 2708 skipping to change at line 2782
UID:19970901T130000Z-123405@host.com UID:19970901T130000Z-123405@host.com
DTSTAMP:19970901T1300Z DTSTAMP:19970901T1300Z
DTSTART;VALUE=DATE:19970317 DTSTART;VALUE=DATE:19970317
SUMMARY:Staff meeting minutes SUMMARY:Staff meeting minutes
DESCRIPTION:1. Staff meeting: Participants include Joe\, Lisa DESCRIPTION:1. Staff meeting: Participants include Joe\, Lisa
and Bob. Aurora project plans were reviewed. There is currently and Bob. Aurora project plans were reviewed. There is currently
no budget reserves for this project. Lisa will escalate to no budget reserves for this project. Lisa will escalate to
management. Next meeting on Tuesday.\n management. Next meeting on Tuesday.\n
2. Telephone Conference: ABC Corp. sales representative called 2. Telephone Conference: ABC Corp. sales representative called
to discuss new printer. Promised to get us a demo by Friday.\n to discuss new printer. Promised to get us a demo by Friday.\n
Dawson/Stenerson 52 Expires February 1999
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
fbprop = *attendee *comment [contact] [dtstart] [dtend] fbprop = *(
[duration] [dtstamp] *freebusy [organizer] *rstatus
[uid] [url] *x-prop ; the following are optional,
; but MUST NOT occur more than once
contact / dtstart / dtend / duration / dtstamp /
organizer / uid / url /
; the following are optional,
; and MAY occur more than once
attendee / comment / freebusy / rstatus / x-prop
)
Description: A "VFREEBUSY" calendar component is a grouping of Description: A "VFREEBUSY" calendar component is a grouping of
component properties that represents either a request for, a reply 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
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 for which 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 (if it exists); and the specifies the free/busy time information (if it exists); and the
Dawson/Stenerson 53 Expires February 1999
"UID" and "DTSTAMP" properties are specified to assist in proper "UID" and "DTSTAMP" properties are specified to assist in proper
sequencing of multiple 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.
Dawson/Stenerson 51 Expires January 1999
Free/Busy information is represented with the "FREEBUSY" property. 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 2805 skipping to change at line 2892
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
Dawson/Stenerson 54 Expires February 1999
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 publish 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:
timezonec = "BEGIN" ":" "VTIMEZONE" CRLF timezonec = "BEGIN" ":" "VTIMEZONE" CRLF
tzid [last-mod] [tzurl] 1*(standardc / daylightc) 2*(
*x-prop
; 'tzid' is required, but MUST NOT occur more
; than once
tzid /
; 'last-mod' and 'tzurl' are optional,
but MUST NOT occur more than once
last-mod / tzurl /
; one of 'standardc' or 'daylightc' MUST occur
..; and each MAY occur more than once.
standardc / daylightc /
; the following is optional,
; and MAY occur more than once
x-prop
Dawson/Stenerson 55 Expires February 1999
)
"END" ":" "VTIMEZONE" CRLF "END" ":" "VTIMEZONE" CRLF
standardc = "BEGIN" ":" "STANDARD" CRLF standardc = "BEGIN" ":" "STANDARD" CRLF
tzprop tzprop
"END" ":" "STANDARD" CRLF "END" ":" "STANDARD" CRLF
daylightc = "BEGIN" ":" "DAYLIGHT" CRLF daylightc = "BEGIN" ":" "DAYLIGHT" CRLF
tzprop tzprop
"END" ":" "DAYLIGHT" CRLF "END" ":" "DAYLIGHT" CRLF
tzprop = *comment dtstart (*rdate / *rrule) tzprop = 3*(
*tzname tzoffsetto tzoffsetfrom *x-prop
; the following are each REQUIRED,
; but MUST NOT occur more than once
dtstart / tzoffsetto / tzoffsetfrom /
; the following are optional,
; and MAY occur more than once
comment / rdate / rrule / tzname / x-prop
)
Description: A time zone is unambiguously defined by the set of time Description: A time zone is unambiguously defined by the set of time
measurement rules determined by the governing body for a given measurement rules determined by the governing body for a given
geographic area. These rules describe at a minimum the base offset geographic area. These rules describe at a minimum the base offset
from UTC for the time zone, often referred to as the Standard Time from UTC for the time zone, often referred to as the Standard Time
offset. Many locations adjust their Standard Time forward or backward offset. Many locations adjust their Standard Time forward or backward
by one hour, in order to accommodate seasonal changes in number of by one hour, in order to accommodate seasonal changes in number of
daylight hours, often referred to as Daylight Saving Time. Some daylight hours, often referred to as Daylight Saving Time. Some
locations adjust their time by a fraction of an hour. Standard Time locations adjust their time by a fraction of an hour. Standard Time
is also known as Winter Time. Daylight Saving Time is also known as is also known as Winter Time. Daylight Saving Time is also known as
Advanced Time, Summer Time, or Legal Time in certain countries. The Advanced Time, Summer Time, or Legal Time in certain countries. The
following table shows the changes in time zone rules for the eastern following table shows the changes in time zone rules in effect for
United States starting from 1967. Each line represents a description New York City starting from 1967. Each line represents a description
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
Dawson/Stenerson 56 Expires February 1999
1975-1975 Feb 23, 02:00 -0400 EDT 1975-1975 Feb 23, 02:00 -0400 EDT
1976-1986 last Sun in Apr, 02:00 -0400 EDT 1976-1986 last Sun in Apr, 02:00 -0400 EDT
1987-* first Sun in Apr, 02:00 -0400 EDT 1987-* first Sun in Apr, 02:00 -0400 EDT
Note: The specification of a global time zone registry is not
addressed by this document and is left for future study.
However, implementers may find the Olson time zone database [TZ]
a useful reference. It is an informal, public-domain collection
of time zone information, which is currently being maintained by
volunteer Internet participants, and is used in several
operating systems. This database contains current and historical
time zone information for a wide variety of locations around the
globe; it provides a time zone identifier for every unique time
zone rule set in actual use since 1970, with historical data
going back to the introduction of standard time.
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
dependent on the ability to capture and convey date and time dependent on the ability to capture and convey date and time
information in an unambiguous format. The specification of current information in an unambiguous format. The specification of current
time zone information is integral to this behavior. time zone information is integral to this behavior.
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.
skipping to change at line 2926 skipping to change at line 3058
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.
Each "VTIMEZONE" calendar component consists of a collection of one Each "VTIMEZONE" calendar component consists of a collection of one
or more sub-components that describe the rule for a particular or more sub-components that describe the rule for a particular
observance (either a Standard Time or a Daylight Saving Time observance (either a Standard Time or a Daylight Saving Time
Dawson/Stenerson 57 Expires February 1999
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 2963 skipping to change at line 3096
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.
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. TZURL SHOULD refer to a resource that is
accessible by anyone who might need to interpret the object. This
SHOULD NOT normally be a file: URL or other URL that is not widely-
accessible.
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.
The mandatory "TZOFFSETFROM" property gives the UTC offset which is The mandatory "TZOFFSETFROM" property gives the UTC offset which is
in use when the onset of this time zone observance begins. in use when the onset of this time zone observance begins.
"TZOFFSETFROM" is combined with "DTSTART" to define the effective "TZOFFSETFROM" is combined with "DTSTART" to define the effective
onset for the time zone sub-component definition. For example, the onset for the time zone sub-component definition. For example, the
following represents the time at which the observance of Standard following represents the time at which the observance of Standard
Time took effect in Fall 1967 for the eastern United States: Time took effect in Fall 1967 for New York City:
DTSTART:19671029T020000 DTSTART:19671029T020000
Dawson/Stenerson 58 Expires February 1999
TZOFFSETFROM:-0400 TZOFFSETFROM:-0400
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 is 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:
skipping to change at line 3034 skipping to change at line 3170
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)
and ends no later than April 7, 1998 02:00:00 EST (i.e., latest valid and ends no later than April 7, 1998 02:00:00 EST (i.e., latest valid
date and time for EST in this scenario). For example, this can be date and time for EST in this scenario). For example, this can be
used for a recurring event that occurs every Friday, 8am-9:00 AM, used for a recurring event that occurs every Friday, 8am-9:00 AM,
starting June 1, 1997, ending December 31, 1997. starting June 1, 1997, ending December 31, 1997.
BEGIN:VTIMEZONE BEGIN:VTIMEZONE
TZID:America-New_York TZID:US-Eastern
LAST-MODIFIED:19870101T000000Z LAST-MODIFIED:19870101T000000Z
Dawson/Stenerson 59 Expires February 1999
BEGIN:STANDARD BEGIN:STANDARD
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 indefinitely. event starting today and continuing indefinitely.
BEGIN:VTIMEZONE BEGIN:VTIMEZONE
TZID:America-New_York TZID:US-Eastern
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/US-Eastern
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
skipping to change at line 3085 skipping to change at line 3221
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).
BEGIN:VTIMEZONE BEGIN:VTIMEZONE
TZID:America-New_York TZID:US--Fictitious-Eastern
LAST-MODIFIED:19870101T000000Z LAST-MODIFIED:19870101T000000Z
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
Dawson/Stenerson 60 Expires February 1999
TZNAME:EST TZNAME:EST
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:US--Fictitious-Eastern
LAST-MODIFIED:19870101T000000Z LAST-MODIFIED:19870101T000000Z
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
skipping to change at line 3145 skipping to change at line 3282
4.6.6 Alarm Component 4.6.6 Alarm Component
Component Name: VALARM Component Name: VALARM
Purpose: Provide a grouping of component properties that define an Purpose: Provide a grouping of component properties that define an
alarm. alarm.
Formal Definition: A "VALARM" calendar component is defined by the Formal Definition: A "VALARM" calendar component is defined by the
following notation: following notation:
Dawson/Stenerson 61 Expires February 1999
alarmc = "BEGIN" ":" "VALARM" CRLF alarmc = "BEGIN" ":" "VALARM" CRLF
(audioprop / dispprop / emailprop / procprop) (audioprop / dispprop / emailprop / procprop)
"END" ":" "VALARM" CRLF "END" ":" "VALARM" CRLF
audioprop = action trigger [duration repeat] [attach] *x-prop audioprop = 2*(
dispprop = action description trigger [duration ; 'action' and 'trigger' are both REQUIRED,
repeat] *x-prop ; but MUST NOT occur more than once
emailprop = action 1*attendee *attach description action / trigger /
trigger [duration repeat] summary *x-prop
Dawson/Stenerson 58 Expires January 1999 ; 'duration' and 'repeat' are both optional,
procprop = action attach [description] trigger [duration ; and MUST NOT occur more than once each,
repeat] *x-prop ; but if one occurs, so MUST the other
duration / repeat /
; the following is optional,
; but MUST NOT occur more than once
attach /
; the following is optional,
; and MAY occur more than once
x-prop
)
dispprop = 3*(
; the following are all REQUIRED,
; but MUST NOT occur more than once
action / description / trigger /
; 'duration' and 'repeat' are both optional,
; and MUST NOT occur more than once each,
; but if one occurs, so MUST the other
duration / repeat /
; the following is optional,
; and MAY occur more than once
*x-prop
)
emailprop = 4*(
Dawson/Stenerson 62 Expires February 1999
; the following are all REQUIRED,
; but MUST NOT occur more than once
action / description / trigger / summary
; the following is REQUIRED,
; and MAY occur more than once
attendee /
; 'duration' and 'repeat' are both optional,
; and MUST NOT occur more than once each,
; but if one occurs, so MUST the other
duration / repeat /
; the following are optional,
; and MAY occur more than once
attach / x-prop
)
procprop = 3*(
; the following are all REQUIRED,
; but MUST NOT occur more than once
action / attach / trigger /
; 'duration' and 'repeat' are both optional,
; and MUST NOT occur more than once each,
; but if one occurs, so MUST the other
duration / repeat /
; 'description' is optional,
; and MUST NOT occur more than once
description /
; the following is optional,
; and MAY occur more than once
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.
Dawson/Stenerson 63 Expires February 1999
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
"VALARM" calendar component in the following ways: "VALARM" calendar component in the following ways:
When the action is "AUDIO", the alarm can also include one and only When the action is "AUDIO", the alarm can also include one and only
one "ATTACH" property, which MUST point to a sound resource, which is one "ATTACH" property, which MUST point to a sound resource, which is
rendered when the alarm is triggered. rendered when the alarm is triggered.
When the action is "DISPLAY", the alarm MUST also include a When the action is "DISPLAY", the alarm MUST also include a
"DESCRIPTION" property, which contains the text to be displayed when "DESCRIPTION" property, which contains the text to be displayed when
skipping to change at line 3211 skipping to change at line 3434
"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
Dawson/Stenerson 64 Expires February 1999
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
skipping to change at line 3267 skipping to change at line 3490
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:
Dawson/Stenerson 65 Expires February 1999
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;FMTTYPE=audio/basic:ftp://host.com/pub/sounds/bell-01.aud 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
skipping to change at line 3323 skipping to change at line 3545
pointer the document template for the agenda file. pointer the document template for the agenda file.
ATTACH;FMTTYPE=application/binary:http://host.com/templates/agen ATTACH;FMTTYPE=application/binary:http://host.com/templates/agen
da.doc 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;FMTTYPE=application/binary:ftp://host.com/novo- ATTACH;FMTTYPE=application/binary:ftp://host.com/novo-
procs/felizano.exe procs/felizano.exe
END:VALARM END:VALARM
Dawson/Stenerson 66 Expires February 1999
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
skipping to change at line 3377 skipping to change at line 3599
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.
Dawson/Stenerson 67 Expires February 1999
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].
skipping to change at line 3432 skipping to change at line 3654
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.
Dawson/Stenerson 63 Expires January 1999
Description: The vendor of the implementation SHOULD assure that this 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.
Dawson/Stenerson 68 Expires February 1999
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)
pidvalue = text pidvalue = text
;Any text that describes the product and version ;Any text that describes the product and version
;and that is generally assured of being unique. ;and that is generally assured of being unique.
skipping to change at line 3486 skipping to change at line 3708
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
Dawson/Stenerson 69 Expires February 1999
4.8 Component Properties 4.8 Component Properties
The following properties can appear within calendar components, as The following properties can appear within calendar components, as
specified by each component property definition. specified by each component property definition.
4.8.1 Descriptive Component Properties 4.8.1 Descriptive Component Properties
The following properties specify descriptive information about The following properties specify descriptive information about
calendar components. calendar components.
skipping to change at line 3536 skipping to change at line 3758
"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 = [";" fmttypeparam] *(";" xparam) attparam = *(
; the following is optional,
; but MUST NOT occur more than once
(";" fmttypeparam) /
; the following is optional,
; and MAY occur more than once
(";" xparam)
)
Dawson/Stenerson 70 Expires February 1999
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
Dawson/Stenerson 65 Expires January 1999
ATTACH;FMTTYPE=application/postscript:ftp://xyzCorp.com/pub/ ATTACH;FMTTYPE=application/postscript:ftp://xyzCorp.com/pub/
reports/r-960812.ps 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.
skipping to change at line 3573 skipping to change at line 3807
a calendar component of a particular type and category. Within the a calendar component of a particular type and category. Within the
"VEVENT", "VTODO" or "VJOURNAL" calendar components, more than one "VEVENT", "VTODO" or "VJOURNAL" calendar components, more than one
category can be specified as a list of categories separated by the category can be specified as a list of categories 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:
categories = "CATEGORIES" catparam ":" text *("," text) categories = "CATEGORIES" catparam ":" text *("," text)
CRLF CRLF
catparam = [";" languageparam] catparam = *(
*(";" xparam)
; the following is optional,
; but MUST NOT occur more than once
(";" languageparam ) /
; the following is optional,
; and MAY occur more than once
(";" xparam)
)
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
Dawson/Stenerson 71 Expires February 1999
4.8.1.3 Classification 4.8.1.3 Classification
Property Name: CLASS Property Name: CLASS
Purpose: This property defines the access classification for a Purpose: This property defines the access classification for a
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 3636 skipping to change at line 3881
CLASS:PUBLIC CLASS:PUBLIC
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.
Dawson/Stenerson 72 Expires February 1999
Value Type: TEXT Value Type: TEXT
Property Parameters: Non-standard, alternate text representation and Property Parameters: Non-standard, alternate text representation and
language property parameters can be specified on this property. language property parameters can be specified on this property.
Conformance: This property can be specified in "VEVENT", "VTODO", Conformance: This property can be specified in "VEVENT", "VTODO",
"VJOURNAL", "VTIMEZONE" or "VFREEBUSY" calendar components. "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 = *(
*(";" xparam)
; the following are optional,
; but MUST NOT occur more than once
(";" altrepparam) / (";" languageparam) /
; the following is optional,
; and MAY occur more than once
(";" 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
Property Name: DESCRIPTION Property Name: DESCRIPTION
Purpose: This property provides a more complete description of the Purpose: This property provides a more complete description of the
skipping to change at line 3679 skipping to change at line 3935
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" or "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.
Dawson/Stenerson 73 Expires February 1999
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.
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 argument 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 = *(
*(";" xparam)
; the following are optional,
; but MUST NOT occur more than once
(";" altrepparam) / (";" languageparam) /
; the following is optional,
; and MAY occur more than once
(";" 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.
Dawson/Stenerson 74 Expires February 1999
Property Parameters: Non-standard property parameters can be Property Parameters: Non-standard property parameters can be
specified on this property. specified on this property.
Conformance: This property can be specified in "VEVENT" or "VTODO" Conformance: This property can be specified in "VEVENT" or "VTODO"
calendar components.. calendar components..
Description: The property value specifies latitude and longitude, in Description: 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 or west of the prime meridian as a positive or negative location east or west of the prime meridian as a positive or negative
real number, respectively. The latitude represents the location north real number, respectively. The longitude and latitude values MAY be
and south of the equator as a positive or negative real number, specified up to six decimal places, which will allow for accuracy to
respectively. The longitude and latitude values MUST be specified as within one meter of geographical position. Receiving applications
decimal degrees and SHOULD be specified to six decimal places. This MUST accept values of this precision and MAY truncate values of
will allow for granularity within a meter of the geographical greater precision.
position. The simple formula for converting degrees-minutes-seconds
into decimal degrees is: Values for latitude and longitude shall be expressed as decimal
fractions of degrees. Whole degrees of latitude shall be represented
by a two-digit decimal number ranging from 0 through 90. Whole
degrees of longitude shall be represented by a decimal number ranging
from 0 through 180. When a decimal fraction of a degree is specified,
it shall be separated from the whole number of degrees by a decimal
point.
Latitudes north of the equator shall be specified by a plus sign (+),
or by the absence of a minus sign (-), preceding the digits
designating degrees. Latitudes south of the Equator shall be
designated by a minus sign (-) preceding the digits designating
degrees. A point on the Equator shall be assigned to the Northern
Hemisphere.
Longitudes east of the prime meridian shall be specified by a plus
sign (+), or by the absence of a minus sign (-), preceding the digits
designating degrees. Longitudes west of the meridian shall be
designated by minus sign (-) preceding the digits designating
degrees. A point on the prime meridian shall be assigned to the
Eastern Hemisphere. A point on the 180th meridian shall be assigned
to the Western Hemisphere. One exception to this last convention is
permitted. For the special condition of describing a band of latitude
around the earth, the East Bounding Coordinate data element shall be
assigned the value +180 (180) degrees.
Any spatial address with a latitude of +90 (90) or -90 degrees will
specify the position at the North or South Pole, respectively. The
component for longitude may have any legal value.
With the exception of the special condition described above, this
form is specified in Department of Commerce, 1986, Representation of
geographic point locations for information interchange (Federal
Information Processing Standard 70-1): Washington, Department of
Commerce, National Institute of Standards and Technology.
The simple formula for converting degrees-minutes-seconds into
decimal degrees is:
decimal = degrees + minutes/60 + seconds/3600. decimal = degrees + minutes/60 + seconds/3600.
Dawson/Stenerson 75 Expires February 1999
Format Definition: The property is defined by the following notation: Format Definition: The property is defined by the following notation:
geo = "GEO" geoparam ":" geovalue CRLF geo = "GEO" geoparam ":" geovalue CRLF
geoparam = *(";" xparam) geoparam = *(";" xparam)
geovalue = float ";" float geovalue = float ";" float
;Latitude and Longitude components ;Latitude and Longitude components
Example: The following is an example of this property: Example: The following is an example of this property:
skipping to change at line 3762 skipping to change at line 4067
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 "VEVENT" or "VTODO" Conformance: This property can be specified in "VEVENT" or "VTODO"
calendar component. calendar component.
Description: Specific venues such as conference or meeting rooms may Description: Specific venues such as conference or meeting rooms may
be explicitly specified using this property. An alternate be explicitly specified using this property. An alternate
representation may be specified that is a URI that points to representation may be specified that is a URI that points to
directory information with more structured specification of the directory information with more structured specification of the
location. For example, the alternate representation may specify location. For example, the alternate representation may specify
either an LDAP URI pointing to an LDAP server entry or a CID URI either an LDAP URI pointing to an LDAP server entry or a CID URI
pointing to a MIME body part containing a vCard 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:
location = "LOCATION locparam ":" text CRLF location = "LOCATION locparam ":" text CRLF
locparam = [";" altrepparam] [";" languageparam] locparam = *(
*(";" xparam)
; the following are optional,
; but MUST NOT occur more than once
(";" altrepparam) / (";" languageparam) /
; the following is optional,
; and MAY occur more than once
(";" xparam)
)
Dawson/Stenerson 76 Expires February 1999
Example: The following are some examples of this property: Example: The following are some examples of this property:
LOCATION:Conference Room - F123, Bldg. 002 LOCATION:Conference Room - F123, Bldg. 002
LOCATION;ALTREP="http://xyzcorp.com/conf-rooms/f123.vcf": LOCATION;ALTREP="http://xyzcorp.com/conf-rooms/f123.vcf":
Conference Room - F123, Bldg. 002 Conference Room - F123, Bldg. 002
4.8.1.8 Percent Complete 4.8.1.8 Percent Complete
Property Name: PERCENT-COMPLETE Property Name: PERCENT-COMPLETE
skipping to change at line 3817 skipping to change at line 4133
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 3840 skipping to change at line 4154
PERCENT-COMPLETE:39 PERCENT-COMPLETE:39
4.8.1.9 Priority 4.8.1.9 Priority
Property Name: PRIORITY Property Name: PRIORITY
Purpose: The property defines the relative priority for a calendar Purpose: The property defines the relative priority for a calendar
component. component.
Dawson/Stenerson 77 Expires February 1999
Value Type: INTEGER Value Type: INTEGER
Property Parameters: Non-standard property parameters can be Property Parameters: Non-standard property parameters can be
specified on this property. specified on this property.
Conformance: The property can be specified in a "VEVENT" or "VTODO" Conformance: 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
skipping to change at line 3872 skipping to change at line 4187
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 3896 skipping to change at line 4210
prioparam = *(";" xparam) prioparam = *(";" xparam)
privalue = integer ;Must be in the range [0..9] privalue = integer ;Must be in the range [0..9]
; All other values are reserved for future use ; All other values are reserved for future use
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
Dawson/Stenerson 78 Expires February 1999
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
skipping to change at line 3927 skipping to change at line 4242
Conformance: This property can be specified in "VEVENT" or "VTODO" Conformance: This property can be specified in "VEVENT" or "VTODO"
calendar component. calendar component.
Description: The property value is an arbitrary text. More than one Description: The property value is an arbitrary text. More than one
resource can be specified as a list of resources separated by the resource can be specified as a list of resources separated by the
COMMA character (US-ASCII decimal 44). COMMA character (US-ASCII decimal 44).
Format Definition: The property is defined by the following notation: Format Definition: 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 = *(
*(";" xparam)
; the following are optional,
; but MUST NOT occur more than once
(";" altrepparam) / (";" languageparam) /
; the following is optional,
; and MAY occur more than once
(";" 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
Dawson/Stenerson 79 Expires February 1999
4.8.1.11 Status 4.8.1.11 Status
Property Name: STATUS Property Name: STATUS
Purpose: This property defines the overall status or confirmation for Purpose: This property defines the overall status or confirmation 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
skipping to change at line 3981 skipping to change at line 4307
;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:
Dawson/Stenerson 80 Expires February 1999
STATUS:TENTATIVE STATUS:TENTATIVE
The following is an example of this property for a "VTODO" calendar The following is an example of this property for a "VTODO" calendar
component: component:
STATUS:NEEDS-ACTION STATUS:NEEDS-ACTION
The following is an example of this property for a "VJOURNAL" The following is an example of this property for a "VJOURNAL"
calendar component: calendar component:
skipping to change at line 4032 skipping to change at line 4357
"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 = *(
*(";" xparam)
; the following are optional,
; but MUST NOT occur more than once
(";" altrepparam) / (";" languageparam) /
; the following is optional,
; and MAY occur more than once
(";" 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 Dawson/Stenerson 81 Expires February 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 4092 skipping to change at line 4428
Property Parameters: Non-standard, value data type, time zone Property Parameters: Non-standard, value data type, time zone
identifier property parameters can be specified on this property. identifier property parameters can be specified on this property.
Conformance: This property can be specified in "VEVENT" or 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 Dawson/Stenerson 82 Expires February 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 in the UTC time format. The value MUST be later in MUST be specified in the UTC time format. The value MUST be later 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 = *(
[";" tzidparam]
*(";" xparam) ; the following are optional,
; but MUST NOT occur more than once
(";" "VALUE" "=" ("DATE-TIME" / "DATE")) /
(";" tzidparam) /
; the following is optional,
; and MAY occur more than once
(";" xparam)
)
dtendval = date-time / date dtendval = date-time / date
;Value MUST match value type ;Value MUST match value type
Example: The following is an example of this property: Example: The following is an example of this property:
DTEND:19960401T235959Z DTEND:19960401T235959Z
DTEND;VALUE=DATE:19980704 DTEND;VALUE=DATE:19980704
skipping to change at line 4134 skipping to change at line 4481
Property Parameters: Non-standard, value data type, time zone Property Parameters: Non-standard, value data type, time zone
identifier property parameters can be specified on this property. identifier property parameters can be specified on this property.
Conformance: The property can be specified once in a "VTODO" calendar Conformance: The property can be specified once in a "VTODO" calendar
component. 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.
Dawson/Stenerson 83 Expires February 1999
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 = *(
[";" tzidparam]
; the following are optional,
; but MUST NOT occur more than once
(";" "VALUE" "=" ("DATE-TIME" / "DATE")) /
(";" tzidparam) /
; the following is optional,
; and MAY occur more than once
*(";" xparam) *(";" xparam)
)
dueval = date-time / date dueval = date-time / date
;Value MUST match value type ;Value MUST match value type
Example: The following is an example of this property: Example: The following is an example of this property:
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
skipping to change at line 4176 skipping to change at line 4534
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.
Dawson/Stenerson 84 Expires February 1999
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:
dtstart = "DTSTART" dtstparam ":" dtstval CRLF dtstart = "DTSTART" dtstparam ":" dtstval CRLF
dtstparam = [";" "VALUE" "=" ("DATE-TIME" / "DATE")] dtstparam = *(
[";" tzidparam]
; the following are optional,
; but MUST NOT occur more than once
(";" "VALUE" "=" ("DATE-TIME" / "DATE")) /
(";" tzidparam) /
; the following is optional,
; and MAY occur more than once
*(";" xparam) *(";" xparam)
)
dtstval = date-time / date dtstval = date-time / date
;Value MUST match value type ;Value MUST match value type
Example: The following is an example of this property: Example: The following is an example of this property:
DTSTART:19980118T073000Z DTSTART:19980118T073000Z
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 "VEVENT", "VTODO", Conformance: The property can be specified in "VEVENT", "VTODO",
"VFREEBUSY" or "VALARM" calendar components. "VFREEBUSY" or "VALARM" calendar components.
Description: In a "VEVENT" calendar component the property may be Description: In a "VEVENT" calendar component the property may be
used to specify a duration of the event, instead of an explicit 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
Dawson/Stenerson 85 Expires February 1999
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 ":" dur-value CRLF duration = "DURATION" durparam ":" dur-value CRLF
;consisting of a positive duration of time. ;consisting of a positive duration of time.
durparam = *(";" xparam) durparam = *(";" xparam)
skipping to change at line 4257 skipping to change at line 4628
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).
Dawson/Stenerson 86 Expires February 1999
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 = *(
; the following is optional,
; but MUST NOT occur more than once
(";" fbtypeparam) /
; the following is optional,
; and MAY occur more than once
(";" xparam)
)
fbvalue = period *["," period] fbvalue = period *["," period]
;Time value MUST be in the UTC time format. ;Time value MUST be in the UTC time format.
Example: The following are some examples of this property: Example: The following are some examples of this property:
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
skipping to change at line 4311 skipping to change at line 4694
specified on this property. specified on this property.
Conformance: This property can be specified once in a "VEVENT" Conformance: This property can be specified once in a "VEVENT"
calendar component. calendar component.
Description: Time Transparency is the characteristic of an event that Description: Time Transparency is the characteristic of an event that
determines whether it appears to consume time on a calendar. Events determines whether it appears to consume time on a calendar. Events
that consume actual time for the individual or resource associated that consume actual time for the individual or resource associated
with the calendar SHOULD be recorded as OPAQUE, allowing them to be with the calendar SHOULD be recorded as OPAQUE, allowing them to be
detected by free-busy time searches. Other events, which do not take detected by free-busy time searches. Other events, which do not take
Dawson/Stenerson 79 Expires January 1999
up the individual's (or resource's) time SHOULD be recorded as up the individual's (or resource's) time SHOULD be recorded as
TRANSPARENT, making them invisible to free-busy time searches. TRANSPARENT, making them invisible to free-busy time searches.
Dawson/Stenerson 87 Expires February 1999
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.
;Default value is OPAQUE ;Default value is OPAQUE
skipping to change at line 4365 skipping to change at line 4747
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 a is either DATE-TIME or TIME and not intended to specify a UTC or 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).
Note: This document does not define a naming convention for time
zone identifiers. Implementers may want to use the naming
conventions defined in existing time zone specifications such as
the public-domain Olson database [TZ]. The specification of
Dawson/Stenerson 88 Expires February 1999
globally unique time zone identifiers is not addressed by this
document and is left for future study.
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:
TZID:America-New_York TZID:US-Eastern
TZID:California-Los_Angeles TZID:California-Los_Angeles
The following is an example of a globally unique time zone The following is an example of a fictitious globally unique time zone
identifier: identifier:
TZID:/US-New_York-New_York TZID:/US-New_York-New_York
4.8.3.2 Time Zone Name 4.8.3.2 Time Zone Name
Property Name: TZNAME Property Name: TZNAME
Purpose: This property specifies the customary designation for a time Purpose: This property specifies the customary designation for a time
zone description. zone description.
skipping to change at line 4411 skipping to change at line 4801
component. component.
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 = *(
*(";" xparam)
; the following is optional,
; but MUST NOT occur more than once
Dawson/Stenerson 89 Expires February 1999
(";" languageparam) /
; the following is optional,
; and MAY occur more than once
(";" xparam)
)
Example: The following are example of this property: Example: The following are example of this property:
TZNAME:EST TZNAME:EST
The following is an example of this property when two different The following is an example of this property when two different
languages for the time zone name are specified: languages for the time zone name are specified:
TZNAME;LANGUAGE=en:EST TZNAME;LANGUAGE=en:EST
TZNAME;LANGUAGE=fr-CA:HNE TZNAME;LANGUAGE=fr-CA:HNE
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 4460 skipping to change at line 4860
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 90 Expires February 1999
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 represent time zones east of the prime meridian, or Positive numbers represent time zones east of the prime meridian, or
ahead of UTC. Negative numbers represent time zones west of the prime ahead of UTC. Negative numbers represent time zones west of the 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:
skipping to change at line 4513 skipping to change at line 4913
Purpose: The TZURL provides a means for a VTIMEZONE component to Purpose: 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. 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.
Dawson/Stenerson 91 Expires February 1999
Conformance: This property can be specified in a "VTIMEZONE" calendar Conformance: This property can be specified in a "VTIMEZONE" calendar
component. component.
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 4568 skipping to change at line 4967
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 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
Dawson/Stenerson 92 Expires February 1999
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.
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
attparam = [";" cutypeparam] [";"memberparam] [";" roleparam] attparam = *(
[";" partstatparam] [";" rsvpparam] [";" deltoparam]
[";" delfromparam] [";" sentbyparam] [";"cnparam]
[";" dirparam] [";" languageparam] *(";" xparam)
Example: The following are examples of this property's use for a to- ; the following are optional,
; but MUST NOT occur more than once
(";" cutypeparam) / (";"memberparam) /
(";" roleparam) / (";" partstatparam) /
(";" rsvpparam) / (";" deltoparam) /
(";" delfromparam) / (";" sentbyparam) /
(";"cnparam) / (";" dirparam) /
(";" languageparam) /
; the following is optional,
; and MAY occur more than once
(";" xparam)
)
Example: The following are examples of this property’s use for a to-
do: do:
Dawson/Stenerson 93 Expires February 1999
ORGANIZER:MAILTO:jsmith@host1.com ORGANIZER:MAILTO:jsmith@host1.com
ATTENDEE;MEMBER="MAILTO:DEV-GROUP@host2.com": ATTENDEE;MEMBER="MAILTO:DEV-GROUP@host2.com":
MAILTO:joecool@host2.com MAILTO:joecool@host2.com
ATTENDEE;DELEGATED-FROM="MAILTO:immud@host3.com": ATTENDEE;DELEGATED-FROM="MAILTO:immud@host3.com":
MAILTO:ildoit@host1.com MAILTO:ildoit@host1.com
The following is an example of this property used for specifying The following is an example of this property used for specifying
multiple attendees to an event: multiple attendees to an event:
ORGANIZER:MAILTO:jsmith@host1.com ORGANIZER:MAILTO:jsmith@host1.com
skipping to change at line 4643 skipping to change at line 5058
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.
Dawson/Stenerson 94 Expires February 1999
Conformance: The property can be specified in a "VEVENT", "VTODO", Conformance: The property can be specified in a "VEVENT", "VTODO",
"VJOURNAL" or "VFREEBUSY" calendar component. "VJOURNAL" or "VFREEBUSY" calendar component.
Description: The property value consists of textual contact Description: The property value consists of textual contact
information. An alternative representation for the property value 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 = *(
*(";" xparam)
; the following are optional,
; but MUST NOT occur more than once
(";" altrepparam) / (";" languageparam) /
; the following is optional,
; and MAY occur more than once
(";" xparam)
)
Example: The following is an example of this property referencing Example: The following is an example of this property referencing
textual contact information: textual contact information:
CONTACT:Jim Dolittle\, ABC Industries\, +1-919-555-1234 CONTACT:Jim Dolittle\, ABC Industries\, +1-919-555-1234
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:
skipping to change at line 4698 skipping to change at line 5124
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
Dawson/Stenerson 95 Expires February 1999
4.8.4.3 Organizer 4.8.4.3 Organizer
Property Name: ORGANIZER Property Name: ORGANIZER
Purpose: The property defines the organizer for a calendar component. Purpose: The property defines the organizer for a calendar component.
Value Type: CAL-ADDRESS Value Type: CAL-ADDRESS
Property Parameters: Non-standard, language, common name, directory Property Parameters: Non-standard, language, common name, directory
entry reference, sent by property parameters can be specified on this entry reference, sent by property parameters can be specified on this
skipping to change at line 4747 skipping to change at line 5173
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 = *(
[";" languageparam] *(";" xparam)
; the following are optional,
; but MUST NOT occur more than once
(";" cnparam) / (";" dirparam) / (";" sentbyparam) /
(";" languageparam) /
; the following is optional,
; and MAY occur more than once
Dawson/Stenerson 96 Expires February 1999
(";" 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 4801 skipping to change at line 5239
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.
Dawson/Stenerson 97 Expires February 1999
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
"THISANDFUTURE" to indicate a range defined by the given recurrence "THISANDFUTURE" to indicate a range defined by the given recurrence
instance and all subsequent instances. instance and all subsequent instances.
Format Definition: The property is defined by the following notation: Format Definition: The property is defined by the following notation:
recurid = "RECURRENCE-ID" ridparam ":" ridval CRLF recurid = "RECURRENCE-ID" ridparam ":" ridval CRLF
ridparam = [";" "VALUE" "=" ("DATE-TIME" / "DATE)] ridparam = *(
[";" tzidparam] [";" rangeparam]
*(";" xparam) ; the following are optional,
; but MUST NOT occur more than once
(";" "VALUE" "=" ("DATE-TIME" / "DATE)) /
(";" tzidparam) / (";" rangeparam) /
; the following is optional,
; and MAY occur more than once
(";" xparam)
)
ridval = date-time / date ridval = date-time / date
;Value MUST match value type ;Value MUST match value type
Example: The following are examples of this property: Example: The following are examples of this property:
RECURRENCE-ID;VALUE=DATE:19960401 RECURRENCE-ID;VALUE=DATE:19960401
RECURRENCE-ID;RANGE=THISANDFUTURE:19960120T120000Z RECURRENCE-ID;RANGE=THISANDFUTURE:19960120T120000Z
4.8.4.5 Related To 4.8.4.5 Related To
Property Name: RELATED-TO Property Name: RELATED-TO
Dawson/Stenerson 98 Expires February 1999
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.
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" or "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 4889 skipping to change at line 5336
component is canceled or deleted, then there is an implied impact to component is canceled or deleted, then there is an implied impact to
the related CHILD calendar components. This property is intended only the related CHILD calendar components. This property is intended only
to provide information on the relationship of calendar components. It to provide information on the relationship of calendar components. It
is up to the target calendar system to maintain any property is up to the target calendar system to maintain any property
implications of this relationship. implications of this relationship.
Format Definition: The property is defined by the following notation: Format Definition: The property is defined by the following notation:
related = "RELATED-TO" [relparam] ":" text CRLF related = "RELATED-TO" [relparam] ":" text CRLF
relparam = [";" reltypeparam] relparam = *(
*(";" xparm)
; the following is optional,
; but MUST NOT occur more than once
(";" reltypeparam) /
; the following is optional,
; and MAY occur more than once
(";" xparm)
Dawson/Stenerson 99 Expires February 1999
)
The following is an example of this property: The following is an example of this property:
RELATED-TO:<jsmith.part7.19960817T083000.xyzMail@host3.com> RELATED-TO:<jsmith.part7.19960817T083000.xyzMail@host3.com>
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
skipping to change at line 4921 skipping to change at line 5380
"VTODO", "VJOURNAL" or "VFREEBUSY" calendar components. "VTODO", "VJOURNAL" or "VFREEBUSY" calendar components.
Description: This property may be used in a calendar component to Description: This property may be used in a calendar component to
convey a location where a more dynamic rendition of the calendar convey a location where a more dynamic rendition of the calendar
information associated with the calendar component can be found. 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 4944 skipping to change at line 5402
Property Name: UID Property Name: UID
Purpose: This property defines the persistent, globally unique Purpose: This property defines the persistent, globally unique
identifier for the calendar component. identifier for the calendar component.
Value Type: TEXT Value Type: TEXT
Property Parameters: Non-standard property parameters can be Property Parameters: Non-standard property parameters can be
specified on this property. specified on this property.
Dawson/Stenerson 100 Expires February 1999
Conformance: The property MUST be specified in the "VEVENT", "VTODO", Conformance: The property MUST be specified in the "VEVENT", "VTODO",
"VJOURNAL" or "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
skipping to change at line 4976 skipping to change at line 5435
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 4998 skipping to change at line 5456
Format Definition: The property is defined by the following notation: Format Definition: The property is defined by the following notation:
uid = "UID" uidparam ":" text CRLF uid = "UID" uidparam ":" text CRLF
uidparam = *(";" xparam) uidparam = *(";" xparam)
Example: The following is an example of this property: Example: The following is an example of this property:
UID:19960401T080045Z-4000F192713-0052@host1.com UID:19960401T080045Z-4000F192713-0052@host1.com
Dawson/Stenerson 101 Expires February 1999
4.8.5 Recurrence Component Properties 4.8.5 Recurrence Component Properties
The following properties specify recurrence information in calendar The following properties specify recurrence information in calendar
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
skipping to change at line 5031 skipping to change at line 5490
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
still be maintained by the calendaring and scheduling system because still be maintained by the calendaring and scheduling system because
the original "DTSTART" value has inherent usage dependencies by other the original "DTSTART" value has inherent usage dependencies by other
properties such as the "RECURRENCE-ID". properties such as the "RECURRENCE-ID".
Format Definition: The property is defined by the following notation: Format Definition: The property is defined by the following notation:
exdate = "EXDATE" exdtparam ":" exdtval *("," exdtval) CRLF exdate = "EXDATE" exdtparam ":" exdtval *("," exdtval) CRLF
exdtparam = [";" "VALUE" "=" ("DATE-TIME" / "DATE")] exdtparam = *(
[";" tzidparam]
*(";" xparam) Dawson/Stenerson 102 Expires February 1999
; the following are optional,
; but MUST NOT occur more than once
(";" "VALUE" "=" ("DATE-TIME" / "DATE")) /
(";" tzidparam) /
; the following is optional,
; and MAY occur more than once
(";" xparam)
)
exdtval = date-time / date exdtval = 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:
EXDATE:19960402T010000Z,19960403T010000Z,19960404T010000Z EXDATE:19960402T010000Z,19960403T010000Z,19960404T010000Z
4.8.5.2 Exception Rule 4.8.5.2 Exception Rule
skipping to change at line 5087 skipping to change at line 5556
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 duplicate instances are properties (i.e., "RDATE" and "RRULE"). Where duplicate instances are
generated by the "RRULE" and "RDATE" properties, only one recurrence generated by the "RRULE" and "RDATE" properties, only one recurrence
is considered. Duplicate instances are ignored. is considered. Duplicate instances are ignored.
Dawson/Stenerson 103 Expires February 1999
The "EXRULE" property can be used to exclude the value specified in The "EXRULE" 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
still be maintained by the calendaring and scheduling system because still be maintained by the calendaring and scheduling system because
the original "DTSTART" value has inherent usage dependencies by other the original "DTSTART" value has inherent usage dependencies by other
properties such as the "RECURRENCE-ID". properties such as the "RECURRENCE-ID".
Format Definition: The property is defined by the following notation: Format Definition: The property is defined by the following notation:
exrule = "EXRULE" exrparam ":" recur CRLF exrule = "EXRULE" exrparam ":" recur CRLF
skipping to change at line 5144 skipping to change at line 5612
identifier property parameters can be specified on this property. identifier property parameters can be specified on this property.
Conformance: The property can be specified in "VEVENT", "VTODO", Conformance: The property can be specified in "VEVENT", "VTODO",
"VJOURNAL" or "VTIMEZONE" calendar components. "VJOURNAL" or "VTIMEZONE" calendar components.
Description: This property can appear along with the "RRULE" property Description: This property can appear along with the "RRULE" property
to define an aggregate set of repeating occurrences. When they both to define an aggregate set of repeating occurrences. When they both
appear in an iCalendar object, the recurring events are defined by appear in an iCalendar object, the recurring events are defined by
the union of occurrences defined by both the "RDATE" and "RRULE". the union of occurrences defined by both the "RDATE" and "RRULE".
Dawson/Stenerson 94 Expires January 1999
The recurrence dates, if specified, are used in computing the The recurrence dates, if specified, are used in computing the
recurrence set. The recurrence set is the complete set of recurrence recurrence set. The recurrence set is the complete set of recurrence
instances for a calendar component. The recurrence set is generated instances for a calendar component. The recurrence set is generated
by considering the initial "DTSTART" property along with the "RRULE", by considering the initial "DTSTART" property along with the "RRULE",
"RDATE", "EXDATE" and "EXRULE" properties contained within the "RDATE", "EXDATE" and "EXRULE" properties contained within the
iCalendar object. The "DTSTART" property defines the first instance iCalendar object. The "DTSTART" property 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"
Dawson/Stenerson 104 Expires February 1999
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"
and "RDATE" properties, and excluding any start date/times which fall and "RDATE" properties, and excluding any start date/times which fall
within the union of start date/times generated by any specified within the union of start date/times generated by any specified
"EXRULE" and "EXDATE" properties. This implies that start date/times "EXRULE" and "EXDATE" properties. This implies that start date/times
within exclusion related properties (i.e., "EXDATE" and "EXRULE") within exclusion related properties (i.e., "EXDATE" and "EXRULE")
take precedence over those specified by inclusion properties (i.e., take precedence over those specified by inclusion properties (i.e.,
"RDATE" and "RRULE"). Where duplicate instances are generated by the "RDATE" and "RRULE"). Where duplicate instances are generated by the
"RRULE" and "RDATE" properties, only one recurrence is considered. "RRULE" and "RDATE" properties, only one recurrence is considered.
Duplicate instances are ignored. Duplicate instances are ignored.
Format Definition: The property is defined by the following notation: Format Definition: The property is defined by the following notation:
rdate = "RDATE" rdtparam ":" rdtval *("," rdtval) CRLF rdate = "RDATE" rdtparam ":" rdtval *("," rdtval) CRLF
rdtparam = [";" "VALUE" "=" ("DATE-TIME" / "DATE" rdtparam = *(
/ "PERIOD")]
[";" tzidparam] ; the following are optional,
*(";" xparam) ; but MUST NOT occur more than once
(";" "VALUE" "=" ("DATE-TIME" / "DATE" / "PERIOD")) /
(";" tzidparam) /
; the following is optional,
; and MAY occur more than once
(";" xparam)
)
rdtval = date-time / date / period rdtval = date-time / date / period
;Value MUST match value type ;Value MUST match value type
Example: The following are examples of this property: Example: The following are examples of this property:
RDATE:19970714T123000Z RDATE:19970714T123000Z
RDATE;TZID=US-EASTERN:19970714T083000 RDATE;TZID=US-EASTERN:19970714T083000
skipping to change at line 5195 skipping to change at line 5674
RDATE;VALUE=DATE:19970101,19970120,19970217,19970421 RDATE;VALUE=DATE:19970101,19970120,19970217,19970421
19970526,19970704,19970901,19971014,19971128,19971129,19971225 19970526,19970704,19970901,19971014,19971128,19971129,19971225
4.8.5.4 Recurrence Rule 4.8.5.4 Recurrence Rule
Property Name: RRULE Property Name: RRULE
Purpose: This property defines a rule or repeating pattern for Purpose: This property defines a rule or repeating pattern for
recurring events, to-dos, or time zone definitions. recurring events, to-dos, or time zone definitions.
Dawson/Stenerson 105 Expires February 1999
Value Type: RECUR Value Type: RECUR
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 95 Expires January 1999
Conformance: This property can be specified one or more times in Conformance: This property can be specified one or more times in
recurring "VEVENT", "VTODO" and "VJOURNAL" calendar components. It recurring "VEVENT", "VTODO" and "VJOURNAL" calendar components. It
can also be specified once in each STANDARD or DAYLIGHT sub-component can also be specified once in each STANDARD or DAYLIGHT sub-component
of the "VTIMEZONE" calendar component. of the "VTIMEZONE" calendar component.
Description: The recurrence rule, if specified, is used in computing Description: The recurrence 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
skipping to change at line 5249 skipping to change at line 5728
notation: notation:
rrule = "RRULE" rrulparam ":" recur CRLF rrule = "RRULE" rrulparam ":" recur CRLF
rrulparam = *(";" xparam) rrulparam = *(";" xparam)
Example: All examples assume the Eastern United States time zone. Example: All examples assume the Eastern United States time zone.
Daily for 10 occurrences: Daily for 10 occurrences:
DTSTART;TZID=America-New York:19970902T090000 DTSTART;TZID=US-Eastern:19970902T090000
Dawson/Stenerson 106 Expires February 1999
RRULE:FREQ=DAILY;COUNT=10 RRULE:FREQ=DAILY;COUNT=10
==> (1997 9:00 AM EDT)September 2-11 ==> (1997 9:00 AM EDT)September 2-11
Daily until December 24, 1997: Daily until December 24, 1997:
Dawson/Stenerson 96 Expires January 1999 DTSTART;TZID=US-Eastern:19970902T090000
DTSTART;TZID=America-New York:19970902T090000
RRULE:FREQ=DAILY;UNTIL=19971224T000000Z RRULE:FREQ=DAILY;UNTIL=19971224T000000Z
==> (1997 9:00 AM EDT)September 2-30;October 1-25 ==> (1997 9:00 AM EDT)September 2-30;October 1-25
(1997 9:00 AM EST)October 26-31;November 1-30;December 1-23 (1997 9:00 AM EST)October 26-31;November 1-30;December 1-23
Every other day - forever: Every other day - forever:
DTSTART;TZID=America-New York:19970902T090000 DTSTART;TZID=US-Eastern:19970902T090000
RRULE:FREQ=DAILY;INTERVAL=2 RRULE:FREQ=DAILY;INTERVAL=2
==> (1997 9:00 AM EDT)September2,4,6,8...24,26,28,30; ==> (1997 9:00 AM EDT)September2,4,6,8...24,26,28,30;
October 2,4,6...20,22,24 October 2,4,6...20,22,24
(1997 9:00 AM EST)October 26,28,30;November 1,3,5,7...25,27,29; (1997 9:00 AM EST)October 26,28,30;November 1,3,5,7...25,27,29;
Dec 1,3,... Dec 1,3,...
Every 10 days, 5 occurrences: Every 10 days, 5 occurrences:
DTSTART;TZID=America-New York:19970902T090000 DTSTART;TZID=US-Eastern:19970902T090000
RRULE:FREQ=DAILY;INTERVAL=10;COUNT=5 RRULE:FREQ=DAILY;INTERVAL=10;COUNT=5
==> (1997 9:00 AM EDT)September 2,12,22;October 2,12 ==> (1997 9:00 AM EDT)September 2,12,22;October 2,12
Everyday in January, for 3 years: Everyday in January, for 3 years:
DTSTART;TZID=America-New York:19980101T090000 DTSTART;TZID=US-Eastern:19980101T090000
RRULE:FREQ=YEARLY;UNTIL=20000131T090000Z; RRULE:FREQ=YEARLY;UNTIL=20000131T090000Z;
BYMONTH=1;BYDAY=SU,MO,TU,WE,TH,FR,SA BYMONTH=1;BYDAY=SU,MO,TU,WE,TH,FR,SA
or or
RRULE:FREQ=DAILY;UNTIL=20000131T090000Z;BYMONTH=1 RRULE:FREQ=DAILY;UNTIL=20000131T090000Z;BYMONTH=1
==> (1998 9:00 AM EDT)January 1-31 ==> (1998 9:00 AM EDT)January 1-31
(1999 9:00 AM EDT)January 1-31 (1999 9:00 AM EDT)January 1-31
(2000 9:00 AM EDT)January 1-31 (2000 9:00 AM EDT)January 1-31
Weekly for 10 occurrences Weekly for 10 occurrences
DTSTART;TZID=America-New York:19970902T090000 DTSTART;TZID=US-Eastern:19970902T090000
RRULE:FREQ=WEEKLY;COUNT=10 RRULE:FREQ=WEEKLY;COUNT=10
==> (1997 9:00 AM EDT)September 2,9,16,23,30;October 7,14,21 ==> (1997 9:00 AM EDT)September 2,9,16,23,30;October 7,14,21
(1997 9:00 AM EST)October 28;November 4 (1997 9:00 AM EST)October 28;November 4
Weekly until December 24, 1997 Weekly until December 24, 1997
DTSTART;TZID=America-N