Logoot: A Scalable Optimistic Replication Algorithm for Collaborative Editing on P2P Networks

Weiss, Stéphane; Urso, Pascal; Molli, Pascal

doi:10.1109/icdcs.2009.75

Cited by 104 publications

(159 citation statements)

References 21 publications

(26 reference statements)

Supporting

Mentioning

153

Contrasting

Unclassified

Order By: Relevance

“…Docx2Go proposed by Puttaswamy et al [10] is a framework for collaborative editing over XML documents on mobile devices where not all devices have the complete document. It adapts the Logoot approach proposed by Weiss et al [11] for XML documents. XML elements possess unique identifiers, the set of identifiers being ordered and dense.…”

Section: Related Workmentioning

confidence: 99%

Enhancing rich content wikis with real‐time collaboration

Ignat

André

Oster

2017

Concurrency and Computation

View full text Add to dashboard Cite

SUMMARYWikis are one of the most important tools of Web 2.0 allowing users to easily edit shared data. However, wikis offer limited support for merging concurrent contributions on the same pages. Users have to manually merge concurrent changes and there is no support for an automatic merging. Real-time collaborative editing reduces conflicts as the time frame for concurrent work is very short. In this paper, we propose extending wiki systems with real-time collaboration. We propose an automatic merging solution adapted for rich content wikis. Our solution relies on an operational transformation algorithm defined for high level operations that capture user actions such as move, merge and split. Copyright c 0000 John Wiley & Sons, Ltd.KEY WORDS: CSCW; collaborative editing; operational transformation; wiki INTRODUCTIONThe Web 2.0 era is associated with the growing success of participatory collaborative tools for public users. Enterprises have integrated a part of these tools in their information systems to improve their productivity and to facilitate the emergence of a form of collective intelligence.Among these tools, wikis efficiently share and structure a large amount of knowledge. Wikis are interlinked pages of rich text. Any user can view and edit these pages. For instance, a software development team can dedicate a wiki page to the minutes of their meetings, another one to their bug reports and a last one to the progress of their development. This way, everybody can keep an eye on when is the next meeting, who will attend, the minutes of a previous meeting, what are the bugs found or fixed, and the completed work on the project. Moreover, a wiki allows fast updates and everybody can edit the content without any restriction. A wiki offers all these features in a single tool.However, most existing wiki systems such as MediaWiki do not automatically merge parallel modifications on the same page. This becomes critical when changes have to be performed very quickly. A typical example is breaking news, when it is common that hundreds of people contribute to the same related Wikipedia pages in a very short amount of time. If two users are concurrently editing the same article, when they try to save their changes, the changes of only one user are published. The other user will be presented with two versions of the wiki page: the one that the user tried to publish and the recently published version. Conflicts, i.e. concurrent changes on the same article, have to be manually resolved by users by retyping or copying and pasting the changes they performed in the last version that was published. Moreover, users are unaware of other concurrent updates on the same article until they try to publish their own changes. Resolving conflicts might become very tedious, and this can be critical when a change has to be published almost instantly. * Correspondence to: Inria Centre Nancy -Grand Est, 615 rue du Jardin Botanique, 54600 Villers-lès-Nancy, FR. Email: claudia.ignat@inria. Ignat et al. [1,2,3,4] highlight the fact that co...

show abstract

Section: Related Workmentioning

confidence: 99%

Enhancing rich content wikis with real‐time collaboration

Ignat

André

Oster

2017

Concurrency and Computation

View full text Add to dashboard Cite

show abstract

“…We evaluated in this experiment, three-waymerge techniques (diff3 described in Section II-A) used by git system. We evaluated also the usual textual algorithm used for collaboration editing: Operational Transformation (OT) algorithms and Commutative Replicated Data Type (CRDT) algorithms [43], [33], [28], [24]. The most OT algorithms that exist, use a central component.…”

Section: B Algorithms Evaluatedmentioning

confidence: 99%

“…All the studies are focused on synchronous systems and they are focused on execution time or memory occupation. Recently new approaches called Commutative Replicated Data Type (CRDT) are proposed [43], [33], [28], [24] to be a substitution of OT algorithms. As OT algorithms, these approaches are evaluated only on execution time and memory occupation in [1] and [2].…”

Section: Related Workmentioning

confidence: 99%

Improving Textual Merge Result

Ahmed-Nacer¹,

Urso²,

Charoy³

2013

Proceedings of the 9th IEEE International Conference on Collaborative Computing: Networking, Applications and Worksharing

Self Cite

View full text Add to dashboard Cite

Abstract-In asynchronous collaborative systems, merging is an essential component. It allows to reconcile modifications made concurrently as well as managing software change through branching. The collaborative system is in charge to propose a merge result that includes user's modifications. The users now have to check and adapt this result. The adaptation should be as effort-less as possible, otherwise, the users may get frustrated and will quit the collaboration.The objective of this paper is to improve the result quality of the textual merge tool that constitutes the default merge tool of distributed version control systems. The basic idea is to study the behavior of the concurrent modifications during merge procedure. We identified when the existing merge techniques under-perform, and we propose solutions to improve the quality of the merge. We finally compare with the traditional merge tool through a large corpus of collaborative editing.

show abstract

“…Since semantic annotations are embedded in page content in SMW, DSMW replicates only page contents and there is no need to deal with annotations. DSMW uses the Logoot algorithm to synchronize concurrent changes [4]. Logoot guarantees the consistency of the shared pages based on the CCI model (Causality, Convergence, Intentions [5], the model used also by Google Wave).…”

Section: Dsmw Approachmentioning

confidence: 99%

DSMW: Distributed Semantic MediaWiki

Skaf-Molli

Canals

Molli

2010

Lecture Notes in Computer Science

Self Cite

View full text Add to dashboard Cite

Abstract. DSMW is an extension to Semantic Mediawiki (SMW), it allows to create a network of SMW servers that share common semantic wiki pages. DSMW users can create communication channels between servers and use a publish-subscribe approach to manage the change propagation. DSMW synchronizes concurrent updates of shared semantic pages to ensure their consistency. It offers new collaboration modes to semantic wiki users and supports dataflow-oriented processes.

show abstract

Logoot: A Scalable Optimistic Replication Algorithm for Collaborative Editing on P2P Networks

Cited by 104 publications

References 21 publications

Enhancing rich content wikis with real‐time collaboration

Enhancing rich content wikis with real‐time collaboration

Improving Textual Merge Result

DSMW: Distributed Semantic MediaWiki

Contact Info

Product

Resources

About