As per Relevance of the word definition, we have this rfc below:
Network Working Group F.
Request for Comments: 2426 Lotus Development
Category: Standards Track T.
Netscape
September 1998
vCard MIME Directory
Status of this
This document specifies an Internet standards track protocol for
Internet community, and requests discussion and suggestions
improvements. Please refer to the current edition of the "
Official Protocol Standards" (STD 1) for the standardization
and status of this protocol. Distribution of this memo is unlimited
Copyright
Copyright (C) The Internet Society (1998). All Rights Reserved
This memo defines the profile of the MIME Content-Type [MIME-DIR]
directory information for a white-pages person object, based on
vCard electronic business card. The profile definition is
of any particular directory service or protocol. The profile
defined for representing and exchanging a variety of
about an individual (e.g., formatted and structured name and
addresses, email address, multiple telephone numbers, photograph
logo, audio clips, etc.). The directory information used by
profile is based on the attributes for the person object defined
the X.520 and X.521 directory services recommendations. The
also provides the method for including a [VCARD] representation of
white-pages directory entry within the MIME Content-Type defined
the [MIME-DIR] document
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY" and "OPTIONAL" in
document are to be interpreted as described in [RFC 2119].
Dawson & Howes Standards Track [Page 1]
RFC 2426 vCard MIME Directory Profile September 1998
Table of
Overview.........................................................3
1. THE VCARD MIME DIRECTORY PROFILE REGISTRATION.................4
2. MIME DIRECTORY FEATURES.......................................5
2.1 PREDEFINED TYPE USAGE ......................................5
2.1.1 BEGIN and END Type ......................................5
2.1.2 NAME Type ...............................................5
2.1.3 PROFILE Type ............................................5
2.1.4 SOURCE Type .............................................5
2.2 PREDEFINED TYPE PARAMETER USAGE ............................6
2.3 PREDEFINED VALUE TYPE USAGE ................................6
2.4 EXTENSIONS TO THE PREDEFINED VALUE TYPES ...................6
2.4.1 BINARY ..................................................6
2.4.2 VCARD ...................................................6
2.4.3 PHONE-NUMBER ............................................7
2.4.4 UTC-OFFSET ..............................................7
2.5 STRUCTURED TYPE VALUES .....................................7
2.6 LINE DELIMITING AND FOLDING ................................8
3. VCARD PROFILE FEATURES........................................8
3.1 IDENTIFICATION TYPES .......................................8
3.1.1 FN Type Definition ......................................8
3.1.2 N Type Definition .......................................9
3.1.3 NICKNAME Type Definition ................................9
3.1.4 PHOTO Type Definition ..................................10
3.1.5 BDAY Type Definition ...................................11
3.2 DELIVERY ADDRESSING TYPES .................................11
3.2.1 ADR Type Definition ....................................11
3.2.2 LABEL Type Definition ..................................13
3.3 TELECOMMUNICATIONS ADDRESSING TYPES .......................13
3.3.1 TEL Type Definition ....................................14
3.3.2 EMAIL Type Definition ..................................15
3.3.3 MAILER Type Definition .................................15
3.4 GEOGRAPHICAL TYPES ........................................16
3.4.1 TZ Type Definition .....................................16
3.4.2 GEO Type Definition ....................................16
3.5 ORGANIZATIONAL TYPES ......................................17
3.5.1 TITLE Type Definition ..................................17
3.5.2 ROLE Type Definition ...................................18
3.5.3 LOGO Type Definition ...................................18
3.5.4 AGENT Type Definition ..................................19
3.5.5 ORG Type Definition ....................................20
3.6 EXPLANATORY TYPES .........................................20
3.6.1 CATEGORIES Type Definition .............................20
3.6.2 NOTE Type Definition ...................................21
3.6.3 PRODID Type Definition .................................21
3.6.4 REV Type Definition ....................................22
3.6.5 SORT-STRING Type Definition ............................22
Dawson & Howes Standards Track [Page 2]
RFC 2426 vCard MIME Directory Profile September 1998
3.6.6 SOUND Type Definition ..................................23
3.6.7 UID Type Definition ....................................24
3.6.8 URL Type Definition ....................................25
3.6.9 VERSION Type Definition ................................25
3.7 SECURITY TYPES ............................................25
3.7.1 CLASS Type Definition ..................................26
3.7.2 KEY Type Definition ....................................26
3.8 EXTENDED TYPES ............................................27
4. FORMAL GRAMMAR...............................................27
5. DIFFERENCES FROM VCARD V2.1..................................37
6. ACKNOWLEDGEMENTS.............................................39
7. AUTHORS' ADDRESSES...........................................39
8. SECURITY CONSIDERATIONS......................................39
9. REFERENCES...................................................40
10. FULL COPYRIGHT STATEMENT....................................42
The [MIME-DIR] document defines a MIME Content-Type for
different kinds of directory information. The directory
can be based on any of a number of directory schemas. This
defines a [MIME-DIR] usage profile for conveying
information based on one such schema; that of the white-pages type
person object
The schema is based on the attributes for the person object
in the X.520 and X.521 directory services recommendations. The
has augmented the basic attributes defined in the X.500
recommendation in order to provide for an electronic
of the information commonly found on a paper business card.
schema was first defined in the [VCARD] document. Hence, this [MIME
DIR] profile is referred to as the vCard MIME Directory Profile
A directory entry based on this usage profile can include
directory, white-pages information such as the distinguished
used to uniquely identify the entry, a formatted representation
the name used for user-interface or presentation purposes, both
structured and presentation form of the delivery address,
telephone numbers and organizational information associated with
entry. In addition, traditional paper business card information
as an image of an organizational logo or identify photograph can
included in this person object
The vCard MIME Directory Profile also provides support
representing other important information about the person
with the directory entry. For instance, the date of birth of
person; an audio clip describing the pronunciation of the
associated with the directory entry, or some other application of
Dawson & Howes Standards Track [Page 3]
RFC 2426 vCard MIME Directory Profile September 1998
digital sound; longitude and latitude geo-positioning
related to the person associated with the directory entry; date
time that the directory information was last updated;
often written on a business card; Uniform Resource Locators (URL)
a website; public key information. The profile also provides
for non-standard extensions to the schema. This provides
flexibility for implementations to augment the current
of the profile in a standardized way. More information about
electronic business card format can be found in [VCARD].
1. The vCard Mime Directory Profile
This profile is identified by the following [MIME-DIR]
template information. Subsequent sections define the
definition
To: ietf-mime-directory@imc.
Subject: Registration of text/directory MIME profile
Profile name:
Profile purpose: To hold person object or white-pages type
directory information. The person schema captured in the
entries is that commonly found in an electronic business card
Predefined MIME Directory value specifications used: uri, date
date-time,
New value specifications: This profile places further constraints
the [MIME-DIR] text value specification. In addition, it adds
binary, phone-number, utc-offset and vcard value specifications
Predefined MIME Directory types used: SOURCE, NAME, PROFILE, BEGIN
END
Predefined MIME Directory parameters used: ENCODING, VALUE, CHARSET
LANGUAGE, CONTEXT
New types: FN, N, NICKNAME, PHOTO, BDAY, ADR, LABEL, TEL, EMAIL
MAILER, TZ, GEO, TITLE, ROLE, LOGO, AGENT, ORG, CATEGORIES, NOTE
PRODID, REV, SORT-STRING, SOUND, URL, UID, VERSION, CLASS,
New parameters:
Profile special notes: The vCard object MUST contain the FN, N
VERSION types. The type-grouping feature of [MIME-DIR] is
by this profile to group related vCard properties about a
Dawson & Howes Standards Track [Page 4]
RFC 2426 vCard MIME Directory Profile September 1998
entry. For example, vCard properties describing WORK or HOME
characteristics can be grouped with a unique group label
The profile permits the use of non-standard types (i.e.,
identified with the prefix string "X-") as a flexible method
implementations to extend the functionality currently defined
this profile
2. MIME Directory
The vCard MIME Directory Profile makes use of many of the
defined by [MIME-DIR]. The following sections either clarify
extend the content-type definition of [MIME-DIR].
2.1 Predefined Type
The vCard MIME Directory Profile uses the following predefined
from [MIME-DIR].
2.1.1 BEGIN and END
The content entity MUST begin with the BEGIN type with a value
"VCARD". The content entity MUST end with the END type with a
of "VCARD".
2.1.2 NAME
If the NAME type is present, then its value is the displayable
presentation text associated with the source for the vCard,
specified in the SOURCE type
2.1.3 PROFILE
If the PROFILE type is present, then its value MUST be "VCARD".
2.1.4 SOURCE
If the SOURCE type is present, then its value provides
how to find the source for the vCard
Dawson & Howes Standards Track [Page 5]
RFC 2426 vCard MIME Directory Profile September 1998
2.2 Predefined Type Parameter
The vCard MIME Directory Profile uses the following predefined
parameters as defined by [MIME-DIR].
-
-
-
2.3 Predefined VALUE Type
The predefined data type values specified in [MIME-DIR] MUST NOT
repeated in COMMA separated value lists except within the N
NICKNAME, ADR and CATEGORIES value types
The text value type defined in [MIME-DIR] is further restricted
that any SEMI-COLON character (ASCII decimal 59) in the value MUST
escaped with the BACKSLASH character (ASCII decimal 92).
2.4 Extensions To The Predefined VALUE
The predefined data type values specified in [MIME-DIR] have
extended by the vCard profile to include a number of value types
are specific to this profile
2.4.1
The "binary" value type specifies that the type value is inline
encoded binary data. This value type can be specified in the PHOTO
LOGO, SOUND, and KEY types
If inline encoded binary data is specified, the ENCODING
parameter MUST be used to specify the encoding format. The
data MUST be encoded using the "B" encoding format. Long lines
encoded binary data SHOULD BE folded to 75 characters using
folding method defined in [MIME-DIR].
The value type is defined by the following notation
binary =
2.4.2
The "vcard" value type specifies that the type value is
vCard. This value type can be specified in the AGENT type. The
type is defined by this specification. Since each of the
Dawson & Howes Standards Track [Page 6]
RFC 2426 vCard MIME Directory Profile September 1998
declarations with in the vcard value type are being specified
a text value themselves, they MUST be terminated with the
escape sequence "\n" or "\N", instead of the normal newline
sequence CRLF. In addition, any COMMA character (ASCII decimal 44),
SEMI-COLON character (ASCII decimal 59) and COLON character (
decimal 58) MUST be escaped with the BACKSLASH character (
decimal 92). For example, with the AGENT type a value would
specified as
AGENT:BEGIN:VCARD\nFN:Joe Friday\nTEL:+1-919-555-7878\
TITLE:Area Administrator\, Assistant\n EMAIL\;TYPE=INTERN\
ET:jfriday@host.com\nEND:VCARD\
2.4.3 PHONE-
The "phone-number" value type specifies that the type value is
telephone number. This value type can be specified in the TEL type
The value type is a text value that has the special semantics of
telephone number as defined in [CCITT E.163] and [CCITT X.121].
2.4.4 UTC-
The "utc-offset" value type specifies that the type value is a
offset from UTC. This value type can be specified in the TZ type
The value type is an offset from Coordinated Universal Time (UTC).
is specified as a positive or negative difference in units of
and minutes (e.g., +hh:mm). The time is specified as a 24-hour clock
Hour values are from 00 to 23, and minute values are from 00 to 59.
Hour and minutes are 2-digits with high order zeroes required
maintain digit count. The extended format for ISO 8601 UTC
MUST be used. The extended format makes use of a colon character as
separator of the hour and minute text fields
The value is defined by the following notation
time-hour = 2DIGIT ;00-23
time-minute = 2DIGIT ;00-59
utc-offset = ("+" / "-") time-hour ":" time-
2.5 Structured Type
Compound type values are delimited by a field delimiter, specified
the SEMI-COLON character (ASCII decimal 59). A SEMI-COLON in
component of a compound property value MUST be escaped with
BACKSLASH character (ASCII decimal 92).
Dawson & Howes Standards Track [Page 7]
RFC 2426 vCard MIME Directory Profile September 1998
Lists of values are delimited by a list delimiter, specified by
COMMA character (ASCII decimal 44). A COMMA character in a value
be escaped with a BACKSLASH character (ASCII decimal 92).
This profile supports the type grouping mechanism defined in [MIME
DIR]. Grouping of related types is a useful technique to
common semantics concerning the properties of a vCard
2.6 Line Delimiting and
This profile supports the same line delimiting and folding
defined in [MIME-DIR]. Specifically, when parsing a content line
folded lines must first be unfolded according to the
procedure described in [MIME-DIR]. After generating a content line
lines longer than 75 characters SHOULD be folded according to
folding procedure described in [MIME DIR].
Folding is done after any content encoding of a type value.
is done before any decoding of a type value in a content line
3. vCard Profile
The vCard MIME Directory Profile Type contains directory information
typically pertaining to a single directory entry. The information
described using an attribute schema that is tailored for
personal contact information. The vCard can include attributes
describe identification, delivery addressing,
addressing, geographical, organizational, general explanatory
security and access information about the particular
associated with the vCard
3.1 Identification
These types are used in the vCard profile to capture
associated with the identification and naming of the person
resource associated with the vCard
3.1.1 FN Type
To: ietf-mime-directory@imc.
Subject: Registration of text/directory MIME type
Type name:
Type purpose: To specify the formatted text corresponding to the
of the object the vCard represents
Dawson & Howes Standards Track [Page 8]
RFC 2426 vCard MIME Directory Profile September 1998
Type encoding: 8
Type value: A single text value
Type special notes: This type is based on the semantics of the X.520
Common Name attribute. The property MUST be present in the
object
Type example
FN:Mr. John Q. Public\, Esq
3.1.2 N Type
To: ietf-mime-directory@imc.
Subject: Registration of text/directory MIME type
Type name:
Type purpose: To specify the components of the name of the object
vCard represents
Type encoding: 8
Type value: A single structured text value. Each component can
multiple values
Type special note: The structured type value corresponds,
sequence, to the Family Name, Given Name, Additional Names,
Prefixes, and Honorific Suffixes. The text components are
by the SEMI-COLON character (ASCII decimal 59). Individual
components can include multiple text values (e.g.,
Additional Names) separated by the COMMA character (ASCII
44). This type is based on the semantics of the X.520 individual
attributes. The property MUST be present in the vCard object
Type example
N:Public;John;Quinlan;Mr.;Esq
N:Stevenson;John;Philip,Paul;Dr.;Jr.,M.D.,A.C.P
3.1.3 NICKNAME Type
To: ietf-mime-directory@imc.
Subject: Registration of text/directory MIME type
Dawson & Howes Standards Track [Page 9]
RFC 2426 vCard MIME Directory Profile September 1998
Type name:
Type purpose: To specify the text corresponding to the nickname
the object the vCard represents
Type encoding: 8
Type value: One or more text values separated by a COMMA
(ASCII decimal 44).
Type special note: The nickname is the descriptive name given
of or in addition to the one belonging to a person, place, or thing
It can also be used to specify a familiar form of a proper
specified by the FN or N types
Type example
NICKNAME:
NICKNAME:Jim,
3.1.4 PHOTO Type
To: ietf-mime-directory@imc.
Subject: Registration of text/directory MIME type
Type name:
Type purpose: To specify an image or photograph information
annotates some aspect of the object the vCard represents
Type encoding: The encoding MUST be reset to "b" using the
parameter in order to specify inline, encoded binary data. If
value is referenced by a URI value, then the default encoding of 8
is used and no explicit ENCODING parameter is needed
Type value: A single value. The default is binary value. It can
be reset to uri value. The uri value can be used to specify a
outside of this MIME entity
Type special notes: The type can include the type parameter "TYPE"
specify the graphic image format type. The TYPE parameter values
be one of the IANA registered image formats or a non-standard
format
Dawson & Howes Standards Track [Page 10]
RFC 2426 vCard MIME Directory Profile September 1998
Type example
PHOTO;VALUE=uri:http://www.abc.com/pub/
/jqpublic.
PHOTO;ENCODING=b;TYPE=JPEG:
AQEEBQAwdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05ldHNjYXBlIENvbW11
ljYXRpb25zIENvcnBvcmF0aW9uMRwwGgYDVQQLExNJbmZvcm1hdGlvbiBTeXN
<...remainder of "B" encoded binary data...>
3.1.5 BDAY Type
To: ietf-mime-directory@imc.
Subject: Registration of text/directory MIME type
Type name:
Type purpose: To specify the birth date of the object the
represents
Type encoding: 8
Type value: The default is a single date value. It can also be
to a single date-time value
Type examples
BDAY:1996-04-15
BDAY:1953-10-15T23:10:00
BDAY:1987-09-27T08:30:00-06:00
3.2 Delivery Addressing
These types are concerned with information related to the
addressing or label for the vCard object
3.2.1 ADR Type
To: ietf-mime-directory@imc.
Subject: Registration of text/directory MIME type
Type name:
Dawson & Howes Standards Track [Page 11]
RFC 2426 vCard MIME Directory Profile September 1998
Type purpose: To specify the components of the delivery address
the vCard object
Type encoding: 8
Type value: A single structured text value, separated by
SEMI-COLON character (ASCII decimal 59).
Type special notes: The structured type value consists of a
of address components. The component values MUST be specified
their corresponding position. The structured type value corresponds
in sequence, to the post office box; the extended address; the
address; the locality (e.g., city); the region (e.g., state
province); the postal code; the country name. When a component
is missing, the associated component separator MUST still
specified
The text components are separated by the SEMI-COLON character (
decimal 59). Where it makes semantic sense, individual
components can include multiple text values (e.g., a "street
component with multiple lines) separated by the COMMA
(ASCII decimal 44).
The type can include the type parameter "TYPE" to specify
delivery address type. The TYPE parameter values can include "dom"
indicate a domestic delivery address; "intl" to indicate
international delivery address; "postal" to indicate a
delivery address; "parcel" to indicate a parcel delivery address
"home" to indicate a delivery address for a residence; "work"
indicate delivery address for a place of work; and "pref" to
the preferred delivery address when more than one address
specified. These type parameter values can be specified as
parameter list (i.e., "TYPE=dom;TYPE=postal") or as a value
(i.e., "TYPE=dom,postal"). This type is based on semantics of
X.520 geographical and postal addressing attributes. The default
"TYPE=intl,postal,parcel,work". The default can be overridden to
other set of values by specifying one or more alternate values.
example, the default can be reset to "TYPE=dom,postal,work,home"
specify a domestic delivery address for postal delivery to
residence that is also used for work
Type example: In this example the post office box and the
address are absent
ADR;TYPE=dom,home,postal,parcel:;;123
Street;Any Town;CA;91921-1234
Dawson & Howes Standards Track [Page 12]
RFC 2426 vCard MIME Directory Profile September 1998
3.2.2 LABEL Type
To: ietf-mime-directory@imc.
Subject: Registration of text/directory MIME type
Type name:
Type purpose: To specify the formatted text corresponding to
address of the object the vCard represents
Type encoding: 8
Type value: A single text value
Type special notes: The type value is formatted text that can be
to present a delivery address label for the vCard object. The
can include the type parameter "TYPE" to specify delivery label type
The TYPE parameter values can include "dom" to indicate a
delivery label; "intl" to indicate an international delivery label
"postal" to indicate a postal delivery label; "parcel" to indicate
parcel delivery label; "home" to indicate a delivery label for
residence; "work" to indicate delivery label for a place of work;
"pref" to indicate the preferred delivery label when more than
label is specified. These type parameter values can be specified as
parameter list (i.e., "TYPE=dom;TYPE=postal") or as a value
(i.e., "TYPE=dom,postal"). This type is based on semantics of
X.520 geographical and postal addressing attributes. The default
"TYPE=intl,postal,parcel,work". The default can be overridden to
other set of values by specifying one or more alternate values.
example, the default can be reset to "TYPE=intl,post,parcel,home"
specify an international delivery label for both postal and
delivery to a residential location
Type example: A multi-line address label
LABEL;TYPE=dom,home,postal,parcel:Mr.John Q. Public\, Esq.\
Mail Drop: TNE QB\n123 Main Street\nAny Town\, CA 91921-1234
\nU.S.A
3.3 Telecommunications Addressing
These types are concerned with information associated with
telecommunications addressing of the object the vCard represents
Dawson & Howes Standards Track [Page 13]
RFC 2426 vCard MIME Directory Profile September 1998
3.3.1 TEL Type
To: ietf-mime-directory@imc.
Subject: Registration of text/directory MIME type
Type name:
Type purpose: To specify the telephone number for
communication with the object the vCard represents
Type encoding: 8
Type value: A single phone-number value
Type special notes: The value of this type is specified in
canonical form in order to specify an unambiguous representation
the globally unique telephone endpoint. This type is based on
X.500 Telephone Number attribute
The type can include the type parameter "TYPE" to specify
use for the telephone number. The TYPE parameter values can include
"home" to indicate a telephone number associated with a residence
"msg" to indicate the telephone number has voice messaging support
"work" to indicate a telephone number associated with a place
work, "pref" to indicate a preferred-use telephone number, "voice"
indicate a voice telephone number, "fax" to indicate a
telephone number, "cell" to indicate a cellular telephone number
"video" to indicate a video conferencing telephone number, "pager"
indicate a paging device telephone number, "bbs" to indicate
bulletin board system telephone number, "modem" to indicate a
connected telephone number, "car" to indicate a car-phone
number, "isdn" to indicate an ISDN service telephone number, "pcs"
indicate a personal communication services telephone number.
default type is "voice". These type parameter values can be
as a parameter list (i.e., "TYPE=work;TYPE=voice") or as a value
(i.e., "TYPE=work,voice"). The default can be overridden to
set of values by specifying one or more alternate values.
example, the default TYPE of "voice" can be reset to a WORK and HOME
VOICE and FAX telephone number by the value
"TYPE=work,home,voice,fax".
Type example
TEL;TYPE=work,voice,pref,msg:+1-213-555-1234
Dawson & Howes Standards Track [Page 14]
RFC 2426 vCard MIME Directory Profile September 1998
3.3.2 EMAIL Type
To: ietf-mime-directory@imc.
Subject: Registration of text/directory MIME type
Type name:
Type purpose: To specify the electronic mail address
communication with the object the vCard represents
Type encoding: 8
Type value: A single text value
Type special notes: The type can include the type parameter "TYPE"
specify the format or preference of the electronic mail address.
TYPE parameter values can include: "internet" to indicate an
addressing type, "x400" to indicate a X.400 addressing type or "pref
to indicate a preferred-use email address when more than one
specified. Another IANA registered address type can also
specified. The default email type is "internet". A non-standard
can also be specified
Type example
EMAIL;TYPE=internet:jqpublic@xyz.dom1.
EMAIL;TYPE=internet:jdoe@isp.
EMAIL;TYPE=internet,pref:jane_doe@abc.
3.3.3 MAILER Type
To: ietf-mime-directory@imc.
Subject: Registration of text/directory MIME type
Type name:
Type purpose: To specify the type of electronic mail software that
used by the individual associated with the vCard
Type encoding: 8
Type value: A single text value
Dawson & Howes Standards Track [Page 15]
RFC 2426 vCard MIME Directory Profile September 1998
Type special notes: This information can provide assistance to
correspondent regarding the type of data representation which can
used, and how they can be packaged. This property is based on
private MIME type X-Mailer that is generally implemented by MIME
agent products
Type example
MAILER:PigeonMail 2.1
3.4 Geographical
These types are concerned with information associated
geographical positions or regions associated with the object
vCard represents
3.4.1 TZ Type
To: ietf-mime-directory@imc.
Subject: Registration of text/directory MIME type
Type name:
Type purpose: To specify information related to the time zone of
object the vCard represents
Type encoding: 8
Type value: The default is a single utc-offset value. It can also
reset to a single text value
Type special notes: The type value consists of a single value
Type examples
TZ:-05:00
TZ;VALUE=text:-05:00; EST; Raleigh/North
;This example has a single value, not a structure text value
3.4.2 GEO Type
To: ietf-mime-directory@imc.
Subject: Registration of text/directory MIME type
Type name:
Dawson & Howes Standards Track [Page 16]
RFC 2426 vCard MIME Directory Profile September 1998
Type purpose: To specify information related to the
positioning of the object the vCard represents
Type encoding: 8
Type value: A single structured value consisting of two float
separated by the SEMI-COLON character (ASCII decimal 59).
Type special notes: This type specifies information related to
global position of the object associated with the vCard. The
specifies latitude and longitude, in that order (i.e., "LAT LON
ordering). The longitude represents the location east and west of
prime meridian as a positive or negative real number, respectively
The latitude represents the location north and south of the
as a positive or negative real number, respectively. The
and latitude values MUST be specified as decimal degrees and
be specified to six decimal places. This will allow for
within a meter of the geographical position. The text components
separated by the SEMI-COLON character (ASCII decimal 59). The
formula for converting degrees-minutes-seconds into decimal
is
decimal = degrees + minutes/60 + seconds/3600.
Type example
GEO:37.386013;-122.082932
3.5 Organizational
These types are concerned with information associated
characteristics of the organization or organizational units of
object the vCard represents
3.5.1 TITLE Type
To: ietf-mime-directory@imc.
Subject: Registration of text/directory MIME type
Type name:
Type purpose: To specify the job title, functional position
function of the object the vCard represents
Type encoding: 8
Type value: A single text value
Dawson & Howes Standards Track [Page 17]
RFC 2426 vCard MIME Directory Profile September 1998
Type special notes: This type is based on the X.520 Title attribute
Type example
TITLE:Director\, Research and
3.5.2 ROLE Type
To: ietf-mime-directory@imc.
Subject: Registration of text/directory MIME type
Type name:
Type purpose: To specify information concerning the role, occupation
or business category of the object the vCard represents
Type encoding: 8
Type value: A single text value
Type special notes: This type is based on the X.520 Business
explanatory attribute. This property is included as an
type to avoid confusion with the semantics of the TITLE type
incorrect usage of that type when the semantics of this type
intended
Type example
ROLE:
3.5.3 LOGO Type
To: ietf-mime-directory@imc.
Subject: Registration of text/directory MIME type
Type name:
Type purpose: To specify a graphic image of a logo associated
the object the vCard represents
Type encoding: The encoding MUST be reset to "b" using the
parameter in order to specify inline, encoded binary data. If
value is referenced by a URI value, then the default encoding of 8
is used and no explicit ENCODING parameter is needed
Dawson & Howes Standards Track [Page 18]
RFC 2426 vCard MIME Directory Profile September 1998
Type value: A single value. The default is binary value. It can
be reset to uri value. The uri value can be used to specify a
outside of this MIME entity
Type special notes: The type can include the type parameter "TYPE"
specify the graphic image format type. The TYPE parameter values
be one of the IANA registered image formats or a non-standard
format
Type example
LOGO;VALUE=uri:http://www.abc.com/pub/logos/abccorp.
LOGO;ENCODING=b;TYPE=JPEG:
AQEEBQAwdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05ldHNjYXBlIENvbW11
ljYXRpb25zIENvcnBvcmF0aW9uMRwwGgYDVQQLExNJbmZvcm1hdGlvbiBTeXN
<...the remainder of "B" encoded binary data...>
3.5.4 AGENT Type
To: ietf-mime-directory@imc.
Subject: Registration of text/directory MIME type
Type name:
Type purpose: To specify information about another person who
act on behalf of the individual or resource associated with
vCard
Type encoding: 8-
Type value: The default is a single vcard value. It can also be
to either a single text or uri value. The text value can be used
specify textual information. The uri value can be used to
information outside of this MIME entity
Type special notes: This type typically is used to specify an
administrator, assistant, or secretary for the individual
with the vCard. A key characteristic of the Agent type is that
represents somebody or something that is separately addressable
Type example
AGENT;VALUE=uri
CID:JQPUBLIC.part3.960129T083020.xyzMail@host3.
Dawson & Howes Standards Track [Page 19]
RFC 2426 vCard MIME Directory Profile September 1998
AGENT:BEGIN:VCARD\nFN:Susan Thomas\nTEL:+1-919-555-
1234\nEMAIL\;INTERNET:sthomas@host.com\nEND:VCARD\
3.5.5 ORG Type
To: ietf-mime-directory@imc.
Subject: Registration of text/directory MIME type
Type name:
Type purpose: To specify the organizational name and units
with the vCard
Type encoding: 8
Type value: A single structured text value consisting of
separated the SEMI-COLON character (ASCII decimal 59).
Type special notes: The type is based on the X.520 Organization
and Organization Unit attributes. The type value is a structured
consisting of the organization name, followed by one or more
of organizational unit names
Type example: A type value consisting of an organizational name
organizational unit #1 name and organizational unit #2 name
ORG:ABC\, Inc.;North American Division;
3.6 Explanatory
These types are concerned with additional explanations, such as
related to informational notes or revisions specific to the vCard
3.6.1 CATEGORIES Type
To: ietf-mime-directory@imc.
Subject: Registration of text/directory MIME type
Type name:
Type purpose: To specify application category information about
vCard
Type encoding: 8
Dawson & Howes Standards Track [Page 20]
RFC 2426 vCard MIME Directory Profile September 1998
Type value: One or more text values separated by a COMMA
(ASCII decimal 44).
Type example
CATEGORIES:TRAVEL
CATEGORIES:INTERNET,IETF,INDUSTRY,INFORMATION
3.6.2 NOTE Type
To: ietf-mime-directory@imc.
Subject: Registration of text/directory MIME type
Type name:
Type purpose: To specify supplemental information or a comment
is associated with the vCard
Type encoding: 8
Type value: A single text value
Type special notes: The type is based on the X.520
attribute
Type example
NOTE:This fax number is operational 0800 to 1715
EST\, Mon-Fri
3.6.3 PRODID Type
To: ietf-mime-directory@imc.
Subject: Registration of text/directory MIME type
Type name:
Type purpose: To specify the identifier for the product that
the vCard object
Type encoding: 8-
Type value: A single text value
Dawson & Howes Standards Track [Page 21]
RFC 2426 vCard MIME Directory Profile September 1998
Type special notes: Implementations SHOULD use a method such as
specified for Formal Public Identifiers in ISO 9070 to assure
the text value is unique
Type example
PRODID:-//ONLINE DIRECTORY//NONSGML Version 1//
3.6.4 REV Type
To: ietf-mime-directory@imc.
Subject: Registration of text/directory MIME type
Type name:
Type purpose: To specify revision information about the
vCard
Type encoding: 8-
Type value: The default is a single date-time value. Can also
reset to a single date value
Type special notes: The value distinguishes the current revision
the information in this vCard for other renditions of
information
Type example
REV:1995-10-31T22:27:10
REV:1997-11-15
3.6.5 SORT-STRING Type
To: ietf-mime-directory@imc.
Subject: Registration of text/directory MIME type SORT-
Type Name: SORT-
Type purpose: To specify the family name or given name text to
used for national-language-specific sorting of the FN and N types
Type encoding: 8
Type value: A single text value
Dawson & Howes Standards Track [Page 22]
RFC 2426 vCard MIME Directory Profile September 1998
Type special notes: The sort string is used to provide family name
given name text that is to be used in locale- or national-language
specific sorting of the formatted name and structured name types
Without this information, sorting algorithms could incorrectly
this vCard within a sequence of sorted vCards. When this type
present in a vCard, then this family name or given name value is
for sorting the vCard
Type examples: For the case of family name sorting, the
examples define common sort string usage with the FN and N types
FN:Rene van der
N:van der Harten;Rene;J.;Sir;R.D.O.N
SORT-STRING:
FN:Robert Pau Shou
N:Pau;Shou Chang;
SORT-STRING:
FN:Osamu
N:Koura;
SORT-STRING:
FN:Oscar del
N:del Pozo Triscon;
SORT-STRING:
FN:Chistine d'
N:d'Aboville;
SORT-STRING:
3.6.6 SOUND Type
To: ietf-mime-directory@imc.
Subject: Registration of text/directory MIME type
Type name:
Type purpose: To specify a digital sound content information
annotates some aspect of the vCard. By default this type is used
specify the proper pronunciation of the name type value of the vCard
Type encoding: The encoding MUST be reset to "b" using the
parameter in order to specify inline, encoded binary data. If
value is referenced by a URI value, then the default encoding of 8
is used and no explicit ENCODING parameter is needed
Dawson & Howes Standards Track [Page 23]
RFC 2426 vCard MIME Directory Profile September 1998
Type value: A single value. The default is binary value. It can
be reset to uri value. The uri value can be used to specify a
outside of this MIME entity
Type special notes: The type can include the type parameter "TYPE"
specify the audio format type. The TYPE parameter values MUST be
of the IANA registered audio formats or a non-standard audio format
Type example
SOUND;TYPE=BASIC;VALUE=uri:CID:JOHNQPUBLIC.part8.
19960229T080000.xyzMail@host1.
SOUND;TYPE=BASIC;ENCODING=b:
AQEEBQAwdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05ldHNjYXBlIENvbW11
ljYXRpb25zIENvcnBvcmF0aW9uMRwwGgYDVQQLExNJbmZvcm1hdGlvbiBTeXN
<...the remainder of "B" encoded binary data...>
3.6.7 UID Type
To: ietf-mime-directory@imc.
Subject: Registration of text/directory MIME type
Type name:
Type purpose: To specify a value that represents a globally
identifier corresponding to the individual or resource
with the vCard
Type encoding: 8
Type value: A single text value
Type special notes: The type is used to uniquely identify the
that the vCard represents
The type can include the type parameter "TYPE" to specify the
of the identifier. The TYPE parameter value should be an
registered identifier format. The value can also be a non-
format
Type example
UID:19950401-080045-40000F192713-0052
Dawson & Howes Standards Track [Page 24]
RFC 2426 vCard MIME Directory Profile September 1998
3.6.8 URL Type
To: ietf-mime-directory@imc.
Subject: Registration of text/directory MIME type
Type name:
Type purpose: To specify a uniform resource locator associated
the object that the vCard refers to
Type encoding: 8
Type value: A single uri value
Type example
URL:http://www.swbyps.restaurant.french/~chezchic.
3.6.9 VERSION Type
To: ietf-mime-directory@imc.
Subject: Registration of text/directory MIME type
Type name:
Type purpose: To specify the version of the vCard specification
to format this vCard
Type encoding: 8
Type value: A single text value
Type special notes: The property MUST be present in the vCard object
The value MUST be "3.0" if the vCard corresponds to
specification
Type example
VERSION:3.0
3.7 Security
These types are concerned with the security of communication
or access to the vCard
Dawson & Howes Standards Track [Page 25]
RFC 2426 vCard MIME Directory Profile September 1998
3.7.1 CLASS Type
To: ietf-mime-directory@imc.
Subject: Registration of text/directory MIME type
Type name:
Type purpose: To specify the access classification for a
object
Type encoding: 8
Type value: A single text value
Type special notes: An access classification is only one component
the general security model for a directory service.
classification attribute provides a method of capturing the intent
the owner for general access to information described by the
object
Type examples
CLASS:
CLASS:
CLASS:
3.7.2 KEY Type
To: ietf-mime-directory@imc.
Subject: Registration of text/directory MIME type
Type name:
Type purpose: To specify a public key or authentication
associated with the object that the vCard represents
Type encoding: The encoding MUST be reset to "b" using the
parameter in order to specify inline, encoded binary data. If
value is a text value, then the default encoding of 8bit is used
no explicit ENCODING parameter is needed
Type value: A single value. The default is binary. It can also
reset to text value. The text value can be used to specify a
key
Dawson & Howes Standards Track [Page 26]
RFC 2426 vCard MIME Directory Profile September 1998
Type special notes: The type can also include the type parameter
to specify the public key or authentication certificate format.
parameter type should specify an IANA registered public key
authentication certificate format. The parameter type can
specify a non-standard format
Type example
KEY;ENCODING=b:
wdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05ldHNjYXBlIENbW11
Rpb25zIENvcnBvcmF0aW9uMRwwGgYDVQQLExNJbmZvcm1hdGlvbiBTeXN
ZW1zMRwwGgYDVQQDExNyb290Y2EubmV0c2NhcGUuY29tMB4XDTk3
E5NDc1OVoXDTk3MTIwMzE5NDc1
VQQKEx1OZXRzY2FwZSBDb21tdW5pY2F0aW9ucyBDb3JwLjEYMBYGA1
MPVGltb3RoeSBBIEhvd2VzMSEwHwYJKoZIhvcNAQkBFhJob3dlc0
Y2FwZS5jb20xFTATBgoJkiaJk/IsZAEBEwVob3dlczBcMA0GCSqGSIb3
EBAQUAA0sAMEgCQQC0JZf6wkg8pLMXHHCUvMfL5H6zjSk4vTTXZpYyrdN
dXcoX49LKiOmgeJSzoiFKHtLOIboyludF90CgqcxtwKnAgMBAAGjNjA0
EGCWCGSAGG+EIBAQQEAwIAoDAfBgNVHSMEGDAWgBT84FToB/GV3jr3
+hUMbsQukjANBgkqhkiG9w0BAQQFAAOBgQBexv7o7mi3PLXadkmNP9
mx93HGp0Kgyx1jIVMyNgsemeAwBM+MSlhMfcpbTrONwNjZYW8vJDSoi//
rZlVt9bJbs7MNYZVsyF1unsqaln4/vy6Uawfg8VUMk1U7jt8LYpo4YULU
UZHPYVUaSgVttImOHZIKi4hlPXBOhcUQ==
3.8 Extended
The types defined by this document can be extended with private
using the non-standard, private values mechanism defined in [
2045]. Non-standard, private types with a name starting with "X-"
be defined bilaterally between two cooperating agents without
registration or standardization
4. Formal
The following formal grammar is provided to assist developers
building parsers for the vCard
This syntax is written according to the form described in RFC 2234,
but it references just this small subset of RFC 2234 literals
;*******************************************
; Commonly Used Literal
;*******************************************
ALPHA = %x41-5A / %x61-7
; Latin Capital Letter A-Latin Capital Letter Z /
; Latin Small Letter a-Latin Small Letter
Dawson & Howes Standards Track [Page 27]
RFC 2426 vCard MIME Directory Profile September 1998
CHAR = %x01-7
; Any C0 Controls and Basic Latin, excluding NULL
; Code Charts, pages 7-6 through 7-9 in [UNICODE
CR = %x0
; Carriage
LF = %0
; Line
CRLF = CR
; Internet standard
;CTL = %x00-1F / %x7
; Controls. Not used, but referenced in comments
DIGIT = %x30-39
; Digit Zero-Digit
DQUOTE = %x22
; Quotation
HTAB = %x09
; Horizontal
SP = %x20
;
VCHAR = %x21-7
; Visible (printing)
WSP = SP /
; White
;*******************************************
; Basic vCard
;*******************************************
vcard_entity = 1*(vcard
vcard = [group "."] "BEGIN" ":" "VCARD" 1*
1*(contentline
;A vCard object MUST include the VERSION, FN and N types
[group "."] "END" ":" "VCARD" 1*
contentline = [group "."] name *(";" param ) ":" value
; When parsing a content line, folded lines must
; be unfolded according to the unfolding
Dawson & Howes Standards Track [Page 28]
RFC 2426 vCard MIME Directory Profile September 1998
; described above. When generating a content line,
; longer than 75 characters SHOULD be folded according
; the folding procedure described in [MIME DIR].
group = 1*(ALPHA / DIGIT / "-")
name = iana-token / x-
; Parsing of the param and value
; based on the "name" or type
; as defined in ABNF sections
iana-token = 1*(ALPHA / DIGIT / "-")
; vCard type or parameter identifier registered with
x-name = "X-" 1*(ALPHA / DIGIT / "-")
; Reserved for non-standard
param = param-name "=" param-value *("," param-value
param-name = iana-token / x-
param-value = ptext / quoted-
ptext = *SAFE-
value = *VALUE-
quoted-string = DQUOTE QSAFE-CHAR
NON-ASCII = %x80-
; Use is restricted by CHARSET
; on outer MIME object (UTF-8 preferred
QSAFE-CHAR = WSP / %x21 / %x23-7E / NON-
; Any character except CTLs,
SAFE-CHAR = WSP / %x21 / %x23-2B / %x2D-39 / %x3C-7E / NON-
; Any character except CTLs, DQUOTE, ";", ":", ","
VALUE-CHAR = WSP / VCHAR / NON-
; Any textual
;*******************************************
; vCard Type
;
; Provides type-specific definitions for how
; "value" and "param" are defined
;*******************************************
Dawson & Howes Standards Track [Page 29]
RFC 2426 vCard MIME Directory Profile September 1998
;For name="NAME
param = ""
; No parameters
value = text-
;For name="PROFILE
param = ""
; No parameters
value = text-
; Value MUST be the case insensitive value "
;For name="SOURCE
param = source-
; No parameters
value =
source-param = ("VALUE" "=" "uri")
/ ("CONTEXT" "=" "word")
; Parameter value specifies the protocol
; for the uri value
/ (x-name "=" *SAFE-CHAR
;For name="FN
;This type MUST be included in a vCard object
param = text-
; Text parameters
value = text-
;For name="N
;This type MUST be included in a vCard object
param = text-
; Text parameters
value = n-
n-value = 0*4(text-value *("," text-value) ";")
text-value *("," text-value
; Family; Given; Middle; Prefix; Suffix
; Example: Public;John;Quincy,Adams;Reverend Dr.
;For name="NICKNAME
param = text-
; Text parameters
Dawson & Howes Standards Track [Page 30]
RFC 2426 vCard MIME Directory Profile September 1998
value = text-
;For name="PHOTO
param = img-inline-
; Only image parameters
param =/ img-refer-
; Only image parameters
value = img-inline-
; Value and parameter MUST
value =/ img-refer-
; Value and parameter MUST
;For name="BDAY
param = ("VALUE" "=" "date")
; Only value parameter
param =/ ("VALUE" "=" "date-time")
; Only value parameter
value = date-
; Value MUST match value
value =/ date-time-
; Value MUST match value
;For name="ADR
param = adr-param / text-
; Only adr and text parameters
value = adr-
;For name="LABEL
param = adr-param / text-
; Only adr and text parameters
value = text-
;For name="TEL
param = tel-
; Only tel parameters
value = phone-number-
tel-param = "TYPE" "=" tel-type *("," tel-type
Dawson & Howes Standards Track [Page 31]
RFC 2426 vCard MIME Directory Profile September 1998
tel-type = "HOME" / "WORK" / "PREF" / "VOICE" / "FAX" / "MSG
/ "CELL" / "PAGER" / "BBS" / "MODEM" / "CAR" / "ISDN
/ "VIDEO" / "PCS" / iana-token / x-
; Values are case
;For name="EMAIL
param = email-
; Only email parameters
value = text-
email-param = "TYPE" "=" email-type ["," "PREF"]
; Value is case
email-type = "INTERNET" / "X400" / iana-token / "X-"
; Values are case
;For name="MAILER
param = text-
; Only text parameters
value = text-
;For name="TZ
param = ""
; No parameters
value = utc-offset-
;For name="GEO
param = ""
; No parameters
value = float-value ";" float-
;For name="TITLE
param = text-
; Only text parameters
value = text-
;For name="ROLE
param = text-
; Only text parameters
value = text-
;For name="LOGO
Dawson & Howes Standards Track [Page 32]
RFC 2426 vCard MIME Directory Profile September 1998
param = img-inline-param / img-refer-
; Only image parameters
value = img-inline-value / img-refer-
; Value and parameter MUST
;For name="AGENT
param = agent-inline-
param =/ agent-refer-
value = agent-inline-
; Value and parameter MUST
value =/ agent-refer-
; Value and parameter MUST
agent-inline-param = ""
; No parameters
agent-refer-param = "VALUE" "=" "uri
; Only value parameter
agent-inline-value = text-
; Value MUST be a valid vCard
agent-refer-value =
; URI MUST refer to image content of given
;For name="ORG
param = text-
; Only text parameters
value = org-
org-value = *(text-value ";") text-
; First is Organization Name, remainder are Organization Units
;For name="CATEGORIES
param = text-
; Only text parameters
value = text-
;For name="NOTE
param = text-
; Only text parameters
Dawson & Howes Standards Track [Page 33]
RFC 2426 vCard MIME Directory Profile September 1998
value = text-
;For name="PRODID
param = ""
; No parameters
value = text-
;For name="REV
param = ["VALUE" =" "date-time"]
; Only value parameters allowed. Values are case insensitive
param =/ "VALUE" =" "date
; Only value parameters allowed. Values are case insensitive
value = date-time-
value =/ date-
;For name="SORT-STRING
param = text-
; Only text parameters
value = text-
;For name="SOUND
param = snd-inline-
; Only sound parameters
param =/ snd-refer-
; Only sound parameters
value = snd-line-
; Value MUST match value
value =/ snd-refer-
; Value MUST match value
snd-inline-value = binary-value
; Value MUST be "b" encoded audio
snd-inline-param = ("VALUE" "=" "binary"])
/ ("ENCODING" "=" "b")
/ ("TYPE" "=" *SAFE-CHAR
; Value MUST be an IANA registered audio
snd-refer-value =
; URI MUST refer to audio content of given
Dawson & Howes Standards Track [Page 34]
RFC 2426 vCard MIME Directory Profile September 1998
snd-refer-param = ("VALUE" "=" "uri")
/ ("TYPE" "=" word
; Value MUST be an IANA registered audio
;For name="UID
param = ""
; No parameters
value = text-
;For name="URL
param = ""
; No parameters
value =
;For name="VERSION
;This type MUST be included in a vCard object
param = ""
; No parameters
value = text-
; Value MUST be "3.0"
;For name="CLASS
param = ""
; No parameters
value = "PUBLIC" / "PRIVATE" / "CONFIDENTIAL
/ iana-token / x-
; Value are case
;For name="KEY
param = key-txt-
; Only value and type parameters
param =/ key-bin-
; Only value and type parameters
value = text-
value =/ binary-
key-txt-param = "TYPE" "="
key-bin-param = ("TYPE" "=" keytype
/ ("ENCODING" "=" "b")
; Value MUST be a "b" encoded key or
Dawson & Howes Standards Track [Page 35]
RFC 2426 vCard MIME Directory Profile September 1998
keytype = "X509" / "PGP" / iana-token / x-
; Values are case
;For name="X-" non-standard
param = text-param / (x-name "=" param-value
; Only text or non-standard parameters
value = text-
;*******************************************
; vCard Commonly Used Parameter
;*******************************************
text-param = ("VALUE" "=" "ptext")
/ ("LANGUAGE" "=" langval
/ (x-name "=" param-value
langval = language string as defined in RFC 1766>
img-inline-value = binary-
;Value MUST be "b" encoded image
img-inline-
img-inline-param = ("VALUE" "=" "binary")
/ ("ENCODING" "=" "b")
/ ("TYPE" "=" param-
;TYPE value MUST be an IANA registered image
img-refer-value =
;URI MUST refer to image content of given
img-refer-param = ("VALUE" "=" "uri")
/ ("TYPE" "=" param-value
;TYPE value MUST be an IANA registered image
adr-param = ("TYPE" "=" adr-type *("," adr-type))
/ (text-param
adr-type = "dom" / "intl" / "postal" / "parcel" / "home
/ "work" / "pref" / iana-type / x-
adr-value = 0*6(text-value ";") text-
; PO Box, Extended Address, Street, Locality, Region,
; Code, Country
Dawson & Howes Standards Track [Page 36]
RFC 2426 vCard MIME Directory Profile September 1998
;*******************************************
; vCard Type Value
;*******************************************
text-value-list = 1*text-value *("," 1*text-value
text-value = *(SAFE-CHAR / ":" / DQUOTE / ESCAPED-CHAR
ESCAPED-CHAR = "\\" / "\;" / "\," / "\n" / "\N")
; \\ encodes \, \n or \N encodes
; \; encodes ;, \, encodes ,
binary-value =
date-value =
time-value =
date-time-value =
float-value =
phone-number-value =
E.163] and [CCITT X.121]>
uri-value =
utc-offset-value = ("+" / "-") time-hour ":" time-
time-hour = 2DIGIT ;00-23
time-minute = 2DIGIT ;00-59
5. Differences From vCard v2.1
This specification has been reviewed by the IETF community.
review process introduced a number of differences from the [VCARD
version 2.1. These differences require that vCard objects
to this specification have a different version number than a
conforming to [VCARD]. The differences include the following
. The QUOTED-PRINTABLE inline encoding has been eliminated
Only the "B" encoding of [RFC 2047] is an allowed value
the ENCODING parameter
. The method for specifying CRLF character sequences in
type values has been changed. The CRLF character sequence
a text type value is specified with the backslash
sequence "\n" or "\N".
Dawson & Howes Standards Track [Page 37]
RFC 2426 vCard MIME Directory Profile September 1998
. Any COMMA or SEMICOLON in a text type value must be
escaped
. VERSION value corresponding to this specification MUST
"3.0".
. The [MIME-DIR] predefined types of SOURCE, NAME and
are allowed
. The [MIME-DIR] VALUE type parameter for value data typing
allowed. In addition, there are extensions made to these
values for additional value types used in this specification
. The [VCARD] CHARSET type parameter has been eliminated
Character set can only be specified on the CHARSET
on the Content-Type MIME header field
. The [VCARD] support for non-significant WSP character
been eliminated
. The "TYPE=" prefix to parameter values is required.
[VCARD] this was optional
. LOGO, PHOTO and SOUND multimedia formats MUST be either
registered types or non-standard types
. Inline binary content must be "B" encoded and folded. A
line after the encoded binary content is no longer required
. TEL values can be identified as personal
services telephone numbers with the PCS type parameter value
. The CATEGORIES, CLASS, NICKNAME, PRODID and SORT-STRING
have been added
. The VERSION, N and FN types MUST be specified in a vCard
This identifies the version of the specification that
