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-0014.xml 2.8KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667686970717273747576
  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>Message Tone</title>
  10. <abstract>A proposal for including the sender's tone in messages.</abstract>
  11. &LEGALNOTICE;
  12. <number>0014</number>
  13. <status>Rejected</status>
  14. <type>Standards Track</type>
  15. <sig>Standards</sig>
  16. <dependencies>
  17. <spec>XMPP Core</spec>
  18. </dependencies>
  19. <supersedes/>
  20. <supersededby/>
  21. <shortname>N/A</shortname>
  22. <author>
  23. <firstname>Mike</firstname>
  24. <surname>Mintz</surname>
  25. <email>psicoder@yahoo.com</email>
  26. <jid>mikem@jabber.org</jid>
  27. </author>
  28. <revision>
  29. <version>0.2</version>
  30. <date>2002-01-16</date>
  31. <initials>psa</initials>
  32. <remark>First release to CVS, including editorial changes and assignment of number.</remark>
  33. </revision>
  34. <revision>
  35. <version>0.1</version>
  36. <date>2001-11-17</date>
  37. <initials>mm</initials>
  38. <remark>Initial version.</remark>
  39. </revision>
  40. </header>
  41. <section1 topic='Introduction'>
  42. <p>When people speak to one another, they use various tones of voice and body language to express themselves. When communicating online, people have no easy way of expressing themselves clearly. By incorporating message tones into Jabber, people will be able to convey tones such as anger, sarcasm, and confusion.</p>
  43. </section1>
  44. <section1 topic='Protocol Implementation'>
  45. <p>Tone can be added only to messages, and it is added as an &#60;x&#62; tag inside a message. The &#60;x&#62; tag will look something like this:</p>
  46. <example>
  47. &#60;x xmlns='jabber:x:tone'&#62;angry&#60;/x&#62;
  48. </example>
  49. <p>The specified tone is included as CDATA within the &#60;x&#62; element.</p>
  50. <section2 topic='Example'>
  51. <p>Here is an example of a message with a tone:</p>
  52. <example>
  53. &#60;message to='mikem@jabber.org'&#62;
  54. &#60;body&#62;
  55. Why the hell did they reject my idea?
  56. &#60;/body&#62;
  57. &#60;x xmlns='jabber:x:tone'&#62;angry&#60;/x&#62;
  58. &#60;/message&#62;
  59. </example>
  60. </section2>
  61. </section1>
  62. <section1 topic='Representing Tones'>
  63. <p>Tones are not meant to be sent with every message. They should be used only in cases where a tone dramatically applies. The overuse of tones will cause them to lose their effect.</p>
  64. <p>Because tones are abstract and not clearly defined, there is no standard list of tones. Clients should receive the tone as it is and display it as plain text, in such a way that it is linked to a specific message. Clients may want to have a specified list of tones that a user can select from when sending a message.</p>
  65. <p>Tones should be short and simple. Here is a list of good tones:</p>
  66. <ul>
  67. <li>angry</li>
  68. <li>confused</li>
  69. <li>excited</li>
  70. <li>joking</li>
  71. <li>sad</li>
  72. <li>sarcastic</li>
  73. <li>serious</li>
  74. </ul>
  75. </section1>
  76. </xep>