draft-ietf-asid-mime-vcard-04.txt   draft-ietf-asid-mime-vcard-05.txt 
Network Working Group Frank Dawson Network Working Group Frank Dawson
INTERNET DRAFT Lotus Development Corporation Request for Comments: DRAFT Lotus Development Corporation
ietf-asid-mime-vcard-04.txt Tim Howes draft-ietf-asid-mime-vcard-05.txt Tim Howes
Expires six months after November 21, 1997 Netscape Communications March 8, 1998 Netscape Communications
vCard MIME Directory Profile vCard MIME Directory Profile
Status of this Memo Status of this Memo
This document is an Internet-Draft. Internet-Drafts are working This document is an Internet-Draft. Internet-Drafts are working
documents of the Internet Engineering Task Force (IETF), its areas, documents of the Internet Engineering Task Force (IETF), its areas,
and its working groups. Note that other groups may also distribute and its working groups. Note that other groups may also distribute
working documents as Internet-Drafts. working documents as Internet-Drafts.
skipping to change at line 49 skipping to change at page 1, line 50
addresses, email address, multiple telephone numbers, photograph, addresses, email address, multiple telephone numbers, photograph,
logo, audio clips, etc.). The directory information used by this logo, audio clips, etc.). The directory information used by this
profile is based on the attributes for the person object defined in profile is based on the attributes for the person object defined in
the X.520 and X.521 directory services recommendations. The profile the X.520 and X.521 directory services recommendations. The profile
also provides the method for including a [VCARD] representation of a also provides the method for including a [VCARD] representation of a
white-pages directory entry within the MIME Content-Type defined by white-pages directory entry within the MIME Content-Type defined by
the [MIME-DIR] document. the [MIME-DIR] document.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY" and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY" and "OPTIONAL" in this
document are to be interopreted as described in [RFC-2119]. document are to be interopreted as described in [RFC 2119].
1. Overview vCard MIME Directory Profile
The [MIME-DIR] document defines a MIME Content-Type for holding Table of Contents
different kinds of directory information. The directory information
may be based on any of a number of directory schemas. This document
defines a [MIME-DIR] usage profile for conveying directory
Dawson & Howes [Page 1] May 1998 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..................................................6
2.1.4 SOURCE Type...................................................6
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.........................................................7
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.............................................8
3.1.3 NICKNAME Type Definition......................................9
3.1.4 PHOTO Type Definition........................................10
3.1.5 BDAY Type Definition.........................................10
3.2 DELIVERY ADDRESSING TYPES.......................................11
3.2.1 ADR Type Definition..........................................11
3.2.2 LABEL Type Definition........................................12
3.3 TELECOMMUNICATIONS ADDRESSING TYPES.............................13
3.3.1 TEL Type Definition..........................................13
3.3.2 EMAIL Type Definition........................................14
3.3.3 MAILER Type Definition.......................................14
3.4 GEOGRAPHICAL TYPES..............................................15
3.4.1 TZ Type Definition...........................................15
3.4.2 GEO Type Definition..........................................15
3.5 ORGANIZATIONAL TYPES............................................16
3.5.1 TITLE Type Definition........................................16
3.5.2 ROLE Type Definition.........................................16
3.5.3 LOGO Type Definition.........................................17
3.5.4 AGENT Type Definition........................................18
3.5.5 ORG Type Definition..........................................18
3.6 EXPLANATORY TYPES...............................................19
3.6.1 CATEGORIES Type Definition...................................19
3.6.2 NOTE Type Definition.........................................19
3.6.3 PRODID Type Definition.......................................20
3.6.4 REV Type Definition..........................................20
3.6.5 SORT-STRING Type Definition..................................21
3.6.6 SOUND Type Definition........................................21
3.6.7 UID Type Definition..........................................22
vCard MIME Directory Profile vCard MIME Directory Profile
3.6.8 URL Type Definition..........................................22
3.6.9 VERSION Type Definition......................................23
3.7 SECURITY TYPES..................................................23
3.7.1 CLASS Type Definition........................................23
3.7.2 KEY Type Definition..........................................24
3.8 EXTENDED TYPES..................................................25
4. FORMAL GRAMMAR.....................................................25
5. DIFFERENCES WITH VCARD V2.1........................................34
6. ACKNOWLEDGEMENTS...................................................35
7. AUTHORS?S ADDRESSES................................................35
8. REFERENCES.........................................................35
9. FULL COPYRIGHT STATEMENT...........................................37
vCard MIME Directory Profile
Overview
The [MIME-DIR] document defines a MIME Content-Type for holding
different kinds of directory information. The directory information
may be based on any of a number of directory schemas. This document
defines a [MIME-DIR] usage profile for conveying directory
information based on one such schema; that of the white-pages type of information based on one such schema; that of the white-pages type of
person object. person object.
The schema is based on the attributes for the person object defined The schema is based on the attributes for the person object defined
in the X.520 and X.521 directory services recommendations. The schema in the X.520 and X.521 directory services recommendations. The schema
has augmented the basic attributes defined in the X.500 series has augmented the basic attributes defined in the X.500 series
recommendation in order to provide for an electronic representation recommendation in order to provide for an electronic representation
of the information commonly found on a paper business card. This of the information commonly found on a paper business card. This
schema was first defined in the [VCARD] document. Hence, this [MIME- schema was first defined in the [VCARD] document. Hence, this [MIME-
DIR] profile is referred to as the vCard MIME Directory Profile. DIR] profile is referred to as the vCard MIME Directory Profile.
skipping to change at line 98 skipping to change at page 4, line 48
digital sound; longitude and latitude geo-positioning information digital sound; longitude and latitude geo-positioning information
related to the person associated with the directory entry; date and related to the person associated with the directory entry; date and
time that the directory information was last updated; annotations time that the directory information was last updated; annotations
often written on a business card; Uniform Resource Locators (URL) for often written on a business card; Uniform Resource Locators (URL) for
a website; public key information. The profile also provides support a website; public key information. The profile also provides support
for non-standard extensions to the schema. This provides the for non-standard extensions to the schema. This provides the
flexibility for implementations to augment the current capabilities flexibility for implementations to augment the current capabilities
of the profile in a standardized way. More information about this of the profile in a standardized way. More information about this
electronic business card format can be found in [VCARD]. electronic business card format can be found in [VCARD].
2. The vCard Mime Directory Profile Registration 1. The vCard Mime Directory Profile Registration
This profile is identified by the following [MIME-DIR] registration This profile is identified by the following [MIME-DIR] registration
template information. Subsequent sections define the profile template information. Subsequent sections define the profile
definition. definition.
To: ietf-mime-directory@imc.org To: ietf-mime-directory@imc.org
Subject: Registration of application/directory MIME profile VCARD Subject: Registration of text/directory MIME profile VCARD
vCard MIME Directory Profile
Profile name: VCARD Profile name: VCARD
Profile purpose: To hold person object or white-pages type of Profile purpose: To hold person object or white-pages type of
directory information. The person schema captured in the directory directory information. The person schema captured in the directory
entries is that commonly found in an electronic business card. entries is that commonly found in an electronic business card.
Predefined MIME Directory types used: SOURCE, NAME, PROFILE, BEGIN, Predefined MIME Directory types used: SOURCE, NAME, PROFILE, BEGIN,
END, PROFILE. END.
Dawson & Howes [Page 2] May 1998
vCard MIME Directory Profile
Predefined MIME Directory parameters used: ENCODING, VALUE, CHARSET, Predefined MIME Directory parameters used: ENCODING, VALUE, CHARSET,
LANGUAGE, CONTEXT. LANGUAGE, CONTEXT.
New types: FN, N, NICKNAME, PHOTO, BDAY, ADR, LABEL, TEL, EMAIL, New types: FN, N, NICKNAME, PHOTO, BDAY, ADR, LABEL, TEL, EMAIL,
MAILER, TZ, GEO, TITLE, ROLE, LOGO, AGENT, ORG, CATEGORIES, NOTE, MAILER, TZ, GEO, TITLE, ROLE, LOGO, AGENT, ORG, CATEGORIES, NOTE,
PRODID, REV, SORT-STRING, SOUND, URL, UID, VERSION, CLASS, KEY PRODID, REV, SORT-STRING, SOUND, URL, UID, VERSION, CLASS, KEY
New parameters: TYPE New parameters: TYPE
Profile special notes: The type-grouping feature of [MIME-DIR] is Profile special notes: The vCard object MUST contain the FN, N and
supported by this profile to group related vCard properties about a VERSION types. The type-grouping feature of [MIME-DIR] is supported
directory entry. For example, vCard properties describing WORK or by this profile to group related vCard properties about a directory
HOME related characteristics MAY be grouped with a unique group entry. For example, vCard properties describing WORK or HOME related
label. characteristics MAY be grouped with a unique group label.
The profile permits the use of non-standard types (i.e., those The profile permits the use of non-standard types (i.e., those
identified with the prefix string "X-") as a flexible method for identified with the prefix string "X-") as a flexible method for
implementations to extend the functionality currently defined within implementations to extend the functionality currently defined within
this profile. this profile.
3. MIME Directory Features 2. MIME Directory Features
The vCard MIME Directory Profile makes use of many of the features The vCard MIME Directory Profile makes use of many of the features
defined by [MIME-DIR]. The following sections either clarify or defined by [MIME-DIR]. The following sections either clarify or
extend the content-type definition of [MIME-DIR]. extend the content-type definition of [MIME-DIR].
3.1 Predefined Type Usage 2.1 Predefined Type Usage
The vCard MIME Directory Profile uses the following predefined types The vCard MIME Directory Profile uses the following predefined types
from [MIME-DIR]. from [MIME-DIR].
3.1.1 BEGIN and END Type 2.1.1 BEGIN and END Type
The content entity MUST begin with the BEGIN type with a value of The content entity MUST begin with the BEGIN type with a value of
"VCARD". The content entity MUST end with the END type with a value "VCARD". The content entity MUST end with the END type with a value
of "VCARD". of "VCARD".
3.1.2 NAME Type 2.1.2 NAME Type
If the NAME type appears within a MIME entity conforming to this If the NAME type appears within a MIME entity conforming to this
profile, it's value is the displayable, presentation text associated profile, it's value is the displayable, presentation text associated
with the source for the vCard, as specified in the SOURCE type. with the source for the vCard, as specified in the SOURCE type.
3.1.3 PROFILE Type vCard MIME Directory Profile
2.1.3 PROFILE Type
If the PROFILE type appears within a MIME entity conforming to this If the PROFILE type appears within a MIME entity conforming to this
profile, it's value must be "VCARD". profile, it?s value MUST be "VCARD".
3.1.4 SOURCE Type 2.1.4 SOURCE Type
If the SOURCE type appears within a MIME entity conforming to this If the SOURCE type appears within a MIME entity conforming to this
profile, it's value provides information how to find the source for profile, it's value provides information how to find the source for
the vCard. the vCard.
Dawson & Howes [Page 3] May 1998 2.2 Predefined Type Parameter Usage
vCard MIME Directory Profile
3.2 Predefined Type Parameter Usage
The vCard MIME Directory Profile uses the following predefined types The vCard MIME Directory Profile uses the following predefined types
parameters as defined by [MIME-DIR]. parameters as defined by [MIME-DIR].
. LANGUAGE LANGUAGE
. ENCODING ENCODING
. VALUE VALUE
3.3 Predefined VALUE Type Usage 2.3 Predefined VALUE Type Usage
The predefined data type values specified in [MIME-DIR] MAY NOT be The predefined data type values specified in [MIME-DIR] MAY NOT be
repeated in COMMA separated value lists, unless specified by this repeated in COMMA separated value lists, unless specified by this
specification. specification.
3.4 Extensions To The Predefined VALUE Types 2.4 Extensions To The Predefined VALUE Types
The predefined data type values specified in [MIME-DIR] have been The predefined data type values specified in [MIME-DIR] have been
extended by the vCard profile to include a number of value types that extended by the vCard profile to include a number of value types that
are specific to this profile. are specific to this profile.
3.4.1 BINARY 2.4.1 BINARY
The "binary" value type specifies that the type value is inline, The "binary" value type specifies that the type value is inline,
encoded binary data. This value type may be specified in the PHOTO, encoded binary data. This value type may be specified in the PHOTO,
LOGO, SOUND, and KEY types. LOGO, SOUND, and KEY types.
If inline encoded binary data is specified, the ENCODING type If inline encoded binary data is specified, the ENCODING type
parameter must be used to specify the encoding format. The binary parameter MUST be used to specify the encoding format. The binary
data MUST be encoded using the "B" encoding format. Long lines of data MUST be encoded using the "B" encoding format. Long lines of
encoded binary data may be folded using the folding method defined in encoded binary data may be folded using the folding method defined in
[MIME-DIR]. [MIME-DIR].
The value type is defined by the following notation: The value type is defined by the following notation:
binary = <A "B" binary encoded string as defined by [RFC 2047].> binary = <A "B" binary encoded string as defined by [RFC 2047].>
vCard MIME Directory Profile
3.4.2 VCARD 2.4.2 VCARD
The "vcard" value type specifies that the type value is another The "vcard" value type specifies that the type value is another
vCard. This value type may be specified in the AGENT type. The value vCard. This value type may be specified in the AGENT type. The value
type is defined by this specification. Since each of the type type is defined by this specification. Since each of the type
declarations with in the vcard value type are being specified within declarations with in the vcard value type are being specified within
a type value themselves, they MUST be terminated with the backslash a type value themselves, they MUST be terminated with the backslash
escapement sequence "\n" or "\N", instead of the character sequence escapement sequence "\n" or "\N", instead of the character sequence
CRLF. For example, with the AGENT type a value would be specified as: CRLF. For example, with the AGENT type a value would be specified as
:
AGENT:BEGIN:VCARD\nFN:Joe Friday\nTEL:+1-919-555-7878\n AGENT:BEGIN:VCARD\nFN:Joe Friday\nTEL:+1-919-555-7878\n
TITLE:Area Administrator\, Assistant\n TITLE:Area Administrator\, Assistant\n
EMAIL;INTERNET:jfriday@host.com\n EMAIL;INTERNET:jfriday@host.com\n
END:VCARD END:VCARD
Dawson & Howes [Page 4] May 1998 2.4.3 PHONE-NUMBER
vCard MIME Directory Profile
3.4.3 PHONE-NUMBER
The "phone-number" value type specifies that the type value is a The "phone-number" value type specifies that the type value is a
telephone number. This value type may be specified in the TEL type. telephone number. This value type may be specified in the TEL type.
The value type is a text value that has the special semantics of a The value type is a text value that has the special semantics of a
telephone number as defined in [CCITT E.163] and [CCITT X.121]. telephone number as defined in [CCITT E.163] and [CCITT X.121].
3.4.4 UTC-OFFSET 2.4.4 UTC-OFFSET
The "utc-offset" value type specifies that the type value is a signed The "utc-offset" value type specifies that the type value is a signed
offset from UTC. This value type may be specified in the TZ type. offset from UTC. This value type may be specified in the TZ type.
The value type is an offset from Coordinated Universal Time (UTC). It The value type is an offset from Coordinated Universal Time (UTC). It
is specified as a positive or negative difference in units of hours is specified as a positive or negative difference in units of hours
and minutes (e.g., +hh:mm). The time is specified as a 24-hour clock. 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 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 to Hour and minutes are 2-digits with high order zeroes required to
maintain digit count. The extended format for ISO 8601 UTC offsets maintain digit count. The extended format for ISO 8601 UTC offsets
MUST be used. The extended format makes use of a colon character as a MUST be used. The extended format makes use of a colon character as a
separator of the hour and minute text fields. separator of the hour and minute text fields.
The value is defined by the following notation: The value is defined by the following notation:
time-hour = 2DIGIT ;00-23 time-hour = 2DIGIT ;00-23
time-minute = 2DIGIT ;00-59 time-minute = 2DIGIT ;00-59
utc-offset = ("+" / "-") time-hour ":" time-minute utc-offset = ("+" / "-") time-hour ":" time-minute
3.5 Structured Type Values 2.5 Structured Type Values
Compound type values are delimited by a field delimiter, specified by Compound type values are delimited by a field delimiter, specified by
the SEMI-COLON character (ASCII decimal 59). A SEMI-COLON in a the SEMI-COLON character (ASCII decimal 59). A SEMI-COLON in a
component of a compound property value must be escaped with a component of a compound property value MUST be escaped with a
BACKSLASH character (ASCII decimal 92). BACKSLASH character (ASCII decimal 92).
Lists of values are delimited by a list delimiter, specified by the Lists of values are delimited by a list delimiter, specified by the
COMMA character (ASCII decimal 44). A COMMA character in a value must COMMA character (ASCII decimal 44). A COMMA character in a value MUST
be escaped with a BACKSLASH character (ASCII decimal 92). be escaped with a BACKSLASH character (ASCII decimal 92).
vCard MIME Directory Profile
This profile supports the type grouping mechanism defined in [MIME- This profile supports the type grouping mechanism defined in [MIME-
DIR]. Grouping of related types is a useful technique to communicate DIR]. Grouping of related types is a useful technique to communicate
common semantics concerning the properties of a vCard. common semantics concerning the properties of a vCard.
3.6 Line Delimiting and Folding 2.6 Line Delimiting and Folding
This profile supports the same line delimiting and folding methods This profile supports the same line delimiting and folding methods
defined in [MIME-DIR]. defined in [MIME-DIR].
4. vCard Profile Features 3. vCard Profile Features
The vCard MIME Directory Profile Type contains directory information, The vCard MIME Directory Profile Type contains directory information,
typically pertaining to a single directory entry. The information is typically pertaining to a single directory entry. The information is
described using an attribute schema that is tailored for capturing described using an attribute schema that is tailored for capturing
personal contact information. The vCard can include attributes that personal contact information. The vCard can include attributes that
describe identification, delivery addressing, telecommunications describe identification, delivery addressing, telecommunications
Dawson & Howes [Page 5] May 1998
vCard MIME Directory Profile
addressing, geographical, organizational, general explanatory and addressing, geographical, organizational, general explanatory and
security and access information about the particular object security and access information about the particular object
associated with the vCard. associated with the vCard.
4.1 Identification Types 3.1 Identification Types
These types are used in the vCard profile to capture information These types are used in the vCard profile to capture information
associated with the identification and naming of the person or associated with the identification and naming of the person or
resource associated with the vCard. resource associated with the vCard.
4.1.1 FN Type Definition 3.1.1 FN Type Definition
To: ietf-mime-directory@imc.org To: ietf-mime-directory@imc.org
Subject: Registration of application/directory MIME type FN Subject: Registration of text/directory MIME type FN
Type name:FN Type name:FN
Type purpose: To specify the formatted text corresponding to the name Type purpose: To specify the formatted text corresponding to the name
of the object the vCard represents. of the object the vCard represents.
Type encoding: 8bit Type encoding: 8bit
Type value: A single text value. Type value: A single text value.
Type special notes: This type is based on the semantics of the X.520 Type special notes: This type is based on the semantics of the X.520
Common Name attribute. Common Name attribute. The property MUST be present if the vCard
conforms to this specification.
Type example: Type example:
FN:Mr. John Q. Public, Esq. FN:Mr. John Q. Public, Esq.
4.1.2 N Type Definition 3.1.2 N Type Definition
To: ietf-mime-directory@imc.org To: ietf-mime-directory@imc.org
vCard MIME Directory Profile
Subject: Registration of application/directory MIME type N Subject: Registration of text/directory MIME type N
Type name: N Type name: N
Type purpose: To specify the structured components of the name of the Type purpose: To specify the structured components of the name of the
object the vCard represents. object the vCard represents.
Type encoding: 8bit Type encoding: 8bit
Type value: A single structured text value. Each component may have Type value: A single structured text value. Each component may have
multiple values. multiple values.
Type special note: The structured text value corresponds, in Type special note: The structured text value corresponds, in
sequence, to the Family Name, Given Name, Additional Names, Honorific sequence, to the Family Name, Given Name, Additional Names, Honorific
Prefixes, and Honorific Suffixes. The text components are separated Prefixes, and Honorific Suffixes. The text components are separated
by the SEMI-COLON character (ASCII decimal 59) and possibly one or by the SEMI-COLON character (ASCII decimal 59) and possibly one or
more LWSP. Individual text components MAY include multiple text more LWSP. Individual text components MAY include multiple text
values (e.g., multiple Additional Names), separated by the COMMA values (e.g., multiple Additional Names), separated by the COMMA
Dawson & Howes [Page 6] May 1998
vCard MIME Directory Profile
character (ASCII decimal 44). This type is based on the semantics of character (ASCII decimal 44). This type is based on the semantics of
the X.520 individual name attributes. the X.520 individual name attributes. The property MUST be present in
the vCard object.
Type example: Type example:
N:Public;John;Quinlan;Mr.;Esq. N:Public;John;Quinlan;Mr.;Esq.
N:Stevenson;John;Philip,Paul;Dr.;Jr.,M.D.,A.C.P. N:Stevenson;John;Philip,Paul;Dr.;Jr.,M.D.,A.C.P.
4.1.3 NICKNAME Type Definition 3.1.3 NICKNAME Type Definition
To: ietf-mime-directory@imc.org To: ietf-mime-directory@imc.org
Subject: Registration of application/directory MIME type NICKNAME Subject: Registration of text/directory MIME type NICKNAME
Type name: NICKNAME Type name: NICKNAME
Type purpose: To specify the text corresponding to the nickname of Type purpose: To specify the text corresponding to the nickname of
the object the vCard represents. the object the vCard represents.
Type encoding: 8bit Type encoding: 8bit
Type value: One or more text values separated by a COMMA character Type value: One or more text values separated by a COMMA character
(ASCII decimal 44). (ASCII decimal 44).
Type special note: The nickname is the descriptive name given instead Type special note: The nickname is the descriptive name given instead
of or in addition to the one belonging to a person, place, or thing. of or in addition to the one belonging to a person, place, or thing.
It may also be used to specify a familiar form of a proper name It may also be used to specify a familiar form of a proper name
specified by the FN or N types. specified by the FN or N types.
Type example: Type example:
NICKNAME:Robbie NICKNAME:Robbie
vCard MIME Directory Profile
NICKNAME:Jim,Jimmie NICKNAME:Jim,Jimmie
4.1.4 PHOTO Type Definition 3.1.4 PHOTO Type Definition
To: ietf-mime-directory@imc.org To: ietf-mime-directory@imc.org
Subject: Registration of application/directory MIME type PHOTO Subject: Registration of text/directory MIME type PHOTO
Type name: PHOTO Type name: PHOTO
Type purpose: To specify an image or photograph information that Type purpose: To specify an image or photograph information that
annotates some aspect of the object the vCard represents. annotates some aspect of the object the vCard represents.
Type encoding: The encoding MUST be reset to "b" using the ENCODING Type encoding: The encoding MUST be reset to "b" using the ENCODING
parameter in order to specify inline, encoded binary data. If the parameter in order to specify inline, encoded binary data. If the
value is referenced by a URI value, then the default encoding of 8bit value is referenced by a URI value, then the default encoding of 8bit
is used and no explicit ENCODING parameter is needed. is used and no explicit ENCODING parameter is needed.
Dawson & Howes [Page 7] May 1998
vCard MIME Directory Profile
Type value: A single value. The default is binary. It may also be Type value: A single value. The default is binary. It may also be
reset to uri. The uri value may be used to specify a value outside of reset to uri. The uri value may be used to specify a value outside of
this MIME entity. this MIME entity.
Type special notes: The type MAY include the type parameter "TYPE" to Type special notes: The type MAY include the type parameter "TYPE" to
specify the graphic image format type. The TYPE parameter values MUST specify the graphic image format type. The TYPE parameter values MUST
be one of the IANA registered image formats or a non-standard image be one of the IANA registered image formats or a non-standard image
format. format.
Type example: Type example:
PHOTO;VALUE=uri:=http://www.abc.com/pub/photos PHOTO;VALUE=uri:=http://www.abc.com/pub/photos
/jqpublic.gif /jqpublic.gif
PHOTO;ENCODING=b;TYPE=JPEG:MIICajCCAdOgAwIBAgICBEUwDQYJKoZIhvcN PHOTO;ENCODING=b;TYPE=JPEG:MIICajCCAdOgAwIBAgICBEUwDQYJKoZIhvcN
AQEEBQAwdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05ldHNjYXBlIENvbW11bm AQEEBQAwdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05ldHNjYXBlIENvbW11bm
ljYXRpb25zIENvcnBvcmF0aW9uMRwwGgYDVQQLExNJbmZvcm1hdGlvbiBTeXN0 ljYXRpb25zIENvcnBvcmF0aW9uMRwwGgYDVQQLExNJbmZvcm1hdGlvbiBTeXN0
<...remainder of "B" encoded binary data...> <...remainder of "B" encoded binary data...>
4.1.5 BDAY Type Definition 3.1.5 BDAY Type Definition
To: ietf-mime-directory@imc.org To: ietf-mime-directory@imc.org
Subject: Registration of application/directory MIME type BDAY Subject: Registration of text/directory MIME type BDAY
Type name: BDAY Type name: BDAY
Type purpose: To specify the birthdate of the object the vCard Type purpose: To specify the birthdate of the object the vCard
represents. represents.
Type encoding: 8bit Type encoding: 8bit
Type value: The default is a single date value. It may also be reset Type value: The default is a single date value. It may also be reset
to a single date-time value. to a single date-time value.
vCard MIME Directory Profile
Type examples: Type examples:
BDAY:1996-04-15 BDAY:1996-04-15
BDAY:1953-10-15T23:10:00Z BDAY:1953-10-15T23:10:00Z
BDAY:1987-09-27T08:30:00-06:00 BDAY:1987-09-27T08:30:00-06:00
4.2 Delivery Addressing Types 3.2 Delivery Addressing Types
These types are concerned with information related to the delivery These types are concerned with information related to the delivery
addressing or label for the vCard object. addressing or label for the vCard object.
4.2.1 ADR Type Definition 3.2.1 ADR Type Definition
To: ietf-mime-directory@imc.org To: ietf-mime-directory@imc.org
Subject: Registration of application/directory MIME type ADR Subject: Registration of text/directory MIME type ADR
Dawson & Howes [Page 8] May 1998
vCard MIME Directory Profile
Type name: ADR Type name: ADR
Type purpose: To specify the structured components of the delivery Type purpose: To specify the structured components of the delivery
address for the vCard object. address for the vCard object.
Type encoding: 8bit Type encoding: 8bit
Type value: A single structured text value, separated by the SEMI- Type value: A single structured text value, separated by the SEMI-
COLON character (ASCII decimal 59) and optionally one or more LWSP. COLON character (ASCII decimal 59) and optionally one or more LWSP.
Type special notes: The structured text value consists of a sequence Type special notes: The structured text value consists of a sequence
of address components. The component values MUST be specified in of address components. The component values MUST be specified in
their corresponding position. The structured text value corresponds, their corresponding position. The structured text value corresponds,
in sequence, to the post office box; the extended address; the street in sequence, to the post office box; the extended address; the street
address; the locality (e.g., city); the region (e.g., state or address; the locality (e.g., city); the region (e.g., state or
province); the postal code; the country name. When a component value province); the postal code; the country name. When a component value
is missing, the associated component separator must still be is missing, the associated component separator MUST still be
specified. specified.
The type may include the type parameter "TYPE" to specify the The type may include the type parameter "TYPE" to specify the
delivery address type. The TYPE parameter values may include "dom" to delivery address type. The TYPE parameter values may include "dom" to
indicate a domestic delivery address; "intl" to indicate an indicate a domestic delivery address; "intl" to indicate an
international delivery address; "postal" to indicate a postal international delivery address; "postal" to indicate a postal
delivery address; "parcel" to indicate a parcel delivery address; delivery address; "parcel" to indicate a parcel delivery address;
"home" to indicate a delivery address for a residence; "work" to "home" to indicate a delivery address for a residence; "work" to
indicate delivery address for a place of work; and "pref" to indicate indicate delivery address for a place of work; and "pref" to indicate
the preferred delivery address when more than one address is the preferred delivery address when more than one address is
specified. These type parameter values may be specified as a specified. These type parameter values may be specified as a
parameter list (i.e., "TYPE=dom;TYPE=postal") or as a value list parameter list (i.e., "TYPE=dom;TYPE=postal") or as a value list
(i.e., "TYPE=dom,postal"). This type is based on semantics of the (i.e., "TYPE=dom,postal"). This type is based on semantics of the
X.520 geographical and postal addressing attributes. The default is X.520 geographical and postal addressing attributes. The default is
"TYPE=intl,postal,parcel,work". The default can be overridden to some "TYPE=intl,postal,parcel,work". The default can be overridden to some
other set of values by specifying one or more alternate values. For other set of values by specifying one or more alternate values. For
example, the default can be reset to "TYPE=dom,postal,work,home" to example, the default can be reset to "TYPE=dom,postal,work,home" to
vCard MIME Directory Profile
specify a domestic delivery address for postal delivery to a specify a domestic delivery address for postal delivery to a
residence that is also used for work. residence that is also used for work.
Type example: In this example the post office box and the extended Type example: In this example the post office box and the extended
address are absent. address are absent.
ADR;TYPE=dom,home,postal,parcel:;;123 Main ADR;TYPE=dom,home,postal,parcel:;;123 Main
Street;Any Town;CA;91921-1234 Street;Any Town;CA;91921-1234
4.2.2 LABEL Type Definition 3.2.2 LABEL Type Definition
To: ietf-mime-directory@imc.org To: ietf-mime-directory@imc.org
Subject: Registration of application/directory MIME type LABEL Subject: Registration of text/directory MIME type LABEL
Type name: LABEL Type name: LABEL
Type purpose: To specify the formatted text corresponding to delivery Type purpose: To specify the formatted text corresponding to delivery
address of the object the vCard represents. address of the object the vCard represents.
Dawson & Howes [Page 9] May 1998
vCard MIME Directory Profile
Type encoding: 8bit Type encoding: 8bit
Type value: A single text value. Type value: A single text value.
Type special notes: The type value is formatted text that may be used Type special notes: The type value is formatted text that may be used
to present a delivery address label for the vCard object. The type to present a delivery address label for the vCard object. The type
may include the type parameter "TYPE" to specify delivery label type. may include the type parameter "TYPE" to specify delivery label type.
The TYPE parameter values may include "dom" to indicate a domestic The TYPE parameter values may include "dom" to indicate a domestic
delivery label; "intl" to indicate an international delivery label; delivery label; "intl" to indicate an international delivery label;
"postal" to indicate a postal delivery label; "parcel" to indicate a "postal" to indicate a postal delivery label; "parcel" to indicate a
skipping to change at line 548 skipping to change at page 12, line 47
residence; "work" to indicate delivery label for a place of work; and residence; "work" to indicate delivery label for a place of work; and
"pref" to indicate the preferred delivery label when more than one "pref" to indicate the preferred delivery label when more than one
label is specified. These type parameter values may specified as a label is specified. These type parameter values may specified as a
parameter list (i.e., "TYPE=dom;TYPE=postal") or as a value list parameter list (i.e., "TYPE=dom;TYPE=postal") or as a value list
(i.e., "TYPE=dom,postal"). This type is based on semantics of the (i.e., "TYPE=dom,postal"). This type is based on semantics of the
X.520 geographical and postal addressing attributes. The default is X.520 geographical and postal addressing attributes. The default is
"TYPE=intl,postal,parcel,work". The default can be overridden to some "TYPE=intl,postal,parcel,work". The default can be overridden to some
other set of values by specifying one or more alternate values. For other set of values by specifying one or more alternate values. For
example, the default can be reset to "TYPE=intl,post,parcel,home" to example, the default can be reset to "TYPE=intl,post,parcel,home" to
specify an international delivery label for both postal and parcel specify an international delivery label for both postal and parcel
delivery to a residencial location. delivery to a residential location.
Type example: A multi-line address label. Type example: A multi-line address label.
LABEL;TYPE=dom,home,postal,parcel:Mr.John Q. Public, Esq.\n LABEL;TYPE=dom,home,postal,parcel:Mr.John Q. Public, Esq.\n
Mail Drop: TNE QB\n Mail Drop: TNE QB\n
123 Main Street\n 123 Main Street\n
Any Town, CA 91921-1234\n Any Town, CA 91921-1234\n
U.S.A. U.S.A.
4.3 Telecommunications Addressing Types vCard MIME Directory Profile
3.3 Telecommunications Addressing Types
These types are concerned with information associated with the These types are concerned with information associated with the
telecommunications addressing of the object the vCard represents. telecommunications addressing of the object the vCard represents.
4.3.1 TEL Type Definition 3.3.1 TEL Type Definition
To: ietf-mime-directory@imc.org To: ietf-mime-directory@imc.org
Subject: Registration of application/directory MIME type TEL Subject: Registration of text/directory MIME type TEL
Type name: TEL Type name: TEL
Type purpose: To specify the telephone number for telephony Type purpose: To specify the telephone number for telephony
communication with the object the vCard represents. communication with the object the vCard represents.
Type encoding: 8bit Type encoding: 8bit
Type value: A single phone-number. Type value: A single phone-number.
Type special notes: The value of this type is specified in a Type special notes: The value of this type is specified in a
canonical form in order to specify an unambiguous representation of canonical form in order to specify an unambiguous representation of
Dawson & Howes [Page 10] May 1998
vCard MIME Directory Profile
the globally unique telephone endpoint. This type is based on the the globally unique telephone endpoint. This type is based on the
X.500 Telephone Number attribute. X.500 Telephone Number attribute.
The type may include the type parameter "TYPE" to specify intended The type may include the type parameter "TYPE" to specify intended
use for the telephone number. The TYPE parameter values may include: use for the telephone number. The TYPE parameter values may include:
"home" to indicate a telephone number associated with a residence, "home" to indicate a telephone number associated with a residence,
"msg" to indicate the telephone number has voice messaging support, "msg" to indicate the telephone number has voice messaging support,
"work" to indicate a telephone number associated with a place of "work" to indicate a telephone number associated with a place of
work, "pref" to indicate a preferred-use telephone number, "voice" to work, "pref" to indicate a preferred-use telephone number, "voice" to
indicate a voice telephone number, "fax" to indicate a facsimile indicate a voice telephone number, "fax" to indicate a facsimile
skipping to change at line 613 skipping to change at page 14, line 4
a parameter list (i.e., "TYPE=work;TYPE=voice") or as a value list a parameter list (i.e., "TYPE=work;TYPE=voice") or as a value list
(i.e., "TYPE=work,voice"). The default may be overridden to another (i.e., "TYPE=work,voice"). The default may be overridden to another
set of values by specifying one or more alternate values. For set of values by specifying one or more alternate values. For
example, the default TYPE of "voice" can be reset to a WORK and HOME, example, the default TYPE of "voice" can be reset to a WORK and HOME,
VOICE and FAX telephone number by the value list VOICE and FAX telephone number by the value list
"TYPE=work,home,voice,fax". "TYPE=work,home,voice,fax".
Type example: Type example:
TEL;TYPE=work,voice,pref,msg:+1-213-555-1234 TEL;TYPE=work,voice,pref,msg:+1-213-555-1234
vCard MIME Directory Profile
4.3.2 EMAIL Type Definition 3.3.2 EMAIL Type Definition
To: ietf-mime-directory@imc.org To: ietf-mime-directory@imc.org
Subject: Registration of application/directory MIME type EMAIL Subject: Registration of text/directory MIME type EMAIL
Type name: EMAIL Type name: EMAIL
Type purpose: To specify the electronic mail address for Type purpose: To specify the electronic mail address for
communication with the object the vCard represents. communication with the object the vCard represents.
Type encoding: 8bit Type encoding: 8bit
Type value: A single text value. Type value: A single text value.
skipping to change at line 640 skipping to change at page 14, line 32
specify the format or preference of the electronic mail address. The specify the format or preference of the electronic mail address. The
TYPE parameter values may include: "internet" to indicate an Internet TYPE parameter values may include: "internet" to indicate an Internet
addressing type, "x400" to indicate a X.400 addressing type or "pref" addressing type, "x400" to indicate a X.400 addressing type or "pref"
to indicate a preferred-use email address when more than one is to indicate a preferred-use email address when more than one is
specified. Another IANA registered address type may also be specified. Another IANA registered address type may also be
specified. The default email type is "internet". A non-standard value specified. The default email type is "internet". A non-standard value
may also be specified. may also be specified.
Type example: Type example:
Dawson & Howes [Page 11] May 1998
vCard MIME Directory Profile
EMAIL;TYPE=internet:jqpublic@xyz.dom1.com EMAIL;TYPE=internet:jqpublic@xyz.dom1.com
EMAIL;TYPE=internet:jdoe@isp.net EMAIL;TYPE=internet:jdoe@isp.net
EMAIL;TYPE=internet,pref:jane_doe@abc.com EMAIL;TYPE=internet,pref:jane_doe@abc.com
4.3.3 MAILER Type Definition 3.3.3 MAILER Type Definition
To: ietf-mime-directory@imc.org To: ietf-mime-directory@imc.org
Subject: Registration of application/directory MIME type MAILER Subject: Registration of text/directory MIME type MAILER
Type name: MAILER Type name: MAILER
Type purpose: To specify the type of electronic mail software that is Type purpose: To specify the type of electronic mail software that is
used by the individual associated with the vCard. used by the individual associated with the vCard.
Type encoding: 8bit Type encoding: 8bit
Type value: A single text value. Type value: A single text value.
Type special notes: This information may provide assistance to a Type special notes: This information may provide assistance to a
correspondent regarding the type of data representation which can be correspondent regarding the type of data representation which can be
used, and how they may be packaged. This property is based on the used, and how they may be packaged. This property is based on the
private MIME type X-Mailer that is generally implemented by MIME user private MIME type X-Mailer that is generally implemented by MIME user
agent products. agent products.
vCard MIME Directory Profile
Type example: Type example:
MAILER:PigeonMail 2.1 MAILER:PigeonMail 2.1
4.4 Geographical Types 3.4 Geographical Types
These types are concerned with information associated with These types are concerned with information associated with
geographical positions or regions associated with the object the geographical positions or regions associated with the object the
vCard represents. vCard represents.
4.4.1 TZ Type Definition 3.4.1 TZ Type Definition
To: ietf-mime-directory@imc.org To: ietf-mime-directory@imc.org
Subject: Registration of application/directory MIME type TZ Subject: Registration of text/directory MIME type TZ
Type name: TZ Type name: TZ
Type purpose: To specify information related to the time zone of the Type purpose: To specify information related to the time zone of the
object the vCard represents. object the vCard represents.
Type encoding: 8bit. Type encoding: 8bit.
Type value: The default is a single utc-offset value. It may also be Type value: The default is a single utc-offset value. It may also be
reset to a single text value. reset to a single text value.
Type special notes: The type value consists of a single value. Type special notes: The type value consists of a single value.
Dawson & Howes [Page 12] May 1998
vCard MIME Directory Profile
Type examples: Type examples:
TZ:-05:00 TZ:-05:00
TZ;VALUE=text:-05:00; EST; Raleigh/North America TZ;VALUE=text:-05:00; EST; Raleigh/North America
;This example has a single value, not a structure text value. ;This example has a single value, not a structure text value.
4.4.2 GEO Type Definition 3.4.2 GEO Type Definition
To: ietf-mime-directory@imc.org To: ietf-mime-directory@imc.org
Subject: Registration of application/directory MIME type GEO Subject: Registration of text/directory MIME type GEO
Type name: GEO Type name: GEO
Type purpose: To specify information related to the global Type purpose: To specify information related to the global
positioning of the object the vCard represents. positioning of the object the vCard represents.
Type encoding: 8bit. Type encoding: 8bit.
Type value: Two float values separated by the SEMI-COLON character Type value: Two float values separated by the SEMI-COLON character
(ASCII decimal 59). (ASCII decimal 59).
Type special notes: This type specifies information related to the Type special notes: This type specifies information related to the
global position of the object associated with the vCard. The value global position of the object associated with the vCard. The value
vCard MIME Directory Profile
specifies latitude and longitude, in that order (i.e., "LAT LON" specifies latitude and longitude, in that order (i.e., "LAT LON"
ordering). The longitude represents the location east and west of the ordering). The longitude represents the location east and west of the
prime meridian as a positive or negative real number, respectively. prime meridian as a positive or negative real number, respectively.
The latitude represents the location north and south of the equator The latitude represents the location north and south of the equator
as a positive or negative real number, respectively. The longitude as a positive or negative real number, respectively. The longitude
and latitude values must be specified as decimal degrees and should and latitude values MUST be specified as decimal degrees and should
be specified to six decimal places. This will allow for granularity be specified to six decimal places. This will allow for granularity
within a meter of the geographical position. The text components are within a meter of the geographical position. The text components are
separated by the SEMI-COLON character (ASCII decimal 59). The simple separated by the SEMI-COLON character (ASCII decimal 59). The simple
formula for converting degrees-minutes-seconds into decimal degrees formula for converting degrees-minutes-seconds into decimal degrees
is: is:
decimal = degrees + minutes/60 + seconds/3600. decimal = degrees + minutes/60 + seconds/3600.
Type example: Type example:
GEO:37.386013;-122.082932 GEO:37.386013;-122.082932
4.5 Organizational Types 3.5 Organizational Types
These types are concerned with information associated with These types are concerned with information associated with
characteristics of the organization or organizational units of the characteristics of the organization or organizational units of the
object the vCard represents. object the vCard represents.
4.5.1 TITLE Type Definition 3.5.1 TITLE Type Definition
To: ietf-mime-directory@imc.org To: ietf-mime-directory@imc.org
Subject: Registration of application/directory MIME type TITLE Subject: Registration of text/directory MIME type TITLE
Dawson & Howes [Page 13] May 1998
vCard MIME Directory Profile
Type name: TITLE Type name: TITLE
Type purpose: To specify the job title, functional position or Type purpose: To specify the job title, functional position or
function of the object the vCard represents. function of the object the vCard represents.
Type encoding: 8bit Type encoding: 8bit
Type value: A single text value. Type value: A single text value.
Type special notes: This type is based on the X.520 Title attribute. Type special notes: This type is based on the X.520 Title attribute.
Type example: Type example:
TITLE:Director, Research and Development TITLE:Director, Research and Development
4.5.2 ROLE Type Definition 3.5.2 ROLE Type Definition
To: ietf-mime-directory@imc.org To: ietf-mime-directory@imc.org
Subject: Registration of application/directory MIME type ROLE Subject: Registration of text/directory MIME type ROLE
Type name: ROLE Type name: ROLE
vCard MIME Directory Profile
Type purpose: To specify information concerning the role, occupation, Type purpose: To specify information concerning the role, occupation,
or business category of the object the vCard represents. or business category of the object the vCard represents.
Type encoding: 8bit Type encoding: 8bit
Type value: A single text value. Type value: A single text value.
Type special notes: This type is based on the X.520 Business Category Type special notes: This type is based on the X.520 Business Category
explanatory attribute. This property is included as an organizational explanatory attribute. This property is included as an organizational
type to avoid confusion with the semantics of the TITLE type and type to avoid confusion with the semantics of the TITLE type and
incorrect usage of that type when the semantics of this type is incorrect usage of that type when the semantics of this type is
intended. intended.
Type example: Type example:
ROLE:Programmer ROLE:Programmer
4.5.3 LOGO Type Definition 3.5.3 LOGO Type Definition
To: ietf-mime-directory@imc.org To: ietf-mime-directory@imc.org
Subject: Registration of application/directory MIME type LOGO Subject: Registration of text/directory MIME type LOGO
Type name: LOGO Type name: LOGO
Type purpose: To specify a graphic image of a logo associated with Type purpose: To specify a graphic image of a logo associated with
the object the vCard represents. the object the vCard represents.
Type encoding: The encoding MUST be reset to "b" using the ENCODING Type encoding: The encoding MUST be reset to "b" using the ENCODING
parameter in order to specify inline, encoded binary data. If the parameter in order to specify inline, encoded binary data. If the
Dawson & Howes [Page 14] May 1998
vCard MIME Directory Profile
value is referenced by a URI value, then the default encoding of 8bit value is referenced by a URI value, then the default encoding of 8bit
is used and no explicit ENCODING parameter is needed. is used and no explicit ENCODING parameter is needed.
Type value: A single value. The default is binary. It may also be Type value: A single value. The default is binary. It may also be
reset to uri. The uri value may be used to specify a value outside of reset to uri. The uri value may be used to specify a value outside of
this MIME entity. this MIME entity.
Type special notes: The type MAY include the type parameter "TYPE" to Type special notes: The type MAY include the type parameter "TYPE" to
specify the graphic image format type. The TYPE parameter values MUST specify the graphic image format type. The TYPE parameter values MUST
be one of the IANA registered image formats or a non-standard image be one of the IANA registered image formats or a non-standard image
format. format.
Type example: Type example:
LOGO;VALUE=uri:http://www.abc.com/pub/logos/abccorp.jpg LOGO;VALUE=uri:http://www.abc.com/pub/logos/abccorp.jpg
LOGO;ENCODING=b;TYPE=JPEG:MIICajCCAdOgAwIBAgICBEUwDQYJKoZIhvcN LOGO;ENCODING=b;TYPE=JPEG:MIICajCCAdOgAwIBAgICBEUwDQYJKoZIhvcN
AQEEBQAwdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05ldHNjYXBlIENvbW11bm AQEEBQAwdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05ldHNjYXBlIENvbW11bm
ljYXRpb25zIENvcnBvcmF0aW9uMRwwGgYDVQQLExNJbmZvcm1hdGlvbiBTeXN0 ljYXRpb25zIENvcnBvcmF0aW9uMRwwGgYDVQQLExNJbmZvcm1hdGlvbiBTeXN0
<...the remainder of "B" encoded binary data...> <...the remainder of "B" encoded binary data...>
vCard MIME Directory Profile
4.5.4 AGENT Type Definition 3.5.4 AGENT Type Definition
To: ietf-mime-directory@imc.org To: ietf-mime-directory@imc.org
Subject: Registration of application/directory MIME type AGENT Subject: Registration of text/directory MIME type AGENT
Type name: AGENT Type name: AGENT
Type purpose: To specify information about another person who will Type purpose: To specify information about another person who will
act on behalf of the individual or resource associated with the act on behalf of the individual or resource associated with the
vCard. vCard.
Type encoding: 8-bit. Type encoding: 8-bit.
Type value: The default is a single vcard value. It may also be reset Type value: The default is a single vcard value. It may also be reset
skipping to change at line 873 skipping to change at page 18, line 38
represents somebody or something that is separately addressable. represents somebody or something that is separately addressable.
Type example: Type example:
AGENT;VALUE=uri: AGENT;VALUE=uri:
CID:JQPUBLIC.part3.960129T083020.xyzMail@host3.com CID:JQPUBLIC.part3.960129T083020.xyzMail@host3.com
AGENT:BEGIN:VCARD\n AGENT:BEGIN:VCARD\n
FN:Susan Thomas\n FN:Susan Thomas\n
TEL:+1-919-555-1234\n TEL:+1-919-555-1234\n
Dawson & Howes [Page 15] May 1998
vCard MIME Directory Profile
EMAIL;INTERNET:sthomas@host.com\n EMAIL;INTERNET:sthomas@host.com\n
END:VCARD\n END:VCARD\n
4.5.5 ORG Type Definition 3.5.5 ORG Type Definition
To: ietf-mime-directory@imc.org To: ietf-mime-directory@imc.org
Subject: Registration of application/directory MIME type ORG Subject: Registration of text/directory MIME type ORG
Type name: ORG Type name: ORG
Type purpose: To specify the organizational name and units associated Type purpose: To specify the organizational name and units associated
with the vCard. with the vCard.
Type encoding: 8bit Type encoding: 8bit
Type value: A single structured text value consisting of components Type value: A single structured text value consisting of components
separated the SEMI-COLON character (ASCII decimal 59). separated the SEMI-COLON character (ASCII decimal 59).
Type special notes: The type is based on the X.520 Organization Name Type special notes: The type is based on the X.520 Organization Name
and Organization Unit attributes. The type value is a structured text and Organization Unit attributes. The type value is a structured text
vCard MIME Directory Profile
consisting of the organization name, followed by one or more levels consisting of the organization name, followed by one or more levels
of organizational unit names. of organizational unit names.
Type example: A type value consisting of an organizational name, Type example: A type value consisting of an organizational name,
organizational unit #1 name and organizational unit #2 name. organizational unit #1 name and organizational unit #2 name.
ORG:ABC, Inc.;North American Division;Marketing ORG:ABC, Inc.;North American Division;Marketing
4.6 Explanatory Types 3.6 Explanatory Types
These types are concerned with additional explanations, such as that These types are concerned with additional explanations, such as that
related to informational notes or revisions specific to the vCard. related to informational notes or revisions specific to the vCard.
4.6.1 CATEGORIES Type Definition 3.6.1 CATEGORIES Type Definition
To: ietf-mime-directory@imc.org To: ietf-mime-directory@imc.org
Subject: Registration of application/directory MIME type CATEGORIES Subject: Registration of text/directory MIME type CATEGORIES
Type name: CATEGORIES Type name: CATEGORIES
Type purpose: To specify application category information about the Type purpose: To specify application category information about the
vCard. vCard.
Type encoding: 8bit Type encoding: 8bit
Type value: One or more text values separated by a COMMA character Type value: One or more text values separated by a COMMA character
(ASCII decimal 44). (ASCII decimal 44).
Type example: Type example:
CATEGORIES:TRAVEL AGENT CATEGORIES:TRAVEL AGENT
Dawson & Howes [Page 16] May 1998
vCard MIME Directory Profile
CATEGORIES:INTERNET,IETF,INDUSTRY,INFORMATION TECHNOLOGY CATEGORIES:INTERNET,IETF,INDUSTRY,INFORMATION TECHNOLOGY
4.6.2 NOTE Type Definition 3.6.2 NOTE Type Definition
To: ietf-mime-directory@imc.org To: ietf-mime-directory@imc.org
Subject: Registration of application/directory MIME type NOTE Subject: Registration of text/directory MIME type NOTE
Type name: NOTE Type name: NOTE
Type purpose: To specify supplemental information or a comment that Type purpose: To specify supplemental information or a comment that
is associated with the vCard. is associated with the vCard.
Type encoding: 8bit Type encoding: 8bit
Type value: A single text value. Type value: A single text value.
Type special notes: The type is based on the X.520 Description Type special notes: The type is based on the X.520 Description
attribute. attribute.
vCard MIME Directory Profile
Type example: Type example:
NOTE:This fax number is operational 0800 to 1715 NOTE:This fax number is operational 0800 to 1715
EST, Mon-Fri. EST, Mon-Fri.
4.6.3 PRODID Type Definition 3.6.3 PRODID Type Definition
To: ietf-mime-directory@imc.org To: ietf-mime-directory@imc.org
Subject: Registration of application/directory MIME type PRODID Subject: Registration of text/directory MIME type PRODID
Type name: PRODID Type name: PRODID
Type purpose: To specify the identifier for the product that created Type purpose: To specify the identifier for the product that created
the vCard object. the vCard object.
Type encoding: 8-bit. Type encoding: 8-bit.
Type value: A single text value. Type value: A single text value.
Type special notes: Implementations SHOULD use a method such as that Type special notes: Implementations SHOULD use a method such as that
specified for Formal Public Identifiers in ISO 9070 to assure that specified for Formal Public Identifiers in ISO 9070 to assure that
the text value is unique. the text value is unique.
Type example: Type example:
PRODID:-//ONLINE DIRECTORY//NONSGML Version 1//EN PRODID:-//ONLINE DIRECTORY//NONSGML Version 1//EN
4.6.4 REV Type Definition 3.6.4 REV Type Definition
To: ietf-mime-directory@imc.org To: ietf-mime-directory@imc.org
Subject: Registration of application/directory MIME type REV Subject: Registration of text/directory MIME type REV
Dawson & Howes [Page 17] May 1998
vCard MIME Directory Profile
Type name: REV Type name: REV
Type purpose: To specify revision information about the current Type purpose: To specify revision information about the current
vCard. vCard.
Type encoding: 8-bit. Type encoding: 8-bit.
Type value: The default is a single date-time value. May also be Type value: The default is a single date-time value. May also be
reset to a single date value. reset to a single date value.
Type special notes: The value distinguishes the current revision of Type special notes: The value distinguishes the current revision of
the information in this vCard for other renditions of the the information in this vCard for other renditions of the
information. information.
Type example: Type example:
REV:1995-10-31T22:27:10Z REV:1995-10-31T22:27:10Z
REV:1997-11-15 REV:1997-11-15
vCard MIME Directory Profile
4.6.5 SORT-STRING Type Definition 3.6.5 SORT-STRING Type Definition
To: ietf-mime-directory@imc.org To: ietf-mime-directory@imc.org
Subject: Registration of text/directory MIME type SORT-STRING Subject: Registration of text/directory MIME type SORT-STRING
Type Name: SORT-STRING Type Name: SORT-STRING
Type purpose: To specify the text to be used in national language Type purpose: To specify the text to be used in national language
specific sorting of the values specified by the FN or N types. specific sorting of the values specified by the FN or N types.
skipping to change at line 1044 skipping to change at page 21, line 36
within a sequence of sorted vCards. If this type is present in a within a sequence of sorted vCards. If this type is present in a
vCard, then this value should be used for sorting the vCard, instead vCard, then this value should be used for sorting the vCard, instead
of the values of the FN or N types. of the values of the FN or N types.
Type example: The following would define the sort string "Harten" for Type example: The following would define the sort string "Harten" for
the "FN:Rene J. van der Harten" or "N:van der the "FN:Rene J. van der Harten" or "N:van der
Harten;Rene;J.;Sir;R.D.O.N.". Harten;Rene;J.;Sir;R.D.O.N.".
SORT-STRING:Harten SORT-STRING:Harten
4.6.6 SOUND Type Definition 3.6.6 SOUND Type Definition
To: ietf-mime-directory@imc.org To: ietf-mime-directory@imc.org
Dawson & Howes [Page 18] May 1998 Subject: Registration of text/directory MIME type SOUND
vCard MIME Directory Profile
Subject: Registration of application/directory MIME type SOUND
Type name: SOUND Type name: SOUND
Type purpose: To specify a digital sound content information that Type purpose: To specify a digital sound content information that
annotates some aspect of the vCard. By default this type is used to annotates some aspect of the vCard. By default this type is used to
specify the proper pronunciation of the name type value of the vCard. specify the proper pronunciation of the name type value of the vCard.
Type encoding: The encoding MUST be reset to "b" using the ENCODING Type encoding: The encoding MUST be reset to "b" using the ENCODING
parameter in order to specify inline, encoded binary data. If the parameter in order to specify inline, encoded binary data. If the
value is referenced by a URI value, then the default encoding of 8bit value is referenced by a URI value, then the default encoding of 8bit
is used and no explicit ENCODING parameter is needed. is used and no explicit ENCODING parameter is needed.
Type value: A single value. The default is binary. It may also be Type value: A single value. The default is binary. It may also be
reset to uri. The uri value may be used to specify a value outside of reset to uri. The uri value may be used to specify a value outside of
this MIME entity. this MIME entity.
vCard MIME Directory Profile
Type special notes: The type MAY include the type parameter "TYPE" to Type special notes: The type MAY include the type parameter "TYPE" to
specify the audio format type. The TYPE parameter values MUST be one specify the audio format type. The TYPE parameter values MUST be one
of the IANA registered audio formats or a non-standard audio format. of the IANA registered audio formats or a non-standard audio format.
Type example: Type example:
SOUND;TYPE=BASIC;VALUE=uri:CID:JOHNQPUBLIC.part8. SOUND;TYPE=BASIC;VALUE=uri:CID:JOHNQPUBLIC.part8.
19960229T080000.xyzMail@host1.com 19960229T080000.xyzMail@host1.com
SOUND;TYPE=BASIC;ENCODING=b:MIICajCCAdOgAwIBAgICBEUwDQYJKoZIhvcN SOUND;TYPE=BASIC;ENCODING=b:MIICajCCAdOgAwIBAgICBEUwDQYJKoZIhvcN
AQEEBQAwdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05ldHNjYXBlIENvbW11bm AQEEBQAwdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05ldHNjYXBlIENvbW11bm
ljYXRpb25zIENvcnBvcmF0aW9uMRwwGgYDVQQLExNJbmZvcm1hdGlvbiBTeXN0 ljYXRpb25zIENvcnBvcmF0aW9uMRwwGgYDVQQLExNJbmZvcm1hdGlvbiBTeXN0
<...the remainder of "B" encoded binary data...> <...the remainder of "B" encoded binary data...>
4.6.7 UID Type Definition 3.6.7 UID Type Definition
To: ietf-mime-directory@imc.org To: ietf-mime-directory@imc.org
Subject: Registration of application/directory MIME type UID Subject: Registration of text/directory MIME type UID
Type name: UID Type name: UID
Type purpose: To specify a value that represents a globally unique Type purpose: To specify a value that represents a globally unique
identifier corresponding to the individual or resource associated identifier corresponding to the individual or resource associated
with the vCard. with the vCard.
Type encoding: 8bit. Type encoding: 8bit.
Type value: A single text value. Type value: A single text value.
Type special notes: The type is used to uniquely identify the object Type special notes: The type is used to uniquely identify the object
that the vCard represents. that the vCard represents.
The type may include the type parameter "TYPE" to specify the format The type may include the type parameter "TYPE" to specify the format
of the identifier. The TYPE parameter value may be any IANA of the identifier. The TYPE parameter value may be any IANA
registered identifier format. The value may also be a non-standard registered identifier format. The value may also be a non-standard
format. format.
Dawson & Howes [Page 19] May 1998
vCard MIME Directory Profile
Type example: Type example:
UID:19950401-080045-40000F192713-0052 UID:19950401-080045-40000F192713-0052
4.6.8 URL Type Definition 3.6.8 URL Type Definition
To: ietf-mime-directory@imc.org To: ietf-mime-directory@imc.org
Subject: Registration of application/directory MIME type URL Subject: Registration of text/directory MIME type URL
Type name: URL Type name: URL
Type purpose: To specify a uniform resource locator associated with Type purpose: To specify a uniform resource locator associated with
the object that the vCard refers to. the object that the vCard refers to.
vCard MIME Directory Profile
Type encoding: 8bit Type encoding: 8bit
Type value: A single uri value. Type value: A single uri value.
Type example: Type example:
URL:http://www.swbyps.restaurant.french/~chezchic.html URL:http://www.swbyps.restaurant.french/~chezchic.html
4.6.9 VERSION Type Definition 3.6.9 VERSION Type Definition
To: ietf-mime-directory@imc.org To: ietf-mime-directory@imc.org
Subject: Registration of application/directory MIME type VERSION Subject: Registration of text/directory MIME type VERSION
Type name: VERSION Type name: VERSION
Type purpose: To specify the version of the vCard specification used Type purpose: To specify the version of the vCard specification used
to format this vCard. to format this vCard.
Type encoding: 8bit Type encoding: 8bit
Type value: A single text value. Type value: A single text value.
Type special notes: The value MUST be "3.0" if the vCard version Type special notes: The property MUST be present in the vCard object.
corresponds to this specification. The value MUST be "3.0" if the vCard corresponds to this
specification.
Type example: Type example:
VERSION: 3.0 VERSION: 3.0
4.7 Security Types 3.7 Security Types
These types are concerned with the security of communication pathways These types are concerned with the security of communication pathways
or access to the vCard. or access to the vCard.
4.7.1 CLASS Type Definition 3.7.1 CLASS Type Definition
To: ietf-mime-directory@imc.org To: ietf-mime-directory@imc.org
Dawson & Howes [Page 20] May 1998 Subject: Registration of text/directory MIME type CLASS
vCard MIME Directory Profile
Subject: Registration of application/directory MIME type CLASS
Type name: CLASS Type name: CLASS
Type purpose: To specify the access classification for a vCard Type purpose: To specify the access classification for a vCard
object. object.
Type encoding: 8bit Type encoding: 8bit
Type value: A single text value. Type value: A single text value.
Type special notes: An access classification is only one component of Type special notes: An access classification is only one component of
the general security model for a directory service. The the general security model for a directory service. The
vCard MIME Directory Profile
classification attribute provides a method of capturing the intent of classification attribute provides a method of capturing the intent of
the owner for general access to information described by the vCard the owner for general access to information described by the vCard
object. object.
Type examples: Type examples:
CLASS:PUBLIC CLASS:PUBLIC
CLASS:PRIVATE CLASS:PRIVATE
CLASS:CONFIDENTIAL CLASS:CONFIDENTIAL
4.7.2 KEY Type Definition 3.7.2 KEY Type Definition
To: ietf-mime-directory@imc.org To: ietf-mime-directory@imc.org
Subject: Registration of application/directory MIME type KEY Subject: Registration of text/directory MIME type KEY
Type name: KEY Type name: KEY
Type purpose: To specify a public key or authentication certificate Type purpose: To specify a public key or authentication certificate
associated with the object that the vCard represents. associated with the object that the vCard represents.
Type encoding: The encoding MUST be reset to "b" using the ENCODING Type encoding: The encoding MUST be reset to "b" using the ENCODING
parameter in order to specify inline, encoded binary data. If the parameter in order to specify inline, encoded binary data. If the
value is a text value, then the default encoding of 8bit is used and value is a text value, then the default encoding of 8bit is used and
no explicit ENCODING parameter is needed. no explicit ENCODING parameter is needed.
skipping to change at line 1223 skipping to change at page 24, line 47
Type special notes: The type may also include the type parameter TYPE Type special notes: The type may also include the type parameter TYPE
to specify the public key or authentication certificate format. The to specify the public key or authentication certificate format. The
parameter type may specify any IANA registered public key or parameter type may specify any IANA registered public key or
authentication certificate format. The parameter type may also authentication certificate format. The parameter type may also
specify a non-standard format. specify a non-standard format.
Type example: Type example:
KEY;ENCODING=b: MIICajCCAdOgAwIBAgICBEUwDQYJKoZIhvcNAQEEBQA KEY;ENCODING=b: MIICajCCAdOgAwIBAgICBEUwDQYJKoZIhvcNAQEEBQA
wdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05ldHNjYXBlIENbW11bmljYX wdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05ldHNjYXBlIENbW11bmljYX
Dawson & Howes [Page 21] May 1998
vCard MIME Directory Profile
Rpb25zIENvcnBvcmF0aW9uMRwwGgYDVQQLExNJbmZvcm1hdGlvbiBTeXN0 Rpb25zIENvcnBvcmF0aW9uMRwwGgYDVQQLExNJbmZvcm1hdGlvbiBTeXN0
ZW1zMRwwGgYDVQQDExNyb290Y2EubmV0c2NhcGUuY29tMB4XDTk3MDYwNj ZW1zMRwwGgYDVQQDExNyb290Y2EubmV0c2NhcGUuY29tMB4XDTk3MDYwNj
E5NDc1OVoXDTk3MTIwMzE5NDc1OVowgYkxCzAJBgNVBAYTAlVTMSYwJAYD E5NDc1OVoXDTk3MTIwMzE5NDc1OVowgYkxCzAJBgNVBAYTAlVTMSYwJAYD
VQQKEx1OZXRzY2FwZSBDb21tdW5pY2F0aW9ucyBDb3JwLjEYMBYGA1UEAx VQQKEx1OZXRzY2FwZSBDb21tdW5pY2F0aW9ucyBDb3JwLjEYMBYGA1UEAx
MPVGltb3RoeSBBIEhvd2VzMSEwHwYJKoZIhvcNAQkBFhJob3dlc0BuZXRz MPVGltb3RoeSBBIEhvd2VzMSEwHwYJKoZIhvcNAQkBFhJob3dlc0BuZXRz
Y2FwZS5jb20xFTATBgoJkiaJk/IsZAEBEwVob3dlczBcMA0GCSqGSIb3DQ Y2FwZS5jb20xFTATBgoJkiaJk/IsZAEBEwVob3dlczBcMA0GCSqGSIb3DQ
EBAQUAA0sAMEgCQQC0JZf6wkg8pLMXHHCUvMfL5H6zjSk4vTTXZpYyrdN2 EBAQUAA0sAMEgCQQC0JZf6wkg8pLMXHHCUvMfL5H6zjSk4vTTXZpYyrdN2
dXcoX49LKiOmgeJSzoiFKHtLOIboyludF90CgqcxtwKnAgMBAAGjNjA0MB dXcoX49LKiOmgeJSzoiFKHtLOIboyludF90CgqcxtwKnAgMBAAGjNjA0MB
EGCWCGSAGG+EIBAQQEAwIAoDAfBgNVHSMEGDAWgBT84FToB/GV3jr3mcau EGCWCGSAGG+EIBAQQEAwIAoDAfBgNVHSMEGDAWgBT84FToB/GV3jr3mcau
+hUMbsQukjANBgkqhkiG9w0BAQQFAAOBgQBexv7o7mi3PLXadkmNP9LcIP +hUMbsQukjANBgkqhkiG9w0BAQQFAAOBgQBexv7o7mi3PLXadkmNP9LcIP
mx93HGp0Kgyx1jIVMyNgsemeAwBM+MSlhMfcpbTrONwNjZYW8vJDSoi//y mx93HGp0Kgyx1jIVMyNgsemeAwBM+MSlhMfcpbTrONwNjZYW8vJDSoi//y
vCard MIME Directory Profile
rZlVt9bJbs7MNYZVsyF1unsqaln4/vy6Uawfg8VUMk1U7jt8LYpo4YULU7 rZlVt9bJbs7MNYZVsyF1unsqaln4/vy6Uawfg8VUMk1U7jt8LYpo4YULU7
UZHPYVUaSgVttImOHZIKi4hlPXBOhcUQ== UZHPYVUaSgVttImOHZIKi4hlPXBOhcUQ==
4.8 Extended Types 3.8 Extended Types
The types defined by this document can be extended with private types The types defined by this document can be extended with private types
using the non-standard, private values mechanism defined in [RFC- using the non-standard, private values mechanism defined in [RFC
2045]. Non-standard, private types with a name starting with "X-" may 2045]. Non-standard, private types with a name starting with "X-" may
be defined bilaterally between two cooperating agents without outside be defined bilaterally between two cooperating agents without outside
registration or standardization. registration or standardization.
5. Differences With vCard v2.1 4. Formal Grammar
This specification has been reviewed by the IETF community. The The following formal grammar is provided to assist developers in
review process introduced a number of differences with the [VCARD] building parsers for the vCard.
version 2.1. These differences are minor, but require that vCard
objects conforming to this specification have a different version
number than a vCard conforming to [VCARD]. The differences include
the following:
. The QUOTED-PRINTABLE inline encoding has been eliminated. This syntax is written according to the form described in RFC 2234,
Only the "B" encoding of [RFC 2047] is an allowed value for but it references just this small subset of RFC 2234 literals:
the ENCODING parameter.
. The method for specifying CRLF character sequences in type ;*******************************************
values has been changed. The CRLF character sequence in a ; Commonly Used Literal Definition
type value is specified with the backslash character sequence ;*******************************************
"\n" or "\N".
. Any COMMA or SEMICOLON in a type value must be backslash ALPHA = %x41-5A / %x61-7A
escaped. ; Latin Capital Letter A-Latin Capital Letter Z /
; Latin Small Letter a-Latin Small Letter z
. VERSION value corresponding to this specification must be CHAR = %x01-7F
"3.0". ; Any C0 Controls and Basic Latin, excluding NULL from
; Code Charts, pages 7-6 through 7-9 in [UNICODE]
. The [MIME-DIR] predefined types of SOURCE, NAME and PROFILE CR = %x0D
are allowed. ; Carriage Return
. The [MIME-DIR] VALUE type parameter for value data typing is LF = %0A
allowed. In addition, there are extensions made to these type ; Line Feed
values for additional value types used in this specification.
Dawson & Howes [Page 22] May 1998 CRLF = CR LF
; Internet standard newline
vCard MIME Directory Profile ;CTL = %x00-1F / %x7F
; Controls. Not used, but referenced in comments.
. The [VCARD] CHARSET type parameter has been eliminated. DIGIT = %x30-39
Character set may only be specified on the CHARSET parameter ; Digit Zero-Digit Nine
on the Content-Type MIME header field.
. The [VCARD] support for non-signficant LWSP character, other DQUOTE = %x22
than after the COMMA character list separator, SEMICOLON ; Quotation Mark
character value component separator and the COLON value
separator has been eliminated.
. LOGO, PHOTO and SOUND multimedia formats need to be either HTAB = %x09
IANA registered types or non-standard types. ; Horizontal Tabulation
vCard MIME Directory Profile
. Inline binary content must be "B" encoded and folded. A blank SP = %x20
line after the encoded binary content is nolonger required. ; space
. TEL values may be identified as personal communication VCHAR = %x21-7E
services telephone numbers with the PCS type parameter value. ; Visible (printing) characters
. The CATEGORIES, CLASS, NICKNAME, PRODID and SORT-STRING types WSP = SP / HTAB
have been added. ; White Space
6. Formal Grammar ;*******************************************
; Basic vCard Definition
;*******************************************
The following formal grammar is provided to assist developers in vcard_entity = 1*(vcard)
building parsers for the vCard.
This syntax is written according to the form described in RFC 822, vcard = [group "."] "BEGIN" ":" *WSP "VCARD" 1*CRLF
but it references just this small subset of RFC 822 literals: 1*(contentline)
;A vCard object MUST include the VERSION, FN and N types.
[group "."] "END" ":" *WSP "VCARD" 1*CRLF
CR = <ASCII CR, carriage return> ; (15, 13.) contentline = [group "."] name *(";" *WSP param ) ":" value CRLF
LF = <ASCII LF, linefeed> ; (12,10.) ; When parsing a content line, folded lines must first
CRLF = CR LF ; be unfolded according to the unfolding procedure
SPACE = <ASCII SP, space> ; (40,32.) ; described above. When generating a content line, lines
HTAB =<ASCII HT, horizontal-tab> ; (11,9.) ; longer than 75 characters SHOULD be folded according to
WS = (SPACE / HTAB) ; the folding procedure described above.
All literal property names are valid as upper, lower, or mixed case. group = 1*(ALPHA / DIGIT / "-")
char = <any printable character from the current name = iana-token / x-name
character set > ; Parsing of the param and value is
; based on the "name" or type identifier
; as defined in ABNF sections below
word = 1*char iana-token = 1*(ALPHA / DIGIT / "-")
; vCard type or parameter identifier registered with IANA
group = word "." x-name = "X-" 1*(ALPHA / DIGIT / "-")
; Reserved for non-standard use
vcard_entity = 1*(vcard) param = [param-name "="] param-value *("," *WSP param-value)
vcard = [group] "BEGIN" ":" [WS] "VCARD" 1*CRLF param-name = iana-token / x-name
1*([group] item *CRLF
[group] "END" ":" [WS] "VCARD" 1*CRLF
;All lines may be "folded".
item = "NAME" *txtparam ":" [WS] text CRLF param-value = text / quoted-string
/ "PROFILE" *txtparam ":" [WS] "VCARD" CRLF
Dawson & Howes [Page 23] May 1998 text = *SAFE-CHAR
value = *VALUE-CHAR
quoted-string = DQUOTE *qtext DQUOTE
qtext = QSAFE-CHAR / QUOTED-CHAR
vCard MIME Directory Profile vCard MIME Directory Profile
/ "SOURCE" *srcparam ":" [WS] uri CRLF NON-ASCII = %x80-FF
/ "FN" *txtparam ":" [WS] text CRLF ; Use is restricted by CHARSET parameter
/ "N" *(txtparam) ":" [WS] nameparts CRLF ; on outer MIME object (UTF-8 preferred)
/ "NICKNAME" *(txtparam) ":" [WS] text *("," [WS] text)
CRLF
/ "PHOTO" (imginline / imgrefer)
/ "BDAY" (dateval / datetimeval)
/ "ADR" adrparam ":" [WS] adrparts CRLF
/ "LABEL" *(adrparam) ":" [WS] text CRLF
/ "TEL" *(telparam) ":" [WS] phone-number CRLF
/ "EMAIL" *(emailparam) ":" [WS] text CRLF
/ "MAILER" *txtparam ":" [WS] text CRLF
/ "TZ" [";" [WS] "VALUE" "=" "utc-offset"] ":"
[WS] utc-offset
/ "GEO" [";" [WS] "VALUE" "=" "float"] ":"
float ";" float
/ "TITLE" *txtparam ":" [WS] text CRLF
/ "ROLE" *txtparam ":" [WS] text CRLF
/ "LOGO" (imginline / imgrefer)
/ "AGENT" ":" text CRLF
;The text value MUST be a string of vCard types, each
;type terminated with a "\n" or "\N" escapement.
/ "ORG" *txtparam ":" [WS] orgparts CRLF
/ "CATEGORIES" *txtparam ":" [WS] text *("," [WS] text)
CRLF
/ "NOTE" *txtparam ":" [WS] text CRLF
/ "PRODID *txtparam ":" [WS] text CRLF
/ "REV" (dateval / datetimeval)
/ "SOUND" (sndinline / sndrefer)
/ "URL" [";" [WS] "VALUE" "=" "uri"] ":" [WS] uri CRLF
/ "UID" [";" [WS] "VALUE" "=" "text"] ":" [WS] text CRLF
/ "VERSION" ":" "3.0"
/ "CLASS" *txtparam ":" [WS] text CRLF
/ "KEY" (keytext) / (keybinary)
/ "X-" word *txtparam ":" [WS] value
txtparam = (";" [WS] "VALUE" "=" "text") QSAFE-CHAR = WSP / %x21 / %x23-5B / %x5D-7E / NON-ASCII
/ (";" [WS] "LANGUAGE" "=" langval) ; Any character except CTLs, DQUOTE, or "\"
/ (";" [WS] "X-" word "=" word)
langval = <a language string as defined in RFC 1766> QUOTED-CHAR = "\" ("\" / DQUOTE)
; \\ encodes \ and \" encodes "
srcparam = (";" [WS] "VALUE" "=" "uri") SAFE-CHAR = WSP / %x21 / %x23-2B / %x2D-39 / %x3C-7E / NON-ASCII
/ (";" [WS] "CONTEXT" "=" word) ; Any character except CTLs, DQUOTE, ";", ":", ","
VALUE-CHAR = WSP / VCHAR / NON-ASCII
; Any textual character
;*******************************************
; vCard Type Definition
;
; Provides type-specific definitions for how the
; "value" and "param" are defined.
;*******************************************
;For name="NAME"
param = ""
;No parameters allowed
value = text-value
;For name="PROFILE"
param = ""
;No parameters allowed
value = "VCARD"
;For name="SOURCE"
param = source-param
;No parameters allowed
value = uri
source-param = ( "VALUE" "=" "uri")
/ ( "CONTEXT" "=" word)
;Parameter values specifies the protocol ;Parameter values specifies the protocol
; context for the URI value. ; context for the URI value.
/ (";" [WS] "X-" word "=" word) / (x-name "=" *SAFE-CHAR
adrparam = ";" [WS] ["TYPE" "="] adrtype *("," [WS] adrtype) ;For name="FN"
*(txtparam) ;This type MUST be included in a vCard object.
param = text-param
;Text parameters allowed
adrtype = "dom" / "intl" / "postal" / "parcel" / "home" value = text-value
/ "work" / "pref" / ianatype / "X-" word vCard MIME Directory Profile
Dawson & Howes [Page 24] May 1998 ;For name="N"
;This type MUST be included in a vCard object.
param = text-param
;Text parameters allowed
value = n-value
n-value = 0*4(text-value *("," text-value) ";")
text-value *("," text-value)
; Family, Given, Middle, Prefix, Suffix.
; Example:Public;John;Quincy,Adams;Reverend Dr.;III,
; Esq.
;For name="NICKNAME"
param = text-param
;Text parameters allowed
value = text-list
;For name="PHOTO"
param = img-inline-param
;Only image parameters allowed
param =/ img-refer-param
;Only image parameters allowed
value = img-inline-value
;Value and parameter MUST match
value =/ img-refer-value
;Value and parameter MUST match
;For name="BDAY"
param = ("VALUE" "=" "DATE")
;Only value parameter allowed
param =/ ("VALUE" "=" "DATE-TIME")
;Only value parameter allowed
value = date-value
;Value MUST match value type
value =/ date-time-value
;Value MUST match value type
;For name="ADR"
param = adr-param / text-param
;Only adr and text parameters allowed
value = adr-value
;For name="LABEL"
param = adr-param / text-param
;Only adr and text parameters allowed
vCard MIME Directory Profile vCard MIME Directory Profile
adrparts = 0*6(text ";") text value = text-value
; PO Box, Extended Address, Street, Locality, Region, Postal
; Code, Country Name
orgparts = *(text ";") text ;For name="TEL"
; First is Organization Name, remainder are Organization Units. param = tel-param
;Only tel parameters allowed
nameparts = 0*4(text *("," text) ";") text *("," text) value = phone-number-value
; Family, Given, Middle, Prefix, Suffix.
; Example:Public;John;Q.;Reverend Dr.;III, Esq.
telparam = ";" [WS] ["TYPE" "="] teltype *("," [WS] teltype) tel-param = ["TYPE" "="] tel-type *("," *WSP tel-type)
teltype = "HOME" / "WORK" / "PREF" / "VOICE" / "FAX" / "MSG" tel-type = "HOME" / "WORK" / "PREF" / "VOICE" / "FAX" / "MSG"
/ "CELL" / "PAGER" / "BBS" / "MODEM" / "CAR" / "ISDN" / "CELL" / "PAGER" / "BBS" / "MODEM" / "CAR" / "ISDN"
/ "VIDEO" / "PCS" / ianatype / "X-" word / "VIDEO" / "PCS" / iana-token / x-name
emailparam = ";" [WS] ["TYPE" "="] emailtype ["," [WS] "PREF"] ;For name="EMAIL"
param = email-param
;Only email parameters allowed
emailtype = "INTERNET" / "X400" / ianatype / "X-" word value = text-value
imginline = imginlparm ":" [WS] binary CRLF email-param = ["TYPE" "="] email-type ["," *WSP "PREF"]
;Value MUST be "b" encoded image content
imginlparm = [";" [WS] "VALUE" "=" "binary"] email-type = "INTERNET" / "X400" / iana-token / "X-" word
";" [WS] "ENCODING" "=" "b"
";" [WS] "TYPE" "=" word
;Value MUST be an IANA registered image type
imgrefer = imgrefparm ":" [WS] uri ;For name="MAILER"
param = text-param
;Only text parameters allowed
value = text-value
;For name="TZ"
param = ""
;No parameters allowed
value = utc-offset-value
;For name="GEO"
param = ""
;No parameters allowed
value = float-value ";" float-value
;For name="TITLE"
param = text-param
;Only text parameters allowed
value = text-value
;For name="ROLE"
param = text-param
;Only text parameters allowed
value = text-value
vCard MIME Directory Profile
;For name="LOGO"
param = img-inline-param / img-refer-param
;Only image parameters allowed
value = img-inline-value / img-refer-value
;Value and parameter MUST match
;For name="AGENT"
param = agent-inline-param
param =/ agent-refer-param
value = agent-inline-value
value =/ agent-refer-value
agent-inline-param = ""
;No parameters allowed
agent-refer-param = "VALUE" "=" "uri"
;Only value parameter allowed
agent-inline-value = text-value
;Value MUST be a valid vCard object
agent-refer-value = uri
;URI MUST refer to image content of given type ;URI MUST refer to image content of given type
imgrefparm = ";" [WS] "VALUE" "=" "uri" ;For name="ORG"
";" [WS] "TYPE" "=" word
;Value MUST be an IANA registered image type
sndinline = sndinlparm ":" [WS] binary CRLF param = text-param
;Only text parameters allowed
value = org-value
org-value = *(text-value ";") text-value
; First is Organization Name, remainder are Organization Units.
;For name="CATEGORIES"
param = text-param
;Only text parameters allowed
value = text-list
;For name="NOTE"
param = text-param
;Only text parameters allowed
value = text-value
;For name="PRODID"
param = ""
;No parameters allowed
vCard MIME Directory Profile
value = text-value
;For name="REV"
param = ["VALUE" =" "DATE-TIME"]
;Only value parameters allowed
param =/ "VALUE" =" "DATE"
;Only value parameters allowed
value = date-time-value
value =/ date-value
;For name="SORT-STRING"
param = text-param
;Only text parameters allowed
value = text
;For name="SOUND"
param = snd-inline-param
;Only sound parameters allowed
param =/ snd-refer-param
;Only sound parameters allowed
value = snd-line-value
;Value MUST match value type
value =/ snd-refer-value
;Value MUST match value type
snd-inline-value = binary CRLF
;Value MUST be "b" encoded audio content ;Value MUST be "b" encoded audio content
sndinlparm = [";" [WS] "VALUE" "=" "binary"] snd-inline-param = ("VALUE" "=" "binary"])
";" [WS] "ENCODING" "=" "b" / ("ENCODING" "=" "b")
";" [WS] "TYPE" "=" word / ("TYPE" "=" *SAFE-CHAR)
;Value MUST be an IANA registered audio type ;Value MUST be an IANA registered audio type
sndrefer = sndrefparm ":" [WS] uri snd-refer-value = uri
;URI MUST refer to audio content of given type ;URI MUST refer to audio content of given type
sndrefparm = ";" [WS] "VALUE" "=" "uri" snd-refer-param = ("VALUE" "=" "uri")
";" [WS] "TYPE" "=" word / ("TYPE" "=" word)
;Value MUST be an IANA registered audio type ;Value MUST be an IANA registered audio type
dateval = [";" [WS] "VALUE" "=" "date"] ":" [WS] date ;For name="UID"
param = ""
;No parameters allowed
datetimeval = ";" [WS] "VALUE" "=" "date-time" ";" [ws] date-time value = text-value
vCard MIME Directory Profile
Dawson & Howes [Page 25] May 1998 ;For name="URL"
param = ""
;No parameters allowed
vCard MIME Directory Profile value = uri
/ "KEY" (keytext) / (keybinary) ;For name="VERSION"
;This type MUST be included in a vCard object.
param = ""
;No parameters allowed
keytext = [";" [WS] "TYPE" "=" keytype] [";" [WS] "TYPE" "=" value = "3.0"
"text"] ":" text
keybinary = [";" [WS] "TYPE" "=" keytype] (";" [WS] "TYPE" "=" ;For name="CLASS"
"binary") (";" [WS] "ENCODING" "=" "b") ":" [WS] param = ""
binary ;No parameters allowed
value = "PUBLIC" / "PRIVATE" / "CONFIDENTIAL"
/ iana-token / x-name
;For name="KEY"
param = key-txt-param
;Only value and type parameters allowed
param =/ key-bin-param
;Only value and type parameters allowed
value = text-value
value =/ binary
key-txt-param = "TYPE" "=" keytype
key-bin-param = ("TYPE" "=" keytype)
/ ("ENCODING" "=" "b)
;Value MUST be a "b" encoded key or certificate ;Value MUST be a "b" encoded key or certificate
keytype = "X509" / "PGP" / ianatype / "X-" word keytype = "X509" / "PGP" / iana-token / x-name
value = binary / boolean / date / date-time / float / integer ;For name="X-" non-standard type
/ phone-number / text / time / utc-offset / vcard / param = text-param / (x-name "=" *SAFE-CHAR)
/ ianavalue ;Only text or non-standard parameters allowed
text = *(word WS) value = text-list
; To include a SEMICOLON in this string it must be escaped
; with a "\" character. To include a COMMA in this string it
; MUST be escaped with a "\" characer.
binary = <A text string as defined in [RFC 2047]> ;*******************************************
; vCard Commonly Used Parameter Definition
;*******************************************
date = <A single value as defined in [MIME-DIR]> text-param = ("VALUE" "=" "text")
/ ("LANGUAGE" "=" langval)
/ (x-name "=" *SAFE-CHAR)
time = <A single value as defined in [MIME-DIR]> langval = <a language string as defined in RFC 1766>
vCard MIME Directory Profile
date-time = <A single value as defined in [MIME-DIR] img-inline-value = binary
;Value MUST be "b" encoded image content
float = <A single value as defined in [MIME-DIR]> img-inline-param = ("VALUE" "=" "binary")
/ ("ENCODING" "=" "b")
/ ("TYPE" "=" *SAFE-CHAR
;TYPE value MUST be an IANA registered image type
phone-number = <A text value as defined in [CCITT E.163] and img-refer-value = uri
[CCITT X.121]> ;URI MUST refer to image content of given type
uri = <A single value as defined in RFC 1738> img-refer-param = ("VALUE" "=" "uri")
/ ("TYPE" "=" *SAFE-CHAR)
;TYPE value MUST be an IANA registered image type
utc-offset = ("+" / "-") time-hour ":" time-minute adr-param = (["TYPE" "="] adr-type *("," *WSP adr-type))
/ (text-param)
adr-type = "dom" / "intl" / "postal" / "parcel" / "home"
/ "work" / "pref" / iana-type / x-name
adr-value = 0*6(text-value ";") text-value
; PO Box, Extended Address, Street, Locality, Region, Postal
; Code, Country Name
;*******************************************
; vCard Type Value Definition
;*******************************************
text-list = <A text list value as defined in [MIME-DIR]>
text-value = <A single text value as defined in [MIME-DIR]>
binary-value = <A "b" encoded text value as defined in [RFC 2047]>
date-value = <A single date value as defined in [MIME-DIR]>
time-value = <A single time value as defined in [MIME-DIR]>
date-time-value = <A single date-time value as defined in [MIME-DIR]
float-value = <A single float value as defined in [MIME-DIR]>
phone-number-value = <A single text value as defined in [CCITT
E.163] and [CCITT X.121]>
uri-value = <A text value as defined in RFC 1738>
utc-offset-value = ("+" / "-") time-hour ":" time-minute
time-hour = 2DIGIT ;00-23 time-hour = 2DIGIT ;00-23
time-minute = 2DIGIT ;00-59 time-minute = 2DIGIT ;00-59
vCard MIME Directory Profile
ianatype = <Any IANA registered value> 5. Differences With vCard v2.1
ianavalue = <ANY IANA registered value type format> This specification has been reviewed by the IETF community. The
review process introduced a number of differences with the [VCARD]
version 2.1. These differences are minor, but require that vCard
objects conforming to this specification have a different version
number than a vCard conforming to [VCARD]. The differences include
the following:
6.1 Acknowledgements The QUOTED-PRINTABLE inline encoding has been eliminated.
Only the "B" encoding of [RFC 2047] is an allowed value for
the ENCODING parameter.
The authors would like to thank the participants in the IETF ASID The method for specifying CRLF character sequences in text
working group, in addition to the following individuals, Roland type values has been changed. The CRLF character sequence in
Alden, Stephen Bartlett, Alec Dun, Daniel Gurney, Bruce Johnston, a text type value is specified with the backslash character
Daniel Klaussen, Chris Newman, Vinod Seraphin, Michelle Watkins; who sequence "\n" or "\N".
provided numerous suggestions and comments on this work.
Dawson & Howes [Page 26] May 1998 Any COMMA or SEMICOLON in a text type value must be backslash
escaped.
VERSION value corresponding to this specification MUST be
"3.0".
The [MIME-DIR] predefined types of SOURCE, NAME and PROFILE
are allowed.
The [MIME-DIR] VALUE type parameter for value data typing is
allowed. In addition, there are extensions made to these type
values for additional value types used in this specification.
The [VCARD] CHARSET type parameter has been eliminated.
Character set may only be specified on the CHARSET parameter
on the Content-Type MIME header field.
The [VCARD] support for non-significant WSP character, other
than after the COMMA character list separator, SEMICOLON
character value component separator and the COLON value
separator has been eliminated.
LOGO, PHOTO and SOUND multimedia formats MUST be either IANA
registered types or non-standard types.
Inline binary content must be "B" encoded and folded. A blank
line after the encoded binary content is no longer required.
TEL values may be identified as personal communication
services telephone numbers with the PCS type parameter value.
The CATEGORIES, CLASS, NICKNAME, PRODID and SORT-STRING types
have been added.
vCard MIME Directory Profile vCard MIME Directory Profile
6.2 Authors's Addresses The VERSION, N and FN types MUST be specified in a vCard.
This identifies the version of the specification that the
object was formatted to. It also assures that every vCard
will include both a structured and formatted name that can be
used to identify the object.
6. Acknowledgements
The many valuable comments contributed by members of the IETF ASID
working group are gratefully acknowledged, as are the contributions
by Roland Alden, Stephen Bartlett, Alec Dun, Daniel Gurney, Bruce
Johnston, Daniel Klaussen, Vinod Seraphin, Michelle Watkins. Chris
Newman was especially helpful in navigating the intricacies of ABNF
lore.
7. Authors?s Addresses
BEGIN:vCard BEGIN:vCard
VERSION:3.0
FN:Frank Dawson FN:Frank Dawson
ORG:Lotus Development Corporation ORG:Lotus Development Corporation
ADR;TYPE=WORK,POSTAL,PARCEL:;;6544 Battleford Drive ADR;TYPE=WORK,POSTAL,PARCEL:;;6544 Battleford Drive
;Raleigh;NC;27613-3502;U.S.A. ;Raleigh;NC;27613-3502;U.S.A.
TEL;TYPE=VOICE,MSG,WORK: +1-919-676-9515 TEL;TYPE=VOICE,MSG,WORK: +1-919-676-9515
TEL;TYPE=FAX,WORK: +1-919-676-9564 TEL;TYPE=FAX,WORK: +1-919-676-9564
EMAIL;TYPE=INTERNET,PREF:Frank_Dawson@Lotus.com EMAIL;TYPE=INTERNET,PREF:Frank_Dawson@Lotus.com
EMAIL;TYPE=INTERNET:fdawson@earthlink.net EMAIL;TYPE=INTERNET:fdawson@earthlink.net
URL:http://home.earthlink.net/~fdawson URL:http://home.earthlink.net/~fdawson
END:vCard END:vCard
BEGIN:vCard BEGIN:vCard
VERSION:3.0
FN:Tim Howes FN:Tim Howes
ORG:Netscape Communications Corp. ORG:Netscape Communications Corp.
ADR;TYPE=WORK:;;501 E. Middlefield Rd.;Mountain View; ADR;TYPE=WORK:;;501 E. Middlefield Rd.;Mountain View;
CA; 94043;U.S.A. CA; 94043;U.S.A.
TEL;TYPE=VOICE,MSG,WORK:+1-415-937-3419 TEL;TYPE=VOICE,MSG,WORK:+1-415-937-3419
TEL;TYPE=FAX,WORK:+1-415-528-4164 TEL;TYPE=FAX,WORK:+1-415-528-4164
EMAIL;TYPE=INTERNET:howes@netscape.com EMAIL;TYPE=INTERNET:howes@netscape.com
END:vCard END:vCard
6.3 References 8. References
The following documents are referenced by this work. The following documents are referenced by this work.
[ISO 8601] ISO 8601:1988 - Data elements and interchange formats - [ISO 8601] ISO 8601:1988 - Data elements and interchange formats -
Information interchange - Representation of dates and times - The Information interchange - Representation of dates and times - The
International Organization for Standardization, June, 1988. International Organization for Standardization, June, 1988.
[ISO 8601 TC] ISO 8601, Technical Corrigendum 1 - Data elements and [ISO 8601 TC] ISO 8601, Technical Corrigendum 1 - Data elements and
interchange formats - Information interchange - Representation of interchange formats - Information interchange - Representation of
dates and times - The International Organization for Standardization, dates and times - The International Organization for Standardization,
May, 1991. May, 1991.
vCard MIME Directory Profile
[ISO 9070] ISO 9070, Information Processing - SGML support facilities [ISO 9070] ISO 9070, Information Processing - SGML support facilities
- Registration Procedures for Public Text Owner Identifiers, April, - Registration Procedures for Public Text Owner Identifiers, April,
1991. 1991.
[CCITT E.163] Recommendation E.163 - Numbering Plan for The [CCITT E.163] Recommendation E.163 - Numbering Plan for The
International Telephone Service, CCITT Blue Book, Fascicle II.2, pp. International Telephone Service, CCITT Blue Book, Fascicle II.2, pp.
128-134, November, 1988. 128-134, November, 1988.
[CCITT X.121] Recommendation X.121 - International Numbering Plan for [CCITT X.121] Recommendation X.121 - International Numbering Plan for
Public Data Networks, CCITT Blue Book, Fascicle VIII.3, pp. 317-332, Public Data Networks, CCITT Blue Book, Fascicle VIII.3, pp. 317-332,
November, 1988. November, 1988.
[CCITT X.520] Recommendation X.520 - The Directory - Selected [CCITT X.520] Recommendation X.520 - The Directory - Selected
Attribute Types, November 1988. Attribute Types, November 1988.
[CCITT X.521] Recommendation X.521 - The Directory - Selected Object [CCITT X.521] Recommendation X.521 - The Directory - Selected Object
Classes, November 1988. Classes, November 1988.
Dawson & Howes [Page 27] May 1998 [MIME-DIR] Howes, T., Smith, M., Dawson, F. "A MIME Content-Type for
Directory Information", RFC xxxx, March 1998.
vCard MIME Directory Profile
[MIME-DIR] Howes, T., Smith, M., "A MIME Content-Type for Directory
Information", Internet-draft-ietf-asid-mime-direct-05.txt, November,
1997.
[RFC-822] Crocker, D., "Standard for the Format of ARPA Internet Text
Messages", STD 11, RFC 822, August 1982.
[RFC-1738] Berners-Lee, T., Masinter, L., McCahill, M., "Uniform [RFC 1738] Berners-Lee, T., Masinter, L., McCahill, M., "Uniform
Resource Locators (URL)", RFC 1738, December 1994. Resource Locators (URL)", RFC 1738, December 1994.
[RFC-1766] Alvestrand, H., "Tags for the Identification of [RFC 1766] Alvestrand, H., "Tags for the Identification of
Languages", March 1995. Languages", March 1995.
[RFC-1872] Levinson, E., "The MIME Multipart/Related Content-type," [RFC 1872] Levinson, E., "The MIME Multipart/Related Content-type,"
RFC 1872, December 1995. RFC 1872, December 1995.
[RFC-2045] Freed, N., Borenstein, N., " Multipurpose Internet Mail [RFC 2045] Freed, N., Borenstein, N., " Multipurpose Internet Mail
Extensions (MIME) - Part One: Format of Internet Message Bodies", RFC Extensions (MIME) - Part One: Format of Internet Message Bodies", RFC
2045, November 1996. 2045, November 1996.
[RFC-2046] Freed, N., Borenstein, N., " Multipurpose Internet Mail [RFC 2046] Freed, N., Borenstein, N., " Multipurpose Internet Mail
Extensions (MIME) - Part Two: Media Types", RFC 2046, November 1996. Extensions (MIME) - Part Two: Media Types", RFC 2046, November 1996.
[RFC-2047] Moore, K., "Multipurpose Internet Mail Extensions (MIME) - [RFC 2047] Moore, K., "Multipurpose Internet Mail Extensions (MIME) -
Part Three: Message Header Extensions for Non-ASCII Text", RFC 2047, Part Three: Message Header Extensions for Non-ASCII Text", RFC 2047,
November 1996. November 1996.
[RFC-2048] Freed, N., J. Klensin, J. Postel, "Multipurpose Internet [RFC 2048] Freed, N., J. Klensin, J. Postel, "Multipurpose Internet
Mail Extensions (MIME) - Part Four: Registration Procedures", RFC Mail Extensions (MIME) - Part Four: Registration Procedures", RFC
2048, January 1997. 2048, January 1997.
[RFC2119] "Key words for use in RFCs to Indicate Requirement Levels", [RFC 2119] "Key words for use in RFCs to Indicate Requirement
RFC 2119, March 1997. Levels", RFC 2119, March 1997.
[VCARD] VERSIT Consortium, "vCard - The Electronic Business Card [RFC 2234] Crocker, D., Overell, P., "Augmented BNF for Syntax
Version 2.1", http://www.versit.com/pdi/vcard-21.txt, September 18, Specifications: ABNF", RFC 2234, November 1997.
[UNICODE] "The Unicode Standard - Version 2.0", The Unicode
Consortium, July 1996.
vCard MIME Directory Profile
[VCARD] Internet Mail Consortium, "vCard - The Electronic Business
Card Version 2.1", http://www.imc.org/pdi/vcard-21.txt, September 18,
1996. 1996.
7. Full Copyright Statement 9. Full Copyright Statement
"Copyright (C) The Internet Society (date). All Rights Reserved. "Copyright (C) The Internet Society (date). All Rights Reserved.
This document and translations of it MAY be copied and furnished to This document and translations of it MAY be copied and furnished to
others, and derivative works that comment on or otherwise explain it others, and derivative works that comment on or otherwise explain it
or assist in its implmentation MAY be prepared, copied, published and or assist in its implementation MAY be prepared, copied, published
distributed, in whole or in part, without restriction of any kind, and distributed, in whole or in part, without restriction of any
provided that the above copyright notice and this paragraph are kind, provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this included on all such copies and derivative works. However, this
document itself MAY not be modified in any way, such as by removing document itself MAY not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for developing Internet standards in which case the procedures for
copyrights defined in the Internet Standards process MUST be copyrights defined in the Internet Standards process MUST be
Dawson & Howes [Page 28] May 1998
vCard MIME Directory Profile
followed, or as required to translate it into languages other than followed, or as required to translate it into languages other than
English. English.
The limited permissions granted above are perpetual and will not be The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assigns. revoked by the Internet Society or its successors or assigns.
This document and the information contained herein is provided on an This document and the information contained herein is provided on an
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
__
Dawson & Howes [Page 29] May 1998
 End of changes. 232 change blocks. 
408 lines changed or deleted 714 lines changed or added

This html diff was produced by rfcdiff 1.33. The latest version is available from http://tools.ietf.org/tools/rfcdiff/