This JEP provides canonical documentation of the vCard-XML format currently in use within the Jabber community.
NOTICE: This Historical JEP provides canonical documentation of a protocol that is in wide use within the Jabber community. This JEP is not a standards-track specification within the Jabber Software Foundation's standards process; therefore it may be converted to standards-track in the future or may be obsoleted by a more modern protocol.
Status: Active
Type: Historical
Number: 0054
Version: 1.1
Last Updated: 2003-03-26
JIG: Standards JIG
Approving Body: Jabber Council
Dependencies: XMPP Core
Supersedes: None
Superseded By: None
Short Name: vcard-temp
Email: stpeter@jabber.org
JID: stpeter@jabber.org
This Jabber Enhancement Proposal is copyright 1999 - 2004 by the Jabber Software Foundation (JSF) and is in full conformance with the JSF's Intellectual Property Rights Policy <http://www.jabber.org/jsf/ipr-policy.php>. This material may be distributed only subject to the terms and conditions set forth in the Open Publication License, v1.0 or later (the latest version is presently available at <http://www.opencontent.org/openpub/>).
The preferred venue for discussion of this document is the Standards-JIG discussion list: <http://mail.jabber.org/mailman/listinfo/standards-jig>.
The Extensible Messaging and Presence Protocol (XMPP) is defined in the XMPP Core and XMPP IM specifications contributed by the Jabber Software Foundation to the Internet Standards Process, which is managed by the Internet Engineering Task Force in accordance with RFC 2026. Any protocols defined in this JEP have been developed outside the Internet Standards Process and are to be understood as extensions to XMPP rather than as an evolution, development, or modification of XMPP itself.
The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119.
This JEP documents the vCard-XML format currently in use within the Jabber community. A future JEP will recommend a standards-track protocol to supersede this informational document.
The basic functionality is for a user to store and retrieve an XML representation of his or her vCard using the data storage capabilities native to all existing Jabber server implementations. This is done by by sending an <iq/> of type "set" (storage) or "get" (retrieval) to one's Jabber server containing a <vCard/> child scoped by the 'vcard-temp' namespace, with the <vCard/> element containing the actual vCard-XML elements as defined by the vCard-XML DTD. Other users may then view one's vCard information.
vCards are an existing and widely-used standard for personal user information storage, somewhat like an electronic business card. The vCard format is defined in RFC 2426 [1].
In 1998 and 1999, Frank Dawson submitted four revisions of an Internet-Draft proposing to represent the standard vCard format in XML. When the Jabber project was originally looking for a method to store personal user information, the most recent revision was draft-dawson-vcard-xml-dtd-01 [2]. He also submitted a -02 revision on November 15, 1998 [3] and a -03 revision on June 22, 1999 [4].
Unfortunately, Dawson's proposal did not move forward within the IETF's standards process. For reasons now lost in the mists of time, the Jabber project continued to use the DTD from draft-dawson-vcard-xml-dtd-01, making two small modifications to adapt it for use within Jabber (adding the JABBERID and DESC elements) but also specifying element names in all caps rather than lowercase as defined in draft-dawson-vcard-xml-dtd-01. In addition, the Jabber community followed the usage (but not DTD) in that draft regarding version information, including it as an attribute of the vCard element rather than as a child element. This format was implemented within Jabber under the 'vcard-temp' namespace.
A user may retrieve his or her own vCard by sending XML of the following form to his or her own JID (the 'to' attibute SHOULD NOT be included):
Example 1. Requesting One's Own vCard
<iq from='stpeter@jabber.org/Gabber' type='get' id='v1'> <vCard xmlns='vcard-temp'/> </iq>
The server should then return the vCard to the user:
Example 2. Receiving One's Own vCard
<iq to='stpeter@jabber.org/Gabber' type='result' id='v1'> <vCard xmlns='vcard-temp'> <FN>Peter Saint-Andre</FN> <N> <FAMILY>Saint-Andre<FAMILY> <GIVEN>Peter</GIVEN> <MIDDLE/> </N> <NICKNAME>stpeter</NICKNAME> <URL>http://www.jabber.org/people/stpeter.php</URL> <BDAY>1966-08-06</BDAY> <ORG> <ORGNAME>Jabber Software Foundation</ORGNAME> <ORGUNIT/> </ORG> <TITLE>Executive Director</TITLE> <ROLE>Patron Saint</ROLE> <TEL><VOICE/><WORK/><NUMBER>303-308-3282</NUMBER></TEL> <TEL><FAX/><WORK/><NUMBER/></TEL> <TEL><MSG/><WORK/><NUMBER/></TEL> <ADR> <WORK/> <EXTADD>Suite 600</EXTADD> <STREET>1899 Wynkoop Street</STREET> <LOCALITY>Denver</LOCALITY> <REGION>CO</REGION> <PCODE>80202</PCODE> <CTRY>USA</CTRY> </ADR> <TEL><VOICE/><HOME/><NUMBER>303-555-1212</NUMBER></TEL> <TEL><FAX/><HOME/><NUMBER/></TEL> <TEL><MSG/><HOME/><NUMBER/></TEL> <ADR> <HOME/> <EXTADD/> <STREET/> <LOCALITY>Denver</LOCALITY> <REGION>CO</REGION> <PCODE>80209</PCODE> <CTRY>USA</CTRY> </ADR> <EMAIL><INTERNET/><PREF/><USERID>stpeter@jabber.org</USERID></EMAIL> <JABBERID>stpeter@jabber.org</JABBERID> <DESC> More information about me is located on my personal website: http://www.saint-andre.com/ </DESC> </vCard> </iq>
A user may update his or her vCard by sending an IQ of type "set" to the server, following the format in the previous use case.
If a user attempts to perform an IQ set on another user's vCard, the server MUST return a 403 "Forbidden" error.
A user may view another user's vCard by sending an IQ of type "get" to the other user's bare JID. A compliant server MUST return the vCard to the requestor and not forward the IQ to the requestee's connected resource.
Example 3. Requesting Another User's vCard
<iq to='jer@jabber.org' type='get' id='v3'> <vCard xmlns='vcard-temp'/> </iq>
The server should then return the other user's vCard to the requestor:
Example 4. Receiving Another User's vCard
<iq from='jer@jabber.org' to='stpeter@jabber.org/home' type='result' id='v3'> <vCard xmlns='vcard-temp'> <FN>JeremieMiller</FN> <N> <GIVEN>Jeremie</GIVEN> <FAMILY>Miller</FAMILY> <MIDDLE/> </N> <NICKNAME>jer</NICKNAME> <EMAIL><INTERNET/><PREF/><USERID>jeremie@jabber.org</USERID></EMAIL> <JABBERID>jer@jabber.org</JABBERID> </vCard> </iq>
There are no security features or concerns related to this proposal.
This JEP requires no interaction with the Internet Assigned Numbers Authority (IANA) [5].
The Jabber Registrar [6] registers the 'vcard-temp' namespace in its registry of official namespaces.
Note the following:
The following DTD is a slightly modified version of that contained in draft-dawson-vcard-xml-dtd-01. The only modifications were to add the JABBERID and DESC elements.
<?xml version="1.0" encoding="UTF-8"?> <!-- Copyright (C) The Internet Society (2000). All Rights Reserved. This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implmentation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organizations, except as needed for the purpose of developing Internet standards in which case the procedures for copyrights defined in the Internet Standards process MUST be followed, or as required to translate it into languages other than English. The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assigns. This document and the information contained herein is provided on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. --> <!-- ==== --> <!-- NOTE: the following root element is not used in the modified vcard-temp DTD published by the Jabber project (now Jabber Software Foundation) and is included here only for historical purposes; implementations that comply with vcard-temp must specify the root element as vCard, not xCard. --> <!-- Root element and container for one or more vCard objects --> <!ELEMENT xCard (vCard)+> <!-- Individual vCard container --> <!ELEMENT vCard ( (VERSION, FN, N), (NICKNAME?, PHOTO?, BDAY?, ADR?, LABEL?, TEL?, EMAIL?, JABBERID?, MAILER?, TZ?, GEO?, TITLE?, ROLE?, LOGO?, AGENT?, ORG?, CATEGORIES?, NOTE?, PRODID?, REV?, SORT-STRING?, SOUND?, UID?, URL?, CLASS?, KEY?, DESC? )*)> <!-- vCard specification version property. This MUST be 2.0, if the document conforms to RFC 2426. --> <!ELEMENT VERSION (#PCDATA)> <!-- Formatted or display name property. --> <!ELEMENT FN (#PCDATA)> <!-- Structured name property. Name components with multiple values must be specified as a comma separated list of values. --> <!ELEMENT N ( FAMILY?, GIVEN?, MIDDLE?, PREFIX?, SUFFIX?)> <!ELEMENT FAMILY (#PCDATA)> <!ELEMENT GIVEN (#PCDATA)> <!ELEMENT MIDDLE (#PCDATA)> <!ELEMENT PREFIX (#PCDATA)> <!ELEMENT SUFFIX (#PCDATA)> <!-- Nickname property. Multiple nicknames must be specified as a comma separated list value. --> <!ELEMENT NICKNAME (#PCDATA)> <!-- Photograph property. Value is either a BASE64 encoded binary value or a URI to the external content. --> <!ELEMENT PHOTO ((TYPE, BINVAL) | EXTVAL)> <!-- Birthday property. Value must be an ISO 8601 formatted date or date/time value. --> <!ELEMENT BDAY (#PCDATA)> <!-- Structured address property. Address components with multiple values must be specified as a comma separated list of values. --> <!ELEMENT ADR ( HOME?, WORK?, POSTAL?, PARCEL?, (DOM | INTL)?, PREF?, POBOX?, EXTADR?, STREET?, LOCALITY?, REGION?, PCODE?, CTRY? )> <!ELEMENT POBOX (#PCDATA)> <!ELEMENT EXTADR (#PCDATA)> <!ELEMENT STREET (#PCDATA)> <!ELEMENT LOCALITY (#PCDATA)> <!ELEMENT REGION (#PCDATA)> <!ELEMENT PCODE (#PCDATA)> <!ELEMENT CTRY (#PCDATA)> <!-- Address label property. --> <!ELEMENT LABEL ( HOME?, WORK?, POSTAL?, PARCEL?, (DOM | INTL)?, PREF?, LINE+ )> <!-- Individual label lines. --> <!ELEMENT LINE (#PCDATA)> <!-- Telephone number property. --> <!ELEMENT TEL ( HOME?, WORK?, VOICE?, FAX?, PAGER?, MSG?, CELL?, VIDEO?, BBS?, MODEM?, ISDN?, PCS?, PREF?, NUMBER )> <!-- Phone number value. --> <!ELEMENT NUMBER (#PCDATA)> <!-- Email address property. Default type is INTERNET. --> <!ELEMENT EMAIL ( HOME?, WORK?, INTERNET?, PREF?, X400?, USERID )> <!ELEMENT USERID (#PCDATA)> <!-- NOTE: the following element was added by the Jabber project (now Jabber Software Foundation) to handle Jabber IDs; the value must be in the form of user@host --> <!ELEMENT JABBERID (#PCDATA)> <!-- Mailer (e.g., Mail User Agent Type) property. --> <!ELEMENT MAILER (#PCDATA)> <!-- Time zone's Standard Time UTC offset. Value must be an ISO 8601 formatted UTC offset. --> <!ELEMENT TZ (#PCDATA)> <!-- Geographical position. Values are the decimal degress of LATitude and LONgitude. The value should be specified to six decimal places.--> <!ELEMENT GEO (LAT, LON)> <!-- Latitude value. --> <!ELEMENT LAT (#PCDATA)> <!-- Longitude value. --> <!ELEMENT LON (#PCDATA)> <!-- Title property. --> <!ELEMENT TITLE (#PCDATA)> <!-- Role property. --> <!ELEMENT ROLE (#PCDATA)> <!-- Organization logo property. --> <!ELEMENT LOGO ((TYPE, BINVAL) | EXTVAL)> <!-- Administrative agent property. --> <!ELEMENT AGENT (vCard | EXTVAL)> <!-- Organizational name and units property. --> <!ELEMENT ORG (ORGNAME, ORGUNIT*)> <!ELEMENT ORGNAME (#PCDATA)> <!ELEMENT ORGUNIT (#PCDATA)> <!-- Application specific categories property. --> <!ELEMENT CATEGORIES (KEYWORD+)> <!ELEMENT KEYWORD (#PCDATA)> <!-- Commentary note property. --> <!ELEMENT NOTE (#PCDATA)> <!-- Identifier of product that generated the vCard property. --> <!ELEMENT PRODID (#PCDATA)> <!-- Last revised property. The value must be an ISO 8601 formatted UTC date/time. --> <!ELEMENT REV (#PCDATA)> <!-- Sort string property. --> <!ELEMENT SORT-STRING (#PCDATA)> <!-- Formatted name pronunciation property. The value is either a textual phonetic pronunciation, a BASE64 encoded binary digital audio pronunciation or a URI to an external binary digital audio pronunciation.--> <!ELEMENT SOUND (PHONETIC | BINVAL | EXTVAL)> <!-- Textual phonetic pronunciation. --> <!ELEMENT PHONETIC (#PCDATA)> <!-- Unique identifier property. --> <!ELEMENT UID (#PCDATA)> <!-- Directory URL property. --> <!ELEMENT URL (#PCDATA)> <!-- NOTE: the following element was added by the Jabber project (now Jabber Software Foundation) to handle free-form descriptive text. --> <!ELEMENT DESC (#PCDATA)> <!-- Privacy classification property. --> <!ELEMENT CLASS (PUBLIC | PRIVATE | CONFIDENTIAL)> <!ELEMENT PUBLIC EMPTY> <!ELEMENT PRIVATE EMPTY> <!ELEMENT CONFIDENTIAL EMPTY> <!-- Authentication credential or encryption key property. --> <!ELEMENT KEY (TYPE?, CRED)> <!ELEMENT CRED (#PCDATA)> <!-- ==== --> <!-- Common elements. --> <!-- Addressing type indicators. --> <!ELEMENT HOME EMPTY> <!ELEMENT WORK EMPTY> <!ELEMENT POSTAL EMPTY> <!ELEMENT PARCEL EMPTY> <!ELEMENT DOM EMPTY> <!ELEMENT INTL EMPTY> <!ELEMENT PREF EMPTY> <!ELEMENT VOICE EMPTY> <!ELEMENT FAX EMPTY> <!ELEMENT PAGER EMPTY> <!ELEMENT MSG EMPTY> <!ELEMENT CELL EMPTY> <!ELEMENT VIDEO EMPTY> <!ELEMENT BBS EMPTY> <!ELEMENT MODEM EMPTY> <!ELEMENT ISDN EMPTY> <!ELEMENT PCS EMPTY> <!ELEMENT INTERNET EMPTY> <!ELEMENT X400 EMPTY> <!-- Format type parameter. --> <!ELEMENT TYPE (#PCDATA)> <!-- Base64 encoded binary value. --> <!ELEMENT BINVAL (#PCDATA)> <!-- URI to external binary value --> <!ELEMENT EXTVAL (#PCDATA)> <!-- ==== -->
1. RFC 2426: vCard MIME Directory Profile <http://www.ietf.org/rfc/rfc2426.txt>.
2. This document is archived at <http://www.watersprings.org/pub/id/draft-dawson-vcard-xml-dtd-01.txt>.
3. This document is archived at <http://www.watersprings.org/pub/id/draft-dawson-vcard-xml-dtd-02.txt>.
4. This document is archived at <http://www.watersprings.org/pub/id/draft-dawson-vcard-xml-dtd-03.txt>.
5. The Internet Assigned Numbers Authority (IANA) is the central coordinator for the assignment of unique parameter values for Internet protocols, such as port numbers and URI schemes. For further information, see <http://www.iana.org/>.
6. The Jabber Registrar maintains a list of reserved Jabber protocol namespaces as well as registries of parameters used in the context of protocols approved by the Jabber Software Foundation. For further information, see <http://www.jabber.org/registrar/>.
END