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-0088.xml 8.5KB

  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>Client Webtabs</title>
  10. <abstract>A protocol for displaying web-based tabs in clients.</abstract>
  12. <number>0088</number>
  13. <status>Deferred</status>
  14. <type>Informational</type>
  15. <sig>Standards</sig>
  16. <dependencies>
  17. <spec>XMPP Core</spec>
  18. <spec>XEP-0030</spec>
  19. <spec>XEP-0049</spec>
  20. </dependencies>
  21. <supersedes/>
  22. <supersededby/>
  23. <shortname>webtab</shortname>
  24. <author>
  25. <firstname>Richard</firstname>
  26. <surname>Dobson</surname>
  27. <email></email>
  28. <jid></jid>
  29. </author>
  30. <revision>
  31. <version>0.4</version>
  32. <date>2004-03-14</date>
  33. <initials>red</initials>
  34. <remark>Added Terminology section and associated alterations and added clarification about what the webtabs are.</remark>
  35. </revision>
  36. <revision>
  37. <version>0.3</version>
  38. <date>2003-09-30</date>
  39. <initials>red</initials>
  40. <remark>Moved service discovery to top of use cases, added option for separate webtab provider and added reference to XEP-0101.</remark>
  41. </revision>
  42. <revision>
  43. <version>0.2</version>
  44. <date>2003-05-16</date>
  45. <initials>red</initials>
  46. <remark>Clean ups.</remark>
  47. </revision>
  48. <revision>
  49. <version>0.1</version>
  50. <date>2003-03-02</date>
  51. <initials>red</initials>
  52. <remark>Initial version.</remark>
  53. </revision>
  54. </header>
  55. <section1 topic='Introduction'>
  56. <p>Webtabs are a way for servers to specify a number to web pages which can be used in clients and displayed like the web-based services in Yahoo Messenger, MSN Messenger and JIM. This enables a server administrator to easily create services for Jabber clients and also help to integrate Jabber clients with existing web-based applications.</p>
  57. </section1>
  58. <section1 topic='Requirements'>
  59. <p>The motivations for this document are:</p>
  60. <ul>
  61. <li>To enable servers to specify a selection of web-based services for use in a client.</li>
  62. <li>To allow easy integration with existing web-based systems.</li>
  63. <li>To give more value to people's Jabber services over another's.</li>
  64. <li>To allow the creation of virtually limitless web-based services for Jabber clients without clients needing to be specifically coded to support that service.</li>
  65. </ul>
  66. </section1>
  67. <section1 topic='Use Cases'>
  68. <section2 topic='Service Discovery'>
  69. <p>&xep0030; SHALL be used for discovering support for webtabs on servers.</p>
  70. <example caption='Disco info response containing support for webtabs'><![CDATA[
  71. <iq
  72. type='result'
  73. from=''
  74. to='user@domain/resource'
  75. id='disco1'>
  76. <query xmlns=''>
  77. <feature var=''/>
  78. </query>
  79. </iq>]]></example>
  80. <p>It is RECOMMENDED that the jabber server itself (JSM in jabberd) serves the webtab list, but if desired by the server implementor they MAY be served by a separate host/component.</p>
  81. <example caption='Separate webtab host specified by server'><![CDATA[
  82. <iq
  83. type='result'
  84. from=''
  85. to='user@domain/resource'
  86. id='disco1'>
  87. <query xmlns=''>
  88. <item
  89. jid=''
  90. name='Webtab Provider'/>
  91. </query>
  92. </iq>
  93. <iq
  94. type='result'
  95. from=''
  96. to='user@domain/resource'
  97. id='disco1'>
  98. <query xmlns=''>
  99. <feature var=''/>
  100. </query>
  101. </iq>]]></example>
  102. </section2>
  103. <section2 topic='Retrieving list of web tabs'>
  104. <p>The list of available web tabs is retrieved using the following protocol:</p>
  105. <example caption='Request for list of webtabs available on a server'><![CDATA[
  106. <iq
  107. to=''
  108. type='get'
  109. id='webtab1'>
  110. <query xmlns=''/>
  111. </iq>]]></example>
  112. <example caption='Response from server listing the available webtabs'><![CDATA[
  113. <iq
  114. to=''
  115. from=''
  116. type='result'
  117. id='webtab1'>
  118. <query xmlns=''>
  119. <webtab type='email' id='em' name='Webmail'>
  121. </webtab>
  122. <webtab type='bookmark' id='bk' name='Bookmarks'>
  124. </webtab>
  125. <webtab type='calendar' id='cal' name='Calendar'>
  127. </webtab>
  128. <webtab type='news' id='nws' name='BBC News'>
  130. </webtab>
  131. </query>
  132. </iq>]]></example>
  133. <p>The webtab contains CDATA which is the URL of the webtab, the webtab is an HTML page retrieved from an HTTP server using a standard browser which you embed into your client UI using a technique such as the IWebBrowser2 control interface on windows which allows you to embed either the IE or Gecko engines depending on what you have installed, this data is REQUIRED.</p>
  134. <p>The "type" attribute tells the client what the service being provided is, this allows a client to display icons on the tabs to represent them, handling of the type in clients is OPTIONAL, inclusion of this attribute is REQUIRED (See "XMPP Registrar Considerations" for examples of values for this attribute).</p>
  135. <p>The "name" attribute is the offical name of a particular service this can be displayed as the tab name, this attribute is REQUIRED.</p>
  136. <p>The "id" attribute is a unique identifier for a service which you can use to refer to it later, used for when using private storage to store a preference to which tabs should be visible, this attribute is REQUIRED.</p>
  137. </section2>
  138. <section2 topic='Private storage of preferences'>
  139. <p>&xep0049; SHALL be used for storing webtab preferences.</p>
  140. <example caption='Request for current webtab preferences'><![CDATA[
  141. <iq
  142. to=''
  143. type='get'
  144. id='prefs1'>
  145. <query xmlns='jabber:iq:private'>
  146. <prefs xmlns="webtab:prefs"/>
  147. </query>
  148. </iq>]]></example>
  149. <example caption='Response with webtab preferences'><![CDATA[
  150. <iq
  151. to=''
  152. from=''
  153. type='result'
  154. id='prefs1'>
  155. <query xmlns='jabber:iq:private'>
  156. <prefs xmlns='webtab:prefs'>
  157. <webtab id='em' visible='true'/>
  158. <webtab id='bk' visible='false'/>
  159. <webtab id='cal' visible='true'/>
  160. </prefs>
  161. </query>
  162. </iq>]]></example>
  163. <p>The "id" attribute matches the "id" attribute from the list of webtabs, this attribute is used to match these preferences to the webtab in question, this attribute is REQUIRED.</p>
  164. <p>The "visible" attribute tells the client that a tab SHOULD or SHOULD NOT be hidden, a client SHOULD provide an interface for managing the visibility of the tabs and updating the preferences appropriately, this attribute is REQUIRED.</p>
  165. </section2>
  166. <section2 topic='Service authentication'>
  167. <p>It is RECOMMENDED that a mechanism such as &xep0101; be used for automatic service authentication.</p>
  168. </section2>
  169. </section1>
  170. <section1 topic='Implementation Notes'>
  171. <p>The following guidelines may assist client developers.</p>
  172. <ul>
  173. <li>Use the "type" attribute as a way of determining what services a webtab provides, you can then use this to possibly display appropriate icons to represent the webtab in the client UI.</li>
  174. <li>MUST use the "name" attribute when you have to refer to a webtab by name.</li>
  175. <li>MUST use the private storage specification provided to store information about which tabs SHOULD be visible.</li>
  176. </ul>
  177. </section1>
  178. <section1 topic='Security Considerations'>
  179. <p>It is recommended that XEP-0101 be used to provide transparent authentication of the webtabs.</p>
  180. </section1>
  181. <section1 topic='IANA Considerations'>
  182. <p>No IANA interaction required.</p>
  183. </section1>
  184. <section1 topic='XMPP Registrar Considerations'>
  185. <p>The &REGISTRAR; will need to register the new namespace of "" and possibly the list of offical types will need to be managed too.</p>
  186. <table caption='Possible types for webtabs'>
  187. <tr>
  188. <th>Type</th>
  189. <th>Purpose</th>
  190. </tr>
  191. <tr>
  192. <td>email</td>
  193. <td>Web based email</td>
  194. </tr>
  195. <tr>
  196. <td>calendar</td>
  197. <td>Web based calendar</td>
  198. </tr>
  199. <tr>
  200. <td>bookmark</td>
  201. <td>Web based bookmark management service</td>
  202. </tr>
  203. <tr>
  204. <td>news</td>
  205. <td>General news headlines</td>
  206. </tr>
  207. <tr>
  208. <td>news/sport</td>
  209. <td>Sport headlines</td>
  210. </tr>
  211. </table>
  212. </section1>
  213. </xep>