Icalendar rfc pdf

A property specifying this parameter MUST also include a value that reflects the default representation of the text value. The parameter specifies the common name to be associated with the calendar user specified by the property. The parameter value is text. The parameter value can be used for display text to be associated with the calendar address specified by the property.

The parameter identifies the type of calendar user specified by the property. This parameter can be specified on a property that has a value type of calendar address. This parameter specifies those calendar uses that have delegated their participation in a group scheduled event or to-do to the calendar user specified by the property.

The individual calendar address parameter values MUST each be specified in a quoted-string. This parameter specifies those calendar users whom have been delegated participation in a group scheduled event or to-do by the calendar user specified by the property. The parameter specifies a reference to the directory entry associated with the calendar user specified by the property. The parameter value is a URI.

The default encoding is "8BIT", corresponding to a property value consisting of text. The parameter specifies the content type of the referenced object. Description: The parameter specifies the free or busy time type. The value FREE indicates that the time interval is free for scheduling. The value BUSY indicates that the time interval is busy because one or more events have been scheduled for that interval. If not specified on a property that allows this parameter, the default is BUSY.

The parameter identifies the language of the text in the property or property parameter value. The value of the "language" property parameter is that defined in [ RFC ]. For transport in a MIME entity, the Content-Language header field can be used to set the default language for the entire body part. Otherwise, no default language is assumed. The parameter identifies the groups or list membership for the calendar user specified by the property. The parameter identifies the participation status for the calendar user specified by the property value.

The values MUST match one of the values allowed for the given calendar component. The parameter specifies the effective range of recurrence instances that is specified by the property. The effective range is from the recurrence identified specified by the property. If this parameter is not specified an allowed property, then the default range is the single instance specified by the recurrence identifier value of the property.

The parameter specifies whether the 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 to trigger off the end of the calendar component. The parameter specifies the hierarchical relationship type of the calendar component referenced 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 is a subordinate of the calendar component; SIBLING to indicate that the referenced calendar component is a peer of the calendar component.

The parameter specifies the participation role for the calendar user specified by the property in the group schedule calendar component. The parameter identifies the expectation of a reply from the calendar user specified by the property value.

This parameter is used by the "Organizer" to request a participation status reply from an "Attendee" of a group scheduled event or to-do. The parameter specifies the calendar user that is acting on behalf of the calendar user specified by the property. This property parameter specifies a text value which uniquely identifies the "VTIMEZONE" calendar component to be used when evaluating the time portion of the property.

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. Description: The parameter specifies the data type and format of the property value. The property values MUST be of a single value type. If the property's value is the default value type, then this parameter need not be specified. However, if the property's default value type is overridden by some other allowable value type, then this parameter MUST be specified.

The definition of each property restricts the value to be one of the value data types, or simply value types, defined in this section. For example, an inline attachment of an object code might be included in an iCalendar object. No additional content value encoding i. The format for the value type is expressed as the [ISO ] complete representation, basic format for a calendar date.

The textual format specifies a four-digit year, two-digit month, and two-digit day of the month. There are no separator characters between the year, month and day component text. Example: The following represents July 14, 4. The format is based on the [ISO ] complete representation, basic format for a calendar date and time of day.

They are used to represent the same hour, minute, and second value regardless of which time zone is currently being observed. For example, an event can be defined that indicates that an individual will be busy from AM to PM every day, no matter which time zone the person is in. In these cases, a local time can be specified. This means that two ATTENDEEs, in different time zones, receiving the same event definition as a floating time, may be participating in the event at different actual times.

In most cases, a fixed time is desired. The format is expressed as the [ISO ] basic format for the duration of time. The format can represent durations in terms of weeks, days, hours, minutes, and seconds.

Example: The valid range for "integer" is to If the sign is not specified, then the value is assumed to be positive. The start MUST be before the ; end. There are two forms of a period of time.

First, a period of time is identified by its start and its end. The start of the period MUST be before the end of the period. Second, a period of time can also be defined by a start and a positive duration of time. The value type is a structured value consisting of a list of one or more recurrence grammar parts.

The rule parts are not ordered in any particular sequence. Individual rule parts MUST only be specified once. The FREQ rule part identifies the type of recurrence rule. This rule part MUST be specified in the recurrence rule. The UNTIL rule part defines a date-time value which bounds the recurrence rule in an inclusive manner. If the value specified by UNTIL is synchronized with the specified recurrence, this date or date-time becomes the last instance of the recurrence.

Valid values are 0 to If an integer modifier is not present, it means all days of this type within the specified frequency. Valid values are 1 to 31 or to For example, represents the tenth to the last day of the month. Valid values are 1 to or to For example, -1 represents the last day of the year December 31st and represents the th to the last day of the year March 1st.

Valid values are 1 to 53 or to This corresponds to weeks according to week numbering as defined in [ISO ]. A week is defined as a seven day period, starting on the day of the week defined to be the week start see WKST.

Week number one of the calendar year is the first week which contains at least four 4 days in that calendar year. For example, 3 represents the third week of the year. Note: Assuming a Monday week start, week 53 can only occur when Thursday is January 1 or if it is a leap year and Wednesday is January 1. Valid values are 1 to The WKST rule part specifies the day on which the workweek starts. The default value is MO. If present, this indicates the nth occurrence of the specific occurrence within the set of events specified by the rule.

Information, not contained in the rule, necessary to determine the various recurrence instance start time and dates are derived from the Start Time DTSTART entry attribute. 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 frequency generally reduce or limit the number of occurrences of the recurrence generated. BYxxx rule parts for a period of time less than the frequency generally increase or expand the number of occurrences of the recurrence.

The applicability to other character sets is for future work. The value type is defined by the following notation. The "TIME" data type is used to identify values that contain a time of day.

The format is based on the [ISO ] complete representation, basic format for a time of day. The text format consists of a two-digit hour of the day i.

The seconds value of 60 MUST only to be used to account for "leap" seconds. Fractions of a second are not supported by this format. The value of "" and "" are not allowed. The time-second, if present, may not be 60; if absent, it defaults to zero.

Typically, this information will consist of a single iCalendar object. However, multiple iCalendar objects can be sequentially grouped together. A property takes the form defined by the "contentline" notation defined in section 4. Property names, parameter names and enumerated parameter values are case insensitive.

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. In addition, it MUST include at least one calendar component. Special forms of iCalendar objects are possible to publish just busy time i. In addition, a complex iCalendar object is possible that is used to capture a complete snapshot of the contents of a calendar e. For example, it can be an activity; such as a one-hour long, department meeting from AM to AM, tomorrow.

It is also used in television for booking commercials. Valid values are 1 to 53 and 1 to This corresponds to weeks according to week numbering as defined in ISO Email for.

Home Aspose. Copyright and License Notice. Basic Grammar and Conventions. Formatting Conventions. Related Memos. List and Field Separators. Multiple Values. Binary Content. Character Set. Property Parameters. Alternate Text Representation. 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 based on the [ ISO. The start of the period MUST be before the end of the period. Second, a period of time can also be defined by a start and a positive duration of time.

The rule parts are not ordered in any particular sequence. Individual rule parts MUST only be specified once. The FREQ rule part identifies the type of recurrence rule. This rule part MUST be specified in the recurrence rule. Valid values are 0 to If an integer modifier is not present, it means all days of this type within the specified frequency. Valid values are 1 to 31 or to For example, represents the tenth to the last day of the month. Valid values are 1 to or to For example, -1 represents the last day of the year December 31st and represents the th to the last day of the year March 1st.

Valid values are 1 to 53 or to This corresponds to weeks according to week numbering as defined in [ ISO. A week is defined as a seven day period, starting on the day of the week defined to be the week start see WKST. Week number one of the calendar year is the first week that contains at least four 4 days in that calendar year. For example, 3 represents the third week of the year. Note: Assuming a Monday week start, week 53 can only occur when Thursday is January 1 or if it is a leap year and Wednesday is January 1.

Valid values are 1 to The WKST rule part specifies the day on which the workweek starts. The default value is MO. If present, this indicates the nth occurrence of the specific occurrence within the set of occurrences specified by the rule. Recurrence rules may generate recurrence instances with an invalid date e. Information, not contained in the rule, necessary to determine the various recurrence instance start time and dates are derived from the Start Time "DTSTART" component attribute.

BYxxx rule parts modify the recurrence in some manner. BYxxx rule parts for a period of time that is the same or greater than the frequency generally reduce or limit the number of occurrences of the recurrence generated. BYxxx rule parts for a period of time less than the frequency generally increase or expand the number of occurrences of the recurrence.

If the computed local start time of a recurrence instance does not exist, or occurs more than once, for the specified time zone, the time of the recurrence instance is interpreted in the same manner as an explicit DATE-TIME value describing that date and time, as specified in Section 3.

The "TIME" value type is used to identify values that contain a time of day. The text format consists of a two-digit, hour of the day i. The seconds value of 60 MUST only be used to account for positive "leap" seconds. Fractions of a second are not supported by this format.

Typically, this information will consist of an iCalendar stream with a single iCalendar object. However, multiple iCalendar objects can be sequentially grouped together in an iCalendar stream. Property A property is the definition of an individual attribute describing a calendar object or a calendar component.

A property takes the form defined by the "contentline" notation defined in Section 3. Property names, parameter names, and enumerated parameter values are case-insensitive. Calendar Components The body of the 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 object as a whole.

The calendar components are collections of properties that express a particular calendar semantic. In addition, it MUST include at least one calendar component. Special forms of iCalendar objects are possible to publish just busy time i.

In addition, a complex iCalendar object that is used to capture a complete snapshot of the contents of a calendar is possible e. Applications MUST ignore x-comp and iana-comp values they don't recognize. For example, it can be an activity; such as a one-hour long, department meeting from AM to AM, tomorrow.

Generally, an event will take up time on an individual calendar. Hence, the event will appear as an opaque interval in a search for busy time.

For recurring events, it also specifies the very first instance in the recurrence set. For example, it can be Desruisseaux Standards Track [Page 56] RFC iCalendar September used to represent an item of work assigned to an individual; such as "turn in travel expense today".

On midnight May 1st, this to-do would be considered overdue. Examples of a journal entry include a daily record of a legislative body or a journal entry of individual telephone contacts for the day or an ordered list of accomplishments for the day. It is transparent to any such searches.

Aurora project plans were reviewed. There is currently no budget reserves for this project. Lisa will escalate to management. Next meeting on Tuesday. Promised to get us a demo by Friday. Henry Miller Handsoff Insurance : Car was totaled by tree. Is looking into a loaner car. The "VFREEBUSY" calendar component is intended for use in iCalendar object methods involving requests for free time, requests for busy time, requests for both free and busy, and the associated replies.

This property provides a terse representation of time periods. Many locations adjust their Standard Time forward or backward by one hour, in order to accommodate seasonal changes in number of daylight hours, often referred to as Daylight Saving Time.

Some locations adjust their time by a fraction of an hour. Standard Time is also known as Winter Time. The following table shows the changes in time zone rules in effect for New York City starting from Each line represents a description or rule for a particular observance. 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 , with historical data going back to the introduction of standard time. Desruisseaux Standards Track [Page 64] RFC iCalendar September Interoperability between two calendaring and scheduling applications, especially for recurring events, to-dos or journal entries, is dependent on the ability to capture and convey date and time information in an unambiguous format.

The specification of current time zone information is integral to this behavior. This is necessary for some classes of events, such as airline flights, that start in one time zone and end in another. Desruisseaux Standards Track [Page 65] RFC iCalendar September For a given time zone, there may be multiple unique definitions of the observances over a period of time. The collection of these sub-components is used to describe the time zone for a given period of time.

The offset to apply at any given time is found by locating the observance that has the last onset date and time before the time in question, and using the offset value from that observance. This could be used for displaying dates. The "RRULE" property defines the recurrence rule for the onset of the observance defined by this time zone sub-component.

The "RDATE" property can also be used to define the onset of the observance by giving the individual onset date and times. Note that this is only suitable for a recurring event that starts on or later than March 11, at EDT i. For example, this can be used for a recurring event that occurs every Friday, A.

Note that there is no effective end date to either of the Standard Time or Daylight Time rules. This information would be valid for a recurring event starting today and continuing indefinitely. There is a second Daylight Time rule that picks up where the other left off. For example, it may be used to define a reminder for a pending event or an overdue to-do. When the alarm is triggered, the email message is sent.

The alarm can be defined such that it triggers repeatedly. This repetition count is in addition to the initial triggering of the alarm.

Both of these properties MUST be present in order to specify a repeating alarm. If one of these two properties is absent, then the alarm will not repeat beyond the initial trigger. The intention is that the sound will be played as the alarm effect.

If an "ATTACH" property is specified that does not refer to a sound resource, or Desruisseaux Standards Track [Page 74] RFC iCalendar September if the specified sound resource cannot be rendered because its format is unsupported, or because it cannot be retrieved , then the CUA or other entity responsible for playing the sound may choose a fallback action, such as playing a built-in default sound, or playing no sound at all. Note: Implementations should carefully consider whether they accept alarm components from untrusted sources, e.

One reasonable policy is to always ignore alarm components that the calendar user has not set herself, or at least ask for confirmation in such a case. It does not repeat. The email has a subject, body, and attachment link. Attached is a pointer the document template for the agenda file. Calendar Properties The Calendar Properties are attributes that apply to the iCalendar object, as a whole.

These properties do not appear within a calendar component. Conformance: This property can be specified once in an iCalendar object. The Gregorian calendar scale is assumed if this property is not specified in the iCalendar object.

It is expected that other calendar scales will be defined in other specifications or by future versions of this memo. No methods are defined by this specification. This is the subject of other specifications, such as the iCalendar Transport- independent Interoperability Protocol iTIP defined by [ bis ]. In such cases, the iCalendar object is merely being used to transport a snapshot of Desruisseaux Standards Track [Page 77] RFC iCalendar September some calendar information; without the intention of conveying a scheduling semantic.

For example, it is not to be used to further the understanding of non- standard properties. Example: The following is an example of this property. It does not imply that English is the default language. Version Property Name: VERSION Purpose: This property specifies the identifier corresponding to the highest version number or the minimum and maximum range of the iCalendar specification that is required in order to interpret the iCalendar object.

Description: A value of "2. Component Properties The following properties can appear within calendar components, as specified by each component property definition. Descriptive Component Properties The following properties specify descriptive information about calendar components. Property Parameters: IANA, non-standard, inline encoding, and value data type property parameters can be specified on this property.

This property is used in "VALARM" calendar components to specify an audio sound resource or an email message attachment. This property can be specified as a URI pointing to a resource or as inline binary encoded content. When this property is specified as inline binary encoded content, calendar applications MAY attempt to guess the media type of the resource via inspection of its content if and only if the media type of the resource is not given by the "FMTTYPE" parameter.

The categories are useful in searching for a calendar component of a particular type and category. Desruisseaux Standards Track [Page 82] RFC iCalendar September Description: An access classification is only one component of the general security system within a calendar application.

It provides a method of capturing the scope of the access the calendar owner intends for information within an individual calendar entry. The access classification of an individual iCalendar component is useful when measured along with the other security components of a calendar system e. Hence, the semantics of the individual access classifications cannot be completely defined by this memo alone. Additionally, due to the "blind" nature of most exchange processes using this memo, these access classifications cannot serve as an enforcement statement for a system receiving an iCalendar object.

Rather, they provide a method for capturing the intention of the calendar owner for the access to the calendar component. Description: This property is used to specify a comment to the calendar user.

We can't hold this meeting without them. Phoenix design team MUST attend this meeting. Geographic Position Property Name: GEO Purpose: This property specifies information related to the global position for the activity specified by a calendar component. Description: This property value specifies latitude and longitude, in that order i. The longitude represents the location east or west of the prime meridian as a positive or negative real number, respectively.

The longitude and latitude values MAY be specified up to six decimal places, which will allow for accuracy to within one meter of geographical position.

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 Whole degrees of longitude shall be represented by a decimal number ranging from 0 through When a decimal fraction of a degree is specified, it shall be separated from the whole number of degrees by a decimal point. 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 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 th meridian shall be assigned to the Western Hemisphere. One exception to this last convention is permitted. The component for longitude may have any legal value. Description: Specific venues such as conference or meeting rooms may be explicitly specified using this property.

An alternate representation may be specified that is a URI that points to directory information with more structured specification of the location. Description: The property value is a positive integer between 0 and A value of "0" indicates the to-do has not yet been started. A value of "" indicates that the to-do has been completed. Integer values in between indicate the percent partially complete. Desruisseaux Standards Track [Page 88] RFC iCalendar September When a to-do is assigned to multiple individuals, the property value indicates the percent complete for that portion of the to-do assigned to the assignee or delegatee.

For example, if a to-do is assigned to both individuals "A" and "B". Description: This priority is specified as an integer in the range 0 to 9. A value of 0 specifies an undefined priority. A value of 1 is the highest priority. A value of 2 is the second highest priority. Subsequent numbers specify a decreasing ordinal priority.

A value of 9 is the lowest priority. A value in the range of 6 to 9 is "LOW" priority.