From 535cd0a682f237ad9755299f576b5feff0510fb9 Mon Sep 17 00:00:00 2001 From: stpeter Date: Mon, 27 Jun 2011 15:22:44 -0600 Subject: [PATCH] 0.6 --- xep-0292.xml | 16 +++++++++++++--- 1 file changed, 13 insertions(+), 3 deletions(-) diff --git a/xep-0292.xml b/xep-0292.xml index afcd95bb..dc0c1666 100644 --- a/xep-0292.xml +++ b/xep-0292.xml @@ -31,6 +31,12 @@ samizzi@cisco.com samizzi@cisco.com + + 0.6 + 2011-06-27 + sm/psa +

Clarified status of VERSION and TZ properties.

 + 0.5 2011-06-24 @@ -227,7 +233,7 @@ ]]> -

An XMPP entity publishes or updates its vCard by sending an IQ-set to itself, containing a <vcard/> child element qualified by the 'urn:ietf:params:xml:ns:vcard-4.0' namespace.

+

An XMPP entity publishes or updates its vCard by sending an IQ-set to itself, containing a <vcard/> child element qualified by the 'urn:ietf:params:xml:ns:vcard-4.0' namespace. The publication request needs to include the entire vCard, not a "diff" against the prior data (if any).

]]> -

Note: There is no payload, because this is a pure notification (the receiver needs to retrieve the vCard using an IQ-get as described earlier..

+

Note: There is no payload, because this is a pure notification (the receiver needs to retrieve the vCard using an IQ-get as described earlier.

 -

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 "thing" for the vCard4 KIND property &vcardthing;. An example follows.

+

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 "thing" for the vCard4 KIND property &vcardthing;, as illustrated in the following example:

The source of the spurious <PHONETIC/> element is unknown. However, it does not exist in vCard4 and therefore is simply discarded when mapping.

+ +

As explained in XEP-0054, the <VERSION/> element from the final Dawson draft was not used in vcard-temp; instead, the vcard-temp protocol used a 'version' attribute (in fact the Dawson drafts were inconsistent, since the DTD defined a <VERSION/> element and the body of the specification used a 'version' attribute).

+

The following properties are defined differently in vcard-temp and vCard4. As a result, the mappings are workable but might not preserve all information that could have been contained in vcard-temp data.

@@ -425,6 +434,7 @@ property-key = element key {
  • REV
  • ROLE
  • TITLE
    • +
  • TZ
  • UID
  • URL