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-0123.xml 8.2KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148
  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>Entity Metadata</title>
  10. <abstract>NOTE: This proposal was retracted by the author on 2004-02-19.</abstract>
  11. <!--
  12. <abstract>Using Infobits and Service Discovery to define and communicate metadata about entities.</abstract>
  13. -->
  14. &LEGALNOTICE;
  15. <number>0123</number>
  16. <status>Retracted</status>
  17. <type>Standards Track</type>
  18. <sig>Standards</sig>
  19. <dependencies>
  20. <spec>XMPP Core</spec>
  21. <spec>XMPP IM</spec>
  22. <spec>XEP-0030</spec>
  23. <spec>XEP-0120</spec>
  24. </dependencies>
  25. <supersedes/>
  26. <supersededby/>
  27. <shortname>N/A</shortname>
  28. &stpeter;
  29. <revision>
  30. <version>0.3</version>
  31. <date>2003-12-16</date>
  32. <initials>psa</initials>
  33. <remark>Incorporated infobits changes and vCard infobit mappings; metadata about relationships to be moved to forthcoming specification.</remark>
  34. </revision>
  35. <revision>
  36. <version>0.2</version>
  37. <date>2003-10-23</date>
  38. <initials>psa</initials>
  39. <remark>Changed ent to entity, rel to relation.</remark>
  40. </revision>
  41. <revision>
  42. <version>0.1</version>
  43. <date>2003-10-22</date>
  44. <initials>psa</initials>
  45. <remark>Initial version, split off from XEP-0120.</remark>
  46. </revision>
  47. </header>
  48. <section1 topic='Background and Requirements'>
  49. <p>Traditionally, the only mechanism for communicating detailed information about entities on the Jabber network has been an XML version of the vCard format for electronic business cards (see &xep0054;). Unfortunately, the vCard format has several major drawbacks:</p>
  50. <ol>
  51. <li>It is mainly limited to data about persons (although it has been used on the Jabber network to describe things like servers).</li>
  52. <li>The format contains relatively few data fields.</li>
  53. <li>The format is not extensible.</li>
  54. <li>As implemented, the data is not searchable.</li>
  55. <li>As implemented, the data cannot be filtered depending on the identity of the requestor.</li>
  56. </ol>
  57. <p>It is becoming increasingly important to define a robust, extensible format for describing entities on the Jabber network. Such a format should be:</p>
  58. <ol>
  59. <li>Applicable not just to people but to any entity on the network, including but not limited to servers, components, bots, &xep0045; rooms, &xep0060; nodes, and in general anything that can be addressed as a Jabber ID (as defined in &xmppcore;).</li>
  60. <li>Usable in encapsulating any information about the entity itself (name, address, description, title, etc.).</li>
  61. <li>Extensible enough to handle any metadata that may be needed for current and future applications (including, at a minimum, everything that can be defined in vCard); it must be possible to use it for public protocols defined by the IETF or XMPP Standards Foundation as well as for custom or private protocols.</li>
  62. <li>Well-defined enough, through datatyping and public registries where applicable, to enable robust searching and filtering based on defined data fields and their values.</li>
  63. </ol>
  64. </section1>
  65. <section1 topic='Protocol'>
  66. <p>Information about entities is provided using the &xep0120; protocol and registered infobit keynames (mainly those specified in &xep0125; although entity metadata is by no means limited to vCard information and could include infobits such as those specified in &xep0121;). The metadata is discovered by interacting with a common &xep0030; node named "metadata". The queried entity replies with a service discovery result containing any infobits that the entity wishes to reveal about itself to the requesting entity. This information is always metadata about the entity itself, not any other entities or any relationships that the entity may have to other entities.</p>
  67. </section1>
  68. <section1 topic='Use Cases'>
  69. <section2 topic='Discovering Support'>
  70. <p>Support for entity metadata is discovered by means of Service Discovery. If the queried entity provides metadata about itself, it SHOULD advertise that fact by listing an item named "metadata" in response to a disco#items query.</p>
  71. <example caption='One Entity Queries Another via Disco'><![CDATA[
  72. <iq type='get'
  73. from='juliet@capulet.com/balcony'
  74. to='romeo@montague.net/orchard'
  75. id='disco1'>
  76. <query xmlns='http://jabber.org/protocol/disco#items'/>
  77. </iq>
  78. ]]></example>
  79. <p>The entity returns its associated items:</p>
  80. <example caption='Entity Returns Disco Item Results'><![CDATA[
  81. <iq type='result'
  82. from='romeo@montague.net/orchard'
  83. to='juliet@capulet.com/balcony'
  84. id='disco1'>
  85. <query xmlns='http://jabber.org/protocol/disco#items'>
  86. ...
  87. <item jid='juliet@capulet.com'
  88. node='metadata'
  89. name='Information about Juliet Capulet'/>
  90. ...
  91. </query>
  92. </iq>
  93. ]]></example>
  94. </section2>
  95. <section2 topic='Requesting Metadata About Another Entity'>
  96. <p>In order to request the advertised metadata, the requesting entity sends a disco#info request to the 'metadata' node of the JID communicated in the previous result.</p>
  97. <example caption='Requestor Requests Metadata'><![CDATA[
  98. <iq type='get'
  99. from='juliet@capulet.com/balcony'
  100. to='romeo@montague.net'
  101. id='request1'>
  102. <query xmlns='http://jabber.org/protocol/disco#info'
  103. node='metadata'/>
  104. </iq>
  105. ]]></example>
  106. <p>The entity returns its metadata to the requestor.</p>
  107. <example caption='Entity Returns Metadata Result'><![CDATA[
  108. <iq type='result'
  109. from='romeo@montague.net'
  110. to='juliet@capulet.com/balcony'
  111. id='request2'>
  112. <query xmlns='http://jabber.org/protocol/disco#info'
  113. node='metadata'>
  114. <info 'http://jabber.org/protocol/infobits'>
  115. <bit key='fn'>Romeo Montague</bit>
  116. <bit key='country'>Italy</bit>
  117. <bit key='city'>Verona</bit>
  118. <bit key='gender'>male</bit>
  119. <bit key='nickname'>loverboy</bit>
  120. </info>
  121. </query>
  122. </iq>
  123. ]]></example>
  124. </section2>
  125. </section1>
  126. <section1 topic='Integration with Directory Services'>
  127. <p>One of the primary motivations behind this proposal is to enable the construction of useful directory services on the Jabber network. Examples of such services include but are not limited to:</p>
  128. <ul>
  129. <li>robust user directories</li>
  130. <li>directories of groupchat rooms</li>
  131. <li>directories of pubsub nodes</li>
  132. <li>server directories</li>
  133. </ul>
  134. <p>Although such directories will be a valuable addition to the network, it is imperative to understand that the canonical source for metadata about an entity is the entity itself. Mechanisms for keeping directories synchronized with entities are outside the scope of this document, and in any case a directory may not be privy to all information about an entity (since in general a user should publish to a directory only the information that he or she deems world-readable).</p>
  135. <p>Directories SHOULD require registration using &xep0077;. Before registering with a directory, an entity SHOULD adjust its access controls or privacy rules accordingly, including appropriate definition of classes and addition of the directory server's JID to the relevant privacy rules. Upon accepting registration from an entity, a directory SHOULD immediately send a metadata request to the registering entity. Synchronization of metadata is a matter for the directory implementation to determine, and perhaps negotiate with the registering entity; all such synchronization and negotiation is out of scope for this document.</p>
  136. </section1>
  137. <section1 topic='Security Considerations'>
  138. <p>Metadata MAY be world-readable. Entities MUST take care to ensure that they exercise proper control over access to such information. Users of IM clients SHOULD be warned that their data may be world-readable and be given the option to not publish such information or control it via appropriate mechanisms (such as privacy rules).</p>
  139. </section1>
  140. <section1 topic='IANA Considerations'>
  141. <p>This document requires no interaction with &IANA;.</p>
  142. </section1>
  143. <section1 topic='XMPP Registrar Considerations'>
  144. <section2 topic='Service Discovery Nodes'>
  145. <p>Upon advancement of this proposal to a status of Draft, the &REGISTRAR; shall add the 'metadata' node to its registry of common Service Discovery nodes.</p>
  146. </section2>
  147. </section1>
  148. </xep>