office-collab — archive

How do we count? - September 26, 2012

From: Patrick Durusau <[email protected]>
To: [email protected]
Date: Wed, 26 Sep 2012 12:50:00 -0000

Oliver, On 09/26/2012 07:04 AM, Oliver-Rainer Wittmann wrote: Hi, Andreas, Yes, Andreas is more or less right - it is a feature of the application. Do you think it make sense to create a dependency in the file format between two tracked changes which is not needed? Even if changes impact the same content, isn't it still true that a user can accept or reject either change? Say a change reorders content: white and black -> black and white (one change) Second change, bolds the phrase and adds a note to a student "This is the customary order." Actually that is three changes but you get the picture. But we have to record the changes, whether on the same content or not, in some order. The "natural" order would be to record the changes in the order in which they occur, although you could present those to the user in any order the application chooses. For example, all the changes to particular content could be presented on particular content and not in the "order" in which they occurred. But that is a presentation issue, not one of the format for tracking changes. Yes? Hope you are having a great day! Patrick PS: In an inverted index, the positions of tokens are always counted as positions in a text stream. But there the text being indexed is fixed. What we need for operations based change tracking is a common method for identifying elements, attributes and their values and content. So that "counting" up all the values to any given point in change tracking, gives us a common value that locates a change (and that we record in the change tracking syntax). I restate the problem just to help me think about possible solutions. It seems to me that this has been solved before (or something very similar). Mit freundlichen Grüßen / Best regards Oliver-Rainer Wittmann -- Advisory Software Engineer ------------------------------------------------------------------------------------------------------------------------------------------- IBM Deutschland Beim Strohhause 17 20097 Hamburg Phone: +49-40-6389-1415 E-Mail: [email protected] ------------------------------------------------------------------------------------------------------------------------------------------- IBM Deutschland Research & Development GmbH / Vorsitzende des Aufsichtsrats: Martina Koederitz Geschäftsführung: Dirk Wittkopp Sitz der Gesellschaft: Böblingen / Registergericht: Amtsgericht Stuttgart, HRB 243294 From: "Andreas J. Guelzow" <[email protected]> To: <[email protected]> Date: 25.09.2012 17:11 Subject: Re: [office-collab] How do we count? - September 26, 2012 Sent by: <[email protected]> On Tue, 2012-09-25 at 08:31 -0600, Oliver-Rainer Wittmann wrote: Hi, Operations are being added upon a stack/queue. Each operation is working in relation to the document state at their time. Every operation is simply added upon the stack, there is a basic time/stack depth relation. I am not sure, if it needed that operations need to be on a stack/queue for an intrinsic change tracking. My view is: In general two changes are independent unless the changes are touching the same content. Even if they are touching the same content they can be independent - e.g., formatting a text as bold and afterwards as underlined. I admit that certain changes are depending on each other, but this is not the general case from my point of view. I think it is an important feature of CT in an application that certain changes can be rejected/accepted independently. This feature is not really supported by bringing the changes into a strict order. I don't think that this is a feature of the file format. The file format needs an efficient way of storing a record of these changes. I don't think that whether individual changes can be accepted or rejected has nothing to do with that. Andreas -- Andreas J. Guelzow, PhD, FTICA Concordia University College of Alberta [attachment "signature.asc" deleted by Oliver-Rainer Wittmann/Germany/IBM] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] -- Patrick Durusau [email protected] Former Chair, V1 - US TAG to JTC 1/SC 34 Convener, JTC 1/SC 34/WG 3 (Topic Maps) Editor, OpenDocument Format TC (OASIS), Project Editor ISO/IEC 26300 Co-Editor, ISO/IEC 13250-1, 13250-5 (Topic Maps) Another Word For It (blog): http://tm.durusau.net Homepage: http://www.durusau.net Twitter: patrickDurusau