That's interesting, Peter. If you mean version control systems of the kind that are used with source-code management, it seems to me that the paper demonstrates how such a version control system can't work. That is because such version-control systems operate syntactically on the file format, not semantically on what the conveyed document is.
Alternatively, if you mean some sort of versioned file or control (i.e., document-management) system, that doesn't work well decentralized. Folks love decentralized tracking of changes in interchanged documents. And folks still want to be able to see what the differences are in terms of how the document is perceived by them. There are communities of practice where change-tracking carried with the document and presented in usable ways is very important. Civil administration and law firms seem to be particularly keen about it. In those contexts, lack of adequate change-tracking is a deal breaker. This may not matter for the sweet spot to which Corinthia is addressed. I think an easy way to determine the importance of change-tracking will be to see how rapidly, if at all, the Microsoft Office Web Apps and the small-device versions provide some sort of versioning with change-tracking in conjunction with their collaborative-editing facilities. The ubiquity and reach of those applications should provide useful information on what end up being important features for collaborative on-line/off-line mixed operations. - Dennis -----Original Message----- From: Peter Kelly [mailto:pmke...@apache.org] Sent: Saturday, June 13, 2015 22:47 To: dev@corinthia.incubator.apache.org Subject: Re: "Navigating the Document-Format Anti-Pattern" This is one of the main reasons why I believe that change tracking information has no place in a document format, but is better dealt with by a version control system. — Dr Peter M. Kelly pmke...@apache.org PGP key: http://www.kellypmk.net/pgp-key <http://www.kellypmk.net/pgp-key> (fingerprint 5435 6718 59F0 DD1F BFA0 5E46 2523 BAA1 44AE 2966) [ ... ]
