kopia lustrzana https://github.com/collective/icalendar
updating style adding rfc5545 text and converting it to rst
Rok Garbas
rodzic
fe4e4ef803
commit
0f057a74a7
|
|
@ -160,7 +160,7 @@ div.sphinxsidebar ul {
|
|||
margin-top: 7px;
|
||||
padding: 0;
|
||||
line-height: 130%;
|
||||
font-size: 1.3em;
|
||||
font-size: 14px;
|
||||
margin-left: 1em;
|
||||
}
|
||||
|
||||
|
|
|
|||
|
|
@ -9,5 +9,6 @@ Contents
|
|||
|
||||
about
|
||||
examples
|
||||
RFC 5545 <rfc5545/index>
|
||||
changelog
|
||||
license
|
||||
|
|
|
|||
|
|
@ -0,0 +1,44 @@
|
|||
1. Introduction
|
||||
===============
|
||||
|
||||
The use of calendaring and scheduling has grown considerably in the
|
||||
last decade. Enterprise and inter-enterprise business has become
|
||||
dependent on rapid scheduling of events and actions using this
|
||||
information technology. This memo is intended to progress the level
|
||||
of interoperability possible between dissimilar calendaring and
|
||||
scheduling applications. This memo defines a MIME content type for
|
||||
exchanging electronic calendaring and scheduling information. The
|
||||
Internet Calendaring and Scheduling Core Object Specification, or
|
||||
iCalendar, allows for the capture and exchange of information
|
||||
normally stored within a calendaring and scheduling application; such
|
||||
as a Personal Information Manager (PIM) or a Group-Scheduling
|
||||
product.
|
||||
|
||||
The iCalendar format is suitable as an exchange format between
|
||||
applications or systems. The format is defined in terms of a MIME
|
||||
content type. This will enable the object to be exchanged using
|
||||
several transports, including but not limited to SMTP, HTTP, a file
|
||||
system, desktop interactive protocols such as the use of a memory-
|
||||
based clipboard or drag/drop interactions, point-to-point
|
||||
asynchronous communication, wired-network transport, or some form of
|
||||
unwired transport such as infrared.
|
||||
|
||||
The memo also provides for the definition of iCalendar object methods
|
||||
that will map this content type to a set of messages for supporting
|
||||
calendaring and scheduling operations such as requesting, replying
|
||||
to, modifying, and canceling meetings or appointments, to-dos, and
|
||||
journal entries. The iCalendar object methods can be used to define
|
||||
other calendaring and scheduling operations such as requesting for
|
||||
and replying with free/busy time data. Such a scheduling protocol is
|
||||
defined in the iCalendar Transport-independent Interoperability
|
||||
Protocol (iTIP) defined in [2446bis].
|
||||
|
||||
The memo also includes a formal grammar for the content type based on
|
||||
the Internet ABNF defined in [RFC5234]. This ABNF is required for
|
||||
the implementation of parsers and to serve as the definitive
|
||||
reference when ambiguities or questions arise in interpreting the
|
||||
descriptive prose definition of the memo. Additional restrictions
|
||||
that could not easily be expressed with the ABNF syntax are specified
|
||||
as comments in the ABNF. Comments with normative statements should
|
||||
be treated as such.
|
||||
|
||||
|
|
@ -0,0 +1,122 @@
|
|||
2. Basic Grammar and Conventions
|
||||
================================
|
||||
|
||||
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
|
||||
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
|
||||
document are to be interpreted as described in [RFC2119].
|
||||
|
||||
This memo makes use of both a descriptive prose and a more formal
|
||||
notation for defining the calendaring and scheduling format.
|
||||
|
||||
The notation used in this memo is the ABNF notation of [RFC5234].
|
||||
Readers intending on implementing the format defined in this memo
|
||||
should be familiar with this notation in order to properly interpret
|
||||
the specifications of this memo.
|
||||
|
||||
All numeric values used in this memo are given in decimal notation.
|
||||
|
||||
All names of properties, property parameters, enumerated property
|
||||
values, and property parameter values are case-insensitive. However,
|
||||
all other property values are case-sensitive, unless otherwise
|
||||
stated.
|
||||
|
||||
.. note::
|
||||
|
||||
All indented editorial notes, such as this one, are intended
|
||||
to provide the reader with additional information. The
|
||||
information is not essential to the building of an implementation
|
||||
conformant with this memo. The information is provided to
|
||||
highlight a particular feature or characteristic of the memo.
|
||||
|
||||
The format for the iCalendar object is based on the syntax of the
|
||||
text/directory media type [RFC2425]. While the iCalendar object is
|
||||
not a profile of the text/directory media type [RFC2425], it does
|
||||
reuse a number of the elements from the [RFC2425] specification.
|
||||
|
||||
|
||||
2.1. Formatting Conventions
|
||||
---------------------------
|
||||
|
||||
The elements defined in this memo are defined in prose. Many of the
|
||||
terms used to describe these have common usage that is different than
|
||||
the standards usage of this memo. In order to reference, within this
|
||||
memo, elements of the calendaring and scheduling model, core object
|
||||
(this memo), or interoperability protocol [2446bis] some formatting
|
||||
conventions have been used. Calendaring and scheduling roles are
|
||||
referred to in quoted-strings of text with the first character of
|
||||
each word in uppercase. For example, "Organizer" refers to a role of
|
||||
a "Calendar User" within the scheduling protocol defined by
|
||||
[2446bis]. 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" refers to the event
|
||||
calendar component, "VTODO" refers to the to-do calendar component,
|
||||
and "VJOURNAL" refers to the daily journal calendar component.
|
||||
Scheduling methods defined by iTIP [2446bis] are referred to with
|
||||
capitalized, quoted-strings of text. For example, "REQUEST" refers
|
||||
to the method for requesting a scheduling calendar component be
|
||||
created or modified, and "REPLY" refers to the method a recipient of
|
||||
a request uses to update their status with the "Organizer" of the
|
||||
calendar component.
|
||||
|
||||
The properties defined by this memo are referred to with capitalized,
|
||||
quoted-strings of text, followed by the word "property". For
|
||||
example, "ATTENDEE" property refers to the iCalendar property used to
|
||||
convey the calendar address of a calendar user. Property parameters
|
||||
defined by this memo are referred to with lowercase, quoted-strings
|
||||
of text, followed by the word "parameter". For example, "value"
|
||||
parameter refers to the iCalendar property parameter used to override
|
||||
the default value type for a property value. Enumerated values
|
||||
defined by this memo are referred to with capitalized text, either
|
||||
alone or followed by the word "value". For example, the "MINUTELY"
|
||||
value can be used with the "FREQ" component of the "RECUR" value type
|
||||
to specify repeating components based on an interval of one minute or
|
||||
more.
|
||||
|
||||
The following table lists the different characters from the
|
||||
[US-ASCII] character set that is referenced in this document. For
|
||||
each character, the table specifies the character name used
|
||||
throughout this document, along with its US-ASCII decimal codepoint.
|
||||
|
||||
====================== =================
|
||||
Character name Decimal codepoint
|
||||
====================== =================
|
||||
HTAB 9
|
||||
LF 10
|
||||
CR 13
|
||||
DQUOTE 22
|
||||
SPACE 32
|
||||
PLUS SIGN 43
|
||||
COMMA 44
|
||||
HYPHEN-MINUS 45
|
||||
PERIOD 46
|
||||
SOLIDUS 47
|
||||
COLON 58
|
||||
SEMICOLON 59
|
||||
LATIN CAPITAL LETTER N 78
|
||||
LATIN CAPITAL LETTER T 84
|
||||
LATIN CAPITAL LETTER X 88
|
||||
LATIN CAPITAL LETTER Z 90
|
||||
BACKSLASH 92
|
||||
LATIN SMALL LETTER N 110
|
||||
====================== =================
|
||||
|
||||
|
||||
2.2. Related Memos
|
||||
------------------
|
||||
|
||||
Implementers will need to be familiar with several other memos that,
|
||||
along with this memo, form a framework for Internet calendaring and
|
||||
scheduling standards. This memo specifies a core specification of
|
||||
objects, value types, properties, and property parameters.
|
||||
|
||||
* iTIP [2446bis] specifies an interoperability protocol for
|
||||
scheduling between different implementations;
|
||||
|
||||
* iCalendar Message-Based Interoperability Protocol (iMIP) [2447bis]
|
||||
specifies an Internet email binding for [2446bis].
|
||||
|
||||
This memo does not attempt to repeat the specification of concepts or
|
||||
definitions from these other memos. Where possible, references are
|
||||
made to the memo that provides for the specification of these
|
||||
concepts or definitions.
|
||||
|
||||
|
|
@ -0,0 +1,198 @@
|
|||
3.1 Content Lines
|
||||
=================
|
||||
|
||||
The iCalendar object is organized into individual lines of text,
|
||||
called content lines. Content lines are delimited by a line break,
|
||||
which is a CRLF sequence (CR character followed by LF character).
|
||||
|
||||
Lines of text SHOULD NOT be longer than 75 octets, excluding the line
|
||||
break. Long content lines SHOULD be split into a multiple line
|
||||
representations using a line "folding" technique. That is, a long
|
||||
line can be split between any two characters by inserting a CRLF
|
||||
immediately followed by a single linear white-space character (i.e.,
|
||||
SPACE or HTAB). Any sequence of CRLF followed immediately by a
|
||||
single linear white-space character is ignored (i.e., removed) when
|
||||
processing the content type.
|
||||
|
||||
For example, the line::
|
||||
|
||||
DESCRIPTION:This is a long description that exists on a long line.
|
||||
|
||||
Can be represented as::
|
||||
|
||||
DESCRIPTION:This is a lo
|
||||
ng description
|
||||
that exists on a long line.
|
||||
|
||||
The process of moving from this folded multiple-line representation
|
||||
to its single-line representation is called "unfolding". Unfolding
|
||||
is accomplished by removing the CRLF and the linear white-space
|
||||
character that immediately follows.
|
||||
|
||||
When parsing a content line, folded lines MUST first be unfolded
|
||||
according to the unfolding procedure described above.
|
||||
|
||||
.. note::
|
||||
|
||||
It is possible for very simple implementations to generate
|
||||
improperly folded lines in the middle of a UTF-8 multi-octet
|
||||
sequence. For this reason, implementations need to unfold lines
|
||||
in such a way to properly restore the original sequence.
|
||||
|
||||
The content information associated with an iCalendar object is
|
||||
formatted using a syntax similar to that defined by [RFC2425]. That
|
||||
is, the content information consists of CRLF-separated content lines.
|
||||
|
||||
The following notation defines the lines of content in an iCalendar
|
||||
object::
|
||||
|
||||
contentline = name *(";" param ) ":" value CRLF
|
||||
; This ABNF is just a general definition for an initial parsing
|
||||
; of the content line into its property name, parameter list,
|
||||
; and value string
|
||||
|
||||
; When parsing a content line, folded lines MUST first
|
||||
; be unfolded according to the unfolding procedure
|
||||
; described above. When generating a content line, lines
|
||||
; longer than 75 octets SHOULD be folded according to
|
||||
; the folding procedure described above.
|
||||
|
||||
name = iana-token / x-name
|
||||
|
||||
iana-token = 1*(ALPHA / DIGIT / "-")
|
||||
; iCalendar identifier registered with IANA
|
||||
|
||||
x-name = "X-" [vendorid "-"] 1*(ALPHA / DIGIT / "-")
|
||||
; Reserved for experimental use.
|
||||
|
||||
vendorid = 3*(ALPHA / DIGIT)
|
||||
; Vendor identification
|
||||
|
||||
param = param-name "=" param-value *("," param-value)
|
||||
; Each property defines the specific ABNF for the parameters
|
||||
; allowed on the property. Refer to specific properties for
|
||||
; precise parameter ABNF.
|
||||
|
||||
param-name = iana-token / x-name
|
||||
|
||||
param-value = paramtext / quoted-string
|
||||
|
||||
paramtext = *SAFE-CHAR
|
||||
|
||||
value = *VALUE-CHAR
|
||||
|
||||
quoted-string = DQUOTE *QSAFE-CHAR DQUOTE
|
||||
|
||||
QSAFE-CHAR = WSP / %x21 / %x23-7E / NON-US-ASCII
|
||||
; Any character except CONTROL and DQUOTE
|
||||
|
||||
SAFE-CHAR = WSP / %x21 / %x23-2B / %x2D-39 / %x3C-7E
|
||||
/ NON-US-ASCII
|
||||
; Any character except CONTROL, DQUOTE, ";", ":", ","
|
||||
|
||||
VALUE-CHAR = WSP / %x21-7E / NON-US-ASCII
|
||||
; Any textual character
|
||||
|
||||
NON-US-ASCII = UTF8-2 / UTF8-3 / UTF8-4
|
||||
; UTF8-2, UTF8-3, and UTF8-4 are defined in [RFC3629]
|
||||
|
||||
CONTROL = %x00-08 / %x0A-1F / %x7F
|
||||
; All the controls except HTAB
|
||||
|
||||
The property value component of a content line has a format that is
|
||||
property specific. Refer to the section describing each property for
|
||||
a definition of this format.
|
||||
|
||||
All names of properties, property parameters, enumerated property
|
||||
values and property parameter values are case-insensitive. However,
|
||||
all other property values are case-sensitive, unless otherwise
|
||||
stated.
|
||||
|
||||
|
||||
3.1.1. List and Field Separators
|
||||
--------------------------------
|
||||
|
||||
Some properties and parameters allow a list of values. Values in a
|
||||
list of values MUST be separated by a COMMA character. There is no
|
||||
significance to the order of values in a list. For those parameter
|
||||
values (such as those that specify URI values) that are specified in
|
||||
quoted-strings, the individual quoted-strings are separated by a
|
||||
COMMA character.
|
||||
|
||||
Some property values are defined in terms of multiple parts. These
|
||||
structured property values MUST have their value parts separated by a
|
||||
SEMICOLON character.
|
||||
|
||||
Some properties allow a list of parameters. Each property parameter
|
||||
in a list of property parameters MUST be separated by a SEMICOLON
|
||||
character.
|
||||
|
||||
Property parameters with values containing a COLON character, a
|
||||
SEMICOLON character or a COMMA character MUST be placed in quoted
|
||||
text.
|
||||
|
||||
For example, in the following properties, a SEMICOLON is used to
|
||||
separate property parameters from each other and a COMMA character is
|
||||
used to separate property values in a value list.
|
||||
|
||||
::
|
||||
|
||||
ATTENDEE;RSVP=TRUE;ROLE=REQ-PARTICIPANT:mailto:
|
||||
jsmith@example.com
|
||||
|
||||
RDATE;VALUE=DATE:19970304,19970504,19970704,19970904
|
||||
|
||||
|
||||
3.1.2. Multiple Values
|
||||
----------------------
|
||||
|
||||
Some properties defined in the iCalendar object can have multiple
|
||||
values. The general rule for encoding multi-valued items is to
|
||||
simply create a new content line for each value, including the
|
||||
property name. However, it should be noted that some properties
|
||||
support encoding multiple values in a single property by separating
|
||||
the values with a COMMA character. Individual property definitions
|
||||
should be consulted for determining whether a specific property
|
||||
allows multiple values and in which of these two forms. Multi-valued
|
||||
properties MUST NOT be used to specify multiple language variants of
|
||||
the same value. Calendar applications SHOULD display all values.
|
||||
|
||||
|
||||
3.1.3. Binary Content
|
||||
---------------------
|
||||
|
||||
Binary content information in an iCalendar object SHOULD be
|
||||
referenced using a URI within a property value. That is, the binary
|
||||
content information SHOULD be placed in an external MIME entity that
|
||||
can be referenced by a URI from within the iCalendar object. In
|
||||
applications where this is not feasible, binary content information
|
||||
can be included within an iCalendar object, but only after first
|
||||
encoding it into text using the "BASE64" encoding method defined in
|
||||
[RFC4648]. Inline binary content SHOULD only be used in applications
|
||||
whose special circumstances demand that an iCalendar object be
|
||||
expressed as a single entity. A property containing inline binary
|
||||
content information MUST specify the "ENCODING" property parameter.
|
||||
Binary content information placed external to the iCalendar object
|
||||
MUST be referenced by a uniform resource identifier (URI).
|
||||
|
||||
The following example specifies an "ATTACH" property that references
|
||||
an attachment external to the iCalendar object with a URI reference::
|
||||
|
||||
ATTACH:http://example.com/public/quarterly-report.doc
|
||||
|
||||
The following example specifies an "ATTACH" property with inline
|
||||
binary encoded content information::
|
||||
|
||||
ATTACH;FMTTYPE=text/plain;ENCODING=BASE64;VALUE=BINARY:VGhlIH
|
||||
F1aWNrIGJyb3duIGZveCBqdW1wcyBvdmVyIHRoZSBsYXp5IGRvZy4
|
||||
|
||||
|
||||
3.1.4. Character Set
|
||||
--------------------
|
||||
|
||||
There is not a property parameter to declare the charset used in a
|
||||
property value. The default charset for an iCalendar stream is UTF-8
|
||||
as defined in [RFC3629].
|
||||
|
||||
The "charset" Content-Type parameter MUST be used in MIME transports
|
||||
to specify the charset being used.
|
||||
|
|
@ -0,0 +1,916 @@
|
|||
3.2. Property Parameters
|
||||
========================
|
||||
|
||||
A property can have attributes with which it is associated. These
|
||||
"property parameters" contain meta-information about the property or
|
||||
the property value. Property parameters are provided to specify such
|
||||
information as the location of an alternate text representation for a
|
||||
property value, the language of a text property value, the value type
|
||||
of the property value, and other attributes.
|
||||
|
||||
Property parameter values that contain the COLON, SEMICOLON, or COMMA
|
||||
character separators MUST be specified as quoted-string text values.
|
||||
Property parameter values MUST NOT contain the DQUOTE character. The
|
||||
DQUOTE character is used as a delimiter for parameter values that
|
||||
contain restricted characters or URI text. For example::
|
||||
|
||||
DESCRIPTION;ALTREP="cid:part1.0001@example.org":The Fall'98 Wild
|
||||
Wizards Conference - - Las Vegas\, NV\, USA
|
||||
|
||||
Property parameter values that are not in quoted-strings are case-
|
||||
insensitive.
|
||||
|
||||
The general property parameters defined by this memo are defined by
|
||||
the following notation::
|
||||
|
||||
icalparameter = altrepparam ; Alternate text representation
|
||||
/ cnparam ; Common name
|
||||
/ cutypeparam ; Calendar user type
|
||||
/ delfromparam ; Delegator
|
||||
/ deltoparam ; Delegatee
|
||||
/ dirparam ; Directory entry
|
||||
/ encodingparam ; Inline encoding
|
||||
/ fmttypeparam ; Format type
|
||||
/ fbtypeparam ; Free/busy time type
|
||||
/ languageparam ; Language for text
|
||||
/ memberparam ; Group or list membership
|
||||
/ partstatparam ; Participation status
|
||||
/ rangeparam ; Recurrence identifier range
|
||||
/ trigrelparam ; Alarm trigger relationship
|
||||
/ reltypeparam ; Relationship type
|
||||
/ roleparam ; Participation role
|
||||
/ rsvpparam ; RSVP expectation
|
||||
/ sentbyparam ; Sent by
|
||||
/ tzidparam ; Reference to time zone object
|
||||
/ valuetypeparam ; Property value data type
|
||||
/ other-param
|
||||
|
||||
other-param = (iana-param / x-param)
|
||||
|
||||
iana-param = iana-token "=" param-value *("," param-value)
|
||||
; Some other IANA-registered iCalendar parameter.
|
||||
|
||||
x-param = x-name "=" param-value *("," param-value)
|
||||
; A non-standard, experimental parameter.
|
||||
|
||||
Applications MUST ignore x-param and iana-param values they don't
|
||||
recognize.
|
||||
|
||||
|
||||
3.2.1 Alternate Text Representation
|
||||
-----------------------------------
|
||||
|
||||
**Parameter Name:** ALTREP
|
||||
|
||||
**Purpose:** To specify an alternate text representation for the
|
||||
property value.
|
||||
|
||||
**Format Definition:** This property parameter is defined by the
|
||||
following notation::
|
||||
|
||||
altrepparam = "ALTREP" "=" DQUOTE uri DQUOTE
|
||||
|
||||
**Description**: This parameter specifies a URI that points to an
|
||||
alternate representation for a textual property value. A property
|
||||
specifying this parameter MUST also include a value that reflects
|
||||
the default representation of the text value. The URI parameter
|
||||
value MUST be specified in a quoted-string.
|
||||
|
||||
.. note::
|
||||
|
||||
While there is no restriction imposed on the URI schemes
|
||||
allowed for this parameter, Content Identifier (CID) [RFC2392],
|
||||
HTTP [RFC2616], and HTTPS [RFC2818] are the URI schemes most
|
||||
commonly used by current implementations.
|
||||
|
||||
**Example:**
|
||||
|
||||
::
|
||||
|
||||
DESCRIPTION;ALTREP="CID:part3.msg.970415T083000@example.com":
|
||||
Project XYZ Review Meeting will include the following agenda
|
||||
items: (a) Market Overview\, (b) Finances\, (c) Project Man
|
||||
agement
|
||||
|
||||
The "ALTREP" property parameter value might point to a "text/html"
|
||||
content portion.
|
||||
|
||||
::
|
||||
|
||||
Content-Type:text/html
|
||||
Content-Id:<part3.msg.970415T083000@example.com>
|
||||
|
||||
<html>
|
||||
<head>
|
||||
<title></title>
|
||||
</head>
|
||||
<body>
|
||||
<p>
|
||||
<b>Project XYZ Review Meeting</b> will include
|
||||
the following agenda items:
|
||||
<ol>
|
||||
<li>Market Overview</li>
|
||||
<li>Finances</li>
|
||||
<li>Project Management</li>
|
||||
</ol>
|
||||
</p>
|
||||
</body>
|
||||
</html>
|
||||
|
||||
|
||||
3.2.2. Common Name
|
||||
------------------
|
||||
|
||||
**Parameter Name:** CN
|
||||
|
||||
**Purpose:** To specify the common name to be associated with the
|
||||
calendar user specified by the property.
|
||||
|
||||
**Format Definition:** This property parameter is defined by the
|
||||
following notation::
|
||||
|
||||
cnparam = "CN" "=" param-value
|
||||
|
||||
**Description:** This parameter can be specified on properties with a
|
||||
CAL-ADDRESS value type. 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.
|
||||
|
||||
**Example:**
|
||||
|
||||
::
|
||||
ORGANIZER;CN="John Smith":mailto:jsmith@example.com
|
||||
|
||||
|
||||
3.2.3. Calendar User Type
|
||||
-------------------------
|
||||
|
||||
**Parameter Name:** CUTYPE
|
||||
|
||||
**Purpose:** To identify the type of calendar user specified by the
|
||||
property.
|
||||
|
||||
**Format Definition:** This property parameter is defined by the
|
||||
following notation::
|
||||
|
||||
::
|
||||
|
||||
cutypeparam = "CUTYPE" "="
|
||||
("INDIVIDUAL" ; An individual
|
||||
/ "GROUP" ; A group of individuals
|
||||
/ "RESOURCE" ; A physical resource
|
||||
/ "ROOM" ; A room resource
|
||||
/ "UNKNOWN" ; Otherwise not known
|
||||
/ x-name ; Experimental type
|
||||
/ iana-token) ; Other IANA-registered
|
||||
; type
|
||||
; Default is INDIVIDUAL
|
||||
|
||||
**Description:** This parameter can be specified on properties with a
|
||||
CAL-ADDRESS value type. The parameter identifies the type of
|
||||
calendar user specified by the property. If not specified on a
|
||||
property that allows this parameter, the default is INDIVIDUAL.
|
||||
Applications MUST treat x-name and iana-token values they don't
|
||||
recognize the same way as they would the UNKNOWN value.
|
||||
|
||||
**Example:**
|
||||
|
||||
::
|
||||
|
||||
ATTENDEE;CUTYPE=GROUP:mailto:ietf-calsch@example.org
|
||||
|
||||
|
||||
3.2.4. Delegators
|
||||
-----------------
|
||||
|
||||
**Parameter Name:** DELEGATED-FROM
|
||||
|
||||
**Purpose:** To specify the calendar users that have delegated their
|
||||
participation to the calendar user specified by the property.
|
||||
|
||||
**Format Definition:** This property parameter is defined by the
|
||||
following notation::
|
||||
|
||||
delfromparam = "DELEGATED-FROM" "=" DQUOTE cal-address
|
||||
DQUOTE *("," DQUOTE cal-address DQUOTE)
|
||||
|
||||
**Description:** This parameter can be specified on properties with a
|
||||
CAL-ADDRESS value type. This parameter specifies those calendar
|
||||
users 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.
|
||||
|
||||
**Example:**
|
||||
|
||||
::
|
||||
|
||||
ATTENDEE;DELEGATED-FROM="mailto:jsmith@example.com":mailto:
|
||||
jdoe@example.com
|
||||
|
||||
3.2.5. Delegatees
|
||||
-----------------
|
||||
|
||||
Parameter Name: DELEGATED-TO
|
||||
|
||||
Purpose: To specify the calendar users to whom the calendar user
|
||||
specified by the property has delegated participation.
|
||||
|
||||
Format Definition: This property parameter is defined by the
|
||||
following notation:
|
||||
|
||||
deltoparam = "DELEGATED-TO" "=" DQUOTE cal-address DQUOTE
|
||||
*("," DQUOTE cal-address DQUOTE)
|
||||
|
||||
Description: This parameter can be specified on properties with a
|
||||
CAL-ADDRESS value type. 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 individual calendar address parameter values MUST each be
|
||||
specified in a quoted-string.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
Desruisseaux Standards Track [Page 17]
|
||||
|
||||
RFC 5545 iCalendar September 2009
|
||||
|
||||
|
||||
Example:
|
||||
|
||||
ATTENDEE;DELEGATED-TO="mailto:jdoe@example.com","mailto:jqpublic
|
||||
@example.com":mailto:jsmith@example.com
|
||||
|
||||
3.2.6. Directory Entry Reference
|
||||
|
||||
Parameter Name: DIR
|
||||
|
||||
Purpose: To specify reference to a directory entry associated with
|
||||
the calendar user specified by the property.
|
||||
|
||||
Format Definition: This property parameter is defined by the
|
||||
following notation:
|
||||
|
||||
dirparam = "DIR" "=" DQUOTE uri DQUOTE
|
||||
|
||||
Description: This parameter can be specified on properties with a
|
||||
CAL-ADDRESS value type. 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 URI parameter
|
||||
value MUST be specified in a quoted-string.
|
||||
|
||||
Note: While there is no restriction imposed on the URI schemes
|
||||
allowed for this parameter, CID [RFC2392], DATA [RFC2397], FILE
|
||||
[RFC1738], FTP [RFC1738], HTTP [RFC2616], HTTPS [RFC2818], LDAP
|
||||
[RFC4516], and MID [RFC2392] are the URI schemes most commonly
|
||||
used by current implementations.
|
||||
|
||||
Example:
|
||||
|
||||
ORGANIZER;DIR="ldap://example.com:6666/o=ABC%20Industries,
|
||||
c=US???(cn=Jim%20Dolittle)":mailto:jimdo@example.com
|
||||
|
||||
3.2.7. Inline Encoding
|
||||
|
||||
Parameter Name: ENCODING
|
||||
|
||||
Purpose: To specify an alternate inline encoding for the property
|
||||
value.
|
||||
|
||||
Format Definition: This property parameter is defined by the
|
||||
following notation:
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
Desruisseaux Standards Track [Page 18]
|
||||
|
||||
RFC 5545 iCalendar September 2009
|
||||
|
||||
|
||||
encodingparam = "ENCODING" "="
|
||||
( "8BIT"
|
||||
; "8bit" text encoding is defined in [RFC2045]
|
||||
/ "BASE64"
|
||||
; "BASE64" binary encoding format is defined in [RFC4648]
|
||||
)
|
||||
|
||||
Description: This property parameter identifies the inline encoding
|
||||
used in a property value. The default encoding is "8BIT",
|
||||
corresponding to a property value consisting of text. The
|
||||
"BASE64" encoding type corresponds to a property value encoded
|
||||
using the "BASE64" encoding defined in [RFC2045].
|
||||
|
||||
If the value type parameter is ";VALUE=BINARY", then the inline
|
||||
encoding parameter MUST be specified with the value
|
||||
";ENCODING=BASE64".
|
||||
|
||||
Example:
|
||||
|
||||
ATTACH;FMTTYPE=text/plain;ENCODING=BASE64;VALUE=BINARY:TG9yZW
|
||||
0gaXBzdW0gZG9sb3Igc2l0IGFtZXQsIGNvbnNlY3RldHVyIGFkaXBpc2ljaW
|
||||
5nIGVsaXQsIHNlZCBkbyBlaXVzbW9kIHRlbXBvciBpbmNpZGlkdW50IHV0IG
|
||||
xhYm9yZSBldCBkb2xvcmUgbWFnbmEgYWxpcXVhLiBVdCBlbmltIGFkIG1pbm
|
||||
ltIHZlbmlhbSwgcXVpcyBub3N0cnVkIGV4ZXJjaXRhdGlvbiB1bGxhbWNvIG
|
||||
xhYm9yaXMgbmlzaSB1dCBhbGlxdWlwIGV4IGVhIGNvbW1vZG8gY29uc2VxdW
|
||||
F0LiBEdWlzIGF1dGUgaXJ1cmUgZG9sb3IgaW4gcmVwcmVoZW5kZXJpdCBpbi
|
||||
B2b2x1cHRhdGUgdmVsaXQgZXNzZSBjaWxsdW0gZG9sb3JlIGV1IGZ1Z2lhdC
|
||||
BudWxsYSBwYXJpYXR1ci4gRXhjZXB0ZXVyIHNpbnQgb2NjYWVjYXQgY3VwaW
|
||||
RhdGF0IG5vbiBwcm9pZGVudCwgc3VudCBpbiBjdWxwYSBxdWkgb2ZmaWNpYS
|
||||
BkZXNlcnVudCBtb2xsaXQgYW5pbSBpZCBlc3QgbGFib3J1bS4=
|
||||
|
||||
3.2.8. Format Type
|
||||
|
||||
Parameter Name: FMTTYPE
|
||||
|
||||
Purpose: To specify the content type of a referenced object.
|
||||
|
||||
Format Definition: This property parameter is defined by the
|
||||
following notation:
|
||||
|
||||
fmttypeparam = "FMTTYPE" "=" type-name "/" subtype-name
|
||||
; Where "type-name" and "subtype-name" are
|
||||
; defined in Section 4.2 of [RFC4288].
|
||||
|
||||
Description: This parameter can be specified on properties that are
|
||||
used to reference an object. The parameter specifies the media
|
||||
type [RFC4288] of the referenced object. For example, on the
|
||||
"ATTACH" property, an FTP type URI value does not, by itself,
|
||||
|
||||
|
||||
|
||||
Desruisseaux Standards Track [Page 19]
|
||||
|
||||
RFC 5545 iCalendar September 2009
|
||||
|
||||
|
||||
necessarily convey the type of content associated with the
|
||||
resource. The parameter value MUST be the text for either an
|
||||
IANA-registered media type or a non-standard media type.
|
||||
|
||||
Example:
|
||||
|
||||
ATTACH;FMTTYPE=application/msword:ftp://example.com/pub/docs/
|
||||
agenda.doc
|
||||
|
||||
3.2.9. Free/Busy Time Type
|
||||
|
||||
Parameter Name: FBTYPE
|
||||
|
||||
Purpose: To specify the free or busy time type.
|
||||
|
||||
Format Definition: This property parameter is defined by the
|
||||
following notation:
|
||||
|
||||
fbtypeparam = "FBTYPE" "=" ("FREE" / "BUSY"
|
||||
/ "BUSY-UNAVAILABLE" / "BUSY-TENTATIVE"
|
||||
/ x-name
|
||||
; Some experimental iCalendar free/busy type.
|
||||
/ iana-token)
|
||||
; Some other IANA-registered iCalendar free/busy type.
|
||||
|
||||
Description: This 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. The value BUSY-UNAVAILABLE indicates that the time
|
||||
interval is busy and that the interval can not be scheduled. The
|
||||
value BUSY-TENTATIVE indicates that the time interval is busy
|
||||
because one or more events have been tentatively scheduled for
|
||||
that interval. If not specified on a property that allows this
|
||||
parameter, the default is BUSY. Applications MUST treat x-name
|
||||
and iana-token values they don't recognize the same way as they
|
||||
would the BUSY value.
|
||||
|
||||
Example: The following is an example of this parameter on a
|
||||
"FREEBUSY" property.
|
||||
|
||||
FREEBUSY;FBTYPE=BUSY:19980415T133000Z/19980415T170000Z
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
Desruisseaux Standards Track [Page 20]
|
||||
|
||||
RFC 5545 iCalendar September 2009
|
||||
|
||||
|
||||
3.2.10. Language
|
||||
|
||||
Parameter Name: LANGUAGE
|
||||
|
||||
Purpose: To specify the language for text values in a property or
|
||||
property parameter.
|
||||
|
||||
Format Definition: This property parameter is defined by the
|
||||
following notation:
|
||||
|
||||
languageparam = "LANGUAGE" "=" language
|
||||
|
||||
language = Language-Tag
|
||||
; As defined in [RFC5646].
|
||||
|
||||
Description: This parameter identifies the language of the text in
|
||||
the property value and of all property parameter values of the
|
||||
property. The value of the "LANGUAGE" property parameter is that
|
||||
defined in [RFC5646].
|
||||
|
||||
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.
|
||||
|
||||
Example: The following are examples of this parameter on the
|
||||
"SUMMARY" and "LOCATION" properties:
|
||||
|
||||
SUMMARY;LANGUAGE=en-US:Company Holiday Party
|
||||
|
||||
LOCATION;LANGUAGE=en:Germany
|
||||
|
||||
LOCATION;LANGUAGE=no:Tyskland
|
||||
|
||||
3.2.11. Group or List Membership
|
||||
|
||||
Parameter Name: MEMBER
|
||||
|
||||
Purpose: To specify the group or list membership of the calendar
|
||||
user specified by the property.
|
||||
|
||||
Format Definition: This property parameter is defined by the
|
||||
following notation:
|
||||
|
||||
memberparam = "MEMBER" "=" DQUOTE cal-address DQUOTE
|
||||
*("," DQUOTE cal-address DQUOTE)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
Desruisseaux Standards Track [Page 21]
|
||||
|
||||
RFC 5545 iCalendar September 2009
|
||||
|
||||
|
||||
Description: This parameter can be specified on properties with a
|
||||
CAL-ADDRESS value type. The parameter identifies the groups or
|
||||
list membership for the calendar user specified by the property.
|
||||
The parameter value is either a single calendar address in a
|
||||
quoted-string or a COMMA-separated list of calendar addresses,
|
||||
each in a quoted-string. The individual calendar address
|
||||
parameter values MUST each be specified in a quoted-string.
|
||||
|
||||
Example:
|
||||
|
||||
ATTENDEE;MEMBER="mailto:ietf-calsch@example.org":mailto:
|
||||
jsmith@example.com
|
||||
|
||||
ATTENDEE;MEMBER="mailto:projectA@example.com","mailto:pr
|
||||
ojectB@example.com":mailto:janedoe@example.com
|
||||
|
||||
3.2.12. Participation Status
|
||||
|
||||
Parameter Name: PARTSTAT
|
||||
|
||||
Purpose: To specify the participation status for the calendar user
|
||||
specified by the property.
|
||||
|
||||
Format Definition: This property parameter is defined by the
|
||||
following notation:
|
||||
|
||||
partstatparam = "PARTSTAT" "="
|
||||
(partstat-event
|
||||
/ partstat-todo
|
||||
/ partstat-jour)
|
||||
|
||||
partstat-event = ("NEEDS-ACTION" ; Event needs action
|
||||
/ "ACCEPTED" ; Event accepted
|
||||
/ "DECLINED" ; Event declined
|
||||
/ "TENTATIVE" ; Event tentatively
|
||||
; accepted
|
||||
/ "DELEGATED" ; Event delegated
|
||||
/ x-name ; Experimental status
|
||||
/ iana-token) ; Other IANA-registered
|
||||
; status
|
||||
; These are the participation statuses for a "VEVENT".
|
||||
; Default is NEEDS-ACTION.
|
||||
|
||||
partstat-todo = ("NEEDS-ACTION" ; To-do needs action
|
||||
/ "ACCEPTED" ; To-do accepted
|
||||
/ "DECLINED" ; To-do declined
|
||||
/ "TENTATIVE" ; To-do tentatively
|
||||
; accepted
|
||||
|
||||
|
||||
|
||||
Desruisseaux Standards Track [Page 22]
|
||||
|
||||
RFC 5545 iCalendar September 2009
|
||||
|
||||
|
||||
/ "DELEGATED" ; To-do delegated
|
||||
/ "COMPLETED" ; To-do completed
|
||||
; COMPLETED property has
|
||||
; DATE-TIME completed
|
||||
/ "IN-PROCESS" ; To-do in process of
|
||||
; being completed
|
||||
/ x-name ; Experimental status
|
||||
/ iana-token) ; Other IANA-registered
|
||||
; status
|
||||
; These are the participation statuses for a "VTODO".
|
||||
; Default is NEEDS-ACTION.
|
||||
|
||||
|
||||
|
||||
partstat-jour = ("NEEDS-ACTION" ; Journal needs action
|
||||
/ "ACCEPTED" ; Journal accepted
|
||||
/ "DECLINED" ; Journal declined
|
||||
/ x-name ; Experimental status
|
||||
/ iana-token) ; Other IANA-registered
|
||||
; status
|
||||
; These are the participation statuses for a "VJOURNAL".
|
||||
; Default is NEEDS-ACTION.
|
||||
|
||||
Description: This parameter can be specified on properties with a
|
||||
CAL-ADDRESS value type. The parameter identifies the
|
||||
participation status for the calendar user specified by the
|
||||
property value. The parameter values differ depending on whether
|
||||
they are associated with a group-scheduled "VEVENT", "VTODO", or
|
||||
"VJOURNAL". The values MUST match one of the values allowed for
|
||||
the given calendar component. If not specified on a property that
|
||||
allows this parameter, the default value is NEEDS-ACTION.
|
||||
Applications MUST treat x-name and iana-token values they don't
|
||||
recognize the same way as they would the NEEDS-ACTION value.
|
||||
|
||||
Example:
|
||||
|
||||
ATTENDEE;PARTSTAT=DECLINED:mailto:jsmith@example.com
|
||||
|
||||
3.2.13. Recurrence Identifier Range
|
||||
|
||||
Parameter Name: RANGE
|
||||
|
||||
Purpose: To specify the effective range of recurrence instances from
|
||||
the instance specified by the recurrence identifier specified by
|
||||
the property.
|
||||
|
||||
Format Definition: This property parameter is defined by the
|
||||
following notation:
|
||||
|
||||
|
||||
|
||||
Desruisseaux Standards Track [Page 23]
|
||||
|
||||
RFC 5545 iCalendar September 2009
|
||||
|
||||
|
||||
rangeparam = "RANGE" "=" "THISANDFUTURE"
|
||||
; To specify the instance specified by the recurrence identifier
|
||||
; and all subsequent recurrence instances.
|
||||
|
||||
Description: This parameter can be specified on a property that
|
||||
specifies a recurrence identifier. The parameter specifies the
|
||||
effective range of recurrence instances that is specified by the
|
||||
property. The effective range is from the recurrence identifier
|
||||
specified by the property. If this parameter is not specified on
|
||||
an allowed property, then the default range is the single instance
|
||||
specified by the recurrence identifier value of the property. The
|
||||
parameter value can only be "THISANDFUTURE" to indicate a range
|
||||
defined by the recurrence identifier and all subsequent instances.
|
||||
The value "THISANDPRIOR" is deprecated by this revision of
|
||||
iCalendar and MUST NOT be generated by applications.
|
||||
|
||||
Example:
|
||||
|
||||
RECURRENCE-ID;RANGE=THISANDFUTURE:19980401T133000Z
|
||||
|
||||
3.2.14. Alarm Trigger Relationship
|
||||
|
||||
Parameter Name: RELATED
|
||||
|
||||
Purpose: To specify the relationship of the alarm trigger with
|
||||
respect to the start or end of the calendar component.
|
||||
|
||||
Format Definition: This property parameter is defined by the
|
||||
following notation:
|
||||
|
||||
trigrelparam = "RELATED" "="
|
||||
("START" ; Trigger off of start
|
||||
/ "END") ; Trigger off of end
|
||||
|
||||
Description: This parameter can be specified on properties that
|
||||
specify an alarm trigger with a "DURATION" value type. 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. If the parameter is not
|
||||
specified on an allowable property, then the default is START.
|
||||
|
||||
Example:
|
||||
|
||||
TRIGGER;RELATED=END:PT5M
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
Desruisseaux Standards Track [Page 24]
|
||||
|
||||
RFC 5545 iCalendar September 2009
|
||||
|
||||
|
||||
3.2.15. Relationship Type
|
||||
|
||||
Parameter Name: RELTYPE
|
||||
|
||||
Purpose: To specify the type of hierarchical relationship associated
|
||||
with the calendar component specified by the property.
|
||||
|
||||
Format Definition: This property parameter is defined by the
|
||||
following notation:
|
||||
|
||||
reltypeparam = "RELTYPE" "="
|
||||
("PARENT" ; Parent relationship - Default
|
||||
/ "CHILD" ; Child relationship
|
||||
/ "SIBLING" ; Sibling relationship
|
||||
/ iana-token ; Some other IANA-registered
|
||||
; iCalendar relationship type
|
||||
/ x-name) ; A non-standard, experimental
|
||||
; relationship type
|
||||
|
||||
Description: This parameter can be specified on a property that
|
||||
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 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; or 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.
|
||||
Applications MUST treat x-name and iana-token values they don't
|
||||
recognize the same way as they would the PARENT value.
|
||||
|
||||
Example:
|
||||
|
||||
RELATED-TO;RELTYPE=SIBLING:19960401-080045-4000F192713@
|
||||
example.com
|
||||
|
||||
3.2.16. Participation Role
|
||||
|
||||
Parameter Name: ROLE
|
||||
|
||||
Purpose: To specify the participation role for the calendar user
|
||||
specified by the property.
|
||||
|
||||
Format Definition: This property parameter is defined by the
|
||||
following notation:
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
Desruisseaux Standards Track [Page 25]
|
||||
|
||||
RFC 5545 iCalendar September 2009
|
||||
|
||||
|
||||
roleparam = "ROLE" "="
|
||||
("CHAIR" ; Indicates chair of the
|
||||
; calendar entity
|
||||
/ "REQ-PARTICIPANT" ; Indicates a participant whose
|
||||
; participation is required
|
||||
/ "OPT-PARTICIPANT" ; Indicates a participant whose
|
||||
; participation is optional
|
||||
/ "NON-PARTICIPANT" ; Indicates a participant who
|
||||
; is copied for information
|
||||
; purposes only
|
||||
/ x-name ; Experimental role
|
||||
/ iana-token) ; Other IANA role
|
||||
; Default is REQ-PARTICIPANT
|
||||
|
||||
Description: This parameter can be specified on properties with a
|
||||
CAL-ADDRESS value type. The parameter specifies the participation
|
||||
role for the 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.
|
||||
Applications MUST treat x-name and iana-token values they don't
|
||||
recognize the same way as they would the REQ-PARTICIPANT value.
|
||||
|
||||
Example:
|
||||
|
||||
ATTENDEE;ROLE=CHAIR:mailto:mrbig@example.com
|
||||
|
||||
3.2.17. RSVP Expectation
|
||||
|
||||
Parameter Name: RSVP
|
||||
|
||||
Purpose: To specify whether there is an expectation of a favor of a
|
||||
reply from the calendar user specified by the property value.
|
||||
|
||||
Format Definition: This property parameter is defined by the
|
||||
following notation:
|
||||
|
||||
rsvpparam = "RSVP" "=" ("TRUE" / "FALSE")
|
||||
; Default is FALSE
|
||||
|
||||
Description: This parameter can be specified on properties with a
|
||||
CAL-ADDRESS value type. 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. If not specified on a property that allows this
|
||||
parameter, the default value is FALSE.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
Desruisseaux Standards Track [Page 26]
|
||||
|
||||
RFC 5545 iCalendar September 2009
|
||||
|
||||
|
||||
Example:
|
||||
|
||||
ATTENDEE;RSVP=TRUE:mailto:jsmith@example.com
|
||||
|
||||
3.2.18. Sent By
|
||||
|
||||
Parameter Name: SENT-BY
|
||||
|
||||
Purpose: To specify the calendar user that is acting on behalf of
|
||||
the calendar user specified by the property.
|
||||
|
||||
Format Definition: This property parameter is defined by the
|
||||
following notation:
|
||||
|
||||
sentbyparam = "SENT-BY" "=" DQUOTE cal-address DQUOTE
|
||||
|
||||
Description: This parameter can be specified on properties with a
|
||||
CAL-ADDRESS value type. The parameter specifies the calendar user
|
||||
that is acting on behalf of the calendar user specified by the
|
||||
property. The parameter value MUST be a mailto URI as defined in
|
||||
[RFC2368]. The individual calendar address parameter values MUST
|
||||
each be specified in a quoted-string.
|
||||
|
||||
Example:
|
||||
|
||||
ORGANIZER;SENT-BY="mailto:sray@example.com":mailto:
|
||||
jsmith@example.com
|
||||
|
||||
3.2.19. Time Zone Identifier
|
||||
|
||||
Parameter Name: TZID
|
||||
|
||||
Purpose: To specify the identifier for the time zone definition for
|
||||
a time component in the property value.
|
||||
|
||||
Format Definition: This property parameter is defined by the
|
||||
following notation:
|
||||
|
||||
tzidparam = "TZID" "=" [tzidprefix] paramtext
|
||||
|
||||
tzidprefix = "/"
|
||||
|
||||
Description: This parameter MUST be specified on the "DTSTART",
|
||||
"DTEND", "DUE", "EXDATE", and "RDATE" properties when either a
|
||||
DATE-TIME or TIME value type is specified and when the value is
|
||||
neither a UTC or a "floating" time. Refer to the DATE-TIME or
|
||||
TIME value type definition for a description of UTC and "floating
|
||||
time" formats. This property parameter specifies a text value
|
||||
|
||||
|
||||
|
||||
Desruisseaux Standards Track [Page 27]
|
||||
|
||||
RFC 5545 iCalendar September 2009
|
||||
|
||||
|
||||
that uniquely identifies the "VTIMEZONE" calendar component to be
|
||||
used when evaluating the time portion of the property. The value
|
||||
of the "TZID" property parameter will be equal to the value of the
|
||||
"TZID" property for the matching time zone definition. An
|
||||
individual "VTIMEZONE" calendar component MUST be specified for
|
||||
each unique "TZID" parameter value specified in the iCalendar
|
||||
object.
|
||||
|
||||
The parameter MUST be specified on properties with a DATE-TIME
|
||||
value if the DATE-TIME is not either a UTC or a "floating" time.
|
||||
Failure to include and follow VTIMEZONE definitions in iCalendar
|
||||
objects may lead to inconsistent understanding of the local time
|
||||
at any given location.
|
||||
|
||||
The presence of the SOLIDUS character as a prefix, indicates that
|
||||
this "TZID" represents a unique ID in a globally defined time zone
|
||||
registry (when such registry is defined).
|
||||
|
||||
Note: This document does not define a naming convention for
|
||||
time zone identifiers. Implementers may want to use the naming
|
||||
conventions defined in existing time zone specifications such
|
||||
as the public-domain TZ database [TZDB]. The specification of
|
||||
globally unique time zone identifiers is not addressed by this
|
||||
document and is left for future study.
|
||||
|
||||
The following are examples of this property parameter:
|
||||
|
||||
DTSTART;TZID=America/New_York:19980119T020000
|
||||
|
||||
DTEND;TZID=America/New_York:19980119T030000
|
||||
|
||||
The "TZID" property parameter MUST NOT be applied to DATE
|
||||
properties and DATE-TIME or TIME properties whose time values are
|
||||
specified in UTC.
|
||||
|
||||
The use of local time in a DATE-TIME or TIME value without the
|
||||
"TZID" property parameter is to be interpreted as floating time,
|
||||
regardless of the existence of "VTIMEZONE" calendar components in
|
||||
the iCalendar object.
|
||||
|
||||
For more information, see the sections on the value types DATE-
|
||||
TIME and TIME.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
Desruisseaux Standards Track [Page 28]
|
||||
|
||||
RFC 5545 iCalendar September 2009
|
||||
|
||||
|
||||
3.2.20. Value Data Types
|
||||
|
||||
Parameter Name: VALUE
|
||||
|
||||
Purpose: To explicitly specify the value type format for a property
|
||||
value.
|
||||
|
||||
Format Definition: This property parameter is defined by the
|
||||
following notation:
|
||||
|
||||
valuetypeparam = "VALUE" "=" valuetype
|
||||
|
||||
valuetype = ("BINARY"
|
||||
/ "BOOLEAN"
|
||||
/ "CAL-ADDRESS"
|
||||
/ "DATE"
|
||||
/ "DATE-TIME"
|
||||
/ "DURATION"
|
||||
/ "FLOAT"
|
||||
/ "INTEGER"
|
||||
/ "PERIOD"
|
||||
/ "RECUR"
|
||||
/ "TEXT"
|
||||
/ "TIME"
|
||||
/ "URI"
|
||||
/ "UTC-OFFSET"
|
||||
/ x-name
|
||||
; Some experimental iCalendar value type.
|
||||
/ iana-token)
|
||||
; Some other IANA-registered iCalendar value type.
|
||||
|
||||
Description: This parameter specifies the value type and format of
|
||||
the property value. The property values MUST be of a single value
|
||||
type. For example, a "RDATE" property cannot have a combination
|
||||
of DATE-TIME and TIME value types.
|
||||
|
||||
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.
|
||||
|
||||
Applications MUST preserve the value data for x-name and iana-
|
||||
token values that they don't recognize without attempting to
|
||||
interpret or parse the value data.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
Desruisseaux Standards Track [Page 29]
|
||||
|
||||
RFC 5545 iCalendar September 2009
|
||||
|
||||
|
||||
|
|
@ -0,0 +1,31 @@
|
|||
3. iCalendar Object Specification
|
||||
=================================
|
||||
|
||||
The following sections define the details of a Calendaring and
|
||||
Scheduling Core Object Specification. The Calendaring and Scheduling
|
||||
Core Object is a collection of calendaring and scheduling
|
||||
information. Typically, this information will consist of an
|
||||
iCalendar stream with one or more iCalendar objects. The body of the
|
||||
iCalendar object consists of a sequence of calendar properties and
|
||||
one or more calendar components.
|
||||
|
||||
Section 3.1 defines the content line format; Section 3.2 defines the
|
||||
property parameter format; Section 3.3 defines the data types for
|
||||
property values; Section 3.4 defines the iCalendar object format;
|
||||
Section 3.5 defines the iCalendar property format; Section 3.6
|
||||
defines the calendar component format; Section 3.7 defines calendar
|
||||
properties; and Section 3.8 defines calendar component properties.
|
||||
|
||||
This information is intended to be an integral part of the MIME
|
||||
content type registration. In addition, this information can be used
|
||||
independent of such content registration. In particular, this memo
|
||||
has direct applicability for use as a calendaring and scheduling
|
||||
exchange format in file-, memory-, or network-based transport
|
||||
mechanisms.
|
||||
|
||||
|
||||
.. toctree::
|
||||
:maxdepth: 2
|
||||
|
||||
3_1_content_lines.rst
|
||||
3_2_property_parameters.rst
|
||||
|
|
@ -0,0 +1,199 @@
|
|||
=========================================================================
|
||||
Internet Calendaring and Scheduling Core Object Specification (iCalendar)
|
||||
=========================================================================
|
||||
|
||||
Abstract
|
||||
""""""""
|
||||
|
||||
This document defines the iCalendar data format for representing and
|
||||
exchanging calendaring and scheduling information such as events,
|
||||
to-dos, journal entries, and free/busy information, independent of any
|
||||
particular calendar service or protocol.
|
||||
|
||||
Status of This Memo
|
||||
"""""""""""""""""""
|
||||
|
||||
This document specifies an Internet standards track protocol for the
|
||||
Internet community, and requests discussion and suggestions for
|
||||
improvements. Please refer to the current edition of the "Internet
|
||||
Official Protocol Standards" (STD 1) for the standardization state
|
||||
and status of this protocol. Distribution of this memo is unlimited.
|
||||
|
||||
Copyright and License Notice
|
||||
""""""""""""""""""""""""""""
|
||||
|
||||
Copyright (c) 2009 IETF Trust and the persons identified as the
|
||||
document authors. All rights reserved.
|
||||
|
||||
This document is subject to BCP 78 and the IETF Trust's Legal
|
||||
Provisions Relating to IETF Documents
|
||||
(http://trustee.ietf.org/license-info) in effect on the date of
|
||||
publication of this document. Please review these documents
|
||||
carefully, as they describe your rights and restrictions with respect
|
||||
to this document. Code Components extracted from this document must
|
||||
include Simplified BSD License text as described in Section 4.e of
|
||||
the Trust Legal Provisions and are provided without warranty as
|
||||
described in the BSD License.
|
||||
|
||||
This document may contain material from IETF Documents or IETF
|
||||
Contributions published or made publicly available before November
|
||||
10, 2008. The person(s) controlling the copyright in some of this
|
||||
material may not have granted the IETF Trust the right to allow
|
||||
modifications of such material outside the IETF Standards Process.
|
||||
Without obtaining an adequate license from the person(s) controlling
|
||||
the copyright in such materials, this document may not be modified
|
||||
outside the IETF Standards Process, and derivative works of it may
|
||||
not be created outside the IETF Standards Process, except to format
|
||||
it for publication as an RFC or to translate it into languages other
|
||||
than English.
|
||||
|
||||
Table of Contents
|
||||
"""""""""""""""""
|
||||
|
||||
.. toctree::
|
||||
:maxdepth: 3
|
||||
|
||||
1_introduction
|
||||
2_basic_grammar_and_convetions
|
||||
3_icalendar_object_specification.rst
|
||||
|
||||
::
|
||||
|
||||
3.2. Property Parameters . . . . . . . . . . . . . . . . . . . 12
|
||||
3.2.1. Alternate Text Representation . . . . . . . . . . . . 13
|
||||
3.2.2. Common Name . . . . . . . . . . . . . . . . . . . . . 15
|
||||
3.2.3. Calendar User Type . . . . . . . . . . . . . . . . . 15
|
||||
3.2.4. Delegators . . . . . . . . . . . . . . . . . . . . . 16
|
||||
3.2.5. Delegatees . . . . . . . . . . . . . . . . . . . . . 16
|
||||
3.2.6. Directory Entry Reference . . . . . . . . . . . . . . 17
|
||||
3.2.7. Inline Encoding . . . . . . . . . . . . . . . . . . . 17
|
||||
3.2.8. Format Type . . . . . . . . . . . . . . . . . . . . . 18
|
||||
3.2.9. Free/Busy Time Type . . . . . . . . . . . . . . . . . 19
|
||||
3.2.10. Language . . . . . . . . . . . . . . . . . . . . . . 20
|
||||
3.2.11. Group or List Membership . . . . . . . . . . . . . . 20
|
||||
3.2.12. Participation Status . . . . . . . . . . . . . . . . 21
|
||||
3.2.13. Recurrence Identifier Range . . . . . . . . . . . . . 22
|
||||
3.2.14. Alarm Trigger Relationship . . . . . . . . . . . . . 23
|
||||
3.2.15. Relationship Type . . . . . . . . . . . . . . . . . . 24
|
||||
3.2.16. Participation Role . . . . . . . . . . . . . . . . . 25
|
||||
3.2.17. RSVP Expectation . . . . . . . . . . . . . . . . . . 25
|
||||
3.2.18. Sent By . . . . . . . . . . . . . . . . . . . . . . . 26
|
||||
3.2.19. Time Zone Identifier . . . . . . . . . . . . . . . . 26
|
||||
3.2.20. Value Data Types . . . . . . . . . . . . . . . . . . 28
|
||||
3.3. Property Value Data Types . . . . . . . . . . . . . . . . 29
|
||||
3.3.1. Binary . . . . . . . . . . . . . . . . . . . . . . . 29
|
||||
3.3.2. Boolean . . . . . . . . . . . . . . . . . . . . . . . 30
|
||||
3.3.3. Calendar User Address . . . . . . . . . . . . . . . . 30
|
||||
3.3.4. Date . . . . . . . . . . . . . . . . . . . . . . . . 31
|
||||
3.3.5. Date-Time . . . . . . . . . . . . . . . . . . . . . . 31
|
||||
3.3.6. Duration . . . . . . . . . . . . . . . . . . . . . . 34
|
||||
3.3.7. Float . . . . . . . . . . . . . . . . . . . . . . . . 35
|
||||
3.3.8. Integer . . . . . . . . . . . . . . . . . . . . . . . 35
|
||||
3.3.9. Period of Time . . . . . . . . . . . . . . . . . . . 36
|
||||
3.3.10. Recurrence Rule . . . . . . . . . . . . . . . . . . . 37
|
||||
3.3.11. Text . . . . . . . . . . . . . . . . . . . . . . . . 45
|
||||
3.3.12. Time . . . . . . . . . . . . . . . . . . . . . . . . 46
|
||||
3.3.13. URI . . . . . . . . . . . . . . . . . . . . . . . . . 48
|
||||
3.3.14. UTC Offset . . . . . . . . . . . . . . . . . . . . . 49
|
||||
3.4. iCalendar Object . . . . . . . . . . . . . . . . . . . . 49
|
||||
3.5. Property . . . . . . . . . . . . . . . . . . . . . . . . 50
|
||||
3.6. Calendar Components . . . . . . . . . . . . . . . . . . . 50
|
||||
3.6.1. Event Component . . . . . . . . . . . . . . . . . . . 52
|
||||
3.6.2. To-Do Component . . . . . . . . . . . . . . . . . . . 56
|
||||
3.6.3. Journal Component . . . . . . . . . . . . . . . . . . 58
|
||||
3.6.4. Free/Busy Component . . . . . . . . . . . . . . . . . 60
|
||||
3.6.5. Time Zone Component . . . . . . . . . . . . . . . . . 63
|
||||
3.6.6. Alarm Component . . . . . . . . . . . . . . . . . . . 72
|
||||
3.7. Calendar Properties . . . . . . . . . . . . . . . . . . . 77
|
||||
3.7.1. Calendar Scale . . . . . . . . . . . . . . . . . . . 77
|
||||
3.7.2. Method . . . . . . . . . . . . . . . . . . . . . . . 78
|
||||
3.7.3. Product Identifier . . . . . . . . . . . . . . . . . 79
|
||||
3.7.4. Version . . . . . . . . . . . . . . . . . . . . . . . 80
|
||||
3.8. Component Properties . . . . . . . . . . . . . . . . . . 81
|
||||
3.8.1. Descriptive Component Properties . . . . . . . . . . 81
|
||||
3.8.1.1. Attachment . . . . . . . . . . . . . . . . . . . 81
|
||||
3.8.1.2. Categories . . . . . . . . . . . . . . . . . . . 82
|
||||
3.8.1.3. Classification . . . . . . . . . . . . . . . . . 83
|
||||
3.8.1.4. Comment . . . . . . . . . . . . . . . . . . . . . 84
|
||||
3.8.1.5. Description . . . . . . . . . . . . . . . . . . . 85
|
||||
3.8.1.6. Geographic Position . . . . . . . . . . . . . . . 87
|
||||
3.8.1.7. Location . . . . . . . . . . . . . . . . . . . . 88
|
||||
3.8.1.8. Percent Complete . . . . . . . . . . . . . . . . 89
|
||||
3.8.1.9. Priority . . . . . . . . . . . . . . . . . . . . 90
|
||||
3.8.1.10. Resources . . . . . . . . . . . . . . . . . . . . 92
|
||||
3.8.1.11. Status . . . . . . . . . . . . . . . . . . . . . 93
|
||||
3.8.1.12. Summary . . . . . . . . . . . . . . . . . . . . . 94
|
||||
3.8.2. Date and Time Component Properties . . . . . . . . . 95
|
||||
3.8.2.1. Date-Time Completed . . . . . . . . . . . . . . . 95
|
||||
3.8.2.2. Date-Time End . . . . . . . . . . . . . . . . . . 96
|
||||
3.8.2.3. Date-Time Due . . . . . . . . . . . . . . . . . . 97
|
||||
3.8.2.4. Date-Time Start . . . . . . . . . . . . . . . . . 99
|
||||
3.8.2.5. Duration . . . . . . . . . . . . . . . . . . . . 100
|
||||
3.8.2.6. Free/Busy Time . . . . . . . . . . . . . . . . . 101
|
||||
3.8.2.7. Time Transparency . . . . . . . . . . . . . . . . 102
|
||||
3.8.3. Time Zone Component Properties . . . . . . . . . . . 103
|
||||
3.8.3.1. Time Zone Identifier . . . . . . . . . . . . . . 103
|
||||
3.8.3.2. Time Zone Name . . . . . . . . . . . . . . . . . 105
|
||||
3.8.3.3. Time Zone Offset From . . . . . . . . . . . . . . 106
|
||||
3.8.3.4. Time Zone Offset To . . . . . . . . . . . . . . . 106
|
||||
3.8.3.5. Time Zone URL . . . . . . . . . . . . . . . . . . 107
|
||||
3.8.4. Relationship Component Properties . . . . . . . . . . 108
|
||||
3.8.4.1. Attendee . . . . . . . . . . . . . . . . . . . . 108
|
||||
3.8.4.2. Contact . . . . . . . . . . . . . . . . . . . . . 111
|
||||
3.8.4.3. Organizer . . . . . . . . . . . . . . . . . . . . 113
|
||||
3.8.4.4. Recurrence ID . . . . . . . . . . . . . . . . . . 114
|
||||
3.8.4.5. Related To . . . . . . . . . . . . . . . . . . . 117
|
||||
3.8.4.6. Uniform Resource Locator . . . . . . . . . . . . 118
|
||||
3.8.4.7. Unique Identifier . . . . . . . . . . . . . . . . 119
|
||||
3.8.5. Recurrence Component Properties . . . . . . . . . . . 120
|
||||
3.8.5.1. Exception Date-Times . . . . . . . . . . . . . . 120
|
||||
3.8.5.2. Recurrence Date-Times . . . . . . . . . . . . . . 122
|
||||
3.8.5.3. Recurrence Rule . . . . . . . . . . . . . . . . . 124
|
||||
3.8.6. Alarm Component Properties . . . . . . . . . . . . . 134
|
||||
3.8.6.1. Action . . . . . . . . . . . . . . . . . . . . . 134
|
||||
3.8.6.2. Repeat Count . . . . . . . . . . . . . . . . . . 135
|
||||
3.8.6.3. Trigger . . . . . . . . . . . . . . . . . . . . . 135
|
||||
3.8.7. Change Management Component Properties . . . . . . . 138
|
||||
3.8.7.1. Date-Time Created . . . . . . . . . . . . . . . . 138
|
||||
3.8.7.2. Date-Time Stamp . . . . . . . . . . . . . . . . . 139
|
||||
3.8.7.3. Last Modified . . . . . . . . . . . . . . . . . . 140
|
||||
3.8.7.4. Sequence Number . . . . . . . . . . . . . . . . . 141
|
||||
3.8.8. Miscellaneous Component Properties . . . . . . . . . 142
|
||||
3.8.8.1. IANA Properties . . . . . . . . . . . . . . . . . 142
|
||||
3.8.8.2. Non-Standard Properties . . . . . . . . . . . . . 142
|
||||
3.8.8.3. Request Status . . . . . . . . . . . . . . . . . 144
|
||||
4. iCalendar Object Examples . . . . . . . . . . . . . . . . . . 146
|
||||
5. Recommended Practices . . . . . . . . . . . . . . . . . . . . 150
|
||||
6. Internationalization Considerations . . . . . . . . . . . . . 151
|
||||
7. Security Considerations . . . . . . . . . . . . . . . . . . . 151
|
||||
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 151
|
||||
8.1. iCalendar Media Type Registration . . . . . . . . . . . . 151
|
||||
8.2. New iCalendar Elements Registration . . . . . . . . . . . 155
|
||||
8.2.1. iCalendar Elements Registration Procedure . . . . . . 155
|
||||
8.2.2. Registration Template for Components . . . . . . . . 155
|
||||
8.2.3. Registration Template for Properties . . . . . . . . 156
|
||||
8.2.4. Registration Template for Parameters . . . . . . . . 156
|
||||
8.2.5. Registration Template for Value Data Types . . . . . 157
|
||||
8.2.6. Registration Template for Values . . . . . . . . . . 157
|
||||
8.3. Initial iCalendar Elements Registries . . . . . . . . . . 158
|
||||
8.3.1. Components Registry . . . . . . . . . . . . . . . . . 158
|
||||
8.3.2. Properties Registry . . . . . . . . . . . . . . . . . 158
|
||||
8.3.3. Parameters Registry . . . . . . . . . . . . . . . . . 161
|
||||
8.3.4. Value Data Types Registry . . . . . . . . . . . . . . 162
|
||||
8.3.5. Calendar User Types Registry . . . . . . . . . . . . 162
|
||||
8.3.6. Free/Busy Time Types Registry . . . . . . . . . . . . 163
|
||||
8.3.7. Participation Statuses Registry . . . . . . . . . . . 163
|
||||
8.3.8. Relationship Types Registry . . . . . . . . . . . . . 164
|
||||
8.3.9. Participation Roles Registry . . . . . . . . . . . . 164
|
||||
8.3.10. Actions Registry . . . . . . . . . . . . . . . . . . 165
|
||||
8.3.11. Classifications Registry . . . . . . . . . . . . . . 165
|
||||
8.3.12. Methods Registry . . . . . . . . . . . . . . . . . . 165
|
||||
9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 165
|
||||
10. References . . . . . . . . . . . . . . . . . . . . . . . . . 166
|
||||
10.1. Normative References . . . . . . . . . . . . . . . . . . 166
|
||||
10.2. Informative References . . . . . . . . . . . . . . . . . 167
|
||||
Appendix A. Differences from RFC 2445 . . . . . . . . . . . . . 169
|
||||
A.1. New Restrictions . . . . . . . . . . . . . . . . . . . . 169
|
||||
A.2. Restrictions Removed . . . . . . . . . . . . . . . . . . 169
|
||||
A.3. Deprecated Features . . . . . . . . . . . . . . . . . . . 169
|
||||
|
||||
Plik diff jest za duży
Load Diff
Ładowanie…
Reference in New Issue