Jabber


Compendium can send nodes to a Jabber instant messaging client, by ‘masquerading’ as as a Jabber client. The following assumes that you have registered an account on a Jabber server (eg. www.jabber.org), and created a Contacts List. The contacts list will become the menu of options on the 'Send To Jabber' menus described below.

After Opening a Jabber Connection, you will find that three menu options for sending messages to Jabber become available to you. The first is on The File Menu, see figure 1 below.


Figure 1. The' Send to Jabber' menu from the File Menu


The second is on The Node Right-Click Menu, see figure 2 below:


Figure 2. The 'Send To Jabber' menu from the Node Right-Click Menu


The third is on The White-Space Right-Click Menu, see figure 3 below:


Figure 3. The 'Send To Jabber' menu from


When using either the File menu option or the white-space right-click menu option, all selected nodes in the current view will be sent to the Jabber account you select from the 'Sent To Jabber' menu. If you use the node right-click menu option, only that node is sent to the Jabber account you select. See figure 4, below for an example of a Compendium node arriving in a Jabber client message window.


Figure 4. Node sent from Compendium arriving in a Jabber client message window


A Jabber client can also send messages to Compendium by replying to a received message, or sending a message to a specific Jabber client account that a Compendium user can then connect to inside Compendium. Compendium must have an open Jabber connection to the appropriate account to receive messages. Jabber messages sent to Compendium can be prefixed with certain symbols so that they can be interpreted as specific node types. The prefixes for Compendium node types are:


Node Type

Description

Prefix at start of Jabber message

Question Node Question Node

This represents a Question or Issue for discussion.

[?], [I], [Q]

Answer Node Answer Node

The represents an Answer or Position, often in response to a question or issue.

[!], [A], [P]

Map Node Map Node

This represents a map, which is a container for other nodes and links.

This can be used to:
- create a 'picture' of the relationships between ideas;
- group questions and ideas together in meaningful clusters;
- create associative links between nodes.

[M]

List Node List Node

This represents a list, which is a container for other nodes.

This can be used to create a sortable list of nodes, which will usually be a collection of nodes that don't need to be linked with each other (associative links).

[L]

Pro Node Pro Node

This represents a response in favour of an answer or position.

[+]

Con Node Con Node

This represents a response against an answer or position.

[-]

Reference Node Reference Node

This represents a link to some additional, external reference material, which can be in the form of a web link or Word document etc.

These nodes can also be linked to images, which will then be scaled and used instead of the usual reference node icon.

For further information see Reference Nodes

[R]

Note Node Note Node

This represents some non-specific, additional comment or notation, often about a node or the current view.

[N]

Decision Node Decision Node

This represents a decision reached, usually from an answer or position about a question or issue.

[D]

Argument Node Argument Node

This represents a general argument, usually in response to an answer or position.

[U]



Figure 5 below, shows a Jabber message arriving in a map. In this example, the message would have been prefixed with a 'Con Node' prefix, as can be seen from the icon displayed in the message box.


Figure 5. Message sent from a Jabber client arriving in a Compendium map


The Compendium user can then turn the Jabber message into an actual node by pressing the 'Add To Map' button. This will create a new node in the current map, of the specified node type, with the label being the Jabber message. See figure 6, below. Note that the sender's name is recorded in the first detail page of the new node.


Figure 6. Message sent from a Jabber client converted to a node.


For further information on Jabber please see the jabber.org website.