WDIFF

draft-ietf-asid-mime-vcard-01.txt --> draft-ietf-asid-mime-vcard-02.txt

Network Working Group Frank Dawson
INTERNET DRAFT Tim Howes
draft-ietf-asid-mime-vcard-01.txt IBM/Netscape
ietf-asid-mime-vcard-02.txt Lotus/Netscape Communications
November
March 26, 1996

An Application/Directory 1997

vCard MIME Content-Type
Electronic Business Card Directory Profile

Status of this Memo

This document is an Internet-Draft. Internet-Drafts are working
documents of the Internet Engineering Task Force (IETF), its areas,
and its working groups. Note that other groups may also distribute
working documents as Internet-Drafts.

Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet- Drafts as reference
material or to cite them other than as _work "work in progress._ progress."

To learn the current status of any Internet-Draft, please check the
_1id-abstracts.txt_
"1id-abstracts.txt" listing contained in the Internet- Drafts Shadow
Directories on ftp.is.co.za (Africa), nic.nordu.net (Europe),
munnari.oz.au (Pacific Rim), ds.internic.net (US East Coast), or
ftp.isi.edu (US West Coast).

Abstract

This memo defines a the profile of the MIME Content-Type [MIME-DIR] for
directory information profile for a white pages
person, to be carried in an application/directory MIME Content-Type. white-pages person object, based on a
vCard electronic business card. The profile consists definition is independent
of type definitions (e.g., any particular directory service or protocol. The profile is
defined for representing and exchanging a variety of information
about an individual (e.g., formatted and structured name and delivery
addresses, email
address) address, multiple telephone numbers, photograph,
logo, audio clips, etc.). The directory information used by this
profile is based on the attributes for the person object defined in
the X.520 and X.521 directory services recommendations. The profile
also provides the corresponding format method for including a [VCARD] representation of values that each type is
allowed to contain.

1. Overview

The application/directory a
white-pages directory entry within the MIME Content-Type defined in by
the [MIME-DIR] is
used for representing directory information in MIME format. It document.

1. Overview

The [MIME-DIR] document defines a general framework MIME Content-Type for carrying _type: value_ style holding
different kinds of directory information. The directory information in the body
may be based on any of a MIME message, but does not define
specific types or values. number of directory schemas. This document
defines a [MIME-DIR] usage profile containing
the types and corresponding value formats for representing conveying directory
information about an electronic business card. The profile reflects based on one such schema; that of the vCard (The Electronic Business Card) white-pages type of
person object.

The schema is based on the attributes for the person object defined
in [VCARD].

1.1 The vCard Profile the X.520 and X.521 directory services recommendations. The profile is schema
has augmented the basic attributes defined as follows, using in the profile registration
template from Section 8 of [MIME-DIR].

1.2 vCard Profile Definition

To: ietf-mime-direct@umich.edu

Subject: Registration X.500 series
recommendation in order to provide for an electronic representation
of application/directory MIME profile vcard the information commonly found on a paper business card. This

Dawson & Howes [Page 1] Expires June September 1997

vCard Application/Directory Content Type

Profile name: vcard MIME Directory Profile purpose: To hold vcard information about an electronic
business card.

schema was first defined in the [VCARD] document. Hence, this [MIME-
DIR] profile is referred to as the vCard MIME Directory Profile.

A directory entry based on this usage profile can include traditional
directory, white-pages information such as the distinguished name
used to uniquely identify the entry, a formatted representation of
the name used for user-interface or presentation purposes, both the
structured and presentation form of the delivery address, various
telephone numbers and organizational information associated with the
entry. In addition, traditional paper business card information such
as an image of an organizational logo or identify photograph can be
included in this person object.

The vCard MIME Directory Profile types: also provides support for
representing other important information about the person associated
with the directory entry. For instance, the date of birth of the
person; an audio clip describing the pronunciation of the name
associated with the directory entry, or some other application of the
digital sound; longitude and latitude geo-positioning information
related to the person associated with the directory entry; date and
time that the directory information was last updated; annotations
often written on a business card; Uniform Resource Locators (URL) for
a website; public key information. The profile also provides support
for non-standard extensions to the schema. This provides the
flexibility for implementations to augment the current capabilities
of the profile in a standardized way. More information about this
electronic business card format can be found in [VCARD].

2. The vCard Mime Directory Profile Registration

This profile is identified by the following [MIME-DIR] registration
template information. Subsequent sections define the profile
definition.

To: ietf-mime-directory@umich.edu

Subject: Registration of application/directory MIME profile VCARD

Profile name: VCARD

Profile purpose: To hold person object or white-pages type of
directory information. The person schema captured in the directory
entries is that commonly found in an electronic business card.

Predefined MIME Directory types used: SOURCE, NAME, PROFILE, BEGIN,
END, PROFILE.

Predefined MIME Directory parameters used: ENCODING, VALUE, CHARSET,
LANGUAGE, CONTEXT.

New types: FN, N, PHOTO, BDAY, ADR, LABEL, TEL, EMAIL, MAILER, TZ,
GEO, TITLE, ROLE, LOGO, AGENT, ORG, NOTE, REV, SOUND, URL, UID,
VERSION, KEY

Dawson & Howes [Page 2] Expires September 1997

vCard MIME Directory Profile

New parameters: TYPE

Profile special notes: The type-grouping feature of [MIME-DIR] is
supported by this profile to group related vCard properties about a
directory entry. For example, vCard properties describing WORK or
HOME related characteristics MAY be grouped with a unique group
label.

The profile permits the use of non-standard types (i.e., those
identified with the prefix string "X-") as a flexible method for
implementations to extend the functionality currently defined within
this profile.

3. MIME Directory Features

The vCard MIME Directory Profile makes use of many of the features
defined by [MIME-DIR]. The following sub-sections describe specific
usage constraints or extensions of these predefined features.

3.1 BEGIN and END Type

The content entity must MUST begin with the type BEGIN and type with a value of
VCARD. The content entity MUST end with the END type with a value of
VCARD.

3.2 NAME Type

If the NAME type END. There appears within a MIME entity conforming to this
profile, it's value is no other ordering
limitations on types the displayable, presentation text associated
with the source for the vCard, as specified in the SOURCE type.

3.3 PROFILE Type

If the PROFILE type appears within a MIME entity conforming to this
profile, it's value must be "VCARD".

3.4 SOURCE Type

If the SOURCE type appears within a MIME entity conforming to this
profile, it's value provides information how to find the content entity. source for
the vCard.

3.5 ENCODING Parameter

The default transfer encoding for the vCard profile is _8BIT_. "8bit". The
default transfer encoding can MAY be overridden for an individual type
value by using the _ENCODING_ "ENCODING" type parameter. The parameter value can
be reset to either _7BIT_, _BASE64_ "7bit", "base64" or _QUOTED-PRINTABLE_. "quoted-printable". This type
parameter may MAY be used on any type, unless specified otherwise by the
profile type.

The usual line-folding technique described in [MIME-DIR] can be used
to represent type values consisting of long lines of text. For
example, individual lines in the content entity are delimited by registration.

Dawson & Howes [Page 3] Expires September 1997

vCard MIME Directory Profile

3.6 CHARSET Parameter

The default character set for the
[RFC 822] line break, which vCard profile is a CRLF sequence (ASCII decimal 13,
followed by ASCII decimal 10). Long lines of text can "UTF-8". The
default transfer encoding MAY be split into a
multiple-line representation overridden for an individual type
value by using the RFC 822 _folding_ technique.
That is, wherever there may be linear white space (NOT simply LWSP-
chars), a CRLF immediately followed by at least one LWSP-char may
instead "CHARSET" type parameter. The parameter value MAY
be inserted. For example the line:

NOTE:This is a long note that exists on a long line.

Can reset to any IANA registered character set. This type parameter
MAY be represented as:

NOTE:This is a long note
that exists used on a long line. any type, unless specified otherwise by the profile
type registration.

3.7 LANGUAGE

The process of moving from this folded multiple-line representation
of a default language for the vCard profile is "en-US" (US English).
The default language MAY be overridden for an individual type value to its single line representation is called
_unfolding_. Unfolding is accomplished by regarding CRLF immediately
followed
by a LWSP-char as equivalent to using the LWSP-char.

It is recommended that folding "LANGUAGE" type parameter. The prameter value MAY be limited
reset to higher-level syntactic
breaks any IANA registered language. This type parameter MAY be
used on any type, unless specified otherwise by the profile type
registration.

3.8 Line Endings

The usual line-folding technique described in structured components [MIME-DIR] can be used
to represent type values consisting of the property definition. long lines of text.

A formatted text line break in a type value, MUST also be specified by a
(RFC 822) line break, which is a CRLF sequence. However, since the
CRLF sequence is used to delimit a line, type values with formatted
line breaks (i.e., multiple lines) MUST be encoded using an
alternate encoding of either Quoted-Printable or Base64, as defined
in [RFC 1521]. the Quoted-
Printable encoding.

For example, in the Quoted-Printable encoding the multiple lines of
formatted text are separated with a Quoted-Printable CRLF sequence of
_=0D_
"=0D" followed by _=0A_ "=0A" followed by a Quoted-Printable soft line

Dawson & Howes [Page 2] Expires June 1997

vCard Application/Directory Content Type
break sequence of _=_. "=". Quoted-Printable lines of text must also be
limited to less than 76 characters. The 76 characters does not
include the CRLF [RFC 822] line break sequence. For example a
multiple line LABEL value of:

Mr. John Q. Public
123 Main Street
Any Town, CA 12345

Would be represented in a Quoted-Printable encoding as:

LABEL;ENCODING=QUOTED-PRINTABLE:Mr. John Q. Public=0D=0A=
123 Mail Street=0D=0A=
Any Town, CA 12345

3.9 Structured Type Values

Compound property values are delimited by a field delimiter,
specified by the SEMI-COLON character (ASCII decimal 59). A SEMI-
COLON in a component of a compound property value must be escaped
with a Backslash character

The default character set is _UTF-8_. The default character set can
be overridden for an individual type value by using the _CHARSET_
type parameter.

Dawson & Howes [Page 4] Expires September 1997

vCard MIME Directory Profile

This type parameter may be used on any profile type.
However, supports the use type grouping mechanism defined in [MIME-
DIR]. Grouping of this parameter on some profile related types may not make
sense.

The default language is _en-US_ (US English). a useful technique to communicate
common semantics concerning the properties of a vCard.

4. vCard Features

4.1 VALUE Type Parameter

The default language
can be overridden for an individual predefined data type value values specified in [MIME-DIR] have been
extended by using the
_LANGUAGE_ type parameter. This type parameter may be used on any vCard profile type. However, the use to include a number of this parameter on some profile value types may not make sense. that
are specific to this profile.

4.1.1 BINARY

The default location of the "binary" value type values is inline with the profile
type. However, for some profile types, such as those specifies that specify
multimedia values, it is efficient to organize the type value as a
separate MIME entity. The is inline,
encoded binary data. This value type parameter _VALUE_ can may be specified to
override in the _INLINE_ location of PHOTO,
LOGO, SOUND, and KEY types.

If inline, encoded binary data is specified, the ENCODING type value. The type value can
parameter must be specified as being located in a separate MIME entity with the
_CID_ value. In this case, used to specify the type encoding format.

The value type is defined by the Content-ID for following notation:

binchar = <Any character valid in the
MIME entity containing base64 or quoted-printable
encoding>
binary = *binchar ;A base64 or quoted-printable
encoding of the binary information

4.1.2 VCARD

The "vcard" value type value. In addition, specifies that the type value
can is another
vCard. This value type may be specified as being located out on the network within some
Internet resource with in the _URL_ value. In AGENT type. The value
type is defined by this case, specification.

4.1.3 PHONE-NUMBER

The "phone-number" value type specifies that the type value is the Uniform Resource Locator for the Internet resource containing
the type value. a
telephone number. This value type parameter may be used on any profile type.
However, the use of this parameter on some profile types may not make
sense.

This profile supports specified in the TEL type.
The value type grouping mechanism defined in [MIME-
DIR]. Grouping of related profile types is a useful technique to
communicate common semantics concerning text value that has the properties semantics of a vCard
object.

Intended usage: COMMON

Dawson & Howes [Page 3] Expires June 1997

vCard Application/Directory Content Type telephone
number.

4.1.4 UTC-OFFSET

The associated "utc-offset" value type definitions follow, using specifies that the type registration
template value is a signed
offset from Section 9 of [MIME-DIR].

1.3 Delimiter Profile Types

The following profile types are used to delimit the vCard data within UTC. This value type may be specified in the content TZ type. These types are necessary to completely define

The format of the
content offset from UTC is defined by [DATETIME]. The value
type so that it might be identified is an offset from Coordinated Universal Time (UTC). It is
specified as a vCard object when
the content type is positive or negative difference in a persistent form outside units of hours and
minutes (e.g., +hh:mm). The time is specified as a MIME message.

1.3.1 BEGIN Type Definition

To: ietf-mime-direct@umich.edu

Subject: Registration of application/directory MIME type BEGIN

Type name: BEGIN

Type purpose: To delimit the beginning of the 24-hour clock.
Hour values are from 00 to 24, and minute values are from 00 to 59.
Hour and minutes are 2-digits with high order zeroes required to
maintain digit count. The extended format for ISO 8601 UTC offsets

Dawson & Howes [Page 5] Expires September 1997

vCard content data.

Type encoding: text.

Type special notes: MIME Directory Profile

MUST be used. The only valid value is _vCard_.

Type example:

BEGIN:vCard

1.3.2 END Type Definition

To: ietf-mime-direct@umich.edu

Subject: Registration extended format makes use of application/directory MIME type END

Type name: END

Type purpose: To delimit the end a colon character as a
separator of the vCard content data.

Type encoding: text.

Type special notes: The type either has no value or has the hour and minute text fields.

The value
_vCard_.

Type example:

END: vCard

1.4 is defined by the following notation:

time-hour = 2DIGIT ;00-24
time-minute = 2DIGIT ;00-60
time-numzone = ("+" / "-") time-hour ":" time-minute
utc-offset = time-numzone

4.2 Identification Profile Types

These profile types are concerned with used in the vCard profile to capture information
associated with the identification and naming of the individual person or
resource associated with the vCard object.

Dawson & Howes [Page 4] Expires June 1997

vCard Application/Directory Content Type

1.4.1 vCard.

4.2.1 FN Type Definition

To: ietf-mime-direct@umich.edu ietf-mime-directory@umich.edu

Subject: Registration of application/directory MIME type FN

Type name:FN

Type purpose: To specify the formatted name string associated with
the vCard object.

Type encoding: text.

Type special notes: The value is intended to be used as a formatted
string text corresponding to how the name
of the individual or resource
associated with object the vCard represents.

Type encoding: The default is to 8bit. May also be displayed. reset to 7bit or
quoted-printable.

Type value: text.

Type special notes: This type is based on the semantics of the X.520
Common Name attribute.

The type may specify the type parameters CHARSET, to specify a
character set for the type value, and LANGUAGE, to specify a language
for the type value. These are further defined in [MIME-DIR].

Type example:

FN:Mr. John Q. Public, Esq.

1.4.2

4.2.2 N Type Definition

To: ietf-mime-direct@umich.edu ietf-mime-directory@umich.edu

Subject: Registration of application/directory MIME type N

Type name: N

Type purpose: To specify the structured components of the name strings associated with of the
object the vCard object. represents.

Type encoding: The default is 8bit. May also be reset to 7bit or
quoted-printable.

Type value: text.

Dawson & Howes [Page 6] Expires September 1997

vCard MIME Directory Profile

Type special note: The type value is a structured string text corresponding,
in sequence, to the Family Name, Given Name, Additional Names,
Honorific Prefixes, and Suffixes corresponding to
the individual or resource associated with the vCard. Honorific Suffixes. The component
strings text components are
delimited by the SEMI-COLON character (ASCII decimal 59) and possibly
one or more LWSP. This type is based on the semantics of the X.520
individual name attributes.

The type may specify the type parameters CHARSET, to specify a
character set for the type value, and LANGUAGE, to specify a language
for the type value. These are further defined in [MIME-DIR].

Type example:

N:Public;John;Quinlan;Mr.;Esq.

Dawson & Howes [Page 5] Expires June 1997

vCard Application/Directory Content Type

1.4.3

4.2.3 PHOTO Type Definition

To: ietf-mime-direct@umich.edu ietf-mime-directory@umich.edu

Subject: Registration of application/directory MIME type PHOTO

Type name: PHOTO

Type purpose: To specify an image or photograph information that
annotates some aspect of the vCard object. By default this type is
used to specify a photograph or image of the individual or resource
associated with object the vCard. vCard represents.

Type encoding: text.

Type special notes: The type may include the type parameter _TYPE_ to
specify the format of the graphic image. The TYPE parameter values
may include _GIF_ default is 8bit. May also be reset to indicate the GIF format and _JPEG_ base64 in
order to indicate
the JPEG format. permit inline, encoded binary data.

Type value: The type default is binary. It may also include the type parameter
_ENCODING_ to specify the content encoding applied be reset to the graphic
image. url. The ENCODING parameter
url value may include _7BIT_ to indicate
the 7-bit encoding, _8BIT_ to indicate the 8-bit encoding, _BASE64_
to indicate the Base64 encoding or _QUOTED-PRINTABLE_ be used to indicate the
quoted printable encoding. specify a value outside of this MIME entity.

Type special notes: The type may also MAY include the type parameter _VALUE_ "TYPE" to
specify the location of the type value. graphic image format type. The
VALUE TYPE parameter values may include _INLINE_ to indicate that MUST
be one of the
graphic IANA registered image value is included within the content type value, _URL_
to indicate the uniform resource locator for where the content for
the graphic formats. In addition, a non-
standard image can format MAY be found in the network, and _CID_ to indicate
the content-id for the MIME entity that encapsulates the content for
the graphic image. specified.

Type example:

PHOTO;VALUE=URL:=http://www.abc.com/pub/photos

PHOTO;VALUE=url:=http://www.abc.com/pub/photos
/jqpublic.gif

1.4.4

4.2.4 BDAY Type Definition

To: ietf-mime-direct@umich.edu ietf-mime-directory@umich.edu

Subject: Registration of application/directory MIME type BDAY

Type name: BDAY

Type purpose: To specify the birthdate of the individual associated
with object the vCard. vCard
represents.

Type encoding: text. 8bit.

Type special notes: value: The text value default is a string conforming date. It may also be reset to the ISO
8601 calendar date, complete representation. date-time.

Type example: examples:

Dawson & Howes [Page 6] 7] Expires June September 1997

vCard Application/Directory Content Type MIME Directory Profile

BDAY:1996-04-15

1.5

BDAY:1953-10-15T23:10:00

BDAY:1987-09-27T08:30:00-06:00

4.3 Delivery Addressing Profile Types

These profile types are concerned with information associated with related to the delivery
addressing or label for the object the vCard object.

1.5.1 represents.

4.3.1 ADR Type Definition

To: ietf-mime-direct@umich.edu ietf-mime-directory@umich.edu

Subject: Registration of application/directory MIME type ADR

Type name: ADR

Type purpose: To specify the structured components of the delivery
address strings of for the individual or resource associated with object the vCard. vCard represents.

Type encoding: text The default is 8bit. It may also be reset to 7bit or
quoted-printable.

Type value: text.

Type special notes: The type value is a string structured text consisting of a
sequence of address components (i.e., extended address, street
address, locality, region, postal code, and country name) separated
by SEMI-COLON character (ASCII decimal 59) and optionally one or more
LWSP.

The usual line-folding technique described in [MIME-DIR] can be used
to represent type values consisting of long lines of text. However, a
line break components (i.e., extended address, post office
box, street address, locality, region, postal code, and country name)
separated by the SEMI-COLON character in a value MUST be encoded using either Base64 (ASCII decimal 59) and
optionally one or Quoted-Printable methods. more LWSP.

The type may include the type parameter _TYPE_ "TYPE" to further qualify the
usage of specify the
delivery address. address type. The TYPE parameter values may include:
_DOM_ include "dom" to
indicate a domestic delivery address, _INTL_ address; "intl" to indicate an
international delivery address, _POSTAL_ address; "postal" to indicate a postal
delivery address, _PARCEL_ address; "parcel" to indicate a parcel delivery address,
_HOME_ address;
"home" to indicate a delivery address for a residence, _WORK_ residence; "work" to
indicate delivery address for a place of work, work; and _PREF_ for "pref" to indicate
the preferred delivery address when more than one address might be
specified. These type parameter values may be specified as a
parameter list (i.e., _TYPE=DOM;TYPE=POSTAL_) "TYPE=dom;TYPE=postal") or as a value list
(i.e., _TYPE=DOM;POSTAL_). "TYPE=dom,postal"). This type is based on semantics of the
X.520 geographical and postal addressing attributes. The default is
_TYPE=INTL;POSTAL;PARCEL;WORK_.
"TYPE=intl,postal,parcel,work". The default can be overridden to some
other set of values by specifying one or more alternate values. For
example, the default can be reset to _TYPE=DOM;POSTAL;WORK;HOME_ "TYPE=dom,postal,work,home" to
specify a domestic delivery address for postal delivery to a
residence that is also used for work.

The type may also specify the type parameters CHARSET, to specify a
character set for the type value, and LANGUAGE, to specify a language
for the type value. These are further defined in [MIME-DIR].

Type example:

Dawson & Howes [Page 7] 8] Expires June September 1997

vCard Application/Directory Content Type

ADR;TYPE=DOM;HOME;POSTAL;PARCEL:123 MIME Directory Profile

ADR;TYPE=dom,home,postal,parcel:123 Main
Street;Any Town;CA;91921-1234

1.5.2

4.3.2 LABEL Type Definition

To: ietf-mime-direct@umich.edu ietf-mime-directory@umich.edu

Subject: Registration of application/directory MIME type LABEL

Type name: LABEL

Type purpose: To specify the formatted text corresponding to delivery
address string of the
individual or resource associated with object the vCard. vCard represents.

Type encoding: text The default is 8bit. It may also be reset to 7bit or
quoted-printable.

Type value: text.

Type special notes: The type value is a string consisting of a
sequence of lines of formatted text corresponding to the delivery
address.

The usual line-folding technique described in [MIME-DIR] can that may be used
to represent type values consisting of long lines of text. However, a
formatted line break character in present a value MUST be encoded using
either Base64 or Quoted-Printable methods. delivery address label for the object the vCard
represents.

The type may include the type parameter _TYPE_ "TYPE" to further qualify the
usage of the specify delivery label.
label type. The TYPE parameter values may include:
_DOM_ include "dom" to indicate a
domestic delivery label, _INTL_ label; "intl" to indicate an international delivery label, _POSTAL_
label; "postal" to indicate a postal delivery
label, _PARCEL_ label; "parcel" to
indicate a parcel delivery label, _HOME_ label; "home" to indicate a delivery label
for a residence, _WORK_ residence; "work" to indicate delivery label for a place of work,
work; and _PREF_ for "pref" to indicate the preferred delivery label when more
than one label might be specified. These type parameter values may
specified as a parameter list (i.e.,
_TYPE=DOM;TYPE=POSTAL_) "TYPE=dom;TYPE=postal") or as a
value list (i.e., _TYPE=DOM;POSTAL_). "TYPE=dom,postal"). This type is based on semantics
of the X.520 geographical and postal addressing attributes. The
default is _TYPE=INTL;POSTAL;PARCEL;WORK_. "TYPE=intl,postal,parcel,work". The default can be
overridden to some other set of values by specifying one or more
alternate values. For example, the default can be reset to _TYPE=INTL;POST;PARCEL;HOME_
"TYPE=intl,post,parcel,home" to specify an international delivery
label for both postal and parcel delivery to a residencial location.

Type example:

LABEL;ENCODING=QUOTED-PRINTABLE;TYPE=DOM;HOME;=
POSTAL;PARCEL:Mr.John

LABEL;ENCODING=quoted-printable;TYPE=dom,home,=
postal,parcel:Mr.John Q. Public, Esq.=0D=0A=
Mail Drop: TNE QB=0D=0A=
123 Main Street=0D=0A=
Any Town, CA 91921-1234=0D=0A=
U.S.A.

Dawson & Howes [Page 8] Expires June 1997

vCard Application/Directory Content Type

1.6

4.4 Telecommunications Addressing Profile Types

These profile types are concerned with information associated with the
telecommunications addressing of the object the vCard object.

1.6.1 represents.

Dawson & Howes [Page 9] Expires September 1997

vCard MIME Directory Profile

4.4.1 TEL Type Definition

To: ietf-mime-direct@umich.edu ietf-mime-directory@umich.edu

Subject: Registration of application/directory MIME type TEL

Type name: TEL

Type purpose: To specify the telephone number for telephony
communication with the individual or resource associated with object the
vCard. vCard represents.

Type encoding: text. 8bit.

Type value: phone-number.

Type special notes: .The value of this type is specified in a
canonical form in order to specify an unambiguous representation of
the globally unique telephone endpoint. This type is based on the
X.500 Telephone Number attribute.

The type may include the type parameter _TYPE_ "TYPE" to further qualify the
usage of specify intended
use for the telephone number. The TYPE parameter values may include:
_HOME_
"home" to indicate a telephone number associated with a residence,
_MSG_
"msg" to indicate the telephone line has voice messaging support,
_WORK_
"work" to indicate a telephone number associated with a place of
work, _PREF_ "pref" to indicate a preferred-use telephone number, _VOICE_ "voice" to
indicate a voice telephone line, _FAX_ "fax" to indicate a facsimile
telephone line, _CELL_ "cell" to indicate a cellular telephone line, _VIDEO_ "video"
to indicate a video conferencing telephone line, _PAGER_ "pager" to indicate
a paging device telephone line, _BBS_ "bbs" to indicate a bulletin board
system telephone line, _MODEM_ "modem" to indicate a MODEM connected
telephone line, _CAR_ "car" to indicate a car-phone telephone line, _ISDN_ "isdn"
to indicate an ISDN service telephone line. The default type is
_VOICE_.
"voice". These type parameter values may specified as a parameter
list (i.e., _TYPE=WORK;TYPE=VOICE_) "TYPE=work;TYPE=voice") or as a value list (i.e.,
_TYPE=WORK;VOICE_).
"TYPE=work,voice"). The default may be overridden to another set of
values by specifying one or more alternate values. For example, the
default TYPE of _VOICE_ "voice" can be reset to a WORK and HOME, VOICE and
FAX telephone number by the value list _TYPE=WORK;HOME;VOICE;FAX_. "TYPE=work,home,voice,fax".

Type example:

TEL;TYPE=WORK;VOICE;PREF;MSG:+1-213-555-1234

1.6.2

TEL;TYPE=work,voice,pref,msg:+1-213-555-1234

4.4.2 EMAIL Type Definition

To: ietf-mime-direct@umich.edu ietf-mime-directory@umich.edu

Subject: Registration of application/directory MIME type EMAIL

Dawson & Howes [Page 9] Expires June 1997

vCard Application/Directory Content Type

Type name: EMAIL

Type purpose: To specify the address for electronic mail address for
communication with the vCard object. The address is in the form of a
specific addressing type. The default is an Internet addressing type. object the vCard represents.

Dawson & Howes [Page 10] Expires September 1997

vCard MIME Directory Profile

Type encoding: 8bit.

Type value: text.

Type special notes: . The type may include the type parameter _TYPE_ "TYPE"
to specify the addressing type format of the electronic mail address. The TYPE
parameter values may include: _INTERNET_ "internet" to indicate an Internet
addressing type or _X400_ "x400" to indicate a X.400 addressing type. Other Any
other IANA registered address type values are allowed, but are to may also be specified by individual
electronic mail service providers. specified. The default
email type is
_INTERNET_. "internet". Any non-standard value may also be
specified.

Type example:

EMAIL;Type=INTERNET:jqpublic@xyz.dom1.com

1.6.3

EMAIL;TYPE=internet:jqpublic@xyz.dom1.com

4.4.3 MAILER Type Definition

To: ietf-mime-direct@umich.edu ietf-mime-directory@umich.edu

Subject: Registration of application/directory MIME type MAILER

Type name: MAILER

Type purpose: To specify the type of electronic mail software that is
used by the individual associated with the vCard object. vCard.

Type encoding: The default is 8bit. May also be reset to 7bit or
quoted-printable.

Type value: text.

Type special notes: This information may provide assistance to a
correspondent regarding the type of data representation which can be
used, and how they may be packaged. This property is based on the
private MIME type X-Mailer that is generally accepted within the implemented by MIME user
agent product offerings. products.

Type example:

MAILER:GypsyMail

MAILER:PigeonMail 2.1

1.7

4.5 Geographical Profile Types

These profile types are concerned with information associated with
geographical positions or regions associated with the object the
vCard object.

1.7.1 represents.

4.5.1 TZ Type Definition

To: ietf-mime-direct@umich.edu ietf-mime-directory@umich.edu

Subject: Registration of application/directory MIME type TZ

Dawson & Howes [Page 10] 11] Expires June September 1997

vCard Application/Directory Content Type MIME Directory Profile

Type name: TZ

Type purpose: To specify information related to the time zone of the
object the vCard object. represents.

Type encoding: text. 8bit.

Type special notes: the type value value: The default is specified as a string as
specified in a manner consistent with [ISO 8601]. utc-offset. It is an offset
from Coordinated Universal Time (UTC). An ISO 8601 UTC offset, in
basic format, is specified as a positive or negative difference in
units of hours and minutes (e.g., +hhmm). If minutes are zero, then
they may also be omitted and the format would be specified in units of
hours (e.g., +hh). The time is specified as a 24-hour clock. Hour
values are from 00 to 24, and minute values are from 00 to 59. Hour
and minutes are 2-digits with high order zeroes required reset to maintain
digit count. The extended format for ISO 8601 makes use of a colon
character as a separator of the hour and minute substrings. text.

Type example:

TZ:-0500

1.7.2 examples:

TZ:-05:00

TZ;VALUE=text:-05:00, EST, Raleigh/North America

4.5.2 GEO Type Definition

To: ietf-mime-direct@umich.edu ietf-mime-directory@umich.edu

Subject: Registration of application/directory MIME type GEO

Type name: GEO

Type purpose: To specify information related to the global
positioning of the object the vCard object. represents.

Type encoding: text. 8bit.

Type value: Two float values separated by the SEMI-COLON character
(ASCII decimal 59).

Type special notes: the type The value is a structured string that
specifies a the longitude and latitude. latitude of the
object the vCard represents. The latitude represents the location
north and south of the equator as a positive or negative number,
respectively. The longitude represents the location east and west of
the prime meridian as a positive or negative number, respectively.
The string text components are separated by the SEMI-COLON character (ASCII
decimal 59).

Type example:

GEO:37.24;-17.87

1.8

GEO:+37.24;-17.87

4.6 Organizational Profile Types

These profile types are concerned with information associated with
characteristics of the organization or organizational units
associated with of the
object the vCard object.

Dawson & Howes [Page 11] Expires June 1997

vCard Application/Directory Content Type

1.8.1 represents.

4.6.1 TITLE Type Definition

To: ietf-mime-direct@umich.edu ietf-mime-directory@umich.edu

Subject: Registration of application/directory MIME type TITLE

Dawson & Howes [Page 12] Expires September 1997

vCard MIME Directory Profile

Type name: TITLE

Type purpose: To specify the job title, functional position or
function of the individual or resource associated with object the vCard
object within an organization represents.

Type encoding: The default is 8bit. May also be reset to 7bit or
quoted-printable.

Type value: text.

Type special notes: This type is based on the X.520 Title attribute.

The usual line-folding technique described in [MIME-DIR] can be used
to represent type values consisting of long lines of text.

The type may specify the type parameters CHARSET, to specify a
character set for the type value, and LANGUAGE, to specify a language
for the type value. These are further defined in [MIME-DIR].

Type example:

TITLE:Director, Research and Development

1.8.2

4.6.2 ROLE Type Definition

To: ietf-mime-direct@umich.edu ietf-mime-directory@umich.edu

Subject: Registration of application/directory MIME type ROLE

Type name: ROLE

Type purpose: To specify information concerning the role, occupation,
or business category of the vCard object within an organization. the vCard represents.

Type encoding: The default is 8bit. May also be reset to 7bit or
quoted-printable.

Type value: text.

Type special notes: This type is based on the X.520 Business Category
explanatory attribute. This property is included as an organizational
type to avoid confusion with the semantics of the TITLE type and
incorrect usage of that type when the semantics of this type is
intended.

The type may specify the type parameters CHARSET, to specify a
character set for the type value, and LANGUAGE, to specify a language
for the type value. These are further defined in [MIME-DIR].

Type example:

ROLE:Programmer

Dawson & Howes [Page 12] Expires June 1997

vCard Application/Directory Content Type

1.8.3

4.6.3 LOGO Type Definition

To: ietf-mime-direct@umich.edu ietf-mime-directory@umich.edu

Subject: Registration of application/directory MIME type LOGO

Type name: LOGO

Dawson & Howes [Page 13] Expires September 1997

vCard MIME Directory Profile

Type purpose: To specify a graphic image of the a logo of the
organization that is associated with
the individual or resource object the vCard belongs to. represents.

Type encoding: text.

Type value: The type default is binary. It may also include the type parameter
_ENCODING_ to specify the content encoding applied be reset to the graphic
image. url. The ENCODING parameter
url value may include _BASE64_ to indicate
the Base64 encoding or _QUOTED-PRINTABLE_ to indicate the quoted-
printable encoding. The type may also include the type parameter
_VALUE_ be used to specify the location a value outside of the type value. this MIME entity.

Type special notes: The VALUE
parameter values may include _INLINE_ to indicate that the graphic
image value is included within the content type value, _URL_ to
indicate the uniform resource locator for where MAY include the content for type parameter "TYPE" to
specify the graphic image can format type. The TYPE parameter values MUST
be found in the network, and _CID_ to indicate the
content-id for the MIME entity that encapsulates the content for one of the
graphic image. IANA registered image formats. In addition, a non-
standard image format MAY be specified.

Type example:

LOGO;VALUE=URL:http://www.abc.com/pub/logos/abccorp.jpg

1.8.4

4.6.4 AGENT Type Definition

To: ietf-mime-direct@umich.edu ietf-mime-directory@umich.edu

Subject: Registration of application/directory MIME type AGENT

Type name: AGENT

Type purpose: To specify information about another person who will
act on behalf of the individual or resource associate associated with the vCard
object.
vCard.

Type encoding: text. 8-bit.

Type value: The default is vcard. It may also be reset to text or
url. The text value may be used to specify textual information. The
url value may be used to specify information outside of this MIME
entity.

Type special notes: This type typically is used to specify an area
administrator, assistant, or secretary for the individual associated
with the vCard object. vCard. A key characteristic of the Agent type is that it
represents somebody or something that is separately addressable.
The value for this type is the content message identifier or Uniform

Dawson & Howes [Page 13] Expires June 1997

vCard Application/Directory Content Type

Resource Locator associated with the vCard defining the Agent
individual or resource.

The type may include the type parameter _VALUE_ to specify the
location of the type value. The VALUE parameter values may include
_CID_ to indicate the value specifies the content identifier for the
MIME entity containing the value or _URL_ to indicate the value
specifies the uniform resource locator for the value. The type
parameter may also include _INLINE_; however, this is not a
recommended practice as MIME user agents will not be expected to be
able to process vCard objects nested in this manner. Nested vCard
object will be expected to be mailed within a single message as
multiple MIME entities. The INLINE nesting of vCard object may have
some limited utility in where a monolithic data stream is required.

Type example:

AGENT;VALUE=CID:
<JQPUBLIC.part3.960129T083020.xyzMail@host3.com>

1.8.5

AGENT;VALUE=URL:
CID:///<JQPUBLIC.part3.960129T083020.xyzMail@host3.com>

4.6.5 ORG Type Definition

To: ietf-mime-direct@umich.edu ietf-mime-directory@umich.edu

Subject: Registration of application/directory MIME type ORG

Type name: ORG

Dawson & Howes [Page 14] Expires September 1997

vCard MIME Directory Profile

Type purpose: To specify the organizational name and units associated
with the vCard object. vCard.

Type encoding: The default is 8bit. May also be reset to 7bit or
quoted-printable.

Type value: text.

Type special notes: The type is based on the X.520 Organization Name
and Organization Unit attributes. The type value is a structured
string text
consisting of the organization name, followed by any organizational
units. The string text components are separated the SEMI-
COLON SEMI-COLON character
(ASCII decimal 59).

The type may specify the type parameters CHARSET, to specify a
character set for the type value, and LANGUAGE, to specify a language
for the type value. These are further defined in [MIME-DIR].

Type example:

ORG:ABC, Inc.;North American Division;Marketing

1.9

4.7 Explanatory Profile Types

These profile types are concerned with additional explanations, such as that
related to informational notes or revisions specific to the
vCard object.

Dawson & Howes [Page 14] Expires June 1997

vCard Application/Directory Content Type

1.9.1 notes or revisions specific to the vCard.

4.7.1 NOTE Type Definition

To: ietf-mime-direct@umich.edu ietf-mime-directory@umich.edu

Subject: Registration of application/directory MIME type NOTE

Type name: NOTE

Type purpose: To specify supplemental information or a comment that
is associated with the vCard object. vCard.

Type encoding: The default is 8bit. May also be reset to 7bit or
quoted-printable.

Type value: text.

Type special notes: The type is based on the X.520 Description
attribute.

The type may specify the type parameters CHARSET, to specify a
character set for the type value, and LANGUAGE, to specify a language
for the type value. These are further defined in [MIME-DIR].

Type example:

NOTE:This fax number is operational 0800 to 1715
EST, Mon-Fri.

1.9.2

Dawson & Howes [Page 15] Expires September 1997

vCard MIME Directory Profile

4.7.2 REV Type Definition

To: ietf-mime-direct@umich.edu ietf-mime-directory@umich.edu

Subject: Registration of application/directory MIME type REV

Type name: REV

Type purpose: To specify revision information about the current vCard
object.
vCard.

Type encoding: text. 8-bit.

Type value: The default is date-time. May also be reset to date.

Type special notes: The type value is a calendar date and time of day
in a form conforming to ISO 8601 complete representation. The value
distinguishes the current revision of the information defining this
vCard object.

Type example:

REV:1995-10-31T22:27:10Z

1.9.3 SOUND Type Definition

To: ietf-mime-direct@umich.edu

Subject: Registration of application/directory MIME type SOUND

Type name: SOUND

Dawson & Howes [Page 15] Expires June 1997

vCard Application/Directory Content Type

Type purpose: To specify a digital sound content information that
annotates some aspect of the vCard object. By default this type is
used to specify the proper pronunciation of the name type value of
the vCard object.

Type encoding: text.

Type special notes: The type may include the type parameter _TYPE_ to
specify the format representation of the digital sound. The TYPE parameter values
may include _PCM_ to indicate the MIME basic audio content type ISO 8601 calendar
date and
_WAVE_ to indicate the Wave time of day format. The type may also include the
type parameter _ENCODING_ to specify the content encoding applied to
the digital sound. The ENCODING parameter value may include _BASE64_
to indicate the Base64 encoding. The type may also include the type
parameter _VALUE_ to specify the location of the type value. The
VALUE parameter values may include _INLINE_ to indicate that the
digital sound is included within the content type value, _URL_ to
indicate the uniform resource locator for where the content for the
digital sound can be found in the network, and _CID_ to indicate the
content-id for the MIME entity that encapsulates the content for distinguishes the
digital sound. current
revision of the information defining this vCard.

Type example:
SOUND;TYPE=PCM;VALUE=CID:<JOHNQPUBLIC.part8.
19960229T080000.xyzMail@host1.com>

1.9.4 URL

REV:1995-10-31T22:27:10Z

4.7.3 SOUND Type Definition

To: ietf-mime-direct@umich.edu ietf-mime-directory@umich.edu

Subject: Registration of application/directory MIME type URL SOUND

Type name: URL SOUND

Type purpose: To specify an Internet location a digital sound content information that can be
annotates some aspect of the vCard. By default this type is used to
obtain real-time or more complete information about
specify the individual or
resource associate with proper pronunciation of the vCard object. name type value of the vCard.

Type encoding: text. The default is 8bit. May also be reset to base64 in
order to permit inline encoded binary data.

Type special notes: An application value: The default is binary. It may also be reset to url. The
url value may be used to specify a value outside of this MIME entity.

Type special notes: The type might be MAY include the type parameter "TYPE" to
specify the location of a publicly accessible directory, such as an Internet
whitepages, where up-to-date information can audio format type. The TYPE parameter values MUST be found about one
of the
individual specified by IANA registered audio formats. In addition, a vCard. non-standard
audio format MAY be specified.

Type example:

URL:http://www.swbyps.restaurant.french/~chezchic.html

1.9.5 UID
SOUND;TYPE=BASIC;VALUE=URL:CID://<JOHNQPUBLIC.part8.
19960229T080000.xyzMail@host1.com>

4.7.4 URL Type Definition

To: ietf-mime-direct@umich.edu

Subject: Registration of application/directory MIME type UID ietf-mime-directory@umich.edu

Dawson & Howes [Page 16] Expires June September 1997

vCard Application/Directory Content Type

Type name: UID

Type purpose: To specify a value that represents a globally unique
identifier corresponding to the individual or resource associated
with the vCard object.

Type encoding: text.

Type special notes: The type value can be used as a mechanism to
relate different vCard objects. Some examples of valid forms of
unique identifiers would include ISO 9070 formal public identifiers
(FPI) as defined in [ISO 9070], X.500 distinguished names, machine-
generated random numbers with a statistically high likelihood of
being globally unique, and Uniform Resource Locators (URL). If an URL
is specified, it is suggested that the URL reference a service which
will produce an updated version of the vCard associated with the
individual or resource.

The type may include the MIME Directory Profile

Subject: Registration of application/directory MIME type parameter _TYPE_ to URL

Type name: URL

Type purpose: To specify a uniform resource locator associated with
the format
of the unique identifier. The TYPE parameter values may include
_ISO9070_ to indicate the ISO 9070 FPI type of unique identifier,
_X500_ to indicate object that the X.500 DSN type of unique identifier, _MACH_ to
indicate a machine generated random number type of unique identifier,
and _URL_ to indicate a Uniform Resource Locator type of unique
identifier. vCard refers to.

Type encoding: 8bit.

Type value: url.

Type example:

UID;TYPE=MACH:19950401-080045-40000F192713-0052

1.9.6 Version

URL:http://www.swbyps.restaurant.french/~chezchic.html

4.7.5 UID Type Definition

To: ietf-mime-direct@umich.edu ietf-mime-directory@umich.edu

Subject: Registration of application/directory MIME type UID

Type name: UID

Type purpose: To specify a value that represents a globally unique
identifier corresponding to the individual or resource associated
with the vCard object. vCard.

Type encoding: 8bit.

Type value: text.

Type special notes: The type value can be is used as a mechanism to
relate different vCard objects. Some examples of valid forms of
unique identifiers would include ISO 9070 formal public identifiers
(FPI) as defined in [ISO 9070], X.500 distinguished names, machine-
generated random numbers with a statistically high likelihood of
being globally unique, and Uniform Resource Locators (URL). If an URL
is specified, it is suggested that the URL reference a service which
will produce an updated version of uniquely identify the vCard associated with object
that the
individual or resource.

Dawson & Howes [Page 17] Expires June 1997 vCard Application/Directory Content Type represents.

The type may include the type parameter _TYPE_ "TYPE" to specify the format
of the unique identifier. The TYPE parameter values value may include
_ISO9070_ to indicate the ISO 9070 FPI type be any IANA
registered identifier format. The value may also be a non-standard
format.

Type example:

UID:19950401-080045-40000F192713-0052

4.7.6 Version Type Definition

To: ietf-mime-directory@umich.edu

Subject: Registration of unique identifier,
_X500_ to indicate the X.500 DSN application/directory MIME type VERSION

Type name: UID

Type purpose: To specify the version of unique identifier, _MACH_ the vCard specification used
to
indicate a machine generated random number type of unique identifier,
and _URL_ format this vCard.

Dawson & Howes [Page 17] Expires September 1997

vCard MIME Directory Profile

Type encoding: 8bit.

Type value: text.

Type special notes: The value must be "2.1" if the vCard version
corresponds to indicate a Uniform Resource Locator type of unique
identifier. the [VCARD] specification.

Type example:

UID;TYPE=MACH:19950401-080045-40000F192713-0052

1.10

VERSION: 2.1

4.8 Security Profile Types

These profile types are concerned with the security of communication pathways
or access to the vCard object.

1.10.1 vCard.

4.8.1 KEY Type Definition

To: ietf-mime-direct@umich.edu ietf-mime-directory@umich.edu

Subject: Registration of application/directory MIME type VERSION

Type name: VERSION KEY

Type purpose: To specify an identifier corresponding to the highest
version of the vCard profile used in creating vCard profile used in creating the vCard.

To specify a public key or authentication certificate associated with
the object that the vCard object. represents.

Type encoding: The default is 8bit. May also be reset to base64.

Type value: The default is text. May also be reset to binary.

Type special notes: The type value corresponding may also include the type parameter TYPE
to this version of specify the vCard profile MUST be _2.1_.

1.11 public key or authentication certificate format. The
parameter type may specify any IANA registered public key or
authentication certificate format. The parameter type may also
specify a non-standard format.

4.9 Extended Profile Types

The profile types defined by this document can be extended with private types
using the non-standard, private type mechanism values defined in [MIME].
Private [RFC-2045]. Non-
standard, private types with a name starting with _X-_ "X-" may be defined
bilaterally between two cooperating agents without outside
registration or standardization.

5. Formal Grammar

The following modified Backus-Naur Notation (BNF) formal grammar is provided to assist developers in
building parsers for the vCard.

Dawson & Howes [Page 18] Expires September 1997

vCard MIME Directory Profile

This syntax is written according to the form described in RFC 822,
but it references just this small subset of RFC 822 literals:

CR = <ASCII CR, carriage return> ; (15, 13.)
LF = <ASCII LF, linefeed> ; (12,10.)
CRLF = CR LF
SPACE = <ASCII SP, space> ; (40,32.)
HTAB = <ASCII HT, horizontal-tab> ; (11,9.)

Dawson & Howes [Page 18] Expires June 1997

vCard Application/Directory Content Type

All literal property names are valid as upper, lower, or mixed case.

ws = 1*(SPACE / HTAB)
; _whitespace,_ "whitespace," one or more spaces or tabs

wsls = 1*(SPACE / HTAB / CRLF)
; whitespace with line separators

word = <any printable 7bit us-ascii except []=:., >

groups = groups _._ "." word
/ word

vcard_entity

vcard"entity = 1*([wsls] vcard [wsls])

vcard = _BEGIN_ "BEGIN" [ws] _:_ ":" [ws] _VCARD_ "VCARD" [ws] 1*CRLF
items *CRLF
_END_
"END" ws] [ ":" [ws] _:_ [ws] _VCARD_ "VCARD" 1*CRLF

items = items *CRLF item
/ item
; these may be _folded_ "folded"

item = [groups _._] "."] name
[params] _:_ ":" value CRLF
/ [groups _._] _ADR_ "."] "ADR"
[params] _:_ ":" addressparts CRLF
/ [groups _._] _ORG_ "."] "ORG"
[params] _:_ ":" orgparts CRLF
/ [groups _._] _N_ "."] "N"
[params] _:_ ":" nameparts CRLF
/ [groups _._] _AGENT_ "."] "AGENT"
[params] _:_ ":" vcard CRLF
; these may be _folded_ "folded"

name = _LOGO_ "LOGO" / "PHOTO" / "LABEL" / "FN" / _PHOTO_ "TITLE"
/ _LABEL_ "SOUND" / _FN_ VERSION " " / _TITLE_ "TEL" / _SOUND_ "EMAIL" / _VERSION_ "TZ"
/ _TEL_ "GEO" / _EMAIL_ "NOTE" / _TZ_ "SOURCE" / _GEO_ "NAME" / _NOTE_ "PROFILE"
/ _URL_ "URL" / _BDAY_ " " BDAY / _ROLE_ "ROLE" / _REV_ "REV" / _UID_ "UID" / _KEY_ "KEY"
/ _MAILER_ "MAILER" / _X-_ "X-" word
; these may be _folded_ "folded"

value = 7bit / quoted-printable / base64

7bit = <7bit us-ascii printable chars, excluding CR LF>

Dawson & Howes [Page 19] Expires September 1997

vCard MIME Directory Profile

8bit = <MIME RFC 1521 2045 8-bit text>

quoted-printable = <MIME RFC 1521 2045 quoted-printable text>

base64 = <MIME RFC 1521 2045 base64 text>
; the end of the text is marked with two CRLF sequences
; this results in one blank line before the start of the next
; property

Dawson & Howes [Page 19] Expires June 1997

vCard Application/Directory Content Type

params = _;_ ";" [ws] paramlist

paramlist = paramlist [ws] _;_ ";" [ws] param
/ param

param = _TYPE_ "TYPE" [ws] _=_ "=" [ws] ptypeval
/ _VALUE_ "VALUE" [ws] _=_ "=" [ws] pvalueval
/ _ENCODING_ "ENCODING" [ws] _=_ "=" [ws] pencodingval
/ _CHARSET_ "CHARSET" [ws] _=_ "=" [ws] charsetval
/ _LANGUAGE_ "LANGUAGE" [ws] _=_ "=" [ws] langval
/ _X-_ "X-" word [ws] _=_ "=" [ws] word
/ knowntype

ptypeval = knowntype / _X-_ "X-" word

pvalueval = _INLINE_ "URL" / "TEXT" / "DATE" / "TIME" / "DATE-TIME"
/ "INTEGER" / _URL_ "BOOLEAN" / _CONTENT-ID_ "FLOAT" / _CID_ "BINARY" / _X-_
/ "VCARD" / "PHONE-NUMBER" / "UTC-OFFSET" / "X-" word

pencodingval = _7BIT_ "7BIT / 8BIT
_ _ " "8BIT" / _QUOTED-PRINTABLE_ "QUOTED-PRINTABLE" / _BASE64_ "BASE64"
/ _X-_ "X-" word

charsetval = <a character set string text value as defined in Section 7.1 3
of RFC 1521> 2047>

langval = <a language string as defined in RFC 1766>

addressparts = 0*6(strnosemi _;_) ";") strnosemi
; PO Box, Extended Addr, Street, Locality, Region, Postal Code,
; Country Name

orgparts = *(strnosemi _;_) ";") strnosemi
; First is Organization Name, remainder are Organization Units.

nameparts = 0*4(strnosemi _;_) ";") strnosemi
; Family, Given, Middle, Prefix, Suffix.
; Example:Public;John;Q.;Reverend Dr.;III, Esq.

strnosemi = *(*nonsemi (_\;_ ("\;" / _\_ "\" CRLF)) *nonsemi
; To include a semicolon in this string, it must be escaped
; with a _\_ "\" character.

nonsemi = <any non-control ASCII except _;_> ";">

Dawson & Howes [Page 20] Expires September 1997

vCard MIME Directory Profile

knowntype = _DOM_ "DOM" / _INTL_ " " / _POSTAL_ "POSTAL" INTL / _PARCEL_ "PARCEL" / _HOME_ "HOME" / _WORK_ "WORK"
/ _PREF_ "PREF" / _VOICE_ " " VOICE / _FAX_ "FAX" / _MSG_ "MSG" / _CELL_ "CELL" / _PAGER_ "PAGER"
/ _BBS_ "BBS" / _MODEM_ "MODEM" / _CAR_ "CAR" / _ISDN_ "ISDN" / _VIDEO_ "VIDEO"
/ _INTERNET_ "INTERNET" / _GIF_ "GIF" / _JPEG_ "JPEG" / _PCM_ "PCM" / _WAVE_ "WAVE"
/ _X509_ "X509" / _PGP_

2.1 "PGP"

5.1 Acknowledgements

The authors would like to thank the participants in the IETF ASID
working group, in addition to the following individuals, Roland
Alden, Stephen Bartlett, Alec Dun, Daniel Klaussen, Chris Newman,
Michelle Watkins; who provided numerous suggestions and comments on
this work.

Dawson & Howes [Page 20] Expires June 1997

vCard Application/Directory Content Type

2.2

5.2 Authors's Addresses

BEGIN:vCard
FN:Frank Dawson
ORG:IBM Corporation;Network Software Division
ADR;TYPE=WORK,POSTAL,PARCEL:APNA/CC-303/Bldg. 002;
3039 Cornwallis Rd.;Research Triangle Park;
NC;27709;U.S.A.
TEL;TYPE=VOICE,MSG,WORK: +1 (919) 254-5861
TEL;TYPE=FAX,WORK: +1-919-543-6822
EMAIL;TYPE=INTERNET;PREF:fdawson@raleigh.ibm.com
EMAIL;TYPE=INTERNET,PREF:fdawson@raleigh.ibm.com
EMAIL;TYPE=INTERNET:fdawson@earthlink.net
URL:http://home.earthlink.net/~fdawson
END:vCard

BEGIN:vCard
FN:Tim Howes
ORG:Netscape Communications Corp.
ADR;TYPE=WORK: 501 E. Middlefield Rd.;Mountain View;
CA; 94043;U.S.A.
TEL;TYPE=VOICE,MSG,WORK:+1-415-937-3419
TEL;TYPE=FAX,WORK:+1-415-528-4164
EMAIL;TYPE=INTERNET:howes@netscape.com
END:vCard

2.3

5.3 References

The following documents are referenced by this work.

[ISO 639] ISO 639:1988 - Code for the representation of names of
languages - The International Organization for Standardization, April
1988.

[ISO 3166] ISO 3166:1993 - Codes for the representation of names of
countries - The International Organization for Standardization,
December 1993.

[ISO 8601] ISO 8601:1988 - Data elements and interchange formats -
Information interchange - Representation of dates and times - The
International Organization for Standardization, June, 1988.

Dawson & Howes [Page 21] Expires September 1997

vCard MIME Directory Profile

[ISO 8601 TC] ISO 8601, Technical Corrigendum 1 - Data elements and
interchange formats - Information interchange - Representation of
dates and times - The International Organization for Standardization,
May, 1991.

[ISO 9070] ISO 9070, Information Processing - SGML support facilities
- Registration Procedures for Public Text Owner Identifiers, April,
1991.

[CCITT E.163] Recommendation E.163 - Numbering Plan for The
International Telephone Service, CCITT Blue Book, Fascicle II.2, pp.
128-134, November, 1988.

Dawson & Howes [Page 21] Expires June 1997

vCard Application/Directory Content Type

[CCITT X.121] Recommendation X.121 - International Numbering Plan for
Public Data Networks, CCITT Blue Book, Fascicle VIII.3, pp. 317-332,
November, 1988.

[CCITT X.520] Recommendation X.520 - The Directory - Selected
Attribute Types, November 1988.

[CCITT X.521] Recommendation X.521 - The Directory - Selected Object
Classes, November 1988.

[MIME-DIR] Howes, T., Smith, M., _A "A MIME Content-Type for Directory
Information_, Internet-draft-ietf-asid-mime-direct-03.txt, November,
1996.

[MIME-REG] Freed, N., Postel, J., _Multipurpose Internet Mail
Extensions (MIME) Part Four: Registration Procedures,_ Internet-
Draft draft-ietf-822ext-mime-reg-02.txt, December 1995.
Information", Internet-draft-ietf-asid-mime-direct-05.txt, March,
1997.

[RFC-822] Crocker, D., _Standard "Standard for the Format of ARPA Internet Text
Messages_,
Messages", STD 11, RFC 822, August 1982.

[RFC-1521] Borenstein, N.,

[RFC-2045] Freed, N., _MIME (Multipurpose Borenstein, N., " Multipurpose Internet Mail Extensions)
Extensions (MIME) - Part One: Mechanisms for Specifying and Describing
the Format of Internet Message Bodies_, Bodies", RFC 1521, September 1993.

[RFC-1522]
2045, November 1996.

[RFC-2046] Freed, N., Borenstein, N., " Multipurpose Internet Mail
Extensions (MIME) - Part Two: Media Types", RFC 2046, November 1996.

[RFC-2047] Moore, K., _MIME (Multipurpose "Multipurpose Internet Mail Extensions) Extensions (MIME) -
Part Two: Three: Message Header Extensions for Non-ASCII Text_, Text", RFC 1522,
September 1993. 2047,
November 1996.

[RFC-2048] Freed, N., J. Klensin, J. Postel, "Multipurpose Internet
Mail Extensions (MIME) - Part Four: Registration Procedures", RFC
2048, January 1997.

[RFC-1738] Berners-Lee, T., Masinter, L., McCahill, M., _Uniform "Uniform
Resource Locators (URL)_, (URL)", RFC 1738, December 1994.

[RFC-1766] Alvestrand, H., _Tags "Tags for the Identification of
Languages_,
Languages", March 1995.

[RFC-1872] Levinson, E., _The "The MIME Multipart/Related Content-type,_ Content-type,"
RFC 1872, December 1995.

Dawson & Howes [Page 22] Expires September 1997

vCard MIME Directory Profile

[VCARD] VERSIT Consortium, _vCard "vCard - The Electronic Business Card
Version 2.1_, http://www.versit.com/pdi, 2.1", http://www.versit.com/pdi/vcard-21.txt, September 18,
1996.

Dawson & Howes [Page 22] 23] Expires June September 1997

----