<p>This specification documents the vCard-XML format currently in use within the Jabber community. A future specification will recommend a standards-track protocol to supersede this informational document.</p>
<p>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.</p>
</section1>
<section1topic='History'>
<p>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 &rfc2426;.</p>
<p>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 <note>This document is archived at <<linkurl='http://www.watersprings.org/pub/id/draft-dawson-vcard-xml-dtd-01.txt'>http://www.watersprings.org/pub/id/draft-dawson-vcard-xml-dtd-01.txt</link>>.</note>. He also submitted a -02 revision on November 15, 1998 <note>This document is archived at <<linkurl='http://www.watersprings.org/pub/id/draft-dawson-vcard-xml-dtd-02.txt'>http://www.watersprings.org/pub/id/draft-dawson-vcard-xml-dtd-02.txt</link>>.</note> and a -03 revision on June 22, 1999 <note>This document is archived at <<linkurl='http://www.watersprings.org/pub/id/draft-dawson-vcard-xml-dtd-03.txt'>http://www.watersprings.org/pub/id/draft-dawson-vcard-xml-dtd-03.txt</link>>.</note>.</p>
<p>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.</p>
</section1>
<section1topic='Use Cases'>
<section2topic="Retrieving One's vCard">
<p>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):</p>
<examplecaption="Requesting One's Own vCard"><![CDATA[
<iq
from='stpeter@jabber.org/Gabber'
type='get'
id='v1'>
<vCardxmlns='vcard-temp'/>
</iq>
]]></example>
<p>The server should then return the vCard to the user:</p>
<examplecaption="Receiving One's Own vCard"><![CDATA[
<p>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.</p>
<p>If a user attempts to perform an IQ set on another user's vCard, the server MUST return a 403 "Forbidden" error.</p>
</section2>
<section2topic="Viewing Another User's vCard">
<p>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.</p>
<examplecaption="Requesting Another User's vCard"><![CDATA[
<iq
to='jer@jabber.org'
type='get'
id='v3'>
<vCardxmlns='vcard-temp'/>
</iq>
]]></example>
<p>The server should then return the other user's vCard to the requestor:</p>
<examplecaption="Receiving Another User's vCard"><![CDATA[
<li>The correct capitalization of the wrapper element is <vCard/> (and XML element names are case-sensitive).</li>
<li>All elements within the <vCard/> element MUST be in ALL CAPS (even though this is at odds with draft-dawson-vcard-xml-dtd-01).</li>
<li>The country abbreviation is contained in a <CTRY/> element, <em>not</em> a <COUNTRY/> element (even though this is at odds with draft-dawson-vcard-xml-dtd-01).</li>
<li>Phone numbers MUST be contained in a <NUMBER> element, not included as CDATA within the <TEL/> element.</li>
<li>If no telephone number is included in a <TEL/> element, an empty <NUMBER/> child MUST be included.</li>
<li>Email addresses MUST be contained in a <USERID> element, not included as CDATA within the <EMAIL/> element.</li>
<li>Some Jabber implementations add a 'version' attribute to the <vCard/> element, with the value set at "2.0" or "3.0". The DTD is incorrect, and the examples in draft-dawson-vard-xml-dtd-01 clearly show that version information is to be included by means of a 'version' attribute, not the <VERSION/> element as defined in the DTD. However, to conform to draft-dawson-vard-xml-dtd-01, the value should be "3.0", not "2.0".</li>
</ul>
</section1>
<section1topic='DTD'>
<p>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.</p>
<code><![CDATA[
<?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