Ganesh Paramasivan:
- Moving the storage of deleted changes inline will greatly simplify
the implementation of delete change loading/saving.


Michiel Leenaars:
On that first point, since it is also a question in the document: in case of say
very large deletions (say people moving around large chapters with many elements
such as footnotes within a document etc) it crossed my mind that you might want
to have both mechanisms in place, and have applications decide on the basis of
criteria we do not need to set ourselves (e.g. volume of the removed part) which
option to pick. Simple short stuff might be inline, huge deletions could be kept
elsewhere for performance reasons. Any thoughts on that? Would that be worth the
cost of two mechanisms?


Robin La Fontaine:
My view on this is that we should always avoid having two different ways of representing the same thing, for reasons outlined in the document. In this case there is no very strong reason to have both representations, and therefore I think we should decide on either inline or removed elsewhere. Ganesh provides a view to say that inline is better, and I would tend to agree with this.