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-0036.xml 5.3KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121
  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>Pub-Sub Subscriptions</title>
  10. <abstract>A proposal for the subscribe half of a publish-subscribe protocol within Jabber.</abstract>
  11. &LEGALNOTICE;
  12. <number>0036</number>
  13. <status>Retracted</status>
  14. <type>Standards Track</type>
  15. <sig>Standards</sig>
  16. <dependencies/>
  17. <supersedes/>
  18. <supersededby><spec>XEP-0060</spec></supersededby>
  19. <shortname>None</shortname>
  20. &pgmillard;
  21. &stpeter;
  22. <revision>
  23. <version>0.2</version>
  24. <date>2003-04-22</date>
  25. <initials>psa</initials>
  26. <remark>At the request of the authors, the status of this specification has been changed to Retracted since it has been superseded by XEP-0060.</remark>
  27. </revision>
  28. <revision>
  29. <version>0.1</version>
  30. <date>2002-07-12</date>
  31. <initials>psa</initials>
  32. <remark>Initial version based on discussions at JabberConf.</remark>
  33. </revision>
  34. </header>
  35. <section1 topic='Introduction'>
  36. <p>The Jabber community needs a cohesive standard for publish-subscribe functionality. Certainly there is interest in developing such a standard, as witness the number of proposals written on this topic (&xep0021;, &xep0024;, XEP-0028). Unfortunately, past discussion of this issue has been clouded by confusion over requirements and even terminology. This XEP seeks to clarify the situation somewhat and to provide a protocol for the subscribe half of publish-subscribe functionality within Jabber.</p>
  37. </section1>
  38. <section1 topic='Narrative'>
  39. <p>Traditional pub-sub consists of event notification. This makes it possible for entities to publish data and for other interested entities to receive notification when the data is published. The following are some likely applications of pub-sub functionality within Jabber:</p>
  40. <ul>
  41. <li>Auction and trading systems</li>
  42. <li>Online catalogs</li>
  43. <li>Document workflow systems</li>
  44. <li>Network management systems</li>
  45. <li>NNTP over Jabber</li>
  46. <li>Groupchat</li>
  47. </ul>
  48. <p>In such systems, a subscriber would request to receive notifications about data the subscriber is interested in. We define a "topic" as an object that defines the relationship between a publisher and its subscribers. Specifically, a topic contains three essential collections of information:</p>
  49. <ol>
  50. <li>A description of the information that will be provided</li>
  51. <li>A list of subscribers to items that fit the description</li>
  52. <li>One or more items that fit the description</li>
  53. </ol>
  54. <p>We define an "item" as an instance of data published by the publisher that fits the description associated with a topic. Each item MAY possess a unique identifier that enables the data to be tracked. (NOTE: This XEP does not address the durability of items, i.e., data storage.)</p>
  55. <p>A topic is addressed by means of a unique "topic ID". A topic ID is simply a string with no required semantic meaning. While a topic ID may have semantic meaning (e.g., '/instruments/guitars/electric' or 'rec.music.dylan'), such meaning is not necessary and a topic ID may be any random string (e.g., 'a1gh83jfn342092'). The only requirement is that a topic ID be unique within the context of a specific pub-sub domain (e.g., pubsub.jabber.org).</p>
  56. </section1>
  57. <section1 topic='Protocol Details'>
  58. <example caption="Protocol">
  59. &lt;iq type="set" from="pgm@jabber.org" to="pubsub.jabber.org" id="1"&gt;
  60. &lt;query xmlns="jabber:iq:pubsub"&gt;
  61. &lt;subscribe&gt;
  62. &lt;topic id="12345"/&gt;
  63. &lt;topic id="/presence/dizzyd@jabber.org"/&gt;
  64. &lt;/subscribe&gt;
  65. &lt;/query&gt;
  66. &lt;/iq&gt;
  67. &lt;iq type="set" from="pgm@jabber.org" to="pubsub.jabber.org" id="1"&gt;
  68. &lt;query xmlns="jabber:iq:pubsub"&gt;
  69. &lt;unsubscribe&gt;
  70. &lt;topic id="12345"/&gt;
  71. &lt;/unsubscribe&gt;
  72. &lt;/query&gt;
  73. &lt;/iq&gt;
  74. &lt;iq type="set" to="pubsub.jabber.org" id="1"&gt;
  75. &lt;query xmlns="jabber:iq:pubsub"&gt;
  76. &lt;publish&gt;
  77. &lt;topic id="12345"&gt;
  78. &lt;item&gt;some kind of cdata goes here&lt;/item&gt;
  79. &lt;/topic&gt;
  80. &lt;/publish&gt;
  81. &lt;/query&gt;
  82. &lt;/iq&gt;
  83. &lt;iq type="set" to="pubsub.jabber.org" id="1"&gt;
  84. &lt;query xmlns="jabber:iq:pubsub"&gt;
  85. &lt;createtopic&gt;
  86. &lt;topic id="new_topic"&gt;
  87. &lt;profile&gt;
  88. &lt;!-- is this even remotely close?? --&gt;
  89. &lt;publisher&gt;pgm@jabber.org&lt;/publisher&gt;
  90. &lt;publisher&gt;dizzyd@jabber.org&lt;/publisher&gt;
  91. &lt;/profile&gt;
  92. &lt;/topic&gt;
  93. &lt;topic id="another_topic&gt;
  94. &lt;profile&gt;
  95. &lt;publisher/&gt;
  96. &lt;/profile&gt;
  97. &lt;/topic&gt;
  98. &lt;/createtopic&gt;
  99. &lt;/query&gt;
  100. &lt;/iq&gt;
  101. &lt;iq type="set" to="pubsub.jabber.org" id="1"&gt;
  102. &lt;query xmlns="jabber:iq:pubsub"&gt;
  103. &lt;removetopic&gt;
  104. &lt;topic id="12345"/&gt;
  105. &lt;/removetopic&gt;
  106. &lt;/query&gt;
  107. &lt;/iq&gt;
  108. </example>
  109. </section1>
  110. <section1 topic='Author Note' anchor='authornote'>
  111. <p>Peter Millard, co-author of this specification, died on April 26, 2006.</p>
  112. </section1>
  113. </xep>