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-0148.xml 15KB

  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>Instant Messaging Intelligence Quotient (IM IQ)</title>
  10. <abstract>This specification provides canonical documentation of the jabber:iq:iq namespace.</abstract>
  12. <number>0148</number>
  13. <status>Active</status>
  14. <type>Humorous</type>
  15. <sig>Standards</sig>
  16. <approver>Council</approver>
  17. <dependencies>
  18. <spec>XMPP Core</spec>
  19. </dependencies>
  20. <supersedes/>
  21. <supersededby/>
  22. <shortname>iq-iq</shortname>
  23. &stpeter;
  24. <revision>
  25. <version>1.0</version>
  26. <date>2005-04-01</date>
  27. <initials>psa</initials>
  28. <remark><p>April Fools!</p></remark>
  29. </revision>
  30. </header>
  31. <section1 topic='Introduction' anchor='intro'>
  32. <p>The early Jabber community was a hotbed of innovation and experimentation. Although the community produced a large number of interesting protocols and technologies, not all of them were widely adopted. For example, server-side message filtering (implemented in the mod_filter module of the &jabberd; server) was one promising technology that simply did not scale up beyond a few hundred concurrent users. Another potentially helpful technology (though even less well-known) was that of the "Instant Messaging Intelligence Quotient" (IM IQ) as defined by the 'jabber:iq:iq' protocol. For the sake of historical completeness, this specification provides canonical documentation of that protocol.</p>
  33. </section1>
  34. <section1 topic='Concepts and Approach' anchor='concepts'>
  35. <p>It is a harsh reality of the modern Internet that plenty of stupid people have found their way onto today's communication networks (email, Usenet, IM, and the like). Because the early Jabber developers were your typically elitist geeks (whose mantra seems to have been "not everyone can be as smart as we are"), they sought to shield themselves from the inevitable emergence of dumb Jabber users.</p>
  36. <p>At the same time, recognizing the wisdom of the age-old saying "to err is human", they knew that even normally intelligent people sometimes say appallingly stupid things. In fact, such normally intelligent people (well, okay, geniuses) might be the developers themselves! Thus they sought to build protective measures into Jabber servers so that they could avoid appearing dumb.</p>
  37. <p>The early Jabber developers sought to achieve both of these objectives through the design of server-side intelligence detection systems using dedicated protocol elements qualified by the 'jabber:iq:iq' namespace. This protocol implements procedures for discovering, monitoring, and getting feedback on the intelligence of one's own instant messages, as well as that of other users on the network. The "IM IQ" of each user is determined by server-side parsing of messages sent by all registered users of a server, using advanced linguistic analysis techniques (as described under <link url='#impl'>Implementation Notes</link> below) enforced by the mod_iq jabberd module.</p>
  38. </section1>
  39. <section1 topic='Use Cases' anchor='usecases'>
  40. <section2 topic='Discover Another User&apos;s IM IQ' anchor='disco-other'>
  41. <p>Before chatting with another user over the network or adding that user to one's Jabber roster, it can be helpful to get a sense of how intelligent or unintelligent that person is. This is done by requesting the person's IM IQ from that person's server by sending an IQ get qualified by the 'jabber:iq:iq' namespace to the person's bare JID (user@host) rather than full JID (similar in this regard to the functionality of &xep0054;).</p>
  42. <example caption='Requesting Someone&apos;s IM IQ'><![CDATA[
  43. <iq type='get'
  44. from=''
  45. to=''
  46. id='imiq1'>
  47. <query xmlns='jabber:iq:iq'/>
  48. </iq>
  49. ]]></example>
  50. <p>The server then returns the person's IM IQ, expressed as a REQUIRED &lt;num/&gt; integer between zero and 256, and an OPTIONAL &lt;desc/&gt; containing a natural-language descriptive phrase associated with that range of integer values.</p>
  51. <example caption='Receiving Someone&apos;s IM IQ'><![CDATA[
  52. <iq type='result'
  53. from=''
  54. to=''
  55. id='imiq1'>
  56. <query xmlns='jabber:iq:iq'>
  57. <num>66</num>
  58. <desc>moron</desc>
  59. </query>
  60. </iq>
  61. ]]></example>
  62. </section2>
  63. <section2 topic='Discovering One&apos;s Own IM IQ' anchor='disco-own'>
  64. <p>In order for a user to discover his or her own IM IQ, the user sends an IQ get without any 'to' address.</p>
  65. <example caption='Requesting One&apos;s Own IM IQ'><![CDATA[
  66. <iq type='get' id='myiq'>
  67. <query xmlns='jabber:iq:iq'/>
  68. </iq>
  69. ]]></example>
  70. <example caption='Receiving One&apos;s Own IM IQ'><![CDATA[
  71. <iq type='result' id='myiq'>
  72. <query xmlns='jabber:iq:iq'>
  73. <num>83</num>
  74. <desc>dull</desc>
  75. </query>
  76. </iq>
  77. ]]></example>
  78. <p>A user may not agree with his or her IM IQ as computed by the server (after all, everyone thinks they are above average). Therefore it is possible that a user may attempt to change his or her IM IQ by sending an IQ set to the server:</p>
  79. <example caption='Attempting to Set One&apos;s Own IM IQ'><![CDATA[
  80. <iq type='set' id='myiq'>
  81. <query xmlns='jabber:iq:iq'>
  82. <num>143</num>
  83. <desc>genius</desc>
  84. </query>
  85. </iq>
  86. ]]></example>
  87. <p>However, allowing users to change their own IM IQs is unacceptable, since it would make such information unreliable. Therefore, if a server receives such an IQ set, it MUST return a &notallowed; error to the user, and MAY further decrement the user's IM IQ as a result.</p>
  88. <example caption='Server Returns Error to User on Attempted Set'><![CDATA[
  89. <iq type='error' id='myiq'>
  90. <query xmlns='jabber:iq:iq'>
  91. <num>143</num>
  92. <desc>genius</desc>
  93. </query>
  94. <error code='405' type='cancel'>
  95. <not-allowed xmlns='urn:ietf:params:xml:ns:xmpp-stanzas'/>
  96. </error>
  97. </iq>
  98. ]]></example>
  99. </section2>
  100. <section2 topic='Messaging Hints' anchor='hints'>
  101. <p>Even smart people say stupid things, and we are all familiar with the experience of having said something stupid (or just average) and realizing later that one could have said something exceedingly clever. To prevent people from saying stupid things and to help users appear as smart as possible, the mod_iq jabberd module provides hints to users regarding what to say at a given point in a conversation, based on the advanced linguistic analysis technologies described under <link url='#impl'>Implementation Notes</link> below. A user can ask for a hint by sending the complete message to the server itself, wrapped in a &QUERY; element qualified by the 'jabber:iq:iq' namespace. (While it may be argued that this functionality could be provided client-side, thus saving a roundtrip, it is consistent with the Jabber philosophy of "smart servers, dumb clients" as explained in &xep0134;.)</p>
  102. <example caption='Requesting IM IQ Information'><![CDATA[
  103. <iq type='get'
  104. from=''
  105. to=''
  106. id='hint1'>
  107. <query xmlns='jabber:iq:iq'>
  108. <message to=''>
  109. <thread>some-thread-id</thread>
  110. <body>d00d, u r dum -- RTFM, OK?</body>
  111. </message>
  112. </query>
  113. </iq>
  114. ]]></example>
  115. <p>The server then determines a more intelligent message to send and returns the XML character data of the &BODY; element to the user in a &lt;hint/&gt; element.</p>
  116. <example caption='Server Hints at a More Intelligent Message'><![CDATA[
  117. <iq type='result'
  118. from=''
  119. to=''
  120. id='hint1'>
  121. <query xmlns='jabber:iq:iq'>
  122. <hint>
  123. I&apos;ve heard that there&apos;s this thing called the Internet, which
  124. contains incredible amounts of helpful information. Have you considered
  125. using it?
  126. </hint>
  127. </query>
  128. </iq>
  129. ]]></example>
  130. <p>Messages checked with the server before sending SHOULD NOT affect the user's IM IQ computation; however, the server MAY decrement the user's IM IQ more significantly if the user ends up sending the original message rather than the smarter one provided by the server.</p>
  131. </section2>
  132. </section1>
  133. <section1 topic='Implementation Notes' anchor='impl'>
  134. <section2 topic='Intelligence Levels' anchor='impl-levels'>
  135. <p>The mod_iq jabberd module uses somewhat out-of-date terminology for intelligence levels <note>See, for example, D. Wechsler, <cite>The Measurement of Adult Intelligence</cite> (Baltimore: The Williams and Wilkins Company), 1944.</note>, as shown in the following table.</p>
  136. <table caption='Intelligence Ranges and Descriptions'>
  137. <tr>
  138. <th>Number Range</th>
  139. <th>Descriptive Label</th>
  140. </tr>
  141. <tr>
  142. <td>140+</td>
  143. <td>genius</td>
  144. </tr>
  145. <tr>
  146. <td>120-139</td>
  147. <td>very superior</td>
  148. </tr>
  149. <tr>
  150. <td>110-119</td>
  151. <td>superior</td>
  152. </tr>
  153. <tr>
  154. <td>90-109</td>
  155. <td>normal</td>
  156. </tr>
  157. <tr>
  158. <td>80-89</td>
  159. <td>dull</td>
  160. </tr>
  161. <tr>
  162. <td>70-79</td>
  163. <td>borderline deficiency</td>
  164. </tr>
  165. <tr>
  166. <td>50-69</td>
  167. <td>moron</td>
  168. </tr>
  169. <tr>
  170. <td>20-49</td>
  171. <td>imbecile</td>
  172. </tr>
  173. <tr>
  174. <td>0-19</td>
  175. <td>idiot</td>
  176. </tr>
  177. </table>
  178. <p>While once common, these terms are now considered politically incorrect. However, please note that this specification merely provides informational documentation of a protocol historically used within the Jabber community, and is not intended to stereotype individuals in any manner whatsoever. A given server implementation of the 'jabber:iq:iq' protocol MAY substitute more modern ranges and terminology if desired or leave out the descriptive phrases entirely, and a given client implementation MAY rename or disguise the descriptive phrases.</p>
  179. <p>That said, it is true that many people on the Jabber network do act like morons, imbeciles, and even idiots.</p>
  180. </section2>
  181. <section2 topic='Determination of IM IQ' anchor='impl-determination'>
  182. <p>Using the methods described in the next section, the mod_iq jabberd module assigns and dynamically updates a person's IM IQ based on all the messages sent by the user. Upon registration, each user is assigned a baseline IM IQ of 100 ("intelligent until proven an idiot"), unless the user made errors in the registration process or chose an especially stupid password (e.g., "password"), in which case the initially assigned IM IQ could be as low as 70 ("borderline deficiency"). In a manner similar to server-side "karma" ratings, the IM IQ is then modified dynamically based on the semantic value of the user's outbound messages, up to a high of 256 or down to a low of zero (0).</p>
  183. <p>IM IQ is determined based on a user's actual message traffic only, not on other factors such as inane presence status text or the contacts added to the user's roster. While the latter functionality might have been useful, it would violate the rule of not assigning guilt based on association.</p>
  184. </section2>
  185. <section2 topic='Analysis Methods' anchor='impl-analysis'>
  186. <p>The mod_iq jabberd module makes use of several Analytical Language Engine (ALE) technologies for determining the intelligence of specific messages and thus also a user's IM IQ (the average of all messages sent). These technologies include the following:</p>
  187. <dl>
  188. <di><dt>Phrasal Objectification of Realtime Threads (PORT)</dt><dd>This is a parsing technique for breaking conversation threads into meaningful phrases, even across message boundaries.</dd></di>
  189. <di><dt>Bayesian Estimation of Entropic Responses (BEER)</dt><dd>Within information theory, entropy is a measure of the rate of information transfer; this technique uses Bayesian estimation methods to determine whether a given message imparts useful information or not.</dd></di>
  190. <di><dt>Situational Analysis of Kladistic Evolution (SAKE)</dt><dd>Kladistics (also spelled "cladistics"), from the Greek "klados" (meaning "branch"), is the study of grouping things into branches that diverge from a common origin; it is used in biology to study descent from a common ancestor, and also in the study of conversation threads to determine how a conversation would evolve depending on things said (or messages sent) at any point in the conversation flow.</dd></di>
  191. <di><dt>Semantic Correlation and Observation of Truth in Conversation Handling (SCOTCH)</dt><dd>A person may seem intelligent to the casual observer, but his or her messages may actually not provide deep insights or even track reality in a useful or consistent fashion; this technique builds on early semantic web insights to determine the truth value of a given message within the context of a realtime conversation.</dd></di>
  192. <di><dt>Webs of Intelligent Network Endpoints (WINE)</dt><dd>Any given person can engage in conversations with a large number of interlocutors, yet that person's status as an intelligent network endpoint is influenced by reputational factors across the full web of linguistic interactions, not just with any one person; this technique accounts for such reputational effects to paint a complete picture of the person's perceived intelligence across the network.</dd></di>
  193. </dl>
  194. <p>Naturally, because of the powerful and potentially unpredictable effects of these technologies, development of mod_iq was restricted to senior developers on the jabberd team, or at least (for developers in the U.S.) those over the age of 21. <note>See Title 23, Chapter 1, Subchapter 1, Section 158 of the United States federal legal code as enacted by the National Minimum Drinking Age Act of 1984 &lt;<link url=''></link>&gt;.</note></p>
  195. </section2>
  196. </section1>
  197. <section1 topic='Internationalization Considerations' anchor='i18n'>
  198. <p>The descriptive phrases for various intelligence levels SHOULD be localized based on the user's preferred language; however, if the server does not support the 'xml:lang' attribute, this localization MAY be performed by the client.</p>
  199. </section1>
  200. <section1 topic='Security Considerations' anchor='security'>
  201. <p>Most people become somewhat insecure when they realize that in fact they are not as smart as they thought they were; for this reason, querying the server for one's own IM IQ is NOT RECOMMENDED on a regular basis.</p>
  202. </section1>
  203. <section1 topic='IANA Considerations'>
  204. <p>This document requires no interaction with &IANA;.</p>
  205. </section1>
  206. <section1 topic='XMPP Registrar Considerations'>
  207. <p>The &REGISTRAR; shall include the 'jabber:iq:iq' namespace in its registry of protocol namespaces.</p>
  208. </section1>
  209. <section1 topic='XML Schema' anchor='schema'>
  210. <code><![CDATA[
  211. <?xml version='1.0' encoding='UTF-8'?>
  212. <xs:schema
  213. xmlns:xs=''
  214. targetNamespace='jabber:iq:iq'
  215. xmlns='jabber:iq:iq'
  216. elementFormDefault='qualified'>
  217. <xs:import namespace='jabber:client'/>
  218. <xs:annotation>
  219. <xs:documentation>
  220. The protocol documented by this schema is defined in
  221. XEP-0148:
  222. </xs:documentation>
  223. </xs:annotation>
  224. <xs:element name='query'>
  225. <xs:complexType>
  226. <xs:choice xmlns:jabber='jabber:client'>
  227. <xs:sequence>
  228. <xs:element name='num' type='xs:byte'/>
  229. <xs:element name='desc' type='xs:string' minOccurs='0'/>
  230. </xs:sequence>
  231. <xs:element ref='jabber:message'/>
  232. <xs:element name='hint' type='xs:string'/>
  233. </xs:choice>
  234. </xs:complexType>
  235. </xs:element>
  236. </xs:schema>
  237. ]]></code>
  238. </section1>
  239. </xep>