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


Help: OASIS Mailing Lists Help | MarkMail Help

office message

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

Subject: [OASIS Issue Tracker] Commented: (OFFICE-2621) NEEDS-DISCUSSION:Public Comment: Change Tracking of Lists - Storing delete fragments

    [ http://tools.oasis-open.org/issues/browse/OFFICE-2621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=19983#action_19983 ] 

Dennis Hamilton commented on OFFICE-2621:

Oliver, it bothers me that I am asked to fix something that I didn't break.


I have done extensive analysis of this issue.  I uploaded a document that demonstrates that deletion works just fine, using a technique that alwasy stores well-formed XML that can then be stripped back to what was actually deleted.  This also applies for certain insertions and especially replacements where the extract of replaced material is not itself well-formed XML.

In April, I uploaded my demonstration to <http://www.oasis-open.org/committees/document.php?document_id=37440>.

At the end of May, I also sent that material to others who said they were proposing an alternative, hoping to show them that it is not change-tracking that is broken, but it is the description of change-tracking that is defective.

On Wednesday, July 21, I learned that there is an alternative proposal for ODF change-tracking that may be submitted as an SC34 defect report and as a Public Comment.  This was reported to JTC1 SC34 WG6 (ODF Maintenance), <http://mailman.vse.cz/pipermail/sc34wg6/2010-July/000132.html>.

I don't know whether that proposal expands change-trackign in ODF.  I suspect that any change-tracking extensions would need to be deferred to ODF-next.  However, it appears from the note to WG6 that the proposal will break the current change-tracking, at least for deletions, and will break the principle that the clean text (as if the changes are all accepted) can be extracted just by flattening the XML of ODF in-line text.  (By flattening I mean delete start- and end-tags and use the text that remains).  (We need a note to point out the principle in the ODF 1.2 section on tracked-changes elements.)

Concerning the level of effort, I believe I understand how this works well enough to correct the descriptions in a way that fits with the current, interoperably-working implementation.  That will require great care.  However, the most-difficult part will be verifying that there are no edge cases that arise in all of the ways that change-tracking can be introduced in a document, how it works when changes are atop changes, and so on.

That last part of the work is very demanding and is not something I would undertake lightly.  It would also distract me from other areas of ODF 1.2 that are priorities for me, along with other commitments that I am working on.

I would think that those implementers whose handling of change-tracking would be broken by proposals of a new "solution" would want to put some attention on this issue.

> NEEDS-DISCUSSION: Public Comment: Change Tracking of Lists - Storing delete fragments
> -------------------------------------------------------------------------------------
>                 Key: OFFICE-2621
>                 URL: http://tools.oasis-open.org/issues/browse/OFFICE-2621
>             Project: OASIS Open Document Format for Office Applications (OpenDocument) TC
>          Issue Type: Bug
>          Components: Lists, Paragraph, Table, Text
>    Affects Versions: ODF 1.0, ODF 1.1, ODF 1.2 Part 1 CD 4 
>            Reporter: Robert Weir 
>            Assignee: Dennis Hamilton
>            Priority: Blocker
>             Fix For: ODF 1.2 Part 1 CD 5
> Copied from office-comment list
> Original author: Ganesh Paramasivam <ganesh@crystalfab.com> 
> Original date: 26 Mar 2010 04:56:09 -0000
> Original URL: http://lists.oasis-open.org/archives/office-comment/201003/msg00005.html

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


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