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-0038.xml 30KB

  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>Icon Styles</title>
  10. <abstract>A protocol for specifying exchangeable styles of emoticons and genicons within Jabber IM clients.</abstract>
  12. <number>0038</number>
  13. <status>Deferred</status>
  14. <type>Standards Track</type>
  15. <sig>Standards</sig>
  16. <dependencies/>
  17. <supersedes/>
  18. <supersededby/>
  19. <shortname>None</shortname>
  20. <author>
  21. <firstname>Adam</firstname>
  22. <surname>Theo</surname>
  23. <email></email>
  24. <jid></jid>
  25. </author>
  26. <revision>
  27. <version>0.5</version>
  28. <date>2003-06-02</date>
  29. <initials>at</initials>
  30. <remark>Bent to public will on using a common object element and enveloping all meta information into a meta element.</remark>
  31. </revision>
  32. <revision>
  33. <version>0.4</version>
  34. <date>2003-03-05</date>
  35. <initials>at</initials>
  36. <remark>Added "format" back in. Refused to simplify to use "object" for everything. Fixed some typos.</remark>
  37. </revision>
  38. <revision>
  39. <version>0.3</version>
  40. <date>2002-11-05</date>
  41. <initials>at</initials>
  42. <remark>Simplified, even though it loses some flexibility. Should be the final version.</remark>
  43. </revision>
  44. <revision>
  45. <version>0.2</version>
  46. <date>2002-07-24</date>
  47. <initials>at</initials>
  48. <remark>Added feedback, still needs serious Schema work</remark>
  49. </revision>
  50. <revision>
  51. <version>0.1</version>
  52. <date>2002-06-28</date>
  53. <initials>at</initials>
  54. <remark>Initial version</remark>
  55. </revision>
  56. </header>
  57. <section1 topic='Introduction'>
  58. <p>This proposal standardizes the use of graphical emoticons and "genicons" in Jabber IM clients to prevent confusion and competing conventions that will soon arise, enabling client developers to spend their energy on more important parts of their projects.</p>
  59. <p><link url="">Emoticons</link> are the text string 'smiley' or 'frowny' faces such as <tt>:-)</tt> and <tt>:-(</tt> that people often use in email or instant messaging to represent emotions. Genicons are a term being coined here to mean non-emotive text pictures (often called '<link url="">ASCII Art</link>') that serve to replace typing the full word or to simply be cute or creative in the conversation.</p>
  60. <p>Many new Internet users demand graphical emoticon and genicon support in their IM clients. We should satisfy their needs if we ever wish to see them use Jabber instead of another IM system.</p>
  61. <p>While traditionally emoticons and genicons have been typed and displayed as text, the recent trend of using graphics, and sometimes sounds, instead of text to represent these pictures will be assumed for purposes of this proposal. Also, the term "icon" will be used in place of "emoticon" and "genicon" for purposes of convenience.</p>
  62. </section1>
  63. <section1 topic='Requirements'>
  64. <p>The following issues must be solved for in this specification.</p>
  65. <ul>
  66. <li><strong>Here and Now</strong>: The convention should not rely on technologies such as feature negotiation or generic pub/sub which do not exist yet in Jabber in order to work properly. The convention should be a "here and now" solution, relying only on the current Jabber protocol.</li>
  67. <li><strong>Meaningful</strong>: The convention for creating the icons must be meaningful to users of clients without icon support, or even users on the other side of transports. Whatever method is used, it should not be cryptic or difficult to understand in text-only mode, in case the user does not have or want the capability to view the icons.</li>
  68. <li><strong>Component Friendly</strong>: In order for gateways, bots, and other "semi-intelligent" components to be able to convert or otherwise use the specification (such as to and from the MSN icon style, or use icons in conversations with Artificially Intelligent bots), a specific list of icons must be possible. Since these bots do not have an intelligent human behind them deciding their every action, they cannot deal with unlimited possibilities.</li>
  69. <li><strong>Protect Privacy</strong>: Sender-defined external data must not be required to properly display the icons because it can be used by the sender to track the user, circumventing their privacy. When the sender can define their own graphics or sounds to be used for the icons, they can use unique URLs and monitor when these unique URLs are accessed. External data may be allowed as long as it is not required for proper use of the icons, but it would be best to leave external data completely out of the system.</li>
  70. <li><strong>Conserve Bandwidth</strong>: The amount of markup used within the messages to define the icons should be kept to a minimum, as well as keeping the media files used for the icons from being transferred over the wire with the messages themselves. These easily consume too much bandwidth, a precious resource to most of the Internet.</li>
  71. <li><strong>Be Passive</strong>: The convention should not force transports or recipients to take any action to properly display the icons. Not only does it put extra strain on the components, but it would also unnecessarily break old clients. Transports and recieving clients may have the option of taking some actions, but they should not be forced to.</li>
  72. <li><strong>Internationalization</strong>: The convention must be inherently international in order to ease adoption of Jabber throughout the world and prevent later growing pains. The use of English must be kept to a minimum, restricted to "meta information" about the icons themselves, and must dynamically allow for non-English language sets.</li>
  73. </ul>
  74. <p>Because icons in Jabber should be easy to use, extensible, and customizable, they will be created using style definition files which can be exchanged between users and supporting clients. The specification will not allow external data, in order to protect the privacy of users, and will not rely on file transfers or directory services in order to not break old clients or components.</p>
  75. </section1>
  76. <section1 topic='Discovery'>
  77. <p>To find out if an entity supports Jabber Icon Styles, look for the feature category of <tt></tt> using <tt>jabber:iq:browse</tt> or <tt></tt>. The same feature category can be used with feature negotiation.</p>
  78. </section1>
  79. <section1 topic='Specification'>
  80. <p>Because icons in Jabber should be easy to use, extensible, and customizable, they will be created using style definition files which can be exchanged between users and supporting clients. The specification will not require external data, in order to protect the privacy of users, and will not rely on file transfers or directory services in order to not break old clients or components. How these icon styles are exchanged - as well as advertised - is out of the scope of this specification. The text strings representing the icons will be sent like any other text (this document doesn't require extra tags or attributes in the messages being sent).</p>
  81. <p>All icons are created by defining each icon then grouping them together into "Icon Definition Files". These files, along with the object files associated with the icons, are called "icon styles". Icon styles may be traded and shared among users of all supporting clients like skins or themes, similar to WinAmp, XMMS, GNOME, and other customizable applications. This creates a platform-independent system, providing a great degree of customization for the user, and allowing client developers to focus on other features.</p>
  82. <section2 topic="Definition File">
  83. <p>Each icon in a style is defined and grouped together in an XML document, the "Icon Definition File". Each definition file for all styles is named "icondef.xml". There is only one such Icon Definition File per style. The W3C Schema for the Icon Definition File plus an example finished Icon Definition File can be found under Schema, below.</p>
  84. </section2>
  85. <section2 topic="Meta Elements">
  86. <p>The meta elements contain information about the Icon Style itself, rather that the individual icons. They are contained within the <tt>&lt;meta&gt;</tt> element, which is directly under the root element. There is one and only one the <tt>&lt;meta&gt;</tt> element.</p>
  87. <ul>
  88. <li><strong>Name</strong>: This is an arbitrary text string (spaces allowed) which is the full name of the Icon Style. Only one name can be included.</li>
  89. <li><strong>Version</strong>: This is an arbitrary text string (no spaces allowed) which is the version number of the Icon Style. Any version format is allowed, but the <tt>major.minor</tt> or <tt>major.minor.trivial</tt> formats are recommended. Only one version can be included.</li>
  90. <li><strong>Description</strong>: This is the full description of the Icon Style. It summarizes the look and types of the icons, and can be used for keywords in searching. This is optional, but recommended.</li>
  91. <li><strong>Author</strong>: This is the full name of the author. Multiple authors are allowed.</li>
  92. <li><strong>Creation</strong>: This is the date of the creation of this version of the Icon Style. The date is in the <link url="">ISO 8601</link> standard format.</li>
  93. <li><strong>Home</strong>: This is the full HTTP web address of the Icon Style's homepage. This is optional.</li>
  94. </ul>
  95. </section2>
  96. <section2 topic="Text Strings">
  97. <p>The <tt>&lt;text/&gt;</tt> element defines what text string(s) are recognized by the client as an icon. There may be multiple <tt>&lt;text/&gt;</tt> elements in an <tt>&lt;icon/&gt;</tt>, such as for different languages or simply for multiple text strings producing the same result (for example: <tt>:-)</tt> and <tt>:)</tt>)</p>
  98. <section3 topic="Internationalization">
  99. <p>Each may have an <tt>xml:lang</tt> attribute, as defined in Section 2.12 in the official <link url="">XML 1.0 reference document</link>. The <tt>xml:lang</tt> attribute allows for two-letter language codes, dialects, and custom "languages" to define foreign IM protocols, for example.</p>
  100. </section3>
  101. <section3 topic="Whitespace">
  102. <p>In order to be more accurate in recognizing text strings intended to be icons from those that are just coincidences in normal conversation, the client should follow the "whitespace rule" of making sure there is some form of whitespace on at least one side of the text string. This is only a guideline; individual clients can implement different rules as needed. A newline and tabs count as whitespace in addition to spaces. This is to make sure that chunks of code and URIs are not accidentally converted into graphical pictures. Also, text strings cannot include newlines or tabs. All characters must be on the same line with only spaces within the string, and extra spaces should not be ignored. This is to make it much easier on text parsers looking for these text strings.</p>
  103. </section3>
  104. <section3 topic="Case Sensitivity">
  105. <p>The text strings must be case sensitive. This is a rule that compliant clients must follow. "Cat" cannot be used in place of "cat" or "CAT". All three are separate text strings, and therefore must have separate <tt>&lt;text/&gt;</tt> elements, although they may of course use the same objects.</p>
  106. </section3>
  107. </section2>
  108. <section2 topic="Objects">
  109. <p>The <tt>&lt;object/&gt;</tt> element defines what multimedia objects are inserted into the displayed message, replacing the text string(s) defined in <tt>&lt;text/&gt;</tt>. An object may be a bitmap graphic, vector graphic, audio clip, rich text formatting rules, or any other media that can be stored in a separate file. The <tt>&lt;object/&gt;</tt> element is identical to <link url="">the OBJECT element used in XHTML 2.0</link>, and the specification used there should be used to govern the <tt>&lt;object/&gt;</tt> element here. Note that because the XHTML 2.0 OBJECT specification is quite complex (although very flexible and future-proof), client developers are encouraged to only implement compliant sub-sets of the OBJECT specification for their clients. There may be one or multiple <tt>&lt;object/&gt;</tt> elements in an <tt>&lt;icon/&gt;</tt>, such as for alternative file formats (such as <tt>
  110. GIF</tt> vs. <tt>PNG</tt>), or multiple objects to use at the same time (such as graphic and sound files).</p>
  111. </section2>
  112. <section2 topic="X Tags">
  113. <p>The <tt>&lt;x/&gt;</tt> element allows any type of extensions to the <tt>icondef.xml</tt> file, such as to specify how the user's nickname can be colored in multi-user chat windows or defining additional data about the style or authors. Each must have an <tt>xmlns</tt> attribute with a namespace that the extension operates under. Multiple <tt>&lt;x/&gt;</tt> elements may be in the <tt>&lt;icon/&gt;</tt> or <tt>&lt;icondef/&gt;</tt> elements. This functionality is optional for clients to support, and clients should ignore all extensions they do not understand.</p>
  114. </section2>
  115. <section2 topic="Hierarchy">
  116. <p>The <tt>icondef.xml</tt> file must all be located in the root directory, which is named after the style and version (example: <tt>./happy_days-1.2</tt> or <tt>./gold_angelic-1.0.0</tt>). There is only one root directory per style. The object files may either be in the root directory as well, or be in sub-directories for categorization and easier maintenance reasons. If sub-directories are used, they must match the URIs used in the <tt>&lt;object/&gt;</tt> element in the <tt>icondef.xml</tt> file.</p>
  117. <example caption="Gold Angelic v1.0.0 Hierarchy Example">
  118. ./gold_angelic-1.0.0
  119. ./gold_angelic-1.0.0/icondef.xml
  120. ./gold_angelic-1.0.0/alert.ogg
  121. ./gold_angelic-1.0.0/red-exclamation-mark.svg
  122. ./gold_angelic-1.0.0/shocked.svg
  123. ./gold_angelic-1.0.0/woman.svg
  124. ./gold_angelic-1.0.0/pngs/happy.png
  125. ./gold_angelic-1.0.0/pngs/sad.png
  126. ./gold_angelic-1.0.0/pngs/man.png
  127. ./gold_angelic-1.0.0/pngs/woman.png
  128. ./gold_angelic-1.0.0/wavs/boohoo.wav
  129. ./gold_angelic-1.0.0/wavs/choir.wav
  130. ./gold_angelic-1.0.0/wavs/alert.wav
  131. </example>
  132. </section2>
  133. <section2 topic="Packaging">
  134. <p>The <tt>icondef.xml</tt> file and all object files must be packaged in the <tt>ZIP</tt> format following the above hierarchy (the directory must exist in the package, with all files in it). The package must have the file extension <tt>.jisp</tt> (Jabber Icon Style Package), and the MIME type <tt>application/vnd.jisp</tt> as defined in the official <link url="">IANA registration</link>. This allows Jabber clients to automatically install icon styles through web browsers. When the client installs the package, it should probably be kept in the archived format, instead of unzipped. This not only saves disk space, but also makes the packages easier to manage and exchange.</p>
  135. </section2>
  136. </section1>
  137. <section1 topic='Implementation Notes'>
  138. <p>Icons styles should be easy to create, distribute, and most importantly, use. The packaging and official MIME type helps with the first steps, but it is ultimately up to the client developers to fully support the specification and make sure it is easy for users to manage.</p>
  139. <section2 topic='Procedure'>
  140. <p>The procedure for using Jabber icons is simple and straightforward.</p>
  141. <ol>
  142. <li>The user installs and turns on ("activates") an icon style (using their client's GUI, most likely) they have received off the Internet or somewhere else.</li>
  143. <li>The user selects the desired icon they wish to include in their message from their client's GUI (a drop-down list of installed icons, for example).</li>
  144. <li>The client translates the selected icon into its main text string equivelent, which is found in the icon's <tt>&lt;text&gt;</tt> element. If there are multiple <tt>&lt;text&gt;</tt> elements, follow the procedure under "Text Strings", below.</li>
  145. <li>The client sends the message with the text string to the intended recipient.</li>
  146. <li>The recipient client receives the message with the text string.</li>
  147. <li>If the recipient has an icon style activated that defines that text string, it is converted into the appropriate object. If there are multiple objects files for each icon, follow the procedure under "Object Files", below. If there are multiple icon styles installed which define that text string, follow the procedure under "Combining Styles", below. If the recipient does not have such an icon activated, then they simply see the text string without any changes.</li>
  148. </ol>
  149. </section2>
  150. <section2 topic='Text Strings'>
  151. <p>Because icons may have multiple text strings associated with them, clients need to be able to figure out which one to use when a user selects the desired icon from their GUI. This is ultimately completely up to the implementation, but here is a suggestion:</p>
  152. <ol>
  153. <li>First look for any text strings that are the same language as what the user is using (if the user is using english, then look for English text strings, ignoring languages like German or Simplified Chinese). Optionally, if the client is smart enough, it can instead look for text strings in the language that the intended recipient is using (using Browse/Disco or simply keeping track of languages used in an ongoing conversation). The language for text strings is found in the <tt>xml:lang</tt> attribute for <tt>&lt;text/&gt;</tt> elements.</li>
  154. <li>If there are no text strings that match the user's language, then look for one that has no defined language.</li>
  155. <li>If there are multiple options even after the above steps, select the one that comes first in the <tt>&lt;icon/&gt;</tt> element.</li>
  156. <li>If there are no text strings that are in the user's language or no language defined at all, then it is probably best for the client to not even display the icon as a choice at all. But if the client still wants to allow it, then simply select the text string of any language that comes first in the <tt>&lt;icon/&gt;</tt> element.</li>
  157. </ol>
  158. </section2>
  159. <section2 topic='Objects'>
  160. <p>Like multiple text strings, icons can have multiple object data files associated with them, and therefore clients also need to be able to figure out which ones to use when a user selects the desired icon from their GUI. Here is a suggestion of how those files can be chosen among multiple options, although this is completely an implementation issue (as with multiple text strings).</p>
  161. <ol>
  162. <li>First look for any of these objects that are of MIME types the client can understand and use. For example, most clients could only use <tt>image/bmp</tt> and maybe <tt>audio/x-wav</tt>, but some newer clients may be able to support <tt>image/png</tt>, <tt>image/svg+xml</tt> and <tt>audio/x-ogg</tt>.</li>
  163. <li>If there are still multiple object MIME types which the client can understand and use, then the client should rank the MIME types it can support, choosing its favorite.</li>
  164. <li>If there are still multiple objects of the same MIME type, then the client should choose the first one in order in the <tt>&lt;icon/&gt;</tt> element.</li>
  165. <li>If there are no files of any MIME type the client can understand, then it should ignore using any objects or even the entire icon.</li>
  166. </ol>
  167. <p>The <link url="">Rules for processing objects</link> in the XHTML 2.0 OBJECT specification may also be of help in coding the procedure of choosing an object to use, especially when it comes to nested and author-preferred objects.</p>
  168. <p>The client should also take note of the file sizes. The client should set (possibly as a user-defined option) the maximum file size in kilobytes for object files. Anything above this amount implies the file will be too big to properly render, and the icon style developer is probably being abusive.</p>
  169. <p>Also, if you are developing an icon style, please make sure the MIME types specified in your <tt>icondef.xml</tt> file are correct. And also make sure that the files you use are reasonable in any byte, pixel, and timelength size. And although any file format can be supported, try to use <tt>BMP</tt>, <tt>PNG</tt>, <tt>SVG</tt>, <tt>WAV</tt>, <tt>OGG</tt> formats because they are open, free, and becoming increasingly supported in developer tools and programming languages.</p>
  170. </section2>
  171. <section2 topic='Combining Styles'>
  172. <p>A client may permit the user to activate multiple icon styles at one time. This would be useful for styles which make use of different text strings, and the user wants them all. The client should force the user to rank the multiple styles for purposes of conflict resolution between icons. The highest ranking style gets preference over lower ranking styles. This ranking doesn't have to be anything more than simply dragging the style names into top-to-bottom rows, with the styles on top being higher ranked than those below.</p>
  173. </section2>
  174. <section2 topic='Core Icons'>
  175. <p>Although any text string can be turned into an icon by defining it in an <tt>icondef.xml</tt> file, it is highly reccomended they either follow traditional ASCII Art (smileys and frownys, for example) or full keywords in simple markup such as double-colons. If you want to design icons, always keep in mind that not every Jabber user uses graphics to "translate" this to something visual, as explained in the "Meaningful" requirement, above. Here is a short list of recommended "core" icons that should be in most definitions, as well as possibly be used by transports:</p>
  176. <ul>
  177. <li><strong>:-)</strong> and <strong>:)</strong> - A smiling face.</li>
  178. <li><strong>:-(</strong> and <strong>:(</strong> - A frowing face.</li>
  179. <li><strong>;-)</strong> and <strong>;)</strong> - A winking smiling face.</li>
  180. <li><strong>:'-(</strong> and <strong>:'(</strong> - A crying face.</li>
  181. <li><strong>>:-(</strong> and <strong>>:(</strong> - An angry face.</li>
  182. <li><strong>:yes:</strong> - A thumbs-up or checkmark.</li>
  183. <li><strong>:no:</strong> - A thumbs-down or a crossmark.</li>
  184. <li><strong>:wait:</strong> - An open hand, palm outstretched.</li>
  185. <li><strong>@->--</strong> and <strong>:rose:</strong> - A rose flower.</li>
  186. <li><strong>:telephone:</strong> - A telephone.</li>
  187. <li><strong>:email:</strong> - An electronic-looking envelope.</li>
  188. <li><strong>:jabber:</strong> - Jabber's lightbulb logo.</li>
  189. <li><strong>:cake:</strong> - A birthday cake.</li>
  190. <li><strong>:kiss:</strong> - A pair of puckered lips.</li>
  191. <li><strong>:heart:</strong> and <strong>:love:</strong> - A heart.</li>
  192. <li><strong>:brokenheart:</strong> - A broken heart.</li>
  193. <li><strong>:music:</strong> - A musical note or instrument.</li>
  194. <li><strong>:beer:</strong> - A beer mug.</li>
  195. <li><strong>:coffee:</strong> - A cup of coffee.</li>
  196. <li><strong>:money:</strong> - A gold coin.</li>
  197. <li><strong>:moon:</strong> - A moon.</li>
  198. <li><strong>:sun:</strong> - A sun.</li>
  199. <li><strong>:star:</strong> - A star.</li>
  200. </ul>
  201. </section2>
  202. </section1>
  203. <section1 topic='Security Considerations'>
  204. <p>There are no security features or concerns related to this proposal.</p>
  205. </section1>
  206. <section1 topic='IANA Considerations'>
  207. <p>The &XSF; shall register and maintain a MIME type and file extension for icon style packages with the IANA. Ones have already been registered by Sebastiaan Deckers (aka 'CBAS') as <tt>application/vnd.jisp</tt> and <tt>.jisp</tt>, respectively. The registration can be found at <link url=""></link>. Sebastiaan's registration shall be considered the official MIME type and file extension of this specification.</p>
  208. <p>Also, this specification uses other MIME types that are maintained by IANA for the object and xml files that are included in the icon style packages.</p>
  209. </section1>
  210. <section1 topic='XMPP Registrar Considerations'>
  211. <p>JANA shall register the namespace <tt></tt> as an official feature category.</p>
  212. <p>Also, JANA may choose to define IM-specific <tt>xml:lang</tt> "language codes" for use within Jabber (in addition to those defined in the XML specification). Such language codes would allow Jabber developers to support icons from MSN, Yahoo, and popular web message programs.</p>
  213. </section1>
  214. <section1 topic='Formal Definition'>
  215. <section2 topic='Schema'>
  216. <code><![CDATA[
  217. <?xml version='1.0' encoding='UTF-8'?>
  218. <xs:schema xmlns:xs="">
  219. <xs:element name="icondef">
  220. <xs:complexType>
  221. <xs:sequence>
  222. <xs:complexType>
  223. <xs:sequence>
  224. <xs:element name="name" type="xs:string"/>
  225. <xs:element name="version" type="xs:string"/>
  226. <xs:element name="description" type="xs:string"/>
  227. <xs:element name="author" type="xs:string" maxOccurs="unbounded">
  228. <xs:complexType>
  229. <xs:attribute name="jid" type="xs:string" use="optional"/>
  230. </xs:complexType>
  231. </xs:element>
  232. <xs:element name="creation" type="xs:date"/>
  233. </xs:sequence>
  234. </xs:complexType>
  235. <xs:element name="icon" minOccurs="1" maxOccurs="unbounded">
  236. <xs:complexType>
  237. <xs:sequence>
  238. <xs:element name="text" type="xs:string" minOccurs="1" maxOccurs="unbounded">
  239. <xs:complexType>
  240. <xs:attribute name="xml:lang" type="xs:language" use="optional"/>
  241. </xs:complexType>
  242. </xs:element>
  243. <xs:element name="object" type="xs:string" minOccurs="1" maxOccurs="unbounded">
  244. <xs:complexType>
  245. <xs:attribute name="mime" type="xs:string" use="required"/>
  246. </xs:complexType>
  247. </xs:element>
  248. <xs:element name="x" type="xs:string" minOccurs="0" maxOccurs="unbounded">
  249. <xs:complexType>
  250. <xs:attribute name="xmlns" type="xs:anyURI" use="required"/>
  251. </xs:complexType>
  252. </xs:element>
  253. </xs:sequence>
  254. </xs:complexType>
  255. </xs:element>
  256. <xs:element name="x" type="xs:string" minOccurs="0" maxOccurs="unbounded">
  257. <xs:complexType>
  258. <xs:attribute name="xmlns" type="xs:anyURI" use="required"/>
  259. </xs:complexType>
  260. </xs:element>
  261. </xs:sequence>
  262. </xs:complexType>
  263. </xs:element>
  264. </xs:schema>
  265. ]]></code>
  266. </section2>
  267. <section2 topic="icondef.xml file example">
  268. <code><![CDATA[
  269. <?xml version='1.0' encoding='UTF-8'?>
  270. <icondef>
  271. <meta>
  272. <name>Gold Angelic</name>
  273. <version>1.0.0</version>
  274. <description>Angelic faces and themes with gold highlights.</description>
  275. <author jid="">Adam Theo</author>
  276. <author jid="">Sebastiaan Deckers</author>
  277. <author jid="">Mattias Campe</author>
  278. <creation>2002-10-31</creation>
  279. <home></home>
  280. </meta>
  281. <icon>
  282. <text>:-)</text>
  283. <text>:)</text>
  284. <object mime="image/png">happy.png</object>
  285. <object mime="audio/x-wav">choir.wav</object>
  286. </icon>
  287. <icon>
  288. <text>:-(</text>
  289. <text>:(</text>
  290. <object mime="image/png">sad.png</object>
  291. <object mime="audio/x-wav">boohoo.wav</object>
  292. </icon>
  293. <icon>
  294. <text>:-O</text>
  295. <text>:O</text>
  296. <object mime="image/svg+xml">shocked.svg</object>
  297. </icon>
  298. <icon>
  299. <text xml:lang="en">::man::</text>
  300. <text xml:lang="de">::mann::</text>
  301. <text xml:lang="cs">::muz::</text>
  302. <text xml:lang="x-msn">(z)</text>
  303. <object mime="image/png">man.png</object>
  304. </icon>
  305. <icon>
  306. <text xml:lang="en">::woman::</text>
  307. <text xml:lang="x-msn">(x)</text>
  308. <object mime="image/svg+xml">woman.svg</object>
  309. <object mime="image/png">woman.png</object>
  310. </icon>
  311. <icon>
  312. <text xml:lang="en">::alert::</text>
  313. <object mime="image/svg+xml">red-exclamation-mark.svg</object>
  314. <object mime="audio/x-ogg">alert.ogg</object>
  315. <object mime="audio/x-wav">alert.wav</object>
  316. </icon>
  317. </icondef>
  318. ]]></code>
  319. </section2>
  320. </section1>
  321. <section1 topic='Future Considerations'>
  322. <ol>
  323. <li>This proposes a standard, simple, plaintext-based icon convention. It does not attempt to create a powerful XML-based convention wherein XML tags are used to extensibly represent the icons. However, this proposal isn't exclusive, and does not prevent such an XML-based convention from being created at a later date. It may also be possible to build such an extensible XML-based convention on top of this plaintext one.</li>
  324. <li>The Icon Styles that the sender used to create the message may be of use to the recipient. A separate specification can be developed for the transferring of the name and version of the Icon Styles used by the sender. The recipient's client may then be smart enough to automatically use the same icons as the sender intended, possibly even fetching and downloading the icon styles as needed. This would likely require directory services, so has not been included in this proposal.</li>
  325. <li>The functionality of the <tt>icondef.xml</tt> files may be useful for variable text strings. Text strings that may change from session to session, such as the user's nickname in a multi-user chat. A set of variables could be defined that represent these variable datas, therefore allowing them to be manipulated in the same way set text strings are.</li>
  326. <li>This convention may be adopted beyond the scope of Jabber into web browsers, email clients, and Wiki sites. There is great potential for a generalized, exchangeable convention for emoticons and genicons.</li>
  327. <li>A "SVG Transport" may be created to enable clients to send <tt>SVG</tt> icons to it and get back icons in another format of their choice, such as <tt>PNG</tt> or <tt>JPG</tt>. This would speed up the adoption of <tt>SVG</tt> within Jabber greatly.</li>
  328. <li>An online Web- (or even Jabber-) based editor to create icon style packages from the individual components would be a great tool for developers. This would be a great project for <link url="">JabberStudio</link> or even the <link url="">Ransom model</link>.</li>
  329. </ol>
  330. </section1>
  331. </xep>