vcard-temp

%ents; ]>

vcard-temp This specification provides canonical documentation of the vCard-XML format currently in use within the Jabber community. &LEGALNOTICE; 0054 Active Historical Standards JIG XMPP Core vcard-temp &stpeter; 1.1 2003-03-26 psa Clarified certain historical inaccuracies and added links to archived versions of Frank Dawson's Internet-Drafts. 1.0 2003-01-09 psa Updated status to Active per vote of the Jabber Council. 0.2 2002-11-06 psa Many small fixes; added implementation notes. 0.1 2002-10-31 psa Initial version.

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.

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 &rfc2426;.

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 This document is archived at <http://www.watersprings.org/pub/id/draft-dawson-vcard-xml-dtd-01.txt>.. He also submitted a -02 revision on November 15, 1998 This document is archived at <http://www.watersprings.org/pub/id/draft-dawson-vcard-xml-dtd-02.txt>. and a -03 revision on June 22, 1999 This document is archived at <http://www.watersprings.org/pub/id/draft-dawson-vcard-xml-dtd-03.txt>..

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):

]]>

The server should then return the vCard to the user:

Peter Saint-Andre Saint-Andre Peter stpeter http://www.jabber.org/people/stpeter.php 1966-08-06 Jabber Software Foundation Executive Director Patron Saint 303-308-3282 Suite 600 1899 Wynkoop Street Denver CO 80202 USA 303-555-1212 Denver CO 80209 USA stpeter@jabber.org stpeter@jabber.org More information about me is located on my personal website: http://www.saint-andre.com/ ]]>

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.

]]>

The server should then return the other user's vCard to the requestor:

JeremieMiller Jeremie Miller jer jeremie@jabber.org jer@jabber.org ]]>

There are no security features or concerns related to this proposal.

This document requires no interaction with &IANA;.

The ®ISTRAR; includes the 'vcard-temp' namespace in its registry of official namespaces (see &NAMESPACES;).

As authorized by &xep0147;, the XMPP Registrar maintains a registry of queries and key-value pairs for use in XMPP URIs (see &QUERYTYPES;).

The "vcard" querytype is registered as a vCard-related action.

]]>

The following submission registers the "vcard" querytype.


  vcard
  vcard-temp
  enables retrieval of an entity's vCard data
  XEP-0054

    ]]>

Note the following:

The correct capitalization of the wrapper element is <vCard/> (and XML element names are case-sensitive).
All elements within the <vCard/> element MUST be in ALL CAPS (even though this is at odds with draft-dawson-vcard-xml-dtd-01).
The country abbreviation is contained in a <CTRY/> element, not a <COUNTRY/> element (even though this is at odds with draft-dawson-vcard-xml-dtd-01).
Phone numbers MUST be contained in a <NUMBER> element, not included as CDATA within the <TEL/> element.
If no telephone number is included in a <TEL/> element, an empty <NUMBER/> child MUST be included.
Email addresses MUST be contained in a <USERID> element, not included as CDATA within the <EMAIL/> element.
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".

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.

]]>