From 0902eb05b0fef07c4e2732faff3caa0bfca80a58 Mon Sep 17 00:00:00 2001 From: Peter Saint-Andre Date: Wed, 22 Aug 2007 20:04:54 +0000 Subject: [PATCH] initial version git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@1180 4b5297f7-1745-476d-ba37-a9c6900126ab --- xep-0228.xml | 117 +++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 117 insertions(+) create mode 100644 xep-0228.xml diff --git a/xep-0228.xml b/xep-0228.xml new file mode 100644 index 00000000..fcdc7f47 --- /dev/null +++ b/xep-0228.xml @@ -0,0 +1,117 @@ + + +%ents; +]> + + +
+ Requirements for Shared Editing + This document defines requirements for the design of XMPP-based shared editing protocols. + &LEGALNOTICE; + 0228 + Experimental + Standards Track + Standards + Council + + XMPP Core + + + + N/A + &stpeter; + + 0.1 + 2007-08-22 + psa +

First draft.

 + +
+ +

Shared editing applications such as whiteboarding have been developed usign XMPP, but there is no general editing and synchronization protocol that can be used by such applications. This document attempts to define the requirements for such a protocol so that work can proceed on protocol development.

+ + + +
    +

  1. The underlying protocol shall be designed for synchronization of XML document instances between entities that communicate via XMPP.

    2. +

  2. All parties to a shared XML editing session must have the same representation of the XML document after all synchronization messages have been processed.

    3. +

  3. It should be possible to use the protocol for multiple application types; examples include but are not limited to whiteboarding using &w3svg;, editing of &w3xhtml; documents, and &xep0204;.

    4. +

  4. There is no requirement to synchronize non-XML data.

    5. +

  5. It must be possible to synchronize XML document instances either between two entities or among more than two entities.

    6. +

  6. The protocol should not (unduly) limit the number of parties to a shared XML editing session.

    7. +

  7. The protocol should be as lightweight as possible in order to minimize bandwidth consumption.

    8. +

  8. Certain applications may need to handle particular features of the XML syntax for that application type (e.g., layers in SVG or pages in XHTML); the protocol must not forbid such specialized semantics.

    9. +
+ + +
    +

  1. It must be possible to use the protocol "directly" between two entities without assistance from intermediaries, either via an XMPP server (&xmppcore;) or in serverless mode (&xep0174;).

    2. +

  2. It must be possible to use the protocol through a &xep0045; room.

    3. +

  3. It should be possible to use the protocol with a specialized synchronization component attached to an XMPP server.

    4. +
+ + +
    +

  1. It must be possible to add new "nodes" (elements and attributes) to the XML document.

    2. +

  2. It must be possible to edit existing nodes.

    3. +

  3. It must be possible to remove existing nodes.

    4. +

  4. It should be possible to move a node from one location to another within the XML document.

    5. +

  5. Where possible, all edits should be commutative in order to minimize the need for locking of the XML document.

    6. +

  6. It should be possible to send the complete content of a node or only the difference between the last version of the node and the current version.

    7. +
+ + +
    +

  1. It should be possible to re-use the XML document outside of a shared editing session (e.g., for offline editing in a different application, or for archiving).

    2. +

  2. It should be possible to specify the version of the protocol.

    3. +

  3. It should be possible to refer to outside resources (e.g., images hosted at websites) from within the protocol.

    4. +

  4. It should be possible to validate synchronization messages against a defined schema for the application type in real time.

    5. +

  5. It should be possible to log all synchronization messages and associated metadata for archiving and logging purposes.

    6. +

  6. It must be possible to uniquely identify each node in an XML document, both within the scope of a standalone shared XML editing session and if the edited object is shared with other appliclations or embedded in other objects.

    7. +

  7. It must be possible to maintain the ordering of XML elements in the document.

    8. +

  8. It must be possible to specify the parent of any given node.

    9. +

  9. It should be possible to associate an XML document with other XML documents.

    10. +

  10. It must be possible to represent human-readable text in a language and character set appropriate for a human user.

    11. +

  11. It should be possible to associate relevant metadata with each node in the XML document, which might include time of creation, identity of the creator, time of last modification, and identity of last modifier.

    12. +

  12. It should be possible to mix text nodes with other child nodes (namely elements).

    13. +
+ + +
    +

  1. It must be possible to initiate, update, join, and terminate a shared XML editing session.

    2. +

  2. It must be possible to specify the roles of parties to a shared XML editing session.

    3. +

  3. It should be possible to re-use the permission from a Multi-User Chat room, Publish-Subscribe node, or other service that has a permissions model.

    4. +

  4. It should be possible to declare shared editing of the XML document to be complete (e.g., in preparation for archiving of the XML document or editing by another application).

    5. +

  5. It should be possible to declare shared editing of part of the XML document to be complete.

    6. +

  6. It must be possible to reject out-of-order synchronization messages.

    7. +

  7. It should be possible to specify that all parties shall move their viewing context to a particular location in the XML data object.

    8. +
+ + +
    +

  1. It should be possible to retrieve the current state of the XML document from a party to the shared editing session.

    2. +

  2. It should be possible to retrieve the history of edits to the XML document from a party to the shared editing session.

    3. +

  3. It should be possible to retrieve all the changes to the XML document since a specific sequence number.

    4. +
+ + +
    +

  1. It must be possible to discover whether another entity can engage in a shared XML editing session.

    2. +

  2. It must be possible to discover which application types another entity can handle.

    3. +

  3. It should be possible to query an entity for the shared XML editing sessions to which it is a party.

    4. +

  4. It should be possible to query an entity for the XML documents it owns or knows about (which may be the result of a past editing session).

    5. +
+ + + +

This document requires no action by &IANA;.

+ + +

This document requires no action by the ®ISTRAR;.

+ + +

For their previous work on XMPP-based shared editing technologies, the author wishes to thank Mats Bengtsson, Michael Bishop, Dave Bryson, Boyd Fletcher, Joonas Govenius, Marshall Huss, Huib-Jan Imbens, Jasen Jacobsen, Michael Krutsch, Keith Lirette, Ian Paterson, Chad Smith, and Dan Winkowski.

+ + +