No Description
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

xep-0093.xml 5.1KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135
  1. <?xml version='1.0' encoding='UTF-8'?>
  2. <!DOCTYPE xep SYSTEM 'xep.dtd' [
  3. <!ENTITY % ents SYSTEM "xep.ent">
  4. %ents;
  5. ]>
  6. <?xml-stylesheet type='text/xsl' href='xep.xsl'?>
  7. <xep>
  8. <header>
  9. <title>Roster Item Exchange</title>
  10. <abstract>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.</abstract>
  11. &LEGALNOTICE;
  12. <number>0093</number>
  13. <status>Deprecated</status>
  14. <type>Historical</type>
  15. <sig>Standards</sig>
  16. <dependencies>
  17. <spec>XMPP Core</spec>
  18. <spec>XMPP IM</spec>
  19. </dependencies>
  20. <supersedes/>
  21. <supersededby>
  22. <spec>XEP-0144</spec>
  23. </supersededby>
  24. <shortname>x-roster</shortname>
  25. <schemaloc>
  26. <url>http://www.xmpp.org/schemas/x-roster.xsd</url>
  27. </schemaloc>
  28. &stpeter;
  29. <revision>
  30. <version>1.2</version>
  31. <date>2005-08-26</date>
  32. <initials>psa</initials>
  33. <remark>Per advancement of XEP-0144 by the Jabber Council, changed status to Deprecated.</remark>
  34. </revision>
  35. <revision>
  36. <version>1.1</version>
  37. <date>2004-02-24</date>
  38. <initials>psa</initials>
  39. <remark>Corrected several small textual errors.</remark>
  40. </revision>
  41. <revision>
  42. <version>1.0</version>
  43. <date>2003-10-08</date>
  44. <initials>psa</initials>
  45. <remark>Per a vote of the Jabber Council, changed status to Active.</remark>
  46. </revision>
  47. <revision>
  48. <version>0.1</version>
  49. <date>2003-05-22</date>
  50. <initials>psa</initials>
  51. <remark>Initial version.</remark>
  52. </revision>
  53. </header>
  54. <section1 topic='Introduction'>
  55. <p>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 &rfc2779;, the 'jabber:x:roster' namespace was removed from &xmppim;. This specification fills the void for canonical documentation.</p>
  56. <p><em>NOTE WELL: This document has been superseded by &xep0144;.</em></p>
  57. </section1>
  58. <section1 topic='Definition'>
  59. <p>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 &lt;message/&gt; element an &lt;x/&gt; child scoped by the 'jabber:x:roster' namespace. This &lt;x/&gt; element MUST contain at least one &lt;item/&gt; child elements (one for each roster item to be sent).</p>
  60. <p>Each &lt;item/&gt; element may possess the following attributes:</p>
  61. <ul>
  62. <li><strong>jid</strong> -- The Jabber Identifier of the contact being sent. This attribute is REQUIRED.</li>
  63. <li><strong>name</strong> -- A natural-language nickname for the contact. This attribute is OPTIONAL.</li>
  64. </ul>
  65. <p>Each &lt;item/&gt; element MAY also contain one or more &lt;group/&gt; children specifying the natural-language name of a user-specified group, for the purpose of categorizing this contact into one or more roster groups.</p>
  66. </section1>
  67. <section1 topic='Examples'>
  68. <example caption='A Roster Item Sent to another Entity'><![CDATA[
  69. <message to='hamlet@denmark' from='horatio@denmark'>
  70. <subject>Visitors</subject>
  71. <body>This message contains roster items.</body>
  72. <x xmlns='jabber:x:roster'>
  73. <item jid='rosencrantz@denmark'
  74. name='Rosencrantz'>
  75. <group>Visitors</group>
  76. </item>
  77. <item jid='guildenstern@denmark'
  78. name='Guildenstern'>
  79. <group>Visitors</group>
  80. </item>
  81. </x>
  82. </message>
  83. ]]></example>
  84. </section1>
  85. <section1 topic='Security Considerations'>
  86. <p>There are no security features or concerns related to this proposal.</p>
  87. </section1>
  88. <section1 topic='IANA Considerations'>
  89. <p>This document requires no interaction with &IANA;.</p>
  90. </section1>
  91. <section1 topic='XMPP Registrar Considerations'>
  92. <p>The 'jabber:x:roster' namespace is registered in the protocol namespaces registry maintained by the &REGISTRAR;.</p>
  93. </section1>
  94. <section1 topic='XML Schema'>
  95. <code><![CDATA[
  96. <?xml version='1.0' encoding='UTF-8'?>
  97. <xs:schema
  98. xmlns:xs='http://www.w3.org/2001/XMLSchema'
  99. targetNamespace='jabber:x:roster'
  100. xmlns='jabber:x:roster'
  101. elementFormDefault='qualified'>
  102. <xs:annotation>
  103. <xs:documentation>
  104. The protocol documented by this schema is defined in
  105. XEP-0093: http://www.xmpp.org/extensions/xep-0093.html
  106. NOTE WELL: This protocol has been superseded by XEP-0144
  107. http://www.xmpp.org/extensions/xep-0144.html
  108. </xs:documentation>
  109. </xs:annotation>
  110. <xs:element name='x'>
  111. <xs:complexType>
  112. <xs:sequence>
  113. <xs:element ref='item' minOccurs='1' maxOccurs='unbounded'/>
  114. </xs:sequence>
  115. </xs:complexType>
  116. </xs:element>
  117. <xs:element name='item'>
  118. <xs:complexType>
  119. <xs:sequence>
  120. <xs:element name='group' type='xs:string' minOccurs='0' maxOccurs='unbounded'/>
  121. </xs:sequence>
  122. <xs:attribute name='jid' type='xs:string' use='required'/>
  123. <xs:attribute name='name' type='xs:string' use='optional'/>
  124. </xs:complexType>
  125. </xs:element>
  126. </xs:schema>
  127. ]]></code>
  128. </section1>
  129. </xep>