Roster Item Exchange

Roster Item Exchange This specification provides canonical documentation of the jabber:x:roster namespace historically used within the Jabber community. NOTE WELL: This specification has been superseded by XEP-0144. This XMPP Extension Protocol is copyright © 1999 – 2024 by the XMPP Standards Foundation (XSF). Permission is hereby granted, free of charge, to any person obtaining a copy of this specification (the "Specification"), to make use of the Specification without restriction, including without limitation the rights to implement the Specification in a software program, deploy the Specification in a network service, and copy, modify, merge, publish, translate, distribute, sublicense, or sell copies of the Specification, and to permit persons to whom the Specification is furnished to do so, subject to the condition that the foregoing copyright notice and this permission notice shall be included in all copies or substantial portions of the Specification. Unless separate permission is granted, modified works that are redistributed shall not contain misleading information regarding the authors, title, number, or publisher of the Specification, and shall not claim endorsement of the modified works by the authors, any organization or project to which the authors belong, or the XMPP Standards Foundation. ## NOTE WELL: This Specification is provided on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. ## In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall the XMPP Standards Foundation or any author of this Specification be liable for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising from, out of, or in connection with the Specification or the implementation, deployment, or other use of the Specification (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if the XMPP Standards Foundation or such author has been advised of the possibility of such damages. This XMPP Extension Protocol has been contributed in full conformance with the XSF's Intellectual Property Rights Policy (a copy of which can be found at <https://xmpp.org/about/xsf/ipr-policy> or obtained by writing to XMPP Standards Foundation, P.O. Box 787, Parker, CO 80134 USA). 0093 Deprecated Historical Standards XMPP Core XMPP IM XEP-0144 x-roster http://www.xmpp.org/schemas/x-roster.xsd Peter Saint-Andre stpeter@stpeter.im stpeter@jabber.org https://stpeter.im/ 1.2 2005-08-26 psa Per advancement of XEP-0144 by the Jabber Council, changed status to Deprecated. 1.1 2004-02-24 psa Corrected several small textual errors. 1.0 2003-10-08 psa Per a vote of the Jabber Council, changed status to Active. 0.1 2003-05-22 psa Initial version.

The Jabber protocols have long included a method for sending roster items to another entity. This method makes use of the 'jabber:x:roster' namespace and has been documented variously in Internet-Drafts and elsewhere. Because this protocol is not required by RFC 2779 RFC 2779: A Model for Presence and Instant Messaging <http://tools.ietf.org/html/rfc2779>., the 'jabber:x:roster' namespace was removed from XMPP IM RFC 6121: Extensible Messaging and Presence Protocol (XMPP): Instant Messaging and Presence <http://tools.ietf.org/html/rfc6121>.. This specification fills the void for canonical documentation.

NOTE WELL: This document has been superseded by Roster Item Exchange (XEP-0144) XEP-0144: Roster Item Exchange <https://xmpp.org/extensions/xep-0144.html>..

The 'jabber:x:roster' namespace (which is not to be confused with the 'jabber:iq:roster' namespace) is used to send roster items from one Jabber entity to another. A roster item is sent by adding to the <message/> element an <x/> child scoped by the 'jabber:x:roster' namespace. This <x/> element MUST contain at least one <item/> child elements (one for each roster item to be sent).

Each <item/> element may possess the following attributes:

jid -- The Jabber Identifier of the contact being sent. This attribute is REQUIRED.
name -- A natural-language nickname for the contact. This attribute is OPTIONAL.

Each <item/> element MAY also contain one or more <group/> children specifying the natural-language name of a user-specified group, for the purpose of categorizing this contact into one or more roster groups.

Visitors This message contains roster items. Visitors Visitors ]]>

There are no security features or concerns related to this proposal.

This document requires no interaction with the Internet Assigned Numbers Authority (IANA) The Internet Assigned Numbers Authority (IANA) is the central coordinator for the assignment of unique parameter values for Internet protocols, such as port numbers and URI schemes. For further information, see <http://www.iana.org/>..

The 'jabber:x:roster' namespace is registered in the protocol namespaces registry maintained by the XMPP Registrar The XMPP Registrar maintains a list of reserved protocol namespaces as well as registries of parameters used in the context of XMPP extension protocols approved by the XMPP Standards Foundation. For further information, see <https://xmpp.org/registrar/>..





  
    
      The protocol documented by this schema is defined in
      XEP-0093: http://www.xmpp.org/extensions/xep-0093.html

      NOTE WELL: This protocol has been superseded by XEP-0144
      http://www.xmpp.org/extensions/xep-0144.html
    
  

  
    
      
        
      
    
  

  
    
      
        
      
      
      
    
  


]]>