One document matched: draft-ietf-vcarddav-vcardrev-19.xml
<?xml version="1.0"?>
<?xml-stylesheet type='text/xsl' href='rfc2629.xslt'?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [
<!ENTITY ccittx5201988 PUBLIC ''
'http://xml.resource.org/public/rfc/bibxml2/reference.CCITT.X520.1988.xml'>
<!ENTITY ccitte1631988 PUBLIC ''
'http://xml.resource.org/public/rfc/bibxml2/reference.CCITT.E163.1988.xml'>
<!ENTITY ccittx5211988 PUBLIC ''
'http://xml.resource.org/public/rfc/bibxml2/reference.CCITT.X521.1988.xml'>
<!ENTITY ccittx1211988 PUBLIC ''
'http://xml.resource.org/public/rfc/bibxml2/reference.CCITT.X121.1988.xml'>
<!ENTITY rfc1738 PUBLIC ''
'http://xml.resource.org/public/rfc/bibxml/reference.RFC.1738.xml'>
<!ENTITY rfc2045 PUBLIC ''
'http://xml.resource.org/public/rfc/bibxml/reference.RFC.2045.xml'>
<!ENTITY rfc2425 PUBLIC ''
'http://xml.resource.org/public/rfc/bibxml/reference.RFC.2425.xml'>
<!ENTITY rfc2426 PUBLIC ''
'http://xml.resource.org/public/rfc/bibxml/reference.RFC.2426.xml'>
<!ENTITY rfc2119 PUBLIC ''
'http://xml.resource.org/public/rfc/bibxml/reference.RFC.2119.xml'>
<!ENTITY rfc2046 PUBLIC ''
'http://xml.resource.org/public/rfc/bibxml/reference.RFC.2046.xml'>
<!ENTITY rfc2397 PUBLIC ''
'http://xml.resource.org/public/rfc/bibxml/reference.RFC.2397.xml'>
<!ENTITY rfc2616 PUBLIC ''
'http://xml.resource.org/public/rfc/bibxml/reference.RFC.2616.xml'>
<!ENTITY rfc5322 PUBLIC ''
'http://xml.resource.org/public/rfc/bibxml/reference.RFC.5322.xml'>
<!ENTITY rfc3629 PUBLIC ''
'http://xml.resource.org/public/rfc/bibxml/reference.RFC.3629.xml'>
<!ENTITY rfc2739 PUBLIC ''
'http://xml.resource.org/public/rfc/bibxml/reference.RFC.2739.xml'>
<!ENTITY rfc3282 PUBLIC ''
'http://xml.resource.org/public/rfc/bibxml/reference.RFC.3282.xml'>
<!ENTITY rfc3406 PUBLIC ''
'http://xml.resource.org/public/rfc/bibxml/reference.RFC.3406.xml'>
<!ENTITY rfc3966 PUBLIC ''
'http://xml.resource.org/public/rfc/bibxml/reference.RFC.3966.xml'>
<!ENTITY rfc3986 PUBLIC ''
'http://xml.resource.org/public/rfc/bibxml/reference.RFC.3986.xml'>
<!ENTITY rfc4122 PUBLIC ''
'http://xml.resource.org/public/rfc/bibxml/reference.RFC.4122.xml'>
<!ENTITY rfc4288 PUBLIC ''
'http://xml.resource.org/public/rfc/bibxml/reference.RFC.4288.xml'>
<!ENTITY rfc5646 PUBLIC ''
'http://xml.resource.org/public/rfc/bibxml/reference.RFC.5646.xml'>
<!ENTITY rfc4770 PUBLIC ''
'http://xml.resource.org/public/rfc/bibxml/reference.RFC.4770.xml'>
<!ENTITY rfc4880 PUBLIC ''
'http://xml.resource.org/public/rfc/bibxml/reference.RFC.4880.xml'>
<!ENTITY rfc5234 PUBLIC ''
'http://xml.resource.org/public/rfc/bibxml/reference.RFC.5234.xml'>
<!ENTITY rfc5545 PUBLIC ''
'http://xml.resource.org/public/rfc/bibxml/reference.RFC.5545.xml'>
<!ENTITY rfc5546 PUBLIC ''
'http://xml.resource.org/public/rfc/bibxml/reference.RFC.5546.xml'>
<!ENTITY rfc5751 PUBLIC ''
'http://xml.resource.org/public/rfc/bibxml/reference.RFC.5751.xml'>
<!ENTITY rfc6068 PUBLIC ''
'http://xml.resource.org/public/rfc/bibxml/reference.RFC.6068.xml'>
<!ENTITY geo-uri PUBLIC ''
'http://xml.resource.org/public/rfc/bibxml/reference.RFC.5870.xml'>
<!ENTITY I-D.ietf-eai-rfc5335bis PUBLIC ''
'http://xml.resource.org/public/rfc/bibxml3/reference.I-D.ietf-eai-rfc5335bis.xml'>
<!ENTITY xml PUBLIC ''
'http://xml.resource.org/public/rfc/bibxml4/reference.W3C.REC-xml-20081126.xml'>
]>
<?rfc rfcedstyle="yes" ?>
<?rfc rfcprocack="yes"?>
<?rfc toc="yes"?>
<?rfc tocdepth="4"?><!-- default = 3 -->
<?rfc symrefs="yes"?>
<?rfc sortrefs="yes"?>
<?rfc compact="yes"?>
<?rfc subcompact="no"?>
<?rfc strict="yes"?>
<?rfc comments="yes"?>
<?rfc inline="yes"?>
<rfc ipr="pre5378Trust200902" docName="draft-ietf-vcarddav-vcardrev-19" category="std"
obsoletes="2425, 2426, 4770"
updates="2739">
<front>
<title abbrev="vCard">vCard Format Specification</title>
<author initials="S." surname="Perreault" fullname="Simon Perreault">
<organization>Viagénie</organization>
<address>
<postal>
<street>2875 Laurier, suite D2-630</street>
<city>Québec</city>
<region>QC</region>
<code>G1V 2M2</code>
<country>Canada</country>
</postal>
<phone>+1 418 656 9254</phone>
<email>simon.perreault@viagenie.ca</email>
<uri>http://www.viagenie.ca</uri>
</address>
</author>
<date year="2011"/>
<area>Applications</area>
<keyword>vcard</keyword>
<abstract>
<t>
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 clips, etc.). This
document obsoletes RFCs 2425, 2426, 2739, and 4770.
</t>
</abstract>
</front>
<middle>
<section title="Introduction">
<t>Electronic address books have become ubiquitous. Their increased presence
on portable, connected devices as well as the diversity of platforms
exchanging 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.</t>
</section>
<section title="Conventions" anchor="oldsection_Abstract">
<t>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 <xref
target="RFC2119"/>.</t>
</section>
<section title="vCard Format Specification">
<t>The text/vcard MIME content type (hereafter known as "vCard", see <xref
target="mime_type_registration"/>) 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.</t>
<section title="Character Set">
<t>The character set for vCard is UTF-8 as defined in <xref
target="RFC3629"/>. There is no way to override this. It is invalid to
specify a different character set in the "charset" MIME parameter (see
<xref target="mime_type_registration"/>).</t>
</section>
<section title="Line Delimiting and Folding" anchor="folding">
<t>Individual lines within vCard are delimited by the <xref
target="RFC5322"/> line break, which is a CRLF sequence (ASCII decimal
13, followed by ASCII decimal 10). 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 <xref
target="RFC5322"/>, Section 2.1.1.</t>
<t>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 (ASCII decimal 32) or horizontal tab,
(ASCII decimal 9)). 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:</t>
<figure><artwork>
NOTE:This is a long description that exists on a long line.
</artwork></figure>
<figure>
<preamble>can be represented as:</preamble>
<artwork>
NOTE:This is a long description
that exists on a long line.
</artwork>
</figure>
<figure>
<preamble>It could also be represented as:</preamble>
<artwork>
NOTE:This is a long descrip
tion that exists o
n a long line.
</artwork>
</figure>
<t>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 ASCII decimal 9 or SPACE ASCII decimal
32) as equivalent to no characters at all (i.e., the CRLF and single white
space character are removed).
<list>
<t>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.</t>
<t>Note: Unfolding is done differently than in <xref target="RFC5322"/>.
Unfolding in <xref target="RFC5322"/> only removes the CRLF, not the
space following it.</t>
</list>
</t>
<t>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.</t>
</section>
<section title="ABNF Format Definition">
<t>The following ABNF uses the notation of <xref target="RFC5234"/>, which
also defines CRLF, WSP, DQUOTE, VCHAR, ALPHA, and DIGIT.</t>
<figure>
<artwork>
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 above.
; When generating a content line, lines longer than 75
; characters SHOULD be folded according to the folding
; procedure described above.
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 = %x80-FF
; Use is restricted by UTF-8
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
</artwork>
</figure>
<t>A line that begins with a white space character is a continuation of the
previous line, as described above. 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 <xref target="RFC5322"/>, in that the sequence
<CRLF><WSP> found anywhere in the content indicates a
continued line and should be removed.</t>
<t>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. Based
on experience with vCard 3 interoperability, it is RECOMMENDED that
property and parameter names be upper-case on output.</t>
<t>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.</t>
<t>Property cardinalities are indicated using the following notation, which is
based on ABNF (see <xref target="RFC5234"/>, section 3.6):</t>
<texttable>
<ttcol align="center">Cardinality</ttcol>
<ttcol align="left">Meaning</ttcol>
<c>1</c>
<c>Exactly one instance per vCard MUST be present.</c>
<c>*1</c>
<c>Exactly one instance per vCard MAY be present.</c>
<c>1*</c>
<c>One or more instances per vCard MUST be present.</c>
<c>*</c>
<c>One or more instances per vCard MAY be present.</c>
</texttable>
<t>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 noted that some
value types support encoding multiple values in a single content line by
separating the values with a comma ",". This approach has been taken for
several of the content types defined below (date, time, integer,
float).</t>
</section>
<section title="Property Value Escaping">
<t>Some properties may contain one or more values delimited by a COMMA
character (ASCII decimal 44). Therefore, a COMMA character in a value MUST
be escaped with a BACKSLASH character (ASCII decimal 92), even for
properties that don't allow multiple instances (for consistency).</t>
<t>Some properties (e.g. N and ADR) comprise multiple fields delimited by a
SEMI-COLON character (ASCII decimal 59). Therefore, a SEMI-COLON in a
field of such a "compound" property MUST be escaped with a BACKSLASH
character. SEMI-COLON characters in non-compound properties MAY be
escaped. On input, an escaped SEMI-COLON character is never a field
separator. An unescaped SEMI-COLON character may be a field
separator, depending on the property in which it appears.</t>
<t>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.</t>
<t>Finally, BACKSLASH characters in values MUST be escaped with a BACKSLASH
character. NEWLINE (ASCII decimal 10) characters in values MUST be encoded
by two characters: a BACKSLASH followed by an 'n' (ASCII decimal 110).</t>
<t>In all other cases, escaping MUST NOT be used.</t>
</section>
</section>
<section title="Property Value Data Types">
<t>Standard value types are defined below.</t>
<figure>
<artwork>
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 [RFC3986]
/ iana-valuespec
; Actual value type depends on property name and VALUE parameter.
text = *TEXT-CHAR
TEXT-CHAR = "\\" / "\," / "\n"
/ <any VALUE-CHAR except , or \>
; 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 [RFC5646], 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
</artwork>
</figure><!-- TODO: update ref -->
<section title="TEXT" anchor="TEXT">
<t>"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 <xref target="LANGUAGE"/>.</t>
<figure>
<preamble>Examples for "text":</preamble>
<artwork>
this is a text value
this is one value,this is another
this is a single value\, with a comma encoded
</artwork>
</figure>
<t>A formatted text line break in a text value type MUST be represented as
the character sequence backslash (ASCII decimal 92) followed by a Latin
small letter n (ASCII decimal 110) or a Latin capital letter N (ASCII
decimal 78), that is "\n" or "\N".</t>
<figure>
<preamble>For example a multiple line NOTE value of:</preamble>
<artwork>
Mythical Manager
Hyjinx Software Division
BabsCo, Inc.
</artwork>
</figure>
<figure>
<preamble>could be represented as:</preamble>
<artwork>
NOTE:Mythical Manager\nHyjinx Software Division\n
BabsCo\, Inc.\n
</artwork>
<postamble>demonstrating the \n literal formatted line break technique,
the CRLF-followed-by-space line folding technique, and the backslash
escape technique.</postamble>
</figure>
</section>
<section title="URI" anchor="URI">
<t>"uri": The "uri" value type should be used to identify values that are
referenced by a URI (including a Content-ID 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 Section 3 of <xref target="RFC3986"/>. Note that the value of a
property of type "uri" is what the URI points to, not the URI itself.</t>
<figure>
<preamble>Examples for "uri":</preamble>
<artwork>
http://www.example.com/my/picture.jpg
ldap://ldap.example.com/cn=babs%20jensen
</artwork>
</figure>
</section>
<section title="DATE, TIME, DATE-TIME, DATE-AND-OR-TIME, and TIMESTAMP">
<t>"date", "time", "date-time", and "timestamp": Each of these value types
is based on the definitions in <xref target="ISO.8601.2004"/> standard.
Multiple such values can be specified using the comma-separated
notation.</t>
<t>Only the basic format is supported.</t>
<section title="DATE" anchor="DATE">
<t>A calendar date as specified in <xref target="ISO.8601.2004"/> section
4.1.2.</t>
<t>Reduced accuracy, as specified in <xref target="ISO.8601.2004"/>
sections 4.1.2.3 a) and b), but not c), is permitted.</t>
<t>Expanded representation, as specified in <xref target="ISO.8601.2004"/>
section 4.1.4, is forbidden.</t>
<t>Truncated representation, as specified in <xref target="ISO.8601.2000"/>
sections 5.2.1.3 d), e), and f), is permitted.</t>
<figure>
<preamble>Examples for "date":</preamble>
<artwork>
19850412
1985-04
1985
--0412
---12
</artwork>
</figure>
<t>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.</t>
</section>
<section title="TIME" anchor="TIME">
<t>A time of day as specified in <xref target="ISO.8601.2004"/> section
4.2.</t>
<t>Reduced accuracy, as specified in <xref target="ISO.8601.2004"/>
section 4.2.2.3, is permitted.</t>
<t>Representation with decimal fraction, as specified in <xref
target="ISO.8601.2004"/> section 4.2.2.4, is forbidden.</t>
<t>The midnight hour is always represented by 00, never 24 (see <xref
target="ISO.8601.2004"/> section 4.2.3).</t>
<t>Truncated representation, as specified in <xref
target="ISO.8601.2000"/> sections 5.3.1.4 a), b), and c), is
permitted.</t>
<figure>
<preamble>Examples for "time":</preamble>
<artwork>
102200
1022
10
-2200
--00
102200Z
102200-0800
</artwork>
</figure>
</section>
<section title="DATE-TIME" anchor="DATE_TIME">
<t>A date and time of day combination as specified in <xref
target="ISO.8601.2004"/> section 4.3.</t>
<t>Truncation of the date part, as specified in <xref
target="ISO.8601.2000"/> section 5.4.2 c), is permitted.</t>
<figure>
<preamble>Examples for "date-time":</preamble>
<artwork>
19961022T140000
--1022T1400
---22T14
</artwork>
</figure>
</section>
<section title="DATE-AND-OR-TIME" anchor="DATE_AND_OR_TIME">
<t>Either a DATE-TIME, a DATE, or a TIME value. To allow unambiguous
interpretation, a standalone TIME value is always preceded by a "T".</t>
<figure>
<preamble>Examples for "date-and-or-time":</preamble>
<artwork>
19961022T140000
--1022T1400
---22T14
19850412
1985-04
1985
--0412
---12
T102200
T1022
T10
T-2200
T--00
T102200Z
T102200-0800
</artwork>
</figure>
</section>
<section title="TIMESTAMP" anchor="TIMESTAMP">
<t>A complete date and time of day combination as specified in <xref
target="ISO.8601.2004"/> section 4.3.2.</t>
<figure>
<preamble>Examples for "timestamp":</preamble>
<artwork>
19961022T140000
19961022T140000Z
19961022T140000-05
19961022T140000-0500
</artwork>
</figure>
</section>
</section>
<section title="BOOLEAN" anchor="BOOLEAN">
<t>"boolean": The "boolean" value type is used to express boolean values.
These values are case insensitive.</t>
<figure>
<preamble>Examples:</preamble>
<artwork>
TRUE
false
True
</artwork>
</figure>
</section>
<section title="INTEGER" anchor="INTEGER">
<t>"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.</t>
<figure>
<preamble>Examples:</preamble>
<artwork>
1234567890
-1234556790
+1234556790,432109876
</artwork>
</figure>
</section>
<section title="FLOAT" anchor="FLOAT">
<t>"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.
<list>
<t>Note: Scientific notation is disallowed. Implementors wishing to use
their favorite language's %f formatting should be careful.</t>
</list>
</t>
<figure>
<preamble>Examples:</preamble>
<artwork>
20.30
1000000.0000001
1.333,3.14
</artwork>
</figure>
</section>
<section title="LANGUAGE-TAG" anchor="LANGUAGE-TAG">
<t>"language-tag": A single language tag, as defined in <xref
target="RFC5646"/>.</t>
</section>
</section>
<section title="Property Parameters" anchor="parameters">
<t>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
(US-ASCII decimal 44).</t>
<t>Property parameter value elements that contain the COLON (US-ASCII decimal 58),
SEMICOLON (US-ASCII decimal 59) or COMMA (US-ASCII decimal 44) character
separators MUST be specified as quoted-string text values. Property
parameter values MUST NOT contain the DQUOTE (US-ASCII decimal 34)
character. The DQUOTE character is used as a delimiter for parameter values
that contain restricted characters or URI text.</t>
<t>Applications MUST ignore x-param and iana-param values they don't
recognize.</t>
<section title="LANGUAGE" anchor="LANGUAGE">
<t>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 <xref
target="RFC3282"/>. The value of the LANGUAGE property parameter is a
language tag as defined in Section 2 of <xref target="RFC5646"/>.</t>
<figure>
<preamble>Examples:</preamble>
<artwork>
ROLE;LANGUAGE=tr:hoca
</artwork>
</figure>
<figure>
<preamble>ABNF:</preamble>
<artwork>
language-param = "LANGUAGE=" Language-Tag
; Language-Tag is defined in section 2.1 of RFC 5646
</artwork>
</figure>
</section>
<section title="VALUE" anchor="VALUE">
<t>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, existing parsing
and processing code can be leveraged. The predefined data type values MUST
NOT be repeated in COMMA separated value lists except within the N,
NICKNAME, ADR, and CATEGORIES properties.</t>
<figure>
<preamble>ABNF:</preamble>
<artwork>
value-param = "VALUE=" value-type
value-type = "text"
/ "uri"
/ "date"
/ "time"
/ "date-time"
/ "timestamp"
/ "boolean"
/ "integer"
/ "float"
/ "language-tag"
/ "utc-offset"
/ iana-token ; registered as described in section 12
/ x-name
</artwork>
</figure>
</section>
<section title="PREF" anchor="PREF">
<t>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, 1 being most preferred.</t>
<t>When the parameter is absent, the default MUST be to interpret the
property instance as being least preferred.</t>
<t>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.</t>
<t>This parameter MAY be applied to any property that allows multiple
instances.</t>
<figure>
<preamble>ABNF:</preamble>
<artwork>
pref-param = "PREF=" (1*2DIGIT / "100")
; An integer between 1 and 100.
</artwork>
</figure>
</section>
<section title="ALTID" anchor="ALTID">
<t>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 (<xref target="LANGUAGE"/>)
parameter which are tagged with the same ALTID value.</t>
<t>This parameter's value is treated as an opaque string. Its sole purpose
is to be compared for equality against other ALTID parameter values.</t>
<t>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.</t>
<t>Property instances having the same ALTID parameter value count as 1
toward cardinality. Therefore, since N (<xref target="N"/>) has
cardinality *1 and TITLE (<xref target="TITLE"/>) has cardinality
*, these three examples would be legal:</t>
<figure>
<artwork>
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
</artwork>
</figure>
<t>while this one would not:</t>
<figure>
<artwork>
N;ALTID=1;LANGUAGE=jp:<U+5C71><U+7530>;<U+592A><U+90CE>;;;
N:Yamada;Taro;;;
(Two instances of the N property.)
</artwork>
</figure>
<t>and these three would be legal but questionable:</t>
<figure>
<artwork>
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.)
</artwork>
</figure>
<t>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:</t>
<figure>
<artwork>
PHOTO;ALTID=1:data:image/jpeg;base64,...
PHOTO;ALTID=1;data:image/jp2;base64,...
</artwork>
</figure>
<figure>
<preamble>ABNF:</preamble>
<artwork>
altid-param = "ALTID=" param-value
</artwork>
</figure>
</section>
<section title="PID" anchor="PID">
<t>The PID parameter is used to identify a specific property among
multiple instances. It plays a role analogous to the UID property (<xref
target="UID"/>) on a per-property instead of per-vCard basis. It MAY
appear more than once in a given property. It MUST NOT appear on
properties that may have only one instance per vCard. Its value is either
a single small positive integer or a pair of small positive integers
separated by a dot. Multiple values may be encoded in a single PID
parameter by separating the values with a comma ",". See <xref
target="synchronization"/> for more details on its usage.</t>
<figure>
<preamble>ABNF:</preamble>
<artwork>
pid-param = "PID=" pid-value *("," pid-value)
pid-value = 1*DIGIT ["." 1*DIGIT]
</artwork>
</figure>
</section>
<section title="TYPE" anchor="TYPE">
<t>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 pre-defined
enumeration. In this document, the following properties make use of this
parameter: FN, NICKNAME, PHOTO, ADR, TEL, EMAIL, IMPP, LANG, TZ,
GEO, TITLE, ROLE, LOGO, ORG, RELATED, CATEGORIES, NOTE, SOUND, URL, KEY,
FBURL, CALADRURI, and CALURI. The TYPE parameter MUST NOT be
applied on other properties defined in this document.</t>
<t>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.</t>
<figure>
<preamble>ABNF:</preamble>
<artwork>
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.
</artwork>
</figure>
</section>
<section title="MEDIATYPE" anchor="MEDIATYPE">
<t>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 of the resource identified by the URI. Some URI
schemes do not need this parameter. For example, the "data" scheme allows
the media type to be explicitly indicated as part of the URI <xref
target="RFC2397"/>. Another scheme, "http", provides the media type as
part of the URI resolution process, with the Content-Type HTTP header
<xref target="RFC2616"/>. The MEDIATYPE parameter is intended to be used
with URI schemes that do not provide such functionality (e.g. "ftp" <xref
target="RFC1738"/>).</t>
<figure>
<preamble>ABNF:</preamble>
<artwork>
mediatype-param = "MEDIATYPE=" mediatype
mediatype = type-name "/" subtype-name *( ";" attribute "=" value )
; "attribute" and "value" are from [RFC2045]
; "type-name" and "subtype-name" are from [RFC4288]
</artwork>
</figure>
</section>
<section title="CALSCALE" anchor="CALSCALE">
<t>The CALSCALE parameter is identical to the CALSCALE property in iCalendar
(see <xref target="RFC5545"/>, 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 the
Gregorian system. It is the default when the parameter is absent.
Additional values may be defined in extension documents and registered
from IANA (see <xref target="iana_values"/>). A vCard implementation MUST
ignore properties with a CALSCALE parameter value that it does not
understand.</t>
<figure>
<preamble>ABNF:</preamble>
<artwork>
calscale-param = "CALSCALE=" calscale-value
calscale-value = "gregorian" / iana-token / x-name
</artwork>
</figure>
</section>
<section title="SORT-AS" anchor="SORT-AS">
<t>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.</t>
<t>This parameter's value is a comma-separated list which MUST have as many
or less elements as the corresponding property value has components.</t>
<figure>
<preamble>ABNF:</preamble>
<artwork>
sort-as-param = "SORT-AS=" sort-as-value
sort-as-value = param-value *("," param-value)
</artwork>
</figure>
<t>
Examples: For the case of surname and given name sorting, the following
examples define common sort string usage with the N property.
</t>
<figure>
<artwork>
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;;
</artwork>
</figure>
<figure>
<preamble>If sorted by surname the results would be:</preamble>
<artwork>
Christine d'Aboville
Rene van der Harten
Osamu Koura
H. James de Mann
Robert Pau Shou Chang
Oscar del Pozo
</artwork>
</figure>
<figure>
<preamble>If sorted by given name the results would be:</preamble>
<artwork>
Christine d'Aboville
H. James de Mann
Osamu Koura
Oscar del Pozo
Rene van der Harten
Robert Pau Shou Chang
</artwork>
</figure>
</section>
<section title="GEO" anchor="GEO-param">
<t>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 <xref target="GEO"/>).</t>
<figure>
<preamble>ABNF:</preamble>
<artwork>
geo-parameter = "GEO=" DQUOTE URI DQUOTE
</artwork>
</figure>
</section>
<section title="TZ" anchor="TZ-param">
<t>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.</t>
<figure>
<preamble>ABNF:</preamble>
<artwork>
tz-parameter = "TZ=" (param-value / DQUOTE URI DQUOTE)
</artwork>
</figure>
</section>
</section>
<section title="vCard Properties" anchor="properties">
<t>What follows is an enumeration of the standard vCard properties.</t>
<section title="General Properties">
<section title="BEGIN" anchor="BEGIN">
<t>
<list style="hanging">
<t hangText="Purpose:">To denote the beginning of a syntactic entity
within a text/vcard content-type.</t>
<t hangText="Value type:">text</t>
<t hangText="Cardinality:">1</t>
<t hangText="Special notes:">The content entity MUST begin with the
BEGIN property with a value of "VCARD". The value is
case-insensitive.</t>
<t>The BEGIN property is used in conjunction with the END property to
delimit an entity containing a related set of properties within an
text/vcard content-type. This construct can be used instead of or in
addition to wrapping separate sets of information inside additional
MIME headers. It is provided for applications that wish to define
content that can contain multiple entities within the same
text/vcard content-type or to define content that can be
identifiable outside of a MIME environment.</t>
<t hangText="ABNF:">
<figure>
<artwork>
BEGIN-param = 0<nothing> ; no parameter allowed
BEGIN-value = "VCARD"
</artwork>
</figure>
</t>
<t hangText="Example:">
<figure>
<artwork>
BEGIN:VCARD
</artwork>
</figure>
</t>
</list>
</t>
</section>
<section title="END" anchor="END">
<t>
<list style="hanging">
<t hangText="Purpose:">To denote the end of a syntactic entity
within a text/vcard content-type.</t>
<t hangText="Value type:">text</t>
<t hangText="Cardinality:">1</t>
<t hangText="Special notes:">The content entity MUST end with the END
type with a value of "VCARD". The value is case-insensitive.</t>
<t>The END property is used in conjunction with the BEGIN property to
delimit an entity containing a related set of properties within an
text/vcard content-type. This construct can be used instead of or
in addition to wrapping separate sets of information inside
additional MIME headers. It is provided for applications that wish
to define content that can contain multiple entities within the same
text/vcard content-type or to define content that can be
identifiable outside of a MIME environment.</t>
<t hangText="ABNF:">
<figure>
<artwork>
END-param = 0<nothing> ; no parameter allowed
END-value = "VCARD"
</artwork>
</figure>
</t>
<t hangText="Example:">
<figure>
<artwork>
END:VCARD
</artwork>
</figure>
</t>
</list>
</t>
</section>
<section title="SOURCE" anchor="SOURCE">
<t>
<list style="hanging">
<t hangText="Purpose:">To identify the source of directory information
contained in the content type.</t>
<t hangText="Value type:">uri</t>
<t hangText="Cardinality:">*</t>
<t hangText="Special notes:">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 <xref
target="RFC3986"/> and/or other information referencing the
vCard to which the information pertains. When directory information is
available from more than one source, the sending entity can pick what
it considers to be the best source, or multiple SOURCE properties can
be included.</t>
<t hangText="ABNF:">
<figure>
<artwork>
SOURCE-param = "VALUE=uri" / pid-param / pref-param / altid-param
/ mediatype-param / any-param
SOURCE-value = URI
</artwork>
</figure>
</t>
<t hangText="Examples:">
<figure>
<artwork>
SOURCE:ldap://ldap.example.com/cn=Babs%20Jensen,%20o=Babsco,%20c=US
SOURCE:http://directory.example.com/addressbooks/jdoe/
Jean%20Dupont.vcf
</artwork>
</figure>
</t>
</list>
</t>
</section>
<section title="KIND" anchor="KIND">
<t>
<list style="hanging">
<t hangText="Purpose:">To specify the kind of object the vCard
represents.</t>
<t hangText="Value type:">A single text value.</t>
<t hangText="Cardinality:">*1</t>
<t hangText="Special notes:">The value may be one of the following:
<list style="hanging">
<t hangText=""individual"">for a vCard representing a
single person or entity. This is the default kind of vCard.</t>
<t hangText=""group"">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 members of the group, but it is not
required to. A group vCard without MEMBER properties can be
considered an abstract grouping, or one whose members are known
empirically (perhaps "IETF Participants" or "Republican U.S.
Senators").</t>
<t>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.</t>
<t hangText=""org"">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.</t>
<t>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.</t>
<t hangText=""location"">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").</t>
<t>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.</t>
<t hangText="An x-name.">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.</t>
<t hangText="An iana-token.">Additional values may be registered
with IANA (see <xref target="iana_values"/>). A new value's
specification document MUST specify which properties make sense
for that new kind of vCard and which do not.</t>
</list>
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 x-name or iana-token
that the implementation does not support), the implementation SHOULD
act in a neutral way, which usually means treating the vCard as
though its kind were "individual". The presence of MEMBER
properties MAY, however, be taken as an indication that the unknown
kind is an extension of "group".</t>
<t>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 icons for the
different kinds; a client might use an outline of a single person to
represent an "individual", an outline of multiple people to
represent a "group", and so on. Alternatively, or in addition, a
client might choose to segregate different kinds of vCards to
different panes, tabs, or selections in the user interface.</t>
<t>Some clients might also make functional distinctions among the
kinds, ignoring "location" vCards for some purposes and considering
only "location" vCards for others.</t>
<t>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
implementors need to consider.</t>
<t hangText="ABNF:">
<figure>
<artwork>
KIND-param = "VALUE=text" / any-param
KIND-value = "individual" / "group" / "org" / "location"
/ iana-token / x-name
</artwork>
</figure>
</t>
<t hangText="Example:">
<figure>
<preamble>This represents someone named Jane Doe working in the
marketing department of the North American division of ABC
Inc.</preamble>
<artwork>
BEGIN:VCARD
VERSION:4.0
KIND:individual
FN:Jane Doe
ORG:ABC\, Inc.;North American Division;Marketing
END:VCARD
</artwork>
</figure>
<figure>
<preamble>This represents the department itself, commonly known as
ABC Marketing.</preamble>
<artwork>
BEGIN:VCARD
VERSION:4.0
KIND:org
FN:ABC Marketing
ORG:ABC\, Inc.;North American Division;Marketing
END:VCARD
</artwork>
</figure>
</t>
</list>
</t>
</section>
<section title="XML" anchor="XML">
<t>
<list style="hanging">
<t hangText="Purpose:">To include extended XML-encoded vCard data in a
plain vCard.</t>
<t hangText="Value type:">A single text value.</t>
<t hangText="Cardinality:">*</t>
<t hangText="Special notes:">The content of this property is a single
XML 1.0 <xref target="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 <xref target="I-D.ietf-vcarddav-vcardxml"/>.</t>
<t>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.</t>
<t>Support for this property is OPTIONAL, but implementations of this
specification MUST preserve instances of this property when
propagating vCards.</t>
<t>See <xref target="I-D.ietf-vcarddav-vcardxml"/> for more
information on the intended use of this property.</t>
<t hangText="ABNF:">
<figure>
<artwork>
XML-param = "VALUE=text" / altid-param
XML-value = text
</artwork>
</figure>
</t>
</list>
</t>
</section>
</section>
<section title="Identification Properties">
<t>These types are used to capture information associated with the
identification and naming of the entity associated with the vCard.</t>
<section title="FN" anchor="FN">
<t>
<list style='hanging'>
<t hangText='Purpose:'>To specify the formatted text corresponding to
the name of the object the vCard represents.</t>
<t hangText='Value type:'>A single text value.</t>
<t hangText="Cardinality:">1*</t>
<t hangText='Special notes:'>This property is based on the semantics
of the X.520 Common Name attribute. The property MUST be present in
the vCard object.</t>
<t hangText="ABNF:">
<figure>
<artwork>
FN-param = "VALUE=text" / type-param / language-param / altid-param
/ pid-param / pref-param / any-param
FN-value = text
</artwork>
</figure>
</t>
<t hangText="Example:">
<figure>
<artwork>
FN:Mr. John Q. Public\, Esq.
</artwork>
</figure>
</t>
</list>
</t>
</section>
<section title="N" anchor="N">
<t>
<list style='hanging'>
<t hangText='Purpose:'>To specify the components of the name of the
object the vCard represents.</t>
<t hangText='Value type:'>A single structured text value. Each component
can have multiple values.</t>
<t hangText="Cardinality:">*1</t>
<t hangText='Special note:'>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 SEMI-COLON character (ASCII
decimal 59). Individual text components can include multiple text
values separated by the COMMA character (ASCII decimal 44). This
property is based on the semantics of the X.520 individual name
attributes. The property SHOULD be present in the vCard object when
the name of the object the vCard represents follows the X.520
model.</t> <t>The SORT-AS parameter MAY be applied to this
property.</t>
<t hangText="ABNF:">
<figure>
<artwork>
N-param = "VALUE=text" / sort-as-param / language-param
/ altid-param / any-param
N-value = list-component 4(";" list-component)
</artwork>
</figure>
</t>
<t hangText="Examples:">
<figure>
<artwork>
N:Public;John;Quinlan;Mr.;Esq.
N:Stevenson;John;Philip,Paul;Dr.;Jr.,M.D.,A.C.P.
</artwork>
</figure>
</t>
</list>
</t>
</section>
<section title="NICKNAME" anchor="NICKNAME">
<t>
<list style='hanging'>
<t hangText='Purpose:'>To specify the text corresponding to the nickname
of the object the vCard represents.</t>
<t hangText='Value type:'>One or more text values separated by a COMMA
character (ASCII decimal 44).</t>
<t hangText="Cardinality:">*</t>
<t hangText='Special note:'>The nickname is the descriptive name given
instead of or in addition to the one belonging to a 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.</t>
<t hangText="ABNF:">
<figure>
<artwork>
NICKNAME-param = "VALUE=text" / type-param / language-param
/ altid-param / pid-param / pref-param / any-param
NICKNAME-value = text-list
</artwork>
</figure>
</t>
<t hangText="Examples:">
<figure>
<artwork>
NICKNAME:Robbie
NICKNAME:Jim,Jimmie
NICKNAME;TYPE=work:Boss
</artwork>
</figure>
</t>
</list>
</t>
</section>
<section title="PHOTO" anchor="PHOTO">
<t>
<list style='hanging'>
<t hangText='Purpose:'>To specify an image or photograph information
that annotates some aspect of the object the vCard represents.</t>
<t hangText='Value type:'>A single URI.</t>
<t hangText="Cardinality:">*</t>
<t hangText="ABNF:">
<figure>
<artwork>
PHOTO-param = "VALUE=uri" / altid-param / type-param
/ mediatype-param
PHOTO-value = URI
</artwork>
</figure>
</t>
<t hangText="Examples:">
<figure>
<artwork>
PHOTO:http://www.example.com/pub/photos/jqpublic.gif
PHOTO:data:image/jpeg;base64,MIICajCCAdOgAwIBAgICBEUwDQYJKoZIhv
AQEEBQAwdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05ldHNjYXBlIENvbW11bm
ljYXRpb25zIENvcnBvcmF0aW9uMRwwGgYDVQQLExNJbmZvcm1hdGlvbiBTeXN0
<...remainder of base64-encoded data...>
</artwork>
</figure>
</t>
</list>
</t>
</section>
<section title="BDAY" anchor="BDAY">
<t>
<list style='hanging'>
<t hangText='Purpose:'>To specify the birth date of the object the vCard
represents.</t>
<t hangText='Value type:'>The default is a single date-and-or-time
value. It can also be reset to a single text value.</t>
<t hangText="Cardinality:">*1</t>
<t hangText="ABNF:">
<figure>
<artwork>
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.
</artwork>
</figure>
</t>
<t hangText="Examples:">
<figure>
<artwork>
BDAY:19960415
BDAY:--0415
BDAY;19531015T231000Z
BDAY;VALUE=text:circa 1800
</artwork>
</figure>
</t>
</list>
</t>
</section>
<section title="ANNIVERSARY" anchor="ANNIVERSARY">
<t>
<list style="hanging">
<t hangText="Purpose:">The date of marriage, or equivalent, of the
object the vCard represents.</t>
<t hangText='Value type:'>The default is a single date-and-or-time
value. It can also be reset to a single text value.</t>
<t hangText="Cardinality:">*1</t>
<t hangText="ABNF:">
<figure>
<artwork>
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.
</artwork>
</figure>
</t>
<t hangText="Examples:">
<figure>
<artwork>
ANNIVERSARY:19960415
</artwork>
</figure>
</t>
</list>
</t>
</section>
<section title="GENDER" anchor="GENDER">
<t>
<list style="hanging">
<t hangText='Purpose:'>To specify the components of the sex and gender
identity of the object the vCard represents.</t>
<t hangText='Value type:'>A single structured value with two
components. Each component has a single text value.</t>
<t hangText="Cardinality:">*1</t>
<t hangText='Special notes:'>The components correspond, in sequence,
to the sex (biological), and gender identity. Each component is
optional.
<list style="hanging">
<t hangText="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".</t>
<t hangText="Gender identity component:">Free-form text.</t>
</list>
</t>
<t hangText="ABNF:">
<figure>
<artwork>
GENDER-param = "VALUE=text" / any-param
GENDER-value = sex [";" text]
sex = "" / "M" / "F" / "O" / "N" / "U"
</artwork>
</figure>
</t>
<t hangText="Examples:">
<figure>
<artwork>
GENDER:M
GENDER:F
GENDER:M;Fellow
GENDER:F;Bird
GENDER:O;intersex
GENDER:;queer
</artwork>
</figure>
</t>
</list>
</t>
</section>
</section>
<section title="Delivery Addressing Properties" anchor="oldsection_3_2">
<t>
These types are concerned with information related to the delivery addressing or label for the vCard object.
</t>
<section title="ADR" anchor="ADR">
<t>
<list style='hanging'>
<t hangText='Purpose:'>To specify the components of the delivery
address for the vCard object.</t>
<t hangText='Value type:'>A single structured text value, separated by
the SEMI-COLON character (ASCII decimal 59).</t>
<t hangText="Cardinality:">*</t>
<t hangText='Special notes:'>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 extended
address (e.g. apartment or suite number); the street address; the
locality (e.g., city); the region (e.g., state or province); the
postal code; the country name (full name in the language specified
in <xref target="LANGUAGE"/>). When a component value is missing,
the associated component separator MUST
still be specified.</t>
<t>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.</t>
<t>The text components are separated by the SEMI-COLON character
(ASCII decimal 59). 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
(ASCII decimal 44).</t>
<t>The property can include the "PREF" parameter to indicate the
preferred delivery address when more than one address is
specified.</t>
<t>The GEO and TZ parameters MAY be used with this property.</t>
<t>The property can also include a "LABEL" parameter to present a
delivery 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.</t>
<t hangText="ABNF:">
<figure>
<artwork>
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
</artwork>
</figure>
</t>
</list>
</t>
<t>
Example: In this example the post office box and the extended address are absent.
</t>
<figure>
<artwork>
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.
</artwork>
</figure>
</section>
</section>
<section title="Communications Properties" anchor="oldsection_3_3">
<t>
These properties describe information about how to communicate with the
object the vCard represents.
</t>
<section title="TEL" anchor="TEL">
<t>
<list style='hanging'>
<t hangText='Purpose:'>To specify the telephone number for telephony
communication with the object the vCard represents.</t>
<t hangText='Value type:'>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 <xref target="RFC3966"/>, but other schemes
MAY be used.</t>
<t hangText="Cardinality:">*</t>
<t hangText='Special notes:'>This property is based on the X.520
Telephone Number attribute.</t>
<t>The property can include the "PREF" parameter to indicate a
preferred-use telephone number.</t>
<t>The property can include the parameter "TYPE" to specify intended
use for the telephone number. The predefined values for the TYPE
parameter are:</t>
</list>
</t>
<texttable>
<ttcol align="left">Value</ttcol>
<ttcol align="left">Description</ttcol>
<c>text</c>
<c>Indicates that the telephone number supports text messages
(SMS).</c>
<c>voice</c>
<c>Indicates a voice telephone number.</c>
<c>fax</c>
<c>Indicates a facsimile telephone number.</c>
<c>cell</c>
<c>Indicates a cellular or mobile telephone number.</c>
<c>video</c>
<c>Indicates a video conferencing telephone number.</c>
<c>pager</c>
<c>Indicates a paging device telephone number.</c>
<c>textphone</c>
<c>Indicates a telecommunication device for people with hearing or
speech difficulties..</c>
</texttable>
<t>
<list style='hanging'>
<t>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".</t>
<t>If this property's value is a URI that can also be used for instant
messaging, the IMPP (<xref target="IMPP"/>) property SHOULD be used
in addition to this property.</t>
<t hangText="ABNF:">
<figure>
<artwork>
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.
</artwork>
</figure>
</t>
</list>
</t>
<t>
Example:
</t>
<figure>
<artwork>
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
</artwork>
</figure>
</section>
<section title="EMAIL" anchor="EMAIL">
<t>
<list style='hanging'>
<t hangText='Purpose:'>To specify the electronic mail address for
communication with the object the vCard represents.</t>
<t hangText='Value type:'>A single text value.</t>
<t hangText="Cardinality:">*</t>
<t hangText='Special notes:'>The property can include tye "PREF"
parameter to indicate a preferred-use email address when more than
one is specified.</t>
<t>Even though the value is free-form UTF-8 text, it is likely to be
interpreted by an MUA as an "addr-spec", as defined in <xref
target="RFC5322"/>, section 3.4.1. Readers should also be aware of
the current work toward internationalized email addresses <xref
target="I-D.ietf-eai-rfc5335bis"/>.</t>
<t hangText="ABNF:">
<figure>
<artwork>
EMAIL-param = "VALUE=text" / pid-param / pref-param / type-param
/ altid-param / any-param
EMAIL-value = text
</artwork>
</figure>
</t>
</list>
</t>
<t>
Example:
</t>
<figure>
<artwork>
EMAIL;TYPE=work:jqpublic@xyz.example.com
EMAIL;PREF=1:jane_doe@example.com
</artwork>
</figure>
</section>
<section title="IMPP" anchor="IMPP">
<t>
<list style="hanging">
<t hangText="Purpose:">To specify the URI for instant messaging and
presence protocol communications with the object the vCard
represents.</t>
<t hangText="Value type:">A single URI.</t>
<t hangText="Cardinality:">*</t>
<t hangText="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.</t>
<t>If this property's value is a URI that can be used for voice and/or
video, the TEL property (<xref target="TEL"/>) SHOULD be used in
addition to this property.</t>
<t>This property is adapted from <xref target="RFC4770"/>, which is
made obsolete by this document.</t>
<t hangText="ABNF:">
<figure>
<artwork>
IMPP-param = "VALUE=uri" / pid-param / pref-param / type-param
/ mediatype-param / altid-param / any-param
IMPP-value = URI
</artwork>
</figure>
</t>
<t hangText="Example:">
<figure>
<artwork>
IMPP;PREF=1:xmpp:alice@example.com
</artwork>
</figure>
</t>
</list>
</t>
</section>
<section title="LANG" anchor="LANG">
<t>
<list style="hanging">
<t hangText="Purpose:">To specify the language(s) that may be used
for contacting the entity associated with the vCard.</t>
<t hangText="Value type:">A single language-tag value.</t>
<t hangText="Cardinality:">*</t>
<t hangText="ABNF:">
<figure>
<artwork>
LANG-param = "VALUE=language-tag" / pid-param / pref-param
/ altid-param / type-param / any-param
LANG-value = Language-Tag
</artwork>
</figure>
</t>
<t hangText="Example:">
<figure>
<artwork>
LANG;TYPE=work;PREF=1:en
LANG;TYPE=work;PREF=2:fr
LANG;TYPE=home:fr
</artwork>
</figure>
</t>
</list>
</t>
</section>
</section>
<section title="Geographical Properties" anchor="oldsection_3_4">
<t>
These properties are concerned with information associated with
geographical positions or regions associated with the object the vCard
represents.
</t>
<section title="TZ" anchor="TZ">
<t>
<list style='hanging'>
<t hangText='Purpose:'>To specify information related to the time zone
of the object the vCard represents.</t>
<t hangText='Value type:'>The default is a single text value. It can
also be reset to a single URI or utc-offset value.</t>
<t hangText="Cardinality:">*</t>
<t hangText='Special notes:'>It is expected that names from the
public-domain Olson database <xref target="TZ-DB"/> will be used, but
this is not a restriction.</t>
<t>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.</t>
<t>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.</t>
<t hangText="ABNF:">
<figure>
<artwork>
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
</artwork>
</figure>
</t>
</list>
</t>
<t>
Examples:
</t>
<figure>
<artwork>
TZ:Raleigh/North America
TZ;VALUE=utc-offset:-0500
; Note: utc-offset format is NOT RECOMMENDED.
</artwork>
</figure>
</section>
<section title="GEO" anchor="GEO">
<t>
<list style='hanging'>
<t hangText='Purpose:'>To specify information related to the global
positioning of the object the vCard represents.</t>
<t hangText='Value type:'>A single URI.</t>
<t hangText="Cardinality:">*</t>
<t hangText='Special notes:'>The "geo" URI scheme <xref
target="RFC5870"/> is particularly well-suited for
this property, but other schemes MAY be used.</t>
<t hangText="ABNF:">
<figure>
<artwork>
GEO-param = "VALUE=uri" / pid-param / pref-param / type-param
/ mediatype-param / altid-param / any-param
GEO-value = URI
</artwork>
</figure>
</t>
</list>
</t>
<t>
Example:
</t>
<figure>
<artwork>
GEO:geo:37.386013,-122.082932
</artwork>
</figure>
</section>
</section>
<section title="Organizational Properties" anchor="oldsection_3_5">
<t>
These properties are concerned with information associated with
characteristics of the organization or organizational units of the object
that the vCard represents.
</t>
<section title="TITLE" anchor="TITLE">
<t>
<list style='hanging'>
<t hangText='Purpose:'>To specify the position or job of the object
the vCard represents.</t>
<t hangText='Value type:'>A single text value.</t>
<t hangText="Cardinality:">*</t>
<t hangText="Special notes:">This property is based on the X.520 Title
attribute.</t>
<t hangText="ABNF:">
<figure>
<artwork>
TITLE-param = "VALUE=text" / language-param / pid-param
/ pref-param / altid-param / type-param / any-param
TITLE-value = text
</artwork>
</figure>
</t>
</list>
</t>
<t>
Example:
</t>
<figure>
<artwork>
TITLE:Research Scientist
</artwork>
</figure>
</section>
<section title="ROLE" anchor="ROLE">
<t>
<list style='hanging'>
<t hangText='Purpose:'>To specify the function or part played in a
particular situation by the object the vCard represents.</t>
<t hangText='Value type:'>A single text value.</t>
<t hangText="Cardinality:">*</t>
<t hangText='Special notes:'>This property is based on the X.520 Business
Category explanatory attribute. 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.</t>
<t hangText="ABNF:">
<figure>
<artwork>
ROLE-param = "VALUE=text" / language-param / pid-param / pref-param
/ type-param / altid-param / any-param
ROLE-value = text
</artwork>
</figure>
</t>
</list>
</t>
<t>
Example:
</t>
<figure>
<artwork>
ROLE:Project Leader
</artwork>
</figure>
</section>
<section title="LOGO" anchor="LOGO">
<t>
<list style='hanging'>
<t hangText='Purpose:'>To specify a graphic image of a logo associated
with the object the vCard represents.</t>
<t hangText='Value type:'>A single URI.</t>
<t hangText="Cardinality:">*</t>
<t hangText="ABNF:">
<figure>
<artwork>
LOGO-param = "VALUE=uri" / language-param / pid-param / pref-param
/ type-param / mediatype-param / altid-param / any-param
LOGO-value = URI
</artwork>
</figure>
</t>
</list>
</t>
<t>
Examples:
</t>
<figure>
<artwork>
LOGO:http://www.example.com/pub/logos/abccorp.jpg
LOGO:data:image/jpeg;base64,MIICajCCAdOgAwIBAgICBEUwDQYJKoZIhvc
AQEEBQAwdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05ldHNjYXBlIENvbW11bm
ljYXRpb25zIENvcnBvcmF0aW9uMRwwGgYDVQQLExNJbmZvcm1hdGlvbiBTeXN0
<...the remainder of base64-encoded data...>
</artwork>
</figure>
</section>
<section title="ORG" anchor="ORG">
<t>
<list style='hanging'>
<t hangText='Purpose:'>To specify the organizational name and units
associated with the vCard.</t>
<t hangText='Value type:'>A single structured text value consisting of
components separated by the SEMI-COLON character (ASCII decimal
59).</t>
<t hangText="Cardinality:">*</t>
<t hangText='Special notes:'>The property is based on the X.520
Organization Name and Organization Unit attributes. The property value
is a structured type consisting of the organization name, followed
by zero or more levels of organizational unit names.</t>
<t>The SORT-AS parameter MAY be applied to this property.</t>
<t hangText="ABNF:">
<figure>
<artwork>
ORG-param = "VALUE=text" / sort-as-param / language-param
/ pid-param / pref-param / altid-param / type-param
/ any-param
ORG-value = component *(";" component)
</artwork>
</figure>
</t>
</list>
</t>
<t>
Example: A property value consisting of an organizational name,
organizational unit #1 name and organizational unit #2 name.
</t>
<figure>
<artwork>
ORG:ABC\, Inc.;North American Division;Marketing
</artwork>
</figure>
</section>
<section title="MEMBER" anchor="MEMBER">
<t>
<list style="hanging">
<t hangText="Purpose:">To include a member in the group this vCard
represents.</t>
<t hangText="Value type:">A single URI. It MAY refer to something other
than a vCard object. For example, an e-mail distribution list could
employ the "mailto" URI scheme <xref target="RFC6068"/> for
efficiency.</t>
<t hangText="Cardinality:">*</t>
<t hangText="Special notes:">This property MUST NOT be present unless
the value of the KIND property is "group".</t>
<t hangText="ABNF:">
<figure>
<artwork>
MEMBER-param = "VALUE=uri" / pid-param / pref-param / altid-param
/ mediatype-param / any-param
MEMBER-value = URI
</artwork>
</figure>
</t>
</list>
</t>
<t>Examples:</t>
<figure>
<artwork>
BEGIN:VCARD
VERSION:4.0
KIND:group
FN:The Doe family
MEMBER:urn:uuid:03a0e51f-d1aa-4385-8a53-e29025acd8af
MEMBER:urn:uuid:b8767877-b4a1-4c70-9acc-505d3819e519
END:VCARD
BEGIN:VCARD
VERSION:4.0
FN:John Doe
UID:urn:uuid:03a0e51f-d1aa-4385-8a53-e29025acd8af
END:VCARD
BEGIN:VCARD
VERSION:4.0
FN:Jane Doe
UID:urn:uuid:b8767877-b4a1-4c70-9acc-505d3819e519
END:VCARD
</artwork>
</figure>
<figure>
<artwork>
BEGIN:VCARD
VERSION:4.0
KIND:group
FN:Funky distribution list
MEMBER:mailto:subscriber1@example.com
MEMBER:xmpp:subscriber2@example.com
MEMBER:sip:subscriber3@example.com
MEMBER:tel:+1-418-555-5555
END:VCARD
</artwork>
</figure>
</section>
<section title="RELATED" anchor="RELATED">
<t>
<list style="hanging">
<t hangText="Purpose:">To specify a relationship between another
entity and the entity represented by this vCard.</t>
<t hangText="Value type:">A single URI. It can also be reset to a
single text value. The text value can be used to specify textual
information.</t>
<t hangText="Cardinality:">*</t>
<t hangText="Special notes:">The TYPE parameter MAY be used to
characterize the related entity. It contains a comma-separated
list of values that are registered from IANA as described in <xref
target="iana_registration"/>. The registry is pre-populated with
the values defined in <xref target="xfn"/>. This document also
specifies two additional values:
<list style="hanging">
<t hangText="agent:">an entity who may sometimes act on behalf of
the entity associated with the vCard.</t>
<t hangText="emergency:">indicates an emergency contact</t>
</list>
</t>
<t hangText="ABNF:">
<figure>
<artwork>
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"
</artwork>
</figure>
</t>
</list>
</t>
<figure>
<preamble>Examples:</preamble>
<artwork>
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
Doe for any inquiries.
</artwork>
</figure>
</section>
</section>
<section title="Explanatory Properties" anchor="oldsection_3_6">
<t>
These properties are concerned with additional explanations, such as that
related to informational notes or revisions specific to the vCard.
</t>
<section title="CATEGORIES" anchor="CATEGORIES">
<t>
<list style='hanging'>
<t hangText='Purpose:'>To specify application category information
about the vCard. Also known as "tags".</t>
<t hangText='Value type:'>One or more text values separated by a COMMA
character (ASCII decimal 44).</t>
<t hangText="Cardinality:">*</t>
<t hangText="ABNF:">
<figure>
<artwork>
CATEGORIES-param = "VALUE=text" / pid-param / pref-param
/ type-param / altid-param / any-param
CATEGORIES-value = text-list
</artwork>
</figure>
</t>
</list>
</t>
<t>
Example:
</t>
<figure>
<artwork>
CATEGORIES:TRAVEL AGENT
CATEGORIES:INTERNET,IETF,INDUSTRY,INFORMATION TECHNOLOGY
</artwork>
</figure>
</section>
<section title="NOTE" anchor="NOTE">
<t>
<list style='hanging'>
<t hangText='Purpose:'>To specify supplemental information or a
comment that is associated with the vCard.</t>
<t hangText='Value type:'>A single text value.</t>
<t hangText="Cardinality:">*</t>
<t hangText='Special notes:'>The property is based on the X.520
Description attribute.</t>
<t hangText="ABNF:">
<figure>
<artwork>
NOTE-param = "VALUE=text" / language-param / pid-param / pref-param
/ type-param / altid-param / any-param
NOTE-value = text
</artwork>
</figure>
</t>
</list>
</t>
<t>
Example:
</t>
<figure>
<artwork>
NOTE:This fax number is operational 0800 to 1715
EST\, Mon-Fri.
</artwork>
</figure>
</section>
<section title="PRODID" anchor="PRODID">
<t>
<list style='hanging'>
<t hangText='Purpose:'>To specify the identifier for the product that
created the vCard object.</t>
<t hangText='Type value:'>A single text value.</t>
<t hangText="Cardinality:">*1</t>
<t hangText='Special notes:'>Implementations SHOULD use a method such
as that specified for Formal Public Identifiers in <xref
target="ISO9070"/> or for Universal Resource Names in <xref
target="RFC3406"/> to ensure that the text value is unique.</t>
<t hangText="ABNF:">
<figure>
<artwork>
PRODID-param = "VALUE=text" / any-param
PRODID-value = text
</artwork>
</figure>
</t>
</list>
</t>
<t>
Example:
</t>
<figure>
<artwork>
PRODID:-//ONLINE DIRECTORY//NONSGML Version 1//EN
</artwork>
</figure>
</section>
<section title="REV" anchor="REV">
<t>
<list style='hanging'>
<t hangText='Purpose:'>To specify revision information about the
current vCard.</t>
<t hangText='Value type:'>A single timestamp value.</t>
<t hangText="Cardinality:">*1</t>
<t hangText='Special notes:'>The value distinguishes the current
revision of the information in this vCard for other renditions of
the information.</t>
<t hangText="ABNF:">
<figure>
<artwork>
REV-param = "VALUE=timestamp" / any-param
REV-value = timestamp
</artwork>
</figure>
</t>
</list>
</t>
<t>
Example:
</t>
<figure>
<artwork>
REV:19951031T222710Z
</artwork>
</figure>
</section>
<section title="SOUND" anchor="SOUND">
<t>
<list style='hanging'>
<t hangText='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.</t>
<t hangText='Value type:'>A single URI.</t>
<t hangText="Cardinality:">*</t>
<t hangText="ABNF:">
<figure>
<artwork>
SOUND-param = "VALUE=uri" / language-param / pid-param / pref-param
/ type-param / mediatype-param / altid-param
/ any-param
SOUND-value = URI
</artwork>
</figure>
</t>
</list>
</t>
<t>
Example:
</t>
<figure>
<artwork>
SOUND:CID:JOHNQPUBLIC.part8.19960229T080000.xyzMail@example.com
SOUND:data:audio/basic;base64,MIICajCCAdOgAwIBAgICBEUwDQYJKoZIh
AQEEBQAwdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05ldHNjYXBlIENvbW11bm
ljYXRpb25zIENvcnBvcmF0aW9uMRwwGgYDVQQLExNJbmZvcm1hdGlvbiBTeXN0
<...the remainder of base64-encoded data...>
</artwork>
</figure>
</section>
<section title="UID" anchor="UID">
<t>
<list style='hanging'>
<t hangText='Purpose:'>To specify a value that represents a globally
unique identifier corresponding to the entity
associated with the vCard.</t>
<t hangText='Value type:'>A single URI value. It MAY also be reset to
free-form text.</t>
<t hangText="Cardinality:">*1</t>
<t hangText='Special notes:'>This property is used to uniquely
identify the object that the vCard represents. The "uuid" URN
namespace defined in <xref target="RFC4122"/> is particularly
well-suited to this task, but other URI schemes MAY be used.
Free-form text MAY also be used.</t>
<t hangText="ABNF:">
<figure>
<artwork>
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
</artwork>
</figure>
</t>
</list>
</t>
<t>
Example:
</t>
<figure>
<artwork>
UID:urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6
</artwork>
</figure>
</section>
<section title="CLIENTPIDMAP" anchor="CLIENTPIDMAP">
<t>
<list style="hanging">
<t hangText="Purpose:">To give a global meaning to a local PID source
identifier.</t>
<t hangText="Value type:">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 <xref target="RFC4122"/> is particularly
well-suited to this task, but other URI schemes MAY be used.</t>
<t hangText="Cardinality:">*</t>
<t hangText="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 <xref
target="synchronization"/> for more details on the usage of
CLIENTPIDMAP.</t>
<t>PID source identifiers MUST be strictly positive. Zero is not
allowed.</t>
<t>As a special exception, the PID parameter MUST NOT be applied to
this property.</t>
<t hangText="ABNF:">
<figure>
<artwork>
CLIENTPIDMAP-param = any-param
CLIENTPIDMAP-value = 1*DIGIT ";" URI
</artwork>
</figure>
</t>
</list>
</t>
<figure>
<preamble>
Example:
</preamble>
<artwork>
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
CLIENTPIDMAP:2;urn:uuid:d89c9c7a-2e1b-4832-82de-7e992d95faa5
</artwork>
</figure>
</section>
<section title="URL" anchor="URL">
<t>
<list style='hanging'>
<t hangText='Purpose:'>To specify a uniform resource locator
associated with the object that the vCard refers to. Examples for
individuals include personal web sites, blogs, and social networking
site identifiers.</t>
<t hangText="Cardinality:">*</t>
<t hangText='Value type:'>A single uri value.</t>
<t hangText="ABNF:">
<figure>
<artwork>
URL-param = "VALUE=uri" / pid-param / pref-param / type-param
/ mediatype-param / altid-param / any-param
URL-value = URI
</artwork>
</figure>
</t>
</list>
</t>
<t>
Example:
</t>
<figure>
<artwork>
URL:http://example.org/restaurant.french/~chezchic.html
</artwork>
</figure>
</section>
<section title="VERSION" anchor="VERSION">
<t>
<list style='hanging'>
<t hangText='Purpose:'>To specify the version of the vCard
specification used to format this vCard.</t>
<t hangText='Value type:'>A single text value.</t>
<t hangText="Cardinality:">1</t>
<t hangText='Special notes:'>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.</t>
<t hangText="ABNF:">
<figure>
<artwork>
VERSION-param = "VALUE=text" / any-param
VERSION-value = "4.0"
</artwork>
</figure>
</t>
</list>
</t>
<t>
Example:
</t>
<figure>
<artwork>
VERSION:4.0
</artwork>
</figure>
</section>
</section>
<section title="Security Properties" anchor="oldsection_3_7">
<t>
These properties are concerned with the security of communication pathways or
access to the vCard.
</t>
<section title="KEY" anchor="KEY">
<t>
<list style='hanging'>
<t hangText='Purpose:'>To specify a public key or authentication
certificate associated with the object that the vCard
represents.</t>
<t hangText='Value type:'>A single URI. It can also be reset to a
text value.</t>
<t hangText="Cardinality:">*</t>
<t hangText="ABNF:">
<figure>
<artwork>
KEY-param = KEY-uri-param / KEY-text-param
KEY-value = KEY-uri-value / KEY-text-value
; Value and parameter MUST match.
KEY-uri-param = "VALUE=uri" / mediatype-param
KEY-uri-value = URI
KEY-text-param = "VALUE=text"
KEY-text-value = text
KEY-param =/ altid-param / pid-param / pref-param / type-param
/ any-param
</artwork>
</figure>
</t>
</list>
</t>
<t>
Examples:
</t>
<figure>
<artwork>
KEY:http://www.example.com/keys/jdoe
KEY;MEDIATYPE=application/pgp-keys:ftp://example.com/keys/jdoe
KEY:data:application/pgp-keys;base64,MIICajCCAdOgAwIBAgICBE
UwDQYJKoZIhvcNAQEEBQAwdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05l
<... remainder of base64-encoded data ...>
</artwork>
</figure>
</section>
</section>
<section title="Calendar Properties">
<t>These properties are further specified in <xref target="RFC2739"/>.</t>
<section title="FBURL" anchor="FBURL">
<t>
<list style="hanging">
<t hangText="Purpose:">To specify the URI for the busy time associated
with the object that the vCard represents.</t>
<t hangText="Value type:">A single URI value.</t>
<t hangText="Cardinality:">*</t>
<t hangText="Special notes:">Where multiple FBURL properties are
specified, the default FBURL property is indicated with the PREF
parameter. The FTP <xref target="RFC1738"/> or HTTP <xref
target="RFC2616"/> type of URI points to an iCalendar <xref
target="RFC5545"/> object associated with a snapshot of the next
few weeks or months of busy time data. If the iCalendar object is
represented as a file or document, its file extension should be
".ifb".</t>
<t hangText="ABNF:">
<figure>
<artwork>
FBURL-param = "VALUE=uri" / pid-param / pref-param / type-param
/ mediatype-param / altid-param / any-param
FBURL-value = URI
</artwork>
</figure>
</t>
<t hangText="Examples:">
<figure>
<artwork>
FBURL;PREF=1:http://www.example.com/busy/janedoe
FBURL;MEDIATYPE=text/calendar:ftp://example.com/busy/project-a.ifb
</artwork>
</figure>
</t>
</list>
</t>
</section>
<section title="CALADRURI" anchor="CALADRURI">
<t>
<list style="hanging">
<t hangText="Purpose:">To specify the calendar user address <xref
target="RFC5545"/> to which a scheduling request <xref
target="RFC5546"/> should be sent for the object represented by
the vCard.</t>
<t hangText="Value type:">A single URI value.</t>
<t hangText="Cardinality:">*</t>
<t hangText="Special notes:">Where multiple CALADRURI properties are
specified, the default CALADRURI property is indicated with the PREF
parameter.</t>
<t hangText="ABNF:">
<figure>
<artwork>
CALADRURI-param = "VALUE=uri" / pid-param / pref-param / type-param
/ mediatype-param / altid-param / any-param
CALADRURI-value = URI
</artwork>
</figure>
</t>
<t hangText="Example:">
<figure>
<artwork>
CALADRURI;PREF=1:mailto:janedoe@example.com
CALADRURI:http://example.com/calendar/jdoe
</artwork>
</figure>
</t>
</list>
</t>
</section>
<section title="CALURI" anchor="CALURI">
<t>
<list style="hanging">
<t hangText="Purpose:">To specify the URI for a calendar associated
with the object represented by the vCard.</t>
<t hangText="Value type:">A single URI value.</t>
<t hangText="Cardinality:">*</t>
<t hangText="Special notes:">Where multiple CALURI properties are
specified, the default CALURI property is indicated with the PREF
parameter. The property should contain a URI pointing to an
iCalendar <xref target="RFC5545"/> object associated with a snapshot
of the user's calendar store. If the iCalendar object is represented
as a file or document, its file extension should be ".ics".</t>
<t hangText="ABNF:">
<figure>
<artwork>
CALURI-param = "VALUE=uri" / pid-param / pref-param / type-param
/ mediatype-param / altid-param / any-param
CALURI-value = URI
</artwork>
</figure>
</t>
<t hangText="Examples:">
<figure>
<artwork>
CALURI;PREF=1:http://cal.example.com/calA
CALURI;MEDIATYPE=text/calendar:ftp://ftp.example.com/calA.ics
</artwork>
</figure>
</t>
</list>
</t>
</section>
</section>
<section title="Extended Properties and Parameters" anchor="oldsection_3_8">
<t>
The properties and parameters defined by this document can be extended.
Non-standard, private properties and parameters with a name starting with
"X-" may be defined bilaterally between two cooperating agents without
outside registration or standardization.
</t>
</section>
</section>
<section title="Synchronization" anchor="synchronization">
<t>vCard data often needs to be synchronized between devices. In this context,
synchronization is defined as the intelligent merging of two representations
of the same object. vCard 4.0 includes mechanisms to aid this process.</t>
<section title="Mechanisms">
<t>Two mechanisms are available: the UID property is used to match
multiple instances of the same vCard, while the PID parameter is used to
match multiple instances of the same property.</t>
<t>The term "matching" is used here to mean recognizing that two instances
are in fact representations of the same object. For example, a single
vCard that is shared with someone results in two vCard instances. After
they have evolved separately, they still represent the same object, and
therefore may be matched by a synchronization engine.</t>
<section title="Matching vCard Instances">
<t>vCard instances for which the UID properties (<xref target="UID"/>) are
equivalent MUST be matched. Equivalence is determined as specified in
<xref target="RFC3986"/>, Section 6.</t>
<t>In all other cases, vCard instances MAY be matched at the discretion of
the synchronization engine.</t>
</section>
<section title="Matching Property Instances" anchor="propmatching">
<t>Property instances belonging to unmatched vCards MUST NOT be
matched.</t>
<t>Property instances whose name (e.g. EMAIL, TEL, etc.) is not the same
MUST NOT be matched.</t>
<t>Property instances whose name is CLIENTPIDMAP are handled separately
and MUST NOT be matched. The synchronization MUST ensure that there is
consistency of CLIENTPIDMAPs among matched vCard instances.</t>
<t>Property instances belonging to matched vCards, whose name is the same,
and whose maximum cardinality is 1 MUST be matched.</t>
<t>Property instances belonging to matched vCards, whose name is the same,
and whose PID parameters match MUST be matched. See <xref
target="pidmatching"/> for details on PID matching.</t>
<t>In all other cases, property instances MAY be matched at the discretion
of the synchronization engine.</t>
</section>
<section title="PID Matching" anchor="pidmatching">
<t>Two PID values for which the first fields are equivalent represent the
same local value.</t>
<t>Two PID values representing the same local value and for which the
second fields point to CLIENTPIDMAP properties whose second field URIs
are equivalent (as specified in <xref target="RFC3986"/>, Section 6)
also represent the same global value.</t>
<t>PID parameters for which at least one pair of their values represent
the same global value MUST be matched.</t>
<t>In all other cases, PID parameters MAY be matched at the discretion of
the synchronization engine.</t>
<figure>
<preamble>
For example, PID value "5.1", in the first vCard below, and PID value
"5.2", in the second vCard below, represent the same global value.
</preamble>
<artwork>
BEGIN:VCARD
VERSION:4.0
EMAIL;PID=4.2,5.1:jdoe@example.com
CLIENTPIDMAP:1;urn:uuid:3eef374e-7179-4196-a914-27358c3e6527
CLIENTPIDMAP:2;urn:uuid:42bcd5a7-1699-4514-87b4-056edf68e9cc
END:VCARD
BEGIN:VCARD
VERSION:4.0
EMAIL;PID=5.1,5.2:john@example.com
CLIENTPIDMAP:1;urn:uuid:0c75c629-6a8d-4d5e-a07f-1bb35846854d
CLIENTPIDMAP:2;urn:uuid:3eef374e-7179-4196-a914-27358c3e6527
END:VCARD
</artwork>
</figure>
</section>
</section>
<section title="Example">
<section title="Creation">
<t>The following simple vCard is first created on a given device.</t>
<figure>
<artwork>
BEGIN:VCARD
VERSION:4.0
UID:urn:uuid:4fbe8971-0bc3-424c-9c26-36c3e1eff6b1
FN;PID=1.1:J. Doe
N:Doe;J.;;;
EMAIL;PID=1.1:jdoe@example.com
CLIENTPIDMAP:1;urn:uuid:53e374d9-337e-4727-8803-a1e9c14e0556
END:VCARD
</artwork>
</figure>
<t>This new vCard is assigned the UID
"urn:uuid:4fbe8971-0bc3-424c-9c26-36c3e1eff6b1" by the creating device.
The FN and EMAIL properties are assigned the same local value of 1, and
this value is given global context by associating it with
"urn:uuid:53e374d9-337e-4727-8803-a1e9c14e0556", which represents the
creating device. We are at liberty to reuse the same local value since
instances of different properties will never be matched. The N property
has no PID because it is forbidden by its maximum cardinality of 1.</t>
</section>
<section title="Initial Sharing">
<t>This vCard is shared with a second device. Upon inspecting the UID
property, the second device understands that this is a new vCard
(i.e. unmatched) and thus the synchronization results in a simple
copy.</t>
</section>
<section title="Adding and Sharing a Property">
<t>A new phone number is created on the first device, then the vCard is
shared with the second device. This is what the second device
receives:</t>
<figure>
<artwork>
BEGIN:VCARD
VERSION:4.0
UID:urn:uuid:4fbe8971-0bc3-424c-9c26-36c3e1eff6b1
FN;PID=1.1:J. Doe
N:Doe;J.;;;
EMAIL;PID=1.1:jdoe@example.com
TEL;PID=1.1;VALUE=uri:tel:+1-555-555-5555
CLIENTPIDMAP:1;urn:uuid:53e374d9-337e-4727-8803-a1e9c14e0556
END:VCARD
</artwork>
</figure>
<t>Upon inspecting the UID property, the second device matches the vCard
it received to the vCard that it already has stored. It then starts
comparing the properties of the two vCards in same-named pairs.</t>
<t>The FN properties are matched because the PID parameters have the
same global value. Since the property value is the same, no update takes
place.</t>
<t>The N properties are matched automatically because their maximum
cardinality is 1. Since the property value is the same, no update takes
place.</t>
<t>The EMAIL properties are matched because the PID parameters have the
same global value. Since the property value is the same, no update takes
place.</t>
<t>The TEL property in the new vCard is not matched to any in the stored
vCard because no property in the stored vCard has the same name.
Therefore, this property is copied from the new vCard to the stored
vCard.</t>
<t>The CLIENTPIDMAP property is handled separately by the synchronization
engine. It ensures that it is consistent with the stored one. If it was
not, the results would be up to the synchronization engine, and thus
undefined by this document.</t>
</section>
<section title="Simultaneous Editing">
<t>A new email address and a new phone number are added to the vCard on
each of the two devices, and then a new synchronization event happens.
Here are the vCards that are communicated to each other:</t>
<figure>
<artwork>
BEGIN:VCARD
VERSION:4.0
UID:urn:uuid:4fbe8971-0bc3-424c-9c26-36c3e1eff6b1
FN;PID=1.1:J. Doe
N:Doe;J.;;;
EMAIL;PID=1.1:jdoe@example.com
EMAIL;PID=2.1:boss@example.com
TEL;PID=1.1;VALUE=uri:tel:+1-555-555-5555
TEL;PID=2.1;VALUE=uri:tel:+1-666-666-6666
CLIENTPIDMAP:1;urn:uuid:53e374d9-337e-4727-8803-a1e9c14e0556
END:VCARD
BEGIN:VCARD
VERSION:4.0
UID:urn:uuid:4fbe8971-0bc3-424c-9c26-36c3e1eff6b1
FN;PID=1.1:J. Doe
N:Doe;J.;;;
EMAIL;PID=1.1:jdoe@example.com
EMAIL;PID=2.2:ceo@example.com
TEL;PID=1.1;VALUE=uri:tel:+1-555-555-5555
TEL;PID=2.2;VALUE=uri:tel:+1-666-666-6666
CLIENTPIDMAP:1;urn:uuid:53e374d9-337e-4727-8803-a1e9c14e0556
CLIENTPIDMAP:2;urn:uuid:1f762d2b-03c4-4a83-9a03-75ff658a6eee
END:VCARD
</artwork>
</figure>
<t>On the first device, the same PID source identifier (1) is reused for
the new EMAIL and TEL properties. On the second device, a new source
identifier (2) is generated, and a corresponding CLIENTPIDMAP property
is created. It contains the second device's identifier,
"urn:uuid:1f762d2b-03c4-4a83-9a03-75ff658a6eee".</t>
<t>The new EMAIL properties are unmatched on both sides since the PID global
value is new in both cases. The sync thus results in a copy on both
sides.</t>
<t>Although the situation appears to be the same for the TEL properties,
in this case the synchronization engine is particularly smart and
matches the two new TEL properties even though their PID global values
are different. Note that in this case, the rules of section <xref
target="propmatching"/> state that two properties MAY be matched at
the discretion of the synchronization engine. Therefore, the two
properties are merged.</t>
<t>All this results in the following vCard which is stored on both
devices:</t>
<figure>
<artwork>
BEGIN:VCARD
VERSION:4.0
UID:urn:uuid:4fbe8971-0bc3-424c-9c26-36c3e1eff6b1
FN:J. Doe
N:Doe;J.;;;
EMAIL;PID=1.1:jdoe@example.com
EMAIL;PID=2.1:boss@example.com
EMAIL;PID=2.2:ceo@example.com
TEL;PID=1.1;VALUE=uri:tel:+1-555-555-5555
TEL;PID=2.1,2.2;VALUE=uri:tel:+1-666-666-6666
CLIENTPIDMAP:1;urn:uuid:53e374d9-337e-4727-8803-a1e9c14e0556
CLIENTPIDMAP:2;urn:uuid:1f762d2b-03c4-4a83-9a03-75ff658a6eee
END:VCARD
</artwork>
</figure>
</section>
<section title="Global Context Simplification">
<t>The two devices finish their synchronization procedure by simplifying
their global contexts. Since they haven't talked to any other device,
the following vCard is for all purposes equivalent to the above. It is
also shorter.</t>
<figure>
<artwork>
BEGIN:VCARD
VERSION:4.0
UID:urn:uuid:4fbe8971-0bc3-424c-9c26-36c3e1eff6b1
FN:J. Doe
N:Doe;J.;;;
EMAIL;PID=1.1:jdoe@example.com
EMAIL;PID=2.1:boss@example.com
EMAIL;PID=3.1:ceo@example.com
TEL;PID=1.1;VALUE=uri:tel:+1-555-555-5555
TEL;PID=2.1;VALUE=uri:tel:+1-666-666-6666
CLIENTPIDMAP:1;urn:uuid:53e374d9-337e-4727-8803-a1e9c14e0556
END:VCARD
</artwork>
</figure>
<t>The details of global context simplification are unspecified by this
document. They are left up to the synchronization engine. This example
is merely intended to illustrate the possibility, which investigating
would be, in the authors' opinion, worthwhile.</t>
</section>
</section>
</section>
<section title="Example: Authors' vCards" anchor="oldsection_7_">
<figure>
<artwork>
BEGIN:VCARD
VERSION:4.0
FN:Simon Perreault
N:Perreault;Simon;;;ing. jr,M.Sc.
BDAY:--0203
ANNIVERSARY:20090808T1430-0500
GENDER:M
LANG;PREF=1:fr
LANG;PREF=2:en
ORG;TYPE=work:Viagénie
ADR;TYPE=work:;Suite D2-630;2875 Laurier;
Québec;QC;G1V 2M2;Canada
TEL;VALUE=uri;TYPE="work,voice";PREF=1:tel:+1-418-656-9254;ext=102
TEL;VALUE=uri;TYPE="work,cell,voice,video,text":tel:+1-418-262-6501
EMAIL;TYPE=work:simon.perreault@viagenie.ca
GEO;TYPE=work:geo:46.772673,-71.282945
KEY;TYPE=work;VALUE=uri:
http://www.viagenie.ca/simon.perreault/simon.asc
TZ:-0500
END:VCARD
</artwork>
</figure>
<figure>
<artwork>
BEGIN:VCARD
VERSION:4.0
FN:Pete Resnick
N:Resnick;Pete;;;
GENDER:M
ORG;TYPE=work:QUALCOMM Incorporated
ADR;TYPE=work:;;5775 Morehouse Drive;San Diego;CA;92121-1714;US
TEL;VALUE=uri;TYPE="work,voice":tel:+1-858-651-4478
EMAIL;TYPE=work:presnick@qualcomm.com
URL;TYPE=work:http://www.qualcomm.com/~presnick/
END:VCARD
</artwork>
</figure>
</section>
<section title="Security Considerations" anchor="security_considerations">
<t>
<list style="symbols">
<t>Internet mail is often used to transport vCards and is subject to many
well known security attacks, including monitoring, replay, and forgery.
Care should be taken by any directory service in allowing information to
leave the scope of the service itself, where any access controls or
confidentiality can no longer be guaranteed. Applications should also
take care to display directory data in a "safe" environment</t>
<t>vCards can carry cryptographic keys or certificates, as described in
<xref target="KEY"/>.</t>
<t>The vCard objects have no inherent authentication or privacy, but
can easily be carried by any security mechanism that transfers MIME
objects with authentication or privacy (e.g. S/MIME <xref
target="RFC5751"/>, OpenPGP <xref target="RFC4880"/>). In cases where
the threat of "spoofed" vCard information is a concern, the vCard SHOULD
BE transported using one of these secure mechanisms.</t>
<t>The information in a vCard may become out of date. In cases where the
vitality of data is important to an originator of a vCard, the SOURCE
property (<xref target="SOURCE"/>) SHOULD be specified. In addition, the
"REV" type described in section <xref target="REV"/> can be specified to
indicate the last time that the vCard data was updated.</t>
</list>
</t>
</section>
<section title="IANA Considerations">
<section title="MIME Type Registration" anchor="mime_type_registration">
<t>IANA is asked to register the following MIME Media Type (in
<http://www.iana.org/assignments/media-types/>).</t>
<t>
<list style="hanging">
<t hangText="To:">ietf-types@iana.org</t>
<t hangText="Subject:">Registration of media type text/vcard</t>
<t hangText="Type name:">text</t>
<t hangText="Subtype name:">vcard</t>
<t hangText="Required parameters:">none</t>
<t hangText="Optional parameters:">version</t>
<t>The "version" parameter is to be interpreted identically as the VERSION
vCard property. If this parameter is present, all vCards in a text/vcard
body part MUST have a VERSION property with value identical to that of
this MIME parameter.</t>
<t>"charset": as defined for text/plain <xref target="RFC2046"/>;
encodings other than UTF-8 <xref target="RFC3629"/> MUST NOT be used.</t>
<t hangText="Encoding considerations:">8bit</t>
<t hangText="Security considerations:">See <xref
target="security_considerations"/>.</t>
<t hangText="Interoperability considerations:">The text/vcard media type
is intended to identify vCard data of any version. There are older
specifications of vCard <xref target="RFC2426"/><xref
target="vCard21"/> still in common use. While
these formats are similar, they are not strictly compatible. In general,
it is necessary to inspect the value of the VERSION property (see <xref
target="VERSION"/>) for identifying the standard to which a
given vCard object conforms.</t>
<t>In addition, the following media types are known to have been used to
refer to vCard data. They should be considered deprecated in favor of
text/vcard.
<list style="symbols">
<t>text/directory</t>
<t>text/directory; profile=vcard</t>
<t>text/x-vcard</t>
</list>
</t>
<t hangText="Published specification:">draft-ietf-vcarddav-vcardrev-19</t>
<t hangText="Applications that use this media type:">They are numerous,
diverse, and include mail user agents, instant messaging clients,
address book applications, directory servers, customer relationship
management software.</t>
<t hangText="Additional information:">
<list style="hanging">
<t hangText="Magic number(s):"></t>
<t hangText="File extension(s):">.vcf .vcard</t>
<t hangText="Macintosh file type code(s):"></t>
</list>
</t>
<t hangText="Person & email address to contact for further
information:">Simon Perreault <simon.perreault@viagenie.ca></t>
<t hangText="Intended usage:">COMMON</t>
<t hangText="Restrictions on usage:">none</t>
<t hangText="Author:">Simon Perreault</t>
<t hangText="Change controller:">IETF</t>
</list>
</t>
</section>
<section title="Registering New vCard Elements" anchor="iana_registration">
<t>This section defines the process for registering new or modified vCard
elements (i.e. properties, parameters, value data types, and values) with
IANA. It does not contain any immediate IANA actions.</t>
<section title="Registration Procedure">
<t>The IETF will create a mailing list,
<eref target="mailto:vcard@ietf.org">vcard@ietf.org</eref>, which can
be used for public discussion of vCard element proposals prior to
registration. Use of the mailing list is strongly encouraged. The IESG
will appoint a designated expert who will monitor the
<eref target="mailto:vcard@ietf.org">vcard@ietf.org</eref> mailing list
and review registrations.</t>
<t>Registration of new vCard elements MUST be reviewed by the
designated expert and published in an RFC. A Standard Tracks RFC is
REQUIRED for the registration of new value data types that modify
existing properties. A Standard Tracks RFC is also REQUIRED for
registration of vCard elements that modify vCard elements previously
documented in a Standard Tracks RFC.</t>
<t>The registration procedure begins when a completed registration
template, defined in the sections below, is sent to
<eref target="mailto:vcard@ietf.org">vcard@ietf.org</eref> and
<eref target="mailto:iana@iana.org">iana@iana.org</eref>. The
designated expert is expected to tell IANA and the submitter of the
registration within two weeks whether the registration is approved,
approved with minor changes, or rejected with cause. When a
registration is rejected with cause, it can be re-submitted if the
concerns listed in the cause are addressed. Decisions made by the
designated expert can be appealed to the IESG Applications Area
Director, then to the IESG. They follow the normal appeals procedure
for IESG decisions.</t>
<t>Once the registration procedure concludes successfully, IANA creates or
modifies the corresponding record in the vCard registry. The completed
registration template is discarded.</t>
<t>An RFC specifying new vCard elements MUST include the completed
registration templates, which MAY be expanded with additional
information. These completed templates will go in the body of
the document, and SHOULD NOT be included or repeated in the
IANA Considerations section.</t>
<t>Finally, note that there is an XML representation for vCard defined in
<xref target="I-D.ietf-vcarddav-vcardxml"/>. An XML representation
SHOULD be defined for new vCard objects.</t>
</section>
<section title="Vendor Namespace">
<t>The vendor namespace is used for vCard elements associated with
commercially available products. "Vendor" or "producer" are construed
as equivalent and very broadly in this context.</t>
<t>A registration may be placed in the vendor namespace by anyone who
needs to interchange files associated with the particular product.
However, the registration formally belongs to the vendor or organization
handling the vCard elements in the namespace being registered. Changes
to the specification will be made at their request, as discussed in
subsequent sections.</t>
<t>vCard elements belonging to the vendor namespace will be distinguished
by the "VND-" prefix. This is followed by an IANA-registered Private
Enterprise Number (PEN), a dash, and a vCard element designation of the
vendor's choosing (e.g., "VND-123456-MUDPIE").</t>
<t>While public exposure and review of vCard elements to be registered in
the vendor namespace is not required, using the <eref
target="mailto:vcard@ietf.org">vcard@ietf.org</eref> mailing list for
review is strongly encouraged to improve the quality of those
specifications. Registrations in the vendor namespace may be submitted
directly to the IANA.</t>
</section>
<section title="Registration Template for Properties">
<t>A property is defined by completing the following template.</t>
<t>
<list style="hanging">
<t hangText="Namespace:">Empty for the global namespace, "VND-NNNN-"
for a vendor-specific property (where NNNN is replaced by the
vendor's PEN).</t>
<t hangText="Property name:">The name of the property.</t>
<t hangText="Purpose:">The purpose of the property. Give a short but
clear description.</t>
<t hangText="Value type:">Any of the valid value types for the
property value needs to be specified. The default value type also
needs to be specified.</t>
<t hangText="Cardinality:">See <xref target="properties"/>.</t>
<t hangText="Property parameters:">Any of the valid property
parameters for the property MUST be specified.</t>
<t hangText="Description:">Any special notes about the property, how
it is to be used, etc.</t>
<t hangText="Format definition:">The ABNF for the property definition
needs to be specified.</t>
<t hangText="Example(s):">One or more examples of instances of the
property needs to be specified.</t>
</list>
</t>
</section>
<section title="Registration Template for Parameters">
<t>A parameter is defined by completing the following template.</t>
<t>
<list style="hanging">
<t hangText="Namespace:">Empty for the global namespace, "VND-NNNN-"
for a vendor-specific property (where NNNN is replaced by the
vendor's PEN).</t>
<t hangText="Parameter name:">The name of the parameter.</t>
<t hangText="Purpose:">The purpose of the parameter. Give a short but
clear description.</t>
<t hangText="Description:">Any special notes about the parameter, how
it is to be used, etc.</t>
<t hangText="Format definition:">The ABNF for the parameter definition
needs to be specified.</t>
<t hangText="Example(s):">One or more examples of instances of the
parameter needs to be specified.</t>
</list>
</t>
</section>
<section title="Registration Template for Value Data Types">
<t>A value data type is defined by completing the following template.</t>
<t>
<list style="hanging">
<t hangText="Value name:">The name of the value type.</t>
<t hangText="Purpose:">The purpose of the value type. Give a short
but clear description.</t>
<t hangText="Description:">Any special notes about the value type, how
it is to be used, etc.</t>
<t hangText="Format definition:">The ABNF for the value type
definition needs to be specified.</t>
<t hangText="Example(s):">One or more examples of instances of the
value type needs to be specified.</t>
</list>
</t>
</section>
<section title="Registration Template for Values">
<t>A value is defined by completing the following template.</t>
<t>
<list style="hanging">
<t hangText="Value:">The value literal.</t>
<t hangText="Purpose:">The purpose of the value. Give a short but
clear description.</t>
<t hangText="Conformance:">The vCard properties and/or parameters
that can take this value needs to be specified.</t>
<t hangText="Example(s):">One or more examples of instances of the
value needs to be specified.</t>
</list>
</t>
<t>The following is a fictitious example of a registration of a vCard
value:</t>
<t>
<list style="hanging">
<t hangText="Value:">supervisor</t>
<t hangText="Purpose:">It means that the related entity is the
direct hierarchical superior (i.e. supervisor or manager) of the
entity this vCard represents.</t>
<t hangText="Conformance:">This value can be used with the "TYPE"
parameter applied on the "RELATED" property.</t>
<t hangText="Example(s):"/>
</list>
</t>
<t>
<figure>
<artwork>
RELATED;TYPE=supervisor:urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6
</artwork>
</figure>
</t>
</section>
</section>
<section anchor="tables" title="Initial vCard Elements Registries">
<t>The IANA is requested to create and maintain the following registries for
vCard elements with pointers to appropriate reference documents. The
registries will be grouped together under the heading "vCard
Elements".</t>
<section title="Properties Registry">
<t>The following table is to be used to initialize the properties
registry.</t>
<texttable>
<ttcol align="left">Namespace</ttcol>
<ttcol align="left">Property</ttcol>
<ttcol align="left">Reference</ttcol>
<c></c>
<c>SOURCE</c>
<c>RFCXXXX, <xref target="SOURCE"/></c>
<c></c>
<c>KIND</c>
<c>RFCXXXX, <xref target="KIND"/></c>
<c></c>
<c>XML</c>
<c>RFCXXXX, <xref target="XML"/></c>
<c></c>
<c>FN</c>
<c>RFCXXXX, <xref target="FN"/></c>
<c></c>
<c>N</c>
<c>RFCXXXX, <xref target="N"/></c>
<c></c>
<c>NICKNAME</c>
<c>RFCXXXX, <xref target="NICKNAME"/></c>
<c></c>
<c>PHOTO</c>
<c>RFCXXXX, <xref target="PHOTO"/></c>
<c></c>
<c>BDAY</c>
<c>RFCXXXX, <xref target="BDAY"/></c>
<c></c>
<c>ANNIVERSARY</c>
<c>RFCXXXX, <xref target="ANNIVERSARY"/></c>
<c></c>
<c>GENDER</c>
<c>RFCXXXX, <xref target="GENDER"/></c>
<c></c>
<c>ADR</c>
<c>RFCXXXX, <xref target="ADR"/></c>
<c></c>
<c>TEL</c>
<c>RFCXXXX, <xref target="TEL"/></c>
<c></c>
<c>EMAIL</c>
<c>RFCXXXX, <xref target="EMAIL"/></c>
<c></c>
<c>IMPP</c>
<c>RFCXXXX, <xref target="IMPP"/></c>
<c></c>
<c>LANG</c>
<c>RFCXXXX, <xref target="LANG"/></c>
<c></c>
<c>TZ</c>
<c>RFCXXXX, <xref target="TZ"/></c>
<c></c>
<c>GEO</c>
<c>RFCXXXX, <xref target="GEO"/></c>
<c></c>
<c>TITLE</c>
<c>RFCXXXX, <xref target="TITLE"/></c>
<c></c>
<c>ROLE</c>
<c>RFCXXXX, <xref target="ROLE"/></c>
<c></c>
<c>LOGO</c>
<c>RFCXXXX, <xref target="LOGO"/></c>
<c></c>
<c>ORG</c>
<c>RFCXXXX, <xref target="ORG"/></c>
<c></c>
<c>MEMBER</c>
<c>RFCXXXX, <xref target="MEMBER"/></c>
<c></c>
<c>RELATED</c>
<c>RFCXXXX, <xref target="RELATED"/></c>
<c></c>
<c>CATEGORIES</c>
<c>RFCXXXX, <xref target="CATEGORIES"/></c>
<c></c>
<c>NOTE</c>
<c>RFCXXXX, <xref target="NOTE"/></c>
<c></c>
<c>PRODID</c>
<c>RFCXXXX, <xref target="PRODID"/></c>
<c></c>
<c>REV</c>
<c>RFCXXXX, <xref target="REV"/></c>
<c></c>
<c>SOUND</c>
<c>RFCXXXX, <xref target="SOUND"/></c>
<c></c>
<c>UID</c>
<c>RFCXXXX, <xref target="UID"/></c>
<c></c>
<c>CLIENTPIDMAP</c>
<c>RFCXXXX, <xref target="CLIENTPIDMAP"/></c>
<c></c>
<c>URL</c>
<c>RFCXXXX, <xref target="URL"/></c>
<c></c>
<c>VERSION</c>
<c>RFCXXXX, <xref target="VERSION"/></c>
<c></c>
<c>KEY</c>
<c>RFCXXXX, <xref target="KEY"/></c>
<c></c>
<c>FBURL</c>
<c>RFCXXXX, <xref target="FBURL"/></c>
<c></c>
<c>CALADRURI</c>
<c>RFCXXXX, <xref target="CALADRURI"/></c>
<c></c>
<c>CALURI</c>
<c>RFCXXXX, <xref target="CALURI"/></c>
</texttable>
</section>
<section title="Parameters Registry">
<t>The following table is to be used to initialize the parameters
registry.</t>
<texttable>
<ttcol align="left">Namespace</ttcol>
<ttcol align="left">Parameter</ttcol>
<ttcol align="left">Reference</ttcol>
<c></c>
<c>LANGUAGE</c>
<c>RFCXXXX, <xref target="LANGUAGE"/></c>
<c></c>
<c>VALUE</c>
<c>RFCXXXX, <xref target="VALUE"/></c>
<c></c>
<c>PREF</c>
<c>RFCXXXX, <xref target="PREF"/></c>
<c></c>
<c>ALTID</c>
<c>RFCXXXX, <xref target="ALTID"/></c>
<c></c>
<c>PID</c>
<c>RFCXXXX, <xref target="PID"/></c>
<c></c>
<c>TYPE</c>
<c>RFCXXXX, <xref target="TYPE"/></c>
<c></c>
<c>MEDIATYPE</c>
<c>RFCXXXX, <xref target="MEDIATYPE"/></c>
<c></c>
<c>CALSCALE</c>
<c>RFCXXXX, <xref target="CALSCALE"/></c>
<c></c>
<c>SORT-AS</c>
<c>RFCXXXX, <xref target="SORT-AS"/></c>
<c></c>
<c>GEO</c>
<c>RFCXXXX, <xref target="GEO-param"/></c>
<c></c>
<c>TZ</c>
<c>RFCXXXX, <xref target="TZ-param"/></c>
</texttable>
</section>
<section title="Value Data Types Registry">
<t>The following table is to be used to initialize the parameters
registry.</t>
<texttable>
<ttcol align="left">Value Data Type</ttcol>
<ttcol align="left">Reference</ttcol>
<c>BOOLEAN</c>
<c>RFCXXXX, <xref target="BOOLEAN"/></c>
<c>DATE</c>
<c>RFCXXXX, <xref target="DATE"/></c>
<c>TIME</c>
<c>RFCXXXX, <xref target="TIME"/></c>
<c>DATE-TIME</c>
<c>RFCXXXX, <xref target="DATE_TIME"/></c>
<c>DATE-AND-OR-TIME</c>
<c>RFCXXXX, <xref target="DATE_AND_OR_TIME"/></c>
<c>TIMESTAMP</c>
<c>RFCXXXX, <xref target="TIMESTAMP"/></c>
<c>FLOAT</c>
<c>RFCXXXX, <xref target="FLOAT"/></c>
<c>INTEGER</c>
<c>RFCXXXX, <xref target="INTEGER"/></c>
<c>TEXT</c>
<c>RFCXXXX, <xref target="TEXT"/></c>
<c>URI</c>
<c>RFCXXXX, <xref target="URI"/></c>
<c>LANGUAGE-TAG</c>
<c>RFCXXXX, <xref target="LANGUAGE-TAG"/></c>
</texttable>
</section>
<section title="Values Registries" anchor="iana_values">
<t>Separate tables will be used for property and parameter values.</t>
<t>The following table is to be used to initialize the property values
registry.</t>
<texttable>
<ttcol align="left">Property</ttcol>
<ttcol align="left">Value</ttcol>
<ttcol align="left">Reference</ttcol>
<c>BEGIN</c>
<c>VCARD</c>
<c>RFCXXXX, <xref target="BEGIN"/></c>
<c>END</c>
<c>VCARD</c>
<c>RFCXXXX, <xref target="END"/></c>
<c>KIND</c>
<c>individual</c>
<c>RFCXXXX, <xref target="KIND"/></c>
<c>KIND</c>
<c>group</c>
<c>RFCXXXX, <xref target="KIND"/></c>
<c>KIND</c>
<c>org</c>
<c>RFCXXXX, <xref target="KIND"/></c>
<c>KIND</c>
<c>location</c>
<c>RFCXXXX, <xref target="KIND"/></c>
</texttable>
<t>The following table is to be used to initialize the parameter values
registry.</t>
<texttable>
<ttcol align="left">Property</ttcol>
<ttcol align="left">Parameter</ttcol>
<ttcol align="left">Value</ttcol>
<ttcol align="left">Reference</ttcol>
<c>FN, NICKNAME, PHOTO, ADR, TEL, EMAIL, IMPP, LANG, TZ, GEO,
TITLE, ROLE, LOGO, ORG, RELATED, CATEGORIES, NOTE, SOUND, URL, KEY,
FBURL, CALADRURI, and CALURI</c>
<c>TYPE</c>
<c>work</c>
<c>RFCXXXX, <xref target="TYPE"/></c>
<c>FN, NICKNAME, PHOTO, ADR, TEL, EMAIL, IMPP, LANG, TZ, GEO,
TITLE, ROLE, LOGO, ORG, RELATED, CATEGORIES, NOTE, SOUND, URL, KEY,
FBURL, CALADRURI, and CALURI</c>
<c>TYPE</c>
<c>home</c>
<c>RFCXXXX, <xref target="TYPE"/></c>
<c>TEL</c>
<c>TYPE</c>
<c>text</c>
<c>RFCXXXX, <xref target="TEL"/></c>
<c>TEL</c>
<c>TYPE</c>
<c>voice</c>
<c>RFCXXXX, <xref target="TEL"/></c>
<c>TEL</c>
<c>TYPE</c>
<c>fax</c>
<c>RFCXXXX, <xref target="TEL"/></c>
<c>TEL</c>
<c>TYPE</c>
<c>cell</c>
<c>RFCXXXX, <xref target="TEL"/></c>
<c>TEL</c>
<c>TYPE</c>
<c>video</c>
<c>RFCXXXX, <xref target="TEL"/></c>
<c>TEL</c>
<c>TYPE</c>
<c>pager</c>
<c>RFCXXXX, <xref target="TEL"/></c>
<c>BDAY, ANNIVERSARY</c>
<c>CALSCALE</c>
<c>gregorian</c>
<c>RFCXXXX, <xref target="BDAY"/></c>
<c>RELATED</c>
<c>TYPE</c>
<c>contact</c>
<c>RFCXXXX, <xref target="RELATED"/> and <xref target="xfn"/></c>
<c>RELATED</c>
<c>TYPE</c>
<c>acquaintance</c>
<c>RFCXXXX, <xref target="RELATED"/> and <xref target="xfn"/></c>
<c>RELATED</c>
<c>TYPE</c>
<c>friend</c>
<c>RFCXXXX, <xref target="RELATED"/> and <xref target="xfn"/></c>
<c>RELATED</c>
<c>TYPE</c>
<c>met</c>
<c>RFCXXXX, <xref target="RELATED"/> and <xref target="xfn"/></c>
<c>RELATED</c>
<c>TYPE</c>
<c>co-worker</c>
<c>RFCXXXX, <xref target="RELATED"/> and <xref target="xfn"/></c>
<c>RELATED</c>
<c>TYPE</c>
<c>colleague</c>
<c>RFCXXXX, <xref target="RELATED"/> and <xref target="xfn"/></c>
<c>RELATED</c>
<c>TYPE</c>
<c>co-resident</c>
<c>RFCXXXX, <xref target="RELATED"/> and <xref target="xfn"/></c>
<c>RELATED</c>
<c>TYPE</c>
<c>neighbor</c>
<c>RFCXXXX, <xref target="RELATED"/> and <xref target="xfn"/></c>
<c>RELATED</c>
<c>TYPE</c>
<c>child</c>
<c>RFCXXXX, <xref target="RELATED"/> and <xref target="xfn"/></c>
<c>RELATED</c>
<c>TYPE</c>
<c>parent</c>
<c>RFCXXXX, <xref target="RELATED"/> and <xref target="xfn"/></c>
<c>RELATED</c>
<c>TYPE</c>
<c>sibling</c>
<c>RFCXXXX, <xref target="RELATED"/> and <xref target="xfn"/></c>
<c>RELATED</c>
<c>TYPE</c>
<c>spouse</c>
<c>RFCXXXX, <xref target="RELATED"/> and <xref target="xfn"/></c>
<c>RELATED</c>
<c>TYPE</c>
<c>kin</c>
<c>RFCXXXX, <xref target="RELATED"/> and <xref target="xfn"/></c>
<c>RELATED</c>
<c>TYPE</c>
<c>muse</c>
<c>RFCXXXX, <xref target="RELATED"/> and <xref target="xfn"/></c>
<c>RELATED</c>
<c>TYPE</c>
<c>crush</c>
<c>RFCXXXX, <xref target="RELATED"/> and <xref target="xfn"/></c>
<c>RELATED</c>
<c>TYPE</c>
<c>date</c>
<c>RFCXXXX, <xref target="RELATED"/> and <xref target="xfn"/></c>
<c>RELATED</c>
<c>TYPE</c>
<c>sweetheart</c>
<c>RFCXXXX, <xref target="RELATED"/> and <xref target="xfn"/></c>
<c>RELATED</c>
<c>TYPE</c>
<c>me</c>
<c>RFCXXXX, <xref target="RELATED"/> and <xref target="xfn"/></c>
<c>RELATED</c>
<c>TYPE</c>
<c>agent</c>
<c>RFCXXXX, <xref target="RELATED"/></c>
<c>RELATED</c>
<c>TYPE</c>
<c>emergency</c>
<c>RFCXXXX, <xref target="RELATED"/></c>
</texttable>
</section>
</section>
</section>
<section title="Acknowledgements">
<t>
The authors would like to thank Tim Howes, Mark Smith, and Frank Dawson, the original
authors of <xref target="RFC2425"/> and <xref target="RFC2426"/>, Pete
Resnick, who got this effort started and provided help along the way, as
well as the following individuals who have participated in the drafting,
review and discussion of this memo:
</t>
<t>
Aki Niemi, Andy Mabbett, Alexander Mayrhofer, Alexey Melnikov, Anil
Srivastava, Barry Leiba, Ben Fortuna, Bernard Desruisseaux, Bernie
Hoeneisen, Bjoern Hoehrmann, Caleb Richarson, Chris Bryant, Chris Newman,
Cyrus Daboo, Daisuke Miyakawa, Dan Brickley, Dan Mosedale, Dany Cauchie,
Darryl Champagne, Dave Thewlis, Filip Navara, Florian Zeitz, Helge Hess,
Jari Urpalainen, Javier Godoy, Jean-Luc Schellens, Joe Hildebrand, José Luis
Gayosso, Joseph Smarr, Julian Reschke, Kepeng Li, Kevin Marks, Kevin Wu Won,
Kurt Zeilenga. Lisa Dusseault, Marc Blanchet, Mark Paterson, Markus Lorenz,
Michael Haardt, Mike Douglass, Nick Levinson, Peter K. Sheerin, Peter
Mogensen, Peter Saint-Andre, Renato Iannella, Rohit Khare, Sly Gryphon,
Stéphane Bortzmeyer, Tantek Celik, and Zoltan Ordogh.
</t>
</section>
</middle>
<back>
<references title='Normative References'>
<?rfc include="reference.ISO.8601.2004"?>
<?rfc include="reference.ISO.8601.2000"?>
&ccitte1631988;
&ccittx1211988;
&ccittx5201988;
&ccittx5211988;
&rfc2045;
&rfc2046;
&rfc2119;
&rfc2739;
&rfc5322;
&rfc3629;
&rfc3966;
&rfc3986;
&rfc4122;
&rfc4288;
&rfc5545;
&rfc5546;
&rfc5646;
&rfc5234;
<reference anchor="xfn" target="http://gmpg.org/xfn/11">
<front>
<title>XHTML Friends Network 1.1</title>
<author initials="T." surname="Çelik" fullname="Tantek Çelik"/>
<author initials="M." surname="Mullenweg" fullname="Matthew Mullenweg"/>
<author initials="E." surname="Meyer" fullname="Eric Meyer"/>
</front>
</reference>
&geo-uri;
<?rfc include="reference.I-D.draft-ietf-vcarddav-vcardxml"?>
&xml;
</references>
<references title="Informative References">
&rfc1738;
&rfc2425;
&rfc2426;
<reference anchor='vCard21'>
<front>
<title>vCard - The Electronic Business Card Version 2.1</title>
<author>
<organization>Internet Mail Consortium</organization>
</author>
<date year='September' day='18' month='September' />
</front>
</reference>
&rfc4770;
<reference anchor='ISO9070'>
<front>
<title>ISO 9070, Information Processing - SGML support facilities -
Registration Procedures for Public Text Owner Identifiers</title>
<author>
<organization>The International Organization for
Standardization</organization>
</author>
<date year='1991' month='April' />
</front>
</reference>
&rfc2397;
&rfc2616;
&rfc3282;
&rfc3406;
&rfc4880;
&rfc5751;
&rfc6068;
&I-D.ietf-eai-rfc5335bis;
<?rfc include="reference.tz"?>
</references>
<section title="Differences from RFCs 2425 and 2426" anchor="diff">
<t>
This appendix contains a list of changes that have been made in the vCard
specification from RFCs 2425 and 2426.
</t>
<section title="New Structure">
<t>
<list style="symbols">
<t><xref target="RFC2425"/> and <xref target="RFC2426"/> have been
merged.</t>
<t>vCard is now not only a MIME type but a stand-alone format.</t>
<t>A proper MIME type registration form has been included.</t>
<t>UTF-8 is now the default character set.</t>
<t>New vCard elements can be registered from IANA.</t>
<t>Expanded text on character set.</t>
</list>
</t>
</section>
<section title="Removed Features">
<t>
<list style="symbols">
<t>The CONTEXT and CHARSET parameters are no more.</t>
<t>The NAME, MAILER, LABEL, and CLASS properties are no more.</t>
<t>The "intl", "dom", "postal", and "parcel" TYPE parameter values for
the ADR property have been removed.</t>
<t>Inline vCards (such as the value of the AGENT property) are no
longer supported.</t>
<t>In the N property, each component may now contain multiple
comma-separated values.</t>
</list>
</t>
</section>
<section title="New Properties and Parameters">
<t>
<list style="symbols">
<t>The KIND, GENDER, LANG, ANNIVERSARY, XML, and CLIENTPIDMAP properties
have been added.</t>
<t><xref target="RFC2739"/>, which defines the FBURL, CALADRURI,
CAPURI, and CALURI properties, has been merged in.</t>
<t><xref target="RFC4770"/>, which defines the IMPP property, has been
merged in.</t>
<t>The "work", "home", and "uri" TYPE parameter values for the EMAIL
property have been added.</t>
<t>The "pref" value of the TYPE parameter is now a parameter of its
own, with a positive integer value indicating the level of
preference.</t>
<t>The ALTID and PID parameters have been added.</t>
</list>
</t>
</section>
<section title="Other Changes">
<t>
<list style="symbols">
<t>Synchronization is addressed in <xref
target="synchronization"/>.</t>
<t>The N property is no longer mandatory.</t>
<t>The value of TEL is now a URI.</t>
<t>The AGENT property was replaced with a type of RELATED.</t>
<t>Date and time values now only support the basic format. Truncation
is now supported.</t>
</list>
</t>
</section>
</section>
<section title="Change Log (to be removed by RFC Editor prior to publication)"
anchor="changelog">
<section title="Changes in -19">
<t>
<list style="symbols">
<t>Fixed nits.</t>
<t>Fixed MEDIATYPE ABNF.</t>
</list>
</t>
</section>
<section title="Changes in -18">
<t>
<list style="symbols">
<t>Fix missing text in KIND section.</t>
</list>
</t>
</section>
<section title="Changes in -17">
<t>
<list style="symbols">
<t>s/individual/entity/</t>
<t>Moved section 3.4 for better flow.</t>
<t>Removed text overriding general MIME and HTTP rules.</t>
<t>Fixed redundant ABNF.</t>
<t>Fixed parameter value quoting in examples.</t>
<t>Added informative reference for Content-Language header.</t>
<t>Moved cardinality table earlier for better flow.</t>
<t>Added normative reference for XML 1.0.</t>
<t>Added informative reference for mailto: scheme.</t>
<t>Clarified where the VERSION property must go.</t>
<t>Created the MEDIATYPE parameter.</t>
<t>Fixed text/vcard encoding considerations.</t>
<t>Added .vcard file extension.</t>
<t>Removed need for extension documents to contain tables in their
IANA Considerations section.</t>
<t>Removed underspecified "Status" column in IANA registry.</t>
<t>Moved obsoleted references to Informative section.</t>
<t>Moved iCalendar references to Normative section.</t>
<t>Expanded specification of KIND values.</t>
<t>Recommend defining an XML representation for new vCard objects.</t>
</list>
</t>
</section>
<section title="Changes in -16">
<t>
<list style="symbols">
<t>RELATED: Added XFN values into IANA registry.</t>
<t>RELATED: Added values "agent" and "emergency".</t>
<t>EMAIL is now free-form text, with informative reference to EAI.</t>
<t>GENDER now has two components: one for biological sex, the other
for gender identity.</t>
<t>Bugfixes to the core ABNF.</t>
<t>Clarified IANA considerations.</t>
<t>UID may be reset to free-form text.</t>
</list>
</t>
</section>
<section title="Changes in -15">
<t>
<list style="symbols">
<t>Reverted N to the 5-component format of vCard 3.</t>
<t>Removed DDAY, BIRTH, and DEATH.</t>
<t>First two components in ADR SHOULD be empty.</t>
<t>Removed the LABEL property.</t>
<t>Removed the binary value type and the ENCODING and FMTTYPE
parameters.</t>
<t>Renamed SEX to GENDER. Set predefined values to "male" and
"female".</t>
<t>Reverted TEL to take a text value by default, but SHOULD be reset
to a URI.</t>
<t>Refer to iCalendar for CALSCALE.</t>
<t>Removed the "thing" value for KIND.</t>
<t>RELATED now uses XFN 1.1 for its value.</t>
<t>Dropped the VERSION parameter. XML MUST be version 1.0.</t>
<t>Dropped the CLASS property.</t>
<t>Property and parameter names SHOULD be upper-case.</t>
<t>Use ABNF for cardinality notation.</t>
</list>
</t>
</section>
<section title="Changes in -14">
<t>
<list style="symbols">
<t>DQUOTE is US-ASCII decimal 34, not 22.</t>
<t>Removed unused reference to RFC 2046.</t>
<t>Updated reference to draft-ietf-vcarddav-vcardxml.</t>
<t>Small fixes to the IANA registration text.</t>
<t>Added notes on the usage of TEL and IMPP properties.</t>
<t>Clarified "country name" component of ADR property.</t>
<t>Removed usage of undefined type value "msg" in TEL example.</t>
<t>Fixed parameter value quoting rules and ABNF.</t>
<t>Added example to LANGUAGE property.</t>
<t>Fixed synchronization example regarding the cardinality of FN.</t>
<t>Added implementation note for float value type.</t>
<t>Removed advice for always including VALUE parameter.</t>
<t>FMTTYPE MUST include the full MIME type.</t>
<t>Made ADR's ABNF more verbose.</t>
<t>Organized TEL TYPE values in a table.</t>
<t>Replaced TOP-SECRET example with NOINDEX.</t>
</list>
</t>
</section>
<section title="Changes in -13">
<t>
<list style="symbols">
<t>Changed global ABNF to make explicit that VERSION comes first.</t>
<t>Reworked example for LANGUAGE property.</t>
<t>s/TYPE/FMTTYPE/ in two examples.</t>
<t>Allow LANGUAGE parameter for text-valued BDAY, DDAY, and
RELATED.</t>
<t>Tightened language on LANGUAGE parameter regarding cardinality.</t>
<t>Removed the NAME property.</t>
<t>Adjusted semi-colon escaping rules.</t>
<t>Added the ALTID parameter.</t>
</list>
</t>
</section>
<section title="Changes in -12">
<t>
<list style="symbols">
<t>Fixed example of LANGUAGE cardinality.</t>
<t>Added note about YYYY-MM date format.</t>
<t>Fixed appendix A.</t>
<t>VERSION property must come first.</t>
<t>Fixed mistake in PID example.</t>
<t>Removed two changes from Appendix A which were probably intended to
go into this change log section.</t>
<t>Explicitly state that the value for the BEGIN and END properties is
case-insensitive.</t>
<t>Removed the SORT-STRING property. Created the SORT-AS
parameter.</t>
<t>"T" and "Z" in dates and times are now mandatory uppercase.</t>
<t>Added the "version" MIME parameter.</t>
<t>More consistent capitalization.</t>
<t>Added missing "ANNIVERSARY" in name production rule.</t>
<t>Added missing calscale-param in param production rule.</t>
<t>Moved definition of GEO and TZ parameters to section 5.</t>
<t>Simplified discussion of encoding.</t>
<t>Removed restriction for "work" and "home" values of TYPE parameter
w.r.t. the KIND property.</t>
<t>XML value may now be binary.</t>
<t>Created VERSION parameter for XML.</t>
<t>BIRTH and DEATH can now have URI values.</t>
<t>Created the FMTTYPE parameter.</t>
<t>KEY can now take a text value.</t>
<t>Added references to RFC 5545 (iCalendar).</t>
<t>Added namespace column in parameters registry.</t>
</list>
</t>
</section>
<section title="Changes in -11">
<t>
<list style="symbols">
<t>Change "XML chunk" to "XML fragment".</t>
<t>Cite W3C document containing definition of "fragment".</t>
<t>Added "XML" to property name ABNF.</t>
<t>Clarified newline escaping rule.</t>
<t>Replaced one remaining "type" with "property".</t>
<t>Removed case insensitivity of parameter values.</t>
<t>XML property can now only contain one element that is not in the
vCard 4 namespace.</t>
<t>Clarified interrelationship between LANGUAGE, cardinality, and
PID.</t>
<t>Added "textphone" TEL type.</t>
<t>Fixed quoting of comma in ORG examples.</t>
</list>
</t>
</section>
<section title="Changes in -10">
<t>
<list style="symbols">
<t>Added component in SORT-STRING for sorting by given name. Fixed and
expanded the examples.</t>
<t>Fixed KIND-value ABNF.</t>
<t>Fixed deprecated media type.</t>
<t>Created the CALSCALE parameter.</t>
<t>Strenghtened the stance on character set.</t>
<t>Defined the Language-Tag ABNF.</t>
<t>Made explicit the fact that IANA does not register templates.</t>
<t>Created the XML property.</t>
<t>Added social networking examples to URL property.</t>
</list>
</t>
</section>
<section title="Changes in -09">
<t>
<list style="symbols">
<t>Removed special meaning for groups. Removed the "work" and "home"
groups. Removed the group registry. Re-introduced the "work" and
"home" TYPE parameter values. Applied the TYPE parameter to
properties which supported the "work" and "home" groups.</t>
<t>Vendor namespace now uses private enterprise number in prefix.</t>
<t>Added "thing" value for KIND property.</t>
</list>
</t>
</section>
<section title="Changes in -08">
<t>
<list style="symbols">
<t>Allow 1985 (year only) in date ABNF.</t>
<t>Fixed missing country in ADR example.</t>
<t>Added the DATE-AND-OR-TIME value.</t>
<t>Made BDAY and DDAY use DATE-AND-OR-TIME.</t>
<t>Prefixed "param" and "value" production rules specific to
properties with the property name.</t>
<t>Replaced the GENDER property with the SEX property.</t>
<t>Added the ANNIVERSARY property.</t>
<t>Added the "friend" and "spouse" types of RELATED.</t>
<t>TZ property now has text / uri value.</t>
<t>Refined the definitions of TITLE and ROLE.</t>
</list>
</t>
</section>
<section title="Changes in -07">
<t>
<list style="symbols">
<t>PREF is now bounded. 100 is the maximum value.</t>
<t>Added the "emergency" RELATED type.</t>
<t>Made GEO a URI.</t>
<t>Added GEO and TZ parameters to ADR.</t>
<t>Changed wording of "default" use of SOUND property.</t>
<t>Completely reworked the date, time, and date-time grammars.</t>
<t>Added the timestamp value type.</t>
<t>REV now has the timestamp value type.</t>
<t>Rewrote ABNF.</t>
<t>ORG can now have a single level.</t>
</list>
</t>
</section>
<section title="Changes in -06">
<t>
<list style="symbols">
<t>Corrected omission of resetability to text value for RELATED.</t>
<t>Let KEY value type be reset to a URI value.</t>
<t>ABNF fixes.</t>
<t>Made gender values extensible.</t>
<t>Gave the PREF parameter a positive integer value.</t>
<t>Removed usage of the undefined "word" ABNF production rule.</t>
<t>Defined property cardinalities.</t>
<t>Defined properties allowable in WORK and HOME groups.</t>
<t>Simplified the LANG property to use the vCard preference
mechanism.</t>
<t>Created the "language-tag" value type.</t>
<t>Added PID to ABNF of SOURCE allowed parameters.</t>
<t>Clarified escaping rules.</t>
<t>Changed ABNF definition of non-standard X- properties.</t>
<t>Removed TYPE parameter from EMAIL properties in examples.</t>
<t>Created the CLIENTPIDMAP property.</t>
<t>Changed PID value to a pair of small integers.</t>
<t>Completely reworked synchronization mechanisms.</t>
<t>Created brand new synchronization example.</t>
</list>
</t>
</section>
<section title="Changes in -05">
<t>
<list style="symbols">
<t>Added multi PID value proposal.</t>
</list>
</t>
</section>
<section title="Changes in -04">
<t>
<list style="symbols">
<t>Added "location" value for KIND property.</t>
<t>Some fixes to ABNF.</t>
<t>Moved "pref" from being a TYPE value to a parameter in its own
right.</t>
<t>Removed the "work" and "home" TYPE values.</t>
<t>Reintroduced the group construct.</t>
<t>Assigned meaning to WORK and HOME groups.</t>
<t>Restricted the TEL TYPE parameter value set.</t>
<t>In N property, removed additional names, and replaced with multiple
given names.</t>
<t>Removed TYPE parameter from EMAIL and IMPP properties.</t>
<t>Replaced AGENT with a type of RELATED.</t>
<t>Use example.org domain in URL example.</t>
<t>Created initial IANA table of values.</t>
<t>Defined meaning of PUBLIC, PRIVATE, CONFIDENTIAL.</t>
</list>
</t>
</section>
<section title="Changes in -03">
<t>
<list style="symbols">
<t>Various changes to the synchronization mechanisms.</t>
<t>Allowed truncated format for dated. See issue #236.</t>
</list>
</t>
</section>
<section title="Changes in -02">
<t>
<list style="symbols">
<t>Removed useless text in IMPP description.</t>
<t>Added CalDAV-SCHED example to CALADRURI.</t>
<t>Removed CAPURI property.</t>
<t>Dashes in dates and colons in times are now mandatory.</t>
<t>Allow for dates such as 2008 and 2008-05 and times such as 07 and
07:54.</t>
<t>Removed inline vCard value.</t>
<t>Made AGENT only accept URI references instead of inline vCards.</t>
<t>Added the MEMBER property.</t>
<t>Renamed the UID parameter to PID.</t>
<t>Changed the value type of the PID parameter to "a small
integer."</t>
<t>Changed the presence of UID and PID when synchronization is to be
used from MUST to SHOULD.</t>
<t>Added the RELATED (<xref target="RELATED"/>) property.</t>
<t>Fixed many ABNF typos (issue #252).</t>
<t>Changed formatting of ABNF comments to make them easier to read
(issue #226).</t>
</list>
</t>
</section>
<section title="Changes in -01">
<t>
<list style="symbols">
<t>Merged <xref target="RFC2739"/> in.</t>
<t>Converted all foobar.com, abc.com, etc. to example.com.</t>
<t>Fixed bugs in ABNF.</t>
<t>Made explicit that coordinates in the GEO property are expressed in
the WGS 84 reference system.</t>
<t>Clarified folding issues with multi-byte characters.</t>
<t>Made the value of TEL a URI.</t>
<t>Added the UID parameter.</t>
<t>Made the UID property's value type a URI.</t>
<t>Added <xref target="synchronization"/>.</t>
<t>Created IANA process for registering new parameters, value types,
and properties.</t>
<t>Created the initial IANA registries.</t>
<t>Created vendor namespace based on text from RFC 4288.</t>
</list>
</t>
</section>
<section title="Changes in -00">
<t>
<list style="symbols">
<t>Name change because draft has been accepted as WG item. Otherwise,
same as draft-resnick-vcarddav-vcardrev-01.</t>
<t>Removed reference to RFC 2234.</t>
<t>Fixed errata from
http://www.rfc-editor.org/errata_search.php?rfc=2426.</t>
<t>Removed passage referring to RFC 2425 profiles.</t>
<t>Renamed <xref target="oldsection_3_3"/> from "Telecommunications
Adressing Properties" to "Communications Properties.</t>
<t>Added <xref target="diff"/> and <xref target="changelog"/>.</t>
<t>Added reference to <xref target="RFC4770"/>.</t>
<t>Removed the group construct.</t>
<t>Made the N property no longer mandatory.</t>
<t>Added the KIND property.</t>
<t>Clarified meaning of TYPE parameter value for PHOTO, LOGO, KEY, and
SOUND.</t>
<t>Removed the CONTEXT parameter.</t>
<t>Removed the MAILER property.</t>
<t>Made reference to <xref target="ISO9070"/> informative.</t>
<t>Removed "intl", "dom", "postal", and "parcel" TYPE parameter values
for the ADR and LABEL properties.</t>
<t>Clarified meaning of "extended address" ADR field.</t>
<t>Mentioned <xref target="RFC3406"/> as another method of generating
PRODID values.</t>
<t>Updated obsolete references.</t>
<t>Allowed BDAY and DDAY value types to be text values for fuzzy
dates.</t>
<t>Removed the CHARSET property. Now the encoding is always UTF-8,
except when overridden by the Content-Type (which is considered a
compatibility feature).</t>
</list>
</t>
</section>
</section>
</back>
</rfc>
| PAFTECH AB 2003-2026 | 2026-04-23 23:29:32 |