[Paper Review] A distributed editing environment for XML documents

Claude Pasquier, Laurent Théry|ArXiv.org|Feb 18, 2009

Advanced Database Systems and Queries3 references3 citations

TL;DR

This paper presents a distributed XML editing system where user interactions—selections and modifications—are serialized as compact XML messages and sent to a central server. The server applies changes to the abstract document tree and broadcasts updates, enabling efficient, asynchronous collaboration over HTTP with minimal network overhead and support for multiple clients with varying connection speeds.

ABSTRACT

XML is based on two essential aspects: the modelization of data in a tree like structure and the separation between the information itself and the way it is displayed. XML structures are easily serializable. The separation between an abstract representation and one or several views on it allows the elaboration of specialized interfaces to visualize or modify data. A lot of developments were made to interact with XML data but the use of these applications over the Internet is just starting. This paper presents a prototype of a distributed editing environment over the Internet. The key point of our system is the way user interactions are handled. Selections and modifications made by a user are not directly reflected on the concrete view, they are serialized in XML and transmitted to a server which applies them to the document and broadcasts updates to the views. This organization has several advantages. XML documents coding selection and modification operations are usually smaller than the edited document and can be directly processed with a transformation engine which can adapt them to different representations. In addition, several selections or modifications can be combined into an unique XML document. This allows one to update multiple views with different frequencies and fits the requirement of an asynchronous communication mode like HTTP.

Motivation & Objective

• To enable efficient, collaborative editing of XML documents over the Internet using asynchronous communication protocols like HTTP.
• To minimize network traffic by transmitting only user interaction actions (selections and modifications) rather than full document copies.
• To support multiple clients with varying connection speeds by decoupling the abstract document model from concrete views.
• To maintain bidirectional synchronization between source and transformed views using a declarative transformation language (XPPML).
• To reduce client-side complexity by centralizing processing logic on the server, making the system suitable for resource-constrained devices.

Proposed method

• User interactions such as selections and modifications are serialized into compact XML documents representing actions on the abstract document tree.
• The system uses an IntegerPath (ipath) mechanism to unambiguously identify nodes via relative positions from the root, avoiding ambiguity in path expressions.
• Selections are managed via symbolic names and structured paths (spath), allowing multiple selections to be tracked and synchronized across clients.
• The server applies actions to the central abstract document tree and broadcasts updates using a transformation engine based on XPPML, which maps changes to different views.
• Changes are transmitted as incremental updates (e.g., move, change, extend selection), enabling efficient synchronization and reducing bandwidth usage.
• Clients receive updates via commit requests and reflect changes in their local views, re-evaluating selections after modifications.

Experimental results

Research questions

• RQ1 How can XML document editing be efficiently supported over asynchronous, low-bandwidth networks like HTTP?
• RQ2 Can user interactions be abstracted as compact, serializable actions to reduce network overhead in collaborative editing?
• RQ3 How can bidirectional synchronization between abstract document trees and multiple rendered views be maintained?
• RQ4 What architectural model allows minimal client-side software while maintaining full editing functionality?
• RQ5 How can concurrent editing and varying client capabilities be supported in a scalable, distributed XML editing environment?

Key findings

• The system reduces network traffic significantly by transmitting only action messages (e.g., selection, modification) rather than full document copies, with action documents typically smaller than the edited document.
• The use of XPPML for bidirectional transformation enables efficient adaptation of changes to different views, supporting multiple representations with different update frequencies.
• The architecture allows multiple clients with diverse connection speeds to collaborate in real time, with changes reflected quickly after server-side processing.
• Performance bottlenecks were observed only during the initial transmission of large formatted documents, which the system addresses by exploring partial transmission (e.g., visible subtrees).
• The system successfully supports the distributed editing of large, structured documents such as Java programs, with low-latency processing of user actions.
• The approach is extensible to support text field editing by integrating DOM-level 2 range concepts for future support of inline text selections.