diff --git a/xep-0084.xml b/xep-0084.xml index 64b19861..6dbd75e2 100644 --- a/xep-0084.xml +++ b/xep-0084.xml @@ -10,7 +10,7 @@ This document defines an XMPP protocol extension for exchanging user avatars. &LEGALNOTICE; 0084 - Proposed + Draft Standards Track Standards @@ -24,11 +24,25 @@ XEP-0153 - TO BE ASSIGNED + avatar + + data + http://www.xmpp.org/schemas/avatar-data.xsd + + + metadata + http://www.xmpp.org/schemas/avatar-metadata.xsd + &stpeter; &pgmillard; &temas; &xvirge; + + 1.0 + 2007-11-07 + psa +

Per a vote of the XMPP Council, advanced status to Draft; concurrently, the XMPP Registrar issued the urn:xmpp:avatar:data and urn:xmpp:avatar:metadata namespaces.

+
0.12 2007-08-31 @@ -141,9 +155,9 @@ - + - + qANQR1DBwU4DX7jmYZnncm... @@ -162,9 +176,9 @@ - + - + - + - + -

The user's virtual pubsub service would then send the metadata notification to entities that have subscribed to the user's metadata node or contacts who have advertised an interest in receiving avatar metadata by including a &xep0115; feature of "http://www.xmpp.org/extensions/xep-0084.html#ns-metadata+notify" &NSNOTE;.

+

The user's virtual pubsub service would then send the metadata notification to entities that have subscribed to the user's metadata node or contacts who have advertised an interest in receiving avatar metadata by including a &xep0115; feature of "urn:xmpp:avatar:metadata+notify".

- + - + - + @@ -242,9 +256,9 @@ to='romeo@montague.lit/home' id='retrieve1'> - + - + qANQR1DBwU4DX7jmYZnncm... @@ -261,7 +275,7 @@ - + @@ -273,9 +287,9 @@ - + - + @@ -289,16 +303,16 @@
-

The PEP subset of pubsub requires that there shall exist a one-to-one relationship between namespaces and nodes. Because the protocol defined herein stipulates the use of two nodes (one for avatar data and one for avatar metadata), we define two namespaces, each with a corresponding root element &NSNOTE;:

+

The PEP subset of pubsub requires that there shall exist a one-to-one relationship between namespaces and nodes. Because the protocol defined herein stipulates the use of two nodes (one for avatar data and one for avatar metadata), we define two namespaces, each with a corresponding root element:

    -
  • <data xmlns='http://www.xmpp.org/extensions/xep-0084.html#ns-data'/>
  • -
  • <metadata xmlns='http://www.xmpp.org/extensions/xep-0084.html#ns-metadata'/>
  • +
  • <data xmlns='urn:xmpp:avatar:data'/>
  • +
  • <metadata xmlns='urn:xmpp:avatar:metadata'/>

These are further specified below.

The <data/> element is used to communicate the avatar data itself, and only for the "image/png" content-type (support for which is REQUIRED).

+ IMAGE DATA ]]> @@ -317,7 +331,7 @@

The <info/> child element is used to communicate avatar metadata. Support for the <info/> element is REQUIRED.

+

The <pointer/> child element is used to point to an avatar that is not published via pubsub or HTTP, but rather is provided by a third-party service such as an online gaming system or virtual world.

+ ... APPLICATION-SPECIFIC DATA ... @@ -391,7 +405,7 @@

The <stop/> child element is used to signal that avatar publishing has been disabled.

+ ]]> @@ -406,9 +420,9 @@ - + - + - + - + - - + + ]]> @@ -515,7 +529,7 @@
-

Until this specification advances to a status of Draft, its associated namespaces shall be "http://www.xmpp.org/extensions/xep-0084.html#ns-data" and "http://www.xmpp.org/extensions/xep-0084.html#ns-metadata"; upon advancement of this specification, the ®ISTRAR; shall issue permanent namespaces in accordance with the process defined in Section 4 of &xep0053;.

+

The ®ISTRAR; includes "urn:xmpp:avatar:data" and "urn:xmpp:avatar:metadata" in its registry of protocol namespaces (see &NAMESPACES;).

@@ -525,10 +539,17 @@ + + + The protocol documented by this schema is defined in + XEP-0084: http://www.xmpp.org/extensions/xep-0084.html + + + @@ -540,10 +561,17 @@ + + + The protocol documented by this schema is defined in + XEP-0084: http://www.xmpp.org/extensions/xep-0084.html + + +