moparisthebest
/
xeps
mirror of https://github.com/moparisthebest/xeps
1
0
Fork 0
Code Issues Releases Wiki Activity

0.8

This commit is contained in:
stpeter 2011-08-31 18:10:39 -06:00
parent a452b8c884
commit 6caad9581c
1 changed files with 12 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
xep-0292.xml
View File

@ -16,8 +16,8 @@
<approver>Council</approver>
<dependencies>
<spec>XMPP Core</spec>
<spec>draft-ietf-vcarddav-vcardrev</spec>
<spec>draft-ietf-vcarddav-vcardxml</spec>
<spec><cite>RFC 6350</cite></spec>
<spec><cite>RFC 6351</cite></spec>
</dependencies>
<supersedes>
<spec>XEP-0054</spec>
@ -31,6 +31,12 @@
<email>samizzi@cisco.com</email>
<jid>samizzi@cisco.com</jid>
</author>
<revision>
<version>0.8</version>
<date>2011-08-31</date>
<initials>psa</initials>
<remark><p>Updated to reflect RFC 6350, RFC 6351, and draft-ietf-vcarddav-kind-app.</p></remark>
</revision>
<revision>
<version>0.7</version>
<date>2011-07-10</date>
@ -106,14 +112,14 @@
</header>
<section1 topic='Introduction' anchor='intro'>
<p>Since 1999, the Jabber/XMPP community has used an interim, unofficial XML representation of vCard data for personal contacts, called &xep0054;. Recently, the IETF has upgraded vCard from vCard3 to &vcardrev;, and at the same time has defined &vcardxml; as an official XML format for vCard4. This document specifies an XMPP extension for use of the vCard4 XML format in XMPP systems, with the intent of obsoleting the vcard-temp format. Primarily this document defines the encapsulation method itself; secondarily it also defines transport methods and a mapping to the vcard-temp format for migration by clients and servers.</p>
<p>Since 1999, the Jabber/XMPP community has used an interim, unofficial XML representation of vCard data for personal contacts, called &xep0054;. Recently, the IETF has upgraded vCard from vCard3 to vCard 4(&rfc6350;), and at the same time has defined an official XML format for vCard4 (&rfc6351;). This document specifies an XMPP extension for use of the vCard4 XML format in XMPP systems, with the intent of obsoleting the vcard-temp format. Primarily this document defines the encapsulation method itself; secondarily it also defines transport methods and a mapping to the vcard-temp format for migration by clients and servers.</p>
</section1>
<section1 topic='Requirements' anchor='reqs'>
<p>This specification was designed with the following requirements in mind.</p>
<ol>
<li>Reuse vCard4 as defined in draft-ietf-vcarddav-vcardrev.</li>
<li>Reuse the vCard4 XML format as defined in draft-ietf-vcarddav-vcardxml.</li>
<li>Reuse vCard4 as defined in <cite>RFC 6350</cite>.</li>
<li>Reuse the vCard4 XML format as defined in <cite>RFC 6351</cite>.</li>
<li>Ensure that clients and servers can easily migrate from vcard-temp to the new encapsulation format.</li>
<li>Notify interested parties of changes to vCard data using standard XMPP extensions, specifically &xep0163;.</li>
<li>Support vCards for non-human entities such as XMPP servers and &xep0045; rooms.</li>
@ -292,7 +298,7 @@
</section1>
<section1 topic='vCards of Automated Entities' anchor='apps'>
<p>Traditionally, vCards have been used on the XMPP network for entities other than human users, e.g. by XMPP servers and chatrooms. When such automated entities use vCards, it is RECOMMENDED to specify a value of "application" for the vCard4 KIND property &vcardthing;, as illustrated in the following example:</p>
<p>Traditionally, vCards have been used on the XMPP network for entities other than human users, e.g. by XMPP servers and chatrooms. When such automated entities use vCards, it is RECOMMENDED to specify a value of "application" for the vCard4 KIND property &vcardapp;, as illustrated in the following example:</p>
<example caption="vCard for a Thing"><![CDATA[
<iq from='jabber.org'
id='yhx51c35'