mirror of
https://github.com/moparisthebest/xeps
synced 2024-12-17 21:32:35 -05:00
278 lines
11 KiB
XML
278 lines
11 KiB
XML
<?xml version='1.0' encoding='UTF-8'?>
|
|
<!DOCTYPE xep SYSTEM 'xep.dtd' [
|
|
<!ENTITY % ents SYSTEM 'xep.ent'>
|
|
%ents;
|
|
]>
|
|
<?xml-stylesheet type='text/xsl' href='xep.xsl'?>
|
|
<xep>
|
|
<header>
|
|
<title>vCard Infobits Mapping</title>
|
|
<abstract>NOTE: This proposal was retracted by the author on 2004-02-19.</abstract>
|
|
<!--
|
|
<abstract>A mapping of vCard data to the Jabber infobits protocol.</abstract>
|
|
-->
|
|
&LEGALNOTICE;
|
|
<number>0125</number>
|
|
<status>Retracted</status>
|
|
<type>Informational</type>
|
|
<sig>Standards</sig>
|
|
<dependencies><spec>XEP-0120</spec></dependencies>
|
|
<supersedes/>
|
|
<supersededby/>
|
|
<shortname>N/A</shortname>
|
|
&stpeter;
|
|
<revision>
|
|
<version>0.1</version>
|
|
<date>2003-12-15</date>
|
|
<initials>psa</initials>
|
|
<remark>Initial version, split off from version 0.5 of XEP-0121 (with revisions to more clearly map vCard elements); further mapping and description required.</remark>
|
|
</revision>
|
|
</header>
|
|
<section1 topic='Introduction'>
|
|
<p>&xep0120; defines a protocol for capturing granular information (or "infobits") about users, servers, services, rooms, nodes, commands, files, and other phenomena on the Jabber/XMPP network; however, that document defines the protocol only, not the infobits themselves. This document specifies how to encapsulate one sort of metadata in infobits: the metadata elements about entities defined by &rfc2426; (supplemented by vCard-like metadata that is not defined in RFC 2426), thus enabling the Jabber community to supersede &xep0054;. Note well that this document is decidedly <em>not</em> meant to provide an exhaustive catalog of possible infobits. Future registrations, whether in XMPP Extension Protocol specifications or direct submissions to the ®ISTRAR;, will specify additional infobits.</p>
|
|
</section1>
|
|
<section1 topic='vCard Mapping'>
|
|
<p>In order to supersede the vCard-XML protocol currently in use within the Jabber community, it is necessary to define infobits that correspond to the data elements defined by the vCard-XML DTD (more precisely, the vCard Profile Features specified in section 3 of RFC 2426). These are shown in the following table. (Note: this mapping uses the vCard entity names specified in &dawson3;, not those specified in XEP-0054.)</p>
|
|
<table caption='Mapping of vCard Fields'>
|
|
<tr>
|
|
<th>Infobit Key</th>
|
|
<th>vCard Element</th>
|
|
<th>Comments</th>
|
|
</tr>
|
|
<tr>
|
|
<td>birthdate</td>
|
|
<td>bday (partial)</td>
|
|
<td>Date of birth (DD); prepend with birthyear and birthmonth (with "-" separators) to create vCard bday content</td>
|
|
</tr>
|
|
<tr>
|
|
<td>birthmonth</td>
|
|
<td>bday (partial)</td>
|
|
<td>Month of birth (MM); prepend with birthyear and append with birthdate (with "-" separators) to create vCard bday content</td>
|
|
</tr>
|
|
<tr>
|
|
<td>birthyear</td>
|
|
<td>bday (partial)</td>
|
|
<td>Year of birth (YYYY); append with birthmonth and birthdate (with "-" separators) to create vCard bday content; the vCard "bday" element is separated into three infobits so that users can abstain from providing a birthyear</td>
|
|
</tr>
|
|
<tr>
|
|
<td>cellphone</td>
|
|
<td>tel + cell</td>
|
|
<td>A cellphone (mobile phone) number; if more than one cellphone number is specified, this infobit keyname should be appended with one of the following modifiers: home, work</td>
|
|
</tr>
|
|
<tr>
|
|
<td>city</td>
|
|
<td>city</td>
|
|
<td>If more than one address is specified (e.g., work and home), this infobit keyname may be appended with any of the following address modifiers: home, work, postal, parcel (e.g., city.home)</td>
|
|
</tr>
|
|
<tr>
|
|
<td>country</td>
|
|
<td>country</td>
|
|
<td>If more than one address is specified (e.g., work and home), this infobit keyname may be appended with any of the following address modifiers: home, work, postal, parcel (e.g., country.home)</td>
|
|
</tr>
|
|
<tr>
|
|
<td>email</td>
|
|
<td>email</td>
|
|
<td>If more than one email address is specified, this infobit name should be appended with one of the following address modifiers: home, work</td>
|
|
</tr>
|
|
<tr>
|
|
<td>extadd</td>
|
|
<td>extadd</td>
|
|
<td>Extended address; if more than one address is specified (e.g., work and home), this infobit keyname may be appended with any of the following address modifiers: home, work, postal, parcel (e.g., extadd.home)</td>
|
|
</tr>
|
|
<tr>
|
|
<td>family</td>
|
|
<td>family</td>
|
|
<td>A family name or surname; in some cultures, known as a "last name"</td>
|
|
</tr>
|
|
<tr>
|
|
<td>fax</td>
|
|
<td>tel + fax</td>
|
|
<td>A fax number; if more than one fax number is specified, this infobit keyname should be appended with one of the following modifiers: home, work</td>
|
|
</tr>
|
|
<tr>
|
|
<td>fn</td>
|
|
<td>fn</td>
|
|
<td>A full name</td>
|
|
</tr>
|
|
<tr>
|
|
<td>given</td>
|
|
<td>given</td>
|
|
<td>A given name; in some cultures, known as a "first name"</td>
|
|
</tr>
|
|
<tr>
|
|
<td>key</td>
|
|
<td>key</td>
|
|
<td>This SHOULD be a URL to or identifier for a public key, but MAY be the key information itself</td>
|
|
</tr>
|
|
<tr>
|
|
<td>lat</td>
|
|
<td>lat</td>
|
|
<td>Latitude in decimal degrees North</td>
|
|
</tr>
|
|
<tr>
|
|
<td>logo</td>
|
|
<td>logo</td>
|
|
<td>This MUST be a URL to a logo; recipients should be prepared to parse the URL in order to retrieve and then decode the binary information</td>
|
|
</tr>
|
|
<tr>
|
|
<td>lon</td>
|
|
<td>lon</td>
|
|
<td>Longitude in decimal degrees East</td>
|
|
</tr>
|
|
<tr>
|
|
<td>middle</td>
|
|
<td>middle</td>
|
|
<td>A person's middle name or initial</td>
|
|
</tr>
|
|
<tr>
|
|
<td>nickname</td>
|
|
<td>nickname</td>
|
|
<td>A person's preferred nickname or less formal name</td>
|
|
</tr>
|
|
<tr>
|
|
<td>orgnam</td>
|
|
<td>orgnam</td>
|
|
<td>A name for an organization</td>
|
|
</tr>
|
|
<tr>
|
|
<td>orgunit</td>
|
|
<td>orgunit</td>
|
|
<td>A name for an organizational unit</td>
|
|
</tr>
|
|
<tr>
|
|
<td>pager</td>
|
|
<td>tel + pager</td>
|
|
<td>A pager number; if more than one pager number is specified, this infobit keyname should be appended with one of the following modifiers: home, work</td>
|
|
</tr>
|
|
<tr>
|
|
<td>pcode</td>
|
|
<td>pcode</td>
|
|
<td>A postal code; if more than one address is specified (e.g., work and home), this infobit name may be appended with any of the following address modifiers: home, work, postal, parcel</td>
|
|
</tr>
|
|
<tr>
|
|
<td>phone</td>
|
|
<td>tel + voice</td>
|
|
<td>A voice phone number; if more than one voice phone number is specified, this infobit keyname should be appended with one of the following modifiers: home, work</td>
|
|
</tr>
|
|
<tr>
|
|
<td>photo</td>
|
|
<td>photo + extval</td>
|
|
<td>This MUST be a URL to a photo; recipients should be prepared to parse the URL in order to retrieve and then decode the binary information</td>
|
|
</tr>
|
|
<tr>
|
|
<td>prefix</td>
|
|
<td>prefix</td>
|
|
<td>A prefix to a name (e.g., "Dr.")</td>
|
|
</tr>
|
|
<tr>
|
|
<td>region</td>
|
|
<td>region</td>
|
|
<td>If more than one address is specified, this infobit keyname may be appended with any of the following address modifiers: home, work, postal, parcel (e.g., region.home)</td>
|
|
</tr>
|
|
<tr>
|
|
<td>role</td>
|
|
<td>role</td>
|
|
<td>A person's role within an organization</td>
|
|
</tr>
|
|
<tr>
|
|
<td>sound</td>
|
|
<td>sound + extval</td>
|
|
<td>This MUST be a URL to a sound file; recipients should be prepared to parse the URL in order to retrieve and then decode the binary information</td>
|
|
</tr>
|
|
<tr>
|
|
<td>street</td>
|
|
<td>street</td>
|
|
<td>Street number and name; if more than one address is specified, this infobit keyname may be appended with any of the following address modifiers: home, work, postal, parcel (e.g., street.home)</td>
|
|
</tr>
|
|
<tr>
|
|
<td>suffix</td>
|
|
<td>suffix</td>
|
|
<td>A suffix to a name (e.g., "Esq.")</td>
|
|
</tr>
|
|
<tr>
|
|
<td>title</td>
|
|
<td>title</td>
|
|
<td>This is a job title, and is not to be confused with the &DUBLINCORE; "title" metadata term</td>
|
|
</tr>
|
|
<tr>
|
|
<td>vmail</td>
|
|
<td>tel + msg</td>
|
|
<td>A voicemail (message) number; if more than one voicemail number is specified, this infobit keyname should be appended with one of the following modifiers: home, work</td>
|
|
</tr>
|
|
<tr>
|
|
<td>website</td>
|
|
<td>url</td>
|
|
<td>URL for any website</td>
|
|
</tr>
|
|
</table>
|
|
</section1>
|
|
<section1 topic='Supplementing vCard'>
|
|
<p>The vCard specification does not include the following infobits because either (1) it is not that granular or (2) they represent entities or properties that did not exist when the vCard format was defined.</p>
|
|
<table caption='Additional vCard-Like Infobits'>
|
|
<tr>
|
|
<th>Infobit</th>
|
|
<th>Comments</th>
|
|
</tr>
|
|
<tr>
|
|
<td>alt</td>
|
|
<td>Altitude in meters above sea level</td>
|
|
</tr>
|
|
<tr>
|
|
<td>area</td>
|
|
<td>An area within a locality; if more than one address is specified, this infobit keyname may be appended with any of the following address modifiers: home, work, postal, parcel (e.g., area.home)</td>
|
|
</tr>
|
|
<tr>
|
|
<td>building</td>
|
|
<td>The name of a specific building; if more than one address is specified, this infobit keyname may be appended with any of the following address modifiers: home, work, postal, parcel (e.g., building.home)</td>
|
|
</tr>
|
|
<tr>
|
|
<td>expertise</td>
|
|
<td>A self-defined area of expertise (no guarantees provided)</td>
|
|
</tr>
|
|
<tr>
|
|
<td>floor</td>
|
|
<td>The floor of a building; if more than one address is specified, this infobit keyname may be appended with any of the following address modifiers: home, work, postal, parcel (e.g., floor.home)</td>
|
|
</tr>
|
|
<tr>
|
|
<td>gender</td>
|
|
<td>The self-defined gender of a user (this is not limited to "male" and "female", although those are the expected values in most instances)</td>
|
|
</tr>
|
|
<tr>
|
|
<td>interest</td>
|
|
<td>A self-defined area of interest</td>
|
|
</tr>
|
|
<tr>
|
|
<td>jid</td>
|
|
<td>An entity's Jabber Identifier</td>
|
|
</tr>
|
|
<tr>
|
|
<td>orgurl</td>
|
|
<td>URL for organization's website</td>
|
|
</tr>
|
|
<tr>
|
|
<td>room</td>
|
|
<td>A specific room; if more than one address is specified, this infobit keyname may be appended with any of the following address modifiers: home, work, postal, parcel (e.g., room.home)</td>
|
|
</tr>
|
|
<tr>
|
|
<td>weblog</td>
|
|
<td>URL for weblog</td>
|
|
</tr>
|
|
</table>
|
|
</section1>
|
|
<section1 topic='Security Considerations'>
|
|
<p>This document introduces no security considerations above and beyond those already defined in XEP-0120.</p>
|
|
</section1>
|
|
<section1 topic='IANA Considerations'>
|
|
<p>This document requires no interaction with &IANA;.</p>
|
|
</section1>
|
|
<section1 topic='XMPP Registrar Considerations'>
|
|
<p>The following is a submission to the infobits registry called for by XEP-0120.</p>
|
|
<section2 topic='vCard Mapping Infobits'>
|
|
<p>To follow.</p>
|
|
</section2>
|
|
<section2 topic='vCard Supplement Infobits'>
|
|
<p>To follow.</p>
|
|
</section2>
|
|
</section1>
|
|
</xep>
|