]> Viagénie

2600 boul. Laurier, suite 625 Québec QC G1V 4W1 Canada +1 418 656 9254 simon.perreault@viagenie.ca http://www.viagenie.ca

QUALCOMM Incorporated

5775 Morehouse Drive San Diego CA 92121-1714 US +1 858 651 4478 presnick@qualcomm.com http://www.qualcomm.com/~presnick/

Applications vcard 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.).

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.

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 .

ietf-types@iana.org Registration of media type text/vcard text vcard none charset The "charset" MIME parameter is interpreted as defined in , section 4.1.2. If it is omitted, the default encoding is UTF-8 as defined in . See . The text/vcard media type is intended to identify vCard data of any version. There are older specifications of 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 ) 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 draft-ietf-vcarddav-vcardrev-04 They are numerous, diverse, and include mail user agents, instant messaging clients, address book applications, directory servers, customer relationship management software, etc. .vcf Simon Perreault <simon.perreault@viagenie.ca> COMMON none Simon Perreault and Pete Resnick IETF

The text/vcard MIME content type (hereafter known as "vCard") contains contact information, typically pertaining to a single contact or group of contacts. The content consists of one or more lines in the format given below.

Individual lines within vCard are delimited by the line break, which is a CRLF sequence (ASCII decimal 13, followed by ASCII decimal 10). Long logical lines of 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 , 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 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 moving from this folded multiple-line representation of a property definition to its single line representation is called unfolding. Unfolding is accomplished by regarding CRLF immediately followed by a white space character (namely HTAB ASCII decimal 9 or SPACE ASCII decimal 32) as equivalent to no characters at all (i.e., the CRLF and single white space character are removed). Note: It is possible for very simple implementations to generate improperly folded lines in the middle of a UTF-8 multi-octet sequence. For this reason, implementations SHOULD unfold lines in such a way as to properly restore the original sequence. Note: Unfolding is done differently than in . Unfolding in only removes the CRLF, not the space following it. Folding is done after any content encoding of a type value. Unfolding is done before any decoding of a type value in a content line.

The following ABNF uses the notation of , which also defines CRLF, WSP, DQUOTE, VCHAR, ALPHA, and DIGIT. After the unfolding of any folded lines as described above, the syntax for a line of this content type is as follows:

contentline = [group "."] name *(";" param) ":" value CRLF ; When parsing a content line, folded lines MUST first ; be unfolded according to the unfolding procedure ; described above. ; When generating a content line, lines longer than 75 ; characters SHOULD be folded according to the folding ; procedure described above. group = "WORK" / "HOME" / iana-token / x-name 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 line that begins with a white space character is a continuation of the previous line, as described above. The white space character and immediately preceeding CRLF should be discarded when reconstructing the original line. Note that this line-folding convention differs from that found in , in that the sequence <CRLF><WSP> found anywhere in the content indicates a continued line and should be removed. Property names and parameter names are case insensitive (e.g., the property name "fn" is the same as "FN" and "Fn"). Parameter values MAY be case sensitive or case insensitive, depending on their definition. The group construct is used to group related properties together. For example, groups named "WORK" and "HOME" could be used to segregate properties such as telephone number, address, etc. Displaying of groups is left entirely up to the application. Predefined groups with assigned meaning are listed in . It is possible to register new groups from IANA. Unregistered groups MAY be used and MUST start with "X-". Each property defined in a vCard instance MAY have multiple values. The general rule for encoding multi-valued properties is to simply create a new content line for each value (including the property name). However, it should be noted that some value types support encoding multiple values in a single content line by 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.

Lists of values are delimited by a list delimiter, specified by the COMMA character (ASCII decimal 44). A COMMA character in a value MUST be escaped with a BACKSLASH character (ASCII decimal 92). Compound type values are delimited by a field delimiter, specified by the SEMI-COLON character (ASCII decimal 59). A SEMI-COLON in a component of a compound property value MUST be escaped with a BACKSLASH character (ASCII decimal 92). 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 / utc-offset / iana-valuespec text-list = *TEXT-LIST-CHAR *("," *TEXT-LIST-CHAR) TEXT-LIST-CHAR = "\\" / "\," / "\n" / <any VALUE-CHAR except , or \ or newline> ; Backslashes, newlines, and commas must be encoded. ; \n or \N can 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 by [RFC2047].> date = date-fullyear ["-" date-month ["-" date-mday]] date-fullyear = 4DIGIT date-month = 2DIGIT ;01-12 date-mday = 2DIGIT ;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 = 2DIGIT ;00-23 time-minute = 2DIGIT ;00-59 time-second = 2DIGIT ;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, as defined in section 12 of this document>

"text": The "text" value type should be used to identify values that contain human-readable text. The character set in which the text is represented is controlled by the "charset" MIME type parameter. Note that there is no way to override this parameter on a per-property basis. As for the language, it is controlled by the "language" property parameter defined in .

Examples for "text": this is a text value this is one value,this is another this is a single value\, with a comma encoded

A formatted text line break in a text value type MUST be represented as the character sequence backslash (ASCII decimal 92) followed by a Latin small letter n (ASCII decimal 110) or a Latin capital letter N (ASCII decimal 78), that is "\n" or "\N".

For example a multiple line DESCRIPTION value of: Mythical Manager Hyjinx Software Division BabsCo, Inc.

could be represented as: DESCRIPTION:Mythical Manager\nHyjinx Software Division\n BabsCo\, Inc.\n demonstrating the \n literal formatted line break technique, the CRLF-followed-by-space line folding technique, and the backslash escape technique.

"uri": The "uri" value type should be used to identify values that are referenced by a URI (including a Content-ID URI), instead of encoded 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 . Note that the value of 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

"date", "time", and "date-time": Each of these value types is based on a subset of the definitions in standard. Multiple "date" 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" value type is used to express boolen values. These values are case insensitive.

Examples: TRUE false True

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

Examples: 1234567890 -1234556790 +1234556790,432109876

"float": The "float" value type is used to express real numbers. 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 be specified in the PHOTO, LOGO, SOUND, and KEY types. If inline encoded binary data is specified, the ENCODING type parameter MUST be used to specify the encoding format. The binary data MUST be encoded using the "B" encoding format. Long lines of encoded binary data SHOULD BE folded to 75 characters using the folding method defined in .

"utc-offset": The "utc-offset" value type specifies that the type value is a signed offset from UTC. This value type can be specified in the TZ type. The value type is an offset from Coordinated Universal Time (UTC). It is specified as a positive or negative difference in units of hours and minutes (e.g., +hh:mm). The time is specified as a 24-hour clock. Hour values are from 00 to 23, and minute values are from 00 to 59. Hour and minutes are 2-digits with high order zeroes required to maintain digit count. The extended format for ISO 8601 UTC offsets MUST be used. The extended format makes use of a colon character as a separator of the hour and minute text fields.

A property can have attributes associated with it. These "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 specified as quoted-string text values. Property parameter values MUST NOT contain the DQUOTE (US-ASCII decimal 22) character. The DQUOTE (US-ASCII decimal 22) character is used as a delimiter for parameter values that contain restricted characters or URI text. For example:

EMAIL;PID=8:jdoe@example.com

Property parameter values that are not in quoted strings are case insensitive. The general property parameters defined by this memo are defined by the following notation:

vcardparameter = encodingparam / valuetypeparam / languageparam / pref-param / pid-param encodingparam = "encoding" "=" encodingtype encodingtype = "b" ; from [RFC2047] / iana-token ; registered as described in ; section 12 of this document valuetypeparam = "value" "=" valuetype valuetype = "uri" ; URI from Appendix A of [RFC3986] / "text" / "date" / "time" / "date-time" ; date time / "integer" / "boolean" / "float" / x-name / iana-token ; registered as described in ; section 12 of this document languageparam = "language" "=" Language-Tag ; Language-Tag is defined in section 2.1 of RFC 4646 pref-param = "pref" pid-param = ("pid" "=" 1*DIGIT)

Applications MUST ignore x-param and iana-param value they don't recognize.

The "language" property parameter is used to identify data in multiple languages. There is no concept of "default" language, except as specified by any "Content-Language" MIME header parameter that is present. The value of the "language" property parameter is a language tag as defined in Section 2 of .

The "encoding" property parameter is used to specify an alternate encoding for a value. If the value contains a CRLF, it must be encoded, since CRLF is used to separate lines in the content-type itself. Currently, only the "b" encoding is supported. The "b" encoding can also be useful for binary values 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 multiple physical lines by using the line folding technique described above. The Content-Transfer-Encoding header field is used to specify the encoding used for the body part as a whole. The "encoding" 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 the one certificate value might specify an encoding of "b" via an "encoding=b" property parameter. The Content-Transfer-Encoding and the encodings of individual properties given by the "encoding" property parameter are independent of one another. When encoding a 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.

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 is encouraged even if the value parameter is not explicity used. By defining a standard set of value types and their formats, existing parsing and processing code can 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 the value type 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 particular value types for all of the items for which it is searching. Because the value type is explicit in the definition, the search engine could look for dates in any item type and provide results that can still be interpreted.

The "pid" parameter is used to identify a specific property among multiple instances. It plays a role analogous to the UID property () on a per-property instead of per-vCard basis. It MUST NOT appear more than once in a given property. It MUST NOT appear on properties that only may have one instance per vCard. Its value is a small integer. Note that the "pid" parameter's value is not globally unique, so it is possible for duplicate values to be created.

The "type" parameter has multiple, different uses. In general, it is a way of specifying class characteristics of the associated property. Most of the time, its value is a comma-separated subset of a pre-defined enumeration. In this document, the following properties make use of this parameter: PHOTO, ADR, LABEL, TEL, EMAIL, IMPP, LOGO, MEMBER, SOUND, and KEY.

What follows is an enumeration of the standard vCard properties.

To denote the beginning of a syntactic entity within a text/vcard content-type. text The content entity MUST begin with the BEGIN property with a value of "VCARD". The BEGIN property is used in conjunction with the END property to 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 entities within the same text/vcard content-type or to define content that can be identifiable outside of a MIME environment.

BEGIN:VCARD

To denote the end of a syntactic entity within a text/vcard content-type. text The content entity MUST end with the END type with a value of "VCARD". The END property is used in conjunction with the BEGIN property to 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 entities within the same text/vcard content-type or to define content that can be identifiable outside of a MIME environment.

END:VCARD

To identify the source of directory information contained in the content type. uri The SOURCE property is used to provide the means by which applications knowledgable in the given directory service protocol can obtain additional or more up-to-date information from the directory service. It contains a URI as defined in and/or other information referencing the vCard to which the information pertains. When directory information is available from more than one source, the sending entity can pick what it considers to be the best source, or multiple SOURCE properties can be included.

SOURCE:ldap://ldap.example.com/cn=Babs%20Jensen,%20o=Babsco,%20c=US SOURCE:http://directory.example.com/addressbooks/jdoe/ Jean%20Dupont.vcf

To identify the displayable name of the directory entity to which information in the vCard pertains. text The NAME property is used to convey the display name of the entity to which the directory information pertains. Its value is the displayable, presentation text associated with the source for the vCard, as specified in the SOURCE property.

NAME:Babs Jensen's Contact Information

To specify the kind of object the vCard represents. A single text value. The value may be one of: "individual" for a single person, "group" for a group of people, "org" for an organization, "location" for a named geographical place, an x-name or an iana-token. If this property is absent, "individual" MUST be assumed as default.

This represents someone named Jane Doe working in the marketing department of the 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

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

To specify the formatted text corresponding to the name of the object the vCard represents. A single text value. This property is based on the semantics of the X.520 Common Name attribute. The property MUST be present in the vCard object.

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

To specify the components of the name of the object the vCard represents. A single structured text value. Each component can have multiple values. The structured property value corresponds, in sequence, to the Surname, Given 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 present in the vCard object when the name of the object the vCard represents follows the X.520 model.

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

To specify the text corresponding to the nickname of the object the vCard represents. One or more text values separated by a COMMA character (ASCII decimal 44). The nickname is the descriptive name given instead of or in addition to the one belonging to a person, place, or thing. It can also be used to specify a familiar form of a proper name specified by the FN or N properties.

NICKNAME:Robbie NICKNAME:Jim,Jimmie

To specify an image or photograph information that annotates some aspect of the object the vCard represents. 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 is used and no explicit ENCODING parameter is needed. A single value. The default is binary value. It can also be reset to uri value. The uri value can be used to specify a value outside of this MIME entity. This property SHOULD include the parameter "TYPE" to specify the graphic image format type. The TYPE parameter value MUST be an image media type as specified in . The full media type name, including the "image/" prefix, should be used. However, implementations SHOULD be able to handle bare subtypes.

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

To specify the birth date of the object the vCard represents. The default is a single date value. It can also be reset to a single date-time or text value.

BDAY:1996-04-15 BDAY:1953-10-15T23:10:00Z BDAY;VALUE=text:circa 1800

To specify the date of death of the object the vCard represents. The default is a single date value. It can also be reset to a single date-time or text value.

To specify the place of birth of the object the vCard represents. A single text value.

BIRTH:Babies'R'Us Hospital

To specify the place of death of the object the vCard represents. A single text value.

DEATH:Aboard the Titanic\, near Newfoundland

To specify the gender of the object the vCard represents. A single text value. The value "M" stands for male while "F" stands for female.

GENDER:F

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

To specify the components of the delivery address for the vCard object. A single structured text value, separated by the SEMI-COLON character (ASCII decimal 59). 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 property can include the "PREF" parameter to indicate the preferred delivery address when more than one address is specified. Example: In this example the post office box and the extended address are absent.

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

To specify the formatted text corresponding to delivery address of the object the vCard represents. A single text value. The property value is formatted text that can be used to present a delivery address label for the vCard object. The property can include the "PREF" parameter to indicate the preferred delivery address when more than one address is specified. Example: A multi-line address label.

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

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

To specify the telephone number for telephony communication with the object the vCard represents. A single URI value. It is expected that the URI scheme will be "tel", as specified in , but other schemes MAY be used. This property is based on the X.520 Telephone Number attribute. The property can include the "PREF" parameter to indicate a prefered-use telephone number. The property can include the parameter "TYPE" to specify intended use for the telephone number. The TYPE parameter values can include: "text" to indicate the telephone number supports text messages, "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. The default type is "voice". These type parameter values can be specified as a parameter list (i.e., "TYPE=text;TYPE=voice") or as a value list (i.e., "TYPE=text,voice"). The default can be overridden to another set of values by specifying one or more alternate values. For example, the default TYPE of "voice" can be reset to a VOICE and FAX telephone number by the value list "TYPE=voice,fax". Example:

WORK.TEL;PREF;TYPE=voice,msg:tel:+1-555-555-5555;ext=5555 HOME.TEL:tel:+33-01-23-45-67

To specify the electronic mail address for communication with the object the vCard represents. A single text value. The property can include tye "PREF" parameter to indicate a preferred-use email address when more than one is specified. Type example:

WORK.EMAIL:jqpublic@xyz.example.com EMAIL;PREF:jane_doe@example.com

To specify the URI for instant messaging and presence protocol communications with the object the vCard represents. A single URI. The property may include the "PREF" parameter to indicate that this is a preferred address and has the same semantics as the "PREF" parameter in a TEL property.

IMPP;PREF:xmpp:alice@example.com

To specify the language(s) that may be used for contacting the individual associated with the vCard. A list of text values. The list is to be interpreted as defined in , Section 14.4, i.e. as 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 be escaped.

LANG:fr,en\;q=0.9

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

To specify information related to the time zone of the object the vCard represents. The default is a single utc-offset value. It can also be reset to a single text value. 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.

To specify information related to the global positioning of the object the vCard represents. A single structured value consisting of two float values separated by the SEMI-COLON character (ASCII decimal 59). This property specifies information related to the global position of the object associated with the vCard. The value specifies latitude and longitude, in that order (i.e., "LAT LON" ordering). The longitude represents the location east and west of the prime meridian as a positive or negative real number, respectively. The latitude represents the location north and south of the equator as a positive or negative real number, respectively. The longitude and latitude values MUST be expressed in the reference system. They MUST be specified as decimal degrees and should be specified to six decimal places. This will allow for granularity within a meter of the geographical position. The text components are separated by the SEMI-COLON character (ASCII decimal 59). The simple formula for converting degrees-minutes-seconds into decimal degrees is:

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

Example:

GEO:37.386013;-122.082932

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

To specify the job title, functional position or function of the object the vCard represents. A single text value. This property is based on the X.520 Title attribute. Example:

TITLE:Director\, Research and Development

To specify information concerning the role, occupation, or business category of the object the vCard represents. A single text value. This property is based on the X.520 Business Category explanatory attribute. This property is included as an organizational type to avoid confusion with the semantics of the TITLE property and incorrect usage of that property when the semantics of this property is intended. Example:

ROLE:Programmer

To specify a graphic image of a logo associated with the object the vCard represents. 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. A single value. The default is binary value. It can also be reset to uri value. The uri value can be used to specify a value outside of this MIME entity. This property SHOULD include the parameter "TYPE" to specify the graphic image format type. The TYPE parameter value MUST be an image media type as specified in . The full media type name, including the "image/" prefix, should be used. However, implementations SHOULD be able to handle bare subtypes. Example:

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

To specify the organizational name and units associated with the vCard. A single structured text value consisting of components separated the SEMI-COLON character (ASCII decimal 59). The property is based on the X.520 Organization Name and Organization Unit attributes. The property value is a structured type consisting of the organization name, followed by one or more levels of organizational unit names. Example: A property value consisting of an organizational name, organizational unit #1 name and organizational unit #2 name.

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

To include a member in the group this vCard represents. A single URI. It MAY refer to something other than a vCard object. For example, an e-mail distribution list could employ the "mailto" URI scheme for efficiency. This property MUST NOT be present unless the value of the KIND property is "group". Examples:

BEGIN:VCARD VERSION:4.0 KIND:group FN:The Doe family MEMBER:urn:uuid:03a0e51f-d1aa-4385-8a53-e29025acd8af MEMBER:urn:uuid:b8767877-b4a1-4c70-9acc-505d3819e519 END:VCARD BEGIN:VCARD VERSION:4.0 FN:John Doe UID:urn:uuid:03a0e51f-d1aa-4385-8a53-e29025acd8af END:VCARD BEGIN:VCARD VERSION:4.0 FN:Jane Doe UID:urn:uuid:b8767877-b4a1-4c70-9acc-505d3819e519 END:VCARD

BEGIN:VCARD VERSION:4.0 KIND:group FN:Funky distribution list MEMBER:mailto:subscriber1@example.com MEMBER:xmpp:subscriber2@example.com MEMBER:sip:subscriber3@example.com MEMBER:tel:+1-418-555-5555 END:VCARD

To specify a relationship the individual this vCard represents has with another. A single URI. The TYPE parameter MAY be used to characterize the related individual. The understood types are: "parent" means that the related individual is the parent of the individual this vCard represents. "child" means the opposite of "parent". "sibling" means that the two individuals are siblings. "manager" means that the related individual is the direct hierarchical superior (i.e. supervisor or manager) of the individual this vCard represents. "assistant" for an assistant or secretary. "agent" for a person who will act on behalf of the individual or resource associated with the vCard. Other types may be registered to IANA as described in , and private extensions starting with "X-" may be used. Examples:

RELATED;TYPE=manager:urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6 RELATED;TYPE=assistant:http://example.com/directory/jdoe.vcf

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

To specify application category information about the vCard. One or more text values separated by a COMMA character (ASCII decimal 44). Example:

CATEGORIES:TRAVEL AGENT CATEGORIES:INTERNET,IETF,INDUSTRY,INFORMATION TECHNOLOGY

To specify supplemental information or a comment that is associated with the vCard. A single text value. The property is based on the X.520 Description attribute. Example:

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

To specify the identifier for the product that created the vCard object. A single text value. Implementations SHOULD use a method such as that specified for Formal Public Identifiers in or for Universal Resource Names in to assure that the text value is unique. Example:

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

To specify revision information about the current vCard. The default is a single date-time value. Can also be reset to a single date value. The value distinguishes the current revision of the information in this vCard for other renditions of the information. Example:

REV:1995-10-31T22:27:10Z REV:1997-11-15

To specify the family name or given name text to be used for national-language-specific sorting of the FN and N types. A single text value. The sort string is used to provide family name or given name text that is to be used in locale- or national-language- specific sorting of the formatted name and structured name types. Without this information, sorting algorithms could incorrectly sort this vCard within a sequence of sorted vCards. When this property is present in a vCard, then this family name or given name value is used for sorting the vCard. Examples: For the case of family name sorting, the following examples define common sort string usage with 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

To specify a digital sound content information that annotates some aspect of the vCard. By default this property is used to specify the proper pronunciation of the name property value of the vCard. 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. A single value. The default is binary value. It can also be reset to uri value. The uri value can be used to specify a value outside of this MIME entity. 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 . 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...>

To specify a value that represents a globally unique identifier corresponding to the individual or resource associated with the vCard. A single URI value. The type is used to uniquely identify the object that the vCard represents. The "uuid" URN namespace defined in is particularly well-suited to this task, but other URI schemes MAY be used. This property MUST NOT appear more than once in a given vCard. Example:

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

To specify a uniform resource locator associated with the object that the vCard refers to. A single uri value. Example:

URL:http://example.org/restaurant.french/~chezchic.html

To specify the version of the vCard specification used to format this vCard. A single text value. 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

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

To specify the access classification for a vCard object. A single text value. An access classification is only one component of the general security model for a directory service. The classification attribute provides a method of capturing the intent of the owner for general access to information described by the vCard object. Predefined values are: This vCard MAY be shared with anyone. This vCard MUST NOT be shared. It MAY be exported if explictly authorized and requested by the creator. This vCard MAY be shared with allowed users or systems. The exact confidentiality level is site-specific and out of scope for the vCard specification. Examples:

CLASS:PUBLIC CLASS:PRIVATE CLASS:CONFIDENTIAL

To specify a public key or authentication certificate associated with the object that the vCard represents. The encoding MUST be reset to "b" using the ENCODING parameter in order to specify inline, encoded binary data. If the value is a text value, then the default encoding of 8bit is used and no explicit ENCODING parameter is needed. A single value. The default is binary. It can also be reset to text value. The text value can be used to specify a text key. This property SHOULD include the parameter "TYPE" to specify the public key or authentication certificate format. The TYPE parameter value MUST be a media type as specified in . Example:

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

These properties are further specified in .

To specify the URI for a user's busy time in a vCard object. A single URI value. Where multiple FBURL properties are specified, the default FBURL property is indicated with the PREF parameter. The FTP or HTTP type of URI points to an iCalendar object associated with a snapshot of the last six weeks of the user's busy time data. If the iCalendar object is represented as a file or document, it's file type should be "ifb".

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

To specify the location to which an event request should be sent for the user. A single URI value. Where multiple CALADRURI properties are specified, the default CALADRURI property is indicated with the PREF parameter.

CALADRURI;PREF:mailto:janedoe@example.com CALDARURI:http://example.com/calendar/jdoe

To specify the URI for a user's calendar in a vCard object. A single URI value. 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".

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

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.

vCard data often needs to be synchronized between devices. In this context, synchronization is defined as the intelligent merging of two representations of the same object. vCard 4.0 includes mechanisms to aid this process.

Two vCards for which the UID properties () are equivalent MUST be considered representations of the same object. Equivalence is determined as specified in , Section 6. vCards without a UID property MAY be matched to vCards with a UID property where a synchronization engine determines there is sufficient similarity to assume equivalence. The particular strategy and criteria used is out of scope for this document. Updates to vCards with multiple instances of particular properties MAY use the PID associated with each property to aid in determining what values have changed. Since PIDs are not globally unique, they can only be used as guidelines to synchronization engine logic. Such logic is out of scope for this document.

Two vCards are to be synchronized:

BEGIN:VCARD VERSION:4.0 UID:urn:uuid:77a01597-0603-40f3-8138-36deca8618da FN:Jane Doe HOME.TEL;PID=1:tel:+33-01-23-45-67 HOME.TEL;PID=3:tel:+1-800-555-1234 EMAIL;PID=1:jdoe@example.com IMPP;PREF:xmpp:jdoe@example.com END:VCARD

BEGIN:VCARD VERSION:4.0 UID:urn:uuid:77a01597-0603-40f3-8138-36deca8618da FN:Jane Doe HOME.TEL;PID=1:tel:+33-01-23-45-67 HOME.TEL;PID=4:tel:+1-800-555-5678 EMAIL;PID=1:jdoe@example.com IMPP;PREF:xmpp:jdoe@example.com END:VCARD

Assuming a synchronization engine is presented with the two vCards, it may decide based upon logic out of scope of this document, that both vCards are representations of the same object, and create a merged vCard such as:

BEGIN:VCARD VERSION:4.0 UID:urn:uuid:77a01597-0603-40f3-8138-36deca8618da FN:Jane Doe HOME.TEL;PID=1:tel:+33-01-23-45-67 HOME.TEL;PID=3:tel:+1-800-555-1234 HOME.TEL;PID=4:tel:+1-800-555-5678 EMAIL;PID=1:jdoe@example.com IMPP;PREF:xmpp:jdoe@example.com END:VCARD

If the synchronization engine then is presented with an updated vCard such as:

BEGIN:VCARD VERSION:4.0 UID:urn:uuid:77a01597-0603-40f3-8138-36deca8618da FN:Jane Doe HOME.TEL;PID=1:tel:+33-01-23-45-67 HOME.TEL;PID=4:tel:+1-800-555-5678 EMAIL;PID=1:jdoe@example.com IMPP;PREF:xmpp:jdoe@example.com END:VCARD

It may use the PIDs on each property to determine that the second phone number in the sequence has been deleted. Note that there may be data beyond what is available within a vCard, such as a speed dial number, that is specific to each individual property instance, which is why providing a correlation between versions is significant.

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

;******************************************* ; Basic vCard Definition ;******************************************* vcard-entity = 1*(vcard) vcard = "BEGIN" ":" "VCARD" 1*CRLF 1*(contentline) ;A vCard object MUST include the VERSION and FN properties. "END" ":" "VCARD" 1*CRLF contentline = [group "."] name *(";" param ) ":" value CRLF ; When parsing a content line, folded lines must first ; be unfolded according to the unfolding procedure ; described above. When generating a content line, lines ; longer than 75 characters SHOULD be folded according to ; the folding procedure described in [MIME DIR]. group = "WORK" / "HOME" / iana-token / x-name 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 = WSP / %x21 / %x23-7E / NON-ASCII ; Any character except CTLs, DQUOTE SAFE-CHAR = WSP / %x21 / %x23-2B / %x2D-39 / %x3C-7E / NON-ASCII ; Any character except CTLs, DQUOTE, ";", ":", "," VALUE-CHAR = WSP / VCHAR / NON-ASCII ; Any textual character ;******************************************* ; vCard Type Definition ; ; Provides type-specific definitions for how the ; "value" and "param" are defined. ;******************************************* ; **** NAME **** param = "" ; No parameters allowed value = text-value ; **** KIND **** param = "" ; No parameters allowed value = kind-value kind-value = "individual" / "group" / "org" / x-name / iana-token ; **** PROFILE **** param = "" ; No parameters allowed value = text-value ; Value MUST be the case insensitive value "VCARD ; **** SOURCE **** param = source-param ; Only source parameters allowed value = uri source-param = ("VALUE" "=" "uri") / (x-name "=" *SAFE-CHAR) ; **** FN **** ;This type MUST be included in a vCard object. param = text-param ; Text parameters allowed value = text-value ; **** N **** param = text-param ; Text parameters allowed value = n-value n-value = 0*3(text-value *("," text-value) ";") text-value *("," text-value) ; Surname; Given Names; Prefix; Suffix. ; **** NICKNAME **** param = text-param / pid-param ; Text parameters allowed value = text-value-list ; **** PHOTO **** param = pid-param / img-inline-param / img-refer-param value = img-inline-value ; Value and parameter MUST match value =/ img-refer-value ; Value and parameter MUST match ; **** BDAY **** param = ("VALUE" "=" "date") ; Only value parameter allowed param =/ ("VALUE" "=" "date-time") ; Only value parameter allowed value = date-value ; Value MUST match value type value =/ date-time-value ; Value MUST match value type ; **** ADR **** param = text-param / pref-param / pid-param value = adr-value ; **** LABEL **** param = text-param / pref-param / pid-param value = text-value ; **** TEL **** param = pref-param / tel-param / pid-param ; Only tel parameters allowed value = uri-value tel-param = "TYPE" "=" tel-type *("," tel-type) tel-type = "VOICE" / "FAX" / "CELL" / "PAGER" / "VIDEO" / "TEXT" / iana-token / x-name ; Values are case insensitive ; **** EMAIL **** param = pref-param / pid-param value = text-value ; **** TZ **** param = "" ; No parameters allowed value = utc-offset-value ; **** GEO **** param = "" ; No parameters allowed value = float-value ";" float-value ; **** TITLE **** param = text-param / pid-param ; Only text parameters allowed value = text-value ; **** ROLE **** param = text-param / pid-param ; Only text parameters allowed value = text-value ; **** LOGO **** param = pid-param / img-inline-param / img-refer-param value = img-inline-value / img-refer-value ; Value and parameter MUST match ; **** ORG **** param = text-param / pid-param ; Only text parameters allowed value = org-value org-value = *(text-value ";") text-value ; First is Organization Name, remainder are Organization Units. ; **** MEMBER **** param = pid-param value = uri ; Any valid URI scheme ; **** RELATED **** param = ("TYPE" "=" related-type) / pid-param ; Value is case insensitive value = uri ; Any valid URI scheme related-type = "parent" / "child" / "sibling" / "manager" / "assistant" / iana-token / "X-" word ; Values are case insensitive ; **** CATEGORIES **** param = text-param / pid-param ; Only text parameters allowed value = text-value-list ; **** NOTE **** param = text-param / pid-param ; Only text parameters allowed value = text-value ; **** PRODID **** param = "" ; No parameters allowed value = text-value ; **** REV **** param = ["VALUE" "=" "date-time"] ; Only value parameters allowed. Values are case insensitive. param =/ "VALUE" "=" "date" ; Only value parameters allowed. Values are case insensitive. value = date-time-value value =/ date-value ; **** SORT-STRING **** param = text-param ; Only text parameters allowed value = text-value ; **** SOUND **** param = snd-inline-param / snd-refer-param / pid-param value = snd-line-value ; Value MUST match value type value =/ snd-refer-value ; Value MUST match value type snd-inline-value = binary-value CRLF ; Value MUST be "b" encoded audio content snd-inline-param = ("VALUE" "=" "binary") / ("ENCODING" "=" "b") / ("TYPE" "=" *SAFE-CHAR) ; Value MUST be an IANA registered audio type snd-refer-value = uri ; URI MUST refer to audio content of given type snd-refer-param = ("VALUE" "=" "uri") / ("TYPE" "=" word) ; Value MUST be an IANA registered audio type ; **** UID **** param = "" ; No parameters allowed value = uri ; **** URL **** param = pid-param value = uri ; **** VERSION **** ;This type MUST be included in a vCard object. param = "" ; No parameters allowed value = text-value ; Value MUST be "4.0" ; **** CLASS **** param = "" ; No parameters allowed value = "PUBLIC" / "PRIVATE" / "CONFIDENTIAL" / iana-token / x-name ; Value are case insensitive ; **** KEY **** param = key-txt-param / key-bin-param / pid-param value = text-value value =/ binary-value key-txt-param = "TYPE" "=" keytype key-bin-param = ("TYPE" "=" keytype) / ("ENCODING" "=" "b") ; Value MUST be a "b" encoded key or certificate keytype = param-value ; Type MUST be a media type as defined in RFC 4288 ; **** X- **** non-standard type param = text-param / (x-name "=" param-value) ; Only text or non-standard parameters allowed value = text-value ;******************************************* ; vCard Commonly Used Parameter Definition ;******************************************* text-param = ("VALUE" "=" "ptext") / ("LANGUAGE" "=" langval) / (x-name "=" param-value) langval = <a language string as defined in [RFC4646]> pref-param = "PREF" pid-param = ("PID" "=" 1*DIGIT) img-inline-value = binary-value ;Value MUST be "b" encoded image content img-inline-param img-inline-param = ("VALUE" "=" "binary") / ("ENCODING" "=" "b") / ("TYPE" "=" param-value) ;TYPE value MUST be an image media type as defined in RFC 4288 img-refer-value = uri ;URI MUST refer to image content of given type img-refer-param = ("VALUE" "=" "uri") / ("TYPE" "=" param-value) ;TYPE value MUST be an image media type as defined in RFC 4288 adr-value = 0*6(text-value ";") text-value ; PO Box, Extended Address, Street, Locality, Region, Postal ; Code, Country Name ;******************************************* ; vCard Type Value Definition ;******************************************* text-value-list = 1*text-value *("," 1*text-value) text-value = *(SAFE-CHAR / ":" / DQUOTE / ESCAPED-CHAR) ESCAPED-CHAR = "\\" / "\;" / "\," / "\n" / "\N" ; \\ encodes \, \n or \N encodes newline ; \; encodes ;, \, encodes , binary-value = <A "b" encoded text value as defined in [RFC2047]> date-value = <A single date value as defined in [RFC2425]> time-value = <A single time value as defined in [RFC2425]> date-time-value = <A single date-time value as defined in [RFC2425]> float-value = <A single float value as defined in [RFC2425]> phone-number-value = phone-prefix 1*(SP 1*DIGIT) [phone-ext] phone-prefix = "+" 1*DIGIT / "(" 1*DIGIT ")" phone-ext = "ext." 1*DIGIT uri-value = <A uri value as defined in [RFC2425]> utc-offset-value = ("+" / "-") time-hour ":" time-minute time-hour = 2DIGIT ;00-23 time-minute = 2DIGIT ;00-59

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

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

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). vCards can carry cryptographic keys or certificates, as described in . specifies a desired security classification policy for a particular vCard. That policy is not enforced in any way. The vCard objects have no inherent authentication or privacy, but can easily be carried by any security mechanism that transfers MIME objects with authentication or privacy. In cases where threats of "spoofed" vCard information is a concern, the vCard SHOULD BE transported using one of these secure mechanisms. The information in a vCard may become out of date. In cases where the vitality of data is important to an originator of a vCard, the "URL" type described in SHOULD BE specified. In addition, the "REV" type described in section can be specified to indicate the last time that the vCard data was updated.

This section defines the process for registering new or modified vCard elements (i.e. properties, parameters, value data types, and values) with IANA.

The IETF will create a mailing list, vcard@ietf.org, 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 designated expert who will monitor the vcard@ietf.org 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 Standard Tracks RFC. The registration procedure begins when a completed registration template, defined in the sections below, is sent to vcard@ietf.org and iana@iana.org. 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 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.

The vendor namespace is used for vCard elements associated with commercially available products. "Vendor" or "producer" are construed as equivalent and very broadly in this context. A registration may be 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 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 the vendor namespace is not required, using the vcard@ietf.org mailing list for review is strongly encouraged to improve the quality of those specifications. Registrations in the vendor namespace may be submitted directly to the IANA.

A group is defined by completing the following template. The name of the group. The purpose of the group. Give a short but clear description. Any special notes about the group, how it is to be used, etc. One or more examples of instances of the value type needs to be specified.

A property is defined by completing the following template. The name of the property. The purpose of the property. Give a short but clear description. Any of the valid value types for the property value needs to be specified. The default value type also needs to be specified. Any of the valid property parameters for the property MUST be specified. Any special notes about the property, how it is to be used, etc. The ABNF for the property definition needs to be specified. One or more examples of instances of the property needs to be specified.

A parameter is defined by completing the following template. The name of the parameter. The purpose of the parameter. Give a short but clear description. Any special notes about the parameter, how it is to be used, etc. The ABNF for the parameter definition needs to be specified. One or more examples of instances of the parameter needs to be specified.

A value data type is defined by completing the following template. The name of the value type. The purpose of the value type. Give a short but clear description. Any special notes about the value type, how it is to be used, etc. The ABNF for the value type definition needs to be specified. One or more examples of instances of the value type needs to be specified.

A value is defined by completing the following template. The value literal. The purpose of the value. Give a short but clear description. The vCard properties and/or parameters that can take this value needs to be specified. One or more examples of instances of the value needs to be specified. The following is a fictitious example of a registration of a vCard value: TOP-SECRET This value is used to specify the access classification of top-secret vCards. This value can be used with the "CLASS" property. The following is an example of this value used with the "CLASS" property:

CLASS:TOP-SECRET

The IANA is requested to create and maintain the following registries for vCard elements with pointers to appropriate reference documents.

The following table is to be used to initialize the groups registry. Goup Description Status Reference WORK Properties related to an individual's work place. Current RFCXXXX HOME Properties related to an individual's home. Current RFCXXXX

The following table is to be used to initialize the properties registry. Property Status Reference SOURCE Current RFCXXXX, NAME Current RFCXXXX, KIND Current RFCXXXX, FN Current RFCXXXX, N Current RFCXXXX, NICKNAME Current RFCXXXX, PHOTO Current RFCXXXX, BDAY Current RFCXXXX, DDAY Current RFCXXXX, BIRTH Current RFCXXXX, DEATH Current RFCXXXX, GENDER Current RFCXXXX, ADR Current RFCXXXX, LABEL Current RFCXXXX, TEL Current RFCXXXX, EMAIL Current RFCXXXX, IMPP Current RFCXXXX, LANG Current RFCXXXX, TZ Current RFCXXXX, GEO Current RFCXXXX, TITLE Current RFCXXXX, ROLE Current RFCXXXX, LOGO Current RFCXXXX, ORG Current RFCXXXX, MEMBER Current RFCXXXX, RELATED Current RFCXXXX, CATEGORIES Current RFCXXXX, NOTE Current RFCXXXX, PRODID Current RFCXXXX, REV Current RFCXXXX, SORT-STRING Current RFCXXXX, SOUND Current RFCXXXX, UID Current RFCXXXX, URL Current RFCXXXX, VERSION Current RFCXXXX, CLASS Current RFCXXXX, KEY Current RFCXXXX, FBURL Current RFCXXXX, CALADRURI Current RFCXXXX, CALURI Current RFCXXXX,

The following table is to be used to initialize the parameters registry. Parameter Status Reference LANGUAGE Current RFCXXXX, ENCODING Current RFCXXXX, VALUE Current RFCXXXX, PID Current RFCXXXX, TYPE Current RFCXXXX,

The following table is to be used to initialize the parameters registry. Value Data Type Status Reference BINARY Current RFCXXXX, BOOLEAN Current RFCXXXX, DATE Current RFCXXXX, TIME Current RFCXXXX, DATE-TIME Current RFCXXXX, FLOAT Current RFCXXXX, INTEGER Current RFCXXXX, TEXT Current RFCXXXX, URI Current RFCXXXX,

Separate tables will be used for property and parameter values. The following table is to be used to initialize the property values registry. Property Value Status Reference BEGIN VCARD Current RFCXXXX, END VCARD Current RFCXXXX, KIND individual Current RFCXXXX, KIND group Current RFCXXXX, KIND org Current RFCXXXX, KIND location Current RFCXXXX, GENDER M Current RFCXXXX, GENDER F Current RFCXXXX, CLASS PUBLIC Current RFCXXXX, CLASS PRIVATE Current RFCXXXX, CLASS CONFIDENTIAL Current RFCXXXX, The following table is to be used to initialize the parameter values registry. Property Parameter Value Status Reference TEL TYPE text Current RFCXXXX, TEL TYPE voice Current RFCXXXX, TEL TYPE fax Current RFCXXXX, TEL TYPE cell Current RFCXXXX, TEL TYPE video Current RFCXXXX, TEL TYPE pager Current RFCXXXX, RELATED TYPE parent Current RFCXXXX, RELATED TYPE child Current RFCXXXX, RELATED TYPE sibling Current RFCXXXX, RELATED TYPE manager Current RFCXXXX, RELATED TYPE assistant Current RFCXXXX, RELATED TYPE agent Current RFCXXXX,

The authors would like to thank Frank Dawson and Tim Howes, the original authors of and , as well as the following individuals who have participated in the drafting, review and discussion of this memo: Marc Blanchet, Stephane Bortzmeyer, Dan Brickley, Chris Bryant, Dany Cauchie, Darryl Champagne, Cyrus Daboo, Lisa Dusseault, Javier Godoy, Helge Hess, Alexander Mayrhofer, Chris Newman, Mark Paterson, Julian Reschke, Peter K. Sheerin, Anil Srivastava, and Kurt Zeilenga.

&iso86011988; &ccitte1631988; &ccittx1211988; &ccittx5201988; &ccittx5211988; &rfc2425; &rfc2426; &rfc2046; &rfc2047; &rfc2119; &rfc2616; &rfc2739; &rfc2822; &rfc2978; &rfc3629; &rfc3966; &rfc3986; &rfc4122; &rfc4288; &rfc4646; &rfc4770; &rfc5234; The International Organization for Standardization Internet Mail Consortium The International Organization for Standardization National Imagery and Mapping Agency &rfc3406;

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

and have been merged. Initially was intended to be extensible but only 2426 ever extended it. vCard is now not only a MIME type but a stand-alone format. A proper MIME type registration form has been included. UTF-8 is now the default character set. New vCard elements can be registered from IANA.

The group construct (i.e. GROUP.PROPERTY:...) no longer exists. The CONTEXT and CHARSET parameters are no more. The MAILER property is no more. The "intl", "dom", "postal", and "parcel" TYPE parameter values for the ADR and LABEL properties have been removed. Inline vCards (such as the value of the AGENT property) are no longer supported. In the N property, additional names are now subsumed into the given names list.

The KIND, GENDER, LANG, DDAY, BIRTH, and DEATH properties have been added. , which defines the FBURL, CALADRURI, CAPURI, and CALURI properties, has been merged in. , which defines the IMPP property, has been merged in. The "work", "home", and "uri" TYPE parameter values for the EMAIL property have been added.

Synchronization is addressed in . The N property is no longer mandatory. The value of TEL is now a URI. The AGENT property was replaced with a type of RELATED.

Added "location" value for KIND property. Some fixes to ABNF. Moved "pref" from being a TYPE value to a parameter in its own right. Removed the "work" and "home" TYPE values. Reintroduced the group construct. Assigned meaning to WORK and HOME groups. Restricted the TEL TYPE parameter value set. In N property, removed additional names, and replaced with multiple given names. Removed TYPE parameter from EMAIL and IMPP properties. Replaced AGENT with a type of RELATED. Use example.org domain in URL example. Created initial IANA table of values. Defined meaning of PUBLIC, PRIVATE, CONFIDENTIAL.

Various changes to the synchronization mechanisms. Allowed truncated format for dated. See issue #236.

Removed useless text in IMPP description. Added CalDAV-SCHED example to CALADRURI. Removed CAPURI property. Dashes in dates and colons in times are now mandatory. Allow for dates such as 2008 and 2008-05 and times such as 07 and 07:54. Removed inline vCard value. Made AGENT only accept URI references instead of inline vCards. Added the MEMBER property. Renamed the UID parameter to PID. Changed the value type of the PID parameter to "a small integer." Changed the presence of UID and PID when synchronization is to be used from MUST to SHOULD. Added the RELATED () property. Fixed many ABNF typos (issue #252). Changed formatting of ABNF comments to make them easier to read (issue #226).

Merged in. Converted all foobar.com, abc.com, etc. to example.com. Fixed bugs in ABNF. Made explicit that coordinates in the GEO property are expressed in the WGS 84 reference system. Clarified folding issues with multi-byte characters. Made the value of TEL a URI. Added the UID parameter. Made the UID property's value type a URI. Added . Created IANA process for registering new parameters, value types, and properties. Created the initial IANA registries. Created vendor namespace based on text from RFC 4288.

Name change because draft has been accepted as WG item. Otherwise, same as draft-resnick-vcarddav-vcardrev-01. Removed reference to RFC 2234. Fixed errata from http://www.rfc-editor.org/errata_search.php?rfc=2426. Removed passage referring to RFC 2425 profiles. Renamed from "Telecommunications Adressing Properties" to "Communications Properties. Added and . Added reference to . Removed the group construct. Made the N property no longer mandatory. Added the KIND property. Clarified meaning of TYPE parameter value for PHOTO, LOGO, KEY, and SOUND. Removed the CONTEXT parameter. Removed the MAILER property. Made reference to informative. Removed "intl", "dom", "postal", and "parcel" TYPE parameter values for the ADR and LABEL properties. Clarified meaning of "extended address" ADR field. Mentioned as another method of generating PRODID values. Updated obsolete references. Allowed BDAY and DDAY value types to be text values for fuzzy dates. Removed the CHARSET property. Now the encoding is always UTF-8, except when overridden by the Content-Type (which is considered a compatibility feature).