office-collab — archive

[Andreas Guelzow]

On Thu, 2011-09-15 at 18:12 -0600, monkeyiq wrote: > On Thu, 2011-09-15 at 23:53 +0200, Thorsten Behrens wrote: > > monkeyiq wrote about ECT: > > > I find this an extremely critical issue has it means that users of > > > change tracking are relying on various applications to imply changes > > > rather than being told directly and explicitly what has changed. > > > > > Hi Ben, > > > > well the same applies to GCT. The very fact that it needs > > annotations is testament to this issue. I maintain that GCT markup, > > while being a nice idea on the xml level, fails my requirements as > > an implementer of a non-xml internal data model application. > > > > Cheers, > > Perhaps we are looking at different aspects here. I am referring to > example like the "Edit Image/Shape/Chart" from the ECT (pp17). In order > for an application to tell you that the image file name changed from > Image1.jpg to Image2.jpg it will have to do a diff on the > > text:tracked-changes/ > text:changed-region@text:id="1"/ > text:deletion ct:id="1"/ > draw:frame > And the inline draw:frame for > text:change-start text:change-id="1" ct:sub-id="2" > > In the GCT this would be explicit in an ac:change attribute. No need to > perform any analysis to see that the xlink:href was Image1.jpg in the > last revision. But changing the name of the image file in the zip package is _not_ a change to the document. The image file names are just internal references to find the appropriate image or chart description. Andreas > -- Andreas J. Guelzow, PhD, FTICA Concordia University College of Alberta This is a digitally signed message part