Calendar component
Click on the red underlined text to get to the source
... Calendar User" within the scheduling protocol defined by [ITIP].
Calendar components defined by this memo are referred to with
capitalized, quoted-strings of text. All calendar components start ...
... Calendar components defined by this memo are referred to with
capitalized, quoted-strings of text. All calendar components start
with the letter "V". For example, "VEVENT ...
... with the letter "V". For example, "VEVENT" refers to the event
calendar component, "VTODO" refers to the to-do calendar component
...
... calendar component, "VTODO" refers to the to-do calendar component
and "VJOURNAL" refers to the daily journal calendar component ...
... calendar component
and "VJOURNAL" refers to the daily journal calendar component.
Scheduling methods defined by [ITIP ...
... capitalized, quoted-strings of text. For example, "REQUEST" refers to
the method for requesting a scheduling calendar component be created
or modified, "REPLY" refers to the method ...
... method a recipient of a request
uses to update their status with the "Organizer" of the calendar
component.
...
...
The "component" parameter conveys the type of iCalendar calendar
component within the body part. If the iCalendar object contains more
than one calendar component ...
... calendar
component within the body part. If the iCalendar object contains more
than one calendar component type, then multiple component parameters
MUST be specified.
...
... VTODO",
"VJOURNAL" calendar component and redistribute the updates to the
"Attendees". An iCalendar object that maliciously changes or cancels
...
... VTODO" or "VJOURNAL" or "VFREEBUSY" calendar
component might be constructed by someone other than the "Organizer"
and sent to the "Attendees". In addition in this memo, other than the
"Organizer", an "Attendee" of a "VEVENT ...
... VTODO", "VJOURNAL"
calendar component is the only other person authorized to update any
parameter associated with their "ATTENDEE ...
... contains a "VEVENT" and "VTODO" calendar component with "VALARM"
calendar components. The "VALARM" calendar component ...
... VTODO" calendar component with "VALARM"
calendar components. The "VALARM" calendar component can be of type
PROCEDURE and can have an attachment containing some sort of
...
... calendar component with "VALARM"
calendar components. The "VALARM" calendar component can be of type
PROCEDURE and can have an attachment containing some sort of
executable program. Implementations that incorporate these types of
...
... VTODO" or "VJOURNAL". The values MUST
match one of the values allowed for the given calendar component. If
not specified on a property that allows this parameter, the default
value is NEEDS-ACTION.
...
... alarm trigger with
respect to the start or end of the calendar component.
Format Definition: The property parameter is defined by the following
...
... alarm will trigger relative to the start or end
of the calendar component. The parameter value START will set the
...
... alarm to trigger off the start of the calendar component; the
parameter value END will set the alarm ...
... parameter value END will set the alarm to trigger off the end of the
calendar component. If the parameter is not specified on an allowable
property, then the default is START.
...
...
Purpose: To specify the type of hierarchical relationship associated
with the calendar component specified by the property.
Format Definition: The property parameter is defined by the following
...
... references another related calendar. The parameter specifies the
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
component; CHILD to indicate that the referenced calendar component
...
... parameter value can be PARENT, to indicate that
the referenced calendar component is a superior of calendar
component; CHILD to indicate that the referenced calendar component
is a subordinate of the calendar component ...
... the referenced calendar component is a superior of calendar
component; CHILD to indicate that the referenced calendar component
is a subordinate of the calendar component; SIBLING to indicate that
...
... calendar
component; CHILD to indicate that the referenced calendar component
is a subordinate of the calendar component; SIBLING to indicate that
the referenced calendar component is a peer of the calendar
component ...
... is a subordinate of the calendar component; SIBLING to indicate that
the referenced calendar component is a peer of the calendar
component. If this parameter is not specified on an allowable
property, the default relationship type is PARENT.
...
... calendar component; SIBLING to indicate that
the referenced calendar component is a peer of the calendar
component. If this parameter is not specified on an allowable
property, the default relationship type is PARENT.
...
... calendar user specified by the property in the group
schedule calendar component. If not specified on a property that
allows this parameter, the default value is REQ-PARTICIPANT.
...
... property parameter specifies a text value which uniquely identifies
the "VTIMEZONE" calendar component to be used when evaluating the
time portion of the property. The value of the TZID property
...
... TZID property for the
matching time zone definition. An individual "VTIMEZONE" calendar
component MUST be specified for each unique "TZID" parameter value
...
... property parameter is to be interpreted as a local time value,
regardless of the existence of "VTIMEZONE" calendar components in the
iCalendar object.
...
... parameter is to be interpreted as floating time, regardless of the
existence of "VTIMEZONE" calendar components in the iCalendar object.
...
... parameter is to be interpreted as a local time value, regardless of
the existence of "VTIMEZONE" calendar components in the iCalendar
object.
...
... A property is the definition of an individual attribute describing a
calendar or a calendar component. A property takes the form defined
by the "contentline" notation defined in section 4.1.1.
...
... Calendar Components ...
... iCalendar object consists of a sequence of calendar
properties and one or more calendar components. The calendar
properties are attributes that apply to the calendar ...
... properties are attributes that apply to the calendar as a whole. The
calendar components are collections of properties that express a
particular calendar semantic ...
... particular calendar semantic. For example, the calendar component can
specify an event, a to-do, a journal entry, time zone information, or
free/busy time information ...
... VERSION" calendar
properties. In addition, it MUST include at least one calendar
component. Special forms of iCalendar objects are possible to publish
just busy time (i.e., only a "VFREEBUSY ...
... iCalendar objects are possible to publish
just busy time (i.e., only a "VFREEBUSY" calendar component) or time
zone (i.e., only a "VTIMEZONE" calendar component ...
... calendar component) or time
zone (i.e., only a "VTIMEZONE" calendar component) information. In
addition, a complex iCalendar object is possible that is used to
...
... calendar (e.g.,
composite of many different calendar components). More commonly, an
iCalendar object will consist of just a single "VEVENT ...
...
Description: A "VEVENT" calendar component is a grouping of component
properties, and possibly including "VALARM" calendar components, that
...
... VEVENT" calendar component is a grouping of component
properties, and possibly including "VALARM" calendar components, that
represents a scheduled amount of time on a calendar. For example, it
...
...
The "VEVENT" is also the calendar component used to specify an
anniversary or daily reminder within a calendar. These events have a
...
... instance in the recurrence set. The "DTEND" property for a "VEVENT"
calendar component specifies the non-inclusive end of the event. For
cases where a "VEVENT" calendar component ...
... calendar component specifies the non-inclusive end of the event. For
cases where a "VEVENT" calendar component specifies a "DTSTART"
property with a DATE data type but no "DTEND" property, the events
...
... calendar date specified by the
"DTSTART" property. For cases where a "VEVENT" calendar component
specifies a "DTSTART" property with a DATE-TIME data type ...
...
The "VEVENT" calendar component cannot be nested within another
calendar component. However, "VEVENT ...
... VEVENT" calendar component cannot be nested within another
calendar component. However, "VEVENT" calendar components can be
...
... calendar component. However, "VEVENT" calendar components can be
related to each other or to a "VTODO" or to a "VJOURNAL ...
...
Example: The following is an example of the "VEVENT" calendar
component used to represent a meeting that will also be opaque to
searches for busy time:
...
...
The following is an example of the "VEVENT" calendar component used
to represent a reminder that will not be opaque, but rather
...
...
The following is an example of the "VEVENT" calendar component used
to represent an anniversary that will occur annually. Since it takes
up no time, it will not appear as opaque ...
...
Formal Definition: A "VTODO" calendar component is defined by the
following notation:
...
...
Description: A "VTODO" calendar component is a grouping of component
properties and possibly "VALARM" calendar components that represent
...
... VTODO" calendar component is a grouping of component
properties and possibly "VALARM" calendar components that represent
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
...
...
The "VTODO" calendar component cannot be nested within another
calendar component. However, "VTODO ...
... 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 ...
... related to each other or to a "VTODO" or to a "VJOURNAL" calendar
component with the "RELATED-TO" property.
A "VTODO ...
...
A "VTODO" calendar component without the "DTSTART" and "DUE" (or
"DURATION") properties specifies a to-do that will be associated with
each successive calendar ...
...
Formal Definition: A "VJOURNAL" calendar component is defined by the
following notation:
...
...
Description: A "VJOURNAL" calendar component is a grouping of
component properties that represent one or more descriptive text
notes associated with a particular calendar ...
... or an ordered list of accomplishments for the day. The "VJOURNAL"
calendar component can also be used to associate a document with a
calendar date.
...
...
The "VJOURNAL" calendar component does not take up time on a
calendar. Hence, it does not play a role ...
...
The "VJOURNAL" calendar component cannot be nested within another
calendar component. However, "VJOURNAL ...
... VJOURNAL" calendar component cannot be nested within another
calendar component. However, "VJOURNAL" calendar components can be
...
... calendar component. However, "VJOURNAL" calendar components can be
related to each other or to a "VEVENT" or to a "VTODO ...
... related to each other or to a "VEVENT" or to a "VTODO" calendar
component, with the "RELATED-TO" property.
Example: The following is an example of the "VJOURNAL ...
...
Description: A "VFREEBUSY" calendar component is a grouping of
component properties that represents either a request for, a reply to
a request for free or busy time information ...
...
The "VFREEBUSY" calendar component cannot be nested within another
calendar component. Multiple "VFREEBUSY ...
... 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
...
... more "FREEBUSY" properties can be specified in the "VFREEBUSY"
calendar component.
When present in a "VFREEBUSY ...
...
When present in a "VFREEBUSY" calendar component, the "DTSTART" and
"DTEND" properties SHOULD be specified prior to any "FREEBUSY"
properties. In a free time request, these properties can be used in
...
... The recurrence properties ("RRULE", "EXRULE", "RDATE", "EXDATE") are
not permitted within a "VFREEBUSY" calendar component. Any recurring
events are resolved into their individual busy time periods using the
"FREEBUSY" property.
...
...
Example: The following is an example of a "VFREEBUSY" calendar
component used to request free or busy time information:
...
...
The following is an example of a "VFREEBUSY" calendar component used
to reply to the request with busy time information:
...
...
The following is an example of a "VFREEBUSY" calendar component used
to publish busy time information.
...
...
Formal Definition: A "VTIMEZONE" calendar component is defined by the
following notation:
...
...
If present, the "VTIMEZONE" calendar component defines the set of
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.
Multiple "VTIMEZONE ...
... VTIMEZONE"
calendar component cannot be nested within other calendar components.
Multiple "VTIMEZONE" calendar components ...
... calendar components.
Multiple "VTIMEZONE" calendar components can exist in an iCalendar
object. In this situation, each "VTIMEZONE ...
...
The "VTIMEZONE" calendar component MUST include the "TZID" property
and at least one definition of a standard or daylight component. The
...
...
An individual "VTIMEZONE" calendar component MUST be specified for
each unique "TZID" parameter value ...
...
Each "VTIMEZONE" calendar component consists of a collection of one
or more sub-components that describe the rule for a particular
observance (either a Standard Time or a Daylight Saving Time
...
... The mandatory "TZID" property is a text value that uniquely
identifies the VTIMZONE calendar component within the scope of an
iCalendar object.
...
... If neither is specified, only one sub-component can be specified in
the "VTIMEZONE" calendar component and it is assumed that the single
observance specified is always in effect.
...
...
Example: The following are examples of the "VTIMEZONE" calendar
component:
This is an example showing time zone information for the Eastern
...
... alarm.
Formal Definition: A "VALARM" calendar component is defined by the
following notation:
...
... )
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
...
... an overdue to-do.
The "VALARM" calendar component MUST include the "ACTION" and
"TRIGGER" properties. The "ACTION" property further constrains the
"VALARM" calendar component ...
... calendar component MUST include the "ACTION" and
"TRIGGER" properties. The "ACTION" property further constrains the
"VALARM" calendar component in the following ways:
When the action is "AUDIO ...
... alarm is triggered.
The "VALARM" calendar component MUST only appear within either a
"VEVENT" or "VTODO ...
... "VEVENT" or "VTODO" calendar component. "VALARM" calendar components
cannot be nested. Multiple mutually independent "VALARM" calendar
components ...
... VEVENT" or "VTODO" calendar component. "VALARM" calendar components
cannot be nested. Multiple mutually independent "VALARM" calendar
components can be specified for a single "VEVENT ...
... calendar component. "VALARM" calendar components
cannot be nested. Multiple mutually independent "VALARM" calendar
components can be specified for a single "VEVENT" or "VTODO" calendar
component ...
... calendar
components can be specified for a single "VEVENT" or "VTODO" calendar
component.
The "TRIGGER" property specifies when the alarm ...
... 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
the "DTSTART" and "DURATION" properties MUST both be present. In an
...
... alarm in a "VTODO" calendar component set to trigger on the "END" of
the to-do, either the "DUE" property MUST be present, or the
"DTSTART" and "DURATION" properties MUST both be present.
...
... addresses specified by the
"ATTENDEE" properties in the "VALARM" calendar component. The
"DESCRIPTION" property of the "VALARM" calendar component MUST be
...
... ATTENDEE" properties in the "VALARM" calendar component. The
"DESCRIPTION" property of the "VALARM" calendar component MUST be
used as the body text of the message, and the "SUMMARY" property MUST
be used as the subject ...
... be used as the subject text. Any "ATTACH" properties in the "VALARM"
calendar component SHOULD be sent as attachments to the message.
In a PROCEDURE alarm ...
...
In a PROCEDURE alarm, the "ATTACH" property in the "VALARM" calendar
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
...
... security risk.
Example: The following example is for a "VALARM" calendar component
that specifies an audio alarm ...
... END:VALARM
The following example is for a "VALARM" calendar component that
specifies a display alarm that will trigger 30 minutes before the
...
... END:VALARM
The following example is for a "VALARM" calendar component that
specifies an email alarm ...
... END:VALARM
The following example is for a "VALARM" calendar component that
specifies a procedural alarm that will trigger at a precise date/time ...
... Calendar Properties are attributes that apply to the iCalendar
object, as a whole. These properties do not appear within a calendar
component. They SHOULD be specified after the "BEGIN:VCALENDAR"
property and prior to any calendar component ...
... calendar
component. They SHOULD be specified after the "BEGIN:VCALENDAR"
property and prior to any calendar component.
...
...
The following properties can appear within calendar components, as
specified by each component property definition.
...
...
The following properties specify descriptive information about
calendar components.
...
...
Purpose: The property provides the capability to associate a document
object with a calendar component.
Value Type: The default value ...
... VTODO",
"VJOURNAL" or "VALARM" calendar components.
Description: The property can be specified within "VEVENT ...
... VTODO",
"VJOURNAL", or "VALARM" calendar components. This property can be
specified multiple times within an iCalendar object.
...
... Property Name: CATEGORIES
Purpose: This property defines the categories for a calendar
component.
Value Type: TEXT
...
... VTODO"
or "VJOURNAL" calendar components.
Description: This property is used to specify categories or subtypes
...
...
Description: This property is used to specify categories or subtypes
of the calendar component. The categories are useful in searching for
a calendar component of a particular type and category. Within the
...
... of the calendar component. The categories are useful in searching for
a calendar component of a particular type and category. Within the
"VEVENT", "VTODO ...
... VEVENT", "VTODO" or "VJOURNAL" calendar components, more than one
category can be specified as a list of categories separated by the
COMMA character (US-ASCII ...
...
Purpose: This property defines the access classification for a
calendar component.
Value Type: TEXT
...
... "VTODO" or "VJOURNAL" calendar components.
Description: An access classification is only one component of the
...
... method for capturing the intention of
the calendar owner for the access to the calendar component.
Format Definition: The property is defined by the following notation:
...
... VJOURNAL", "VTIMEZONE" or "VFREEBUSY" calendar components.
Description: The property can be specified multiple times.
...
...
Purpose: This property provides a more complete description of the
calendar component, than that provided by the "SUMMARY" property.
Value Type: TEXT
...
... VTODO",
"VJOURNAL" or "VALARM" calendar components. The property can be
specified multiple times only within a "VJOURNAL" calendar component ...
... calendar components. The property can be
specified multiple times only within a "VJOURNAL" calendar component.
Description: This property is used in the "VEVENT ...
...
This property is used in the "VJOURNAL" calendar component to capture
one more textual journal entries.
...
...
Purpose: This property specifies information related to the global
position for the activity specified by a calendar component.
Value Type: FLOAT. The value MUST be two SEMICOLON separated FLOAT
...
... VEVENT" or "VTODO"
calendar components.
Description: The property value specifies latitude and longitude, in
...
...
Purpose: The property defines the intended venue for the activity
defined by a calendar component.
Value Type: TEXT
...
... VEVENT" or "VTODO"
calendar component.
Description: Specific venues such as conference or meeting rooms may
...
...
Conformance: This property can be specified in a "VTODO" calendar
component.
Description: The property value is a positive integer ...
...
Purpose: The property defines the relative priority for a calendar
component.
Value Type: INTEGER ...
...
Within a "VEVENT" calendar component, this property specifies a
priority for the event. This property may be useful when more than
...
...
Within a "VTODO" calendar component, this property specified a
priority for the to-do. This property is useful in prioritizing
...
... VEVENT" or "VTODO"
calendar component.
Description: The property value is an arbitrary text. More than one
...
...
Purpose: This property defines the overall status or confirmation for
the calendar component.
Value Type: TEXT
...
...
Description: In a group scheduled calendar component, the property is
used by the "Organizer" to provide a confirmation of the event to the
"Attendees". For example in a "VEVENT ...
... used by the "Organizer" to provide a confirmation of the event to the
"Attendees". For example in a "VEVENT" calendar component, the
"Organizer" can indicate that a meeting is tentative, confirmed or
cancelled. In a "VTODO ...
... "Organizer" can indicate that a meeting is tentative, confirmed or
cancelled. In a "VTODO" calendar component, the "Organizer" can
indicate that an action item needs action, is completed, is in
process or being worked on, or has been cancelled. In a "VJOURNAL ...
... process or being worked on, or has been cancelled. In a "VJOURNAL"
calendar component, the "Organizer" can indicate that a journal entry
is draft, final or has been cancelled or removed.
...
... Example: The following is an example of this property for a "VEVENT"
calendar component:
STATUS:TENTATIVE
...
...
The following is an example of this property for a "VTODO" calendar
component:
STATUS:NEEDS-ACTION
...
... The following is an example of this property for a "VJOURNAL"
calendar component:
STATUS:DRAFT
...
... Purpose: This property defines a short summary or subject for the
calendar component.
Value Type: TEXT
...
... VTODO",
"VJOURNAL" or "VALARM" calendar components.
Description: This property is used in the "VEVENT ...
... VTODO" and
"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
the subject ...
...
The following properties specify date and time related information in
calendar components.
...
...
Conformance: The property can be specified in a "VTODO" calendar
component.
Description: The date and time MUST be in a UTC ...
... Property Name: DTEND
Purpose: This property specifies the date and time that a calendar
component ends.
Value Type: The default value ...
...
Description: Within the "VEVENT" calendar component, this property
defines the date and time by which the event ends. The value MUST be
later in time than the value of the "DTSTART" property.
...
...
Within the "VFREEBUSY" calendar component, this property defines the
end date and time for the free or busy time information. The time
...
...
Conformance: The property can be specified once in a "VTODO" calendar
component.
Description: The value MUST be a date/time ...
... Property Name: DTSTART
Purpose: This property specifies when the calendar component begins.
Value Type: The default value ...
...
Description: Within the "VEVENT" calendar component, this property
defines the start date and time for the event. The property is
...
... start date and time for the event. The property is
REQUIRED in "VEVENT" calendar components. Events can have a start
date/time ...
...
Within the "VFREEBUSY" calendar component, this property defines the
start date and time for the free or busy time information ...
...
Within the "VTIMEZONE" calendar component, this property defines the
effective start date and time for a time zone specification. This
...
... property is REQUIRED within each STANDARD and DAYLIGHT part included
in "VTIMEZONE" calendar components and MUST be specified as a local
DATE-TIME without the "TZID ...
...
Description: In a "VEVENT" calendar component the property may be
used to specify a duration of the event, instead of an explicit end
date/time ...
... 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
date/time ...
... date/time. In a "VFREEBUSY" calendar component the property may be
used to specify the interval of free time being requested. In a
"VALARM" calendar component ...
... calendar component the property may be
used to specify the interval of free time being requested. In a
"VALARM" calendar component the property may be used to specify the
delay period prior to repeating an alarm.
...
...
Conformance: The property can be specified in a "VFREEBUSY" calendar
component.
Property Parameter: "FBTYPE" and non-standard parameters can be
...
...
"FREEBUSY" properties within the "VFREEBUSY" calendar component
SHOULD be sorted in ascending order, based on start time and then end
...
... Conformance: This property can be specified once in a "VEVENT"
calendar component.
Description: Time Transparency is the characteristic of an event that
...
...
The following properties specify time zone information in calendar
components.
...
... Purpose: This property specifies the text value that uniquely
identifies the "VTIMEZONE" calendar component.
Value Type: TEXT
...
... Conformance: This property MUST be specified in a "VTIMEZONE"
calendar component.
Description: This is the label by which a time zone calendar
component ...
... calendar component.
Description: This is the label by which a time zone calendar
component is referenced by any iCalendar properties whose data type
...
...
Conformance: This property can be specified in a "VTIMEZONE" calendar
component.
Description: This property may be specified in multiple languages ...
... Conformance: This property MUST be specified in a "VTIMEZONE"
calendar component.
Description: This property specifies the offset which is in use prior
...
... which the transition to a given observance takes place. This property
MUST only be specified in a "VTIMEZONE" calendar component. A
"VTIMEZONE" calendar component ...
... calendar component. A
"VTIMEZONE" calendar component MUST include this property. The
property value is a signed numeric indicating the number of hours and
possibly minutes from UTC ...
... Conformance: This property MUST be specified in a "VTIMEZONE"
calendar component.
Description: This property specifies the offset which is in use in
...
...
Conformance: This property can be specified in a "VTIMEZONE" calendar
component.
Description: The TZURL provides a means for a VTIMEZONE ...
...
The following properties specify relationship information in calendar
components.
...
... ATTENDEE
Purpose: The property defines an "Attendee" within a calendar
component.
Value Type: CAL-ADDRESS ...
... calendar.
Description: The property MUST only be specified within calendar
components to specify participants, non-participants and the chair of
a group ...
... entity. The property is specified within
an "EMAIL" category of the "VALARM" calendar component to specify an
email address that is to receive the email ...
... ROLE, for the intended role
that the attendee will have in the calendar component; PARTSTAT, for
the status of the attendee's participation; RSVP ...
... VEVENT", "VTODO" or "VJOURNAL" calendar
component. They MUST not be specified in an "ATTENDEE" property in a
"VFREEBUSY ...
... ATTENDEE" property in a
"VFREEBUSY" or "VALARM" calendar component. If the LANGUAGE property
parameter is specified, the identified language ...
... Multiple attendees can be specified by including multiple "ATTENDEE"
properties within the calendar component.
Format Definition: The property is defined by the following notation:
...
... Purpose: The property is used to represent contact information or
alternately a reference to contact information associated with the
calendar component.
Value Type: TEXT
...
... "VJOURNAL" or "VFREEBUSY" calendar component.
Description: The property value consists of textual contact
...
... Property Name: ORGANIZER
Purpose: The property defines the organizer for a calendar component.
Value Type: CAL-ADDRESS ...
... VTODO",
"VJOURNAL calendar components to specify the organizer of a group
scheduled calendar ...
... entity. The property is specified within the
"VFREEBUSY" calendar component to specify the calendar user
requesting the free or busy time. When publishing a "VFREEBUSY ...
... requesting the free or busy time. When publishing a "VFREEBUSY"
calendar component, the property is used to specify the calendar that
the published busy time came from.
...
... VEVENT", "VTODO" or "VJOURNAL" calendar component. The property
value is the effective value of the "DTSTART" property of the
recurrence instance.
...
... Conformance: This property can be specified in an iCalendar object
containing a recurring calendar component.
Description: The full range ...
...
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"
property allows the reference to an individual instance within the
recurrence set.
...
... "SEQUENCE" property values, the "RECURRENCE-ID" value for a
recurrence instance is fixed. When the definition of the recurrence
set for a calendar component changes, and hence the "SEQUENCE"
property value changes, the "RECURRENCE-ID" for a given recurrence
instance might also change.The "RANGE ...
...
Purpose: The property is used to represent a relationship or
reference between one calendar component and another.
Value Type: TEXT
...
... VEVENT", "VTODO" or "VJOURNAL" calendar components.
Description: The property value consists of the persistent, globally
unique identifier ...
...
Description: The property value consists of the persistent, globally
unique identifier of another calendar component. This value would be
represented in a calendar component by the "UID ...
... globally
unique identifier of another calendar component. This value would be
represented in a calendar component by the "UID" property.
...
... UID" property.
By default, the property value points to another calendar component
that has a PARENT relationship to the referencing object. The
"RELTYPE" property parameter is used to either explicitly state ...
... "RELTYPE" property parameter is used to either explicitly state the
default PARENT relationship type to the referenced calendar component
or to override the default PARENT relationship type and specify
either a CHILD or SIBLING relationship. The PARENT relationship
...
... or to override the default PARENT relationship type and specify
either a CHILD or SIBLING relationship. The PARENT relationship
indicates that the calendar component is a subordinate of the
referenced calendar component. The CHILD relationship indicates that
...
... indicates that the calendar component is a subordinate of the
referenced calendar component. The CHILD relationship indicates that
the calendar component is a superior of the referenced calendar
component ...
... referenced calendar component. The CHILD relationship indicates that
the calendar component is a superior of the referenced calendar
component. The SIBLING relationship indicates that the calendar
component is a peer of the referenced calendar component ...
... calendar component. The CHILD relationship indicates that
the calendar component is a superior of the referenced calendar
component. The SIBLING relationship indicates that the calendar
component is a peer of the referenced calendar component.
...
... the calendar component is a superior of the referenced calendar
component. The SIBLING relationship indicates that the calendar
component is a peer of the referenced calendar component.
...
... calendar component is a superior of the referenced calendar
component. The SIBLING relationship indicates that the calendar
component is a peer of the referenced calendar component.
Changes to a calendar component ...
... calendar component.
Changes to a calendar component referenced by this property can have
an implicit impact on the related calendar component. For example, if
...
... Changes to a calendar component referenced by this property can have
an implicit impact on the related calendar component. For example, if
a group event changes its start ...
... related, dependent events will need to have their start and end dates
changed in a corresponding way. Similarly, if a PARENT calendar
component is canceled or deleted, then there is an implied impact to
the related CHILD calendar components ...
... calendar
component is canceled or deleted, then there is an implied impact to
the related CHILD calendar components. This property is intended only
to provide information on the relationship of calendar components. It
...
... the related CHILD calendar components. This property is intended only
to provide information on the relationship of calendar components. It
is up to the target calendar ...
... VTODO", "VJOURNAL" or "VFREEBUSY" calendar components.
Description: This property may be used in a calendar component ...
... calendar components.
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
memo does not attempt to standardize the form of the URI, nor the
...
...
Purpose: This property defines the persistent, globally unique
identifier for the calendar component.
Value Type: TEXT
...
...
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
allows the reference to an individual instance within the recurrence
set.
...
... VEVENT", "VTODO" and "VJOURNAL" calendar
components to assure interoperability with other group scheduling
...
...
The following properties specify recurrence information in calendar
components.
...
... Purpose: This property defines the list of date/time exceptions for a
recurring calendar component.
Value Type: The default value ...
... Conformance: This property can be specified in an iCalendar object
that includes a recurring calendar component.
Description: The exception dates, if specified, are used in computing
...
... Description: The exception dates, if specified, are used in computing
the recurrence set. The recurrence set is the complete set of
recurrence instances for a calendar component. The recurrence set is
generated by considering the initial "DTSTART" property along with
the "RRULE", "RDATE", "EXDATE" and "EXRULE" properties contained
...
... VTODO" or
"VJOURNAL" calendar components.
Description: The exception rule, if specified, is used in computing
...
... Description: The exception rule, if specified, is used in computing
the recurrence set. The recurrence set is the complete set of
recurrence instances for a calendar component. The recurrence set is
generated by considering the initial "DTSTART" property along with
the "RRULE", "RDATE", "EXDATE" and "EXRULE" properties contained
...
... "VJOURNAL" or "VTIMEZONE" calendar components.
Description: This property can appear along with the "RRULE" property
...
... The recurrence dates, if specified, are used in computing the
recurrence set. The recurrence set is the complete set of recurrence
instances for a calendar component. The recurrence set is generated
by considering the initial "DTSTART" property along with the "RRULE",
"RDATE", "EXDATE" and "EXRULE" properties contained within the
...
... VEVENT", "VTODO" and "VJOURNAL" calendar components. It
can also be specified once in each STANDARD or DAYLIGHT sub-component
of the "VTIMEZONE ...
... can also be specified once in each STANDARD or DAYLIGHT sub-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
recurrence instances for a calendar component. The recurrence set is
generated by considering the initial "DTSTART" property along with
the "RRULE", "RDATE", "EXDATE" and "EXRULE" properties contained
...
... the "DTSTART" and "DTEND" properties MUST be specified in local time
and the appropriate set of "VTIMEZONE" calendar components MUST be
included. For detail on the usage of the "VTIMEZONE" calendar
component ...
... calendar components MUST be
included. For detail on the usage of the "VTIMEZONE" calendar
component, see the "VTIMEZONE" calendar component definition.
...
... VTIMEZONE" calendar
component, see the "VTIMEZONE" calendar component definition.
Any duration associated with the iCalendar ...
...
The following properties specify alarm information in calendar
components.
...
...
Conformance: This property MUST be specified once in a "VALARM"
calendar component.
Description: Each "VALARM" calendar component ...
... calendar component.
Description: Each "VALARM" calendar component has a particular type
of action associated with it. This property specifies the type of
action
...
...
Example: The following are examples of this property in a "VALARM"
calendar component:
ACTION:AUDIO ...
... specified on this property.
Conformance: This property can be specified in a "VALARM" calendar
component.
Description: If the alarm ...
... parameter MUST only be specified when the value type is DURATION.
Conformance: This property MUST be specified in the "VALARM" calendar
component.
Description: Within the "VALARM" calendar component ...
... calendar
component.
Description: Within the "VALARM" calendar component, this property
defines when the alarm will trigger. The default value ...
... MUST be present in the associated "VEVENT" or "VTODO" calendar
component. If an alarm is specified for an event with the trigger set
relative to the END, then the "DTEND" property or the "DSTART" and
...
... "DURATION' properties MUST be present in the associated "VEVENT"
calendar component. If the alarm is specified for a to-do with a
trigger set relative to the END, then either the "DUE" property or
...
... the "DSTART" and "DURATION' properties MUST be present in the
associated "VTODO" calendar component.
Alarms specified in an event or to-do which is defined in terms of a
...
... The following properties specify change management information in
calendar components.
...
... "VJOURNAL" or "VFREEBUSY" calendar components.
Description: The value MUST be specified in the UTC time ...
...
Purpose: The property specifies the date and time that the
information associated with the calendar component was last revised
in the calendar store.
...
... "VJOURNAL" or "VTIMEZONE" calendar components.
Description: The property value MUST be specified in the UTC time ...
... Purpose: This property defines the revision sequence number of the
calendar component within a sequence of revisions.
Value Type: integer ...
... calendar component.
Description: When a calendar component is created, its sequence
number is zero (US-ASCII ...
... US-ASCII decimal 48). It is monotonically incremented
by the "Organizer's" CUA each time the "Organizer" makes a
significant revision to the calendar component. When the "Organizer"
makes changes to one of the following properties, the sequence number
...
... MUST increment the sequence number when ever it makes changes to
properties in the calendar component that the "Organizer" deems will
jeopardize the validity of the participation status of the
...
... iCalendar object that it
sends to an "Attendee" to specify the current version of the calendar
component.
The "Attendee" includes this property in an iCalendar ...
... iCalendar object that it
sends to the "Organizer" to specify the version of the calendar
component that the "Attendee" is referring to.
A change to the sequence number ...
... seqparam = *(";" xparam)
Example: The following is an example of this property for a calendar
component that was just created by the "Organizer".
...
... SEQUENCE:0
The following is an example of this property for a calendar component
that has been revised two different times by the "Organizer".
...
...
The following properties specify information about a number of
miscellaneous features of calendar components.
...
... can be specified on this property.
Conformance: This property can be specified in any calendar
component.
Description: The MIME ...
... "VJOURNAL" or "VFREEBUSY" calendar component.
Description: This property is used to return status code ...
... VJOURNAL" and
"VFREEBUSY" calendar components, and "DTSTART" and "DUE", for
"VTODO" calendar components ...
... calendar components, and "DTSTART" and "DUE", for
"VTODO" calendar components, have the same value data type (e.g.,
DATE-TIME ...
... 5. When a calendar user receives multiple requests for the same
calendar component (e.g., REQUEST for a "VEVENT" calendar
component) as a result of being on multiple mailing lists ...
... calendar component (e.g., REQUEST for a "VEVENT" calendar
component) as a result of being on multiple mailing lists
specified by "ATTENDEE ...
... property needs to be specified.
Conformance: The calendar components that the property can appear in
needs to be specified.
...