RE: [office-collab] Re: [office] Groups - MCT Challenge #2 (PDF) uploaded

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

My sympathies are with the statement by Oliver on the call log:

   [16:08] Oliver-Rainer Wittmann: Thus, yes I agree. I would 
   also go a step further: Would be good, if an application 
   could indicate a certain bundling and may be also name it.

Whether an application shows or allows unbundled handling of tracked changes it would be great if they could be recorded as bundled by producers that are able to do so.  It makes the history cleaner.  If consumers preserve that, even if the bundle can be separated, it is nice to be able to accept or reject a bundle as one action.  

MCT can't specify this (any more than it can prevent the ridiculous notion of tracking single keyboard actions all by the same user in the same session), but I think it is important that it enable it.

Finally, I don't know what it means to say that "the information set can't change," so I can't assess the implications of that.

 - Dennis

-----Original Message-----
From: office-collab@lists.oasis-open.org [mailto:office-collab@lists.oasis-open.org] On Behalf Of Svante Schubert
Sent: Wednesday, December 05, 2012 05:08
To: office-collab@lists.oasis-open.org
Cc: office@lists.oasis-open.org
Subject: [office-collab] Re: [office] Groups - MCT Challenge #2 (PDF) uploaded

Excuse the cross-posting, I replied to the sub-committee list directly, with CC to office list to show up the follow-up in the archive.

Note: The scenario has similarities to the former given 'Change-Tracking with "show-changes" enabled' show case:
https://lists.oasis-open.org/archives/office-collab/201210/msg00049.html

Answering Dennis questions:


1.	When the change is created in MCT, is it tracked as a single action with two consequences, or two separate actions?
	
	To answer literally: It does not matter. In general every user interaction can be mapped to a single MCT operation. Still some MCT operations can be compressed to a single one, and other MCT operations can be split up to multiple one. For instance, the insertion of multiple following single characters can be seen as the insertion of text consisting of the single characters. 
[ ... ]
	
2.	When ODF 1.2 tracked-changes are upward converted, is there any difficulty having these be separate operations at what is essentially the place? That is, can they still be recognized and independently accepted/rejected in a straightforward manner?
	No problem, as two operations would be detected.

Perhaps we are able to continue the discussion in our call in about 80 minutes.


On 27.11.2012 19:46, Dennis Hamilton wrote:


Document Name: MCT Challenge #2 (PDF) <https://www.oasis-open.org/apps/org/workgroup/office/document.php?document_id=47560> 

________________________________

Description
This particular challenge does not expose any implementation bugs. The
persistent documents reflect valid tracked-changes in terms of the ODF
specification. That the producer chose this particular approach to
enacting the changes made by an user is appropriately
implementation-determined. The challenge is around MCT equivalents and
alternatives (if any) for the same cases and up-/down-level
interoperability.

[ ... ]