Portable Import/Export Format for XMPP-IM Servers

%ents; ]>

Portable Import/Export Format for XMPP-IM Servers This document specifies a file format for importing and exporting user data to and from XMPP-IM servers. &LEGALNOTICE; 0227 Proposed Standards Track Standards Council XMPP IM XEP-0049 XEP-0054 TO BE ASSIGNED Magnus Henoch henoch@dtek.chalmers.se legoscia@jabber.cd.chalmers.se 0.2 2007-12-13 mh

Use XInclude.

0.1 2007-08-08 psa

Initial published version.

0.0.1 2007-07-27 mh

Initial version.

Different implementations of XMPP-IM servers store user data in various ways, and many implementations have more than one storage format. This leads to problems when a server administrator wants to switch to another implementation or storage format -- the implementation is as likely as not to have an import mechanism that can read the user data in its current form. This document attempts to solve that problem by defining a common file format for import and export of user data in XMPP-IM servers.

The following constraints are imposed on this standard:

The file format is XML-based.

XMPP-IM servers already have tools to process XML data. This also allows extension of the format using namespaces. Furthermore, some of the data that needs to be stored is by definition already in XML form.
The data layout is flexible.

The data is contained in a single XML document; however, it can be split into several files using &w3xinclude;.
All user data is stored, but no server configuration data.

User data has similar form throughout the XMPP world, but server configuration is implementation-specific. Therefore this specification does not attempt to transfer any aspects of the server configuration from one server to another.

Furthermore, the contents of MUC, Pubsub and other services are out of scope for this specification.
Multiple virtual hosts are supported.

Many server implementations can serve several hostnames in a single server instance. Thus this specification allows storing data from several virtual hosts.

Exporting server.

The XMPP-IM server writing its user data to files, following this specification.
Importing server.

The XMPP-IM server reading data from such files.

Data is contained in an XML document, whose root element is <server-data/> qualified by the 'http://www.xmpp.org/extensions/xep-0227.html#ns' namespace &NSNOTE;.

[ ... ] ]]>

At any point in the file, an exporting server may put elements qualified by a namespace not mentioned in this specification. The exported data SHOULD be meaningful without the extensions. An importing server that encounters a namespace that it doesn't understand, or otherwise is unable to import all given data, SHOULD ignore the unknown data, SHOULD notify the operator, and MAY offer to terminate the process.

At any point in the file, an exporting server may put an XInclude <include/> element; see Use of XInclude.

The child elements of the <server-data/> elements are <host/> elements. Each <host/> element describes a virtual host, and has a 'jid' attribute that contains its JID.

An importing server MAY automatically adjust its list of virtual hosts to fit the ones present in the data being imported. If it does not, it SHOULD notify the operator about any mismatch.

[ ... ] [ ... ] ]]>

Each user is represented by a <user/> element under the <host/> element. The <user/> element MUST have a 'name' attribute, which contains the node part of the user's JID, and SHOULD have a 'password' attribute, which contains the user's password.

[ ... ] [ ... ] ]]>

Each <user/> element SHOULD contain the user's roster in the form of a <query/> element qualified by the 'jabber:iq:roster' namespace. This element contains the user's roster in the same format as when retrieving the roster from the server, as described in section 7.3 of &xmppim;.

Friends ]]>

If the exporting server stores messages received while the user was offline, it SHOULD include an <offline-messages/> element as a child of the <user/> element. This element contains all the stored messages to the user, if any, as <message/> elements qualified by the 'jabber:client' namespace, starting with the oldest.

Neither, fair saint, if either thee dislike. Offline Storage

]]>

Private data stored by the server as specified in &xep0049; is represented in this format by including a <query/> element qualified by the 'jabber:iq:private' namespace as a child of the <user/> element. This <query/> element in turn contains all elements saved in private XML storage.

Hamlet ]]>

By &xep0054;, users can store vCards on the server. In this specification, vCards are child elements of the <user/> element, namely a <vCard/> element qualified by the 'vcard-temp' namespace.

Juliet Capulet ]]>

Privacy lists, as specified in &xep0016;, are represented in this format by including a <query/> element qualified by the 'jabber:iq:privacy' namespace as a child of the <user/> element. This element should contain all privacy lists associated with the user. A default privacy list, if set, is specified by including a <default/> element as a child of the <query/> element.

]]>

Each <user/> element SHOULD contain pending incoming subscription requests associated with the user's account. Incoming subscription requests are represented by including <presence/> elements qualified by the 'jabber:client' namespace with the 'type' attribute set to a value of 'subscribe' as children of the <user/> element.

Romeo ]]>

An exporting server may split the data in several files by using the XInclude <include/> element. An importing server MUST support <include/> elements having an 'href' attribute containing a relative URI, having no 'parse' attribute, and having no 'xpointer' attribute; it MAY support other kinds of <include/> elements. An exporting server SHOULD NOT include and an importing server SHOULD NOT process <include/> elements which are decendents, but not children of the <user/> element (since these may be part of user data).

If an exporting server chooses to split the data into several files, it SHOULD use the following scheme:

The main file contains the <server-data/> element, which contains nothing but one <include/> element for each host. The file included for a certain host is placed in the same directory as the main file, and is named by appending ".xml" to the JID of the host, e.g. "capulet.com.xml".

]]>

Each host file contains a <host/> element, which contains nothing but one <include/> element for each user of the host. The file included for a certain user is placed in a subdirectory whose name is the JID of the host, and is named by appending ".xml" to the node part of the user's JID, e.g. "capulet.com/juliet.xml".

]]>

Each user file contains a <user/> element, and includes all data relating to that user.

Friends Juliet Capulet

Neither, fair saint, if either thee dislike. Offline Storage

]]>

The definition of JIDs ensures that this generates valid file names on traditional Unix-like file systems, except for possible length constraints. However, various constraints may force an exporting server to alter this scheme. In any case, the importing server MUST NOT rely on this layout, but MUST do proper XInclude processing.

Exported data files are to be handled with care, since they contain data that users expect to be protected, in particular passwords. An exporting server SHOULD make sure that the generated file is not accessible to unauthorized persons, e.g. by enforcing strict file permissions.

XInclude <include/> elements which are indirect descendents of the <user/> element SHOULD be treated as opaque user data, and SHOULD NOT be processed.

This document requires no interaction with the Internet Assigned Numbers Authority (IANA).

Until this specification advances to a status of Draft, its associated namespace shall be "http://www.xmpp.org/extensions/xep-0227.html#ns"; upon advancement of this specification, the ®ISTRAR; shall issue a permanent namespace in accordance with the process defined in Section 4 of &xep0053;.

]]>