Thanks, Rob, it seems that this opens up interesting doors for down-the-road variants of OpenOffice based on Wave editing models and data models. The challenge and the opportunity is that Wave's OT model acts on the body of a document, so conversations and collaborations can become the body of a more polished document over time. The data model for Wave could be adapted for more traditional body-plus-comments data models via the wavelet construct, though.
Thanks for joining this thread, let's keep the communication flowing. Best, John On Jun 16, 2013 11:02 AM, "Rob Weir" <robw...@apache.org> wrote: > I'm not subscribed to this list, but Christian Grobmeier pointed me to > John's post about how OT and Wave could be relevant to OpenOffice. > > I wanted to mention that the idea is being discussed, but at the > standards level. The default document format for OpenOffice is Open > Document Format (ODF), which is standardized at OASIS and ISO. (I > chair the committee at OASIS). We're currently working on ODF 1.3 and > as part of that we're adding a new change tracking mechanism based on > OT. This is the traditional asynchronous change tracking that office > suites have had for years, but modeled on OT terms. > > And, although not specified at this point, we're also aware that OT > enables more interesting modes of collaboration, including > synchronous/real-time, co-editing, etc. That's the main reason the OT > approach is attractive, is that we can have a single model that will > work for change tracking as well as co-editing. > > Once we get the standard side of this elaborated in more details, then > the next step will be to get it implemented in Apache OpenOffice as > well as the Apache ODF Toolit (incubating). But the pace of > standardization is slow, and I wouldn't expect this before 2014. > > Regards, > > -Rob >
