[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Let's Keep the Cases Straight
I notice that there is a tendency to view whatever already happens using the ODF 1.x change tracking as part of ECT and that GCT escapes it. I think we need to look at the choices in front of us where a. ODF? is what there is in major circulation now, more-or-less related to what is in the ODF 1.0-ODF 1.2 specifications (the ? related to the uncertainty around bugs and limitations in implementations and the specification too. b. GCT is the general proposal that uses the DeltaXML approach as a basis c. ECT is the approach to extending change tracking using ODF? as a starting point. That means we have these to wonder about: 0. ODF? as it is or maybe tidied up a tiny bit (I number this 0 because I don't think we can get away with this) 1. GCT 2. ODF? + GCT (unless we believe we'll ever get away with abandoning ODF? without a way forward, even if it means a protracted deprecation period, sort of like OOXML part 4.) 3. ODF? + ECT (the only place where ECT applies) - Dennis -----Original Message----- From: monkeyiq [mailto:monkeyiq@gmail.com] Sent: Sunday, April 24, 2011 01:30 To: Frank Meies Cc: office-collab@lists.oasis-open.org Subject: Re: [office-collab] Suggestions for moving forward to resolve issues On Fri, 2011-04-22 at 12:55 +0200, Frank Meies wrote: > That's what OOo currently does. There is no difference (neither in the > generated xml nor in the internal structures) if you change the > caption text:p or any other paragraph in the document. So in this particular case, the ECT as it stands is actually a fair bit harder to implement than the GCT. The ECT requiring two very different IO paths depending on context. [ ... ]
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]