![]() The proper expression for all new implementations supporting this specification is to express the type information as attributes on a generic item element. Historically each category was used as the name of an element, and the type was an attribute, such as. Nodes of this category are Jabber users, typically implementing enough of the 'jabber:client' namespace to be compliant.Ī standard or fully-featured Jabber client compliant with the 'jabber:client' namespaceĪ portable device implementing some of the 'jabber:client' namespace It is assumed that this node has service/* children IRC gateway (note: this enables IRC users to connect to Jabber)Ī Jabber server which conforms to the specification for the 'jabber:client' namespaceĪ list of servers. The 'jabber:iq:register' namespace can be used to gain access to such networks, and the 'jabber:iq:search' namespace may also be available. Nodes of this category provide a link to another Instant Messaging network or messaging gateway. ![]() Other language to language (using standard language codes) Keyword-based lookup services (search engines, etc.) Stock market information by symbol (ticker) Log messages (usually presented in a scrolling GUI)Īlerts and warnings (usually presented as popup messages) Recognize different sources of headlines, GUI hints Private, dynamically-generated conference rooms IRC rooms (note: this enables Jabber users to connect to Internet Relay Chat rooms) Nodes of this category provide multi-user chat facilities (a.k.a. Specific applications running as a resource on a conversations The following categories and types are proposed as the canonical list for the purpose of JID-Types: Table 1: Official List of JID-Type Categories and Types ¶ Category A JID-Type, once discovered, is to be used in the same way that a mime-type would be for a file, to alter the user interface representing that JID or provide alternative functionality for interacting with it (either automatically or driven by user interaction). Many programmers are comfortable with the concept of identifying file types by mime-types, which use the format "category/type". ![]() One of the concepts in browsing which helps to extend the interaction between JIDs is a "JID-Type", a simple heirarchy for identifying the role of any JabberID that is similar to the mime-type format. Note well that implementors are encouraged to implement Service Discovery (XEP-0030) instead of Jabber Browsing. We need a better way to structure and manage this culture of multi-namespace JID stew. Some JIDs are parents (such as transports), and often many JIDs have relationships with other JIDs (such as a user to their resources, a server to its services, etc.). Every JabberID (JID) is a node that can be interacted with via messages, presence, and special purpose IQ namespaces. The Jabber world is a diverse place, with lots of services, transports, software agents, users, groupchat rooms, translators, headline tickers, and just about anything that might interact on a real-time basis using conversational messages or presence.
0 Comments
Leave a Reply. |