linuxism

vCard 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 on the World Wide Web or instant messaging. They can contain name and address information, phone numbers, e-mail addresses, URLs,logos, photographs, and audio clips.

[edit]History

Versitcard was originally proposed in 1995 by the Versit Consortium, which consisted of Apple, AT&T Technologies (later Lucent), IBM and Siemens. In December 1996, ownership of the format was handed over to the Internet Mail Consortium, a trade association for companies with an interest in Internet e-mail.

Version 2.1 of the vCard standard is widely supported by e-mail clients. Version 3.0 of the vCard format is an IETF standards-track proposal contained in RFC 2425 and RFC 2426. Version 4.0 is defined in RFC 6350, with a new XML syntax, xCard, defined in RFC 6351. The commonly-used filename extension for vCards is vcf. In RFC 4770, vCard Extensions for Instant Messaging, a new type of entry to hold an IMPP URI is defined, which is "IMPP". This is now part of the base vCard 4.0 specification.

[edit]Media type

The standard Internet media type for a vCard (often referred to as its mime type) is:^[1]

text/vcard

As of version 4.0 specification, other media types known to have been used previously are now deprecated, including:^[1]

text/x-vcard

text/directory;profile=vCard

text/directory

[edit]Example vCard files

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

[edit]vCard 2.1

BEGIN:VCARD
VERSION:2.1
N:Gump;Forrest
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:;;100 Waters Edge;Baytown;LA;30314;United States of America
LABEL;WORK;ENCODING=QUOTED-PRINTABLE: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:42 Plantation St.=0D=0ABaytown, LA 30314=0D=0AUnited States of America
EMAIL;PREF;INTERNET:forrestgump@example.com
REV:20080424T195243Z
END:VCARD

[edit]vCard 3.0

BEGIN:VCARD
VERSION:3.0
N:Gump;Forrest
FN:Forrest Gump
ORG:Bubba Gump Shrimp Co.
TITLE:Shrimp Man
PHOTO;VALUE=URL;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:;;100 Waters Edge;Baytown;LA;30314;United States of America
LABEL;TYPE=WORK: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;TYPE=PREF,INTERNET:forrestgump@example.com
REV:2008-04-24T19:52:43Z
END:VCARD

[edit]vCard 4.0

BEGIN:VCARD
VERSION:4.0
N:Gump;Forrest;;;
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;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
END:VCARD

[edit]xCard

<?xml version="1.0" encoding="UTF-8"?>
<vcards xmlns="urn:ietf:params:xml:ns:vcard-4.0">
  <vcard>
    <n>
      <family>Gump</family>
      <given>Forrest</given>
      <prefix>Mr.</prefix>
    </n>
    <title><text>runner</text></title>
    <photo>
        <parameters>
            <mediatype>image/gif</mediatype>
        </parameters>
        <uri>images/x.jpg</uri>
    </photo>
    <tel>
      <parameters>
        <type>work</type>
        <type>voice</type>
      </parameters>
      <uri>tel:+1 650 000 000</uri>
    </tel>
    <adr>
      <parameters>
        <type>work</type>
        <label>113 Grant avenue
          SAN FRANCISCO, CA 94300
          USA
        </label>
      </parameters>
      <pobox/>
      <ext/>
      <street>113 Grant avenue</street>
      <locality>SAN FRANCISCO</locality>
      <code>94300</code>
      <country>USA</country>
    </adr>
    <email><text>forrest@gmail.com</text></email>
  </vcard>
</vcards>

[edit]hCard 1.0

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.

<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">
        <span class="type">Internet</span> Email (<span class="type">pref</span>erred):
        <a class="value" href="mailto:forrestgump@example.com">forrestgump@example.com</a>
      </div>
      <div class="n">
        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">+1-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:<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">+1-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>

[edit]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 right 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.

 = required  = supported

Name	Versions			Description	Example
	2.1	3.0	4.0
ADR				A structured representation of the physical delivery address for the vCard object.	ADR;TYPE=home:;;123 Main St.;Springfield;IL;12345;USA
AGENT				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://mi5.gov.uk/007
ANNIVERSARY				Defines the person's anniversary.	ANNIVERSARY:19901021
BDAY				Date of birth of the individual associated with the vCard.	BDAY:19700310
BEGIN				All vCards must start with this property.	BEGIN:VCARD
CALADRURI				A URL to use for sending a scheduling request to the person's calendar.	CALADRURI:http://example.com/calendar/jdoe
CALURI				A URL to the person's calendar.	CALURI:http://example.com/calendar/jdoe
CATEGORIES				A list of "tags" that can be used to describe the object represented by this vCard.	CATEGORIES:swimmer,biker
CLASS				Describes the sensitivity of the information in the vCard.	CLASS:public
CLIENTPIDMAP				Used for synchronizing different revisions of the same vCard.	CLIENTPIDMAP:1;urn:uuid:3df403f4-5924-4bb7-b077-3c711d9eb34b
EMAIL				The address for electronic mail communication with the vCard object.	EMAIL:johndoe@hotmail.com
END				All vCards must end with this property.	END:VCARD
FBURL				Defines a URL that shows when the person is "free" or "busy" on their calendar.	FBURL:http://example.com/fb/jdoe
FN				The formatted name string associated with the vCard object.	FN:Dr. John Doe
GENDER				Defines the person's sex.	GENDER:F
GEO				Specifies a latitude and longitude.	2.1, 3.0: GEO:39.95;-75.1667 4.0: GEO:geo:39.95,-75.1667
IMPP		*		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 may use this property, even though it's not part of the 3.0 specs.	IMPP:aim:johndoe@aol.com
KEY				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				Defines the type of entity that this vCard represents, such as an individual or organization.	KIND:individual
LABEL			*	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.	LABEL;TYPE=HOME:123 Main St.\nSpringfield, IL 12345\nUSA
LANG				Defines a language that the person speaks.	LANG:fr-CA
LOGO				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 aBase64 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: PHOTO;TYPE=PNG;ENCODING=B:[base64-data] 4.0: LOGO;MEDIATYPE=image/png:http://example.com/logo.png 4.0: PHOTO:https://t1.daumcdn.net/cfile/tistory/2238F14156E779461A"border: 1px solid rgb(170, 170, 170); padding: 0.2em;">MAILER				Type of email program used.	MAILER:Thunderbird
MEMBER				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				A structured representation of the name of the person, place or thing associated with the vCard object.	N:Doe;John;;Dr;
NAME				Provides a textual representation of the SOURCE property.
NICKNAME				One or more descriptive/familiar names for the object represented by this vCard.	NICKNAME:Jon,Johnny
NOTE				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				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				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: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:https://t1.daumcdn.net/cfile/tistory/215DFB3E56E7794627"border: 1px solid rgb(170, 170, 170); padding: 0.2em;">PRODID				The identifier for the product that created the vCard object.	PRODID:-//ONLINE DIRECTORY//NONSGML Version 1//EN
PROFILE				States that the vCard is a vCard.	PROFILE:VCARD
RELATED				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				A timestamp for the last time the vCard was updated.	REV:20121201T134211Z
ROLE				The role, occupation, or business category of the vCard object within an organization.	ROLE:Executive
SORT-STRING			*	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				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				A URL that can be used to get the latest version of this vCard.	SOURCE:http://johndoe.com/vcard.vcf
TEL				The canonical number string for a telephone number for telephony communication with the vCard object.	TEL;TYPE=cell:(123) 555-5832
TITLE				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				The time zone of the vCard object.	2.1, 3.0: TZ:-0500 4.0: TZ:America/New_York
UID				Specifies a value that represents a persistent, globally unique identifier associated with the object.	UID:urn:uuid:da418720-3754-4631-a169-db89a02b831b
URL				A URL pointing to a website that represents the person in some way.	URL:http://www.johndoe.com
VERSION				The version of the vCard specification. In versions 3.0 and 4.0, this must come right after theBEGIN property.	VERSION:3.0
XML				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.

[edit]vCard extensions

vCard supports private extensions, with an "X-" prefix, a number of which are in common usage^{[citation needed]}.

Some of these include:

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

[edit]See also

• CardDAV
• hCard
• FOAF (software)
• Geo URI

[edit]References

[edit]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 Member Submission 20 January 2010
• vCard implementations notes and bug reports
• vCard proposed errata
• 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
• IETF vCardDAV working group
• commercial vCard Import Export Tool / vCard Magic by pcvita software

CardDAV is an address book client/server protocol designed to allow users to access and share contact data on a server.

The CardDAV protocol was developed by the IETF and has been published as RFC 6352 in August 2011.^[1] CardDAV is based on WebDAV, which is based on HTTP, and it uses vCard for contact data.^[2]

[edit]History

This section is empty. You can help byadding to it. (April 2010)

[edit]Specification

The specification has been proposed as a standard by IETF as the RFC 6352 in August 2011 by C. Daboo from Apple Inc.

[edit]Implementations

The following products implement the server-side portion of the CardDAV protocol: .

• Apple Address Book Server.^[3][4]
• Baïkal, an open-source and lightweight CalDAV+CardDAV server based on SabreDAV API
• Radicale, a simple CalDAV+CardDAV server written in Python with no external depencencies
• CommuniGate Pro supports CardDav protocol.^[5]
• DAViCal supports CardDAV from version 0.9.9.2^[6]
• EVO Mail Server, a mail server software, supporting CardDAV
• fruux, a synchronization service, supporting CardDAV
• Meishi, a standalone, Ruby on Rails based CardDAV server^[7]
• Memotoo, a synchronization service, supporting CardDAV
• ownCloud supports CardDAV protocol since version 2.0.
• SabreDAV, a WebDAV framework for PHP, supports CardDAV since version 1.5.^[8]
• SOGo supports CardDAV access to its address books.^[9]
• Zimbra 6 allows access to its address book via CardDAV.^[10]
• GMail and Google Contacts allow access to user's address book via CardDAV.^[11]
• licobo, an online address book, supporting CardDAV^[12]

The following products implement the client-side portion of the CardDAV protocol:

• ContactSync for Android^[13]
• Apple Address Book in Mac OS X v10.6 "Snow Leopard".^[14]
• Apple iOS, starting from iOS 4.^[15]
• Atmail supports a complete CardDAV client via the Webmail interface^[16]
• Blackberry devices running QNX - Blackberry 10+ phones, Playbook OS 2.0+ tablets
• CardDavMATE, open source HTML5+Javascript CardDAV client (web application)^[17]
• CardDav-Sync for Android^[18]
• CardDAV PHP, open source PHP CardDAV Client^[19]
• Evolution - Works as WebDAV contacts. Except perhaps not currently (version 2.30, 2.31) other than https on port 443.^[20]
• Kerio Connect^[3][21]
• KDE Software Compilation 4.5 will feature CardDAV client support, due in August 2010. It will be available for use by Kaddressbook, which is part of Kontact PIM suite. It will be provided by Akonadi: a PIM server which will also make the data available to other applications.^[22]
• Thunderbird, via the SOGo Connector

[edit]See also

• Comparison of CalDAV and CardDAV implementations
• WebDAV
• CalDAV
• GroupDAV
• vCard
• SyncML

[edit]References

1. ^ CardDAV Resources, CalConnect, retrieved April 10, 2010
2. ^ CardDAV: Related Standards, CalConnect, retrieved April 11, 2010
3. ^ ^a b Implementations: CardDAV Servers, CalConnect, retrieved April 10, 2010
4. ^ Mac OS X Server: Address Book Server, Apple Inc, retrieved April 10, 2010
5. ^ CommuniGate Pro support of CardDav, retrieved April 21, 2011
6. ^ DAViCal release 0.9.9.2, Freshmeat, retrieved September 24, 2010
7. ^ Meishi, Github, retrieved March 30, 2012
8. ^ SabreDAV 1.5 released with CardDAV support, dmfs, retrieved September 11, 2011
9. ^ SOGo: Features, Inverse Inc.
10. ^ Yoon Lee, Jong (September 25, 2009), Zimbra Server: CardDAV server, Zimbra/VMWare Inc, retrieved April 24, 2010
11. ^ Ellingson, Jeff (September 27, 2012), A new way to sync Google Contacts, Google, retrieved September 27, 2012
12. ^ licobo Help, licobo, retrieved February 14, 2013
13. ^ ContactSync
14. ^ Implementations: CardDAV Clients, CalConnect, retrieved April 10, 2010
15. ^ Eran Dilger, Daniel (June 25, 2010), iPhone 4 and iOS vs. Android: desktop and cloud services, AppleInsider, retrieved July 24, 2010
16. ^ Atmail Client: CardDAV interface, Atmail, retrieved May 26, 2010
17. ^ CardDavMATE, Ján Máté, retrieved March 8, 2013
18. ^ CardDav-Sync, Marten Gajda, retrieved November 1, 2012
19. ^ CardDAV PHP, Christian Putzke, retrieved October 23, 2012
20. ^ CardDAV/Clients, retrieved February 19, 2012
21. ^ Kerio Connect, Kerio Technologies, retrieved April 10, 2010
22. ^ Koenig, Tobias (February 4, 2010), CalDAV/CardDAV/GroupDAV Support for Akonadi, Blogspot, retrieved April 24, 2010

[edit]External links

• The Internet Engineering Task Force (IETF)
• CardDAV Resources

This computing article is a stub. You can help Wikipedia by expanding it.