diff --git a/xep-0145.xml b/xep-0145.xml index 44f92f7f..47391791 100644 --- a/xep-0145.xml +++ b/xep-0145.xml @@ -5,67 +5,74 @@ ]> -
- Annotations - This document defines an XML data format for making annotations about XMPP roster items and other entities. - &LEGALNOTICE; - 0145 - Proposed - Standards Track - Standards - Council - - XMPP Core - XEP-0060 - XEP-0223 - - - - rosternotes - - http://www.xmpp.org/schemas/rosternotes.xsd - - - Stefan - Strigler - steve@zeank.in-berlin.de - zeank@jwchat.org - - &stpeter; - - 1.1pre3 - in progress, last updated 2007-09-27 - psa -

Specified use of publish-subscribe private information nodes as the preferred storage mechanism.

 - - - 1.0 - 2006-03-23 - psa -

Per a vote of the Jabber Council, advanced to Active.

 - - - 0.2 - 2005-07-15 - psa -

Editorial review: changed type to Historical; changed namespace to storage:rosternotes; corrected schema; specified use of DateTime profile from XEP-0082; corrected some small textual errors.

 - - - 0.1 - 2004-11-05 - st -

Initial version.

 - -
+
+ Annotations + This document defines a protocol for making annotations about roster items and other entities. + &LEGALNOTICE; + 0145 - -

Many modern IM clients offer functionality that enables a user to make notes about the contacts in their roster. This is helpful if such contacts do not have meaningful information in their vCard or if the user needs to remember additional information related to a roster item. To define such functionality, we specify a <storage> element (similar to that introduced in &xep0048;) and appropriate child elements, qualified by a new namespace of 'storage:rosternotes'. While the <storage/> element can be stored using any XML storage mechanism, this document describes two such methods that are specific to XMPP.

- + Active + Historical + Standards + Council + + XMPP Core - -

Annotations are stored using a <storage/> element qualified by the 'storage:rosternotes' namespace. This element contains a collection of one or more <note/> elements, each representing a note about a given entity. For any given JID there MUST NOT be more than one note.

-

The 'jid' attribute of the <note/> element SHOULD be used without a resource, i.e., it SHOULD be a bare JID (&BAREJID;) rather than a full JID (&FULLJID;). Along with the annotation a client MAY choose to store the creation time ('cdate') and modification time ('mdate') as attributes to the <note/> element containing the annotation; these attributes MUST conform to the DateTime profile specified in &xep0082; and the timezone SHOULD be UTC.

- XEP-0049 + + + + rosternotes + + http://www.xmpp.org/schemas/rosternotes.xsd + + + + Stefan + Strigler + steve@zeank.in-berlin.de + zeank@jwchat.org + + + + 1.0 + 2006-03-23 + psa +

Per a vote of the Jabber Council, advanced to Active.

 + + + + 0.2 + 2005-07-15 + psa +

Editorial review: changed type to Historical; changed namespace to storage:rosternotes; corrected schema; specified use of DateTime profile from XEP-0082; corrected some small textual errors.

 + + + 0.1 + + 2004-11-05 + st +

Initial version.

 + +
+ + +

Many modern IM clients offer functionality that enables users to make notes about items in their roster. This comes in handy if users don't have meaningful information in their vCard or if you need to remember additional things related to a roster item.

+ +

This specification defines a protocol for storing annotations about a given set of entities. Its primary goal is to enable users to store some personal piece of information with their roster items. &xep0049; provides with a convenient method for storing user data on the server using the 'jabber:iq:private' namespace; all we need to do is define a namespace and schema for storing this sort of information. For this the 'storage' element introduced in &xep0048; is reused, and a new namespace of 'storage:rosternotes' is added.

+ + + + + +

Annotations are stored using server-side private XML storage (the 'jabber:iq:private' namespace). A storage element marked by the storage:rosternotes namespace contains a collection of one or more <note/> elements, each representing a note about a given entity. For any given JID there MUST NOT be more than one note.

+ +

The 'jid' attribute of the <note/> element SHOULD be used without a resource. Along with the annotation a client MAY choose to store creation time ('cdate') and modification time ('mdate') as attributes to the <note/> element containing the note; these attributes MUST conform to the DateTime profile specified in &xep0082; and the timezone SHOULD be UTC.

+ + + + Oh my sweetest love ... - ]]> -

Note: All notes are stored as a "bundle" within the same <storage/> element.

- - - -

It is RECOMMENDED to use &xep0060; for data storage, specifically through the use of personal data nodes hosted at the user's virtual publish-subscribe service as described in &xep0223; and illustrated in the following sections.

-

Note: In the past, &xep0049; was the recommended method (see the archived version of this specification at <http://www.xmpp.org/extensions/attic/xep-0048-1.0.html>). In addition, other methods could be used, such as HTTP or WebDAV.

- - - - - - - Seems to be a good writer - Oh my sweetest love ... - - - - - - - http://jabber.org/protocol/pubsub#publish-options - - - true - - - whitelist - - - - + - ]]> - - ]]> - - -

The stored data is automatically pushed to all of the user's connected resources.

- - - - - - Seems to be a good writer - Oh my sweetest love ... - - - - - +]]> - - - - - - Seems to be a good writer - Oh my sweetest love ... - - - - - - ]]> - - -

In order to retrieve stored data without receiving notifications (e.g., upon initial login), the user's client sends a retrieve-items request as specified in XEP-0060.

- - - - +

Note: All notes are stored as a "bundle" within the same <storage/> element.

+ +

Retrieving notes uses the protocol described in XEP-0049.

+ + + + + + - ]]> - - - - - - Seems to be a good writer - Oh my sweetest love ... - - - - +]]> + + + + + + Seems to be a good writer + Oh my sweetest love ... + + - ]]> - - +]]> - -

Security considerations related to object persistent via publish-subscribe are described in XEP-0060 and XEP-0223.

- +

For error conditions please refer to XEP-0049.

- -

No interaction with &IANA; is required as a result of this document.

- + - -

No action by the ®ISTRAR; is required, since the 'storage:rosternotes' namespace is already included in the protocol namespaces registry (see &NAMESPACES;).

- + - - Security considerations related to private XML storage are described in XEP-0049.

+ + + +

No interaction with &IANA; is required as a result of this document.

+ + + +

No namespaces or parameters need to be registered with the ®ISTRAR; as a result of this document.

+ + + + - ]]> - + ]]> + +