TBD
+TBD
Electronic address books have become ubiquitous. Their increased +
Electronic address books have become ubiquitous. Their increased presence on portable, connected devices as well as the diversity of platforms that exchange contact data call for a standard. This memo defines the vCard format, which allows the capture and exchange of information normally stored within an address book or directory application.
-A high-level overview of the differences from RFC 2425 and RFC 2426 can +
A high-level overview of the differences from RFC 2425 and RFC 2426 can be found in Appendix B.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", +
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119.
@@ -1002,7 +1002,7 @@vCard Format Specification
This document defines the vCard data format for representing and +
This document defines the vCard data format for representing and exchanging a variety of information about individuals and other entities (e.g., formatted and structured name and delivery addresses, email address, multiple telephone numbers, photograph, logo, audio @@ -1041,89 +1041,89 @@
The text/vcard MIME content type (hereafter known as "vCard"; see +
The text/vcard MIME content type (hereafter known as "vCard"; see Clause 11.1) contains contact information, typically pertaining to a single contact or group of contacts. The content consists of one or more lines in the format given below.
The charset (see RFC 3536 for internationalization terminology) for +
The charset (see RFC 3536 for internationalization terminology) for vCard is UTF-8 as defined in RFC 3629. There is no way to override this. It is invalid to specify a value other than "UTF-8" in the "charset" MIME parameter (see Clause 11.1).
Individual lines within vCard are delimited by the RFC 5322 line +
Individual lines within vCard are delimited by the RFC 5322 line break, which is a CRLF sequence (U+000D followed by U+000A). Long logical lines of text can be split into a multiple-physical-line representation using the following folding technique. Content lines SHOULD be folded to a maximum width of 75 octets, excluding the line break. Multi-octet characters MUST remain contiguous. The rationale for this folding process can be found in RFC 5322, Section 2.1.1.
-A logical line MAY be continued on the next physical line anywhere +
A logical line MAY be continued on the next physical line anywhere between two characters by inserting a CRLF immediately followed by a single white space character (space (U+0020) or horizontal tab (U+0009)). The folded line MUST contain at least one character. Any sequence of CRLF followed immediately by a single white space character is ignored (removed) when processing the content type. For example, the line:
-NOTE:This is a long description that exists on a long line.
can be represented as:
-can be represented as:
+ NOTE:This is a long description
that exists on a long line.
It could also be represented as:
-It could also be represented as:
+ NOTE:This is a long descrip
tion that exists o
n a long line.
The process of moving from this folded multiple-line representation +
The process of moving from this folded multiple-line representation of a property definition to its single-line representation is called unfolding. Unfolding is accomplished by regarding CRLF immediately followed by a white space character (namely, HTAB (U+0009) or SPACE (U+0020)) as equivalent to no characters at all (i.e., the CRLF and single white space character are removed).
-Note: It is possible for very simple implementations to generate +
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 SHOULD unfold lines in such a way as to properly restore the original sequence.
-Note: Unfolding is done differently than in RFC 5322. Unfolding +
Note: Unfolding is done differently than in RFC 5322. Unfolding in RFC 5322 only removes the CRLF, not the space following it.
-Folding is done after any content encoding of a type value. +
Folding is done after any content encoding of a type value. Unfolding is done before any decoding of a type value in a content line.
The following ABNF uses the notation of RFC 5234, which also defines +
The following ABNF uses the notation of RFC 5234, which also defines CRLF, WSP, DQUOTE, VCHAR, ALPHA, and DIGIT.
-vcard-entity = 1*vcard
vcard = "BEGIN:VCARD" CRLF
"VERSION:4.0" CRLF
1*contentline
"END:VCARD" CRLF
; A vCard object MUST include the VERSION and FN properties.
; VERSION MUST come immediately after BEGIN:VCARD.
contentline = [group "."] name *(";" param) ":" value CRLF
; When parsing a content line, folded lines must first
; be unfolded according to the unfolding procedure
; described in Section 3.2.
; When generating a content line, lines longer than 75
; characters SHOULD be folded according to the folding
; procedure described in Section 3.2.
group = 1*(ALPHA / DIGIT / "-")
name = "SOURCE" / "KIND" / "FN" / "N" / "NICKNAME"
/ "PHOTO" / "BDAY" / "ANNIVERSARY" / "GENDER" / "ADR" / "TEL"
/ "EMAIL" / "IMPP" / "LANG" / "TZ" / "GEO" / "TITLE" / "ROLE"
/ "LOGO" / "ORG" / "MEMBER" / "RELATED" / "CATEGORIES"
/ "NOTE" / "PRODID" / "REV" / "SOUND" / "UID" / "CLIENTPIDMAP"
/ "URL" / "KEY" / "FBURL" / "CALADRURI" / "CALURI" / "XML"
/ iana-token / x-name
; Parsing of the param and value is based on the "name" as
; defined in ABNF sections below.
; Group and name are case-insensitive.
iana-token = 1*(ALPHA / DIGIT / "-")
; identifier registered with IANA
x-name = "x-" 1*(ALPHA / DIGIT / "-")
; Names that begin with "x-" or "X-" are
; reserved for experimental use, not intended for released
; products, or for use in bilateral agreements.
param = language-param / value-param / pref-param / pid-param
/ type-param / geo-parameter / tz-parameter / sort-as-param
/ calscale-param / any-param
; Allowed parameters depend on property name.
param-value = *SAFE-CHAR / DQUOTE *QSAFE-CHAR DQUOTE
any-param = (iana-token / x-name) "=" param-value *("," param-value)
NON-ASCII = UTF8-2 / UTF8-3 / UTF8-4
; UTF8-{2,3,4} are defined in IETF RFC 3629
QSAFE-CHAR = WSP / "!" / %x23-7E / NON-ASCII
; Any character except CTLs, DQUOTE
SAFE-CHAR = WSP / "!" / %x23-39 / %x3C-7E / NON-ASCII
; Any character except CTLs, DQUOTE, ";", ":"
VALUE-CHAR = WSP / VCHAR / NON-ASCII
; Any textual character
A line that begins with a white space character is a continuation of +
vcard-entity = 1*vcard
vcard = "BEGIN:VCARD" CRLF
"VERSION:4.0" CRLF
1*contentline
"END:VCARD" CRLF
; A vCard object MUST include the VERSION and FN properties.
; VERSION MUST come immediately after BEGIN:VCARD.
contentline = [group "."] name *(";" param) ":" value CRLF
; When parsing a content line, folded lines must first
; be unfolded according to the unfolding procedure
; described in Section 3.2.
; When generating a content line, lines longer than 75
; characters SHOULD be folded according to the folding
; procedure described in Section 3.2.
group = 1*(ALPHA / DIGIT / "-")
name = "SOURCE" / "KIND" / "FN" / "N" / "NICKNAME"
/ "PHOTO" / "BDAY" / "ANNIVERSARY" / "GENDER" / "ADR" / "TEL"
/ "EMAIL" / "IMPP" / "LANG" / "TZ" / "GEO" / "TITLE" / "ROLE"
/ "LOGO" / "ORG" / "MEMBER" / "RELATED" / "CATEGORIES"
/ "NOTE" / "PRODID" / "REV" / "SOUND" / "UID" / "CLIENTPIDMAP"
/ "URL" / "KEY" / "FBURL" / "CALADRURI" / "CALURI" / "XML"
/ iana-token / x-name
; Parsing of the param and value is based on the "name" as
; defined in ABNF sections below.
; Group and name are case-insensitive.
iana-token = 1*(ALPHA / DIGIT / "-")
; identifier registered with IANA
x-name = "x-" 1*(ALPHA / DIGIT / "-")
; Names that begin with "x-" or "X-" are
; reserved for experimental use, not intended for released
; products, or for use in bilateral agreements.
param = language-param / value-param / pref-param / pid-param
/ type-param / geo-parameter / tz-parameter / sort-as-param
/ calscale-param / any-param
; Allowed parameters depend on property name.
param-value = *SAFE-CHAR / DQUOTE *QSAFE-CHAR DQUOTE
any-param = (iana-token / x-name) "=" param-value *("," param-value)
NON-ASCII = UTF8-2 / UTF8-3 / UTF8-4
; UTF8-{2,3,4} are defined in IETF RFC 3629
QSAFE-CHAR = WSP / "!" / %x23-7E / NON-ASCII
; Any character except CTLs, DQUOTE
SAFE-CHAR = WSP / "!" / %x23-39 / %x3C-7E / NON-ASCII
; Any character except CTLs, DQUOTE, ";", ":"
VALUE-CHAR = WSP / VCHAR / NON-ASCII
; Any textual character
A line that begins with a white space character is a continuation of the previous line, as described in Clause 4.3. The white space character and immediately preceeding CRLF should be discarded when reconstructing the original line. Note that this line-folding convention differs from that found in RFC 5322, in that the sequence <CRLF><WSP> found anywhere in the content indicates a continued line and should be removed.
-Property names and parameter names are case-insensitive (e.g., the +
Property names and parameter names are case-insensitive (e.g., the property name "fn" is the same as "FN" and "Fn"). Parameter values MAY be case-sensitive or case-insensitive, depending on their definition. Parameter values that are not explicitly defined as being case-sensitive are case-insensitive. Based on experience with vCard 3 interoperability, it is RECOMMENDED that property and parameter names be upper-case on output.
-The group construct is used to group related properties together. +
The group construct is used to group related properties together. The group name is a syntactic convention used to indicate that all property names prefaced with the same group name SHOULD be grouped together when displayed by an application. It has no other significance. Implementations that do not understand or support grouping MAY simply strip off any text before a "." to the left of the type name and present the types and values as normal.
-Property cardinalities are indicated using the following notation, +
Property cardinalities are indicated using the following notation, which is based on ABNF (see RFC 5234, Section 3.6):
-Table 1
| Cardinality | Meaning |
|---|---|
| 1 | Exactly one instance per vCard MUST be present. |
| *1 | Exactly one instance per vCard MAY be present. |
| 1* | One or more instances per vCard MUST be present. |
| * | One or more instances per vCard MAY be present. |
Properties defined in a vCard instance may have multiple values +
Table 1
| Cardinality | Meaning |
|---|---|
| 1 | Exactly one instance per vCard MUST be present. |
| *1 | Exactly one instance per vCard MAY be present. |
| 1* | One or more instances per vCard MUST be present. |
| * | One or more instances per vCard MAY be present. |
Properties defined in a vCard instance may have multiple values depending on the property cardinality. The general rule for encoding multi-valued properties is to simply create a new content line for each value (including the property name). However, it should be @@ -1131,84 +1131,84 @@
Some properties may contain one or more values delimited by a COMMA +
Some properties may contain one or more values delimited by a COMMA character (U+002C). Therefore, a COMMA character in a value MUST be escaped with a BACKSLASH character (U+005C), even for properties that don’t allow multiple instances (for consistency).
-Some properties (e.g., N and ADR) comprise multiple fields delimited +
Some properties (e.g., N and ADR) comprise multiple fields delimited by a SEMICOLON character (U+003B). Therefore, a SEMICOLON in a field of such a "compound" property MUST be escaped with a BACKSLASH character. SEMICOLON characters in non-compound properties MAY be escaped. On input, an escaped SEMICOLON character is never a field separator. An unescaped SEMICOLON character may be a field separator, depending on the property in which it appears.
-Furthermore, some fields of compound properties may contain a list of +
Furthermore, some fields of compound properties may contain a list of values delimited by a COMMA character. Therefore, a COMMA character in one of a field’s values MUST be escaped with a BACKSLASH character, even for fields that don’t allow multiple values (for consistency). Compound properties allowing multiple instances MUST NOT be encoded in a single content line.
-Finally, BACKSLASH characters in values MUST be escaped with a +
Finally, BACKSLASH characters in values MUST be escaped with a BACKSLASH character. NEWLINE (U+000A) characters in values MUST be encoded by two characters: a BACKSLASH followed by either an 'n' (U+006E) or an 'N' (U+004E).
-In all other cases, escaping MUST NOT be used.
In all other cases, escaping MUST NOT be used.
Standard value types are defined below.
- value = text
/ text-list
/ date-list
/ time-list
/ date-time-list
/ date-and-or-time-list
/ timestamp-list
/ boolean
/ integer-list
/ float-list
/ URI ; from Section 3 of IETF RFC 3986
/ utc-offset
/ Language-Tag
/ iana-valuespec
; Actual value type depends on property name and VALUE parameter.
text = *TEXT-CHAR
TEXT-CHAR = "\\" / "\," / "\n" / WSP / NON-ASCII
/ %x21-2B / %x2D-5B / %x5D-7E
; Backslashes, commas, and newlines must be encoded.
component = "\\" / "\," / "\;" / "\n" / WSP / NON-ASCII
/ %x21-2B / %x2D-3A / %x3C-5B / %x5D-7E
list-component = component *("," component)
text-list = text *("," text)
date-list = date *("," date)
time-list = time *("," time)
date-time-list = date-time *("," date-time)
date-and-or-time-list = date-and-or-time *("," date-and-or-time)
timestamp-list = timestamp *("," timestamp)
integer-list = integer *("," integer)
float-list = float *("," float)
boolean = "TRUE" / "FALSE"
integer = [sign] 1*DIGIT
float = [sign] 1*DIGIT ["." 1*DIGIT]
sign = "+" / "-"
year = 4DIGIT ; 0000-9999
month = 2DIGIT ; 01-12
day = 2DIGIT ; 01-28/29/30/31 depending on month and leap year
hour = 2DIGIT ; 00-23
minute = 2DIGIT ; 00-59
second = 2DIGIT ; 00-58/59/60 depending on leap second
zone = utc-designator / utc-offset
utc-designator = %x5A ; uppercase "Z"
date = year [month day]
/ year "-" month
/ "--" month [day]
/ "--" "-" day
date-noreduc = year month day
/ "--" month day
/ "--" "-" day
date-complete = year month day
time = hour [minute [second]] [zone]
/ "-" minute [second] [zone]
/ "-" "-" second [zone]
time-notrunc = hour [minute [second]] [zone]
time-complete = hour minute second [zone]
time-designator = %x54 ; uppercase "T"
date-time = date-noreduc time-designator time-notrunc
timestamp = date-complete time-designator time-complete
date-and-or-time = date-time / date / time-designator time
utc-offset = sign hour [minute]
Language-Tag = <Language-Tag, defined in IETF RFC 5646, Section 2.1>
iana-valuespec = <value-spec, see Section 12>
; a publicly defined valuetype format, registered
; with IANA, as defined in Section 12 of this
; document.
"text": The "text" value type should be used to identify values that +
Standard value types are defined below.
+ value = text
/ text-list
/ date-list
/ time-list
/ date-time-list
/ date-and-or-time-list
/ timestamp-list
/ boolean
/ integer-list
/ float-list
/ URI ; from Section 3 of IETF RFC 3986
/ utc-offset
/ Language-Tag
/ iana-valuespec
; Actual value type depends on property name and VALUE parameter.
text = *TEXT-CHAR
TEXT-CHAR = "\\" / "\," / "\n" / WSP / NON-ASCII
/ %x21-2B / %x2D-5B / %x5D-7E
; Backslashes, commas, and newlines must be encoded.
component = "\\" / "\," / "\;" / "\n" / WSP / NON-ASCII
/ %x21-2B / %x2D-3A / %x3C-5B / %x5D-7E
list-component = component *("," component)
text-list = text *("," text)
date-list = date *("," date)
time-list = time *("," time)
date-time-list = date-time *("," date-time)
date-and-or-time-list = date-and-or-time *("," date-and-or-time)
timestamp-list = timestamp *("," timestamp)
integer-list = integer *("," integer)
float-list = float *("," float)
boolean = "TRUE" / "FALSE"
integer = [sign] 1*DIGIT
float = [sign] 1*DIGIT ["." 1*DIGIT]
sign = "+" / "-"
year = 4DIGIT ; 0000-9999
month = 2DIGIT ; 01-12
day = 2DIGIT ; 01-28/29/30/31 depending on month and leap year
hour = 2DIGIT ; 00-23
minute = 2DIGIT ; 00-59
second = 2DIGIT ; 00-58/59/60 depending on leap second
zone = utc-designator / utc-offset
utc-designator = %x5A ; uppercase "Z"
date = year [month day]
/ year "-" month
/ "--" month [day]
/ "--" "-" day
date-noreduc = year month day
/ "--" month day
/ "--" "-" day
date-complete = year month day
time = hour [minute [second]] [zone]
/ "-" minute [second] [zone]
/ "-" "-" second [zone]
time-notrunc = hour [minute [second]] [zone]
time-complete = hour minute second [zone]
time-designator = %x54 ; uppercase "T"
date-time = date-noreduc time-designator time-notrunc
timestamp = date-complete time-designator time-complete
date-and-or-time = date-time / date / time-designator time
utc-offset = sign hour [minute]
Language-Tag = <Language-Tag, defined in IETF RFC 5646, Section 2.1>
iana-valuespec = <value-spec, see Section 12>
; a publicly defined valuetype format, registered
; with IANA, as defined in Section 12 of this
; document.
"text": The "text" value type should be used to identify values that contain human-readable text. As for the language, it is controlled by the LANGUAGE property parameter defined in Clause 6.2.
-Examples for "text":
-Examples for "text":
+ this is a text value
this is one value,this is another
this is a single value\, with a comma encoded
A formatted text line break in a text value type MUST be represented +
A formatted text line break in a text value type MUST be represented as the character sequence backslash (U+005C) followed by a Latin small letter n (U+006E) or a Latin capital letter N (U+004E), that is, "\n" or "\N".
-For example, a multiple line NOTE value of:
-For example, a multiple line NOTE value of:
+ Mythical Manager
Hyjinx Software Division
BabsCo, Inc.
could be represented as:
-could be represented as:
+ NOTE:Mythical Manager\nHyjinx Software Division\n
BabsCo\, Inc.\n
demonstrating the \n literal formatted line break technique, the +
demonstrating the \n literal formatted line break technique, the CRLF-followed-by-space line folding technique, and the backslash escape technique.
"uri": The "uri" value type should be used to identify values that +
"uri": The "uri" value type should be used to identify values that are referenced by a Uniform Resource Identifier (URI) instead of encoded in-line. These value references might be used if the value is too large, or otherwise undesirable to include directly. The format for the URI is as defined in RFC 3986, Section 3. Note that the value of a property of type "uri" is what the URI points to, not the URI itself.
-Examples for "uri":
-Examples for "uri":
+ http://www.example.com/my/picture.jpg
ldap://ldap.example.com/cn=babs%20jensen
"date", "time", "date-time", "date-and-or-time", and "timestamp": +
"date", "time", "date-time", "date-and-or-time", and "timestamp": Each of these value types is based on the definitions in ISO 8601:2004. Multiple such values can be specified using the comma-separated notation.
-Only the basic format is supported.
A calendar date as specified in ISO 8601:2004, Clause 4.1.2].
-Reduced accuracy, as specified in ISO 8601:2004, Clause 4.1.2.3 a) +
Only the basic format is supported.
A calendar date as specified in ISO 8601:2004, Clause 4.1.2].
+Reduced accuracy, as specified in ISO 8601:2004, Clause 4.1.2.3 a) and b), but not c), is permitted.
-Expanded representation, as specified in ISO 8601:2004, Clause 4.1.4, is forbidden.
-Truncated representation, as specified in ISO 8601:2004, Clause 5.2.1.3 d), e), and f), is permitted.
-Examples for "date":
-Expanded representation, as specified in ISO 8601:2004, Clause 4.1.4, is forbidden.
+Truncated representation, as specified in ISO 8601:2004, Clause 5.2.1.3 d), e), and f), is permitted.
+Examples for "date":
+ 19850412
1985-04
1985
@@ -1218,20 +1218,20 @@ 5. Property Value Data Types
Note the use of YYYY-MM in the second example above. YYYYMM is +
Note the use of YYYY-MM in the second example above. YYYYMM is disallowed to prevent confusion with YYMMDD. Note also that YYYY-MM-DD is disallowed since we are using the basic format instead of the extended format.
A time of day as specified in ISO 8601:2004, Clause 4.2.
-Reduced accuracy, as specified in ISO 8601:2004, Clause 4.2.2.3, +
A time of day as specified in ISO 8601:2004, Clause 4.2.
+Reduced accuracy, as specified in ISO 8601:2004, Clause 4.2.2.3, is permitted.
-Representation with decimal fraction, as specified in +
Representation with decimal fraction, as specified in ISO 8601:2004, Clause 4.2.2.4, is forbidden.
-The midnight hour is always represented by 00, never 24 (see +
The midnight hour is always represented by 00, never 24 (see ISO 8601:2004, Clause 4.2.3).
-Truncated representation, as specified in ISO 8601:2000, Clause 5.3.1.4 a), b), and c), is permitted.
-Examples for "time":
-Truncated representation, as specified in ISO 8601:2000, Clause 5.3.1.4 a), b), and c), is permitted.
+Examples for "time":
+ 102200
1022
10
@@ -1240,18 +1240,18 @@ 5. Property Value Data Types
102200Z
102200-0800
A date and time of day combination as specified in ISO 8601:2004, Clause 4.3.
-Truncation of the date part, as specified in ISO 8601:2000, Clause 5.4.2 c), is permitted.
-Examples for "date-time":
-A date and time of day combination as specified in ISO 8601:2004, Clause 4.3.
+Truncation of the date part, as specified in ISO 8601:2000, Clause 5.4.2 c), is permitted.
+Examples for "date-time":
+ 19961022T140000
--1022T1400
---22T14
Either a DATE-TIME, a DATE, or a TIME value. To allow unambiguous +
Either a DATE-TIME, a DATE, or a TIME value. To allow unambiguous interpretation, a stand-alone TIME value is always preceded by a "T".
-Examples for "date-and-or-time":
-Examples for "date-and-or-time":
+ 19961022T140000
--1022T1400
---22T14
@@ -1268,53 +1268,53 @@ 5. Property Value Data Types
T102200Z
T102200-0800
A complete date and time of day combination as specified in +
A complete date and time of day combination as specified in ISO 8601:2004, Clause 4.3.2.
-Examples for "timestamp":
-Examples for "timestamp":
+ 19961022T140000
19961022T140000Z
19961022T140000-05
19961022T140000-0500
"boolean": The "boolean" value type is used to express boolean +
"boolean": The "boolean" value type is used to express boolean values. These values are case-insensitive.
-Examples:
Examples:
TRUE
false
True
"integer": The "integer" value type is used to express signed +
"integer": The "integer" value type is used to express signed integers in decimal format. If sign is not specified, the value is assumed positive "+". Multiple "integer" values can be specified using the comma-separated notation. The maximum value is 9223372036854775807, and the minimum value is -9223372036854775808. These limits correspond to a signed 64-bit integer using two’s- complement arithmetic.
-Examples:
Examples:
1234567890
-1234556790
+1234556790,432109876
"float": The "float" value type is used to express real numbers. If +
"float": The "float" value type is used to express real numbers. If sign is not specified, the value is assumed positive "+". Multiple "float" values can be specified using the comma-separated notation. Implementations MUST support a precision equal or better than that of the IEEE "binary64" format IEEE 754.
-Note: Scientific notation is disallowed. Implementers wishing to +
Note: Scientific notation is disallowed. Implementers wishing to use their favorite language’s %f formatting should be careful.
-Examples:
Examples:
20.30
1000000.0000001
1.333,3.14
"utc-offset": The "utc-offset" value type specifies that the property +
"utc-offset": The "utc-offset" value type specifies that the property value is a signed offset from UTC. This value type can be specified in the TZ property.
-The value type is an offset from Coordinated Universal Time (UTC). +
The value type is an offset from Coordinated Universal Time (UTC). It is specified as a positive or negative difference in units of hours and minutes (e.g., +hhmm). The time is specified as a 24-hour clock. Hour values are from 00 to 23, and minute values are from 00 @@ -1323,36 +1323,36 @@
A property can have attributes associated with it. These "property +
A property can have attributes associated with it. These "property parameters" contain meta-information about the property or the property value. In some cases, the property parameter can be multi- valued in which case the property parameter value elements are separated by a COMMA (U+002C).
-Property parameter value elements that contain the COLON (U+003A), +
Property parameter value elements that contain the COLON (U+003A), SEMICOLON (U+003B), or COMMA (U+002C) character separators MUST be specified as quoted-string text values. Property parameter values MUST NOT contain the DQUOTE (U+0022) character. The DQUOTE character is used as a delimiter for parameter values that contain restricted characters or URI text.
-Applications MUST ignore x-param and iana-param values they don’t +
Applications MUST ignore x-param and iana-param values they don’t recognize.
The LANGUAGE property parameter is used to identify data in multiple +
The LANGUAGE property parameter is used to identify data in multiple languages. There is no concept of "default" language, except as specified by any "Content-Language" MIME header parameter that is present RFC 3282. The value of the LANGUAGE property parameter is a language tag as defined in RFC 5646, Section 2.
-Examples:
Examples:
ROLE;LANGUAGE=tr:hoca
ABNF:
language-param = "LANGUAGE=" Language-Tag
; Language-Tag is defined in section 2.1 of IETF RFC 5646
The VALUE parameter is OPTIONAL, used to identify the value type +
ABNF:
language-param = "LANGUAGE=" Language-Tag
; Language-Tag is defined in section 2.1 of IETF RFC 5646
The VALUE parameter is OPTIONAL, used to identify the value type (data type) and format of the value. The use of these predefined formats is encouraged even if the value parameter is not explicitly used. By defining a standard set of value types and their formats, @@ -1360,93 +1360,93 @@
ABNF:
value-param = "VALUE=" value-type
value-type = "text"
/ "uri"
/ "date"
/ "time"
/ "date-time"
/ "date-and-or-time"
/ "timestamp"
/ "boolean"
/ "integer"
/ "float"
/ "utc-offset"
/ "language-tag"
/ iana-token ; registered as described in section 12
/ x-name
The PREF parameter is OPTIONAL and is used to indicate that the +
ABNF:
value-param = "VALUE=" value-type
value-type = "text"
/ "uri"
/ "date"
/ "time"
/ "date-time"
/ "date-and-or-time"
/ "timestamp"
/ "boolean"
/ "integer"
/ "float"
/ "utc-offset"
/ "language-tag"
/ iana-token ; registered as described in section 12
/ x-name
The PREF parameter is OPTIONAL and is used to indicate that the corresponding instance of a property is preferred by the vCard author. Its value MUST be an integer between 1 and 100 that quantifies the level of preference. Lower values correspond to a higher level of preference, with 1 being most preferred.
-When the parameter is absent, the default MUST be to interpret the +
When the parameter is absent, the default MUST be to interpret the property instance as being least preferred.
-Note that the value of this parameter is to be interpreted only in +
Note that the value of this parameter is to be interpreted only in relation to values assigned to other instances of the same property in the same vCard. A given value, or the absence of a value, MUST NOT be interpreted on its own.
-This parameter MAY be applied to any property that allows multiple +
This parameter MAY be applied to any property that allows multiple instances.
-ABNF:
pref-param = "PREF=" (1*2DIGIT / "100")
; An integer between 1 and 100.
The ALTID parameter is used to "tag" property instances as being +
ABNF:
pref-param = "PREF=" (1*2DIGIT / "100")
; An integer between 1 and 100.
The ALTID parameter is used to "tag" property instances as being alternative representations of the same logical property. For example, translations of a property in multiple languages generates multiple property instances having different LANGUAGE (Clause 6.2) parameter that are tagged with the same ALTID value.
-This parameter’s value is treated as an opaque string. Its sole +
This parameter’s value is treated as an opaque string. Its sole purpose is to be compared for equality against other ALTID parameter values.
-Two property instances are considered alternative representations of +
Two property instances are considered alternative representations of the same logical property if and only if their names as well as the value of their ALTID parameters are identical. Property instances without the ALTID parameter MUST NOT be considered an alternative representation of any other property instance. Values for the ALTID parameter are not globally unique: they MAY be reused for different property names.
-Property instances having the same ALTID parameter value count as 1 +
Property instances having the same ALTID parameter value count as 1 toward cardinality. Therefore, since N (Clause 7.3.3) has cardinality *1 and TITLE (Clause 7.7.2) has cardinality *, these three examples would be legal:
-N;ALTID=1;LANGUAGE=jp:<U+5C71><U+7530>;<U+592A><U+90CE>;;; N;ALTID=1;LANGUAGE=en:Yamada;Taro;;; (<U+XXXX> denotes a UTF8-encoded Unicode character.)
TITLE;ALTID=1;LANGUAGE=fr:Patron TITLE;ALTID=1;LANGUAGE=en:Boss
TITLE;ALTID=1;LANGUAGE=fr:Patron TITLE;ALTID=1;LANGUAGE=en:Boss TITLE;ALTID=2;LANGUAGE=en:Chief vCard Evangelist
while this one would not:
-while this one would not:
+N;ALTID=1;LANGUAGE=jp:<U+5C71><U+7530>;<U+592A><U+90CE>;;; N:Yamada;Taro;;; (Two instances of the N property.)
and these three would be legal but questionable:
-and these three would be legal but questionable:
+TITLE;ALTID=1;LANGUAGE=fr:Patron TITLE;ALTID=2;LANGUAGE=en:Boss (Should probably have the same ALTID value.)
TITLE;ALTID=1;LANGUAGE=fr:Patron TITLE:LANGUAGE=en:Boss (Second line should probably have ALTID=1.)
N;ALTID=1;LANGUAGE=jp:<U+5C71><U+7530>;<U+592A><U+90CE>;;;
N;ALTID=1;LANGUAGE=en:Yamada;Taro;;;
N;ALTID=1;LANGUAGE=en:Smith;John;;;
(The last line should probably have ALTID=2. But that would be
illegal because N has cardinality *1.)
The ALTID property MAY also be used in may contexts other than with +
The ALTID property MAY also be used in may contexts other than with the LANGUAGE parameter. Here’s an example with two representations of the same photo in different file formats:
-PHOTO;ALTID=1:data:image/jpeg;base64,... PHOTO;ALTID=1;data:image/jp2;base64,...
ABNF:
altid-param = "ALTID=" param-value
The PID parameter is used to identify a specific property among +
ABNF:
altid-param = "ALTID=" param-value
The PID parameter is used to identify a specific property among multiple instances. It plays a role analogous to the UID property (Clause 7.8.7) on a per-property instead of per-vCard basis. It MAY appear more than once in a given property. It MUST NOT appear on @@ -1455,9 +1455,9 @@
ABNF:
pid-param = "PID=" pid-value *("," pid-value)
pid-value = 1*DIGIT ["." 1*DIGIT]
The TYPE parameter has multiple, different uses. In general, it is a +
ABNF:
pid-param = "PID=" pid-value *("," pid-value)
pid-value = 1*DIGIT ["." 1*DIGIT]
The TYPE parameter has multiple, different uses. In general, it is a way of specifying class characteristics of the associated property. Most of the time, its value is a comma-separated subset of a predefined enumeration. In this document, the following properties @@ -1466,16 +1466,16 @@
The "work" and "home" values act like tags. The "work" value implies +
The "work" and "home" values act like tags. The "work" value implies that the property is related to an individual’s work place, while the "home" value implies that the property is related to an individual’s personal life. When neither "work" nor "home" is present, it is implied that the property is related to both an individual’s work place and personal life in the case that the KIND property’s value is "individual", or to none in other cases.
-ABNF:
type-param = "TYPE=" type-value *("," type-value)
type-value = "work" / "home" / type-param-tel
/ type-param-related / iana-token / x-name
; This is further defined in individual property sections.
The MEDIATYPE parameter is used with properties whose value is a URI. +
ABNF:
type-param = "TYPE=" type-value *("," type-value)
type-value = "work" / "home" / type-param-tel
/ type-param-related / iana-token / x-name
; This is further defined in individual property sections.
The MEDIATYPE parameter is used with properties whose value is a URI. Its use is OPTIONAL. It provides a hint to the vCard consumer application about the media type RFC 2046 of the resource identified by the URI. Some URI schemes do not need this parameter. For @@ -1485,9 +1485,9 @@
ABNF:
mediatype-param = "MEDIATYPE=" mediatype
mediatype = type-name "/" subtype-name *( ";" attribute "=" value )
; "attribute" and "value" are from IETF RFC 2045
; "type-name" and "subtype-name" are from [RFC4288]
The CALSCALE parameter is identical to the CALSCALE property in +
ABNF:
mediatype-param = "MEDIATYPE=" mediatype
mediatype = type-name "/" subtype-name *( ";" attribute "=" value )
; "attribute" and "value" are from IETF RFC 2045
; "type-name" and "subtype-name" are from [RFC4288]
The CALSCALE parameter is identical to the CALSCALE property in iCalendar (see RFC 5545, Section 3.7.1). It is used to define the calendar system in which a date or date-time value is expressed. The only value specified by iCalendar is "gregorian", which stands for @@ -1496,47 +1496,47 @@
ABNF:
calscale-param = "CALSCALE=" calscale-value
calscale-value = "gregorian" / iana-token / x-name
The "sort-as" parameter is used to specify the string to be used for +
ABNF:
calscale-param = "CALSCALE=" calscale-value
calscale-value = "gregorian" / iana-token / x-name
The "sort-as" parameter is used to specify the string to be used for national-language-specific sorting. Without this information, sorting algorithms could incorrectly sort this vCard within a sequence of sorted vCards. When this property is present in a vCard, then the given strings are used for sorting the vCard.
-This parameter’s value is a comma-separated list that MUST have as +
This parameter’s value is a comma-separated list that MUST have as many or fewer elements as the corresponding property value has components. This parameter’s value is case-sensitive.
-ABNF:
sort-as-param = "SORT-AS=" sort-as-value
sort-as-value = param-value *("," param-value)
Examples: For the case of surname and given name sorting, the +
ABNF:
sort-as-param = "SORT-AS=" sort-as-value
sort-as-value = param-value *("," param-value)
Examples: For the case of surname and given name sorting, the following examples define common sort string usage with the N property.
- FN:Rene van der Harten
N;SORT-AS="Harten,Rene":van der Harten;Rene,J.;Sir;R.D.O.N.
FN:Robert Pau Shou Chang
N;SORT-AS="Pau Shou Chang,Robert":Shou Chang;Robert,Pau;;
FN:Osamu Koura
N;SORT-AS="Koura,Osamu":Koura;Osamu;;
FN:Oscar del Pozo
N;SORT-AS="Pozo,Oscar":del Pozo Triscon;Oscar;;
FN:Chistine d'Aboville
N;SORT-AS="Aboville,Christine":d'Aboville;Christine;;
FN:H. James de Mann
N;SORT-AS="Mann,James":de Mann;Henry,James;;
If sorted by surname, the results would be:
-If sorted by surname, the results would be:
+ Christine d'Aboville
Rene van der Harten
Osamu Koura
@@ -1544,8 +1544,8 @@ 6. Property Parameters
Robert Pau Shou Chang
Oscar del Pozo
If sorted by given name, the results would be:
-If sorted by given name, the results would be:
+ Christine d'Aboville
H. James de Mann
Osamu Koura
@@ -1553,36 +1553,36 @@ 6. Property Parameters
Rene van der Harten
Robert Pau Shou Chang
The GEO parameter can be used to indicate global positioning +
The GEO parameter can be used to indicate global positioning information that is specific to an address. Its value is the same as that of the GEO property (see Clause 7.6.3).
-ABNF:
geo-parameter = "GEO=" DQUOTE URI DQUOTE
The TZ parameter can be used to indicate time zone information that +
ABNF:
geo-parameter = "GEO=" DQUOTE URI DQUOTE
The TZ parameter can be used to indicate time zone information that is specific to an address. Its value is the same as that of the TZ property.
-ABNF:
tz-parameter = "TZ=" (param-value / DQUOTE URI DQUOTE)
ABNF:
tz-parameter = "TZ=" (param-value / DQUOTE URI DQUOTE)
What follows is an enumeration of the standard vCard properties.
+What follows is an enumeration of the standard vCard properties.
Purpose:
To denote the beginning of a syntactic entity within a +
Purpose:
To denote the beginning of a syntactic entity within a text/vcard content-type.
Value type:
text
+text
Cardinality:
1
+1
Special notes:
The content entity MUST begin with the BEGIN property +
The content entity MUST begin with the BEGIN property with a value of "VCARD". The value is case-insensitive.
-The BEGIN property is used in conjunction with the END property to +
The BEGIN property is used in conjunction with the END property to delimit an entity containing a related set of properties within a text/vcard content-type. This construct can be used instead of including multiple vCards as body parts inside of a multipart/ @@ -1591,24 +1591,24 @@
ABNF:
BEGIN-param = 0" " ; no parameter allowed
BEGIN-value = "VCARD"
BEGIN-param = 0" " ; no parameter allowed
BEGIN-value = "VCARD"
Example:
BEGIN:VCARD
Purpose:
To denote the end of a syntactic entity within a text/vcard +
Purpose:
To denote the end of a syntactic entity within a text/vcard content-type.
Value type:
text
+text
Cardinality:
1
+1
Special notes:
The content entity MUST end with the END type with a +
The content entity MUST end with the END type with a value of "VCARD". The value is case-insensitive.
-The END property is used in conjunction with the BEGIN property to +
The END property is used in conjunction with the BEGIN property to delimit an entity containing a related set of properties within a text/vcard content-type. This construct can be used instead of or in addition to wrapping separate sets of information inside @@ -1617,22 +1617,22 @@
ABNF:
END-param = 0" " ; no parameter allowed
END-value = "VCARD"
END-param = 0" " ; no parameter allowed
END-value = "VCARD"
Example:
END:VCARD
Purpose:
To identify the source of directory information contained +
Purpose:
To identify the source of directory information contained in the content type.
Value type:
uri
+uri
Cardinality:
*
+*
Special notes:
The SOURCE property is used to provide the means by +
The SOURCE property is used to provide the means by which applications knowledgable in the given directory service protocol can obtain additional or more up-to-date information from the directory service. It contains a URI as defined in RFC 3986 @@ -1642,28 +1642,28 @@
ABNF:
SOURCE-param = "VALUE=uri" / pid-param / pref-param / altid-param
/ mediatype-param / any-param
SOURCE-value = URI
Examples:
SOURCE-param = "VALUE=uri" / pid-param / pref-param / altid-param
/ mediatype-param / any-param
SOURCE-value = URI
Examples:
SOURCE:ldap://ldap.example.com/cn=Babs%20Jensen,%20o=Babsco,%20c=US
SOURCE:http://directory.example.com/addressbooks/jdoe/
Jean%20Dupont.vcf
Purpose:
To specify the kind of object the vCard represents.
+Purpose:
To specify the kind of object the vCard represents.
Value type:
A single text value.
+A single text value.
Cardinality:
*1
+*1
Special notes:
The value may be one of the following:
+The value may be one of the following:
"individual"
for a vCard representing a single person or entity. +
for a vCard representing a single person or entity. This is the default kind of vCard.
"group"
for a vCard representing a group of persons or entities. +
for a vCard representing a group of persons or entities. The group’s member entities can be other vCards or other types of entities, such as email addresses or web sites. A group vCard will usually contain MEMBER properties to specify the @@ -1671,46 +1671,46 @@
All properties in a group vCard apply to the group as a whole, +
All properties in a group vCard apply to the group as a whole, and not to any particular MEMBER. For example, an EMAIL property might specify the address of a mailing list associated with the group, and an IMPP property might refer to a group chat room.
"org"
for a vCard representing an organization. An organization +
for a vCard representing an organization. An organization vCard will not (in fact, MUST NOT) contain MEMBER properties, and so these are something of a cross between "individual" and "group". An organization is a single entity, but not a person. It might represent a business or government, a department or division within a business or government, a club, an association, or the like.
-All properties in an organization vCard apply to the +
All properties in an organization vCard apply to the organization as a whole, as is the case with a group vCard. For example, an EMAIL property might specify the address of a contact point for the organization.
"location"
for a named geographical place. A location vCard will +
for a named geographical place. A location vCard will usually contain a GEO property, but it is not required to. A location vCard without a GEO property can be considered an abstract location, or one whose definition is known empirically (perhaps "New England" or "The Seashore").
-All properties in a location vCard apply to the location +
All properties in a location vCard apply to the location itself, and not with any entity that might exist at that location. For example, in a vCard for an office building, an ADR property might give the mailing address for the building, and a TEL property might specify the telephone number of the receptionist.
An x-name.
vCards MAY include private or experimental values for +
vCards MAY include private or experimental values for KIND. Remember that x-name values are not intended for general use and are unlikely to interoperate.
An iana-token.
Additional values may be registered with IANA (see +
Additional values may be registered with IANA (see Clause 11.3.5). A new value’s specification document MUST specify which properties make sense for that new kind of vCard and which do not.
Implementations MUST support the specific string values defined +
Implementations MUST support the specific string values defined above. If this property is absent, "individual" MUST be assumed as the default. If this property is present but the implementation does not understand its value (the value is an @@ -1719,7 +1719,7 @@
Clients often need to visually distinguish contacts based on what +
Clients often need to visually distinguish contacts based on what they represent, and the KIND property provides a direct way for them to do so. For example, when displaying contacts in a list, an icon could be displayed next to each one, using distinctive @@ -1729,21 +1729,21 @@
Some clients might also make functional distinctions among the +
Some clients might also make functional distinctions among the kinds, ignoring "location" vCards for some purposes and considering only "location" vCards for others.
-When designing those sorts of visual and functional distinctions, +
When designing those sorts of visual and functional distinctions, client implementations have to decide how to fit unsupported kinds into the scheme. What icon is used for them? The one for "individual"? A unique one, such as an icon of a question mark? Which tab do they go into? It is beyond the scope of this specification to answer these questions, but these are things implementers need to consider.
-ABNF:
KIND-param = "VALUE=text" / any-param
KIND-value = "individual" / "group" / "org" / "location"
/ iana-token / x-name
Example:
This represents someone named Jane Doe working in the marketing +
ABNF:
KIND-param = "VALUE=text" / any-param
KIND-value = "individual" / "group" / "org" / "location"
/ iana-token / x-name
Example:
This represents someone named Jane Doe working in the marketing department of the North American division of ABC Inc.
- BEGIN:VCARD
VERSION:4.0
KIND:individual
@@ -1751,9 +1751,9 @@ 7. vCard Properties
ORG:ABC\, Inc.;North American Division;Marketing
END:VCARD
This represents the department itself, commonly known as ABC +
This represents the department itself, commonly known as ABC Marketing.
- BEGIN:VCARD
VERSION:4.0
KIND:org
@@ -1763,68 +1763,68 @@ 7. vCard Properties
Purpose:
To include extended XML-encoded vCard data in a plain +
Purpose:
To include extended XML-encoded vCard data in a plain vCard.
Value type:
A single text value.
+A single text value.
Cardinality:
*
-Special notes:
The content of this property is a single XML 1.0 +
*
+Special notes:
The content of this property is a single XML 1.0 W3C REC-xml-20081126 element whose namespace MUST be explicitly specified using the xmlns attribute and MUST NOT be the vCard 4 namespace ("urn:ietf:params:xml:ns:vcard-4.0"). (This implies that it cannot duplicate a standard vCard property.) The element is to be interpreted as if it was contained in a <vcard> element, -as defined in RFC 6351.
The fragment is subject to normal line folding and escaping, i.e., +as defined in RFC 6351.
The fragment is subject to normal line folding and escaping, i.e., replace all backslashes with "\\", then replace all newlines with "\n", then fold long lines.
-Support for this property is OPTIONAL, but implementations of this +
Support for this property is OPTIONAL, but implementations of this specification MUST preserve instances of this property when propagating vCards.
-See RFC 6351 for more information on the intended use of this +
See RFC 6351 for more information on the intended use of this property.
ABNF:
XML-param = "VALUE=text" / altid-param
XML-value = text
XML-param = "VALUE=text" / altid-param
XML-value = text
These types are used to capture information associated with the +
These types are used to capture information associated with the identification and naming of the entity associated with the vCard.
Purpose:
To specify the formatted text corresponding to the name of +
Purpose:
To specify the formatted text corresponding to the name of the object the vCard represents.
Value type:
A single text value.
+A single text value.
Cardinality:
1*
+1*
Special notes:
This property is based on the semantics of the X.520 +
This property is based on the semantics of the X.520 Common Name attribute CCITT Recommendation X520. The property MUST be present in the vCard object.
ABNF:
FN-param = "VALUE=text" / type-param / language-param / altid-param
/ pid-param / pref-param / any-param
FN-value = text
FN-param = "VALUE=text" / type-param / language-param / altid-param
/ pid-param / pref-param / any-param
FN-value = text
Example:
FN:Mr. John Q. Public\, Esq.
Purpose:
To specify the components of the name of the object the +
Purpose:
To specify the components of the name of the object the vCard represents.
Value type:
A single structured text value. Each component can have +
A single structured text value. Each component can have multiple values.
Cardinality:
*1
+*1
Special note:
The structured property value corresponds, in +
The structured property value corresponds, in sequence, to the Family Names (also known as surnames), Given Names, Additional Names, Honorific Prefixes, and Honorific Suffixes. The text components are separated by the SEMICOLON @@ -1834,11 +1834,11 @@
The SORT-AS parameter MAY be applied to this property.
+The SORT-AS parameter MAY be applied to this property.
ABNF:
N-param = "VALUE=text" / sort-as-param / language-param
/ altid-param / any-param
N-value = list-component 4(";" list-component)
N-param = "VALUE=text" / sort-as-param / language-param
/ altid-param / any-param
N-value = list-component 4(";" list-component)
Examples:
N:Public;John;Quinlan;Mr.;Esq.
N:Stevenson;John;Philip,Paul;Dr.;Jr.,M.D.,A.C.P.
@@ -1847,23 +1847,23 @@ Purpose:
To specify the text corresponding to the nickname of the +
Purpose:
To specify the text corresponding to the nickname of the object the vCard represents.
Value type:
One or more text values separated by a COMMA character +
One or more text values separated by a COMMA character (U+002C).
Cardinality:
*
+*
Special note:
The nickname is the descriptive name given instead of +
The nickname is the descriptive name given instead of or in addition to the one belonging to the object the vCard represents. It can also be used to specify a familiar form of a proper name specified by the FN or N properties.
ABNF:
NICKNAME-param = "VALUE=text" / type-param / language-param
/ altid-param / pid-param / pref-param / any-param
NICKNAME-value = text-list
NICKNAME-param = "VALUE=text" / type-param / language-param
/ altid-param / pid-param / pref-param / any-param
NICKNAME-value = text-list
Examples:
NICKNAME:Robbie
NICKNAME:Jim,Jimmie
@@ -1874,17 +1874,17 @@ 7. vCard Properties
Purpose:
To specify an image or photograph information that +
Purpose:
To specify an image or photograph information that annotates some aspect of the object the vCard represents.
Value type:
A single URI.
+A single URI.
Cardinality:
*
+*
ABNF:
PHOTO-param = "VALUE=uri" / altid-param / type-param
/ mediatype-param / pref-param / pid-param / any-param
PHOTO-value = URI
PHOTO-param = "VALUE=uri" / altid-param / type-param
/ mediatype-param / pref-param / pid-param / any-param
PHOTO-value = URI
Examples:
PHOTO:http://www.example.com/pub/photos/jqpublic.gif
PHOTO:data:image/jpeg;base64,MIICajCCAdOgAwIBAgICBEUwDQYJKoZIhv
@@ -1896,18 +1896,18 @@ 7. vCard Properties
Purpose:
To specify the birth date of the object the vCard +
Purpose:
To specify the birth date of the object the vCard represents.
Value type:
The default is a single date-and-or-time value. It can +
The default is a single date-and-or-time value. It can also be reset to a single text value.
Cardinality:
*1
+*1
ABNF:
BDAY-param = BDAY-param-date / BDAY-param-text
BDAY-value = date-and-or-time / text
; Value and parameter MUST match.
BDAY-param-date = "VALUE=date-and-or-time"
BDAY-param-text = "VALUE=text" / language-param
BDAY-param =/ altid-param / calscale-param / any-param
; calscale-param can only be present when BDAY-value is
; date-and-or-time and actually contains a date or date-time.
BDAY-param = BDAY-param-date / BDAY-param-text
BDAY-value = date-and-or-time / text
; Value and parameter MUST match.
BDAY-param-date = "VALUE=date-and-or-time"
BDAY-param-text = "VALUE=text" / language-param
BDAY-param =/ altid-param / calscale-param / any-param
; calscale-param can only be present when BDAY-value is
; date-and-or-time and actually contains a date or date-time.
Examples:
BDAY:19960415
BDAY:--0415
BDAY;19531015T231000Z
@@ -1917,46 +1917,46 @@ 7. vCard Properties
Purpose:
The date of marriage, or equivalent, of the object the +
Purpose:
The date of marriage, or equivalent, of the object the vCard represents.
Value type:
The default is a single date-and-or-time value. It can +
The default is a single date-and-or-time value. It can also be reset to a single text value.
Cardinality:
*1
+*1
ABNF:
ANNIVERSARY-param = "VALUE=" ("date-and-or-time" / "text")
ANNIVERSARY-value = date-and-or-time / text
; Value and parameter MUST match.
ANNIVERSARY-param =/ altid-param / calscale-param / any-param
; calscale-param can only be present when ANNIVERSARY-value is
; date-and-or-time and actually contains a date or date-time.
ANNIVERSARY-param = "VALUE=" ("date-and-or-time" / "text")
ANNIVERSARY-value = date-and-or-time / text
; Value and parameter MUST match.
ANNIVERSARY-param =/ altid-param / calscale-param / any-param
; calscale-param can only be present when ANNIVERSARY-value is
; date-and-or-time and actually contains a date or date-time.
Examples:
ANNIVERSARY:19960415
Purpose:
To specify the components of the sex and gender identity of +
Purpose:
To specify the components of the sex and gender identity of the object the vCard represents.
Value type:
A single structured value with two components. Each +
A single structured value with two components. Each component has a single text value.
Cardinality:
*1
+*1
Special notes:
The components correspond, in sequence, to the sex +
The components correspond, in sequence, to the sex (biological), and gender identity. Each component is optional.
-Sex component:
A single letter. M stands for "male", F stands +
Sex component:
A single letter. M stands for "male", F stands for "female", O stands for "other", N stands for "none or not applicable", U stands for "unknown".
Gender identity component:
Free-form text.
+Free-form text.
ABNF:
GENDER-param = "VALUE=text" / any-param
GENDER-value = sex [";" text]
sex = "" / "M" / "F" / "O" / "N" / "U"
GENDER-param = "VALUE=text" / any-param
GENDER-value = sex [";" text]
sex = "" / "M" / "F" / "O" / "N" / "U"
Examples:
GENDER:M GENDER:F GENDER:M;Fellow @@ -1968,72 +1968,72 @@7. vCard Properties
These types are concerned with information related to the delivery +
These types are concerned with information related to the delivery addressing or label for the vCard object.
Purpose:
To specify the components of the delivery address for the +
Purpose:
To specify the components of the delivery address for the vCard object.
Value type:
A single structured text value, separated by the +
A single structured text value, separated by the SEMICOLON character (U+003B).
Cardinality:
*
+*
Special notes:
The structured type value consists of a sequence of +
The structured type value consists of a sequence of address components. The component values MUST be specified in their corresponding position. The structured type value corresponds, in sequence, to
-the post office box;
+the post office box;
the extended address (e.g., apartment or suite number);
+the extended address (e.g., apartment or suite number);
the street address;
+the street address;
the locality (e.g., city);
+the locality (e.g., city);
the region (e.g., state or province);
+the region (e.g., state or province);
the postal code;
+the postal code;
the country name (full name in the language specified in +
the country name (full name in the language specified in Clause 6.2).
When a component value is missing, the associated component +
When a component value is missing, the associated component separator MUST still be specified.
-Experience with vCard 3 has shown that the first two components +
Experience with vCard 3 has shown that the first two components (post office box and extended address) are plagued with many interoperability issues. To ensure maximal interoperability, their values SHOULD be empty.
-The text components are separated by the SEMICOLON character +
The text components are separated by the SEMICOLON character (U+003B). Where it makes semantic sense, individual text components can include multiple text values (e.g., a "street" component with multiple lines) separated by the COMMA character (U+002C).
-The property can include the "PREF" parameter to indicate the +
The property can include the "PREF" parameter to indicate the preferred delivery address when more than one address is specified.
-The GEO and TZ parameters MAY be used with this property.
-The property can also include a "LABEL" parameter to present a +
The GEO and TZ parameters MAY be used with this property.
+The property can also include a "LABEL" parameter to present a delivery address label for the address. Its value is a plain-text string representing the formatted address. Newlines are encoded as \n, as they are for property values.
-ABNF:
label-param = "LABEL=" param-value
ADR-param = "VALUE=text" / label-param / language-param
/ geo-parameter / tz-parameter / altid-param / pid-param
/ pref-param / type-param / any-param
ADR-value = ADR-component-pobox ";" ADR-component-ext ";"
ADR-component-street ";" ADR-component-locality ";"
ADR-component-region ";" ADR-component-code ";"
ADR-component-country
ADR-component-pobox = list-component
ADR-component-ext = list-component
ADR-component-street = list-component
ADR-component-locality = list-component
ADR-component-region = list-component
ADR-component-code = list-component
ADR-component-country = list-component
ABNF:
label-param = "LABEL=" param-value
ADR-param = "VALUE=text" / label-param / language-param
/ geo-parameter / tz-parameter / altid-param / pid-param
/ pref-param / type-param / any-param
ADR-value = ADR-component-pobox ";" ADR-component-ext ";"
ADR-component-street ";" ADR-component-locality ";"
ADR-component-region ";" ADR-component-code ";"
ADR-component-country
ADR-component-pobox = list-component
ADR-component-ext = list-component
ADR-component-street = list-component
ADR-component-locality = list-component
ADR-component-region = list-component
ADR-component-code = list-component
ADR-component-country = list-component
Example:
In this example, the post office box and the extended +
In this example, the post office box and the extended address are absent.
- ADR;GEO="geo:12.3457,78.910";LABEL="Mr. John Q. Public, Esq.\n
Mail Drop: TNE QB\n123 Main Street\nAny Town, CA 91921-1234\n
U.S.A.":;;123 Main Street;Any Town;CA;91921-1234;U.S.A.
@@ -2041,66 +2041,66 @@ These properties describe information about how to communicate with +
These properties describe information about how to communicate with the object the vCard represents.
Purpose:
To specify the telephone number for telephony communication +
Purpose:
To specify the telephone number for telephony communication with the object the vCard represents.
Value type:
By default, it is a single free-form text value (for +
By default, it is a single free-form text value (for backward compatibility with vCard 3), but it SHOULD be reset to a URI value. It is expected that the URI scheme will be "tel", as specified in RFC 3966, but other schemes MAY be used.
Cardinality:
*
-Special notes:
This property is based on the X.520 Telephone Number -attribute CCITT Recommendation X520.
The property can include the "PREF" parameter to indicate a +
*
+Special notes:
This property is based on the X.520 Telephone Number +attribute CCITT Recommendation X520.
The property can include the "PREF" parameter to indicate a preferred-use telephone number.
-The property can include the parameter "TYPE" to specify intended +
The property can include the parameter "TYPE" to specify intended use for the telephone number. The predefined values for the TYPE parameter are:
Table 2
| Value | Description |
|---|---|
| text | Indicates that the telephone number supports text messages (SMS). |
| voice | Indicates a voice telephone number. |
| fax | Indicates a facsimile telephone number. |
| cell | Indicates a cellular or mobile telephone number. |
| video | Indicates a video conferencing telephone number. |
| pager | Indicates a paging device telephone number. |
| textphone | Indicates a telecommunication device for people with hearing or speech difficulties. |
The default type is "voice". These type parameter values can be +
Table 2
| Value | Description |
|---|---|
| text | Indicates that the telephone number supports text messages (SMS). |
| voice | Indicates a voice telephone number. |
| fax | Indicates a facsimile telephone number. |
| cell | Indicates a cellular or mobile telephone number. |
| video | Indicates a video conferencing telephone number. |
| pager | Indicates a paging device telephone number. |
| textphone | Indicates a telecommunication device for people with hearing or speech difficulties. |
The default type is "voice". These type parameter values can be specified as a parameter list (e.g., TYPE=text;TYPE=voice) or as a value list (e.g., TYPE="text,voice"). The default can be overridden to another set of values by specifying one or more alternate values. For example, the default TYPE of "voice" can be reset to a VOICE and FAX telephone number by the value list TYPE="voice,fax".
-If this property’s value is a URI that can also be used for +
If this property’s value is a URI that can also be used for instant messaging, the IMPP (Clause 7.5.4) property SHOULD be used in addition to this property.
-ABNF:
TEL-param = TEL-text-param / TEL-uri-param
TEL-value = TEL-text-value / TEL-uri-value
; Value and parameter MUST match.
TEL-text-param = "VALUE=text"
TEL-text-value = text
TEL-uri-param = "VALUE=uri" / mediatype-param
TEL-uri-value = URI
TEL-param =/ type-param / pid-param / pref-param / altid-param
/ any-param
type-param-tel = "text" / "voice" / "fax" / "cell" / "video"
/ "pager" / "textphone" / iana-token / x-name
; type-param-tel MUST NOT be used with a property other than TEL.
ABNF:
TEL-param = TEL-text-param / TEL-uri-param
TEL-value = TEL-text-value / TEL-uri-value
; Value and parameter MUST match.
TEL-text-param = "VALUE=text"
TEL-text-value = text
TEL-uri-param = "VALUE=uri" / mediatype-param
TEL-uri-value = URI
TEL-param =/ type-param / pid-param / pref-param / altid-param
/ any-param
type-param-tel = "text" / "voice" / "fax" / "cell" / "video"
/ "pager" / "textphone" / iana-token / x-name
; type-param-tel MUST NOT be used with a property other than TEL.
Example:
TEL;VALUE=uri;PREF=1;TYPE="voice,home":tel:+1-555-555-5555;ext=5555 TEL;VALUE=uri;TYPE=home:tel:+33-01-23-45-67
Purpose:
To specify the electronic mail address for communication +
Purpose:
To specify the electronic mail address for communication with the object the vCard represents.
Value type:
A single text value.
+A single text value.
Cardinality:
*
+*
Special notes:
The property can include tye "PREF" parameter to +
The property can include tye "PREF" parameter to indicate a preferred-use email address when more than one is specified.
-Even though the value is free-form UTF-8 text, it is likely to be +
Even though the value is free-form UTF-8 text, it is likely to be interpreted by a Mail User Agent (MUA) as an "addr-spec", as defined in RFC 5322, Section 3.4.1. Readers should also be aware of the current work toward internationalized email addresses RFC 5335.
ABNF:
EMAIL-param = "VALUE=text" / pid-param / pref-param / type-param
/ altid-param / any-param
EMAIL-value = text
EMAIL-param = "VALUE=text" / pid-param / pref-param / type-param
/ altid-param / any-param
EMAIL-value = text
Example:
EMAIL;TYPE=work:jqpublic@xyz.example.com
EMAIL;PREF=1:jane_doe@example.com
@@ -2109,40 +2109,40 @@ Purpose:
To specify the URI for instant messaging and presence +
Purpose:
To specify the URI for instant messaging and presence protocol communications with the object the vCard represents.
Value type:
A single URI.
+A single URI.
Cardinality:
*
-Special notes:
The property may include the "PREF" parameter to +
*
+Special notes:
The property may include the "PREF" parameter to indicate that this is a preferred address and has the same -semantics as the "PREF" parameter in a TEL property.
If this property’s value is a URI that can be used for voice +semantics as the "PREF" parameter in a TEL property.
If this property’s value is a URI that can be used for voice and/or video, the TEL property (Clause 7.5.2) SHOULD be used in addition to this property.
-This property is adapted from RFC 4770, which is made obsolete by +
This property is adapted from RFC 4770, which is made obsolete by this document.
ABNF:
IMPP-param = "VALUE=uri" / pid-param / pref-param / type-param
/ mediatype-param / altid-param / any-param
IMPP-value = URI
IMPP-param = "VALUE=uri" / pid-param / pref-param / type-param
/ mediatype-param / altid-param / any-param
IMPP-value = URI
Example:
IMPP;PREF=1:xmpp:alice@example.com
Purpose:
To specify the language(s) that may be used for contacting +
Purpose:
To specify the language(s) that may be used for contacting the entity associated with the vCard.
Value type:
A single language-tag value.
+A single language-tag value.
Cardinality:
*
+*
ABNF:
LANG-param = "VALUE=language-tag" / pid-param / pref-param
/ altid-param / type-param / any-param
LANG-value = Language-Tag
LANG-param = "VALUE=language-tag" / pid-param / pref-param
/ altid-param / type-param / any-param
LANG-value = Language-Tag
Example:
LANG;TYPE=work;PREF=1:en
LANG;TYPE=work;PREF=2:fr
LANG;TYPE=home:fr
@@ -2151,34 +2151,34 @@ These properties are concerned with information associated with +
These properties are concerned with information associated with geographical positions or regions associated with the object the vCard represents.
Purpose:
To specify information related to the time zone of the +
Purpose:
To specify information related to the time zone of the object the vCard represents.
Value type:
The default is a single text value. It can also be +
The default is a single text value. It can also be reset to a single URI or utc-offset value.
Cardinality:
*
-Special notes:
It is expected that names from the public-domain +
*
+Special notes:
It is expected that names from the public-domain Olson database TZ-DB will be used, but this is not a -restriction. See also IANA TZ.
Efforts are currently being directed at creating a standard URI +restriction. See also IANA TZ.
Efforts are currently being directed at creating a standard URI scheme for expressing time zone information. Usage of such a scheme would ensure a high level of interoperability between implementations that support it.
-Note that utc-offset values SHOULD NOT be used because the UTC +
Note that utc-offset values SHOULD NOT be used because the UTC offset varies with time — not just because of the usual daylight saving time shifts that occur in may regions, but often entire regions will "re-base" their overall offset. The actual offset may be +/- 1 hour (or perhaps a little more) than the one given.
ABNF:
TZ-param = "VALUE=" ("text" / "uri" / "utc-offset")
TZ-value = text / URI / utc-offset
; Value and parameter MUST match.
TZ-param =/ altid-param / pid-param / pref-param / type-param
/ mediatype-param / any-param
TZ-param = "VALUE=" ("text" / "uri" / "utc-offset")
TZ-value = text / URI / utc-offset
; Value and parameter MUST match.
TZ-param =/ altid-param / pid-param / pref-param / type-param
/ mediatype-param / any-param
Examples:
TZ:Raleigh/North America TZ;VALUE=utc-offset:-0500 @@ -2188,80 +2188,80 @@7. vCard Properties
Purpose:
To specify information related to the global positioning of +
Purpose:
To specify information related to the global positioning of the object the vCard represents.
Value type:
A single URI.
+A single URI.
Cardinality:
*
+*
Special notes:
The "geo" URI scheme RFC 5870 is particularly well +
The "geo" URI scheme RFC 5870 is particularly well suited for this property, but other schemes MAY be used.
ABNF:
GEO-param = "VALUE=uri" / pid-param / pref-param / type-param
/ mediatype-param / altid-param / any-param
GEO-value = URI
GEO-param = "VALUE=uri" / pid-param / pref-param / type-param
/ mediatype-param / altid-param / any-param
GEO-value = URI
Example:
GEO:geo:37.386013,-122.082932
These properties are concerned with information associated with +
These properties are concerned with information associated with characteristics of the organization or organizational units of the object that the vCard represents.
Purpose:
To specify the position or job of the object the vCard +
Purpose:
To specify the position or job of the object the vCard represents.
Value type:
A single text value.
+A single text value.
Cardinality: *
-Special notes:
This property is based on the X.520 Title attribute +
Cardinality: *
+Special notes:
This property is based on the X.520 Title attribute CCITT Recommendation X520.
ABNF:
TITLE-param = "VALUE=text" / language-param / pid-param
/ pref-param / altid-param / type-param / any-param
TITLE-value = text
TITLE-param = "VALUE=text" / language-param / pid-param
/ pref-param / altid-param / type-param / any-param
TITLE-value = text
Example:
TITLE:Research Scientist
Purpose:
To specify the function or part played in a particular +
Purpose:
To specify the function or part played in a particular situation by the object the vCard represents.
Value type:
A single text value.
+A single text value.
Cardinality:
*
+*
Special notes: This property is based on the X.520 Business Category +
Special notes: This property is based on the X.520 Business Category explanatory attribute CCITT Recommendation X520. This property is included as an organizational type to avoid confusion with the semantics of the TITLE property and incorrect usage of that property when the semantics of this property is intended.
-ABNF:
ROLE-param = "VALUE=text" / language-param / pid-param / pref-param
/ type-param / altid-param / any-param
ROLE-value = text
ABNF:
ROLE-param = "VALUE=text" / language-param / pid-param / pref-param
/ type-param / altid-param / any-param
ROLE-value = text
Example:
ROLE:Project Leader
Purpose:
To specify a graphic image of a logo associated with the +
Purpose:
To specify a graphic image of a logo associated with the object the vCard represents.
Value type:
A single URI.
+A single URI.
Cardinality:
*
+*
ABNF:
LOGO-param = "VALUE=uri" / language-param / pid-param / pref-param
/ type-param / mediatype-param / altid-param / any-param
LOGO-value = URI
LOGO-param = "VALUE=uri" / language-param / pid-param / pref-param
/ type-param / mediatype-param / altid-param / any-param
LOGO-value = URI
Examples:
LOGO:http://www.example.com/pub/logos/abccorp.jpg LOGO:data:image/jpeg;base64,MIICajCCAdOgAwIBAgICBEUwDQYJKoZIhvc @@ -2273,47 +2273,47 @@7. vCard Properties
Purpose:
To specify the organizational name and units associated +
Purpose:
To specify the organizational name and units associated with the vCard.
Value type:
A single structured text value consisting of components +
A single structured text value consisting of components separated by the SEMICOLON character (U+003B).
Cardinality:
*
+*
Special notes:
The property is based on the X.520 Organization Name +
The property is based on the X.520 Organization Name and Organization Unit attributes CCITT Recommendation X520. The property value is a structured type consisting of the organization name, followed by zero or more levels of organizational unit names.
-The SORT-AS parameter MAY be applied to this property.
+The SORT-AS parameter MAY be applied to this property.
ABNF:
ORG-param = "VALUE=text" / sort-as-param / language-param
/ pid-param / pref-param / altid-param / type-param
/ any-param
ORG-value = component *(";" component)
ORG-param = "VALUE=text" / sort-as-param / language-param
/ pid-param / pref-param / altid-param / type-param
/ any-param
ORG-value = component *(";" component)
Example:
A property value consisting of an organizational name, +
A property value consisting of an organizational name, organizational unit #1 name, and organizational unit #2 name.
-ORG:ABC\, Inc.;North American Division;Marketing
Purpose:
To include a member in the group this vCard represents.
+Purpose:
To include a member in the group this vCard represents.
Value type:
A single URI. It MAY refer to something other than a +
A single URI. It MAY refer to something other than a vCard object. For example, an email distribution list could employ the "mailto" URI scheme RFC 6068 for efficiency.
Cardinality:
*
+*
Special notes:
This property MUST NOT be present unless the value of +
This property MUST NOT be present unless the value of the KIND property is "group".
ABNF:
MEMBER-param = "VALUE=uri" / pid-param / pref-param / altid-param
/ mediatype-param / any-param
MEMBER-value = URI
MEMBER-param = "VALUE=uri" / pid-param / pref-param / altid-param
/ mediatype-param / any-param
MEMBER-value = URI
Examples:
BEGIN:VCARD VERSION:4.0 KIND:group @@ -2346,30 +2346,30 @@7. vCard Properties
Purpose:
To specify a relationship between another entity and the +
Purpose:
To specify a relationship between another entity and the entity represented by this vCard.
Value type:
A single URI. It can also be reset to a single text +
A single URI. It can also be reset to a single text value. The text value can be used to specify textual information.
Cardinality:
*
+*
Special notes:
The TYPE parameter MAY be used to characterize the +
The TYPE parameter MAY be used to characterize the related entity. It contains a comma-separated list of values that are registered with IANA as described in Clause 11.2. The registry is pre-populated with the values defined in XFN. This document also specifies two additional values:
-agent:
an entity who may sometimes act on behalf of the entity +
agent:
an entity who may sometimes act on behalf of the entity associated with the vCard.
emergency:
indicates an emergency contact
+indicates an emergency contact
ABNF:
RELATED-param = RELATED-param-uri / RELATED-param-text
RELATED-value = URI / text
; Parameter and value MUST match.
RELATED-param-uri = "VALUE=uri" / mediatype-param
RELATED-param-text = "VALUE=text" / language-param
RELATED-param =/ pid-param / pref-param / altid-param / type-param
/ any-param
type-param-related = related-type-value *("," related-type-value)
; type-param-related MUST NOT be used with a property other than
; RELATED.
related-type-value = "contact" / "acquaintance" / "friend" / "met"
/ "co-worker" / "colleague" / "co-resident"
/ "neighbor" / "child" / "parent"
/ "sibling" / "spouse" / "kin" / "muse"
/ "crush" / "date" / "sweetheart" / "me"
/ "agent" / "emergency"
RELATED-param = RELATED-param-uri / RELATED-param-text
RELATED-value = URI / text
; Parameter and value MUST match.
RELATED-param-uri = "VALUE=uri" / mediatype-param
RELATED-param-text = "VALUE=text" / language-param
RELATED-param =/ pid-param / pref-param / altid-param / type-param
/ any-param
type-param-related = related-type-value *("," related-type-value)
; type-param-related MUST NOT be used with a property other than
; RELATED.
related-type-value = "contact" / "acquaintance" / "friend" / "met"
/ "co-worker" / "colleague" / "co-resident"
/ "neighbor" / "child" / "parent"
/ "sibling" / "spouse" / "kin" / "muse"
/ "crush" / "date" / "sweetheart" / "me"
/ "agent" / "emergency"
Examples:
RELATED;TYPE=friend:urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6 RELATED;TYPE=contact:http://example.com/directory/jdoe.vcf RELATED;TYPE=co-worker;VALUE=text:Please contact my assistant Jane @@ -2379,104 +2379,104 @@7. vCard Properties
These properties are concerned with additional explanations, such as +
These properties are concerned with additional explanations, such as that related to informational notes or revisions specific to the vCard.
Purpose:
To specify application category information about the +
Purpose:
To specify application category information about the vCard, also known as "tags".
Value type:
One or more text values separated by a COMMA character +
One or more text values separated by a COMMA character (U+002C).
Cardinality:
*
+*
ABNF:
CATEGORIES-param = "VALUE=text" / pid-param / pref-param
/ type-param / altid-param / any-param
CATEGORIES-value = text-list
CATEGORIES-param = "VALUE=text" / pid-param / pref-param
/ type-param / altid-param / any-param
CATEGORIES-value = text-list
Example:
CATEGORIES:TRAVEL AGENT
CATEGORIES:INTERNET,IETF,INDUSTRY,INFORMATION TECHNOLOGY
Purpose:
To specify supplemental information or a comment that is +
Purpose:
To specify supplemental information or a comment that is associated with the vCard.
Value type:
A single text value.
+A single text value.
Cardinality:
*
+*
Special notes: The property is based on the X.520 Description +
Special notes: The property is based on the X.520 Description attribute CCITT Recommendation X520.
-ABNF:
NOTE-param = "VALUE=text" / language-param / pid-param / pref-param
/ type-param / altid-param / any-param
NOTE-value = text
ABNF:
NOTE-param = "VALUE=text" / language-param / pid-param / pref-param
/ type-param / altid-param / any-param
NOTE-value = text
Example:
NOTE:This fax number is operational 0800 to 1715
EST\, Mon-Fri.
Purpose:
To specify the identifier for the product that created the +
Purpose:
To specify the identifier for the product that created the vCard object.
Type value:
A single text value.
+A single text value.
Cardinality:
*1
+*1
Special notes:
Implementations SHOULD use a method such as that +
Implementations SHOULD use a method such as that specified for Formal Public Identifiers in ISO 9070 or for Universal Resource Names in RFC 3406 to ensure that the text value is unique.
ABNF:
PRODID-param = "VALUE=text" / any-param
PRODID-value = text
PRODID-param = "VALUE=text" / any-param
PRODID-value = text
Example:
PRODID:-//ONLINE DIRECTORY//NONSGML Version 1//EN
Purpose:
To specify revision information about the current vCard.
+Purpose:
To specify revision information about the current vCard.
Value type:
A single timestamp value.
+A single timestamp value.
Cardinality:
*1
+*1
Special notes:
The value distinguishes the current revision of the +
The value distinguishes the current revision of the information in this vCard for other renditions of the information.
ABNF:
REV-param = "VALUE=timestamp" / any-param
REV-value = timestamp
REV-param = "VALUE=timestamp" / any-param
REV-value = timestamp
Example:
REV:19951031T222710Z
Purpose:
To specify a digital sound content information that +
Purpose:
To specify a digital sound content information that annotates some aspect of the vCard. This property is often used to specify the proper pronunciation of the name property value of the vCard.
Value type:
A single URI.
+A single URI.
Cardinality:
*
+*
ABNF:
SOUND-param = "VALUE=uri" / language-param / pid-param / pref-param
/ type-param / mediatype-param / altid-param
/ any-param
SOUND-value = URI
SOUND-param = "VALUE=uri" / language-param / pid-param / pref-param
/ type-param / mediatype-param / altid-param
/ any-param
SOUND-value = URI
Example:
SOUND:CID:JOHNQPUBLIC.part8.19960229T080000.xyzMail@example.com SOUND:data:audio/basic;base64,MIICajCCAdOgAwIBAgICBEUwDQYJKoZIh @@ -2488,51 +2488,51 @@7. vCard Properties
Purpose:
To specify a value that represents a globally unique +
Purpose:
To specify a value that represents a globally unique identifier corresponding to the entity associated with the vCard.
Value type:
A single URI value. It MAY also be reset to free-form +
A single URI value. It MAY also be reset to free-form text.
Cardinality:
*1
+*1
Special notes:
This property is used to uniquely identify the object +
This property is used to uniquely identify the object that the vCard represents. The "uuid" URN namespace defined in RFC 4122 is particularly well suited to this task, but other URI schemes MAY be used. Free-form text MAY also be used.
ABNF:
UID-param = UID-uri-param / UID-text-param
UID-value = UID-uri-value / UID-text-value
; Value and parameter MUST match.
UID-uri-param = "VALUE=uri"
UID-uri-value = URI
UID-text-param = "VALUE=text"
UID-text-value = text
UID-param =/ any-param
UID-param = UID-uri-param / UID-text-param
UID-value = UID-uri-value / UID-text-value
; Value and parameter MUST match.
UID-uri-param = "VALUE=uri"
UID-uri-value = URI
UID-text-param = "VALUE=text"
UID-text-value = text
UID-param =/ any-param
Example:
UID:urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6
Purpose:
To give a global meaning to a local PID source identifier.
+Purpose:
To give a global meaning to a local PID source identifier.
Value type:
A semicolon-separated pair of values. The first field +
A semicolon-separated pair of values. The first field is a small integer corresponding to the second field of a PID parameter instance. The second field is a URI. The "uuid" URN namespace defined in RFC 4122 is particularly well suited to this task, but other URI schemes MAY be used.
Cardinality:
*
-Special notes:
PID source identifiers (the source identifier is the +
*
+Special notes:
PID source identifiers (the source identifier is the second field in a PID parameter instance) are small integers that only have significance within the scope of a single vCard instance. Each distinct source identifier present in a vCard MUST have an associated CLIENTPIDMAP. See Clause 8 for more details -on the usage of CLIENTPIDMAP.
PID source identifiers MUST be strictly positive. Zero is not +on the usage of CLIENTPIDMAP.
PID source identifiers MUST be strictly positive. Zero is not allowed.
-As a special exception, the PID parameter MUST NOT be applied to +
As a special exception, the PID parameter MUST NOT be applied to this property.
ABNF:
CLIENTPIDMAP-param = any-param
CLIENTPIDMAP-value = 1*DIGIT ";" URI
CLIENTPIDMAP-param = any-param
CLIENTPIDMAP-value = 1*DIGIT ";" URI
Example:
TEL;PID=3.1,4.2;VALUE=uri:tel:+1-555-555-5555 EMAIL;PID=4.1,5.2:jdoe@example.com CLIENTPIDMAP:1;urn:uuid:3df403f4-5924-4bb7-b077-3c711d9eb34b @@ -2542,64 +2542,64 @@7. vCard Properties
Purpose:
To specify a uniform resource locator associated with the +
Purpose:
To specify a uniform resource locator associated with the object to which the vCard refers. Examples for individuals include personal web sites, blogs, and social networking site identifiers.
Cardinality:
*
+*
Value type:
A single uri value.
+A single uri value.
ABNF:
URL-param = "VALUE=uri" / pid-param / pref-param / type-param
/ mediatype-param / altid-param / any-param
URL-value = URI
URL-param = "VALUE=uri" / pid-param / pref-param / type-param
/ mediatype-param / altid-param / any-param
URL-value = URI
Example:
URL:http://example.org/restaurant.french/~chezchic.html
Purpose:
To specify the version of the vCard specification used to +
Purpose:
To specify the version of the vCard specification used to format this vCard.
Value type:
A single text value.
+A single text value.
Cardinality:
1
+1
Special notes:
This property MUST be present in the vCard object, +
This property MUST be present in the vCard object, and it must appear immediately after BEGIN:VCARD. The value MUST be "4.0" if the vCard corresponds to this specification. Note that earlier versions of vCard allowed this property to be placed anywhere in the vCard object, or even to be absent.
ABNF:
VERSION-param = "VALUE=text" / any-param
VERSION-value = "4.0"
VERSION-param = "VALUE=text" / any-param
VERSION-value = "4.0"
Example: