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-0089.xml 3.0KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667686970717273747576777879808182
  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>Generic Alerts</title>
  10. <abstract>A protocol for generic alerts (similar to .NET Alerts service).</abstract>
  11. &LEGALNOTICE;
  12. <number>0089</number>
  13. <status>Deferred</status>
  14. <type>Standards Track</type>
  15. <sig>Standards</sig>
  16. <dependencies/>
  17. <supersedes/>
  18. <supersededby/>
  19. <shortname>Not yet assigned</shortname>
  20. <!-- firstname, surname, email, and jid are all MANDATORY per XEP-0001 -->
  21. <!-- include one author section for each co-author -->
  22. <author>
  23. <firstname>Richard</firstname>
  24. <surname>Dobson</surname>
  25. <email>richard@dobson-i.net</email>
  26. <jid>richard@dobson-i.net</jid>
  27. </author>
  28. <revision>
  29. <version>0.2</version>
  30. <date>2003-05-16</date>
  31. <initials>red</initials>
  32. <remark>Changed element from x to alert.</remark>
  33. </revision>
  34. <revision>
  35. <version>0.1</version>
  36. <date>2003-05-12</date>
  37. <initials>red</initials>
  38. <remark>Initial version.</remark>
  39. </revision>
  40. </header>
  41. <section1 topic='Introduction'>
  42. <p>Generic Alerts is a way to extend headlines to allow functionality similar to .NET Alerts.</p>
  43. </section1>
  44. <section1 topic='Requirements'>
  45. <p>The motivations for this document are:</p>
  46. <ul>
  47. <li>To allow services to send alerts to users, e.g. like an auction notifying you when you are outbid or that you have won</li>
  48. </ul>
  49. </section1>
  50. <section1 topic='Use Cases'>
  51. <section2 topic='Generic Alert message'>
  52. <p>Generic Alerts extend headline messages to specify such things as a logo (32x32 png) and url to goto when the alert is clicked:</p>
  53. <example caption='Generic alert message'><![CDATA[
  54. <message to='user@domain.com' from='domain.com' type='headline' id='alert1'>
  55. <subject>Auction Alert</subject>
  56. <body>You have been outbid!</body>
  57. <alert xmlns='http://jabber.org/protocol/alert'>
  58. <logo>http://www.auction.com/alert.png</logo>
  59. <url>http://www.auction.com/item?1292192</url>
  60. </alert>
  61. </message>]]></example>
  62. </section2>
  63. </section1>
  64. <section1 topic='Implementation Notes'>
  65. <p>The following guidelines may assist client developers.</p>
  66. <ul>
  67. <li>The existance of an alert element of the namespace 'http://jabber.org/protocol/alert' means this is an alert and not a normal headline.</li>
  68. <li>Alerts should be displayed differently, possibly in toast popups.</li>
  69. <li>The logo is an optional graphic to display representing the service being alerted on, e.g. ebay logo.</li>
  70. <li>When clicked on the users web browser will be opened to the specified url.</li>
  71. </ul>
  72. </section1>
  73. <section1 topic='Security Considerations'>
  74. <p>None.</p>
  75. </section1>
  76. <section1 topic='IANA Considerations'>
  77. <p>No IANA interaction required.</p>
  78. </section1>
  79. <section1 topic='XMPP Registrar Considerations'>
  80. <p>The &REGISTRAR; will need to register the new namespace of "http://jabber.org/protocol/alert".</p>
  81. </section1>
  82. </xep>