vCard

vCard
Filename extension	.vcf, .v card
Internet media type	text/vcard
Type code	vCrd
Uniform Type Identifier (UTI)	public.vcard
Developed by	Created by Versit Consortium, all rights transferred in 1996 to Internet Mail Consortium, all rights transferred in 2004 to CalConnect
Type of format	Electronic business card

vCard, also known as VCF (Virtual Contact File), is a file format standard for electronic business cards. vCards are often attached to e-mail messages, but can be exchanged in other ways, such as Multimedia Messaging Service (MMS), on the World Wide Web, instant messaging or through QR code. They can contain name and address information, telephone numbers, e-mail addresses, URLs, logos, photographs, and audio clips.[1]

vCard is used as data interchange format in personal digital assistants (PDAs), personal information managers (PIMs) and customer relationship management (CRMs). To accomplish these data interchange applications, other "vCard variants" have been used and proposed as "variant standards", each for its specific niche: XML representation, JSON representation, or web pages.

History

The standard Internet media type (MIME type) for a vCard has varied with each version of the specification:[2]

In the Versit vCard 2.1 specification, the following MIME types were specified, with the note that "the vCard has not been registered as a MIME type with the IANA."[3]:

text/plain

text/x-vcard

multipart/related

application/directory

In 1998, RFC 2425 specified the following types for individual vCards:

text/directory

text/directory; charset="iso-8859-1"; profile="vCard"

multipart/related

Also in 1998, the vCard 3.0 specification, RFC 2426 specified the format for vCards in directories:

text/directory

In 2011 vCard 4.0, as defined in RFC 6350, noted that IANA had marked the following as deprecated:[2]

text/directory

RFC 6350 also noted that all of the following media types should all be considered deprecated, in favor of text/vcard:

text/directory; profile=vCard

text/directory

text/x-vcard

The Internet media type text/vcard was used incorrectly in some SyncML documents to refer to vCard 3.0, and the example was followed in various implementations.

In VCF5 - Open Federated Microformating Project vCard 5.0 mime typals specification, the following MIME types were specified, with the note that "the vCard has not been registered as a MIME types

text/json+application+vcard - *.json.vcf

text/xml+application+vcard - *.xml.vcf

text/serial+application+vcard - *.serial.vcf

text/php+application+vcard - *.php.vcf

text/text+application+vcard - *.txt.vcf

Example of vCard files

The following is an example of a vCard file containing information for one person:

vCard 2.1

BEGIN:VCARD
VERSION:2.1
N:Gump;Forrest;;Mr.
FN:Forrest Gump
ORG:Bubba Gump Shrimp Co.
TITLE:Shrimp Man
PHOTO;GIF:http://www.example.com/dir_photos/my_photo.gif
TEL;WORK;VOICE:(111) 555-1212
TEL;HOME;VOICE:(404) 555-1212
ADR;WORK;PREF:;;100 Waters Edge;Baytown;LA;30314;United States of America
LABEL;WORK;PREF;ENCODING=QUOTED-PRINTABLE;CHARSET=UTF-8:100 Waters Edge=0D=
 =0ABaytown\, LA 30314=0D=0AUnited States of America
ADR;HOME:;;42 Plantation St.;Baytown;LA;30314;United States of America
LABEL;HOME;ENCODING=QUOTED-PRINTABLE;CHARSET=UTF-8:42 Plantation St.=0D=0A=
 Baytown, LA 30314=0D=0AUnited States of America
EMAIL:forrestgump@example.com
REV:20080424T195243Z
END:VCARD

vCard 3.0

BEGIN:VCARD
VERSION:3.0
N:Gump;Forrest;;Mr.;
FN:Forrest Gump
ORG:Bubba Gump Shrimp Co.
TITLE:Shrimp Man
PHOTO;VALUE=URI;TYPE=GIF:http://www.example.com/dir_photos/my_photo.gif
TEL;TYPE=WORK,VOICE:(111) 555-1212
TEL;TYPE=HOME,VOICE:(404) 555-1212
ADR;TYPE=WORK,PREF:;;100 Waters Edge;Baytown;LA;30314;United States of America
LABEL;TYPE=WORK,PREF:100 Waters Edge\nBaytown\, LA 30314\nUnited States of America
ADR;TYPE=HOME:;;42 Plantation St.;Baytown;LA;30314;United States of America
LABEL;TYPE=HOME:42 Plantation St.\nBaytown\, LA 30314\nUnited States of America
EMAIL:forrestgump@example.com
REV:2008-04-24T19:52:43Z
END:VCARD

vCard 4.0

The latest standard, which is built upon the RFC 6350 standard.

BEGIN:VCARD
VERSION:4.0
N:Gump;Forrest;;Mr.;
FN:Forrest Gump
ORG:Bubba Gump Shrimp Co.
TITLE:Shrimp Man
PHOTO;MEDIATYPE=image/gif:http://www.example.com/dir_photos/my_photo.gif
TEL;TYPE=work,voice;VALUE=uri:tel:+1-111-555-1212
TEL;TYPE=home,voice;VALUE=uri:tel:+1-404-555-1212
ADR;TYPE=WORK;PREF=1;LABEL="100 Waters Edge\nBaytown\, LA 30314\nUnited States of America":;;100 Waters Edge;Baytown;LA;30314;United States of America
ADR;TYPE=HOME;LABEL="42 Plantation St.\nBaytown\, LA 30314\nUnited States of America":;;42 Plantation St.;Baytown;LA;30314;United States of America
EMAIL:forrestgump@example.com
REV:20080424T195243Z
x-qq:21588891
END:VCARD

Example of vCard variants

xCard

xCard, the "vCard XML Representation" is a standard proposal of 2011, as RFC 6351. This proposal has not yet become a widely used standard.

<?xml version="1.0" encoding="UTF-8"?>
<vcards xmlns="urn:ietf:params:xml:ns:vcard-4.0">
  <vcard>
    <n>
      <surname>Gump</surname>
      <given>Forrest</given>
      <additional/>
      <prefix>Mr.</prefix>
      <suffix/>
    </n>
    <fn>
      <text>Forrest Gump</text>
    </fn>
    <org>
      <text>Bubba Gump Shrimp Co.</text>
    </org>
    <title>
      <text>Shrimp Man</text>
    </title>
    <photo>
      <parameters>
        <mediatype>
          <text>image/gif</text>
        </mediatype>
      </parameters>
      <uri>http://www.example.com/dir_photos/my_photo.gif</uri>
    </photo>
    <tel>
      <parameters>
        <type>
          <text>work</text>
          <text>voice</text>
        </type>
      </parameters>
      <uri>tel:+1-111-555-1212</uri>
    </tel>
    <tel>
      <parameters>
        <type>
          <text>home</text>
          <text>voice</text>
        </type>
      </parameters>
      <uri>tel:+1-404-555-1212</uri>
    </tel>
    <adr>
      <parameters>
        <label>
          <text>100 Waters Edge
Baytown, LA 30314
United States of America</text>
        </label>
        <type>
          <text>work</text>
        </type>
        <pref>
          <integer>1</integer>
        </pref>
      </parameters>
      <pobox/>
      <ext/>
      <street>100 Waters Edge</street>
      <locality>Baytown</locality>
      <region>LA</region>
      <code>30314</code>
      <country>United States of America</country>
    </adr>
    <adr>
      <parameters>
        <label>
          <text>42 Plantation St.
Baytown, LA 30314
United States of America</text>
        </label>
        <type>
          <text>home</text>
        </type>
      </parameters>
      <pobox/>
      <ext/>
      <street>42 Plantation St.</street>
      <locality>Baytown</locality>
      <region>LA</region>
      <code>30314</code>
      <country>United States of America</country>
    </adr>
    <email>
      <text>forrestgump@example.com</text>
    </email>
    <rev>
      <timestamp>20080424T195243Z</timestamp>
    </rev>
  </vcard>
</vcards>

6996

jCard

jCard, "The JSON Format for vCard" is a standard proposal of 2014, RFC 7095. This proposal has not yet become a widely used standard. Other JSON formats (as npm's vcard-json) are in use. The RFC 7095 does not use real JSON objects, but rather uses arrays of sequence-dependent tag-value pairs (like an XML file).

["vcard",
  [
    ["version", {}, "text", "4.0"],
    ["n", {}, "text", ["Gump", "Forrest", "", "Mr.", ""]],
    ["fn", {}, "text", "Forrest Gump"],
    ["org", {}, "text", "Bubba Gump Shrimp Co."],
    ["title", {} ,"text", "Shrimp Man"],
    ["photo", {"mediatype":"image/gif"}, "uri", "http://www.example.com/dir_photos/my_photo.gif"],
    ["tel", {"type":["work", "voice"]}, "uri", "tel:+1-111-555-1212"],
    ["tel", {"type":["home", "voice"]}, "uri", "tel:+1-404-555-1212"],
    ["adr",
      {"label":"100 Waters Edge\nBaytown, LA 30314\nUnited States of America", "type":"work", "pref":"1"},
      "text",
      ["", "", "100 Waters Edge", "Baytown", "LA", "50505", "United States of America"]
    ],
    ["adr",
      {"label":"42 Plantation St.\nBaytown, LA 30314\nUnited States of America", "type":"home"},
      "text",
      ["", "", "42 Plantation St.", "Baytown", "LA", "30314", "United States of America"]
    ],
    ["email", {}, "text", "forrestgump@example.com"],
    ["rev", {}, "timestamp", "2008-04-24T19:52:43Z"]
  ]
]

Semantic content

vCard information is common in web pages: the "free text" content is human-readable but not machine-readable. As technologies evolve, the "free text" (HTML) was adapting to be also machine-readable.

hCard is a microformat that allows a vCard to be embedded inside an HTML page. It makes use of CSS class names to identify each vCard property. Normal HTML markup and CSS styling can be used alongside the hCard class names without affecting the webpage's ability to be parsed by a hCard parser. h-card is the microformats2 update to hCard.[4][5]
RDFa with the vCard Ontology can be used in HTML and various XML-family languages e.g. SVG, MathML.
Most of vCard properties are mapped using e.g. Schema.org vocabulary (see Person and Organization classes).

Below is an example of first generation hCard.

<html>
  <head>
    <link rel="profile" href="http://microformats.org/profile/hcard" />
  </head>
  <body>
    <div class="vcard">
      <img class="photo" src="http://www.example.com/dir_photos/my_photo.gif" align="left" />
      <h1 class="fn">Forrest Gump</h1>
      <div class="email">
        Email: <a class="value" href="mailto:forrestgump@example.com">forrestgump@example.com</a>
      </div>
      <div class="n">
        Prefix: <span class="honorific-prefix">Mr.</span><br>
        First Name: <span class="given-name">Forrest</span><br>
        Last Name: <span class="family-name">Gump</span>
      </div>

      <div class="label" style="display:none">
        <span class="type">home</span>
        42 Plantation St.<br>Baytown, LA 30314<br>United States of America
      </div>
      <div class="adr">
        <span class="type">Home</span> Address:<br>
        <span class="street-address">42 Plantation St.</span><br>
        <span class="locality">Baytown</span>, <span class="region">LA</span>
        <span class="postal-code">30314</span><br>
        <span class="country-name">United States of America</span>
      </div>
      <div class="tel">
         <abbr class="type" title="voice"></abbr>
         <span class="type">Home</span> Phone: <span class="value">(111) 555-1212</span>
      </div>

      <div>
        Organization: <span class="org">Bubba Gump Shrimp Co.</span><br>
        Title: <span class="title">Shrimp Man</span>
      </div>

      <div class="label" style="display:none">
        <span class="type">work</span>
        100 Waters Edge<br>Baytown, LA 30314<br>United States of America
      </div>
      <div class="adr">
        <span class="type">Work</span> Address (<span class="type">pref</span>erred):<br>
        <span class="street-address">100 Waters Edge</span><br>
        <span class="locality">Baytown</span>, <span class="region">LA</span>
        <span class="postal-code">30314</span><br>
        <span class="country-name">United States of America</span>
      </div>
      <div class="tel">
         <abbr class="type" title="voice"></abbr>
         <span class="type">Work</span> Phone: <span class="value">(404) 555-1212</span>
      </div>

      <em>vCard last updated:</em>
      <time class="rev" datetime="2008-04-24T19:52:43Z">April 24, 2008 at 7:52 PM GMT</time>
    </div>
  </body>
</html>

Below is an example of RDFa in HTML5 using the vCard Ontology:

<html lang="en">
  <head>
    <meta charset="utf-8" />
  </head>
  <body vocab="http://www.w3.org/2006/vcard/ns#">
    <article resource="#Forest-Gump" typeof="Individual">
      <h1 property="fn">Forrest Gump</h1>

      <img property="hasPhoto" src="http://example.org/media/photo.jpg" />

      <div>
        Email: <a property="hasEmail" href="mailto:forrestgump@example.com">forrestgump@example.com</a>
      </div>

      <div>
        Prefix: <span property="honorific-prefix">Mr.</span><br />
        First Name: <span property="given-name">Forrest</span><br />
        Last Name: <span property="family-name">Gump</span>
      </div>

      <div property="hasAddress" typeof="Home">
        Home Address:<br />
        <span property="street-address">42 Plantation St.</span><br />
        <span property="locality">Baytown</span>, <span property="region">LA</span>
        <span property="postal-code" lang="">30314</span><br />
        <span property="country-name">United States of America</span>
      </div>

      <div property="hasTelephone" typeof="Voice Home">
         Voice/Home Phone: <a property="hasValue" href="tel:+11115551212">(111) 555-1212</a>
      </div>
    </article>
  </body>
</html>

Properties

vCard defines the following property types.

All vCards begin with BEGIN:VCARD and end with END:VCARD. All vCards must contain the VERSION property, which specifies the vCard version. VERSION must come immediately after BEGIN, except in the vCard 2.1 standard, which allows it to be anywhere in the vCard. Otherwise, properties can be defined in any order.

Name	Property presence			Description	Example
Name	v. 2.1	v. 3.0	v. 4.0	Description	Example
`ADR`	Optional	Optional	Optional	A structured representation of the physical delivery address for the vCard object.	`ADR;TYPE=home:;;123 Main St.;Springfield;IL;12345;USA`
`AGENT`	Optional	Optional	Undefined	Information about another person who will act on behalf of the vCard object. Typically this would be an area administrator, assistant, or secretary for the individual. Can be either a URL or an embedded vCard.	`AGENT:http://mi6.gov.uk/007`
`ANNIVERSARY`	Undefined	Undefined	Optional	Defines the person's anniversary.	`ANNIVERSARY:19901021`
`BDAY`	Optional	Optional	Optional	Date of birth of the individual associated with the vCard.	`BDAY:19700310`
`BEGIN`	Required	Required	Required	All vCards must start with this property.	`BEGIN:VCARD`
`CALADRURI`	Undefined	Undefined	Optional	A URL to use for sending a scheduling request to the person's calendar.	`CALADRURI:http://example.com/calendar/jdoe`
`CALURI`	Undefined	Undefined	Optional	A URL to the person's calendar.	`CALURI:http://example.com/calendar/jdoe`
`CATEGORIES`	Optional	Optional	Optional	A list of "tags" that can be used to describe the object represented by this vCard.	`CATEGORIES:swimmer,biker`
`CLASS`	Undefined	Optional	Undefined	Describes the sensitivity of the information in the vCard.	`CLASS:public`
`CLIENTPIDMAP`	Undefined	Undefined	Optional	Used for synchronizing different revisions of the same vCard.	`CLIENTPIDMAP:1;urn:uuid:3df403f4-5924-4bb7-b077-3c711d9eb34b`
`EMAIL`	Optional	Optional	Optional	The address for electronic mail communication with the vCard object.	`EMAIL:johndoe@hotmail.com`
`END`	Required	Required	Required	All vCards must end with this property.	`END:VCARD`
`FBURL`	Undefined	Undefined	Optional	Defines a URL that shows when the person is "free" or "busy" on their calendar.	`FBURL:http://example.com/fb/jdoe`
`FN`	Optional	Required	Required	The formatted name string associated with the vCard object.	`FN:Dr. John Doe`
`GENDER`	Undefined	Undefined	Optional	Defines the person's gender.	`GENDER:F`
`GEO`	Optional	Optional	Optional	Specifies a latitude and longitude.	2.1, 3.0: `GEO:39.95;-75.1667` 4.0: `GEO:geo:39.95,-75.1667`
`IMPP`	Undefined	Maybe	Optional	Defines an instant messenger handle. This property was introduced in a separate RFC when the latest vCard version was 3.0. Therefore, 3.0 vCards might use this property without otherwise declaring it.	`IMPP:aim:johndoe@aol.com`
`KEY`	Optional	Optional	Optional	The public encryption key associated with the vCard object. It may point to an external URL, may be plain text, or may be embedded in the vCard as a Base64 encoded block of text.	2.1: `KEY;PGP:http://example.com/key.pgp` 2.1: `KEY;PGP;ENCODING=BASE64:[base64-data]` 3.0: `KEY;TYPE=PGP:http://example.com/key.pgp` 3.0: `KEY;TYPE=PGP;ENCODING=b:[base64-data]` 4.0: `KEY;MEDIATYPE=application/pgp-keys:http://example.com/key.pgp` 4.0: `KEY:data:application/pgp-keys;base64,[base64-data]`
`KIND`	Undefined	Undefined	Optional	Defines the type of entity that this vCard represents: 'application', 'individual', 'group', 'location' or 'organization'; 'x-*' values may be used for experimental purposes.[6][7]	`KIND:individual`
`LABEL`	Optional	Optional	Incorporated without	Represents the actual text that should be put on the mailing label when delivering a physical package to the person/object associated with the vCard (related to the `ADR` property). Not supported in version 4.0. Instead, this information is stored in the `LABEL` parameter of the `ADR` property. Example: `ADR;TYPE=home;LABEL="123 Main St\nNew York, NY 12345":;;123 Main St;New York;NY;12345;USA`	`LABEL;TYPE=HOME:123 Main St.\nSpringfield, IL 12345\nUSA`
`LANG`	Undefined	Undefined	Optional	Defines a language that the person speaks.	`LANG:fr-CA`
`LOGO`	Optional	Optional	Optional	An image or graphic of the logo of the organization that is associated with the individual to which the vCard belongs. It may point to an external URL or may be embedded in the vCard as a Base64 encoded block of text.	2.1: `LOGO;PNG:http://example.com/logo.png` 2.1: `LOGO;PNG;ENCODING=BASE64:[base64-data]` 3.0: `LOGO;TYPE=PNG:http://example.com/logo.png` 3.0: `LOGO;TYPE=PNG;ENCODING=b:[base64-data]` 4.0: `LOGO;MEDIATYPE=image/png:http://example.com/logo.png` 4.0: `LOGO:data:image/png;base64,[base64-data]`
`MAILER`	Optional	Optional	Undefined	Type of email program used.	`MAILER:Thunderbird`
`MEMBER`	Undefined	Undefined	Optional	Defines a member that is part of the group that this vCard represents. Acceptable values include: a "mailto:" URL containing an email address a UID which references the member's own vCard The `KIND` property must be set to "group" in order to use this property.	`MEMBER:urn:uuid:03a0e51f-d1aa-4385-8a53-e29025acd8af`
`N`	Required	Required	Optional	A structured representation of the name of the person, place or thing associated with the vCard object.	`N:Doe;John;;Dr;`
`NAME`	Undefined	Optional	Undefined	Provides a textual representation of the `SOURCE` property.
`NICKNAME`	Undefined	Optional	Optional	One or more descriptive/familiar names for the object represented by this vCard.	`NICKNAME:Jon,Johnny`
`NOTE`	Optional	Optional	Optional	Specifies supplemental information or a comment that is associated with the vCard.	`NOTE:I am proficient in Tiger-Crane Style,\nand I am more than proficient in the exquisite art of the Samurai sword.`
`ORG`	Optional	Optional	Optional	The name and optionally the unit(s) of the organization associated with the vCard object. This property is based on the X.520 Organization Name attribute and the X.520 Organization Unit attribute.	`ORG:Google;GMail Team;Spam Detection Squad`
`PHOTO`	Optional	Optional	Optional	An image or photograph of the individual associated with the vCard. It may point to an external URL or may be embedded in the vCard as a Base64 encoded block of text.	2.1: `PHOTO;JPEG:http://example.com/photo.jpg` 2.1: `PHOTO;JPEG;ENCODING=BASE64:[base64-data]` 3.0: `PHOTO;TYPE=JPEG;VALUE=URI:http://example.com/photo.jpg` 3.0: `PHOTO;TYPE=JPEG;ENCODING=b:[base64-data]` 4.0: `PHOTO;MEDIATYPE=image/jpeg:http://example.com/photo.jpg` 4.0: `PHOTO:data:image/jpeg;base64,[base64-data]`
`PRODID`	Undefined	Optional	Optional	The identifier for the product that created the vCard object.	`PRODID:-//ONLINE DIRECTORY//NONSGML Version 1//EN`
`PROFILE`	Optional	Optional	Undefined	States that the vCard is a vCard.	`PROFILE:VCARD`
`RELATED`	Undefined	Undefined	Optional	Another entity that the person is related to. Acceptable values include: a "mailto:" URL containing an email address a UID which references the person's own vCard	`RELATED;TYPE=friend:urn:uuid:03a0e51f-d1aa-4385-8a53-e29025acd8af`
`REV`	Optional	Optional	Optional	A timestamp for the last time the vCard was updated.	`REV:20121201T134211Z`
`ROLE`	Optional	Optional	Optional	The role, occupation, or business category of the vCard object within an organization.	`ROLE:Executive`
`SORT-STRING`	Undefined	Optional	Incorporated without	Defines a string that should be used when an application sorts this vCard in some way. Not supported in version 4.0. Instead, this information is stored in the `SORT-AS` parameter of the `N` and/or `ORG` properties.	`SORT-STRING:Doe`
`SOUND`	Optional	Optional	Optional	By default, if this property is not grouped with other properties it specifies the pronunciation of the `FN` property of the vCard object. It may point to an external URL or may be embedded in the vCard as a Base64 encoded block of text.	2.1: `SOUND;OGG:http://example.com/sound.ogg` 2.1: `SOUND;OGG;ENCODING=BASE64:[base64-data]` 3.0: `SOUND;TYPE=OGG:http://example.com/sound.ogg` 3.0: `SOUND;TYPE=OGG;ENCODING=b:[base64-data]` 4.0: `SOUND;MEDIATYPE=audio/ogg:http://example.com/sound.ogg` 4.0: `SOUND:data:audio/ogg;base64,[base64-data]`
`SOURCE`	Optional	Optional	Optional	A URL that can be used to get the latest version of this vCard.	`SOURCE:http://johndoe.com/vcard.vcf`
`TEL`	Optional	Optional	Optional	The canonical number string for a telephone number for telephony communication with the vCard object.	`TEL;TYPE=cell:(123) 555-5832`
`TITLE`	Optional	Optional	Optional	Specifies the job title, functional position or function of the individual associated with the vCard object within an organization.	`TITLE:V.P. Research and Development`
`TZ`	Optional	Optional	Optional	The time zone of the vCard object.	2.1, 3.0: `TZ:-0500` 4.0: `TZ:America/New_York`
`UID`	Optional	Optional	Optional	Specifies a value that represents a persistent, globally unique identifier associated with the object.	`UID:urn:uuid:da418720-3754-4631-a169-db89a02b831b`
`URL`	Optional	Optional	Optional	A URL pointing to a website that represents the person in some way.	`URL:http://www.johndoe.com`
`VERSION`	Required	Required	Required	The version of the vCard specification. In version 4.0, this must come right after the `BEGIN` property.	`VERSION:3.0`
`XML`	Undefined	Undefined	Optional	Any XML data that is attached to the vCard. This is used if the vCard was encoded in XML (xCard standard) and the XML document contained elements which are not part of the xCard standard.	`XML:<b>Not an xCard XML element</b>`

A handful of separate specifications define additional vCard properties.

Name	Specification	Description	Example
`BIRTHPLACE`	RFC 6474	The location of the individual's birth.	`BIRTHPLACE;VALUE=text:Maida Vale\, London\, England`
`DEATHDATE`	RFC 6474	The individual's time of death.	`DEATHDATE:19540607`
`DEATHPLACE`	RFC 6474	The location of the individual death.	`DEATHPLACE;VALUE=uri:geo:53.328,-2.229409`
`EXPERTISE`	RFC 6715	A professional subject area that the person has knowledge of.	`EXPERTISE;LEVEL=expert:Computer Science`
`HOBBY`	RFC 6715	A recreational activity that the person actively engages in.	`HOBBY;LEVEL=high:knitting`
`IMPP`	RFC 4770	Defines an instant messenger handle. This was added to the official vCard specification in version 4.0.	`IMPP:aim:johndoe@aol.com`
`INTEREST`	RFC 6715	A recreational activity that the person is interested in, but does not necessarily take part in.	`INTEREST;LEVEL=high:baseball`
`ORG-DIRECTORY`	RFC 6715	A URI representing the person's work place, which can be used to look up information on the person's co-workers.	`ORG-DIRECTORY:http://www.company.com/employees`

vCard extensions

vCard supports private extensions, with an "X-" prefix, a number of which are in common usage.

Some of these include:

Extension	Used as	Data	Semantic
Extensions supported by several different programs.
`X-ABUID`	property	string	Apple Address Book UUID for that entry
`X-ANNIVERSARY`	property	YYYY-MM-DD	arbitrary anniversary (in addition to `BDAY`, birthday)
`X-ASSISTANT`	property	string	assistant name (instead of `AGENT`)
`X-MANAGER`	property	string	manager name
`X-SPOUSE`	property	string	spouse name
`X-GENDER`	property	string	value `Male` or `Female`
`X-WAB-GENDER`	property	`1`/`2`	value `1` for female or `2` for male
`X-AIM`	property	string	Instant Messaging (IM) contact information; `TYPE` parameter as for `TEL`
`X-ICQ`	property	string
`X-GOOGLE-TALK`, `X-GTALK`	property	string
`X-JABBER`	property	string
`X-MSN`	property	string
`X-YAHOO`	property	string
`X-TWITTER`	property	string
`X-SKYPE`, `X-SKYPE-USERNAME`	property	string
`X-GADUGADU`	property	string
`X-GROUPWISE`	property	string
`X-MS-IMADDRESS`	property	string	IM address in VCF attachment from Outlook (right click Contact, Send Full Contact, Internet Format.)
`X-MS-CARDPICTURE`	property	string	Works as `PHOTO` or `LOGO`. Contains an image of the Card in Outlook.
`X-MS-OL-DESIGN`	property	string	Contains XML used by Outlook describing the layout of the information presented as a business card.[8]
`X-PHONETIC-FIRST-NAME`, `X-PHONETIC-LAST-NAME`	property	string	alternative spellings, for assisting with the pronunciation of unfamiliar names
Introduced and used by Mozilla; used by Evolution (software)
`X-MOZILLA-HTML`	property	`TRUE`/`FALSE`	mail recipient prefers HTML-formatted email
`X-MOZILLA-PROPERTY`	property	string	Thunderbird specific settings
Introduced and used by Evolution (software)
`X-EVOLUTION-ANNIVERSARY`	property	YYYY-MM-DD	arbitrary anniversary (in addition to `BDAY`, birthday)
`X-EVOLUTION-ASSISTANT`	property	string	assistant name (instead of `Agent`)
`X-EVOLUTION-BLOG-URL`	property	string/URL	blog URL
`X-EVOLUTION-FILE-AS`	property	string	file under different name (in addition to `N`, name components; and `FN`, full name)
`X-EVOLUTION-LIST`	property	`TRUE`/`FALSE`	entry defines a mailing list (e.g. X-EVOLUTION-LIST:TRUE)
`X-EVOLUTION-LIST-SHOW_ADDRESSES`	property	`TRUE`/`FALSE`	sets whether individual addresses will appear in e-mails sent using a mailing list (e.g. X-EVOLUTION-LIST-SHOW_ADDRESSES:FALSE)
`X-EVOLUTION-MANAGER`	property	string	manager name
`X-EVOLUTION-SPOUSE`	property	string	spouse name
`X-EVOLUTION-VIDEO-URL`	property	string/URL	video chat address
`X-EVOLUTION-CALLBACK`	`TEL TYPE` parameter value	-	callback phone number
`X-EVOLUTION-RADIO`	`TEL TYPE` parameter value	-	radio contact information
`X-EVOLUTION-TELEX`	`TEL TYPE` parameter value	-	Telex contact information
`X-EVOLUTION-TTYTDD`	`TEL TYPE` parameter value	-	TTY TDD contact information
Introduced and used by Kontact and KAddressBook
`X-KADDRESSBOOK-BlogFeed`	property	string/URL	blog URL
`X-KADDRESSBOOK-X-Anniversary`	property	ISO date	arbitrary anniversary, in addition to `BDAY` = birthday
`X-KADDRESSBOOK-X-AssistantsName`	property	string	assistant name (instead of `Agent`)
`X-KADDRESSBOOK-X-IMAddress`	property	string	im address
`X-KADDRESSBOOK-X-ManagersName`	property	string	manager name
`X-KADDRESSBOOK-X-Office`	property	string	office description
`X-KADDRESSBOOK-X-Profession`	property	string	profession
`X-KADDRESSBOOK-X-SpouseName`	property	string	spouse name
`X-KADDRESSBOOK-OPENPGPFP`	property	string	OpenPGP fingerprint (RFC 6350 standardised KEY as a replacement for this)
Introduced and used by WebMoney
`X-WEBMONEY-ID`	property	long	Unique 12-Digit number, which is the address of a member within the WebMoney system

References

"How to use QR codes on Business cards (Vcard or V-card)". Retrieved 19 January 2020.
RFC 6350, section 10.1 "Media Type Registration"
"vCard: The Electronic Business Card (Version 2.1)" (PDF).
"h-card". 2015-02-18. Retrieved 2015-04-05.
"microformats 2". 2015-03-13. Retrieved 2015-04-05.
"vCard Format Specification: 6.1.4. KIND". IETF. August 2011.
"vCard KIND:application". IETF. December 2011.
Sparnaaij, Robert (2011-05-02). "meaning of X-MS-OL-DESIGN;CHARSET=utf-8:". answers.microsoft.com. Retrieved 2015-04-05.

External links

Internet mail Consortium - Personal Data Interchange
vCard: The Electronic Business Card (Version 2.1) vCard 2.1 specification (Sept-18-1996)
Representing vCard Objects in RDF - W3C ontology
RFC 2425 — A MIME Content-Type for Directory Information
RFC 2426 — vCard MIME Directory Profile
RFC 2739 — Calendar Attributes for vCard and LDAP
RFC 4122 — UUID URN namespace (could be used for UID type)
RFC 4770 — vCard Extensions for Instant Messaging
RFC 6350 — vCard Format Specification
RFC 6351 — xCard: vCard XML Representation
RFC 6473 — vCard KIND:application
RFC 6474 — vCard Format Extensions: Place of Birth, Place and Date of Death
RFC 6715 — vCard Format Extensions: Representing vCard Extensions Defined by the Open Mobile Alliance (OMA) Converged Address Book (CAB) Group
RFC 6868 — Parameter Value Encoding in iCalendar and vCard
RFC 7095 — jCard: The JSON Format for vCard
IETF vCardDAV working group
CSV to vCard contacts file converter
vCardz_i free working vcard program
DFDL schemas for vCard
VCF5 ~ Federated Open Micro-formatting Project
Excel (xls) to vCard converter

This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.

[1] "How to use QR codes on Business cards (Vcard or V-card)". Retrieved 19 January 2020.

[mediatype-2] RFC 6350, section 10.1 "Media Type Registration"

[3] "vCard: The Electronic Business Card (Version 2.1)" (PDF).

[4] "h-card". 2015-02-18. Retrieved 2015-04-05.

[5] "microformats 2". 2015-03-13. Retrieved 2015-04-05.

[6] "vCard Format Specification: 6.1.4. KIND". IETF. August 2011.

[:0-7] "vCard KIND:application". IETF. December 2011.

[8] Sparnaaij, Robert (2011-05-02). "meaning of X-MS-OL-DESIGN;CHARSET=utf-8:". answers.microsoft.com. Retrieved 2015-04-05.

vCard

History

Example of vCard files

vCard 2.1

vCard 3.0

vCard 4.0

Example of vCard variants

xCard

jCard

Semantic content

Properties

vCard extensions

See also

References

External links