rfc2426.html 82.3 KB

Raw Blame History Permalink


<html xmlns='http://www.w3.org/1999/xhtml'>
<head profile='http://www.w3.org/2003/g/data-view'>
  <title>vCard MIME Directory Profile</title>
  <link rel="transformation"
    href="http://www.w3.org/2002/12/cal/webize2445.xsl"/>
  <style type="text/css">
  dd.Typeexample {   border-style: solid;  border-color: #d0dbe7;  border-width: 0 0 0 .25em;  padding-left: 0.5em;

  </style>
</head>
<body>
<table>
<tr><td>Network Working Group<br />
Request for Comments: 2426<br />
Category: Standards Track<br />
</td>
<td>F. Dawson<br />Lotus Development Corporation<br />T. Howes<br />Netscape Communications</td>
</tr>
<tr><td>&#160;</td><td>September 1998</td></tr>
</table>
<h1>vCard MIME Directory Profile</h1>
<address>
$Revision: 1.2 $ of $Date: 2005/07/22 21:15:57 $
derived from <a href="http://www.ietf.org/rfc/rfc2426.txt">rfc2426.txt</a>
and enhanced
for <a href="http://www.w3.org/2004/01/rdxh/spec">gleaning formal description</a>
using <a href="slurpIcalSpec.py">slurpIcalSpec.py</a>
by <a href="http://www.w3.org/People/Connolly/">Dan Connolly</a>
</address>


<div><h2>Status of this Memo</h2>
<p>
   This document specifies an Internet standards track protocol for the
   Internet community, and requests discussion and suggestions for
   improvements.  Please refer to the current edition of the "Internet
   Official Protocol Standards" (STD 1) for the standardization state
   and status of this protocol.  Distribution of this memo is unlimited.
</p>
</div><div><h2>Copyright Notice</h2>
<p>
   Copyright (C) The Internet Society (1998).  All Rights Reserved.
</p>
</div><div><h2>Abstract</h2>
<p>
   This memo defines the profile of the MIME Content-Type <a href='#ref_MIME-DIR'>[MIME-DIR]</a> for
   directory information for a white-pages person object, based on a
   vCard electronic business card. The profile definition is independent
   of 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, 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 method for including a <a href='#ref_VCARD'>[VCARD]</a> representation of a
   white-pages directory entry within the MIME Content-Type defined by
   the <a href='#ref_MIME-DIR'>[MIME-DIR]</a> document.
</p>
<p>
   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY" and "OPTIONAL" in this
   document are to be interpreted as described in <a href='#ref_RFC_2119'>[RFC 2119]</a>.
</p>
</div><div><h2>Table of Contents</h2>
<ul type='none'>
<li><a href='#sec'> Overview</a></li>
<li><a href='#sec1.'>1. THE VCARD MIME DIRECTORY PROFILE REGISTRATION</a></li>
<li><a href='#sec2.'>2. MIME DIRECTORY FEATURES</a></li>
<li><a href='#sec2.1'>2.1 PREDEFINED TYPE USAGE </a></li>
<li><a href='#sec2.1.1'>2.1.1 BEGIN and END Type </a></li>
<li><a href='#sec2.1.2'>2.1.2 NAME Type </a></li>
<li><a href='#sec2.1.3'>2.1.3 PROFILE Type </a></li>
<li><a href='#sec2.1.4'>2.1.4 SOURCE Type </a></li>
<li><a href='#sec2.2'>2.2 PREDEFINED TYPE PARAMETER USAGE </a></li>
<li><a href='#sec2.3'>2.3 PREDEFINED VALUE TYPE USAGE </a></li>
<li><a href='#sec2.4'>2.4 EXTENSIONS TO THE PREDEFINED VALUE TYPES </a></li>
<li><a href='#sec2.4.1'>2.4.1 BINARY </a></li>
<li><a href='#sec2.4.2'>2.4.2 VCARD </a></li>
<li><a href='#sec2.4.3'>2.4.3 PHONE-NUMBER </a></li>
<li><a href='#sec2.4.4'>2.4.4 UTC-OFFSET </a></li>
<li><a href='#sec2.5'>2.5 STRUCTURED TYPE VALUES </a></li>
<li><a href='#sec2.6'>2.6 LINE DELIMITING AND FOLDING </a></li>
<li><a href='#sec3.'>3. VCARD PROFILE FEATURES</a></li>
<li><a href='#sec3.1'>3.1 IDENTIFICATION TYPES </a></li>
<li><a href='#sec3.1.1'>3.1.1 FN Type Definition </a></li>
<li><a href='#sec3.1.2'>3.1.2 N Type Definition </a></li>
<li><a href='#sec3.1.3'>3.1.3 NICKNAME Type Definition </a></li>
<li><a href='#sec3.1.4'>3.1.4 PHOTO Type Definition </a></li>
<li><a href='#sec3.1.5'>3.1.5 BDAY Type Definition </a></li>
<li><a href='#sec3.2'>3.2 DELIVERY ADDRESSING TYPES </a></li>
<li><a href='#sec3.2.1'>3.2.1 ADR Type Definition </a></li>
<li><a href='#sec3.2.2'>3.2.2 LABEL Type Definition </a></li>
<li><a href='#sec3.3'>3.3 TELECOMMUNICATIONS ADDRESSING TYPES </a></li>
<li><a href='#sec3.3.1'>3.3.1 TEL Type Definition </a></li>
<li><a href='#sec3.3.2'>3.3.2 EMAIL Type Definition </a></li>
<li><a href='#sec3.3.3'>3.3.3 MAILER Type Definition </a></li>
<li><a href='#sec3.4'>3.4 GEOGRAPHICAL TYPES </a></li>
<li><a href='#sec3.4.1'>3.4.1 TZ Type Definition </a></li>
<li><a href='#sec3.4.2'>3.4.2 GEO Type Definition </a></li>
<li><a href='#sec3.5'>3.5 ORGANIZATIONAL TYPES </a></li>
<li><a href='#sec3.5.1'>3.5.1 TITLE Type Definition </a></li>
<li><a href='#sec3.5.2'>3.5.2 ROLE Type Definition </a></li>
<li><a href='#sec3.5.3'>3.5.3 LOGO Type Definition </a></li>
<li><a href='#sec3.5.4'>3.5.4 AGENT Type Definition </a></li>
<li><a href='#sec3.5.5'>3.5.5 ORG Type Definition </a></li>
<li><a href='#sec3.6'>3.6 EXPLANATORY TYPES </a></li>
<li><a href='#sec3.6.1'>3.6.1 CATEGORIES Type Definition </a></li>
<li><a href='#sec3.6.2'>3.6.2 NOTE Type Definition </a></li>
<li><a href='#sec3.6.3'>3.6.3 PRODID Type Definition </a></li>
<li><a href='#sec3.6.4'>3.6.4 REV Type Definition </a></li>
<li><a href='#sec3.6.5'>3.6.5 SORT-STRING Type Definition </a></li>
<li><a href='#sec3.6.6'>3.6.6 SOUND Type Definition </a></li>
<li><a href='#sec3.6.7'>3.6.7 UID Type Definition </a></li>
<li><a href='#sec3.6.8'>3.6.8 URL Type Definition </a></li>
<li><a href='#sec3.6.9'>3.6.9 VERSION Type Definition </a></li>
<li><a href='#sec3.7'>3.7 SECURITY TYPES </a></li>
<li><a href='#sec3.7.1'>3.7.1 CLASS Type Definition </a></li>
<li><a href='#sec3.7.2'>3.7.2 KEY Type Definition </a></li>
<li><a href='#sec3.8'>3.8 EXTENDED TYPES </a></li>
<li><a href='#sec4.'>4. FORMAL GRAMMAR</a></li>
<li><a href='#sec5.'>5. DIFFERENCES FROM VCARD V2</a></li>
<li><a href='#sec6.'>6. ACKNOWLEDGEMENTS</a></li>
<li><a href='#sec7.'>7. AUTHORS' ADDRESSES</a></li>
<li><a href='#sec8.'>8. SECURITY CONSIDERATIONS</a></li>
<li><a href='#sec9.'>9. REFERENCES</a></li>
<li><a href='#sec10.'>10. FULL COPYRIGHT STATEMENT</a></li>
</ul></div><div><h2>Overview</h2>
<p>
   The <a href='#ref_MIME-DIR'>[MIME-DIR]</a> document defines a MIME Content-Type for holding
   different kinds of directory information. The directory information
   can be based on any of a number of directory schemas. This document
   defines a <a href='#ref_MIME-DIR'>[MIME-DIR]</a> usage profile for conveying directory
   information based on one such schema; that of the white-pages type of
   person object.
</p>
<p>
   The schema is based on the attributes for the person object defined
   in the X.520 and X.521 directory services recommendations. The schema
   has augmented the basic attributes defined in the X.500 series
   recommendation in order to provide for an electronic representation
   of the information commonly found on a paper business card. This
   schema was first defined in the <a href='#ref_VCARD'>[VCARD]</a> document. Hence, this <a href='#ref_MIME-DIR'>[MIME-DIR]</a>
    profile is referred to as the vCard MIME Directory Profile.
</p>
<p>
   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.
</p>
<p>
   The vCard MIME Directory Profile 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
</p>
<p>
   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 <a href='#ref_VCARD'>[VCARD]</a>.
</p>
</div><div><h2 id='sec1.'>1. The vCard Mime Directory Profile Registration</h2>
<pre>
   This profile is identified by the following <a href='#ref_MIME-DIR'>[MIME-DIR]</a> registration
   template information. Subsequent sections define the profile
   definition.

   To: ietf-mime-directory@imc.org

   Subject: Registration of text/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 value specifications used: uri, date,
   date-time, float

   New value specifications: This profile places further constraints on
   the <a href='#ref_MIME-DIR'>[MIME-DIR]</a> text value specification. In addition, it adds a
   binary, phone-number, utc-offset and vcard value specifications.

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

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

   New types: FN, N, NICKNAME, PHOTO, BDAY, ADR, LABEL, TEL, EMAIL,
   MAILER, TZ, GEO, TITLE, ROLE, LOGO, AGENT, ORG, CATEGORIES, NOTE,
   PRODID, REV, SORT-STRING, SOUND, URL, UID, VERSION, CLASS, KEY

   New parameters: TYPE

   Profile special notes: The vCard object MUST contain the FN, N and
   VERSION types. The type-grouping feature of <a href='#ref_MIME-DIR'>[MIME-DIR]</a> is supported
   by this profile to group related vCard properties about a directory

   entry. For example, vCard properties describing WORK or HOME related
   characteristics can 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.

</pre>
</div>
<div><h2 id='sec2.'>2. MIME Directory Features</h2>
<pre>
   The vCard MIME Directory Profile makes use of many of the features
   defined by <a href='#ref_MIME-DIR'>[MIME-DIR]</a>. The following sections either clarify or
   extend the content-type definition of <a href='#ref_MIME-DIR'>[MIME-DIR]</a>.

</pre>
</div>
<div><h2 id='sec2.1'>2.1 Predefined Type Usage</h2>
<pre>
   The vCard MIME Directory Profile uses the following predefined types
   from <a href='#ref_MIME-DIR'>[MIME-DIR]</a>.

</pre>
</div>
<div><h2 id='sec2.1.1'>2.1.1 BEGIN and END Type</h2>
<pre>
   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
   of "VCARD".

</pre>
</div>
<div><h2 id='sec2.1.2'>2.1.2 NAME Type</h2>
<pre>
   If the NAME type is present, then its value is the displayable,
   presentation text associated with the source for the vCard, as
   specified in the SOURCE type.

</pre>
</div>
<div><h2 id='sec2.1.3'>2.1.3 PROFILE Type</h2>
<pre>
   If the PROFILE type is present, then its value MUST be "VCARD".

</pre>
</div>
<div><h2 id='sec2.1.4'>2.1.4 SOURCE Type</h2>
<pre>
   If the SOURCE type is present, then its value provides information
   how to find the source for the vCard.

</pre>
</div>
<div><h2 id='sec2.2'>2.2 Predefined Type Parameter Usage</h2>
<pre>
   The vCard MIME Directory Profile uses the following predefined type
   parameters as defined by <a href='#ref_MIME-DIR'>[MIME-DIR]</a>.

        - LANGUAGE

        - ENCODING

        - VALUE

</pre>
</div>
<div><h2 id='sec2.3'>2.3 Predefined VALUE Type Usage</h2>
<pre>
   The predefined data type values specified in <a href='#ref_MIME-DIR'>[MIME-DIR]</a> MUST NOT be
   repeated in COMMA separated value lists except within the N,
   NICKNAME, ADR and CATEGORIES value types.

   The text value type defined in <a href='#ref_MIME-DIR'>[MIME-DIR]</a> is further restricted such
   that any SEMI-COLON character (ASCII decimal 59) in the value MUST be
   escaped with the BACKSLASH character (ASCII decimal 92).

</pre>
</div>
<div><h2 id='sec2.4'>2.4 Extensions To The Predefined VALUE Types</h2>
<pre>
   The predefined data type values specified in <a href='#ref_MIME-DIR'>[MIME-DIR]</a> have been
   extended by the vCard profile to include a number of value types that
   are specific to this profile.

</pre>
</div>
<div><h2 id='sec2.4.1'>2.4.1 BINARY</h2>
<pre>
   The "binary" value type specifies that the type value is inline,
   encoded binary data. This value type can be specified in the PHOTO,
   LOGO, SOUND, and KEY types.

   If inline encoded binary data is specified, the ENCODING type
   parameter MUST be used to specify the encoding format. The binary
   data MUST be encoded using the "B" encoding format. Long lines of
   encoded binary data SHOULD BE folded to 75 characters using the
   folding method defined in <a href='#ref_MIME-DIR'>[MIME-DIR]</a>.

   The value type is defined by the following notation:

   binary = &lt;A "B" binary encoded string as defined by <a href='#ref_RFC_2047'>[RFC 2047]</a>.>

</pre>
</div>
<div><h2 id='sec2.4.2'>2.4.2 VCARD</h2>
<pre>
   The "vcard" value type specifies that the type value is another
   vCard. This value type can be specified in the AGENT type. The value
   type is defined by this specification. Since each of the type

   declarations with in the vcard value type are being specified within
   a text value themselves, they MUST be terminated with the backslash
   escape sequence "\n" or "\N", instead of the normal newline character
   sequence CRLF. In addition, any COMMA character (ASCII decimal 44),
   SEMI-COLON character (ASCII decimal 59) and COLON character (ASCII
   decimal 58) MUST be escaped with the BACKSLASH character (ASCII
   decimal 92). For example, with the AGENT type a value would be
   specified as:

        AGENT:BEGIN:VCARD\nFN:Joe Friday\nTEL:+1-919-555-7878\n
         TITLE:Area Administrator\, Assistant\n EMAIL\;TYPE=INTERN\n
         ET:jfriday@host.com\nEND:VCARD\n

</pre>
</div>
<div><h2 id='sec2.4.3'>2.4.3 PHONE-NUMBER</h2>
<pre>
   The "phone-number" value type specifies that the type value is a
   telephone number. This value type can be specified in the TEL type.
   The value type is a text value that has the special semantics of a
   telephone number as defined in <a href='#ref_CCITT_E.163'>[CCITT E.163]</a> and <a href='#ref_CCITT_X.121'>[CCITT X.121]</a>.

</pre>
</div>
<div><h2 id='sec2.4.4'>2.4.4 UTC-OFFSET</h2>
<pre>
   The "utc-offset" value type specifies that the type value is a signed
   offset from UTC. This value type can be specified in the TZ type.

   The value type is an offset from Coordinated Universal Time (UTC). It
   is specified as a positive or negative difference in units of hours
   and minutes (e.g., +hh:mm). The time is specified as a 24-hour clock.
   Hour values are from 00 to 23, and minute values are from 00 to 59.
   Hour and minutes are 2-digits with high order zeroes required to
   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
   separator of the hour and minute text fields.

   The value is defined by the following notation:

        time-hour       = 2DIGIT        ;00-23
        time-minute     = 2DIGIT        ;00-59
        utc-offset      = ("+" / "-") time-hour ":" time-minute

</pre>
</div>
<div><h2 id='sec2.5'>2.5 Structured Type Values</h2>
<pre>
   Compound type 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 (ASCII decimal 92).

   Lists of values are delimited by a list delimiter, specified by the
   COMMA character (ASCII decimal 44). A COMMA character in a value MUST
   be escaped with a BACKSLASH character (ASCII decimal 92).

   This profile supports the type grouping mechanism defined in MIME-
   DIR]. Grouping of related types is a useful technique to communicate
   common semantics concerning the properties of a vCard.

</pre>
</div>
<div><h2 id='sec2.6'>2.6 Line Delimiting and Folding</h2>
<pre>
   This profile supports the same line delimiting and folding methods
   defined in <a href='#ref_MIME-DIR'>[MIME-DIR]</a>. Specifically, when parsing a content line,
   folded lines must first be unfolded according to the unfolding
   procedure described in <a href='#ref_MIME-DIR'>[MIME-DIR]</a>. After generating a content line,
   lines longer than 75 characters SHOULD be folded according to the
   folding procedure described in MIME DIR].

   Folding is done after any content encoding of a type value. Unfolding
   is done before any decoding of a type value in a content line.

</pre>
</div>
<div><h2 id='sec3.'>3. vCard Profile Features</h2>
<pre>
   The vCard MIME Directory Profile Type contains directory information,
   typically pertaining to a single directory entry. The information is
   described using an attribute schema that is tailored for capturing
   personal contact information. The vCard can include attributes that
   describe identification, delivery addressing, telecommunications
   addressing, geographical, organizational, general explanatory and
   security and access information about the particular object
   associated with the vCard.

</pre>
</div>
<div><h2 id='sec3.1'>3.1 Identification Types</h2>
<pre>
   These types are used in the vCard profile to capture information
   associated with the identification and naming of the person or
   resource associated with the vCard.

</pre>
</div>
<div><h2 id='sec3.1.1'>3.1.1 FN Type Definition</h2>
<dl>
<dt>To</dt>
<dd class='To'><pre>    ietf-mime-directory@imc.org

</pre>
</dd>
<dt>Subject</dt>
<dd class='Subject'><pre>    Registration of text/directory MIME type FN

</pre>
</dd>
<dt id='Type_FN'>Type name</dt>
<dd class='Typename'><pre>   FN

</pre>
</dd>
<dt>Type purpose</dt>
<dd class='Typepurpose'><pre>    To specify the formatted text corresponding to the name
   of the object the vCard represents.

</pre>
</dd>
<dt>Type encoding</dt>
<dd class='Typeencoding'><pre>    8bit

</pre>
</dd>
<dt>Type value</dt>
<dd class='Typevalue'><pre>    A single text value.

</pre>
</dd>
<dt>Type special notes</dt>
<dd class='Typespecialnotes'><pre>    This type is based on the semantics of the X.520
   Common Name attribute. The property MUST be present in the vCard
   object.

</pre>
</dd>
<dt>Type example</dt>
<dd class='Typeexample'><pre>

        FN:Mr. John Q. Public\, Esq.

</pre>
</dd>
</dl>
</div>
<div><h2 id='sec3.1.2'>3.1.2 N Type Definition</h2>
<dl>
<dt>To</dt>
<dd class='To'><pre>    ietf-mime-directory@imc.org

</pre>
</dd>
<dt>Subject</dt>
<dd class='Subject'><pre>    Registration of text/directory MIME type N

</pre>
</dd>
<dt id='Type_N'>Type name</dt>
<dd class='Typename'><pre>    N

</pre>
</dd>
<dt>Type purpose</dt>
<dd class='Typepurpose'><pre>    To specify the components of the name of the object the
   vCard represents.

</pre>
</dd>
<dt>Type encoding</dt>
<dd class='Typeencoding'><pre>    8bit

</pre>
</dd>
<dt>Type value</dt>
<dd class='Typevalue'><pre>    A single structured text value. Each component can have
   multiple values.

   Type special note: The structured type value corresponds, in
   sequence, to the Family Name, Given Name, Additional Names, Honorific
   Prefixes, and Honorific Suffixes. The text components are separated
   by the SEMI-COLON character (ASCII decimal 59). Individual text
   components can include multiple text values (e.g., multiple
   Additional Names) separated by the COMMA character (ASCII decimal
   44). This type is based on the semantics of the X.520 individual name
   attributes. The property MUST be present in the vCard object.

</pre>
</dd>
<dt>Type example</dt>
<dd class='Typeexample'><pre>

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

        N:Stevenson;John;Philip,Paul;Dr.;Jr.,M.D.,A.C.P.

</pre>
</dd>
</dl>
</div>
<div><h2 id='sec3.1.3'>3.1.3 NICKNAME Type Definition</h2>
<dl>
<dt>To</dt>
<dd class='To'><pre>    ietf-mime-directory@imc.org

</pre>
</dd>
<dt>Subject</dt>
<dd class='Subject'><pre>    Registration of text/directory MIME type NICKNAME

</pre>
</dd>
<dt id='Type_NICKNAME'>Type name</dt>
<dd class='Typename'><pre>    NICKNAME

</pre>
</dd>
<dt>Type purpose</dt>
<dd class='Typepurpose'><pre>    To specify the text corresponding to the nickname of
   the object the vCard represents.

</pre>
</dd>
<dt>Type encoding</dt>
<dd class='Typeencoding'><pre>    8bit

</pre>
</dd>
<dt>Type value</dt>
<dd class='Typevalue'><pre>    One or more text values separated by a COMMA character
   (ASCII decimal 44).

   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.
   It can also be used to specify a familiar form of a proper name
   specified by the FN or N types.

</pre>
</dd>
<dt>Type example</dt>
<dd class='Typeexample'><pre>

        NICKNAME:Robbie

        NICKNAME:Jim,Jimmie

</pre>
</dd>
</dl>
</div>
<div><h2 id='sec3.1.4'>3.1.4 PHOTO Type Definition</h2>
<dl>
<dt>To</dt>
<dd class='To'><pre>    ietf-mime-directory@imc.org

</pre>
</dd>
<dt>Subject</dt>
<dd class='Subject'><pre>    Registration of text/directory MIME type PHOTO

</pre>
</dd>
<dt id='Type_PHOTO'>Type name</dt>
<dd class='Typename'><pre>    PHOTO

</pre>
</dd>
<dt>Type purpose</dt>
<dd class='Typepurpose'><pre>    To specify an image or photograph information that
   annotates some aspect of the object the vCard represents.

</pre>
</dd>
<dt>Type encoding</dt>
<dd class='Typeencoding'><pre>    The encoding MUST be reset to "b" using the ENCODING
   parameter in order to specify inline, encoded binary data. If the
   value is referenced by a URI value, then the default encoding of 8bit
   is used and no explicit ENCODING parameter is needed.

</pre>
</dd>
<dt>Type value</dt>
<dd class='Typevalue'><pre>    A single value. The default is binary value. It can also
   be reset to uri value. The uri value can be used to specify a value
   outside of this MIME entity.

</pre>
</dd>
<dt>Type special notes</dt>
<dd class='Typespecialnotes'><pre>    The type can include the type parameter "TYPE" to
   specify the graphic image format type. The TYPE parameter values MUST
   be one of the IANA registered image formats or a non-standard image
   format.

</pre>
</dd>
<dt>Type example</dt>
<dd class='Typeexample'><pre>

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


        PHOTO;ENCODING=b;TYPE=JPEG:MIICajCCAdOgAwIBAgICBEUwDQYJKoZIhvcN
         AQEEBQAwdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05ldHNjYXBlIENvbW11bm
         ljYXRpb25zIENvcnBvcmF0aW9uMRwwGgYDVQQLExNJbmZvcm1hdGlvbiBTeXN0
         &lt;...remainder of "B" encoded binary data...>

</pre>
</dd>
</dl>
</div>
<div><h2 id='sec3.1.5'>3.1.5 BDAY Type Definition</h2>
<dl>
<dt>To</dt>
<dd class='To'><pre>    ietf-mime-directory@imc.org

</pre>
</dd>
<dt>Subject</dt>
<dd class='Subject'><pre>    Registration of text/directory MIME type BDAY

</pre>
</dd>
<dt id='Type_BDAY'>Type name</dt>
<dd class='Typename'><pre>    BDAY

</pre>
</dd>
<dt>Type purpose</dt>
<dd class='Typepurpose'><pre>    To specify the birth date of the object the vCard
   represents.

</pre>
</dd>
<dt>Type encoding</dt>
<dd class='Typeencoding'><pre>    8bit

</pre>
</dd>
<dt>Type value</dt>
<dd class='Typevalue'><pre>    The default is a single date value. It can also be reset
   to a single date-time value.

   Type examples:

        BDAY:1996-04-15

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

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

</pre>
</dd>
</dl>
</div>
<div><h2 id='sec3.2'>3.2 Delivery Addressing Types</h2>
<pre>
   These types are concerned with information related to the delivery
   addressing or label for the vCard object.

</pre>
</div>
<div><h2 id='sec3.2.1'>3.2.1 ADR Type Definition</h2>
<dl>
<dt>To</dt>
<dd class='To'><pre>    ietf-mime-directory@imc.org

</pre>
</dd>
<dt>Subject</dt>
<dd class='Subject'><pre>    Registration of text/directory MIME type ADR

</pre>
</dd>
<dt id='Type_ADR'>Type name</dt>
<dd class='Typename'><pre>    ADR

</pre>
</dd>
<dt>Type purpose</dt>
<dd class='Typepurpose'><pre>    To specify the components of the delivery address for
   the vCard object.

</pre>
</dd>
<dt>Type encoding</dt>
<dd class='Typeencoding'><pre>    8bit

</pre>
</dd>
<dt>Type value</dt>
<dd class='Typevalue'><pre>    A single structured text value, separated by the
   SEMI-COLON character (ASCII decimal 59).

</pre>
</dd>
<dt>Type special notes</dt>
<dd class='Typespecialnotes'><pre>    The structured type value consists of a sequence
   of address components. The component values MUST be specified in
   their corresponding position. The structured type value corresponds,
   in sequence, to the post office box; the extended address; the street
   address; the locality (e.g., city); the region (e.g., state or
   province); the postal code; the country name. When a component value
   is missing, the associated component separator MUST still be
   specified.

   The text components are separated by the SEMI-COLON character (ASCII
   decimal 59). Where it makes semantic sense, individual text
   components can include multiple text values (e.g., a "street"
   component with multiple lines) separated by the COMMA character
   (ASCII decimal 44).

   The type can include the type parameter "TYPE" to specify the
   delivery address type. The TYPE parameter values can include "dom" to
   indicate a domestic delivery address; "intl" to indicate an
   international delivery address; "postal" to indicate a postal
   delivery address; "parcel" to indicate a parcel delivery address;
   "home" to indicate a delivery address for a residence; "work" to
   indicate delivery address for a place of work; and "pref" to indicate
   the preferred delivery address when more than one address is
   specified. These type parameter values can be specified as a
   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
   X.520 geographical and postal addressing attributes. The default is
   "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" to
   specify a domestic delivery address for postal delivery to a
   residence that is also used for work.

</pre>
</dd>
<dt>Type example</dt>
<dd class='Typeexample'><pre>    In this example the post office box and the extended
   address are absent.

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

</pre>
</dd>
</dl>
</div>
<div><h2 id='sec3.2.2'>3.2.2 LABEL Type Definition</h2>
<dl>
<dt>To</dt>
<dd class='To'><pre>    ietf-mime-directory@imc.org

</pre>
</dd>
<dt>Subject</dt>
<dd class='Subject'><pre>    Registration of text/directory MIME type LABEL

</pre>
</dd>
<dt id='Type_LABEL'>Type name</dt>
<dd class='Typename'><pre>    LABEL

</pre>
</dd>
<dt>Type purpose</dt>
<dd class='Typepurpose'><pre>    To specify the formatted text corresponding to delivery
   address of the object the vCard represents.

</pre>
</dd>
<dt>Type encoding</dt>
<dd class='Typeencoding'><pre>    8bit

</pre>
</dd>
<dt>Type value</dt>
<dd class='Typevalue'><pre>    A single text value.

</pre>
</dd>
<dt>Type special notes</dt>
<dd class='Typespecialnotes'><pre>    The type value is formatted text that can be used
   to present a delivery address label for the vCard object. The type
   can include the type parameter "TYPE" to specify delivery label type.
   The TYPE parameter values can include "dom" to indicate a domestic
   delivery label; "intl" to indicate an international delivery label;
   "postal" to indicate a postal delivery label; "parcel" to indicate a
   parcel delivery label; "home" to indicate a delivery label for a
   residence; "work" to indicate delivery label for a place of work; and
   "pref" to indicate the preferred delivery label when more than one
   label is specified. These type parameter values can be specified as a
   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
   X.520 geographical and postal addressing attributes. The default is
   "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" to
   specify an international delivery label for both postal and parcel
   delivery to a residential location.

</pre>
</dd>
<dt>Type example</dt>
<dd class='Typeexample'><pre>    A multi-line address label.

        LABEL;TYPE=dom,home,postal,parcel:Mr.John Q. Public\, Esq.\n
         Mail Drop: TNE QB\n123 Main Street\nAny Town\, CA  91921-1234
         \nU.S.A.

</pre>
</dd>
</dl>
</div>
<div><h2 id='sec3.3'>3.3 Telecommunications Addressing Types</h2>
<pre>
   These types are concerned with information associated with the
   telecommunications addressing of the object the vCard represents.

</pre>
</div>
<div><h2 id='sec3.3.1'>3.3.1 TEL Type Definition</h2>
<dl>
<dt>To</dt>
<dd class='To'><pre>    ietf-mime-directory@imc.org

</pre>
</dd>
<dt>Subject</dt>
<dd class='Subject'><pre>    Registration of text/directory MIME type TEL

</pre>
</dd>
<dt id='Type_TEL'>Type name</dt>
<dd class='Typename'><pre>    TEL

</pre>
</dd>
<dt>Type purpose</dt>
<dd class='Typepurpose'><pre>    To specify the telephone number for telephony
   communication with the object the vCard represents.

</pre>
</dd>
<dt>Type encoding</dt>
<dd class='Typeencoding'><pre>    8bit

</pre>
</dd>
<dt>Type value</dt>
<dd class='Typevalue'><pre>    A single phone-number value.

</pre>
</dd>
<dt>Type special notes</dt>
<dd class='Typespecialnotes'><pre>    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 can include the type parameter "TYPE" to specify intended
   use for the telephone number. The TYPE parameter values can include:
   "home" to indicate a telephone number associated with a residence,
   "msg" to indicate the telephone number has voice messaging support,
   "work" to indicate a telephone number associated with a place of
   work, "pref" to indicate a preferred-use telephone number, "voice" to
   indicate a voice telephone number, "fax" to indicate a facsimile
   telephone number, "cell" to indicate a cellular telephone number,
   "video" to indicate a video conferencing telephone number, "pager" to
   indicate a paging device telephone number, "bbs" to indicate a
   bulletin board system telephone number, "modem" to indicate a MODEM
   connected telephone number, "car" to indicate a car-phone telephone
   number, "isdn" to indicate an ISDN service telephone number, "pcs" to
   indicate a personal communication services telephone number. The
   default type is "voice". These type parameter values can be specified
   as a parameter list (i.e., "TYPE=work;TYPE=voice") or as a value list
   (i.e., "TYPE=work,voice"). The default can be overridden to another
   set of values by specifying one or more alternate values. For
   example, the default TYPE of "voice" can be reset to a WORK and HOME,
   VOICE and FAX telephone number by the value list
   "TYPE=work,home,voice,fax".

</pre>
</dd>
<dt>Type example</dt>
<dd class='Typeexample'><pre>

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

</pre>
</dd>
</dl>
</div>
<div><h2 id='sec3.3.2'>3.3.2 EMAIL Type Definition</h2>
<dl>
<dt>To</dt>
<dd class='To'><pre>    ietf-mime-directory@imc.org

</pre>
</dd>
<dt>Subject</dt>
<dd class='Subject'><pre>    Registration of text/directory MIME type EMAIL

</pre>
</dd>
<dt id='Type_EMAIL'>Type name</dt>
<dd class='Typename'><pre>    EMAIL

</pre>
</dd>
<dt>Type purpose</dt>
<dd class='Typepurpose'><pre>    To specify the electronic mail address for
   communication with the object the vCard represents.

</pre>
</dd>
<dt>Type encoding</dt>
<dd class='Typeencoding'><pre>    8bit

</pre>
</dd>
<dt>Type value</dt>
<dd class='Typevalue'><pre>    A single text value.

</pre>
</dd>
<dt>Type special notes</dt>
<dd class='Typespecialnotes'><pre>    The type can include the type parameter "TYPE" to
   specify the format or preference of the electronic mail address. The
   TYPE parameter values can include: "internet" to indicate an Internet
   addressing type, "x400" to indicate a X.400 addressing type or "pref"
   to indicate a preferred-use email address when more than one is
   specified. Another IANA registered address type can also be
   specified. The default email type is "internet". A non-standard value
   can also be specified.

</pre>
</dd>
<dt>Type example</dt>
<dd class='Typeexample'><pre>

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

        EMAIL;TYPE=internet:jdoe@isp.net

        EMAIL;TYPE=internet,pref:jane_doe@abc.com

</pre>
</dd>
</dl>
</div>
<div><h2 id='sec3.3.3'>3.3.3 MAILER Type Definition</h2>
<dl>
<dt>To</dt>
<dd class='To'><pre>    ietf-mime-directory@imc.org

</pre>
</dd>
<dt>Subject</dt>
<dd class='Subject'><pre>    Registration of text/directory MIME type MAILER

</pre>
</dd>
<dt id='Type_MAILER'>Type name</dt>
<dd class='Typename'><pre>    MAILER

</pre>
</dd>
<dt>Type purpose</dt>
<dd class='Typepurpose'><pre>    To specify the type of electronic mail software that is
   used by the individual associated with the vCard.

</pre>
</dd>
<dt>Type encoding</dt>
<dd class='Typeencoding'><pre>    8bit

</pre>
</dd>
<dt>Type value</dt>
<dd class='Typevalue'><pre>    A single text value.

</pre>
</dd>
<dt>Type special notes</dt>
<dd class='Typespecialnotes'><pre>    This information can provide assistance to a
   correspondent regarding the type of data representation which can be
   used, and how they can be packaged. This property is based on the
   private MIME type X-Mailer that is generally implemented by MIME user
   agent products.

</pre>
</dd>
<dt>Type example</dt>
<dd class='Typeexample'><pre>

        MAILER:PigeonMail 2.1

</pre>
</dd>
</dl>
</div>
<div><h2 id='sec3.4'>3.4 Geographical Types</h2>
<pre>
   These types are concerned with information associated with
   geographical positions or regions associated with the object the
   vCard represents.

</pre>
</div>
<div><h2 id='sec3.4.1'>3.4.1 TZ Type Definition</h2>
<dl>
<dt>To</dt>
<dd class='To'><pre>    ietf-mime-directory@imc.org

</pre>
</dd>
<dt>Subject</dt>
<dd class='Subject'><pre>    Registration of text/directory MIME type TZ

</pre>
</dd>
<dt id='Type_TZ'>Type name</dt>
<dd class='Typename'><pre>    TZ

</pre>
</dd>
<dt>Type purpose</dt>
<dd class='Typepurpose'><pre>    To specify information related to the time zone of the
   object the vCard represents.

</pre>
</dd>
<dt>Type encoding</dt>
<dd class='Typeencoding'><pre>    8bit

</pre>
</dd>
<dt>Type value</dt>
<dd class='Typevalue'><pre>    The default is a single utc-offset value. It can also be
   reset to a single text value.

</pre>
</dd>
<dt>Type special notes</dt>
<dd class='Typespecialnotes'><pre>    The type value consists of a single value.

   Type examples:

        TZ:-05:00

        TZ;VALUE=text:-05:00; EST; Raleigh/North America
        ;This example has a single value, not a structure text value.

</pre>
</dd>
</dl>
</div>
<div><h2 id='sec3.4.2'>3.4.2 GEO Type Definition</h2>
<dl>
<dt>To</dt>
<dd class='To'><pre>    ietf-mime-directory@imc.org

</pre>
</dd>
<dt>Subject</dt>
<dd class='Subject'><pre>    Registration of text/directory MIME type GEO

</pre>
</dd>
<dt id='Type_GEO'>Type name</dt>
<dd class='Typename'><pre>    GEO

</pre>
</dd>
<dt>Type purpose</dt>
<dd class='Typepurpose'><pre>    To specify information related to the global
   positioning of the object the vCard represents.

</pre>
</dd>
<dt>Type encoding</dt>
<dd class='Typeencoding'><pre>    8bit

</pre>
</dd>
<dt>Type value</dt>
<dd class='Typevalue'><pre>    A single structured value consisting of two float values
   separated by the SEMI-COLON character (ASCII decimal 59).

</pre>
</dd>
<dt>Type special notes</dt>
<dd class='Typespecialnotes'><pre>    This type specifies information related to the
   global position of the object associated with the vCard. The value
   specifies latitude and longitude, in that order (i.e., "LAT LON"
   ordering). The longitude represents the location east and west of the
   prime meridian as a positive or negative real number, respectively.
   The latitude represents the location north and south of the equator
   as a positive or negative real number, respectively. The longitude
   and latitude values MUST be specified as decimal degrees and should
   be specified to six decimal places. This will allow for granularity
   within a meter of the geographical position. The text components are
   separated by the SEMI-COLON character (ASCII decimal 59). The simple
   formula for converting degrees-minutes-seconds into decimal degrees
   is:

        decimal = degrees + minutes/60 + seconds/3600.

</pre>
</dd>
<dt>Type example</dt>
<dd class='Typeexample'><pre>

        GEO:37.386013;-122.082932

</pre>
</dd>
</dl>
</div>
<div><h2 id='sec3.5'>3.5 Organizational Types</h2>
<pre>
   These types are concerned with information associated with
   characteristics of the organization or organizational units of the
   object the vCard represents.

</pre>
</div>
<div><h2 id='sec3.5.1'>3.5.1 TITLE Type Definition</h2>
<dl>
<dt>To</dt>
<dd class='To'><pre>    ietf-mime-directory@imc.org

</pre>
</dd>
<dt>Subject</dt>
<dd class='Subject'><pre>    Registration of text/directory MIME type TITLE

</pre>
</dd>
<dt id='Type_TITLE'>Type name</dt>
<dd class='Typename'><pre>    TITLE

</pre>
</dd>
<dt>Type purpose</dt>
<dd class='Typepurpose'><pre>    To specify the job title, functional position or
   function of the object the vCard represents.

</pre>
</dd>
<dt>Type encoding</dt>
<dd class='Typeencoding'><pre>    8bit

</pre>
</dd>
<dt>Type value</dt>
<dd class='Typevalue'><pre>    A single text value.

</pre>
</dd>
<dt>Type special notes</dt>
<dd class='Typespecialnotes'><pre>    This type is based on the X.520 Title attribute.

</pre>
</dd>
<dt>Type example</dt>
<dd class='Typeexample'><pre>

        TITLE:Director\, Research and Development

</pre>
</dd>
</dl>
</div>
<div><h2 id='sec3.5.2'>3.5.2 ROLE Type Definition</h2>
<dl>
<dt>To</dt>
<dd class='To'><pre>    ietf-mime-directory@imc.org

</pre>
</dd>
<dt>Subject</dt>
<dd class='Subject'><pre>    Registration of text/directory MIME type ROLE

</pre>
</dd>
<dt id='Type_ROLE'>Type name</dt>
<dd class='Typename'><pre>    ROLE

</pre>
</dd>
<dt>Type purpose</dt>
<dd class='Typepurpose'><pre>    To specify information concerning the role, occupation,
   or business category of the object the vCard represents.

</pre>
</dd>
<dt>Type encoding</dt>
<dd class='Typeencoding'><pre>    8bit

</pre>
</dd>
<dt>Type value</dt>
<dd class='Typevalue'><pre>    A single text value.

</pre>
</dd>
<dt>Type special notes</dt>
<dd class='Typespecialnotes'><pre>    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.

</pre>
</dd>
<dt>Type example</dt>
<dd class='Typeexample'><pre>

        ROLE:Programmer

</pre>
</dd>
</dl>
</div>
<div><h2 id='sec3.5.3'>3.5.3 LOGO Type Definition</h2>
<dl>
<dt>To</dt>
<dd class='To'><pre>    ietf-mime-directory@imc.org

</pre>
</dd>
<dt>Subject</dt>
<dd class='Subject'><pre>    Registration of text/directory MIME type LOGO

</pre>
</dd>
<dt id='Type_LOGO'>Type name</dt>
<dd class='Typename'><pre>    LOGO

</pre>
</dd>
<dt>Type purpose</dt>
<dd class='Typepurpose'><pre>    To specify a graphic image of a logo associated with
   the object the vCard represents.

</pre>
</dd>
<dt>Type encoding</dt>
<dd class='Typeencoding'><pre>    The encoding MUST be reset to "b" using the ENCODING
   parameter in order to specify inline, encoded binary data. If the
   value is referenced by a URI value, then the default encoding of 8bit
   is used and no explicit ENCODING parameter is needed.

</pre>
</dd>
<dt>Type value</dt>
<dd class='Typevalue'><pre>    A single value. The default is binary value. It can also
   be reset to uri value. The uri value can be used to specify a value
   outside of this MIME entity.

</pre>
</dd>
<dt>Type special notes</dt>
<dd class='Typespecialnotes'><pre>    The type can include the type parameter "TYPE" to
   specify the graphic image format type. The TYPE parameter values MUST
   be one of the IANA registered image formats or a non-standard image
   format.

</pre>
</dd>
<dt>Type example</dt>
<dd class='Typeexample'><pre>

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

        LOGO;ENCODING=b;TYPE=JPEG:MIICajCCAdOgAwIBAgICBEUwDQYJKoZIhvcN
         AQEEBQAwdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05ldHNjYXBlIENvbW11bm
         ljYXRpb25zIENvcnBvcmF0aW9uMRwwGgYDVQQLExNJbmZvcm1hdGlvbiBTeXN0
         &lt;...the remainder of "B" encoded binary data...>

</pre>
</dd>
</dl>
</div>
<div><h2 id='sec3.5.4'>3.5.4 AGENT Type Definition</h2>
<dl>
<dt>To</dt>
<dd class='To'><pre>    ietf-mime-directory@imc.org

</pre>
</dd>
<dt>Subject</dt>
<dd class='Subject'><pre>    Registration of text/directory MIME type AGENT

</pre>
</dd>
<dt id='Type_AGENT'>Type name</dt>
<dd class='Typename'><pre>    AGENT

</pre>
</dd>
<dt>Type purpose</dt>
<dd class='Typepurpose'><pre>    To specify information about another person who will
   act on behalf of the individual or resource associated with the
   vCard.

</pre>
</dd>
<dt>Type encoding</dt>
<dd class='Typeencoding'><pre>    8-bit

</pre>
</dd>
<dt>Type value</dt>
<dd class='Typevalue'><pre>    The default is a single vcard value. It can also be reset
   to either a single text or uri value. The text value can be used to
   specify textual information. The uri value can be used to specify
   information outside of this MIME entity.

</pre>
</dd>
<dt>Type special notes</dt>
<dd class='Typespecialnotes'><pre>    This type typically is used to specify an area
   administrator, assistant, or secretary for the individual associated
   with the vCard. A key characteristic of the Agent type is that it
   represents somebody or something that is separately addressable.

</pre>
</dd>
<dt>Type example</dt>
<dd class='Typeexample'><pre>

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

        AGENT:BEGIN:VCARD\nFN:Susan Thomas\nTEL:+1-919-555-
         1234\nEMAIL\;INTERNET:sthomas@host.com\nEND:VCARD\n

</pre>
</dd>
</dl>
</div>
<div><h2 id='sec3.5.5'>3.5.5 ORG Type Definition</h2>
<dl>
<dt>To</dt>
<dd class='To'><pre>    ietf-mime-directory@imc.org

</pre>
</dd>
<dt>Subject</dt>
<dd class='Subject'><pre>    Registration of text/directory MIME type ORG

</pre>
</dd>
<dt id='Type_ORG'>Type name</dt>
<dd class='Typename'><pre>    ORG

</pre>
</dd>
<dt>Type purpose</dt>
<dd class='Typepurpose'><pre>    To specify the organizational name and units associated
   with the vCard.

</pre>
</dd>
<dt>Type encoding</dt>
<dd class='Typeencoding'><pre>    8bit

</pre>
</dd>
<dt>Type value</dt>
<dd class='Typevalue'><pre>    A single structured text value consisting of components
   separated the SEMI-COLON character (ASCII decimal 59).

</pre>
</dd>
<dt>Type special notes</dt>
<dd class='Typespecialnotes'><pre>    The type is based on the X.520 Organization Name
   and Organization Unit attributes. The type value is a structured type
   consisting of the organization name, followed by one or more levels
   of organizational unit names.

</pre>
</dd>
<dt>Type example</dt>
<dd class='Typeexample'><pre>    A type value consisting of an organizational name,
   organizational unit #1 name and organizational unit #2 name.

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

</pre>
</dd>
</dl>
</div>
<div><h2 id='sec3.6'>3.6 Explanatory Types</h2>
<pre>
   These types are concerned with additional explanations, such as that
   related to informational notes or revisions specific to the vCard.

</pre>
</div>
<div><h2 id='sec3.6.1'>3.6.1 CATEGORIES Type Definition</h2>
<dl>
<dt>To</dt>
<dd class='To'><pre>    ietf-mime-directory@imc.org

</pre>
</dd>
<dt>Subject</dt>
<dd class='Subject'><pre>    Registration of text/directory MIME type CATEGORIES

</pre>
</dd>
<dt id='Type_CATEGORIES'>Type name</dt>
<dd class='Typename'><pre>    CATEGORIES

</pre>
</dd>
<dt>Type purpose</dt>
<dd class='Typepurpose'><pre>    To specify application category information about the
   vCard.

</pre>
</dd>
<dt>Type encoding</dt>
<dd class='Typeencoding'><pre>    8bit

</pre>
</dd>
<dt>Type value</dt>
<dd class='Typevalue'><pre>    One or more text values separated by a COMMA character
   (ASCII decimal 44).

</pre>
</dd>
<dt>Type example</dt>
<dd class='Typeexample'><pre>

        CATEGORIES:TRAVEL AGENT

        CATEGORIES:INTERNET,IETF,INDUSTRY,INFORMATION TECHNOLOGY

</pre>
</dd>
</dl>
</div>
<div><h2 id='sec3.6.2'>3.6.2 NOTE Type Definition</h2>
<dl>
<dt>To</dt>
<dd class='To'><pre>    ietf-mime-directory@imc.org

</pre>
</dd>
<dt>Subject</dt>
<dd class='Subject'><pre>    Registration of text/directory MIME type NOTE

</pre>
</dd>
<dt id='Type_NOTE'>Type name</dt>
<dd class='Typename'><pre>    NOTE

</pre>
</dd>
<dt>Type purpose</dt>
<dd class='Typepurpose'><pre>    To specify supplemental information or a comment that
   is associated with the vCard.

</pre>
</dd>
<dt>Type encoding</dt>
<dd class='Typeencoding'><pre>    8bit

</pre>
</dd>
<dt>Type value</dt>
<dd class='Typevalue'><pre>    A single text value.

</pre>
</dd>
<dt>Type special notes</dt>
<dd class='Typespecialnotes'><pre>    The type is based on the X.520 Description
   attribute.

</pre>
</dd>
<dt>Type example</dt>
<dd class='Typeexample'><pre>

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

</pre>
</dd>
</dl>
</div>
<div><h2 id='sec3.6.3'>3.6.3 PRODID Type Definition</h2>
<dl>
<dt>To</dt>
<dd class='To'><pre>    ietf-mime-directory@imc.org

</pre>
</dd>
<dt>Subject</dt>
<dd class='Subject'><pre>    Registration of text/directory MIME type PRODID

</pre>
</dd>
<dt id='Type_PRODID'>Type name</dt>
<dd class='Typename'><pre>    PRODID

</pre>
</dd>
<dt>Type purpose</dt>
<dd class='Typepurpose'><pre>    To specify the identifier for the product that created
   the vCard object.

</pre>
</dd>
<dt>Type encoding</dt>
<dd class='Typeencoding'><pre>    8-bit

</pre>
</dd>
<dt>Type value</dt>
<dd class='Typevalue'><pre>    A single text value.

</pre>
</dd>
<dt>Type special notes</dt>
<dd class='Typespecialnotes'><pre>    Implementations SHOULD use a method such as that
   specified for Formal Public Identifiers in ISO 9070 to assure that
   the text value is unique.

</pre>
</dd>
<dt>Type example</dt>
<dd class='Typeexample'><pre>

        PRODID:-//ONLINE DIRECTORY//NONSGML Version 1//EN

</pre>
</dd>
</dl>
</div>
<div><h2 id='sec3.6.4'>3.6.4 REV Type Definition</h2>
<dl>
<dt>To</dt>
<dd class='To'><pre>    ietf-mime-directory@imc.org

</pre>
</dd>
<dt>Subject</dt>
<dd class='Subject'><pre>    Registration of text/directory MIME type REV

</pre>
</dd>
<dt id='Type_REV'>Type name</dt>
<dd class='Typename'><pre>    REV

</pre>
</dd>
<dt>Type purpose</dt>
<dd class='Typepurpose'><pre>    To specify revision information about the current
   vCard.

</pre>
</dd>
<dt>Type encoding</dt>
<dd class='Typeencoding'><pre>    8-bit

</pre>
</dd>
<dt>Type value</dt>
<dd class='Typevalue'><pre>    The default is a single date-time value. Can also be
   reset to a single date value.

</pre>
</dd>
<dt>Type special notes</dt>
<dd class='Typespecialnotes'><pre>    The value distinguishes the current revision of
   the information in this vCard for other renditions of the
   information.

</pre>
</dd>
<dt>Type example</dt>
<dd class='Typeexample'><pre>

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

        REV:1997-11-15

</pre>
</dd>
</dl>
</div>
<div><h2 id='sec3.6.5'>3.6.5 SORT-STRING Type Definition</h2>
<dl>
<dt>To</dt>
<dd class='To'><pre>    ietf-mime-directory@imc.org

</pre>
</dd>
<dt>Subject</dt>
<dd class='Subject'><pre>    Registration of text/directory MIME type SORT-STRING

</pre>
</dd>
<dt id='Type_SORT-STRING'>Type Name</dt>
<dd class='TypeName'><pre>    SORT-STRING

</pre>
</dd>
<dt>Type purpose</dt>
<dd class='Typepurpose'><pre>    To specify the family name or given name text to be
   used for national-language-specific sorting of the FN and N types.

</pre>
</dd>
<dt>Type encoding</dt>
<dd class='Typeencoding'><pre>    8bit

</pre>
</dd>
<dt>Type value</dt>
<dd class='Typevalue'><pre>    A single text value.

</pre>
</dd>
<dt>Type special notes</dt>
<dd class='Typespecialnotes'><pre>    The sort string is used to provide family name or
   given name text that is to be used in locale- or national-language-
   specific sorting of the formatted name and structured name types.
   Without this information, sorting algorithms could incorrectly sort
   this vCard within a sequence of sorted vCards.  When this type is
   present in a vCard, then this family name or given name value is used
   for sorting the vCard.

   Type examples: For the case of family name sorting, the following
   examples define common sort string usage with the FN and N types.

        FN:Rene van der Harten
        N:van der Harten;Rene;J.;Sir;R.D.O.N.
        SORT-STRING:Harten

        FN:Robert Pau Shou Chang
        N:Pau;Shou Chang;Robert
        SORT-STRING:Pau

        FN:Osamu Koura
        N:Koura;Osamu
        SORT-STRING:Koura

        FN:Oscar del Pozo
        N:del Pozo Triscon;Oscar
        SORT-STRING:Pozo

        FN:Chistine d'Aboville
        N:d'Aboville;Christine
        SORT-STRING:Aboville

</pre>
</dd>
</dl>
</div>
<div><h2 id='sec3.6.6'>3.6.6 SOUND Type Definition</h2>
<dl>
<dt>To</dt>
<dd class='To'><pre>    ietf-mime-directory@imc.org

</pre>
</dd>
<dt>Subject</dt>
<dd class='Subject'><pre>    Registration of text/directory MIME type SOUND

</pre>
</dd>
<dt id='Type_SOUND'>Type name</dt>
<dd class='Typename'><pre>    SOUND

</pre>
</dd>
<dt>Type purpose</dt>
<dd class='Typepurpose'><pre>    To specify a digital sound content information that
   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.

</pre>
</dd>
<dt>Type encoding</dt>
<dd class='Typeencoding'><pre>    The encoding MUST be reset to "b" using the ENCODING
   parameter in order to specify inline, encoded binary data. If the
   value is referenced by a URI value, then the default encoding of 8bit
   is used and no explicit ENCODING parameter is needed.

</pre>
</dd>
<dt>Type value</dt>
<dd class='Typevalue'><pre>    A single value. The default is binary value. It can also
   be reset to uri value. The uri value can be used to specify a value
   outside of this MIME entity.

</pre>
</dd>
<dt>Type special notes</dt>
<dd class='Typespecialnotes'><pre>    The type can include the type parameter "TYPE" to
   specify the audio format type. The TYPE parameter values MUST be one
   of the IANA registered audio formats or a non-standard audio format.

</pre>
</dd>
<dt>Type example</dt>
<dd class='Typeexample'><pre>

        SOUND;TYPE=BASIC;VALUE=uri:CID:JOHNQPUBLIC.part8.
         19960229T080000.xyzMail@host1.com

        SOUND;TYPE=BASIC;ENCODING=b:MIICajCCAdOgAwIBAgICBEUwDQYJKoZIhvcN
         AQEEBQAwdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05ldHNjYXBlIENvbW11bm
         ljYXRpb25zIENvcnBvcmF0aW9uMRwwGgYDVQQLExNJbmZvcm1hdGlvbiBTeXN0
         &lt;...the remainder of "B" encoded binary data...>

</pre>
</dd>
</dl>
</div>
<div><h2 id='sec3.6.7'>3.6.7 UID Type Definition</h2>
<dl>
<dt>To</dt>
<dd class='To'><pre>    ietf-mime-directory@imc.org

</pre>
</dd>
<dt>Subject</dt>
<dd class='Subject'><pre>    Registration of text/directory MIME type UID

</pre>
</dd>
<dt id='Type_UID'>Type name</dt>
<dd class='Typename'><pre>    UID

</pre>
</dd>
<dt>Type purpose</dt>
<dd class='Typepurpose'><pre>    To specify a value that represents a globally unique
   identifier corresponding to the individual or resource associated
   with the vCard.

</pre>
</dd>
<dt>Type encoding</dt>
<dd class='Typeencoding'><pre>    8bit

</pre>
</dd>
<dt>Type value</dt>
<dd class='Typevalue'><pre>    A single text value.

</pre>
</dd>
<dt>Type special notes</dt>
<dd class='Typespecialnotes'><pre>    The type is used to uniquely identify the object
   that the vCard represents.

   The type can include the type parameter "TYPE" to specify the format
   of the identifier. The TYPE parameter value should be an IANA
   registered identifier format. The value can also be a non-standard
   format.

</pre>
</dd>
<dt>Type example</dt>
<dd class='Typeexample'><pre>

        UID:19950401-080045-40000F192713-0052

</pre>
</dd>
</dl>
</div>
<div><h2 id='sec3.6.8'>3.6.8 URL Type Definition</h2>
<dl>
<dt>To</dt>
<dd class='To'><pre>    ietf-mime-directory@imc.org

</pre>
</dd>
<dt>Subject</dt>
<dd class='Subject'><pre>    Registration of text/directory MIME type URL

</pre>
</dd>
<dt id='Type_URL'>Type name</dt>
<dd class='Typename'><pre>    URL

</pre>
</dd>
<dt>Type purpose</dt>
<dd class='Typepurpose'><pre>    To specify a uniform resource locator associated with
   the object that the vCard refers to.

</pre>
</dd>
<dt>Type encoding</dt>
<dd class='Typeencoding'><pre>    8bit

</pre>
</dd>
<dt>Type value</dt>
<dd class='Typevalue'><pre>    A single uri value.

</pre>
</dd>
<dt>Type example</dt>
<dd class='Typeexample'><pre>

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

</pre>
</dd>
</dl>
</div>
<div><h2 id='sec3.6.9'>3.6.9 VERSION Type Definition</h2>
<dl>
<dt>To</dt>
<dd class='To'><pre>    ietf-mime-directory@imc.org

</pre>
</dd>
<dt>Subject</dt>
<dd class='Subject'><pre>    Registration of text/directory MIME type VERSION

</pre>
</dd>
<dt id='Type_VERSION'>Type name</dt>
<dd class='Typename'><pre>    VERSION

</pre>
</dd>
<dt>Type purpose</dt>
<dd class='Typepurpose'><pre>    To specify the version of the vCard specification used
   to format this vCard.

</pre>
</dd>
<dt>Type encoding</dt>
<dd class='Typeencoding'><pre>    8bit

</pre>
</dd>
<dt>Type value</dt>
<dd class='Typevalue'><pre>    A single text value.

</pre>
</dd>
<dt>Type special notes</dt>
<dd class='Typespecialnotes'><pre>    The property MUST be present in the vCard object.
   The value MUST be "3.0" if the vCard corresponds to this
   specification.

</pre>
</dd>
<dt>Type example</dt>
<dd class='Typeexample'><pre>

        VERSION:3.0

</pre>
</dd>
</dl>
</div>
<div><h2 id='sec3.7'>3.7 Security Types</h2>
<pre>
   These types are concerned with the security of communication pathways
   or access to the vCard.

</pre>
</div>
<div><h2 id='sec3.7.1'>3.7.1 CLASS Type Definition</h2>
<dl>
<dt>To</dt>
<dd class='To'><pre>    ietf-mime-directory@imc.org

</pre>
</dd>
<dt>Subject</dt>
<dd class='Subject'><pre>    Registration of text/directory MIME type CLASS

</pre>
</dd>
<dt id='Type_CLASS'>Type name</dt>
<dd class='Typename'><pre>    CLASS

</pre>
</dd>
<dt>Type purpose</dt>
<dd class='Typepurpose'><pre>    To specify the access classification for a vCard
   object.

</pre>
</dd>
<dt>Type encoding</dt>
<dd class='Typeencoding'><pre>    8bit

</pre>
</dd>
<dt>Type value</dt>
<dd class='Typevalue'><pre>    A single text value.

</pre>
</dd>
<dt>Type special notes</dt>
<dd class='Typespecialnotes'><pre>    An access classification is only one component of
   the general security model for a directory service. The
   classification attribute provides a method of capturing the intent of
   the owner for general access to information described by the vCard
   object.

   Type examples:

        CLASS:PUBLIC

        CLASS:PRIVATE

        CLASS:CONFIDENTIAL

</pre>
</dd>
</dl>
</div>
<div><h2 id='sec3.7.2'>3.7.2 KEY Type Definition</h2>
<dl>
<dt>To</dt>
<dd class='To'><pre>    ietf-mime-directory@imc.org

</pre>
</dd>
<dt>Subject</dt>
<dd class='Subject'><pre>    Registration of text/directory MIME type KEY

</pre>
</dd>
<dt id='Type_KEY'>Type name</dt>
<dd class='Typename'><pre>    KEY

</pre>
</dd>
<dt>Type purpose</dt>
<dd class='Typepurpose'><pre>    To specify a public key or authentication certificate
   associated with the object that the vCard represents.

</pre>
</dd>
<dt>Type encoding</dt>
<dd class='Typeencoding'><pre>    The encoding MUST be reset to "b" using the ENCODING
   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
   no explicit ENCODING parameter is needed.

</pre>
</dd>
<dt>Type value</dt>
<dd class='Typevalue'><pre>    A single value. The default is binary. It can also be
   reset to text value. The text value can be used to specify a text
   key.

</pre>
</dd>
<dt>Type special notes</dt>
<dd class='Typespecialnotes'><pre>    The type can also include the type parameter TYPE
   to specify the public key or authentication certificate format. The
   parameter type should specify an IANA registered public key or
   authentication certificate format. The parameter type can also
   specify a non-standard format.

</pre>
</dd>
<dt>Type example</dt>
<dd class='Typeexample'><pre>

        KEY;ENCODING=b:MIICajCCAdOgAwIBAgICBEUwDQYJKoZIhvcNAQEEBQA
         wdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05ldHNjYXBlIENbW11bmljYX
         Rpb25zIENvcnBvcmF0aW9uMRwwGgYDVQQLExNJbmZvcm1hdGlvbiBTeXN0
         ZW1zMRwwGgYDVQQDExNyb290Y2EubmV0c2NhcGUuY29tMB4XDTk3MDYwNj
         E5NDc1OVoXDTk3MTIwMzE5NDc1OVowgYkxCzAJBgNVBAYTAlVTMSYwJAYD
         VQQKEx1OZXRzY2FwZSBDb21tdW5pY2F0aW9ucyBDb3JwLjEYMBYGA1UEAx
         MPVGltb3RoeSBBIEhvd2VzMSEwHwYJKoZIhvcNAQkBFhJob3dlc0BuZXRz
         Y2FwZS5jb20xFTATBgoJkiaJk/IsZAEBEwVob3dlczBcMA0GCSqGSIb3DQ
         EBAQUAA0sAMEgCQQC0JZf6wkg8pLMXHHCUvMfL5H6zjSk4vTTXZpYyrdN2
         dXcoX49LKiOmgeJSzoiFKHtLOIboyludF90CgqcxtwKnAgMBAAGjNjA0MB
         EGCWCGSAGG+EIBAQQEAwIAoDAfBgNVHSMEGDAWgBT84FToB/GV3jr3mcau
         +hUMbsQukjANBgkqhkiG9w0BAQQFAAOBgQBexv7o7mi3PLXadkmNP9LcIP
         mx93HGp0Kgyx1jIVMyNgsemeAwBM+MSlhMfcpbTrONwNjZYW8vJDSoi//y
         rZlVt9bJbs7MNYZVsyF1unsqaln4/vy6Uawfg8VUMk1U7jt8LYpo4YULU7
         UZHPYVUaSgVttImOHZIKi4hlPXBOhcUQ==

</pre>
</dd>
</dl>
</div>
<div><h2 id='sec3.8'>3.8 Extended Types</h2>
<pre>
   The types defined by this document can be extended with private types
   using the non-standard, private values mechanism defined in RFC
   2045]. Non-standard, private types with a name starting with "X-" may
   be defined bilaterally between two cooperating agents without outside
   registration or standardization.

</pre>
</div>
<div><h2 id='sec4.'>4. Formal Grammar</h2>
<pre>
   The following formal grammar is provided to assist developers in
   building parsers for the vCard.

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

   ;*******************************************
   ; Commonly Used Literal Definition
   ;*******************************************

   ALPHA        = %x41-5A / %x61-7A
        ; Latin Capital Letter A-Latin Capital Letter Z /
        ; Latin Small Letter a-Latin Small Letter z

   CHAR         = %x01-7F
        ; Any C0 Controls and Basic Latin, excluding NULL from
        ; Code Charts, pages 7-6 through 7-9 in <a href='#ref_UNICODE'>[UNICODE]</a>

   CR           = %x0D
        ; Carriage Return

   LF           = %0A
        ; Line Feed

   CRLF         = CR LF
        ; Internet standard newline

   ;CTL         = %x00-1F / %x7F
        ; Controls. Not used, but referenced in comments.

   DIGIT        = %x30-39
        ; Digit Zero-Digit Nine

   DQUOTE       = %x22
        ; Quotation Mark

   HTAB         = %x09
        ; Horizontal Tabulation

   SP           = %x20
        ; space

   VCHAR        = %x21-7E
        ; Visible (printing) characters

   WSP          = SP / HTAB
        ; White Space

   ;*******************************************
   ; Basic vCard Definition
   ;*******************************************

   vcard_entity = 1*(vcard)

   vcard        = group "."] "BEGIN" ":" "VCARD" 1*CRLF
                  1*(contentline)
        ;A vCard object MUST include the VERSION, FN and N types.
                  group "."] "END" ":" "VCARD" 1*CRLF

   contentline  = group "."] name *(";" param ) ":" value CRLF
        ; When parsing a content line, folded lines must first
        ; be unfolded according to the unfolding procedure

        ; described above. When generating a content line, lines
        ; longer than 75 characters SHOULD be folded according to
        ; the folding procedure described in MIME DIR].

   group        = 1*(ALPHA / DIGIT / "-")

   name         = iana-token / x-name
        ; Parsing of the param and value is
        ; based on the "name" or type identifier
        ; as defined in ABNF sections below

   iana-token   = 1*(ALPHA / DIGIT / "-")
        ; vCard type or parameter identifier registered with IANA

   x-name       = "X-" 1*(ALPHA / DIGIT / "-")
        ; Reserved for non-standard use

   param        = param-name "=" param-value *("," param-value)

   param-name   = iana-token / x-name

   param-value  = ptext / quoted-string

   ptext        = *SAFE-CHAR

   value        = *VALUE-CHAR

   quoted-string = DQUOTE QSAFE-CHAR DQUOTE

   NON-ASCII    = %x80-FF
        ; Use is restricted by CHARSET parameter
        ; on outer MIME object (UTF-8 preferred)

   QSAFE-CHAR   = WSP / %x21 / %x23-7E / NON-ASCII
        ; Any character except CTLs, DQUOTE

   SAFE-CHAR    = WSP / %x21 / %x23-2B / %x2D-39 / %x3C-7E / NON-ASCII
        ; 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        = text-value
        ; Value MUST be the case insensitive value "VCARD

   ;For name="SOURCE"
   param        = source-param
        ; No parameters allowed

   value        = uri

   source-param = ("VALUE" "=" "uri")
                / ("CONTEXT" "=" "word")
        ; Parameter value specifies the protocol context
        ; for the uri value.
                / (x-name "=" *SAFE-CHAR)

   ;For name="FN"
   ;This type MUST be included in a vCard object.
   param        = text-param
        ; Text parameters allowed

   value        = text-value

   ;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

   ;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

   value        = text-value

   ;For name="TEL"
   param        = tel-param
        ; Only tel parameters allowed

   value        = phone-number-value

   tel-param    = "TYPE" "=" tel-type *("," tel-type)

   tel-type     = "HOME" / "WORK" / "PREF" / "VOICE" / "FAX" / "MSG"
                / "CELL" / "PAGER" / "BBS" / "MODEM" / "CAR" / "ISDN"
                / "VIDEO" / "PCS" / iana-token / x-name
        ; Values are case insensitive

   ;For name="EMAIL"
   param        = email-param
        ; Only email parameters allowed

   value        = text-value

   email-param  = "TYPE" "=" email-type "," "PREF"]
        ; Value is case insensitive

   email-type   = "INTERNET" / "X400" / iana-token / "X-" word
        ; Values are case insensitive

   ;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

   ;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 and parameter MUST match

   value        =/ agent-refer-value
        ; Value and parameter MUST match

   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

   ;For name="ORG"

   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

   value        = text-value

   ;For name="REV"
   param        = "VALUE" =" "date-time"]
        ; Only value parameters allowed. Values are case insensitive.

   param        =/ "VALUE" =" "date"
        ; Only value parameters allowed. Values are case insensitive.

   value        = date-time-value

   value        =/ date-value

   ;For name="SORT-STRING"
   param        = text-param
        ; Only text parameters allowed

   value        = text-value

   ;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-value CRLF
        ; Value MUST be "b" encoded audio content

   snd-inline-param     = ("VALUE" "=" "binary"])
                        / ("ENCODING" "=" "b")
                        / ("TYPE" "=" *SAFE-CHAR)
        ; Value MUST be an IANA registered audio type

   snd-refer-value      = uri
        ; URI MUST refer to audio content of given type

   snd-refer-param      = ("VALUE" "=" "uri")
                        / ("TYPE" "=" word)
        ; Value MUST be an IANA registered audio type

   ;For name="UID"
   param        = ""
        ; No parameters allowed

   value        = text-value

   ;For name="URL"
   param        = ""
        ; No parameters allowed

   value        = uri

   ;For name="VERSION"
   ;This type MUST be included in a vCard object.
   param        = ""
        ; No parameters allowed

   value        = text-value
        ; Value MUST be "3.0"

   ;For name="CLASS"
   param        = ""
        ; No parameters allowed

   value        = "PUBLIC" / "PRIVATE" / "CONFIDENTIAL"
                / iana-token / x-name
        ; Value are case insensitive

   ;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-value

   key-txt-param = "TYPE" "=" keytype

   key-bin-param = ("TYPE" "=" keytype)
                 / ("ENCODING" "=" "b")
        ; Value MUST be a "b" encoded key or certificate

   keytype      = "X509" / "PGP" / iana-token / x-name
        ; Values are case insensitive

   ;For name="X-" non-standard type
   param        = text-param / (x-name "=" param-value)
        ; Only text or non-standard parameters allowed

   value        = text-value

   ;*******************************************
   ; vCard Commonly Used Parameter Definition
   ;*******************************************

   text-param   = ("VALUE" "=" "ptext")
                / ("LANGUAGE" "=" langval)
                / (x-name "=" param-value)

   langval      = &lt;a language string as defined in RFC 1766>

   img-inline-value     = binary-value
        ;Value MUST be "b" encoded image content

   img-inline-param

   img-inline-param     = ("VALUE" "=" "binary")
                        / ("ENCODING" "=" "b")
                        / ("TYPE" "=" param-value
        ;TYPE value MUST be an IANA registered image type

   img-refer-value = uri
        ;URI MUST refer to image content of given type

   img-refer-param      = ("VALUE" "=" "uri")
                        / ("TYPE" "=" param-value)
        ;TYPE value MUST be an IANA registered image type

   adr-param    = ("TYPE" "=" adr-type *("," 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-value-list      = 1*text-value *("," 1*text-value)

   text-value   = *(SAFE-CHAR / ":" / DQUOTE / ESCAPED-CHAR)

   ESCAPED-CHAR = "\\" / "\;" / "\," / "\n" / "\N")
        ; \\ encodes \, \n or \N encodes newline
        ; \; encodes ;, \, encodes ,

   binary-value = &lt;A "b" encoded text value as defined in <a href='#ref_RFC_2047'>[RFC 2047]</a>>

   date-value   = &lt;A single date value as defined in <a href='#ref_MIME-DIR'>[MIME-DIR]</a>>

   time-value   = &lt;A single time value as defined in <a href='#ref_MIME-DIR'>[MIME-DIR]</a>>

   date-time-value = &lt;A single date-time value as defined in <a href='#ref_MIME-DIR'>[MIME-DIR]</a>

   float-value  = &lt;A single float value as defined in <a href='#ref_MIME-DIR'>[MIME-DIR]</a>>

   phone-number-value = &lt;A single text  value as defined in CCITT
                         E.163] and <a href='#ref_CCITT_X.121'>[CCITT X.121]</a>>

   uri-value    = &lt;A uri value as defined in <a href='#ref_MIME-DIR'>[MIME-DIR]</a>>

   utc-offset-value = ("+" / "-") time-hour ":" time-minute
   time-hour    = 2DIGIT                ;00-23
   time-minute  = 2DIGIT                ;00-59

</pre>
</div>
<div><h2 id='sec5.'>5. Differences From vCard v2.1</h2>
<pre>
   This specification has been reviewed by the IETF community. The
   review process introduced a number of differences from the <a href='#ref_VCARD'>[VCARD]</a>
   version 2.1. These differences require that vCard objects conforming
   to this specification have a different version number than a vCard
   conforming to <a href='#ref_VCARD'>[VCARD]</a>. The differences include the following:

        . The QUOTED-PRINTABLE inline encoding has been eliminated.
          Only the "B" encoding of <a href='#ref_RFC_2047'>[RFC 2047]</a> is an allowed value for
          the ENCODING parameter.

        . The method for specifying CRLF character sequences in text
          type values has been changed. The CRLF character sequence in
          a text type value is specified with the backslash character
          sequence "\n" or "\N".

        . Any COMMA or SEMICOLON in a text type value must be backslash
          escaped.

        . VERSION value corresponding to this specification MUST be
          "3.0".

        . The <a href='#ref_MIME-DIR'>[MIME-DIR]</a> predefined types of SOURCE, NAME and PROFILE
          are allowed.

        . The <a href='#ref_MIME-DIR'>[MIME-DIR]</a> 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 <a href='#ref_VCARD'>[VCARD]</a> CHARSET type parameter has been eliminated.
          Character set can only be specified on the CHARSET parameter
          on the Content-Type MIME header field.

        . The <a href='#ref_VCARD'>[VCARD]</a> support for non-significant WSP character has
          been eliminated.

        . The "TYPE=" prefix to parameter values is required. In
          <a href='#ref_VCARD'>[VCARD]</a> this was optional.

        . 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 can 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.

        . 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.

</pre>
</div>
<div><h2 id='sec6.'>6. Acknowledgements</h2>
<p>
   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, Patrik Faltstrom, Daniel
   Gurney, Bruce Johnston, Daniel Klaussen, Pete Miller, Keith Moore,
   Vinod Seraphin, Michelle Watkins. Chris Newman was especially helpful
   in navigating the intricacies of ABNF lore.
</p>
</div><div><h2 id='sec7.'>7. Authors' Addresses</h2>
<pre>
   BEGIN:vCard
   VERSION:3.0
   FN:Frank Dawson
   ORG:Lotus Development Corporation
   ADR;TYPE=WORK,POSTAL,PARCEL:;;6544 Battleford Drive
    ;Raleigh;NC;27613-3502;U.S.A.
   TEL;TYPE=VOICE,MSG,WORK:+1-919-676-9515
   TEL;TYPE=FAX,WORK:+1-919-676-9564
   EMAIL;TYPE=INTERNET,PREF:Frank_Dawson@Lotus.com
   EMAIL;TYPE=INTERNET:fdawson@earthlink.net
   URL:http://home.earthlink.net/~fdawson
   END:vCard


   BEGIN:vCard
   VERSION:3.0
   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

</pre>
</div>
<div><h2 id='sec8.'>8. Security Considerations</h2>
<pre>
   vCards can carry cryptographic keys or certificates, as described in
   Section 3.7.2.

   Section 3.7.1 specifies a desired security classification policy for
   a particular vCard. That policy is not enforced in any way.

   The vCard objects have no inherent authentication or privacy, but can
   easily be carried by any security mechanism that transfers MIME
   objects with authentication or privacy. In cases where threats of
   "spoofed" vCard information is a concern, the vCard SHOULD BE

   transported using one of these secure mechanisms.

   The information in a vCard may become out of date. In cases where the
   vitality of data is important to an originator of a vCard, the "URL"
   type described in section 3.6.8 SHOULD BE specified. In addition, the
   "REV" type described in section 3.6.4 can be specified to indicate
   the last time that the vCard data was updated.

</pre>
</div>
<div><h2 id='sec9.'>9. References</h2>
<dl>
<dt id='ref_ISO_8601'>[ISO 8601]</dt>
<dd>    ISO 8601:1988 - Data elements and interchange formats -
Information interchange - Representation of dates and
times - The International Organization for
Standardization, June, 1988.
</dd>
<dt id='ref_ISO_8601_TC'>[ISO 8601 TC]</dt>
<dd> ISO 8601, Technical Corrigendum 1 - Data elements and
interchange formats - Information interchange -
Representation of dates and times - The International
Organization for Standardization, May, 1991.
</dd>
<dt id='ref_ISO_9070'>[ISO 9070]</dt>
<dd>    ISO 9070, Information Processing - SGML support
facilities - Registration Procedures for Public Text
Owner Identifiers, April, 1991.
</dd>
<dt id='ref_CCITT_E.163'>[CCITT E.163]</dt>
<dd> Recommendation E.163 - Numbering Plan for The
International Telephone Service, CCITT Blue Book,
Fascicle II.2, pp.  128-134, November, 1988.
</dd>
<dt id='ref_CCITT_X.121'>[CCITT X.121]</dt>
<dd> Recommendation X.121 - International Numbering Plan for
Public Data Networks, CCITT Blue Book, Fascicle VIII.3,
pp. 317-332, November, 1988.
</dd>
<dt id='ref_CCITT_X.520'>[CCITT X.520]</dt>
<dd> Recommendation X.520 - The Directory - Selected
Attribute Types, November 1988.
</dd>
<dt id='ref_CCITT_X.521'>[CCITT X.521]</dt>
<dd> Recommendation X.521 - The Directory - Selected Object
Classes, November 1988.
</dd>
<dt id='ref_MIME-DIR'>[MIME-DIR]</dt>
<dd>    Howes, T., Smith, M., and F. Dawson, <cite><a href='http://www.ietf.org/rfc/rfc2425'>A MIME Content-
Type for Directory Information</a></cite>, RFC 2425, September
1998.
</dd>
<dt id='ref_RFC_1738'>[RFC 1738]</dt>
<dd>    Berners-Lee, T., Masinter, L., and M. McCahill,
<cite><a href='http://www.ietf.org/rfc/rfc1738'>Uniform Resource Locators (URL)</a></cite>, RFC 1738, December
1994.
</dd>
<dt id='ref_RFC_1766'>[RFC 1766]</dt>
<dd>    Alvestrand, H., <cite><a href='http://www.ietf.org/rfc/rfc1766'>Tags for the Identification of
Languages</a></cite>, RFC 1766, March 1995.
</dd>
<dt id='ref_RFC_1872'>[RFC 1872]</dt>
<dd>    Levinson, E., <cite><a href='http://www.ietf.org/rfc/rfc1872'>The MIME Multipart/Related Content-
type</a></cite>, RFC 1872, December 1995.
</dd>
<dt id='ref_RFC_2045'>[RFC 2045]</dt>
<dd>    Freed, N., and N. Borenstein, <cite><a href='http://www.ietf.org/rfc/rfc2045'>Multipurpose Internet
Mail Extensions (MIME) - Part One: Format of Internet
Message Bodies</a></cite>, RFC 2045, November 1996.
</dd>
<dt id='ref_RFC_2046'>[RFC 2046]</dt>
<dd>    Freed, N., and N. Borenstein, <cite><a href='http://www.ietf.org/rfc/rfc2046'>Multipurpose Internet
Mail Extensions (MIME) - Part Two: Media Types</a></cite>, RFC
2046, November 1996.
</dd>
<dt id='ref_RFC_2047'>[RFC 2047]</dt>
<dd>    Moore, K., <cite><a href='http://www.ietf.org/rfc/rfc2047'>Multipurpose Internet Mail Extensions
(MIME) - Part Three: Message Header Extensions for
Non-ASCII Text</a></cite>, RFC 2047, November 1996.
</dd>
<dt id='ref_RFC_2048'>[RFC 2048]</dt>
<dd>    Freed, N., Klensin, J., and J. Postel, <cite><a href='http://www.ietf.org/rfc/rfc2048'>Multipurpose
Internet Mail Extensions (MIME) - Part Four:
Registration Procedures</a></cite>, RFC 2048, January 1997.
</dd>
<dt id='ref_RFC_2119'>[RFC 2119]</dt>
<dd>    Bradner, S., <cite><a href='http://www.ietf.org/rfc/rfc2119'>Key words for use in RFCs to Indicate
Requirement Levels</a></cite>, BCP 14, RFC 2119, March 1997.
</dd>
<dt id='ref_RFC_2234'>[RFC 2234]</dt>
<dd>    Crocker, D., and P. Overell, <cite><a href='http://www.ietf.org/rfc/rfc2234'>Augmented BNF for Syntax
Specifications: ABNF</a></cite>, RFC 2234, November 1997.
</dd>
<dt id='ref_UNICODE'>[UNICODE]</dt>
<dd>     <cite>The Unicode Standard - Version 2.0</cite>, The Unicode
Consortium, July 1996.
</dd>
<dt id='ref_VCARD'>[VCARD]</dt>
<dd>       Internet Mail Consortium, <cite><a href='http://www.imc.org/pdi/vcard-21.txt'>vCard - The Electronic
Business Card Version 2.1</a></cite>,
http://www.imc.org/pdi/vcard-21.txt, September 18,
1996.
</dd>
<dt id='ref_VCARD'>[VCARD]</dt>
<dd>       Internet Mail Consortium, <cite><a href='http://www.imc.org/pdi/vcard-21.txt'>vCard - The Electronic
Business Card Version 2.1</a></cite>,
http://www.imc.org/pdi/vcard-21.txt, September 18,
1996.
</dd>
</dl>
</div>
<div><h2 id='sec10.'>10. Full Copyright Statement</h2>
<p>
   Copyright (C) The Internet Society (1998).  All Rights Reserved.
</p>
<p>
   This document and translations of it may be copied and furnished to
   others, and derivative works that comment on or otherwise explain it
   or assist in its implementation may be prepared, copied, published
   and distributed, in whole or in part, without restriction of any
   kind, provided that the above copyright notice and this paragraph are
   included on all such copies and derivative works.  However, this
   document itself may not be modified in any way, such as by removing
   the copyright notice or references to the Internet Society or other
   Internet organizations, except as needed for the purpose of
   developing Internet standards in which case the procedures for
   copyrights defined in the Internet Standards process must be
   followed, or as required to translate it into languages other than
   English.
</p>
<p>
   The limited permissions granted above are perpetual and will not be
   revoked by the Internet Society or its successors or assigns.
</p>
<p>
   This document and the information contained herein is provided on an
   "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
   TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
   BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
   HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
   MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
</p>
</div></body></html>