RE: [office-collab] Counting issues, etc

["Dennis E. Hamilton" <dennis.hamilton@acm.org>]

I will provide a direct statement of the challenge on a new thread (not today).

WHAT I'M AFTER:

My reason for introducing a small case that has a grounded existence in actual implementations was to find out what the MCT equivalent is, at a comparable level of detail: How does MCT handle exactly the same situation.

Specifically: Besides the markup of the as-changed specimen of a document, what other material is in the persisted document so an MCT-aware consumer can present the tracked changes and implement acceptance, rejection, and making of further arrangements.

I am asking for a grounded example that shows how MCT handles the same thing or, if it doesn't, what has to happen with MCT instead?

It is a very simple case and I thought this would nail down some specifics that assist in understanding and appraisal of the MCT technique.

I don't think I am disagreeing about anything to do with MCT.  I am in no position to do that. 

I do want to know what a specific (not-necessarily unique) equivalent in MCT is.

Also, I don't think it matters to talk about forward and backward looking.  Both ODF 1.2 and MCT produce a persistent form of the text as changed.  The question is how is the tracked-change information interpreted against that text.  Whatever the nomenclature on items about those transformations, there will have to be a way to present the changed text with in-line indication of additions and deletion that occurred from some previous unmodified form.

That reminds me of something else though.  ODF 1.0/.../1.2 include, in the <text:deletion> element, an <office:change-info> component that has a <dc:creator> element, a <dc:date> element, and an optional run of <text:p> elements providing commentary.  It would be useful to know what the counterpart in MCT is and what it is associated with.  In some sense, these need to align with what the user who caused the particular alteration was doing at the time.  

 - Dennis

-----Original Message-----
From: office-collab@lists.oasis-open.org [mailto:office-collab@lists.oasis-open.org] On Behalf Of Patrick Durusau
Sent: Tuesday, October 02, 2012 17:26
To: office-collab@lists.oasis-open.org
Subject: Re: [office-collab] Counting issues, etc

[ ... ]

For ODF 1.2, ECT and GCT (warning, just my opinion, others may correct), 
change tracking *looks forward* from the document instance as read into 
the application and when the file is saved, changes are recorded against 
the original document markup.

For MCT (again, just my opinion), change tracking *looks backward* from 
the document instance that is being saved and records changes as 
operations against the document that is being saved.

The results should be equivalent but how you specify them and 
advantages/disadvantages are quite different.

[ ... ]