Network Working Group                                         P. Resnick
Internet-Draft                                     QUALCOMM Incorporated
Obsoletes: 2425, 2426, 4770                                 S. Perreault
(if approved)                                                   Viagenie
Updates: 2739 (if approved)                                April 9, 2008
Intended status: Standards Track                          March 17, 2008
Expires: September 18, October 11, 2008

                       vCard Format Specification
                    draft-ietf-vcarddav-vcardrev-00
                    draft-ietf-vcarddav-vcardrev-01

Status of This Memo

   By submitting this Internet-Draft, each author represents that any
   applicable patent or other IPR claims of which he or she is aware
   have been or will be disclosed, and any of which he or she becomes
   aware will be disclosed, in accordance with Section 6 of BCP 79.

   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 in progress."

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/ietf/1id-abstracts.txt.

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html.

   This Internet-Draft will expire on September 18, October 11, 2008.

Copyright Notice

   Copyright (C) The IETF Trust (2008).

Abstract

   This document defines the vCard data format 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.).

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  4  5
   2.  Conventions  . . . . . . . . . . . . . . . . . . . . . . . . .  4  5
   3.  MIME Type Registration . . . . . . . . . . . . . . . . . . . .  4  5
   4.  vCard Format Specification . . . . . . . . . . . . . . . . . .  5  6
     4.1.  Line Delimiting and Folding  . . . . . . . . . . . . . . .  6  7
     4.2.  ABNF Format Definition . . . . . . . . . . . . . . . . . .  6
     4.3.  8
   5.  Property Value Data Types  . . . . . . . . . . . . . . . . . . 10
     5.1.  TEXT . . . . .  8
     4.4.  Pre-defined Parameters . . . . . . . . . . . . . . . . . . 13
   5.  vCard Properties . . . . . . 12
     5.2.  URI  . . . . . . . . . . . . . . . . . 15
     5.1.  General Properties . . . . . . . . . . 12
     5.3.  DATE, TIME, and DATE-TIME  . . . . . . . . . . 15
       5.1.1.  BEGIN . . . . . . 13
     5.4.  BOOLEAN  . . . . . . . . . . . . . . . . . . 15
       5.1.2.  END . . . . . . . 13
     5.5.  INTEGER  . . . . . . . . . . . . . . . . . . 16
       5.1.3.  SOURCE . . . . . . . 14
     5.6.  FLOAT  . . . . . . . . . . . . . . . . . 16
       5.1.4.  NAME . . . . . . . . . 14
     5.7.  BINARY . . . . . . . . . . . . . . . . 17
       5.1.5.  KIND . . . . . . . . . . 14
     5.8.  VCARD  . . . . . . . . . . . . . . . 17
     5.2.  Identification Properties . . . . . . . . . . . 14
     5.9.  UTC-OFFSET . . . . . 18
       5.2.1.  FN . . . . . . . . . . . . . . . . . . . 15
   6.  Property Parameters  . . . . . . . 18
       5.2.2.  N . . . . . . . . . . . . . . 15
     6.1.  LANGUAGE . . . . . . . . . . . . 18
       5.2.3.  NICKNAME . . . . . . . . . . . . . 16
     6.2.  ENCODING . . . . . . . . . . 19
       5.2.4.  PHOTO . . . . . . . . . . . . . . . 16
     6.3.  VALUE  . . . . . . . . . 19
       5.2.5.  BDAY . . . . . . . . . . . . . . . . . 17
     6.4.  UID  . . . . . . . . 20
       5.2.6.  DDAY . . . . . . . . . . . . . . . . . . . 17
     6.5.  TYPE . . . . . . 20
       5.2.7.  BIRTH . . . . . . . . . . . . . . . . . . . . . 18
   7.  vCard Properties . . . 21
       5.2.8.  DEATH . . . . . . . . . . . . . . . . . . . . 18
     7.1.  General Properties . . . . 21
       5.2.9.  GENDER . . . . . . . . . . . . . . . . 18
       7.1.1.  BEGIN  . . . . . . . . 21
     5.3.  Delivery Addressing Properties . . . . . . . . . . . . . . 21
       5.3.1.  ADR . . 18
       7.1.2.  END  . . . . . . . . . . . . . . . . . . . . . . . 21
       5.3.2.  LABEL . . 18
       7.1.3.  SOURCE . . . . . . . . . . . . . . . . . . . . . . 22
     5.4.  Communications Properties . . 19
       7.1.4.  NAME . . . . . . . . . . . . . . 23
       5.4.1.  TEL . . . . . . . . . . . 19
       7.1.5.  KIND . . . . . . . . . . . . . . 23
       5.4.2.  EMAIL . . . . . . . . . . . 20
     7.2.  Identification Properties  . . . . . . . . . . . . . 24
       5.4.3.  IMPP . . . 21
       7.2.1.  FN . . . . . . . . . . . . . . . . . . . . . . 24
       5.4.4.  LANG . . . . 21
       7.2.2.  N  . . . . . . . . . . . . . . . . . . . . . 25
     5.5.  Geographical Properties . . . . . 21
       7.2.3.  NICKNAME . . . . . . . . . . . . 25
       5.5.1.  TZ . . . . . . . . . . . 22
       7.2.4.  PHOTO  . . . . . . . . . . . . . . . 25
       5.5.2.  GEO . . . . . . . . . 22
       7.2.5.  BDAY . . . . . . . . . . . . . . . . 26
     5.6.  Organizational Properties . . . . . . . . . 23
       7.2.6.  DDAY . . . . . . . 26
       5.6.1.  TITLE . . . . . . . . . . . . . . . . . . 23
       7.2.7.  BIRTH  . . . . . . 26
       5.6.2.  ROLE . . . . . . . . . . . . . . . . . . 23
       7.2.8.  DEATH  . . . . . . . 27
       5.6.3.  LOGO . . . . . . . . . . . . . . . . . 23
       7.2.9.  GENDER . . . . . . . . 27
       5.6.4.  AGENT . . . . . . . . . . . . . . . . 24
     7.3.  Delivery Addressing Properties . . . . . . . . 28
       5.6.5.  ORG . . . . . . 24
       7.3.1.  ADR  . . . . . . . . . . . . . . . . . . . 28
     5.7.  Explanatory Properties . . . . . . 24
       7.3.2.  LABEL  . . . . . . . . . . . . 28
       5.7.1.  CATEGORIES . . . . . . . . . . . . 25
     7.4.  Communications Properties  . . . . . . . . . . 29
       5.7.2.  NOTE . . . . . . 25
       7.4.1.  TEL  . . . . . . . . . . . . . . . . . . . 29
       5.7.3.  PRODID . . . . . . 25
       7.4.2.  EMAIL  . . . . . . . . . . . . . . . . . . 29
       5.7.4.  REV . . . . . . 26
       7.4.3.  IMPP . . . . . . . . . . . . . . . . . . . 30
       5.7.5.  SORT-STRING . . . . . . 27
       7.4.4.  LANG . . . . . . . . . . . . . . . 30
       5.7.6.  SOUND . . . . . . . . . . 27
     7.5.  Geographical Properties  . . . . . . . . . . . . . . 31
       5.7.7.  UID . . . 28
       7.5.1.  TZ . . . . . . . . . . . . . . . . . . . . . . 32
       5.7.8.  URL . . . . 28
       7.5.2.  GEO  . . . . . . . . . . . . . . . . . . . . . 32
       5.7.9.  VERSION . . . . 28
     7.6.  Organizational Properties  . . . . . . . . . . . . . . . . 29
       7.6.1.  TITLE  . . . 32
     5.8.  Security Properties . . . . . . . . . . . . . . . . . . . 33
       5.8.1.  CLASS . . 29
       7.6.2.  ROLE . . . . . . . . . . . . . . . . . . . . . . 33
       5.8.2.  KEY . . . 29
       7.6.3.  LOGO . . . . . . . . . . . . . . . . . . . . . . 33
     5.9.  Extended Properties and Parameters . . . 30
       7.6.4.  AGENT  . . . . . . . . . 34
   6.  Formal Grammar . . . . . . . . . . . . . . . 30
       7.6.5.  ORG  . . . . . . . . . 34
   7.  Example: Authors' vCards . . . . . . . . . . . . . . . . 31
     7.7.  Explanatory Properties . . . . . 44
   8.  Security Considerations . . . . . . . . . . . . . 31
       7.7.1.  CATEGORIES . . . . . . 45
   9.  Acknowledgements . . . . . . . . . . . . . . . . 31
       7.7.2.  NOTE . . . . . . . 45
   10. References . . . . . . . . . . . . . . . . . . 32
       7.7.3.  PRODID . . . . . . . . 45
     10.1. Normative References . . . . . . . . . . . . . . . . 32
       7.7.4.  REV  . . . 45
     10.2. Informative References . . . . . . . . . . . . . . . . . . 47
   Appendix A.  Differences from RFCs 2425 and 2426 . . . . 32
       7.7.5.  SORT-STRING  . . . . . 48
     A.1.  New Structure . . . . . . . . . . . . . . . . 33
       7.7.6.  SOUND  . . . . . . . . 48
     A.2.  Removed Features . . . . . . . . . . . . . . . . 33
       7.7.7.  UID  . . . . . 48
     A.3.  New . . . . . . . . . . . . . . . . . . . . 34
       7.7.8.  URL  . . . . . . . . . . . . . . . . . . . . . . . . . 35
       7.7.9.  VERSION  . . . . . . . . . . . . . . . . . . . . . . . 35
     7.8.  Security Properties and Parameters  . . . . . . . . . . . . . . 48
     A.4.  Other Changes . . . . . 35
       7.8.1.  CLASS  . . . . . . . . . . . . . . . . . 49
   Appendix B.  Change Log (to be removed by RFC Editor prior to
                publication) . . . . . . . 35
       7.8.2.  KEY  . . . . . . . . . . . . . 49
     B.1.  Changes in -01 . . . . . . . . . . . . 36
     7.9.  Calendar Properties  . . . . . . . . . . 49

1.  Introduction

   Note: This draft contains much of the same text as 2425 and 2426
   which may not be correct.  Those two RFCs have been merged and the
   structure of this draft is what's new.  Some vCard-specific
   suggestions have been added, but for the most part this is still very
   open.  But we'd like to get feedback on the structure mostly so that
   it may be fixed.

   Electronic address books have become ubiquitous.  Their increased
   presense on portable, connected devices as well as the diversity of
   platforms exchanging contact data call for a standard.  This memo
   defines the vCard format, which allows the capture and exchange of
   information . . . . . . . . . 36
       7.9.1.  FBURL  . . . . . . . . . . . . . . . . . . . . . . . . 36
       7.9.2.  CALADRURI  . . . . . . . . . . . . . . . . . . . . . . 37
       7.9.3.  CAPURI . . . . . . . . . . . . . . . . . . . . . . . . 37
       7.9.4.  CALURI . . . . . . . . . . . . . . . . . . . . . . . . 37
     7.10. Extended Properties and Parameters . . . . . . . . . . . . 38
   8.  Synchronization  . . . . . . . . . . . . . . . . . . . . . . . 38
     8.1.  Mechanisms . . . . . . . . . . . . . . . . . . . . . . . . 38
     8.2.  Example  . . . . . . . . . . . . . . . . . . . . . . . . . 39
   9.  Formal Grammar . . . . . . . . . . . . . . . . . . . . . . . . 40
   10. Example: Authors' vCards . . . . . . . . . . . . . . . . . . . 49
   11. Security Considerations  . . . . . . . . . . . . . . . . . . . 49
   12. IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 50
     12.1. Registering New vCard Elements . . . . . . . . . . . . . . 50
       12.1.1. Registration Procedure . . . . . . . . . . . . . . . . 50
       12.1.2. Vendor Namespace . . . . . . . . . . . . . . . . . . . 51
       12.1.3. Registration Template for Properties . . . . . . . . . 51
       12.1.4. Registration Template for Parameters . . . . . . . . . 52
       12.1.5. Registration Template for Value Data Types . . . . . . 52
       12.1.6. Registration Template for Values . . . . . . . . . . . 52
     12.2. Initial vCard Elements Registries  . . . . . . . . . . . . 53
       12.2.1. Properties Registry  . . . . . . . . . . . . . . . . . 53
       12.2.2. Parameters Registry  . . . . . . . . . . . . . . . . . 55
       12.2.3. Value Data Types Registry  . . . . . . . . . . . . . . 55
   13. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 55
   14. References . . . . . . . . . . . . . . . . . . . . . . . . . . 56
     14.1. Normative References . . . . . . . . . . . . . . . . . . . 56
     14.2. Informative References . . . . . . . . . . . . . . . . . . 58
   Appendix A.  Differences from RFCs 2425 and 2426 . . . . . . . . . 58
     A.1.  New Structure  . . . . . . . . . . . . . . . . . . . . . . 58
     A.2.  Removed Features . . . . . . . . . . . . . . . . . . . . . 59
     A.3.  New Properties and Parameters  . . . . . . . . . . . . . . 59
     A.4.  Other Changes  . . . . . . . . . . . . . . . . . . . . . . 59
   Appendix B.  Change Log (to be removed by RFC Editor prior to
                publication)  . . . . . . . . . . . . . . . . . . . . 59
     B.1.  Changes in -01 . . . . . . . . . . . . . . . . . . . . . . 59
     B.2.  Changes in -00 . . . . . . . . . . . . . . . . . . . . . . 60

1.  Introduction

   Note: This draft contains much of the same text as 2425 and 2426
   which may not be correct.  Those two RFCs have been merged and the
   structure of this draft is what's new.  Some vCard-specific
   suggestions have been added, but for the most part this is still very
   open.  But we'd like to get feedback on the structure mostly so that
   it may be fixed.

   Electronic address books have become ubiquitous.  Their increased
   presense on portable, connected devices as well as the diversity of
   platforms exchanging contact data call for a standard.  This memo
   defines the vCard format, which allows the capture and exchange of
   information normally stored within an address book or directory
   application.

2.  Conventions

   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 [RFC2119].

3.  MIME Type Registration

   To:  ietf-types@iana.org

   Subject:  Registration of media type text/vcard

   Type name:  text

   Subtype name:  vcard

   Required parameters:  none

   Optional parameters:  charset

   Encoding considerations:  The "charset" "charset" MIME parameter is interpreted
      as defined in [RFC2046], section 4.1.2.  If it is omitted, the
      default encoding is UTF-8 as defined in [RFC3629].

   Security considerations:  See Section 11.

   Interoperability considerations:  The text/vcard media type is
      intended to identify vCard data of any version.  There are older
      specifications of vCard [RFC2426][oldreference_VCARD] still in
      common use.  While these formats are similar, they are not
      strictly compatible.  In general, it is necessary to inspect the
      value of the VERSION property (see Section 7.7.9) for identifying
      the standard to which a given vCard object conforms.

      In addition, the following media types are known to have been used
      to refer to vCard data.  They should be considered deprecated in
      favor of text/vcard.

      *  text/directory

      *  text/directory; type=vcard

      *  text/x-vcard

   Published specification:  draft-ietf-vcarddav-vcardrev-01

   Applications that use this media type:  They are numerous, diverse,
      and include mail user agents, instant messaging clients, address
      book applications, directory servers, customer relationship
      management software, etc.

   Additional information:

      Magic number(s):

      File extension(s):  .vcf

      Macintosh file type code(s):

   Person & email address to contact for further information:  Simon
      Perreault <simon.perreault@viagenie.ca>

   Intended usage:  COMMON

   Restrictions on usage:  none

   Author:  Pete Resnick and Simon Perreault

   Change controller:  IETF

4.  vCard Format Specification

   The text/vcard MIME parameter is interpreted content type (hereafter known as defined "vCard")
   contains contact information, typically pertaining to a single
   contact or group of contacts.  The content consists of one or more
   lines in [RFC2046], section 4.1.2.  If it is omitted, the
      default encoding is UTF-8 as defined in [RFC3629].

   Security considerations:  See Section 8.

   Interoperability considerations:  The text/vcard media type is
      intended to identify format given below.

4.1.  Line Delimiting and Folding

   Individual lines within vCard data of any version.  There are older
      specifications delimited by the [RFC2822] line
   break, which is a CRLF sequence (ASCII decimal 13, followed by ASCII
   decimal 10).  Long logical lines of vCard [RFC2426][oldreference_VCARD] still text can be split into a
   multiple-physical-line representation using the following folding
   technique.  Content lines SHOULD be folded to a maximum width of 75
   octets.  Multi-octet characters MUST remain contiguous.  The
   rationale for this folding process can be found in
      common use.  While these formats are similar, they are not
      strictly compatible.  In general, it [RFC2822], Section
   2.1.1.

   A logical line MAY be continued on the next physical line anywhere
   between two characters by inserting a CRLF immediately followed by a
   single white space character (space, ASCII decimal 32, or horizontal
   tab, ASCII decimal 9).  At least one character must be present on the
   folded line.  Any sequence of CRLF followed immediately by a single
   white space character is ignored (removed) when processing the
   content type.  For example the line:

     DESCRIPTION:This is a long description that exists on a long line.

   can be represented as:

     DESCRIPTION:This is necessary to inspect the
      value a long description
      that exists on a long line.

   It could also be represented as:

     DESCRIPTION:This is a long descrip
      tion that exists o
      n a long line.

   The process of the VERSION moving from this folded multiple-line representation
   of a property (see Section 5.7.9) for identifying
      the standard definition to which its single line representation is called
   unfolding.  Unfolding is accomplished by regarding CRLF immediately
   followed by a given vCard object conforms.

      In addition, white space character (namely HTAB ASCII decimal 9 or
   SPACE ASCII decimal 32) as equivalent to no characters at all (i.e.,
   the following media types CRLF and single white space character are known to have been used
      to refer removed).

      Note: It is possible for very simple implementations to vCard data.  They should be considered deprecated generate
      improperly folded lines in
      favor the middle of text/vcard.

      *  text/directory

      *  text/directory; type=vcard

      *  text/x-vcard

   Published specification:  draft-ietf-vcarddav-vcardrev-00

   Applications that use a UTF-8 multi-octet
      sequence.  For this media type:  They are numerous, diverse,
      and include mail user agents, instant messaging clients, address
      book applications, directory servers, customer relationship
      management software, etc.

   Additional information:

      Magic number(s):

      File extension(s):  .vcf

      Macintosh file type code(s):

   Person & email address to contact for further information:  Simon
      Perreault <simon.perreault@viagenie.ca>

   Intended usage:  COMMON

   Restrictions on usage:  none

   Author:  Pete Resnick and Simon Perreault

   Change controller:  IETF

4.  vCard Format Specification

   The text/vcard MIME content type (hereafter known reason, implementations SHOULD unfold lines in
      such a way as "vCard")
   contains contact information, typically pertaining to a single
   contact or group of contacts.  The properly restore the original sequence.

   Folding is done after any content consists encoding of a type value.
   Unfolding is done before any decoding of one or more
   lines a type value in a content
   line.

4.2.  ABNF Format Definition

   The following ABNF uses the format given below.

4.1.  Line Delimiting notation of [RFC5234], which also defines
   CRLF, WSP, DQUOTE, VCHAR, ALPHA, and Folding

   Individual DIGIT.  After the unfolding of
   any folded lines within vCard are delimited by as described above, the [RFC2822] syntax for a line
   break, which of this
   content type is a as follows:

     contentline  = name *(";" param) ":" value CRLF sequence (ASCII decimal 13, followed by ASCII
   decimal 10).  Long logical
        ; When parsing a content line, folded lines of text can MUST first
        ; be split into a
   multiple-physical-line representation using unfolded according to the following folding
   technique.  After unfolding procedure
        ; described above.
        ; When generating a content line, lines longer than 75
        ; characters SHOULD be folded. folded according to the folding
        ; procedure described above.

     name         = x-name / iana-token

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

     x-name       = "x-" 1*(ALPHA / DIGIT / "-")
        ; Names that begin with "x-" or "X-" are
        ; reserved for experimental use, not intended for released
        ; products, or for use in bilateral agreements.

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

     param-name   = x-name / iana-token

     param-value  = ptext / quoted-string

     ptext  = *SAFE-CHAR

     value = *VALUE-CHAR
           / valuespec      ; valuespec defined in section 5.8.4

     quoted-string = DQUOTE *QSAFE-CHAR DQUOTE

     NON-ASCII    = %x80-FF
        ; use 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

   A logical line MAY be continued on the next physical line anywhere
   between two characters by inserting a CRLF immediately followed by that begins with a
   single white space character (space, ASCII decimal 32, or horizontal
   tab, ASCII decimal 9).  At least one character must be present on the
   folded line.  Any sequence of CRLF followed immediately by is a single continuation of
   the previous line, as described above.  The white space character is ignored (removed) and
   immediately preceeding CRLF should be discarded when processing the
   content type.  For example reconstructing
   the line:

     DESCRIPTION:This is a long description original line.  Note that exists on this line-folding convention differs
   from that found in [RFC2822], in that the sequence <CRLF><WSP> found
   anywhere in the content indicates a long line.

   can continued line and should be represented as:

     DESCRIPTION:This
   removed.

   Property names and parameter names are case insensitive (e.g., the
   property name "fn" is a long description
      that exists the same as "FN" and "Fn").  Parameter values
   MAY be case sensitive or case insensitive, depending on their
   definition.

   Each property defined in a long line.

   It could also be represented as:

     DESCRIPTION:This vCard instance MAY have multiple values.
   The general rule for encoding multi-valued properties is to simply
   create a long descrip
      tion new content line for each value (including the property
   name).  However, it should be noted that exists o
      n a long line.

   The process of moving from this folded multiple-line representation
   of some value types support
   encoding multiple values in a property definition to its single content line representation is called
   unfolding.  Unfolding is accomplished by regarding CRLF immediately
   followed separating the
   values with a comma ",".  This approach has been taken for several of
   the content types defined below (date, time, integer, float), for
   space-saving reasons.

5.  Property Value Data Types

   Lists of values are delimited by a white space list delimiter, specified by the
   COMMA character (namely HTAB ASCII decimal 9 or
   SPACE ASCII (ASCII decimal 32) as equivalent to no characters at all (i.e.,
   the CRLF and single white space 44).  A COMMA character are removed).

   Folding is done after any content encoding of in a type value.
   Unfolding is done before any decoding of value
   MUST be escaped with a BACKSLASH character (ASCII decimal 92).

   Compound type value in values are delimited by a content
   line.

4.2.  ABNF Format Definition

   The following ABNF uses the notation of [RFC5234], which also defines
   CRLF, WSP, DQUOTE, VCHAR, ALPHA, and DIGIT.  After the unfolding of
   any folded lines as described above, field delimiter, specified by
   the syntax for SEMI-COLON character (ASCII decimal 59).  A SEMI-COLON in a line
   component of this
   content type is as follows:

   contentline  = name *(";" param) ":" value CRLF
      ; When parsing a content line, folded lines compound property value MUST first
      ; be unfolded according to the unfolding procedure
      ; described above.
      ; When generating escaped with a content line, lines longer than 75
      ; characters SHOULD be folded according to the folding
      ; procedure described above.

   name
   BACKSLASH character (ASCII decimal 92).

   Standard value types are defined below.

     valuespec = x-name  text-list
                / URI               ; from Appendix A of [RFC3986]
                / iana-token

   iana-token   = 1*(ALPHA date-list
                / DIGIT time-list
                / "-")
      ; identifier registered with IANA

   x-name date-time-list
                / boolean
                / integer-list
                / float-list
                / binary
                / vcard
                / utc-offset
                / iana-valuespec

     text-list = "x-" 1*(ALPHA *TEXT-LIST-CHAR *("," *TEXT-LIST-CHAR)

     TEXT-LIST-CHAR = "\\" / DIGIT "\," / "-")
      ; Names that begin with "x-" "\n"
                    / <any VALUE-CHAR except , or "X-" are \ or newline>
         ; reserved for experimental use, not intended for released Backslashes, newlines, and commas must be encoded.
         ; products, \n or for use in bilateral agreements.

   param \N can be used to encode a newline.

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

   param-name date)

     time-list = x-name / iana-token

   param-value time *("," time)

     date-time-list = ptext date "T" time *("," date "T" time)

     boolean = "TRUE" / quoted-string

   ptext "FALSE"

     integer-list = *SAFE-CHAR

   value integer *("," integer)

     integer = *VALUE-CHAR [sign] 1*DIGIT

     float-list = float *("," float)

     float = [sign] 1*DIGIT ["." 1*DIGIT]

     sign = "+" / valuespec      ; valuespec "-"

     binary = <A "B" binary encoded string as defined in section 5.8.4

   contentline by [RFC2047].>

     vcard = name *(";" param) ":" value CRLF
      ; When parsing a content line, folded lines MUST first
      ; be unfolded according to the unfolding procedure
      ; described above.
      ; When generating a content line, lines longer than 75
      ; characters SHOULD be folded according to the folding
      ; procedure described above.

   name <vCard data encoded as specified below.>

     date = x-name / iana-token

   iana-token date-fullyear ["-"] date-month ["-"] date-mday

     date-fullyear = 4 DIGIT

     date-month = 2 DIGIT     ;01-12

     date-mday = 2 DIGIT      ;01-28, 01-29, 01-30, 01-31
                              ;based on month/year

     time = time-hour [":"] time-minute [":"] time-second [time-secfrac]
             [time-zone]

     time-hour = 1*(ALPHA / 2 DIGIT / "-")
      ; identifier registered with IANA

   x-name      ;00-23

     time-minute = "x-" 1*(ALPHA / 2 DIGIT / "-")
      ; Names that begin with "x-" or "X-" are
      ; reserved for experimental use, not intended for released
      ; products, or for use in bilateral agreements.

   param    ;00-59

     time-second = param-name "=" param-value *("," param-value)
   param-name 2 DIGIT    ;00-60 (leap second)

     time-secfrac = x-name / iana-token

   param-value "," 1*DIGIT

     time-zone = ptext "Z" / quoted-string

   ptext time-numzone

     time-numzome = *SAFE-CHAR

   value sign time-hour [":"] time-minute
     utc-offset = *VALUE-CHAR ("+" / valuespec      ; valuespec "-") time-hour ":" time-minute

     iana-valuespec = <a publicly-defined valuetype format, registered
                       with IANA, as defined in section 5.8.4

   A line that begins with a white space character is a continuation 15 of
   the previous line, as described above. this
                       document>

5.1.  TEXT

   "text": The white space character and
   immediately preceeding CRLF "text" value type should be discarded when reconstructing
   the original line.  Note that this line-folding convention differs
   from that found in [RFC2822], in used to identify values that the sequence <CRLF><WSP> found
   anywhere
   contain human-readable text.  The character set in which the content indicates a continued line and should be
   removed.

   Property names and parameter names are case insensitive (e.g., the
   property name "fn" text is
   represented is controlled by the same as "FN" and "Fn").  Parameter values
   MAY be case sensitive or case insensitive, depending on their
   definition.

   Each property defined in a vCard instance MAY have multiple values.
   The general rule for encoding multi-valued properties "charset" MIME type parameter.  Note
   that there is no way to simply
   create override this parameter on a new content line per-property
   basis.  As for each value (including the property
   name).  However, language, it should be noted that some value types support
   encoding multiple values is controlled by the "language"
   property parameter defined in Section 6.1.

   Examples for "text":

       this is a text value
       this is one value,this is another
       this is a single content line by separating the
   values value\, with a comma ",".  This approach has been taken for several of
   the content types defined below (date, time, integer, float), for
   space-saving reasons.

4.3.  Value Types

   Lists of values are delimited by a list delimiter, specified by the
   COMMA character (ASCII decimal 44). encoded

   A COMMA character formatted text line break in a text value type MUST be escaped with a BACKSLASH represented
   as the character sequence backslash (ASCII decimal 92).

   Compound type values are delimited 92) followed by a field delimiter, specified by
   the SEMI-COLON character
   Latin small letter n (ASCII decimal 59).  A SEMI-COLON in a
   component of a compound property value MUST be escaped with 110) or a
   BACKSLASH character Latin capital letter N
   (ASCII decimal 92).

   Standard value types are defined below.

     valuespec =  text-list
                / URI               ; from Appendix A of [RFC3986]
                / date-list
                / time-list
                / date-time-list
                / boolean
                / integer-list
                / float-list
                / binary
                / vcard
                / phone-number
                / utc-offset
                / iana-valuespec

     text-list = *TEXT-LIST-CHAR *("," *TEXT-LIST-CHAR)

     TEXT-LIST-CHAR = "\\" / "\," / 78), that is "\n"
                    / <any VALUE-CHAR except , or \ or newline>
         ; Backslashes, newlines, and commas must "\N".

   For example a multiple line DESCRIPTION value of:

       Mythical Manager
       Hyjinx Software Division
       BabsCo, Inc.

   could be encoded.
         ; represented as:

       DESCRIPTION:Mythical Manager\nHyjinx Software Division\n
        BabsCo\, Inc.\n

   demonstrating the \n or \N can literal formatted line break technique, the
   CRLF-followed-by-space line folding technique, and the backslash
   escape technique.

5.2.  URI

   "uri": The "uri" value type should be used to encode a newline.

     date-list = date *("," date)

     time-list = time *("," time)

     date-time-list = date "T" time *("," date "T" time)

     boolean = "TRUE" / "FALSE"

     integer-list = integer *("," integer)

     integer = [sign] 1*DIGIT

     float-list = float *("," float)

     float = [sign] 1*DIGIT ["." 1*DIGIT]

     sign = "+" / "-"

     binary = <A "B" binary encoded string as defined identify values that
   are referenced by [RFC2047].>

     vcard = <vCard data a URI (including a Content-ID URI), instead of
   encoded as specified below.>

     phone-number = <A telephone number as defined in
                     [CCITT.E163.1988] and [CCITT.X121.1988]>

     date = date-fullyear ["-"] date-month ["-"] date-mday

     date-fullyear = 4 DIGIT

     date-month = 2 DIGIT     ;01-12
     date-mday = 2 DIGIT      ;01-28, 01-29, 01-30, 01-31
                              ;based on month/year

     time = time-hour [":"] time-minute [":"] time-second [time-secfrac]
             [time-zone]

     time-hour = 2 DIGIT      ;00-23

     time-minute = 2 DIGIT    ;00-59

     time-second = 2 DIGIT    ;00-60 (leap second)

     time-secfrac = "," 1*DIGIT

     time-zone = "Z" / time-numzone

     time-numzome = sign time-hour [":"] time-minute

     utc-offset = ("+" / "-") time-hour ":" time-minute

     iana-valuespec = <a publicly-defined valuetype format, registered
                       with IANA, in-line.  These value references might be used if the value
   is too large, or otherwise undesirable to include directly.  The
   format for the URI is as defined in section 15 [RFC3986].  Note that the value
   of this
                       document>

   Some specific notes on a property of type "uri" is what the URI points to, not the URI
   itself.

   Examples for "uri":

       http://www.example.com/my/picture.jpg
       ldap://ldap.example.com/cn=babs%20jensen

5.3.  DATE, TIME, and DATE-TIME

   "date", "time", and "date-time": Each of these value types is based
   on a subset of the definitions in [ISO.8601.1988] standard.  Multiple
   "date" and formats:

   "text": "time" values can be specified using the comma-separated
   notation.

   Examples for "date":

       1985-04-12
       1996-08-05,1996-11-11
       19850412

   Examples for "time":

       10:22:00
       102200
       10:22:00.33
       10:22:00.33Z
       10:22:33,11:22:00
       10:22:00-08:00

   Examples for "date-time":

       1996-10-22T14:00:00Z
       1996-08-11T12:34:56Z
       19960811T123456Z
       1996-10-22T14:00:00Z,1996-08-11T12:34:56Z

5.4.  BOOLEAN

   "boolean": The "text" "boolean" value type should be is used to identify express boolen values.
   These values that
   contain human-readable text. are case insensitive.

   Examples:

       TRUE
       false
       True

5.5.  INTEGER

   "integer": The character set "integer" value type is used to express signed
   integers in which decimal format.  If sign is not specified, the text value is
   represented
   assumed positive "+".  Multiple "integer" values can be specified
   using the comma-separated notation.

   Examples:

       1234567890
       -1234556790
       +1234556790,432109876

5.6.  FLOAT

   "float": The "float" value type is controlled by used to express real numbers.  If
   sign is not specified, the "charset" MIME value is assumed positive "+".  Multiple
   "float" values can be specified using the comma-separated notation.

   Examples:

       20.30
       1000000.0000001
       1.333,3.14

5.7.  BINARY

   "binary": The "binary" value type parameter.  Note specifies that there the type value is no way to override this parameter on a per-property
   basis.  As for
   inline, encoded binary data.  This value type can be specified in the language, it
   PHOTO, LOGO, SOUND, and KEY types.

   If inline encoded binary data is controlled by specified, the "language"
   property 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 Section 4.4.

   Examples for "text":

       this is a text 4.1.

5.8.  VCARD

   "vcard": The "vcard" value type specifies that the type value
       this is one value,this is
   another
       this is a single value\, with a comma encoded

   A formatted text line break vCard.  This value type can be specified in the AGENT
   property.  The value type is defined by this specification.  Since
   each of the type declarations within the vcard value type are being
   specified within a text value type themselves, they MUST be represented
   as terminated
   with the backslash escape sequence "\n" or "\N", instead of the
   normal newline character sequence backslash CRLF.  In addition, any COMMA
   character (ASCII decimal 92) followed by a
   Latin small letter n 44), SEMI-COLON character (ASCII decimal 110) or a Latin capital letter N 59)
   and COLON character (ASCII decimal 78), that is "\n" or "\N". 58) MUST be escaped with the
   BACKSLASH character (ASCII decimal 92).  For example example, with the AGENT
   property a multiple line DESCRIPTION value of:

       Mythical Manager
       Hyjinx Software Division
       BabsCo, Inc.

   could would be represented specified as:

       DESCRIPTION:Mythical Manager\nHyjinx Software Division\n
        BabsCo\, Inc.\n

   demonstrating the \n literal formatted line break technique,

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

5.9.  UTC-OFFSET

   "utc-offset": The "utc-offset" value type specifies that the
   CRLF-followed-by-space line folding technique, and type
   value is a signed offset from UTC.  This value type can be specified
   in the backslash
   escape technique.

   "uri": TZ type.

   The "uri" value type should 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 to identify values that
   are referenced by used.  The extended format makes use of a URI (including colon
   character as a Content-ID URI), instead separator of
   encoded in-line. the hour and minute text fields.

6.  Property Parameters

   A property can have attributes associated with it.  These value references might "property
   parameters" contain meta-information about the property or the
   property value.

   Property parameter values that contain the COLON (US-ASCII decimal
   58), SEMICOLON (US-ASCII decimal 59) or COMMA (US-ASCII decimal 44)
   character separators MUST be used if specified as quoted-string text values.
   Property parameter values MUST NOT contain the value DQUOTE (US-ASCII
   decimal 22) character.  The DQUOTE (US-ASCII decimal 22) character is too large,
   used as a delimiter for parameter values that contain restricted
   characters or otherwise undesirable to include directly. URI text.  For example:

     FN;UID="urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6":Jane Doe

   Property parameter values that are not in quoted strings are case
   insensitive.

   The
   format for general property parameters defined by this memo are defined by
   the URI is following notation:

          vcardparameter = encodingparam
                         / valuetypeparam
                         / languageparam
                         / uidparam

          encodingparam = "encoding" "=" encodingtype

          encodingtype = "b"       ; from [RFC2047]
                     / iana-token  ; registered as defined described in [RFC3986].  Note that the value
   of a property
                                   ; section 15 of type this document

          valuetypeparam = "value" "=" valuetype

          valuetype = "uri" is what the URI points to, not the        ; URI
   itself.

   Examples for "uri":

       http://www.foobar.com/my/picture.jpg
       ldap://ldap.foobar.com/cn=babs%20jensen

   "date", "time", and "date-time": Each from Appendix A of these value types [RFC3986]
                     / "text"
                     / "date"
                     / "time"
                     / "date-time" ; date time
                     / "integer"
                     / "boolean"
                     / "float"
                     / x-name
                     / iana-token  ; registered as described in
                                   ; section 15 of this document

          languageparam = "language" "=" Language-Tag
              ; Language-Tag is based
   on a subset defined in section 2.1 of RFC 4646

          uidparam = "uid" "=" URI  ; from Appendix A of the definitions in [ISO.8601.1988] standard.  Multiple
   "date" [RFC3986]

   Applications MUST ignore x-param and "time" values can be specified using the comma-separated
   notation.

   Examples for "date":

       1985-04-12
       1996-08-05,1996-11-11
       19850412

   Examples for "time":

       10:22:00
       102200
       10:22:00.33
       10:22:00.33Z
       10:22:33,11:22:00
       10:22:00-08:00
   Examples for "date-time":

       1996-10-22T14:00:00Z
       1996-08-11T12:34:56Z
       19960811T123456Z
       1996-10-22T14:00:00Z,1996-08-11T12:34:56Z

   "boolean": The "boolean" iana-param value type is used to express boolen values.
   These values are case insensitive.

   Examples:

       TRUE
       false
       True

   "integer": they don't
   recognize.

6.1.  LANGUAGE

   The "integer" value type "language" property parameter is used to express signed
   integers identify data in decimal format.  If sign is not specified, the value
   multiple languages.  There is
   assumed positive "+".  Multiple "integer" values can be no concept of "default" language,
   except as specified
   using the comma-separated notation.

   Examples:

       1234567890
       -1234556790
       +1234556790,432109876

   "float": by any "Content-Language" MIME header parameter
   that is present.  The "float" value type of the "language" property parameter is a
   language tag as defined in Section 2 of [RFC4646].

6.2.  ENCODING

   The "encoding" property parameter is used to express real numbers. specify an alternate
   encoding for a value.  If
   sign is not specified, the value is assumed positive "+".  Multiple
   "float" values can be specified using the comma-separated notation.

   Examples:

       20.30
       1000000.0000001
       1.333,3.14

   "binary": The "binary" value type specifies that the type value is
   inline, encoded binary data.  This value type can contains a CRLF, it must be specified in the
   PHOTO, LOGO, SOUND, and KEY types.

   If inline encoded binary data
   encoded, since CRLF is specified, the ENCODING type
   parameter MUST be used to specify separate lines in the content-type
   itself.  Currently, only the "b" encoding format. is supported.

   The binary
   data MUST "b" encoding can also be encoded using useful for binary values that are mixed
   with other text information in the "B" body part (e.g., a certificate).
   Using a per-value "b" encoding format.  Long lines of
   encoded binary data SHOULD BE folded to 75 characters using in this case leaves the
   folding method defined other
   information in Section 4.1.

   "vcard": a more readable form.  The "vcard" value type specifies that the type value is
   another vCard.  This encoded base 64 value type can
   be specified in split across multiple physical lines by using the AGENT
   property. line folding
   technique described above.

   The value type Content-Transfer-Encoding header field is defined by this specification.  Since
   each of used to specify the type declarations within
   encoding used for the vcard value type are being
   specified within body part as a text whole.  The "encoding" property
   parameter is used to specify an encoding for a particular value themselves, they MUST be terminated
   with
   (e.g., a certificate).  In this case, the backslash escape sequence "\n" or "\N", instead of Content-Transfer-Encoding
   header might specify "8bit", while the
   normal newline character sequence CRLF.  In addition, any COMMA
   character (ASCII decimal 44), SEMI-COLON character (ASCII decimal 59) one certificate value might
   specify an encoding of "b" via an "encoding=b" property parameter.

   The Content-Transfer-Encoding and COLON character (ASCII decimal 58) MUST be escaped with the
   BACKSLASH character (ASCII decimal 92).  For example, with encodings of individual
   properties given by the AGENT "encoding" property parameter are independent
   of one another.  When encoding 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

   "phone-number": text/vcard body part for
   transmission, individual property encodings are performed first, then
   the entire body part is encoded according to the Content-Transfer-
   Encoding.  When decoding a text/vcard body part, the Content-
   Transfer-Encoding is decoded first, and then any individual
   properties with an "encoding" property parameter are decoded.

6.3.  VALUE

   The "phone-number" "value" parameter is optional, and is used to identify the value
   type specifies that (data type) and format of the value.  The use of these
   predefined formats is encouraged even if the type value parameter is not
   explicity used.  By defining a telephone number.  This standard set of value type types and their
   formats, existing parsing and processing code can be specified in the
   TEL type. leveraged.  The value
   predefined data type is a text values MUST NOT be repeated in COMMA separated
   value that has lists except within the special
   semantics of a telephone number as defined in [CCITT.E163.1988] N, NICKNAME, ADR and
   [CCITT.X121.1988].

   "utc-offset": The "utc-offset" CATEGORIES
   properties.

   Including the value type specifies that explicitly as part of each property provides
   an extra hint to keep parsing simple and support more generalized
   applications.  For example a search engine would not have to know the type
   particular value types for all of the items for which it is a signed offset from UTC.  This value type can be specified
   in
   searching.  Because the TZ type.

   The value type is an offset from Coordinated Universal Time (UTC).
   It is specified as a positive or negative difference explicit in units of
   hours the definition, the
   search engine could look for dates in any item type and minutes (e.g., +hh:mm). provide
   results that can still be interpreted.

6.4.  UID

   The time "uid" parameter is specified as a 24-hour
   clock.  Hour values are from 00 used to 23, and minute values are from 00 uniquely identify the property.  It
   plays a role analogous to 59.  Hour the UID property (Section 7.7.7) on a per-
   property instead of per-vCard basis.  It MUST NOT appear more than
   once in a given property, and minutes are 2-digits with high order zeroes required
   to maintain digit count.  The extended format for ISO 8601 UTC
   offsets MUST be present if synchronization is
   to be used.  See Section 8.

6.5.  TYPE

   The extended format makes use of "type" parameter has multiple, different uses.  In general, it is
   a colon
   character as way of specifying class characteristics of the associated property.
   Most of the time, its value is a separator comma-separated subset of a pre-
   defined enumeration.  In this document, the hour and minute text fields.

4.4.  Pre-defined Parameters

   The following parameters are defined for general use.

         predefined-param = encodingparm
                          / valuetypeparm
                          / languageparm

         encodingparm = "encoding" "=" encodingtype

         encodingtype = "b"       ; from [RFC2047]
                    / iana-token  ; registered as described in
                                  ; section 15 properties make
   use of this document

         predefined-param = encodingparm
                          / valuetypeparm
                          / languageparm

         encodingparm = "encoding" "=" encodingtype

         encodingtype = "b"       ; from [RFC2047]
                    / iana-token  ; registered as described in
                                  ; section 15 parameter: PHOTO, ADR, LABEL, TEL, EMAIL, IMPP, LOGO,
   SOUND, and KEY.

7.  vCard Properties

   What follows is an enumeration of this document

         predefined-param = encodingparm
                          / valuetypeparm
                          / languageparm

         encodingparm = "encoding" "=" encodingtype

         encodingtype = "b"       ; from [RFC2047]
                    / iana-token  ; registered as described in
                                  ; section 15 the standard vCard properties.

7.1.  General Properties

7.1.1.  BEGIN

   Purpose:  To denote the beginning of this document a syntactic entity within a
      text/vcard content-type.

   Value type:  text

   Special notes:  The "language" content entity MUST begin with the BEGIN property
      with a value of "VCARD".

      The BEGIN property parameter is used in conjunction with the END property to identify data
      delimit an entity containing a related set of properties within an
      text/vcard content-type.  This construct can be used instead of or
      in addition to wrapping separate sets of information inside
      additional MIME headers.  It is provided for applications that
      wish to define content that can contain multiple languages.  There is no concept entities within
      the same text/vcard content-type or to define content that can be
      identifiable outside of "default" language,
   except as specified by any "Content-Language" a MIME header parameter
   that is present.  The value environment.

   Example:

         BEGIN:VCARD

7.1.2.  END

   Purpose:  To denote the end of a syntactic entity within a text/vcard
      content-type.

   Value type:  text

   Special notes:  The content entity MUST end with the "language" property parameter is END type with a
   language tag as defined in Section 2
      value of [RFC4646]. "VCARD".

      The "encoding" END property parameter is used in conjunction with the BEGIN property to specify
      delimit an alternate
   encoding for a value.  If the value contains entity containing a CRLF, it must related set of properties within an
      text/vcard content-type.  This construct can be
   encoded, since CRLF is used instead of or
      in addition to wrapping separate lines in the content-type
   itself.  Currently, only the "b" encoding sets of information inside
      additional MIME headers.  It is supported.

   The "b" encoding can also be useful provided for binary values applications that
      wish to define content that are mixed
   with other text information in the body part (e.g., a certificate).
   Using a per-value "b" encoding in this case leaves the other
   information in a more readable form.  The encoded base 64 value can
   be split across contain multiple physical lines by using entities within
      the line folding
   technique described above.

   The Content-Transfer-Encoding header field is used same text/vcard content-type or to specify the
   encoding used for the body part as define content that can be
      identifiable outside of a whole. MIME environment.

   Example:

         END:VCARD

7.1.3.  SOURCE

   Purpose:  To identify the source of directory information contained
      in the content type.

   Value type:  uri

   Special notes:  The "encoding" SOURCE property
   parameter is used to specify an encoding for a particular value
   (e.g., a certificate).  In this case, the Content-Transfer-Encoding
   header might specify "8bit", while provide the one certificate value might
   specify an encoding of "b" via an "encoding=b" property parameter.

   The Content-Transfer-Encoding and means by
      which applications knowledgable in the encodings of individual
   properties given by directory service
      protocol can obtain additional or more up-to-date information from
      the "encoding" property parameter are independent
   of one another.  When encoding directory service.  It contains a text/vcard body part for
   transmission, individual property encodings are performed first, then URI as defined in [RFC3986]
      and/or other information referencing the entire body part is encoded according vCard to which the Content-Transfer-
   Encoding.
      information pertains.  When decoding a text/vcard body part, the Content-
   Transfer-Encoding is decoded first, and then any individual
   properties with an "encoding" property parameter are decoded.

   The "value" parameter is optional, and is used to identify the value
   type (data type) and format of the value.  The use of these
   predefined formats directory information is encouraged even if available
      from more than one source, the value parameter is not
   explicity used.  By defining a standard set of value types and their
   formats, existing parsing and processing code sending entity can pick what it
      considers to be leveraged.  The
   predefined data type values MUST NOT be repeated in COMMA separated
   value lists except within the N, NICKNAME, ADR and CATEGORIES
   properties.

   Including best source, or multiple SOURCE properties can
      be included.

   Examples:

     SOURCE:ldap://ldap.example.com/cn=Babs%20Jensen,%20o=Babsco,%20c=US

     SOURCE:http://directory.example.com/addressbooks/jdoe/
      Jean%20Dupont.vcf

7.1.4.  NAME
   Purpose:  To identify the value type explicitly as part displayable name of each property provides
   an extra hint the directory entity to keep parsing simple and support more generalized
   applications.  For example a search engine would not have
      which information in the vCard pertains.

   Value type:  text

   Special notes:  The NAME property is used to know convey the
   particular value types for all display name
      of the items for entity to which it is
   searching.  Because the directory information pertains.  Its
      value type is explicit in the definition, displayable, presentation text associated with the
   search engine could look
      source for dates the vCard, as specified in any item type and provide
   results that can still be interpreted.

5. the SOURCE property.

   Example:

         NAME:Babs Jensen's Contact Information

7.1.5.  KIND

   Purpose:  To specify the kind of object the vCard Properties

   What follows is represents.

   Value type:  A single text value.

   Special notes:  The value may be one of: "individual" for a single
      person, "group" for a group of people, "org" for an enumeration organization,
      an x-name or an iana-token.  If this property is absent,
      "individual" MUST be assumed as default.

   Example:

      This represents someone named Jane Doe working in the marketing
      department of the standard vCard properties.

5.1.  General North American division of ABC Inc.

         BEGIN:VCARD
         VERSION:4.0
         KIND:individual
         FN:Jane Doe
         ORG:ABC\, Inc.;North American Division;Marketing
         END:VCARD

      This represents the department itself, commonly known as ABC
      Marketing.

         BEGIN:VCARD
         VERSION:4.0
         KIND:org
         FN:ABC Marketing
         ORG:ABC\, Inc.;North American Division;Marketing
         END:VCARD

7.2.  Identification Properties

5.1.1.  BEGIN

   These types are used to capture information associated with the
   identification and naming of the person or resource associated with
   the vCard.

7.2.1.  FN

   Purpose:  To denote specify the beginning of a syntactic entity within a
      text/vcard content-type. formatted text corresponding to the name of
      the object the vCard represents.

   Value type:  A single text value.

   Special notes:  The content entity MUST begin with the BEGIN  This property
      with a value of "VCARD".

      The BEGIN type is used in conjunction with based on the END type to delimit
      an entity containing a related set semantics of properties within an text/
      vcard content-type.  This construct can the X.520
      Common Name attribute.  The property MUST be used instead of or present in
      addition to wrapping separate sets of information inside
      additional MIME headers.  It is provided for applications that
      wish to define content that can contain multiple entities within the same text/vcard content-type or to define content that can be
      identifiable outside of a MIME environment. vCard
      object.

   Example:

         BEGIN:VCARD

5.1.2.  END

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

7.2.2.  N

   Purpose:  To denote specify the end components of a syntactic entity within a text/vcard
      content-type. the name of the object the
      vCard represents.

   Value type:  A single structured text value.  Each component can have
      multiple values.

   Special notes: note:  The content entity MUST end with the END type with a structured property value of "VCARD".

      The END type is used in conjunction with the BEGIN type to delimit
      an entity containing a related set of properties within an text/
      vcard content-type.  This construct can be used instead of or corresponds, in
      addition to wrapping separate sets of information inside
      additional MIME headers.  It is provided for applications that
      wish
      sequence, to define content that can contain multiple entities within the same text/vcard content-type or to define content that 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 property is based on the semantics of the X.520
      individual name attributes.  The property SHOULD be
      identifiable outside present in the
      vCard object when the name of a MIME environment.

   Example:

         END:VCARD

5.1.3.  SOURCE the object the vCard represents
      follows the X.520 model.

   Examples:

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

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

7.2.3.  NICKNAME

   Purpose:  To identify specify the source text corresponding to the nickname of directory information contained
      in the content type.
      object the vCard represents.

   Value type:  uri  One or more text values separated by a COMMA character
      (ASCII decimal 44).

   Special notes: note:  The SOURCE property nickname is used to provide the means by
      which applications knowledgable in the descriptive name given directory service
      protocol can obtain additional instead of
      or more up-to-date information from
      the directory service.  It contains a URI as defined in [RFC3986]
      and/or other information referencing the vCard addition to which the
      information pertains.  When directory information is available
      from more than one source, the sending entity can pick what it
      considers belonging to be the best source, a person, place, or multiple SOURCE properties thing.
      It can also be included. used to specify a familiar form of a proper name
      specified by the FN or N properties.

   Examples:

         SOURCE:ldap://ldap.host/cn=Babs%20Jensen,%20o=Babsco,%20c=US

         SOURCE:http://directory.example.com/addressbooks/jdoe/
          Jean%20Dupont.vcf

5.1.4.  NAME

             NICKNAME:Robbie

             NICKNAME:Jim,Jimmie

7.2.4.  PHOTO

   Purpose:  To identify the displayable name specify an image or photograph information that
      annotates some aspect of the directory entity object the vCard represents.

   Encoding:  The encoding MUST be reset to
      which information "b" using the ENCODING
      parameter in order to specify inline, encoded binary data.  If the vCard pertains.
      value is referenced by a URI value, then the default encoding is
      used and no explicit ENCODING parameter is needed.

   Value type:  text

   Special notes:  A single value.  The NAME property default is binary value.  It can
      also be reset to uri value.  The uri value can be used to convey the display name specify
      a value outside of this MIME entity.

   Special notes:  This property SHOULD include the entity parameter "TYPE" to which
      specify the directory information pertains.  Its graphic image format type.  The TYPE parameter value is the displayable, presentation text associated with the
      source for the vCard,
      MUST be an image media type as specified in [RFC4288].  The full
      media type name, including the SOURCE property. "image/" prefix, should be used.
      However, implementations SHOULD be able to handle bare subtypes.

   Example:

         NAME:Babs Jensen's Contact Information

5.1.5.  KIND

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

       PHOTO;ENCODING=b;TYPE=image/jpeg:MIICajCCAdOgAwIBAgICBEUwDQYJKo
        ZIhvcNAQEEBQAwdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05ldHNjYXBlIENv
        bW11bmljYXRpb25zIENvcnBvcmF0aW9uMRwwGgYDVQQLExNJbmZvcm1hdGlvbi
        <...remainder of "B" encoded binary data...>

7.2.5.  BDAY

   Purpose:  To specify the kind birth date of the object the vCard
      represents.

   Value type:  A  The default is a single text date value.

   Special notes:  The value may  It can also be one of: "individual" for
      reset to a single
      person, "group" for a group of people, "org" for an organization,
      an x-name date-time or an iana-token.  If this property is absent,
      "individual" MUST be assumed as default.

   Example:

      This represents someone named Jane Doe working in text value.

   Examples:

             BDAY:1996-04-15

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

             BDAY;VALUE=text:circa 1800

7.2.6.  DDAY

   Purpose:  To specify the marketing
      department date of the North American division death of ABC Inc.

         BEGIN:VCARD
         VERSION:4.0
         KIND:individual
         FN:Jane Doe
         ORG:ABC\, Inc.;North American Division;Marketing
         END:VCARD

      This represents the department itself, commonly known as ABC
      Marketing.

         BEGIN:VCARD
         VERSION:4.0
         KIND:org
         FN:ABC Marketing
         ORG:ABC\, Inc.;North American Division;Marketing
         END:VCARD

5.2.  Identification Properties

   These types are used to capture information associated with the
   identification and naming of object the person vCard
      represents.

   Value type:  The default is a single date value.  It can also be
      reset to a single date-time or resource associated with
   the vCard.

5.2.1.  FN text value.

7.2.7.  BIRTH

   Purpose:  To specify the formatted text corresponding to the name place of birth of the object the vCard
      represents.

   Value type:  A single text value.

   Special notes:  This property is based on

   Example:

             BIRTH:Babies'R'Us Hospital

7.2.8.  DEATH

   Purpose:  To specify the semantics place of death of the X.520
      Common Name attribute.  The property MUST be present in object the vCard
      object.
      represents.

   Value type:  A single text value.

   Example:

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

5.2.2.  N

             DEATH:Aboard the Titanic\, near Newfoundland

7.2.9.  GENDER

   Purpose:  To specify the components of the name gender of the object the vCard represents.

   Value type:  A single structured text value.  Each component can have
      multiple values.

   Special note: notes:  The structured type value corresponds, in sequence, "M" stands for male while "F" stands for
      female.

   Example:

             GENDER:F

7.3.  Delivery Addressing Properties

   These types are concerned with information related to the Family Name, Given Name, Additional Names, Honorific Prefixes,
      and Honorific Suffixes.  The text components are separated by delivery
   addressing or label for the vCard object.

7.3.1.  ADR

   Purpose:  To specify the
      SEMI-COLON character (ASCII decimal 59).  Individual text components can include multiple of the delivery address for the
      vCard object.

   Value type:  A single structured text values (e.g., multiple
      Additional Names) value, separated by the COMMA SEMI-
      COLON character (ASCII decimal
      44).  This 59).

   Special notes:  The structured type is based on the semantics value consists of the X.520 individual
      name attributes. a sequence of
      address components.  The property SHOULD component values MUST be present specified in
      their corresponding position.  The structured type value
      corresponds, in sequence, to the vCard
      object when post office box; the name of extended
      address (e.g. apartment or suite number); the object street address; the vCard represents follows
      locality (e.g., city); the X.520 model.

   Examples:

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

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

5.2.3.  NICKNAME

   Purpose:  To specify region (e.g., state or province); the text corresponding to
      postal code; the nickname of country name.  When a component value is missing,
      the
      object associated component separator MUST still be specified.

      The text components are separated by the vCard represents.

   Value type:  One or more 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 a the COMMA character
      (ASCII decimal 44).

   Special note:

      The nickname is type can include the descriptive name given instead of
      or in addition type parameter "TYPE" to specify the one belonging to a person, place, or thing.
      It
      delivery address type.  The TYPE parameter values can also be used include
      "home" to specify indicate a familiar form of delivery address for a proper name
      specified by the FN or N types.

   Examples:

             NICKNAME:Robbie

             NICKNAME:Jim,Jimmie

5.2.4.  PHOTO

   Purpose:  To specify an image or photograph information that
      annotates some aspect residence; "work" to
      indicate delivery address for a place of the object the vCard represents.

   Encoding:  The encoding MUST be reset work; and "pref" to "b" using
      indicate the ENCODING preferred delivery address when more than one address
      is specified.  These type parameter in order to specify inline, encoded binary data.  If the values can be specified as a
      parameter list (i.e., "TYPE=home;TYPE=pref") or as a value list
      (i.e., "TYPE=home,pref").  This type is referenced by a URI value, then based on semantics of the
      X.520 geographical and postal addressing attributes.  The default encoding
      is
      used "TYPE=work".

   Example: In this example the post office box and no explicit ENCODING parameter is needed. the extended address
   are absent.

           ADR;TYPE=home:;;123 Main Street;Any Town;CA;91921-1234

7.3.2.  LABEL

   Purpose:  To specify the formatted text corresponding to delivery
      address of the object the vCard represents.

   Value type:  A single text value.

   Special notes:  The default is binary value.  It can
      also be reset to uri value.  The uri property value is formatted text that can be used
      to specify present a value outside of this MIME entity.

   Special notes:  This property SHOULD delivery address label for the vCard object.  The
      type can include the type parameter "TYPE" to specify the graphic image format delivery
      label type.  The TYPE parameter value
      MUST be an image media type as specified in [RFC4288].  The full
      media type name, including the "image/" prefix, should be used.
      However, implementations SHOULD be able values can include "home" to handle bare subtypes.

   Example:

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

       PHOTO;ENCODING=b;TYPE=image/jpeg:MIICajCCAdOgAwIBAgICBEUwDQYJKo
        ZIhvcNAQEEBQAwdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05ldHNjYXBlIENv
        bW11bmljYXRpb25zIENvcnBvcmF0aW9uMRwwGgYDVQQLExNJbmZvcm1hdGlvbi
        <...remainder of "B" encoded binary data...>

5.2.5.  BDAY

   Purpose:  To specify the birth date of the object the vCard
      represents.

   Value type:  The default is
      indicate a single date value.  It can also be
      reset delivery label for a residence; "work" to indicate
      delivery label for a single date-time or text value.

   Examples:

             BDAY:1996-04-15

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

             BDAY;VALUE=text:circa 1800

5.2.6.  DDAY

   Purpose:  To specify the date of death place of work; and "pref" to indicate the object the vCard
      represents.

   Value type:  The default
      preferred delivery label when more than one label is a single date value.  It specified.
      These type parameter values can also be
      reset to specified as a single date-time parameter list
      (i.e., "TYPE=home;TYPE=pref") or text value.

5.2.7.  BIRTH

   Purpose:  To specify the place of birth of the object the vCard
      represents.

   Value type:  A single text value. as a value list (i.e.,
      "TYPE=home,pref").  The default is "TYPE=work".

   Example:

             BIRTH:Babies'R'Us Hospital

5.2.8.  DEATH

   Purpose:  To specify A multi-line address label.

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

7.4.  Communications Properties

   These properties are concerned with information associated with the place of death of
   way communications with the object the vCard
      represents.

   Value type:  A single text value.

   Example:

             DEATH:Aboard the Titanic\, near Newfoundland

5.2.9.  GENDER represents are carried
   out.

7.4.1.  TEL

   Purpose:  To specify the gender of telephone number for telephony communication
      with the object the vCard represents.

   Value type:  A single text URI value.  It is expected that the URI scheme
      will be "tel", as specified in [RFC3966], but other schemes MAY be
      used.

   Special notes:  This property is based on the X.520 Telephone Number
      attribute.

      The value "M" stands for male while "F" stands property can include the parameter "TYPE" to specify intended
      use for
      female.

   Example:

             GENDER:F

5.3.  Delivery Addressing Properties

   These types are concerned the telephone number.  The TYPE parameter values can
      include: "home" to indicate a telephone number associated with information related 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 the delivery
   addressing
      another set of values by specifying one or label for more alternate values.
      For example, the vCard object.

5.3.1.  ADR 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".

   Example:

           TEL;TYPE=work,voice,pref,msg:tel:+1-555-555-5555;ext=5555
           TEL;TYPE=home:tel:+33-01-23-45-67

7.4.2.  EMAIL

   Purpose:  To specify the components of the delivery electronic mail address for communication
      with the object the vCard object. represents.

   Value type:  A single structured text value, separated by the SEMI-
      COLON character (ASCII decimal 59). value.

   Special notes:  The structured type value consists of a sequence of
      address components.  The component values MUST be specified in
      their corresponding position.  The structured type value
      corresponds, in sequence, to the post office box; the extended
      address (e.g. apartment or suite number); the street address; the
      locality (e.g., city); the region (e.g., state or province); the
      postal code; the country name.  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. format or preference of the electronic mail address.
      The TYPE parameter values can include
      "home" include: "internet" to indicate an
      Internet addressing type, "x400" to indicate a delivery address X.400 addressing
      type, "uri" to indicate a URI useable for electronic
      communication, "home" to indicate an address associated with a residence;
      residence, "work" to indicate delivery an address for associated with a place
      of work; and work, or "pref" to indicate the preferred delivery a preferred-use email address when
      more than one address is specified.  These  Another IANA registered address type parameter values
      can also be specified as a
      parameter list (i.e., "TYPE=home;TYPE=pref") or as a value list
      (i.e., "TYPE=home,pref").  This type is based on semantics of the
      X.520 geographical and postal addressing attributes. specified.  The default email type is "TYPE=work".

   Example: In this example the post office box and the extended address
   are absent.

           ADR;TYPE=home:;;123 Main Street;Any Town;CA;91921-1234

5.3.2.  LABEL "internet".  A
      non-standard value can also be specified.

   Type example:

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

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

           EMAIL;TYPE=uri,work:http://example.com/contact.php

7.4.3.  IMPP

   Purpose:  To specify the formatted text corresponding to delivery
      address of URI for instant messaging and presence
      protocol communications with the object the vCard represents.

   Value type:  A single text value.

   Special notes: URI.  The property value is formatted text type of the URI indicates the
      protocol that can be used
      to present a delivery address label for the vCard object. this contact.

   Special notes:  The
      type can property may include the type parameter "TYPE" to
      specify delivery
      label type. an intended use for the URI.  The TYPE parameter values can
      include "home" to
      indicate a delivery label for a residence; "work" to indicate
      delivery label one or more of the following:

      *  An indication of the type of communication for which this URI
         is appropriate.  This can be a place value of work; "personal" or
         "business".

      *  An indication of the location of a device associated with this
         URI.  Values can be "home", "work", or "mobile".

      *  The value "pref" indicates this is a preferred address and has
         the same semantics as the "pref" to indicate value in a TEL property.

   Example:

       IMPP;TYPE=personal,pref:xmpp:alice@example.com

7.4.4.  LANG

   Purpose:  To specify the
      preferred delivery label when more than one label language(s) that may be used for contacting
      the individual associated with the vCard.

   Value type:  A list of text values.

   Special notes:  The list is specified.

      These type parameter values can to be specified interpreted as a parameter list
      (i.e., "TYPE=home;TYPE=pref") or defined in
      [RFC2616], Section 14.4, i.e. as a the value list (i.e.,
      "TYPE=home,pref").  The default is "TYPE=work". of an Accept-Language
      HTTP header.  This lets one specify preference among languages.
      Note that any SEMI-COLON character (ASCII decimal 59) must be
      escaped.

   Example: A multi-line address label.

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

5.4.  Communications

       LANG:fr,en\;q=0.9

7.5.  Geographical Properties

   These properties are concerned with information associated with the
   way communications
   geographical positions or regions associated with the object the
   vCard represents are carried
   out.

5.4.1.  TEL represents.

7.5.1.  TZ

   Purpose:  To specify information related to the telephone number for telephony communication
      with time zone of the
      object the vCard represents.

   Value type:  A  The default is a single utc-offset value.  It can also
      be reset to a single phone-number text value.

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

      The property can include the 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 single value.

   Type examples:

           TZ:-05:00

           TZ;VALUE=text:-05:00; EST; Raleigh/North America
           ;This example 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 single value, not a car-phone telephone number, "isdn" structure text value.

7.5.2.  GEO

   Purpose:  To specify information related to
      indicate an ISDN service telephone number, "pcs" the global positioning of
      the object the vCard represents.

   Value type:  A single structured value consisting of two float values
      separated by the SEMI-COLON character (ASCII decimal 59).

   Special notes:  This property specifies information related to indicate a
      personal communication services telephone number. the
      global position of the object associated with the vCard.  The default
      type is "voice".  These type parameter values can be specified
      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 parameter list (i.e., "TYPE=work;TYPE=voice") positive or negative real number,
      respectively.  The latitude represents the location north and
      south of the equator as a value list
      (i.e., "TYPE=work,voice"). positive or negative real number,
      respectively.  The default can be overridden to
      another set of longitude and latitude values by specifying one or more alternate values.
      For example, MUST be expressed
      in the default TYPE of "voice" can [WGS84] reference system.  They MUST be reset specified as
      decimal degrees and should be specified to six decimal places.
      This will allow for granularity within a WORK
      and HOME, VOICE and FAX telephone number meter of the geographical
      position.  The text components are separated by the value list
      "TYPE=work,home,voice,fax".

   Example:

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

5.4.2.  EMAIL SEMI-COLON
      character (ASCII decimal 59).  The simple formula for converting
      degrees-minutes-seconds into decimal degrees is:

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

   Example:

           GEO:37.386013;-122.082932

7.6.  Organizational Properties

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

7.6.1.  TITLE

   Purpose:  To specify the electronic mail address for communication
      with job title, functional position or function
      of the object the vCard represents.

   Value type:  A single text value.

   Special notes:  The type can include  This property is based on the type parameter "TYPE" to X.520 Title attribute.

   Example:

           TITLE:Director\, Research and Development

7.6.2.  ROLE

   Purpose:  To specify information concerning the format role, occupation, or preference
      business category 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, "uri" to indicate a URI useable for electronic
      communication, "home" to indicate object the vCard represents.

   Value type:  A single text value.

   Special notes:  This property is based on the X.520 Business Category
      explanatory attribute.  This property is included as an address associated with a
      residence, "work"
      organizational type to indicate an address associated avoid confusion with a place the semantics of work, or "pref" to indicate a preferred-use email address the
      TITLE property and incorrect usage of that property when
      more than one is specified.  Another IANA registered address type
      can also be specified.  The default email type the
      semantics of this property is "internet".  A
      non-standard value can also be specified.

   Type example:

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

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

           EMAIL;TYPE=uri,work:http://example.com/contact.php

5.4.3.  IMPP intended.

   Example:

           ROLE:Programmer

7.6.3.  LOGO

   Purpose:  To specify the URI for instant messaging and presence
      protocol communications a graphic image of a logo associated with the
      object the vCard represents.

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

   Value type:  A single URI. value.  The type of the URI indicates the
      protocol that default is binary value.  It can
      also be reset to uri value.  The uri value can be used for to specify
      a value outside of this contact. MIME entity.

   Special notes:  The  This property may SHOULD include the type parameter "TYPE" to
      specify an intended use for the URI. graphic image format type.  The TYPE parameter values
      include one or more of the following:

      *  An indication of the type of communication for which this URI
         is appropriate.  This can be a value of "personal" or
         "business".

      *  An indication of the location of a device associated with this
         URI.  Values can
      MUST be "home", "work", or "mobile".

      *  The value "pref" indicates this is a preferred address and has
         the same semantics an image media type as the "pref" value specified in a TEL property.

   Example:

       IMPP;TYPE=personal,pref:xmpp:alice@example.com

5.4.4.  LANG

   Purpose:  To specify the language(s) that may be used for contacting
      the individual associated with the vCard.

   Value type:  A list of text values.

   Special notes: [RFC4288].  The list is to be interpreted as defined in
      [RFC2616], Section 14.4, i.e. as full
      media type name, including the value of an Accept-Language
      HTTP header.  This lets one specify preference among languages.
      Note that any SEMI-COLON character (ASCII decimal 59) must "image/" prefix, should be
      escaped. used.
      However, implementations SHOULD be able to handle bare subtypes.

   Example:

       LANG:fr,en\;q=0.9

5.5.  Geographical Properties

   These properties are concerned with information associated with
   geographical positions or regions associated with the object the
   vCard represents.

5.5.1.  TZ

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

         LOGO;ENCODING=b;TYPE=image/jpeg:MIICajCCAdOgAwIBAgICBEUwDQYJKoZ
          AQEEBQAwdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05ldHNjYXBlIENvbW11bm
          ljYXRpb25zIENvcnBvcmF0aW9uMRwwGgYDVQQLExNJbmZvcm1hdGlvbiBTeXN0
          <...the remainder of "B" encoded binary data...>

7.6.4.  AGENT

   Purpose:  To specify information related to the time zone about another person who will act on
      behalf of the
      object individual or resource associated with the vCard represents. vCard.

   Value type:  The default is a single utc-offset vcard value.  It can also be
      reset to either a single text or uri value.

   Special notes:  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.

5.5.2.  GEO

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

   Value type:  A single structured value consisting of two float values
      separated by the SEMI-COLON character (ASCII decimal 59).

   Special notes:  This property specifies information related can be
      used to the
      global position of the object associated with the vCard. specify textual information.  The uri 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 can be specified used 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.

   Example:

           GEO:37.386013;-122.082932

5.6.  Organizational Properties

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

5.6.1.  TITLE

   Purpose:  To
      specify the job title, functional position or function
      of the object the vCard represents.

   Value type:  A single text value. information outside of this MIME entity.

   Special notes:  This property typically is based on used to specify an area
      administrator, assistant, or secretary for the X.520 Title attribute. individual
      associated with the vCard.  A key characteristic of the AGENT
      property is that it represents somebody or something that is
      separately addressable.

   Example:

           TITLE:Director\, Research and Development

5.6.2.  ROLE

           AGENT;VALUE=uri:

            CID:JQPUBLIC.part3.960129T083020.xyzMail@example.com

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

7.6.5.  ORG

   Purpose:  To specify information concerning the role, occupation, or
      business category of the object organizational name and units associated
      with the vCard represents. vCard.

   Value type:  A single structured text value. value consisting of components
      separated the SEMI-COLON character (ASCII decimal 59).

   Special notes:  This  The property is based on the X.520 Business Category
      explanatory attribute.  This Organization Name
      and Organization Unit attributes.  The property value is included as an
      organizational a
      structured type to avoid confusion with the semantics of the
      TITLE property and incorrect usage consisting of that property when the
      semantics organization name, followed by
      one or more levels of this property is intended. organizational unit names.

   Example:

           ROLE:Programmer

5.6.3.  LOGO

   Purpose:  To specify a graphic image A property value consisting of a logo associated an organizational name,
   organizational unit #1 name and organizational unit #2 name.

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

7.7.  Explanatory Properties

   These properties are concerned with the
      object the vCard represents.

   Encoding:  The encoding MUST be reset additional explanations, such as
   that related to "b" using the ENCODING
      parameter in order informational notes or revisions specific to the
   vCard.

7.7.1.  CATEGORIES

   Purpose:  To specify inline, encoded binary data.  If application category information about the
      value is referenced
      vCard.

   Value type:  One or more text values separated by a URI value, then the default encoding of
      8bit is used and no explicit ENCODING parameter COMMA character
      (ASCII decimal 44).

   Example:

           CATEGORIES:TRAVEL AGENT

           CATEGORIES:INTERNET,IETF,INDUSTRY,INFORMATION TECHNOLOGY

7.7.2.  NOTE

   Purpose:  To specify supplemental information or a comment that is needed.
      associated with the vCard.

   Value type:  A single text 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.

   Special notes:  This  The property SHOULD include is based on the parameter "TYPE" X.520 Description
      attribute.

   Example:

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

7.7.3.  PRODID

   Purpose:  To specify the graphic image format type.  The TYPE parameter value
      MUST be an image media type identifier for the product that created the
      vCard object.

   Type value:  A single text value.

   Special notes:  Implementations SHOULD use a method such as that
      specified for Formal Public Identifiers in [RFC4288].  The full
      media type name, including the "image/" prefix, should be used.
      However, implementations SHOULD be able [ISO9070] or for
      Universal Resource Names in [RFC3406] to handle bare subtypes. assure that the text
      value is unique.

   Example:

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

         LOGO;ENCODING=b;TYPE=image/jpeg:MIICajCCAdOgAwIBAgICBEUwDQYJKoZ
          AQEEBQAwdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05ldHNjYXBlIENvbW11bm
          ljYXRpb25zIENvcnBvcmF0aW9uMRwwGgYDVQQLExNJbmZvcm1hdGlvbiBTeXN0
          <...the remainder of "B" encoded binary data...>

5.6.4.  AGENT

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

7.7.4.  REV

   Purpose:  To specify revision information about another person who will act on
      behalf of the individual or resource associated with the current vCard.

   Value type:  The default is a single vcard date-time value.  It can  Can also be
      reset to either a single text or uri date 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.

   Special notes:  This property typically is used to specify an area
      administrator, assistant, or secretary for the individual
      associated with  The value distinguishes the vCard.  A key characteristic current revision of the AGENT
      property is that it represents somebody or something that is
      separately addressable.
      information in this vCard for other renditions of the information.

   Example:

           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

5.6.5.  ORG

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

           REV:1997-11-15

7.7.5.  SORT-STRING

   Purpose:  To specify the organizational family name and units associated
      with or given name text to be used
      for national-language-specific sorting of the vCard. FN and N types.

   Value type:  A single structured text value consisting of components
      separated the SEMI-COLON character (ASCII decimal 59). value.

   Special notes:  The property sort string is based on used to provide family name or
      given name text that is to be used in locale- or national-
      language- specific sorting of the X.520 Organization Name formatted name and Organization Unit attributes.  The structured
      name types.  Without this information, sorting algorithms could
      incorrectly sort this vCard within a sequence of sorted vCards.
      When this property value is present in a
      structured type consisting of the organization name, followed by
      one vCard, then this family name or more levels of organizational unit names.

   Example: A property
      given name value consisting is used for sorting the vCard.

   Examples: For the case of an organizational name,
   organizational unit #1 family name and organizational unit #2 name.

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

5.7.  Explanatory Properties

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

5.7.1.  CATEGORIES

   Purpose:  To specify application category information about following examples
   define common sort string usage with the
      vCard.

   Value type:  One or more text values separated by a COMMA character
      (ASCII decimal 44).

   Example:

           CATEGORIES:TRAVEL AGENT

           CATEGORIES:INTERNET,IETF,INDUSTRY,INFORMATION TECHNOLOGY

5.7.2.  NOTE FN and N properties.

           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

7.7.6.  SOUND

   Purpose:  To specify supplemental information or a comment digital sound content information that is
      associated with
      annotates some aspect of the vCard.

   Value type:  A single text value.

   Special notes:  The  By default this property is based on the X.520 Description
      attribute.

   Example:

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

5.7.3.  PRODID

   Purpose:  To specify the identifier for proper pronunciation of the product that created name property
      value of the
      vCard object.

   Type value:  A single text value.

   Special notes:  Implementations SHOULD use a method such as that
      specified for Formal Public Identifiers in [ISO9070] or for
      Universal Resource Names vCard.

   Encoding:  The encoding MUST be reset to "b" using the ENCODING
      parameter in [RFC3406] order to assure that specify inline, encoded binary data.  If the text
      value is unique.

   Example:

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

5.7.4.  REV

   Purpose:  To specify revision information about referenced by a URI value, then the current vCard. default encoding of
      8bit is used and no explicit ENCODING parameter is needed.

   Value type:  A single value.  The default is a single date-time binary value.  Can  It can
      also be reset to uri value.  The uri value can be used to specify
      a value outside of this MIME entity.

   Special notes:  This property SHOULD include the parameter "TYPE" to
      specify the audio format type.  The TYPE parameter value MUST be
      an audio media type as specified in [RFC4288].  The full media
      type name, including the "audio/" prefix, should be used.
      However, implementations SHOULD be able to handle bare subtypes.

   Example:

         SOUND;TYPE=audio/basic;VALUE=uri:CID:JOHNQPUBLIC.part8.
          19960229T080000.xyzMail@example.com

         SOUND;TYPE=audio/basic;ENCODING=b:MIICajCCAdOgAwIBAgICBEUwDQYJK
          AQEEBQAwdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05ldHNjYXBlIENvbW11bm
          ljYXRpb25zIENvcnBvcmF0aW9uMRwwGgYDVQQLExNJbmZvcm1hdGlvbiBTeXN0
          <...the remainder of "B" encoded binary data...>

7.7.7.  UID

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

   Value type:  A single date URI value.

   Special notes:  The value distinguishes type is used to uniquely identify the current revision of object that
      the
      information vCard represents.  The "uuid" URN namespace defined in
      [RFC4122] is particularly well-suited to this vCard for task, but other renditions of URI
      schemes MAY be used.

      This property MUST NOT appear more than once in a given vCard, and
      MUST be present if synchronization is to be used.  See Section 8.

      The UID parameter MUST NOT be applied to this property.

   Example:

           UID:urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6

7.7.8.  URL

   Purpose:  To specify a uniform resource locator associated with the information.
      object that the vCard refers to.

   Value type:  A single uri value.

   Example:

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

           REV:1997-11-15

5.7.5.  SORT-STRING

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

7.7.9.  VERSION

   Purpose:  To specify the family name or given name text to be used
      for national-language-specific sorting version of the FN and N types. vCard specification used to
      format this vCard.

   Value type:  A single text value.

   Special notes:  The sort string is used to provide family name or
      given name text that is to property MUST be used present 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 property is present in a vCard, then this family name or
      given name object.
      The value is used for sorting the vCard.

   Examples: For the case of family name sorting, the following examples
   define common sort string usage with MUST be "4.0" if the FN and N properties.

           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

5.7.6.  SOUND vCard corresponds to this
      specification.

   Example:

           VERSION:4.0

7.8.  Security Properties

   These properties are concerned with the security of communication
   pathways or access to the vCard.

7.8.1.  CLASS

   Purpose:  To specify a digital sound content information that
      annotates some aspect of the vCard.  By default this property access classification for a vCard object.

   Value type:  A single text value.

   Special notes:  An access classification is
      used to specify only one component of the proper pronunciation
      general security model for a directory service.  The
      classification attribute provides a method of capturing the name property
      value intent
      of the vCard. owner for general access to information described by the
      vCard object.

   Examples:

           CLASS:PUBLIC

           CLASS:PRIVATE

           CLASS:CONFIDENTIAL

7.8.2.  KEY

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

   Encoding:  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 text value, then the default encoding of 8bit is used
      and no explicit ENCODING parameter is needed.

   Value type:  A single value.  The default is binary value. binary.  It can also be
      reset to uri text value.  The uri text value can be used to specify a value outside of this MIME entity. text
      key.

   Special notes:  The property can also include the parameter TYPE to
      specify the public key or authentication certificate format.  This
      parameter should specify an IANA registered public key or
      authentication certificate format.  It can also specify a non-
      standard format.

   Special notes:  This property SHOULD include the parameter "TYPE" to
      specify the audio format type. public key or authentication certificate format.  The
      TYPE parameter value MUST be
      an audio a media type as specified in
      [RFC4288].  The full media
      type name, including the "audio/" prefix, should be used.
      However, implementations SHOULD be able to handle bare subtypes.

   Example:

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

         SOUND;TYPE=audio/basic;ENCODING=b:MIICajCCAdOgAwIBAgICBEUwDQYJK
          AQEEBQAwdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05ldHNjYXBlIENvbW11bm
          ljYXRpb25zIENvcnBvcmF0aW9uMRwwGgYDVQQLExNJbmZvcm1hdGlvbiBTeXN0
          <...the remainder

         KEY;TYPE=application/pgp-keys;ENCODING=b:mQGiBEbEPUsRBACBF0RSIN
          mGutdM+KSAl7HMzwXHaLbvEOyu8At80I8qGejhzWowKbfem3X0m68Y/vhb+J2g
          7q11KHpnEdNb67uZaj9nTQ09Q+UFtH25qD/Afn3+9bOJQaPjAUYzXu3vD/xmN8
          <...remainder of "B" encoded binary data...>

5.7.7.  UID

7.9.  Calendar Properties

   These properties are further specified in [RFC2739].

7.9.1.  FBURL
   Purpose:  To specify the URI for a value that represents user's busy time in a globally unique
      identifier corresponding to the individual or resource associated
      with the vCard. vCard
      object.

   Value type:  A single text URI value.

   Special notes:  The type is used to uniquely identify  Where multiple FBURL properties are specified, the object that
      default FBURL property is indicated with the vCard represents. PREF parameter.  The
      FTP or HTTP type can include the type parameter "TYPE" of URI points to specify an iCalendar object associated
      with a snapshot of the format last six weeks of the identifier.  The TYPE parameter value user's busy time
      data.  If the iCalendar object is represented as a file or
      document, it's file type should be an IANA
   registered identifier format.  The value can also be a non-standard
   format.

   Example:

           UID:19950401-080045-40000F192713-0052

5.7.8.  URL "ifb".

   Examples:

     FBURL;PREF:http://www.example.com/busy/janedoe
     FBURL:FTP://ftp.example.com/busy/project-a.ifb

7.9.2.  CALADRURI

   Purpose:  To specify a uniform resource locator associated with the
      object that location to which an event request should be
      sent for the vCard refers to. user.

   Value type:  A single uri URI value.

   Special notes:  Where multiple CALADRURI properties are specified,
      the default CALADRURI property is indicated with the PREF
      parameter.

   Example:

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

5.7.9.  VERSION

     CALADRURI;PREF:mailto:janedoe@example.com

7.9.3.  CAPURI

   Purpose:  To specify the version of the vCard specification used to
      format this vCard. a protocol independent location from which a
      calendaring and scheduling client (i.e., CUA) can communicate with
      a user's entire calendar.

   Value type:  A single text URI value.

   Special notes:  The property MUST be present in the vCard object.
      The value MUST be "4.0" if the vCard corresponds to this
      specification.

   Example:

           VERSION:4.0

5.8.  Security Properties

   These  Where multiple CAPURI properties are concerned with specified, the security of communication
   pathways or access to
      default CAPURI property is indicated with the vCard.

5.8.1.  CLASS PREF parameter.

7.9.4.  CALURI
   Purpose:  To specify the access classification URI for a user's calendar in a vCard object.

   Value type:  A single text URI value.

   Special notes:  An access classification  Where multiple CALURI properties are specified, the
      default CALURI property is indicated with the PREF parameter.  The
      property should contain a URI pointing to an iCalendar object
      associated with a snapshot of the user's calendar store.  If the
      iCalendar object is represented as a file or document, it's file
      type should be "ics".

   Examples:

     CALURI;PREF:http://cal.example.com/calA
     CALURI:ftp://ftp.example.com/calA.ics

7.10.  Extended Properties and Parameters

   The properties and parameters defined by this document can be
   extended.  Non-standard, private properties and parameters with a
   name starting with "X-" may be defined bilaterally between two
   cooperating agents without outside registration or standardization.

8.  Synchronization

   vCard data often needs to be synchronized between devices.  In this
   context, synchronization is only one component of defined as the
      general security model for a directory service.  The
      classification attribute provides a method intelligent merging of capturing the intent two
   representations of the owner for general access to information described by the
      vCard same object.

   Examples:

           CLASS:PUBLIC

           CLASS:PRIVATE

           CLASS:CONFIDENTIAL

5.8.2.  KEY

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

   Encoding:  The encoding 4.0 includes mechanisms to
   aid this process.

8.1.  Mechanisms

   Two vCards for which the UID properties (Section 7.7.7) are
   equivalent MUST be reset to "b" using considered representations of the ENCODING
      parameter same object.
   Equivalence is determined as specified in order [RFC3986], Section 6.  A
   missing UID property MUST NOT be considered equivalent to specify inline, encoded binary data.  If any other.
   Hence, the
      value UID property MUST be present if synchronization is to be
   used.

   Pairs of properties, one from each of a text value, then the default encoding pair of 8bit is used vCards representing
   the same object, having equivalent names and no explicit ENCODING UID parameter is needed.

   Value type:  A single value.  The default is binary.  It can also be
      reset to text value.  The text value can values
   MUST be used to specify a text
      key.

   Special notes:  The property can also include considered representations of the same object.  A missing UID
   parameter TYPE MUST NOT be considered equivalent to
      specify any other.  Hence, the public key or authentication certificate format.  This
   UID parameter should specify an IANA registered public key or
      authentication certificate format. MUST be present if synchronization is to be used.

   It can also specify is expected that a non-
      standard format.

   Special notes:  This synchronization engine will exploit such
   property SHOULD include the parameter "TYPE" to
      specify associations by e.g. overwriting the public key or authentication certificate format.  The
      TYPE parameter destination property
   value and parameters with the source destination property value MUST be a media type as specified in
      [RFC4288].

   Example:

         KEY;TYPE=application/pgp-keys;ENCODING=b:mQGiBEbEPUsRBACBF0RSIN
          mGutdM+KSAl7HMzwXHaLbvEOyu8At80I8qGejhzWowKbfem3X0m68Y/vhb+J2g
          7q11KHpnEdNb67uZaj9nTQ09Q+UFtH25qD/Afn3+9bOJQaPjAUYzXu3vD/xmN8
          <...remainder of "B" encoded binary data...>

5.9.  Extended Properties and Parameters
   parameters.  The properties and parameters defined by particular merging strategy is out of scope for this document can be
   extended.  Non-standard, private properties
   document.

8.2.  Example

   Two vCards are to by synchronized:

     BEGIN:VCARD
     VERSION:4.0
     UID:urn:uuid:77a01597-0603-40f3-8138-36deca8618da
     FN;UID="urn:uuid:dade7896-81bd-4a3c-950e-bdfc04f15b61":Jane Doe
     EMAIL;UID="urn:uuid:69531f4a-c34d-4a1e-8922-bd38a9476a53":
      jdoe1@example.com
     EMAIL;UID="urn:uuid:48a28f93-d4a4-4430-a7c6-a784ecb3f865":
      jdoe2@example.com
     END:VCARD

     BEGIN:VCARD
     VERSION:4.0
     UID:urn:uuid:77a01597-0603-40f3-8138-36deca8618da
     FN;UID="urn:uuid:dade7896-81bd-4a3c-950e-bdfc04f15b61":Jane Doe
     EMAIL;UID="urn:uuid:69531f4a-c34d-4a1e-8922-bd38a9476a53":
      jdoe3@example.com
     EMAIL;UID="urn:uuid:a69f4bff-49c5-4829-8c95-63db67c85bd6":
      jdoe4@example.com
     END:VCARD

   Assuming the first one is the source and parameters with the other is the
   destination, a
   name starting with "X-" synchronization engine may be defined bilaterally between two
   cooperating agents without outside registration or standardization.

6. produce the following
   merged vCard:

     BEGIN:VCARD
     VERSION:4.0
     UID:urn:uuid:77a01597-0603-40f3-8138-36deca8618da
     FN;UID="urn:uuid:dade7896-81bd-4a3c-950e-bdfc04f15b61":Jane Doe
     EMAIL;UID="urn:uuid:69531f4a-c34d-4a1e-8922-bd38a9476a53":
      jdoe1@example.com
     EMAIL;UID="urn:uuid:48a28f93-d4a4-4430-a7c6-a784ecb3f865":
      jdoe2@example.com
     EMAIL;UID="urn:uuid:a69f4bff-49c5-4829-8c95-63db67c85bd6":
      jdoe4@example.com
     END:VCARD

9.  Formal Grammar

   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 [RFC5234],
   but it references just this small subset of [RFC5234] literals:

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

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

    vcard_entity = 1*(vcard)

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

    contentline  = 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].

    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 outer MIME object (UTF-8 preferred)

    QSAFE-CHAR   = %x41-5A WSP / %x21 / %x23-7E / %x61-7A NON-ASCII
         ; Latin Capital Letter A-Latin Capital Letter Z Any character except CTLs, DQUOTE

    SAFE-CHAR    = WSP / %x21 / %x23-2B / %x2D-39 / %x3C-7E / NON-ASCII
         ; Latin Small Letter a-Latin Small Letter z
    CHAR Any character except CTLs, DQUOTE, ";", ":", ","

    VALUE-CHAR   = %x01-7F WSP / VCHAR / NON-ASCII
         ; Any C0 Controls and Basic Latin, excluding NULL from textual character

    ;*******************************************
    ; Code Charts, pages 7-6 through 7-9 in [UNICODE]

    CR           = %x0D
         ; Carriage Return

    LF           = %0A vCard Type Definition
    ; Line Feed

    CRLF         = CR LF
    ; Internet standard newline

    ;CTL         = %x00-1F / %x7F Provides type-specific definitions for how the
    ; Controls. Not used, but referenced in comments.

    DIGIT "value" and "param" are defined.
    ;*******************************************
    ;For name="NAME"
    param        = %x30-39 ""
         ; Digit Zero-Digit Nine

    DQUOTE No parameters allowed

    value        = text-value

    ;For name="KIND"
    param        = %x22 ""
         ; Quotation Mark

    HTAB No parameters allowed

    value        = kind-value

    kind-value   = "individual" / "group" / "org" / x-name / iana-token

    ;For name="PROFILE"
    param        = %x09 ""
         ; Horizontal Tabulation

    SP No parameters allowed

    value        = %x20 text-value
         ; space

    VCHAR Value MUST be the case insensitive value "VCARD

    ;For name="SOURCE"
    param        = %x21-7E source-param
         ; Visible (printing) characters

    WSP Only source parameters allowed

    value        = uri

    source-param = SP ("VALUE" "=" "uri")
                 / HTAB
         ; White Space

    ;*******************************************
    ; Basic (x-name "=" *SAFE-CHAR)
    ;For name="FN"
    ;This type MUST be included in a vCard Definition
    ;*******************************************

    vcard_entity object.
    param        = 1*(vcard)

    vcard text-param
         ; Text parameters allowed

    value        = "BEGIN" ":" "VCARD" 1*CRLF
                   1*(contentline)
         ;A vCard object text-value

    ;For name="N"
    ;This type MUST include the VERSION, FN and N types.
                   "END" ":" "VCARD" 1*CRLF

    contentline be included in a vCard object.

    param        = name *(";" 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 ) ":" value CRLF        = text-param
         ; When parsing a content line, folded lines must first Text parameters allowed
    value        = text-value-list

    ;For name="PHOTO"
    param        = img-inline-param
         ; be unfolded according to the unfolding procedure Only image parameters allowed

    param        =/ img-refer-param
         ; described above. When generating a content line, lines Only image parameters allowed

    value        = img-inline-value
         ; longer than 75 characters SHOULD be folded according to Value and parameter MUST match

    value        =/ img-refer-value
         ; the folding procedure described in [MIME DIR].

    name Value and parameter MUST match

    ;For name="BDAY"
    param        = iana-token / x-name ("VALUE" "=" "date")
         ; Parsing of the Only value parameter allowed

    param and        =/ ("VALUE" "=" "date-time")
         ; Only value is parameter allowed

    value        = date-value
         ; based on the "name" or Value MUST match value type identifier
         ; as defined in ABNF sections below
    iana-token   = 1*(ALPHA / DIGIT / "-")
    value        =/ date-time-value
         ; vCard Value MUST match value type or parameter identifier registered with IANA

    x-name

    ;For name="ADR"
    param        = "X-" 1*(ALPHA / DIGIT adr-param / "-") text-param
         ; Reserved for non-standard use

    param Only adr and text parameters allowed

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

    param-name adr-value

    ;For name="LABEL"
    param        = iana-token adr-param / x-name

    param-value text-param
         ; Only adr and text parameters allowed

    value        = ptext / quoted-string

    ptext text-value

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

    value        = *VALUE-CHAR

    quoted-string = DQUOTE QSAFE-CHAR DQUOTE

    NON-ASCII uri-value

    tel-param    = %x80-FF
         ; Use is restricted by outer MIME object (UTF-8 preferred)

    QSAFE-CHAR "TYPE" "=" tel-type *("," tel-type)
    tel-type     = WSP "HOME" / "WORK" / "PREF" / "VOICE" / "FAX" / %x21 "MSG"
                 / %x23-7E "CELL" / NON-ASCII
         ; Any character except CTLs, DQUOTE

    SAFE-CHAR    = WSP "PAGER" / %x21 "BBS" / %x23-2B "MODEM" / %x2D-39 "CAR" / %x3C-7E "ISDN"
                 / NON-ASCII
         ; Any character except CTLs, DQUOTE, ";", ":", ","

    VALUE-CHAR   = WSP "VIDEO" / VCHAR "PCS" / NON-ASCII
         ; Any textual character

    ;******************************************* iana-token / x-name
         ; vCard Type Definition Values are case insensitive

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

    value        = text-value

    email-param  = "TYPE" "=" email-type ["," "PREF"]
         ; Provides type-specific definitions for how the Value is case insensitive

    email-type   = "INTERNET" / "X400" / iana-token / "X-" word
         ; "value" and "param" Values are defined.
    ;******************************************* case insensitive

    ;For name="NAME" name="TZ"
    param        = ""
         ; No parameters allowed

    value        = text-value utc-offset-value

    ;For name="KIND" name="GEO"
    param        = ""
         ; No parameters allowed
    value        = kind-value
    kind-value   = "individual" / "group" / "org" / x-name / iana-token float-value ";" float-value

    ;For name="PROFILE" name="TITLE"
    param        = "" text-param
         ; No Only text parameters allowed

    value        = text-value

    ;For name="ROLE"
    param        = text-param
         ; Value MUST be the case insensitive Only text parameters allowed

    value "VCARD        = text-value

    ;For name="SOURCE" name="LOGO"
    param        = source-param img-inline-param / img-refer-param
         ; Only source image parameters allowed

    value        = uri

    source-param = ("VALUE" "=" "uri") img-inline-value / (x-name "=" *SAFE-CHAR)

    ;For name="FN"
    ;This type img-refer-value
         ; Value and parameter MUST be included in a vCard object. match

    ;For name="AGENT"
    param        = agent-inline-param

    param        =/ agent-refer-param

    param        =/ text-param

    value        = agent-inline-value
         ; Text Value and parameter MUST match

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

    value        =/ text-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

    ;For name="N"
    ;This type
         ; Value MUST be included in a valid vCard object. object

    agent-refer-value = uri
         ; URI MUST refer to valid vCard object
    ;For name="ORG"

    param        = text-param
         ; Text Only text parameters allowed

    value        = n-value

    n-value org-value

    org-value    = 0*4(text-value *("," text-value) *(text-value ";") text-value *("," text-value)
         ; Family; Given; Middle; Prefix; Suffix.
         ; Example: Public;John;Quincy,Adams;Reverend Dr. III First is Organization Name, remainder are Organization Units.

    ;For name="NICKNAME" name="CATEGORIES"
    param        = text-param
         ; Text Only text parameters allowed

    value        = text-value-list

    ;For name="PHOTO" name="NOTE"
    param        = img-inline-param text-param
         ; Only image text parameters allowed
    value        = text-value

    ;For name="PRODID"
    param        =/ img-refer-param        = ""
         ; Only image No parameters allowed

    value        = img-inline-value
         ; Value and parameter MUST match

    value        =/ img-refer-value
         ; Value and parameter MUST match text-value

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

    param        =/ ("VALUE" "=" "date-time") "VALUE" =" "date"
         ; Only value parameter allowed parameters allowed. Values are case insensitive.

    value        = date-value
         ; Value MUST match value type

    value        =/ date-time-value
         ; Value MUST match

    value type        =/ date-value

    ;For name="ADR" name="SORT-STRING"
    param        = adr-param / text-param
         ; Only adr and text parameters allowed

    value        = adr-value text-value

    ;For name="LABEL" name="SOUND"
    param        = adr-param / text-param snd-inline-param
         ; Only adr and text sound parameters allowed

    value        = text-value

    ;For name="TEL"
    param        = tel-param        =/ snd-refer-param
         ; Only tel sound parameters allowed

    value        = phone-number-value

    tel-param snd-line-value
         ; Value MUST match value type

    value        =/ snd-refer-value
         ; Value MUST match value type

    snd-inline-value     = "TYPE" "=" tel-type *("," tel-type)
    tel-type binary-value CRLF
         ; Value MUST be "b" encoded audio content

    snd-inline-param     = "HOME" / "WORK" / "PREF" / "VOICE" / "FAX" / "MSG"
                 / "CELL" / "PAGER" / "BBS" / "MODEM" / "CAR" / "ISDN"
                 / "VIDEO" / "PCS" ("VALUE" "=" "binary"])
                         / iana-token ("ENCODING" "=" "b")
                         / x-name ("TYPE" "=" *SAFE-CHAR)
         ; Values are case insensitive

    ;For name="EMAIL"
    param Value MUST be an IANA registered audio type

    snd-refer-value      = email-param uri
         ; Only email parameters allowed
    value        = text-value

    email-param URI MUST refer to audio content of given type
    snd-refer-param      = "TYPE" ("VALUE" "=" email-type ["," "PREF"]
         ; Value is case insensitive

    email-type   = "INTERNET" / "X400" / iana-token "uri")
                         / "X-" word ("TYPE" "=" word)
         ; Values are case insensitive Value MUST be an IANA registered audio type

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

    value        = utc-offset-value uri

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

    value        = float-value ";" float-value uri

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

    value        = text-value

    ;For name="ROLE"
    param        = text-param
         ; Only text parameters allowed

    value        = text-value Value MUST be "4.0"

    ;For name="LOGO" name="CLASS"
    param        = img-inline-param / img-refer-param ""
         ; Only image No parameters allowed

    value        = img-inline-value "PUBLIC" / img-refer-value "PRIVATE" / "CONFIDENTIAL"
                 / iana-token / x-name
         ; Value and parameter MUST match are case insensitive

    ;For name="AGENT" name="KEY"
    param        = agent-inline-param

    param        =/ agent-refer-param key-txt-param
         ; Only value and type parameters allowed

    param        =/ text-param

    value        = agent-inline-value key-bin-param
         ; Value Only value and parameter MUST match type parameters allowed

    value        = text-value

    value        =/ agent-refer-value binary-value

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

    key-bin-param = ("TYPE" "=" keytype)
                  / ("ENCODING" "=" "b")
         ; Value and parameter MUST match

    value        =/ text-value be a "b" encoded key or certificate
    keytype      = param-value
         ; Value and parameter Type MUST match

    agent-inline-param be a media type as defined in RFC 4288

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

    agent-refer-param

    value        = "VALUE" "=" "uri" text-value

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

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

    langval      = <a language string as defined in [RFC4646]>

    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 parameter allowed

    agent-inline-value = text-value
         ; Value MUST be a valid vCard object

    agent-refer-value an image media type as defined in RFC 4288
    img-refer-value = uri
         ; URI
         ;URI MUST refer to valid vCard object

    ;For name="ORG"

    param image content of given type

    img-refer-param      = text-param
         ; Only text parameters allowed ("VALUE" "=" "uri")
                         / ("TYPE" "=" param-value)
         ;TYPE value MUST be an image media type as defined in RFC 4288

    adr-param    = org-value

    org-value ("TYPE" "=" adr-type *("," adr-type))
                 / (text-param)

    adr-type     = *(text-value "home" / "work" / "pref" / iana-token / x-name

    adr-value    = 0*6(text-value ";") text-value
         ; First is Organization Name, remainder are Organization Units.

    ;For name="CATEGORIES"
    param        = text-param PO Box, Extended Address, Street, Locality, Region, Postal
         ; Only text parameters allowed

    value        = text-value-list

    ;For name="NOTE"
    param        = text-param Code, Country Name
    ;*******************************************
    ; Only text parameters allowed
    value vCard Type Value Definition
    ;*******************************************

    text-value-list      = 1*text-value *("," 1*text-value)

    text-value

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

    value   = text-value

    ;For name="REV"
    param *(SAFE-CHAR / ":" / DQUOTE / ESCAPED-CHAR)

    ESCAPED-CHAR = ["VALUE" =" "date-time"] "\\" / "\;" / "\," / "\n" / "\N")
         ; Only value parameters allowed. Values are case insensitive.

    param        =/ "VALUE" =" "date" \\ encodes \, \n or \N encodes newline
         ; Only value parameters allowed. Values are case insensitive.

    value        = date-time-value

    value        =/ date-value

    ;For name="SORT-STRING"
    param \; encodes ;, \, encodes ,

    binary-value = text-param
         ; Only <A "b" encoded text parameters allowed value as defined in [RFC2047]>

    date-value   = text-value

    ;For name="SOUND"
    param        = snd-inline-param
         ; Only sound parameters allowed

    param        =/ snd-refer-param
         ; Only sound parameters allowed <A single date value as defined in [RFC2425]>

    time-value   = snd-line-value
         ; Value MUST match <A single time value type as defined in [RFC2425]>

    date-time-value = <A single date-time value        =/ snd-refer-value
         ; Value MUST match as defined in [RFC2425]>

    float-value  = <A single float value type

    snd-inline-value as defined in [RFC2425]>

    phone-number-value = binary-value CRLF
         ; Value MUST be "b" encoded audio content

    snd-inline-param phone-prefix 1*(SP 1*DIGIT) [phone-ext]

    phone-prefix = ("VALUE" "=" "binary"])
                         / ("ENCODING" "=" "b") "+" 1*DIGIT / ("TYPE" "=" *SAFE-CHAR)
         ; Value MUST be an IANA registered audio type

    snd-refer-value "(" 1*DIGIT ")"

    phone-ext = "ext." 1*DIGIT

    uri-value    = <A uri
         ; URI MUST refer value as defined in [RFC2425]>

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

10.  Example: Authors' vCards

      BEGIN:VCARD
      VERSION:4.0
      FN:Pete Resnick
      N:Resnick;Pete;;;
      GENDER:M
      ORG:QUALCOMM Incorporated
      ADR;TYPE=work:;;5775 Morehouse Drive;San Diego;CA;92121-1714;US
      TEL;TYPE=voice:tel:+1-858-651-4478
      EMAIL;TYPE=internet:presnick@qualcomm.com
      URL:http://www.qualcomm.com/~presnick/
      END:VCARD

      BEGIN:VCARD
      VERSION:4.0
      FN:Simon Perreault
      N:Perreault;Simon;;;ing. jr.,M.Sc.
      BDAY:1983-02-03
      GENDER:M
      ORG:Viagenie
      ADR;TYPE=work:;;2600 boul. Laurier\, suite 625;
       Quebec;QC;G1V 4W1;Canada
      TEL;TYPE=voice,work:tel:+1-418-656-9254;ext=102
      TEL;TYPE=fax,work:tel:+1-418-656-9257
      EMAIL;TYPE=internet,work:simon.perreault@viagenie.ca
      GEO:46.772673,-71.282945
      CLASS:PUBLIC
      KEY;VALUE=uri:http://www.viagenie.ca/simon.perreault/simon.asc
      END:VCARD

11.  Security Considerations

   o  Internet mail is subject to many well known security attacks,
      including monitoring, replay, and forgery.  Care should be taken
      by any directory service in allowing information to leave the
      scope of the service itself, where any access controls can no
      longer be guaranteed.  Applications should also take care to
      display directory data in a "safe" environment (e.g., PostScript-
      valued types).

   o  vCards can carry cryptographic keys or certificates, as described
      in Section 7.8.2.

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

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

   o  The information in a vCard may become out of date.  In cases where
      the vitality of data is important to audio content an originator of given a vCard, the
      "URL" type
    snd-refer-param      = ("VALUE" "=" "uri")
                         / ("TYPE" "=" word)
         ; Value MUST be an IANA registered audio described in Section 7.7.8 SHOULD BE specified.  In
      addition, the "REV" type

    ;For name="UID"
    param        = "TYPE" "=" (iana-token / x-name)
         ;TYPE value should described in section Section 7.7.4 can be an
      specified to indicate the last time that the vCard data was
      updated.

12.  IANA registered identifier format

    value        = text-value

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

    value        = uri

    ;For name="VERSION"
    ;This type MUST be included in a Considerations

12.1.  Registering New 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 Elements

   This section defines the process for registering new or modified
   vCard elements (i.e. properties, parameters, value data types, and type parameters allowed

    value        = text-value

    value        =/ binary-value

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

    key-bin-param = ("TYPE" "=" keytype)
                  / ("ENCODING" "=" "b")
         ; Value MUST
   values) with IANA.

12.1.1.  Registration Procedure

   The IETF will create a mailing list, vcard@ietf.org [1], which can be
   used for public discussion of vCard element proposals prior to
   registration.  Use of the mailing list is strongly encouraged.  The
   IESG will appoint a "b" encoded key or certificate
    keytype      = param-value
         ; Type designated expert who will monitor the
   vcard@ietf.org [1] mailing list and review registrations.

   Registration of new vCard elements MUST be reviewed by the designated
   expert and published in an RFC.  A Standard Tracks RFC is REQUIRED
   for the regisration of new value data types that modify existing
   properties.  A Standard Tracks RFC is also REQUIRED for registration
   of vCard elements that modify vCard elements previously documented in
   a media type as Standard Tracks RFC.

   The registration procedure begins when a completed registration
   template, defined in RFC 4288

    ;For name="X-" non-standard type
    param        = text-param / (x-name "=" param-value)
         ; Only text the sections below, is sent to
   vcard@ietf.org [1] and iana@iana.org [2].  The designated expert is
   expected to tell IANA and the submitter of the registration within
   two weeks whether the registration is approved, approved with minor
   changes, or non-standard parameters allowed

    value        = text-value

    ;*******************************************
    ; rejected with cause.  When a registration is rejected
   with cause, it can be re-submitted if the concerns listed in the
   cause are addressed.  Decisions made by the designated expert can be
   appealed to the IESG Applications Area Director, then to the IESG.
   They follow the normal appeals procedure for IESG decisions.

12.1.2.  Vendor Namespace

   The vendor namespace is used for vCard Commonly Used Parameter Definition
    ;*******************************************
    text-param   = ("VALUE" "=" "ptext")
                 / ("LANGUAGE" "=" langval)
                 / (x-name "=" param-value)

    langval      = <a language string elements associated with
   commercially available products.  "Vendor" or "producer" are
   construed as defined equivalent and very broadly in [RFC4646]>

    img-inline-value     = binary-value
         ;Value MUST this context.

   A registration may be "b" encoded image content

    img-inline-param

    img-inline-param     = ("VALUE" "=" "binary")
                         / ("ENCODING" "=" "b")
                         / ("TYPE" "=" param-value
         ;TYPE value MUST placed in the vendor namespace by anyone who
   needs to interchange files associated with the particular product.
   However, the registration formally belongs to the vendor or
   organization handling the vCard elements in the namespace being
   registered.  Changes to the specification will be made at their
   request, as discussed in subsequent sections.

   vCard elements belonging to the vendor namespace will be
   distinguished by the "VND-" prefix.  That may be followed, at the
   discretion of the registrant, by either a vCard element name from a
   well-known producer (e.g., "VND-MUDPIE") or by an image media type as defined IANA-approved
   designation of the producer's name that is followed by a vCard
   element designation (e.g., "VND-BIGCOMPANY-MUDPIE").

   While public exposure and review of vCard elements to be registered
   in RFC 4288

    img-refer-value = uri
         ;URI MUST refer the vendor namespace is not required, using the vcard@ietf.org [1]
   mailing list for review is strongly encouraged to image content improve the quality
   of given type

    img-refer-param      = ("VALUE" "=" "uri")
                         / ("TYPE" "=" param-value)
         ;TYPE value MUST those specifications.  Registrations in the vendor namespace may
   be an image media type as submitted directly to the IANA.

12.1.3.  Registration Template for Properties

   A property is defined in RFC 4288

    adr-param    = ("TYPE" "=" adr-type *("," adr-type))
                 / (text-param)

    adr-type     = "home" / "work" / "pref" / iana-token / x-name

    adr-value    = 0*6(text-value ";") text-value
         ; PO Box, Extended Address, Street, Locality, Region, Postal
         ; Code, Country Name
    ;*******************************************
    ; vCard Type by completing the following template.

   Property name:  The name of the property.

   Purpose:  The purpose of the property.  Give a short but clear
      description.

   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 = <A "b" encoded text type:  Any of the valid value as defined in [RFC2047]>

    date-value   = <A single date types for the property value as defined in [RFC2425]>

    time-value   = <A single time
      needs to be specified.  The default value as type also needs to be
      specified.

   Property parameters:  Any of the valid property parameters for the
      property MUST be specified.

   Description:  Any special notes about the property, how it is to be
      used, etc.

   Format definition:  The ABNF for the property definition needs to be
      specified.

   Example(s):  One or more examples of instances of the property needs
      to be specified.

12.1.4.  Registration Template for Parameters

   A parameter is defined in [RFC2425]>
    date-time-value = <A single date-time by completing the following template.

   Parameter name:  The name of the parameter.

   Purpose:  The purpose of the parameter.  Give a short but clear
      description.

   Description:  Any special notes about the parameter, how it is to be
      used, etc.

   Format definition:  The ABNF for the parameter definition needs to be
      specified.

   Example(s):  One or more examples of instances of the parameter needs
      to be specified.

12.1.5.  Registration Template for Value Data Types

   A value as data type is defined in [RFC2425]>

    float-value  = <A single float by completing the following template.

   Value name:  The name of the value as defined in [RFC2425]>

    phone-number-value = <A single text type.

   Purpose:  The purpose of the value as defined in [CCITT
                          E.163] and [CCITT.X121.1988]>

    uri-value    = <A uri type.  Give a short but clear
      description.

   Description:  Any special notes about the value as defined in [RFC2425]>

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

7.  Example: Authors' vCards

      BEGIN:VCARD
      VERSION:4.0
      FN:Pete Resnick
      N:Resnick;Pete;;;
      GENDER:M
      ORG:QUALCOMM Incorporated
      ADR;TYPE=work:;;5775 Morehouse Drive;San Diego;CA;92121-1714;US
      TEL;TYPE=voice:+1-858-651-4478
      EMAIL;TYPE=internet:presnick@qualcomm.com
      URL:http://www.qualcomm.com/~presnick/
      END:VCARD

      BEGIN:VCARD
      VERSION:4.0
      FN:Simon Perreault
      N:Perreault;Simon;;;ing. jr.,M.Sc.
      BDAY:1983-02-03
      GENDER:M
      ORG:Viagenie
      ADR;TYPE=work:;;2600 boul. Laurier\, suite 625;
       Quebec;QC;G1V 4W1;Canada
      TEL;TYPE=voice,work:+1-418-656-9254
      TEL;TYPE=fax,work:+1-418-656-9257
      EMAIL;TYPE=internet,work:simon.perreault@viagenie.ca
      GEO:46.772673,-71.282945
      CLASS:PUBLIC
      KEY;VALUE=uri:http://www.viagenie.ca/simon.perreault/simon.asc
      END:VCARD

8.  Security Considerations

   o  Internet mail type, how it is subject to many well known security attacks,
      including monitoring, replay, and forgery.  Care should be taken
      used, etc.

   Format definition:  The ABNF for the value type definition needs to
      be specified.

   Example(s):  One or more examples of instances of the value type
      needs to be specified.

12.1.6.  Registration Template for Values

   A value is defined by any directory service in allowing information to leave completing the
      scope following template.

   Value:  The value literal.

   Purpose:  The purpose of the service itself, where any access controls value.  Give a short but clear
      description.

   Conformance:  The vCard properties and/or parameters that can no
      longer be guaranteed.  Applications should also take care
      this value needs to
      display directory data in a "safe" environment (e.g., PostScript-
      valued types).

   o  vCards can carry cryptographic keys be specified.

   Example(s):  One or certificates, as described
      in Section 5.8.2.

   o  Section 5.8.1 specifies more examples of instances of the value needs to
      be specified.

   The following is a desired security classification policy
      for fictitious example of a registration of a particular vCard.  That policy is not enforced in any way.

   o  The vCard objects have no inherent authentication or privacy, but
   value:

   Value:  TOP-SECRET

   Purpose:  This value is used to specify the access classification of
      top-secret vCards.

   Conformance:  This value can easily be carried by any security mechanism that transfers
      MIME objects used with authentication or privacy.  In cases where
      threats the "CLASS" property.

   Example(s):  The following is an example of "spoofed" this value used with the
      "CLASS" property:

     CLASS:TOP-SECRET

12.2.  Initial vCard information Elements Registries

   The IANA is a concern, requested to create and maintain the following registries
   for vCard
      SHOULD BE transported using one of these secure mechanisms.

   o elements with pointers to appropriate reference documents.

12.2.1.  Properties Registry

   The following table is to be used to initialize the properties
   registry.

            +-------------+---------+------------------------+
            | Property    | Status  | Reference              |
            +-------------+---------+------------------------+
            | SOURCE      | Current | RFCXXXX, Section 7.1.3 |
            | NAME        | Current | RFCXXXX, Section 7.1.4 |
            | KIND        | Current | RFCXXXX, Section 7.1.5 |
            | FN          | Current | RFCXXXX, Section 7.2.1 |
            | N           | Current | RFCXXXX, Section 7.2.2 |
            | NICKNAME    | Current | RFCXXXX, Section 7.2.3 |
            | PHOTO       | Current | RFCXXXX, Section 7.2.4 |
            | BDAY        | Current | RFCXXXX, Section 7.2.5 |
            | DDAY        | Current | RFCXXXX, Section 7.2.6 |
            | BIRTH       | Current | RFCXXXX, Section 7.2.7 |
            | DEATH       | Current | RFCXXXX, Section 7.2.8 |
            | GENDER      | Current | RFCXXXX, Section 7.2.9 |
            | ADR         | Current | RFCXXXX, Section 7.3.1 |
            | LABEL       | Current | RFCXXXX, Section 7.3.2 |
            | TEL         | Current | RFCXXXX, Section 7.4.1 |
            | EMAIL       | Current | RFCXXXX, Section 7.4.2 |
            | IMPP        | Current | RFCXXXX, Section 7.4.3 |
            | LANG        | Current | RFCXXXX, Section 7.4.4 |
            | TZ          | Current | RFCXXXX, Section 7.5.1 |
            | GEO         | Current | RFCXXXX, Section 7.5.2 |
            | TITLE       | Current | RFCXXXX, Section 7.6.1 |
            | ROLE        | Current | RFCXXXX, Section 7.6.2 |
            | LOGO        | Current | RFCXXXX, Section 7.6.3 |
            | AGENT       | Current | RFCXXXX, Section 7.6.4 |
            | ORG         | Current | RFCXXXX, Section 7.6.5 |
            | CATEGORIES  | Current | RFCXXXX, Section 7.7.1 |
            | NOTE        | Current | RFCXXXX, Section 7.7.2 |
            | PRODID      | Current | RFCXXXX, Section 7.7.3 |
            | REV         | Current | RFCXXXX, Section 7.7.4 |
            | SORT-STRING | Current | RFCXXXX, Section 7.7.5 |
            | SOUND       | Current | RFCXXXX, Section 7.7.6 |
            | UID         | Current | RFCXXXX, Section 7.7.7 |
            | URL         | Current | RFCXXXX, Section 7.7.8 |
            | VERSION     | Current | RFCXXXX, Section 7.7.9 |
            | CLASS       | Current | RFCXXXX, Section 7.8.1 |
            | KEY         | Current | RFCXXXX, Section 7.8.2 |
            | FBURL       | Current | RFCXXXX, Section 7.9.1 |
            | CALADRURI   | Current | RFCXXXX, Section 7.9.2 |
            | CAPURI      | Current | RFCXXXX, Section 7.9.3 |
            | CALURI      | Current | RFCXXXX, Section 7.9.4 |
            +-------------+---------+------------------------+

12.2.2.  Parameters Registry

   The information in a vCard may become out of date.  In cases where
      the vitality of data following table is important to an originator of a vCard, be used to initialize the
      "URL" type described in parameters
   registry.

              +-----------+---------+----------------------+
              | Parameter | Status  | Reference            |
              +-----------+---------+----------------------+
              | LANGUAGE  | Current | RFCXXXX, Section 5.7.8 SHOULD BE specified.  In
      addition, the "REV" type described in section 6.1 |
              | ENCODING  | Current | RFCXXXX, Section 5.7.4 can 6.2 |
              | VALUE     | Current | RFCXXXX, Section 6.3 |
              | UID       | Current | RFCXXXX, Section 6.4 |
              | TYPE      | Current | RFCXXXX, Section 6.5 |
              +-----------+---------+----------------------+

12.2.3.  Value Data Types Registry

   The following table is to be
      specified used to indicate the last time that initialize the vCard data was
      updated.

9. parameters
   registry.

           +-----------------+---------+----------------------+
           | Value Data Type | Status  | Reference            |
           +-----------------+---------+----------------------+
           | BINARY          | Current | RFCXXXX, Section 5.7 |
           | BOOLEAN         | Current | RFCXXXX, Section 5.4 |
           | DATE            | Current | RFCXXXX, Section 5.3 |
           | TIME            | Current | RFCXXXX, Section 5.3 |
           | DATE-TIME       | Current | RFCXXXX, Section 5.3 |
           | FLOAT           | Current | RFCXXXX, Section 5.6 |
           | INTEGER         | Current | RFCXXXX, Section 5.5 |
           | TEXT            | Current | RFCXXXX, Section 5.1 |
           | URI             | Current | RFCXXXX, Section 5.2 |
           +-----------------+---------+----------------------+

13.  Acknowledgements

   The authors would like to thank Frank Dawson and Tim Howes, the
   original authors of [RFC2425] and [RFC2426], as well as the following
   individuals who have participated in the drafting, review and
   discussion of this memo:

   Marc Blanchet, Chris Bryant, Darryl Champagne, Cyrus Daboo, Lisa
   Dusseault, Javier Godoy, Alexander Mayrhofer, Chris Newman, Mark
   Paterson, and Julien Reschke.

10. Alexander Mayrhofer, Julian Reschke, Peter K. Sheerin, Anil
   Srivastava, and Kurt Zeilenga.

14.  References

10.1.

14.1.  Normative References

   [CCITT.E163.1988]       International Telephone and Telegraph
                           Consultative Committee, "Numbering Plan for
                           the International Telephone Service",
                           CCITT Recommendation E.163, 1988.

   [CCITT.X121.1988]       International Telephone and Telegraph
                           Consultative Committee, "International
                           Numbering Plan for the Public Data Networks",
                           CCITT Recommendation X.121, 1988.

   [CCITT.X520.1988]       International International Telephone and
                           Telegraph Consultative Committee,
                           "Information Technology - Open Systems
                           Interconnection - The Directory: Selected
                           Attribute Types", CCITT Recommendation X.520,
                           November 1988.

   [CCITT.X521.1988]       International International Telephone and
                           Telegraph Consultative Committee,
                           "Information Technology - Open Systems
                           Interconnection - The Directory: Selected
                           Object Classes", CCITT Recommendation X.521,
                           November 1988.

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

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

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

   [RFC2119]               Bradner, S., "Key words for use in RFCs to
                           Indicate Requirement Levels", BCP 14,
                           RFC 2119, March 1997.

   [RFC2425]               Howes, T., Smith, M., and F. Dawson, "A MIME
                           Content-Type for Directory Information",
                           RFC 2425, September 1998.

   [RFC2426]               Dawson, F. and T. Howes, "vCard MIME
                           Directory Profile", RFC 2426, September 1998.

   [RFC2616]               Fielding, R., Gettys, J., Mogul, J., Frystyk,
                           H., Masinter, L., Leach, P., and T. Berners-
                           Lee, "Hypertext Transfer Protocol --
                           HTTP/1.1", RFC 2616, June 1999.

   [RFC2739]               Small, T., Hennessy, D., and F. Dawson,
                           "Calendar Attributes for vCard and LDAP",
                           RFC 2739, January 2000.

   [RFC2822]               Resnick, P., "Internet Message Format",
                           RFC 2822, April 2001.

   [RFC2978]               Freed, N. and J. Postel, "IANA Charset
                           Registration Procedures", BCP 19, RFC 2978,
                           October 2000.

   [RFC3629]               Yergeau, F., "UTF-8, a transformation format
                           of ISO 10646", STD 63, RFC 3629,
                           November 2003.

   [RFC3966]               Schulzrinne, H., "The tel URI for Telephone
                           Numbers", RFC 3966, December 2004.

   [RFC3986]               Berners-Lee, T., Fielding, R., and L.
                           Masinter, "Uniform Resource Identifier (URI):
                           Generic Syntax", STD 66, RFC 3986,
                           January 2005.

   [RFC4122]               Leach, P., Mealling, M., and R. Salz, "A
                           Universally Unique IDentifier (UUID) URN
                           Namespace", RFC 4122, July 2005.

   [RFC4288]               Freed, N. and J. Klensin, "Media Type
                           Specifications and Registration Procedures",
                           BCP 13, RFC 4288, December 2005.

   [RFC4646]               Phillips, A. and M. Davis, "Tags for
                           Identifying Languages", BCP 47, RFC 4646,
                           September 2006.

   [RFC4770]               Jennings, C. and J. Reschke, Ed., "vCard
                           Extensions for Instant Messaging (IM)",
                           RFC 4770, January 2007.

   [RFC5234]               Crocker, D. and P. Overell, "Augmented BNF
                           for Syntax Specifications: ABNF", STD 68,
                           RFC 5234, January 2008.

   [oldreference_UNICODE]  The International Organization for
                           Standardization, "The Unicode Standard -
                           Version 2.0", The Unicode Consortium",
                           July 1996.

   [oldreference_VCARD]    Internet Mail Consortium, "vCard - The
                           Electronic Business Card Version 2.1",
                           September September.

10.2.

14.2.  Informative References

   [ISO9070]               The International Organization for
                           Standardization, "ISO 9070, Information
                           Processing - SGML support facilities -
                           Registration Procedures for Public Text Owner
                           Identifiers", April 1991.

   [RFC3406]               Daigle, L., van Gulik, D., Iannella, R., and
                           P. Faltstrom, "Uniform Resource Names (URN)
                           Namespace Definition Mechanisms", BCP 66,
                           RFC 3406, October 2002.

   [WGS84]                 National Imagery and Mapping Agency,
                           "Department of Defense World Geodetic System
                           1984, Third Edition", NIMA TR8350.2,
                           January 2000.

URIs

   [1]  <mailto:vcard@ietf.org>

   [2]  <mailto:iana@iana.org>

Appendix A.  Differences from RFCs 2425 and 2426

   This appendix contains a list of changes that have been made in the
   vCard specification from RFCs 2425 and 2426.

A.1.  New Structure

   o  [RFC2425] and [RFC2426] have been merged.  Initially [RFC2425] was
      intended to be extensible but only 2426 ever extended it.

   o  vCard is now not only a MIME type but a stand-alone format.

   o  A proper MIME type registration form has been included.

   o  UTF-8 is now the default character set.

   o  New vCard elements can be registered from IANA.

A.2.  Removed Features

   o  The group construct (i.e.  GROUP.PROPERTY:...) no longer exists.

   o  The CONTEXT and CHARSET parameters are no more.

   o  The MAILER property is no more.

   o  The "intl", "dom", "postal", and "parcel" TYPE parameter values
      for the ADR and LABEL properties have been removed.

A.3.  New Properties and Parameters

   o  The KIND, GENDER, LANG, DDAY, BIRTH, and DEATH properties have
      been added.

   o  [RFC2739], which defines the FBURL, CALADRURI, CAPURI, and CALURI
      properties, has been merged in.

   o  [RFC4770], which defines the IMPP property, has been merged in.

   o  The "work", "home", and "uri" TYPE parameter values for the EMAIL
      property have been added.

A.4.  Other Changes

   o  Synchronization is addressed in Section 8.

   o  The N property is no longer mandatory.

   o  The value of TEL is now a URI.

Appendix B.  Change Log (to be removed by RFC Editor prior to
             publication)

B.1.  Changes in -01

   o  Merged [RFC2739] in.

   o  Converted all foobar.com, abc.com, etc. to example.com.

   o  Fixed bugs in ABNF.

   o  Made explicit that coordinates in the GEO property are expressed
      in the WGS 84 reference system.

   o  Clarified folding issues with multi-byte characters.

   o  Made the value of TEL a URI.

   o  Added the UID parameter.

   o  Made the UID property's value type a URI.

   o  Added Section 8.

   o  Created IANA process for registering new parameters, value types,
      and properties.

   o  Created the initial IANA registries.

   o  Created vendor namespace based on text from RFC 4288.

B.2.  Changes in -00

   o  Name change because draft has been accepted as WG item.
      Otherwise, same as draft-resnick-vcarddav-vcardrev-01.

   o  Removed reference to RFC 2234.

   o  Fixed errata from
      http://www.rfc-editor.org/errata_search.php?rfc=2426.

   o  Removed passage referring to RFC 2425 profiles.

   o  Renamed Section 5.4 7.4 from "Telecommunications Adressing Properties"
      to "Communications Properties.

   o  Added Appendix A and Appendix B.

   o  Added reference to [RFC4770].

   o  Removed the group construct.

   o  Made the N property no longer mandatory.

   o  Added the KIND property.

   o  Clarified meaning of TYPE parameter value for PHOTO, LOGO, KEY,
      and SOUND.

   o  Removed the CONTEXT parameter.

   o  Removed the MAILER property.

   o  Made reference to [ISO9070] informative.

   o  Removed "intl", "dom", "postal", and "parcel" TYPE parameter
      values for the ADR and LABEL properties.

   o  Clarified meaning of "extended address" ADR field.

   o  Mentioned [RFC3406] as another method of generating PRODID values.

   o  Updated obsolete references.

   o  Allowed BDAY and DDAY value types to be text values for fuzzy
      dates.

   o  Removed the CHARSET property.  Now the encoding is always UTF-8,
      except when overridden by the Content-Type (which is considered a
      compatibility feature).

Authors' Addresses

   Peter W. Resnick
   QUALCOMM Incorporated
   5775 Morehouse Drive
   San Diego, CA  92121-1714
   US

   Phone: +1 858 651 4478
   EMail: presnick@qualcomm.com
   URI:   http://www.qualcomm.com/~presnick/

   Simon Perreault
   Viagenie
   2600 boul. Laurier, suite 625
   Quebec, QC  G1V 4W1
   Canada

   Phone: +1 418 656 9254
   EMail: simon.perreault@viagenie.ca
   URI:   http://www.viagenie.ca

Full Copyright Statement

   Copyright (C) The IETF Trust (2008).

   This document is subject to the rights, licenses and restrictions
   contained in BCP 78, and except as set forth therein, the authors
   retain all their rights.

   This document and the information contained herein are provided on an
   "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
   OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
   THE INTERNET ENGINEERING TASK FORCE DISCLAIM 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.

Intellectual Property

   The IETF takes no position regarding the validity or scope of any
   Intellectual Property Rights or other rights that might be claimed to
   pertain to the implementation or use of the technology described in
   this document or the extent to which any license under such rights
   might or might not be available; nor does it represent that it has
   made any independent effort to identify any such rights.  Information
   on the procedures with respect to rights in RFC documents can be
   found in BCP 78 and BCP 79.

   Copies of IPR disclosures made to the IETF Secretariat and any
   assurances of licenses to be made available, or the result of an
   attempt made to obtain a general license or permission for the use of
   such proprietary rights by implementers or users of this
   specification can be obtained from the IETF on-line IPR repository at
   http://www.ietf.org/ipr.

   The IETF invites any interested party to bring to its attention any
   copyrights, patents or patent applications, or other proprietary
   rights that may cover technology that may be required to implement
   this standard.  Please address the information to the IETF at
   ietf-ipr@ietf.org.

Acknowledgements

   Funding for the RFC Editor function is provided by the IETF
   Administrative Support Activity (IASA).  This document was produced
   using xml2rfc v1.32 (of http://xml.resource.org/) from a source in
   RFC-2629 XML format.