draft-ietf-calsch-ical-03.txt   draft-ietf-calsch-ical-04.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-03.txt> October 22, 1997 <draft-ietf-calsch-ical-04.txt> October 22, 1997
Expires Mary 1998 Expires Mary 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 MAY also distribute working working groups. Note that other groups MAY also distribute working
skipping to change at line 83 skipping to change at line 83
event request, send a cancellation notice for an event, modify or event request, send a cancellation notice for an event, modify or
replace the definition of an event, provide a counter proposal for an replace 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. journal entry calendar component.
Dawson/Stenerson 2 Expires MAY 1998 Dawson/Stenerson 2 Expires MAY 1998
Table of Contents Table of Contents
1......................................................................7 1.Introduction........................................................8
Introduction...........................................................8
2. Basic Grammar and Conventions.......................................8 2. Basic Grammar and Conventions.......................................8
2.1 Formatting Conventions...........................................9 2.1 Formatting Conventions...........................................9
2.2 Related Memos...................................................10 2.2 Related Memos...................................................10
3. TEXT/CALENDAR Registration Information.............................10 3. TEXT/CALENDAR Registration Information.............................10
4. iCalendar Object Specification.....................................12 4. iCalendar Object Specification.....................................12
4.1 Content Considerations..........................................13 4.1 Content Considerations..........................................13
4.1.1 Content Lines................................................13 4.1.1 Content Lines................................................13
4.1.2 List and Field Separators....................................14 4.1.2 List and Field Separators....................................14
4.1.3 Multiple Values..............................................15 4.1.3 Multiple Values..............................................15
4.1.4 Binary Content...............................................15 4.1.4 Binary Content...............................................15
skipping to change at line 126 skipping to change at line 125
4.6 Component Properties............................................41 4.6 Component Properties............................................41
4.6.1 Attachment...................................................41 4.6.1 Attachment...................................................41
4.6.2 Attendee.....................................................42 4.6.2 Attendee.....................................................42
4.6.3 Categories...................................................44 4.6.3 Categories...................................................44
4.6.4 Classification...............................................45 4.6.4 Classification...............................................45
4.6.5 Comment......................................................46 4.6.5 Comment......................................................46
4.6.6 Contact......................................................46 4.6.6 Contact......................................................46
4.6.7 Date/Time Completed..........................................47 4.6.7 Date/Time Completed..........................................47
4.6.8 Date/Time Created............................................47 4.6.8 Date/Time Created............................................47
4.6.9 Date/Time Due................................................47 4.6.9 Date/Time Due................................................47
4.6.10 Date/Time End...............................................48 4.6.10..................................................Date/Time End 48
4.6.11 Date/Time Stamp.............................................48 4.6.11................................................Date/Time Stamp 48
4.6.12 Date/Time Start.............................................49 4.6.12................................................Date/Time Start 49
4.6.13 Daylight....................................................49 4.6.13.......................................................Daylight 49
4.6.14 Description.................................................50 4.6.14....................................................Description 50
4.6.15 Duration....................................................50 4.6.15.......................................................Duration 50
4.6.16 Exception Date/Times........................................51 4.6.16...........................................Exception Date/Times 51
4.6.17 Exception Rule..............................................52 4.6.17.................................................Exception Rule 52
4.6.18.................................................Free/Busy Time 52
Dawson/Stenerson 3 Expires MAY 1998 Dawson/Stenerson 3 Expires MAY 1998
4.6.18 Free/Busy Time..............................................52 4.6.19............................................Geographic Position 54
4.6.19 Geographic Position.........................................54 4.6.20..................................................Last Modified 54
4.6.20 Last Modified...............................................54 4.6.21.......................................................Location 54
4.6.21 Location....................................................54 4.6.22...............................................Percent Complete 55
4.6.22 Percent Complete............................................55 4.6.23.......................................................Priority 56
4.6.23 Priority....................................................56 4.6.24..........................................Recurrence Date/Times 56
4.6.24 Recurrence Date/Times.......................................56 4.6.25..................................................Recurrence ID 57
4.6.25 Recurrence ID...............................................57 4.6.26................................................Recurrence Rule 58
4.6.26 Recurrence Rule.............................................58 4.6.27.....................................................Related To 65
4.6.27 Related To..................................................65 4.6.28...................................................Repeat Count 66
4.6.28 Repeat Count................................................66 4.6.29.................................................Request Status 66
4.6.29 Request Status..............................................66 4.6.30......................................................Resources 68
4.6.30 Resources...................................................68 4.6.31................................................Sequence Number 68
4.6.31 Sequence Number.............................................68 4.6.32.........................................................Status 69
4.6.32 Status......................................................69 4.6.33........................................................Summary 70
4.6.33 Summary.....................................................70 4.6.34..............................................Time Transparency 70
4.6.34 Time Transparency...........................................70 4.6.35.................................................Time Zone Name 71
4.6.35 Time Zone Name..............................................71 4.6.36...............................................Time Zone Offset 71
4.6.36 Time Zone Offset............................................71 4.6.37.......................................Uniform Resource Locator 71
4.6.37 Uniform Resource Locator....................................71 4.6.38..............................................Unique Identifier 72
4.6.38 Unique Identifier...........................................72 4.6.39........................................Non-standard Properties 73
4.6.39 Non-standard Properties.....................................73
5. Recommended Practices..............................................73 5. Recommended Practices..............................................73
6. Registration of Content Type Elements..............................74 6. Registration of Content Type Elements..............................74
6.1 Registration of New and Modified iCalendar object Methods.......74 6.1 Registration of New and Modified iCalendar object Methods.......74
6.2 Registration of New Properties..................................74 6.2 Registration of New Properties..................................74
6.2.1 Define the property..........................................74 6.2.1 Define the property..........................................74
6.2.2 Post the Property definition.................................75 6.2.2 Post the Property definition.................................75
6.2.3 Allow a comment period.......................................75 6.2.3 Allow a comment period.......................................75
6.2.4 Submit the property for approval.............................75 6.2.4 Submit the property for approval.............................75
6.3 Property Change Control.........................................76 6.3 Property Change Control.........................................76
7. File extension.....................................................76 7. File extension.....................................................76
8. Macintosh File Type Code...........................................76 8. Macintosh File Type Code...........................................76
9. References.........................................................76 9. References.........................................................76
10. Acknowledgments...................................................78 10. Acknowledgments..................................................78
11. Copyright.........................................................78 11. Copyright........................................................78
12. Author's Address..................................................78 12. Author's Address.................................................78
13. iCalendar object Examples.........................................79 13. iCalendar object Examples........................................79
14. Full Copyright Statement..........................................82 14. Full Copyright Statement.........................................82
1. 1.
Dawson/Stenerson 4 Expires MAY 1998 Dawson/Stenerson 4 Expires MAY 1998
Introduction 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
skipping to change at line 1047 skipping to change at line 1046
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
If BYxxx component values are found which are beyond the available If BYxxx component 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.
Dawson/Stenerson 20 Expires MAY 1998 Dawson/Stenerson 20 Expires MAY 1998
BYxxx components modify the recurrence in some manner. BYxxx BYxxx components modify the recurrence in some manner. BYxxx
components for a period of time which is the same or greater than the components 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 recurrence generated. For example, "FREQ=DAILY;BYMONTH=1" reduces the
the number of recurrence instances from all days (if BYMONTH tag is number of recurrence instances from all days (if BYMONTH tag is not
not present) to all days in January. BYxxx components for a period of present) to all days in January. BYxxx components for a period of
time less than the frequency generally increase or expand the number time less than the frequency generally increase or expand the number
of occurrences of the recurrence. For example, of occurrences of the recurrence. For example,
‘ ‘FREQ=YEARLY;BYMONTH=1,2’ ’ increases the number of days within the "FREQ=YEARLY;BYMONTH=1,2" increases the number of days within the
yearly recurrence set from 1 (if BYMONTH tag is not present) to 2. yearly recurrence set from 1 (if BYMONTH tag is not present) to 2.
If only one BYxxx component is specified in the recurrence rule, the If only one BYxxx component is specified in the recurrence rule, the
list of ‘ ‘n’ ’ unique values would cause ‘ ‘n’ ’ occurrences of the list of "n" unique values would cause "n" occurrences of the
recurrence within each specified frequency interval, where each recurrence within each specified frequency interval, where each
unique list value is substituted in the appropriate date position unique list value is substituted in the appropriate date position
within DTSTART for each such occurrence. within DTSTART for each such occurrence.
If multiple BYxxx components are specified, then the list of ‘ ‘n’ ’ If multiple BYxxx components are specified, then the list of "n"
unique values for each lower frequency BYxxx components is applied to unique values for each lower frequency BYxxx components is applied to
the list of ‘ ‘n’ ’ unique values for higher frequency BYxxx the list of "n" unique values for higher frequency BYxxx components.
components. This process will not always increase the set of This process will not always increase the set of occurrences. If a
occurrences. If a higher component is inconsistent with what was higher component is inconsistent with what was generated for lower
generated for lower components, it would reduce the set. The ordering components, it would reduce the set. The ordering of BYxxx components
of BYxxx components from lower frequency to higher frequency is as from lower frequency to higher frequency is as follows: BYMINUTE,
follows: BYMINUTE, BYHOUR, BYDAY, BYMONTHDAY, BYYEARDAY, BYWEEKNO, BYHOUR, BYDAY, BYMONTHDAY, BYYEARDAY, BYWEEKNO, BYMONTH, BYSETPOS.
BYMONTH, BYSETPOS.
Here is an example of evaluating multiple BYxxx components. Here is an example of evaluating multiple BYxxx components.
‘ ‘FREQ=YEARLY;INTERVAL=2;BYMONTH=1;BYDAY=SU;BYHOUR=8,9;BYMINUTE=30 "FREQ=YEARLY;INTERVAL=2;BYMONTH=1;BYDAY=SU;BYHOUR=8,9;BYMINUTE=30"
’ ’
would first apply the ‘ ‘BYMINUTE=30’ ’ To ‘ ‘BYHOUR=8,9’ ’ to arrive at would first apply the "BYMINUTE=30" To "BYHOUR=8,9" to arrive at
‘ ‘every 8:30AM and 9:30AM’ ’. This in turn would be applied to "every 8:30AM and 9:30AM". This in turn would be applied to
‘ ‘BYDAY=SU’ ’ to arrive at ‘ ‘every Sunday at 8:30AM and 9:30AM’ ’. This "BYDAY=SU" to arrive at "every Sunday at 8:30AM and 9:30AM". This
would be applied to ‘ ‘BYMONTH=1’ ’ to arrive at ‘ ‘every Sunday in would be applied to "BYMONTH=1" to arrive at "every Sunday in January
January at 8:30AM and 9:30AM’ ’. Considering the FREQUENCY and at 8:30AM and 9:30AM". Considering the FREQUENCY and INTERVAL, this
INTERVAL, this would become ‘ ‘Every Sunday in January at 8:30AM and would become "Every Sunday in January at 8:30AM and 9:30AM, every
9:30AM, every other year’ ’. If the BYMINUTE, BYDAY, BYMONTHDAY, other year". If the BYMINUTE, BYDAY, BYMONTHDAY, BYYEARDAY, BYHOUR or
BYYEARDAY, BYHOUR or BYMONTH component was missing, the appropriate BYMONTH component was missing, the appropriate mintues, hour, day or
mintues, hour, day or month would have been retrieved from DTSTART. month would have been retrieved from DTSTART.
The data type is defined by the following notation: The data type is defined by the following notation:
recur = ‘ ‘FREQ’ ’=freq ";" recur = "FREQ"=freq ";"
[("UNTIL" "=" enddate ";") / ("COUNT" "=" digits ";")] [("UNTIL" "=" enddate ";") / ("COUNT" "=" digits ";")]
["INTERVAL" "=" digits ";"] ["INTERVAL" "=" digits ";"]
["BYMINUTE" "=" byminlist ";"] ["BYMINUTE" "=" byminlist ";"]
["BYHOUR" "=" byhrlist ";"] ["BYHOUR" "=" byhrlist ";"]
["BYDAY" "=" bywdaylist ";"] ["BYDAY" "=" bywdaylist ";"]
["BYMONTHDAY" "=" bymodaylist ";"] ["BYMONTHDAY" "=" bymodaylist ";"]
["BYYEARDAY" "=" byyrdaylist ";"] ["BYYEARDAY" "=" byyrdaylist ";"]
["BYWEEKNO" "=" bywknolist ";"] ["BYWEEKNO" "=" bywknolist ";"]
["BYMONTH" "=" bymolist ";"] ["BYMONTH" "=" bymolist ";"]
Dawson/Stenerson 21 Expires MAY 1998
["BYSETPOS" "=" bysplist ";"] ["BYSETPOS" "=" bysplist ";"]
["WKST" "=" weekday ";")] ["WKST" "=" weekday ";")]
Dawson/Stenerson 21 Expires MAY 1998
*("X-" word "=" word) ";" *("X-" word "=" word) ";"
;Individual components MAY only be specified once. ;Individual components MAY only be specified once.
;Rule components need not be specified in particular any order. ;Rule components need not be specified in particular any order.
freq = "MINUTELY’ ’ / "HOURLY" / "DAILY" / "WEEKLY" / "YEARLY" freq = "MINUTELY" / "HOURLY" / "DAILY" / "WEEKLY" / "YEARLY"
enddate = date ;A UTC value enddate = date ;A UTC value
digits = 1*DIGIT digits = 1*DIGIT
DIGIT =<any ASCII decimal digit> ;0-9 DIGIT =<any ASCII decimal digit> ;0-9
byminlist = minutes / ( minutes *(‘ ‘,’ ’ minutes) ) byminlist = minutes / ( minutes *("," minutes) )
minutes = 1*2digits ;0 to 60 minutes = 1*2digits ;0 to 60
byhrlist = hour / ( hour *(‘ ‘,’ ’ hour) ) byhrlist = hour / ( hour *("," hour) )
hour = 1*2 digits ;0 to 24 hour = 1*2 digits ;0 to 24
bywdaylist = weekdaynum / ( weekdaynum *(‘ ‘,’ ’ weekdaynum) ) bywdaylist = weekdaynum / ( weekdaynum *("," weekdaynum) )
weekdaynum = [([plus] ordwk / minus ordwk)] weekday weekdaynum = [([plus] ordwk / minus ordwk)] weekday
plus = "+" plus = "+"
minus = "-" minus = "-"
ordwk = 1*2digits ;1 to 53 ordwk = 1*2digits ;1 to 53
weekday = "SU" / "MO" / "TU" / "WE" / "TH" / "FR" / "SA" weekday = "SU" / "MO" / "TU" / "WE" / "TH" / "FR" / "SA"
;Corresponding to SUNDAY, MONDAY, TUESDAY, WEDNESDAY, THURSDAY, ;Corresponding to SUNDAY, MONDAY, TUESDAY, WEDNESDAY, THURSDAY,
;FRIDAY, SATURDAY and SUNDAY days of the week. ;FRIDAY, SATURDAY and SUNDAY days of the week.
bymodaylist = monthdaynum / ( monthdaynum *(‘ ‘,’ ’ monthdaynum) ) bymodaylist = monthdaynum / ( monthdaynum *("," monthdaynum) )
monthdaynum = ([plus] ordmoday) / (minus ordmoday) monthdaynum = ([plus] ordmoday) / (minus ordmoday)
ordmoday = 1*2digits ;1 to 31 ordmoday = 1*2digits ;1 to 31
byyrdaylist = yeardaynum / ( yeardaynum *(‘ ‘,’ ’ yeardaynum) ) byyrdaylist = yeardaynum / ( yeardaynum *("," yeardaynum) )
yeardaynum = ([plus] ordyrday) / (minus ordyrday) yeardaynum = ([plus] ordyrday) / (minus ordyrday)
ordyrday = 1*3digits ;1 to 366 ordyrday = 1*3digits ;1 to 366
bywknolist = weeknum / ( weeknum *(‘ ‘,’ ’ weeknum) ) bywknolist = weeknum / ( weeknum *("," weeknum) )
weeknum = ([plus] ordwk) / (minus ordwk) weeknum = ([plus] ordwk) / (minus ordwk)
bymolist = monthnum / ( monthnum *(‘ ‘,’ ’ monthnum) ) bymolist = monthnum / ( monthnum *("," monthnum) )
Dawson/Stenerson 22 Expires MAY 1998
monthnum = 1*2digits ;1 to 12 monthnum = 1*2digits ;1 to 12
Dawson/Stenerson 22 Expires MAY 1998
bysplist = setposday / ( setposday *("," setposday) ) bysplist = setposday / ( setposday *("," setposday) )
setposday = yeardaynum setposday = yeardaynum
For example, the following is a rule which specifies 10 meetings For example, the following is a rule which specifies 10 meetings
which occur every other day: which 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.
skipping to change at line 1215 skipping to change at line 1212
negative, with a leading HYPEN-MINUS character (ASCII decimal 45), if negative, with a leading HYPEN-MINUS character (ASCII decimal 45), if
the local time is behind UTC. Local time has neither the UTC the local time is behind UTC. Local time has neither the UTC
designator nor the UTC offset suffix text. The data type is defined designator nor the UTC offset suffix text. The data type is defined
by the following notation: by the following notation:
DIGIT =<any ASCII decimal digit> ;0-9 DIGIT =<any ASCII decimal digit> ;0-9
time-hour = 2DIGIT ;00-23 time-hour = 2DIGIT ;00-23
time-minute = 2DIGIT ;00-59 time-minute = 2DIGIT ;00-59
time-second = 2DIGIT ;00-59 time-second = 2DIGIT ;00-59
Dawson/Stenerson 23 Expires MAY 1998
time-numzone = ("+" / "-") time-hour time-minute time-numzone = ("+" / "-") time-hour time-minute
time-zone = "Z" / time-numzone time-zone = "Z" / time-numzone
Dawson/Stenerson 23 Expires MAY 1998
time = time-hour time-minute time-second [time-zone] time = time-hour time-minute time-second [time-zone]
For example, the following represents 8:30 AM in New York, five hours For example, the following represents 8:30 AM in New York, five hours
behind UTC, in local time and local time with UTC offset. In behind UTC, in local time and local time with UTC offset. In
addition, 1:30 PM in UTC is illustrated: addition, 1:30 PM in UTC is illustrated:
083000 083000
083000-0500 083000-0500
133000Z 133000Z
skipping to change at line 1270 skipping to change at line 1266
For example, the following is an URL for a local file: For example, the following is an URL for a local file:
file:///my-report.txt file:///my-report.txt
4.1.9.13 UTC Offset 4.1.9.13 UTC Offset
The "UTC-OFFSET" data type is used to identify properties that The "UTC-OFFSET" data type is used to identify properties that
contain an offset from UTC to local time. The data type is defined by contain an offset from UTC to local time. The data type is defined by
the following notation: the following notation:
Dawson/Stenerson 24 Expires MAY 1998
utc-offset = time-numzone ;As defined above in time data type utc-offset = time-numzone ;As defined above in time data type
Dawson/Stenerson 24 Expires MAY 1998
For example, the following are UTC offsets are given for standard For example, the following are UTC offsets are given for standard
time for New York (five hours behind UTC) and Geneva (one hour ahead time for New York (five hours behind UTC) and Geneva (one hour ahead
of UTC): of UTC):
-0500 -0500
+0100 +0100
4.2 iCalendar object 4.2 iCalendar object
skipping to change at line 1324 skipping to change at line 1320
propname = <any properties defined in this memo> propname = <any properties defined in this memo>
/ iana-prop / x-token / iana-prop / x-token
x-token = <The two characters "X-" or "x-" followed, with no x-token = <The two characters "X-" or "x-" followed, with no
intervening white space, by any atom> intervening white space, by any atom>
iana-prop = <A publicly defined extension property, registered iana-prop = <A publicly defined extension property, registered
with IANA, as specified by this memo> with IANA, as specified by this memo>
Dawson/Stenerson 25 Expires MAY 1998
The following is an example of a property: The following is an example of a property:
Dawson/Stenerson 25 Expires MAY 1998
DTSTART:19960415T083000-05:00 DTSTART:19960415T083000-05:00
This memo places no imposed ordering of properties within an This memo places no imposed ordering of properties within an
iCalendar object. iCalendar object.
Property names, parameter names and parameter values (i.e., Property names, parameter names and parameter values (i.e.,
everything to the left of the ":" on a line) are case insensitive. everything to the left of the ":" on a line) are case insensitive.
For example, the property name "DUE" is the same as "due" and "Due". For example, the property name "DUE" is the same as "due" and "Due".
4.4 Calendar Components 4.4 Calendar Components
skipping to change at line 1378 skipping to change at line 1374
anniversary or daily reminder within a calendar. These events have a anniversary or daily reminder within a calendar. These events have a
start time but no end time. The start time MAY also be specified as a start time but no end time. The start time MAY also be specified as a
DATE value data type, instead of the default DATE-TIME. DATE value data type, instead of the default DATE-TIME.
A "VEVENT" calendar component is defined by the following notation: A "VEVENT" calendar component is defined by the following notation:
eventc = "BEGIN" ":" [ws] "VEVENT" CRLF eventc = "BEGIN" ":" [ws] "VEVENT" CRLF
eventprop *alarmc eventprop *alarmc
"END" ":" [ws] "VEVENT" CRLF "END" ":" [ws] "VEVENT" CRLF
Dawson/Stenerson 26 Expires MAY 1998
eventprop = *attach *attendee *categories [class] *comment eventprop = *attach *attendee *categories [class] *comment
*contact [created] [description] [dtend / duration] *contact [created] [description] [dtend / duration]
Dawson/Stenerson 26 Expires MAY 1998
dtstart *exdate *exrule [geo] [last-mod] [location] dtstart *exdate *exrule [geo] [last-mod] [location]
[priority] [rstatus] *related *resources *rdate [priority] [rstatus] *related *resources *rdate
*rrule dtstamp [seq] [status] summary [transp] uid *rrule dtstamp [seq] [status] summary [transp] uid
*url [recurid] *url [recurid]
The "VEVENT" calendar component can not be nested within another The "VEVENT" calendar component can not be nested within another
calendar component. The "VEVENT" calendar components MAY be related calendar component. The "VEVENT" calendar components MAY be related
to each other or to a "VTODO" or "VJOURNAL" calendar component with to each other or to a "VTODO" or "VJOURNAL" calendar component with
the "RELATED-TO" property. the "RELATED-TO" property.
skipping to change at line 2890 skipping to change at line 2887
MAY be reset to DATE or PERIOD. MAY be reset to DATE or PERIOD.
4.6.25 Recurrence ID 4.6.25 Recurrence ID
This property is identified by the property name RECURRENCE-ID. This This property is identified by the property name RECURRENCE-ID. This
property identifies a specific instance of a recurring "VEVENT", property identifies a specific instance of a recurring "VEVENT",
"VTODO" or "VJOURNAL" calendar component. The property value is the "VTODO" or "VJOURNAL" calendar component. The property value is the
effective value of the "DTSTART" property of the recurrence instance. effective value of the "DTSTART" property of the recurrence instance.
The time of day component for the value MUST be either an UTC or a The time of day component for the value MUST be either an UTC or a
local time with UTC offset time format, unless the original calendar local time with UTC offset time format, unless the original calendar
object was expressed as a ‘ ‘floating’ ’ calendar object; that is in object was expressed as a "floating" calendar object; that is in
local time with no time zone calendar component specified. If the local time with no time zone calendar component specified. If the
value of the "DTSTART" property is a DATE type value, then the value value of the "DTSTART" property is a DATE type value, then the value
MUST be the calendar date for the recurrence instance. MUST be the calendar date for the recurrence instance.
The date/time value is set to the time when the original recurrence The date/time value is set to the time when the original recurrence
instance would occur - - meaning that if the intent is to change a instance would occur - - meaning that if the intent is to change a
Friday meeting to Thursday, the date/time is still set to the Friday meeting to Thursday, the date/time is still set to the
original Friday meeting. original Friday meeting.
The "RECURRENCE-ID" property is used in conjunction with the "UID" The "RECURRENCE-ID" property is used in conjunction with the "UID"
 End of changes. 35 change blocks. 
81 lines changed or deleted 78 lines changed or added

This html diff was produced by rfcdiff 1.34. The latest version is available from http://tools.ietf.org/tools/rfcdiff/