OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

office-collab message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: [office-collab] Some thoughts on Change Tracking


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.

I always thought that annotating a change in the GCT was more for higher
level semantic use. For example, editing an article if one gets new
information about "General X does Y" they might make that part of the
annotation for the change set to keep higher level semantics for the
edit.

I'm interested in the non-xml data models. Abiword uses a piecetable to
store and edit the document, and has a non ODF native file format which
it is geared towards.

Though during IO things boil down to using various append() methods on
the piecetable to bring in the document structure;
https://github.com/monkeyiq/odf-2011-track-changes-git-svn/blob/master/plugins/opendocument/imp/xp/ODi_TextContent_ListenerState.cpp#L2836

And some of the append() methods are around here;
https://github.com/monkeyiq/odf-2011-track-changes-git-svn/blob/master/src/text/ptbl/xp/pt_PieceTable.h#L280





[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]