On 27/11/14 23:30, Svante Schubert wrote: > Basically the paper states: To improve document revision systems we > should stop use file comparison for change detection. Instead the > changes should be kept during editing and exchanged. Even being standardize.
This looks like a supplement to Git-Hub, rather than a replacement. That said, I see a couple of potential issues with a "document change markup protocol": * Bloated size. Taking a real world example. I have a document that currently is 80 MB in size. As recently as four days ago, it was 140 MB in size, whilst three months ago, it was 60 MB in size. Were all of the document changes to be included, today's document would be at least 150 MB in size. * Scrubbing: The only way to ensure that document scrubbers strip all of the changes, is if there are either prefixes, or suffixes that are reserved exclusively for "document change markup protocol" words, styles, and other things that end up being used for tracking the document changes. Of necessity, these functions will have to be exclusive. * Comprehensiveness: At the risk of being pedantic, at what point does an edit go into the "document change markup protocol": # If I type "tyep" rather than "type", and immediately correct the error, does that become a part of the "permanent record"? Perhaps one needs to provide justification for: ## Why the altered content becomes part of the "permanent record"; ## Why the altered content does not become part of the "permanent record"; FWIW, the "tyep"/"type" example is from using tools that save glyphs as soon as they are the individual keys are pressed. (IOW, the glyphs are saved in "real time".) The current state of predictive word selection is such, that it is not uncommon for software to automatically insert the predicted word, rather than the desired word, with the user having to either leave the wrong word in, or completely rewrite the sentence, to retain the same meaning, but with different vocabulary, or terminate the message just before the word, send that message, then send the problem word, then send the message until the next non-predicted, and unfixable word." ### I am assuming that tools will exist that will completely scrub all "document changes", and markup relating to them, and that other tools will be able to compare "document changes" between different documents with the same basic content. jonathon * English - detected * English * English <javascript:void(0);>
signature.asc
Description: OpenPGP digital signature
