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.
The motivations for this document are:
Service Discovery (XEP-0030)
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.
The list of available web tabs is retrieved using the following protocol:
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.
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).
The "name" attribute is the offical name of a particular service this can be displayed as the tab name, this attribute is REQUIRED.
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.
Private XML Storage (XEP-0049)
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.
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.
It is RECOMMENDED that a mechanism such as HTTP Authentication using Jabber Tickets (XEP-0101)
The following guidelines may assist client developers.
It is recommended that XEP-0101 be used to provide transparent authentication of the webtabs.
No IANA interaction required.
The XMPP Registrar
Type | Purpose |
---|---|
Web based email | |
calendar | Web based calendar |
bookmark | Web based bookmark management service |
news | General news headlines |
news/sport | Sport headlines |