Generic Maps

%ents; ]>

Generic Maps A protocol for transport of generic maps (graphical displays of specific subsets of buddies). &LEGALNOTICE; 0110 Deferred Standards Track Standards JIG None None None Not yet assigned Jiri Komzak j.komzak@open.ac.uk jkk25@jabber.open.ac.uk Martin Dzbor m.dzbor@open.ac.uk md267@jabber.open.ac.uk 0.1 2003-07-28 jk Initial version.

Generic maps provide a way to extending the roster into a general display showing contacts (JIDs) together with further additional information. The further information is provided by the position in the map (and possibly by the dot type - e.g. shape or colour). In addition to showing people belonging to one roster group, it is possible to cluster people, use more detailed inset maps etc. each of these features providing a unique context.

The motivations for this JEP are:

It is faster and easier to find people using a rich graphical view as compared to linear lists/trees
Maps provide easily understandable further information (context) about the contact
Maps show relations among JIDs and give better idea about their distribution in a given space (e.g. geographic region, company, campus)

The requirements for the protocol are:

General definition of projection based on some attribute(s) of particular JIDs
Scaleability - in display size and size of transmitted data

Generic Map is actually XML description of a graphical display, which can then be sent as a part of <message/> or <iq/> packet together with information about how to obtain attributes needed for its display (other resources required).

Example 1 shows a typical message containing simple Generic Map.

Map of our office Cool stuff, I can see you on-line in the map.

http://domain.com/maps/ortho_0.gif ortho_0.gif - map for map1.ygf ]]>

Each map consists of one or more layers. The main purpose of layers is to combine maps and views to deliver information suitable for a particular context, and to offer greater flexibility to the user in respect to customization.

Layers can be defined either inline or by a reference to another map. Each layer has a specified position in the map, a scale and a priority. The maps defined inline contain also projection, underlying image and a list of entities lying inside it (i.e. typically JIDs or clusters of JIDs). The underlying images are sent out of band using the jabber:x:oob namespace or possibly defined in some other way (e.g. xml-based SVG).

The map in Example 1 uses an implicit map projection assuming that attributes x and y are directly the co-ordinates of a particular entity (e.g. buddy1@jabber.org) in the image (ortho_0.gif) expressed in pixels.

A similar map with coordinates specified using geographic latitude + longitude (possibly obtained using Geographic Location Information JEP-0080: Geographic Location Information http://www.jabber.org/jeps/jep-0080.html extension) is shown in Example 2 (only the map tag is shown).

]]>

As can be seen in Example 2, the projection can be specified using any parameters either explicitly set in the item tags or obtained for the particular JID from some other source (e.g. JUD or LDAP).

Another important feature of this proposal is scaleability, which is achieved by grouping the individual JIDs with similar properties (e.g. 'near' locations) into clusters. Cluster is basically a list of constituting entities (JIDs) that share similar values of specified attribute (e.g. JIDs that are co-located in the same town/region/country). The size of clusters may depend on the resolution and intended scale of the map. In the map clusters can be displayed using a distinctive icon.

]]>

The following guidelines may assist the developers of a mapping plug-in in the Jabber clients.

The expression in the <projection/> tag uses values of different attributes specified for the JID either directly in the <map/> tag or elsewhere in the environment.

The image files (maps) are transferred as an extra extension of packet using the filename as a unique id.

The attributes are either specified in the <map/> tag or known in the environment (e.g. presence), but they could be also provided by a subscribed service using Publish-Subscribe JEP-0060: Publish-Subscribe http://www.jabber.org/jeps/jep-0060.html (e.g. GPS or LBS from a mobile operator).

The clustering of items can be specified directly in the map tag or done using a pixel resolution of the display available.

No security features or concerns related to this proposal.

No IANA interaction required.

The Jabber Registrar The Jabber Registrar maintains a list of reserved Jabber namespaces as well as a registry of parameters used in the context of JEPs approved by the JSF. For further information, see http://www.jabber.org/registrar/ will need to register the new namespace of "http://jabber.org/protocol/map".