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-3312) NEEDS-DISCUSSION:Public Comment: Proposal to improve change tracking in ODF

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

Dennis Hamilton commented on OFFICE-3312:

Here's another guiding principle that presents an invariant, but I am not sure how consistently it can be achieved.

GUIDING PRINCIPLE #2 - For Formatted Text [Provisional]

There are only insertions and deletions and changes of styles.

Replacement of one text by another is the same as a deletion followed by an insertion.

SubPrinciple #2.1.  There is no deletion introduce as part of an insertion.  Any deletion as part of a replacement is adjacent to the insertion, either before it or after it, but adjacent.

SubPrinciple #2.2 Any commentary about a preceding deletion or insertion can be kept out of line with the history of tracked changes.  (This is distinct from annotations, which are simply treated as part of the text, perhaps).

SubPrinciple #2.3 The document format support for change-tracking is such that latest of the insertions and deletions that still apply to a stretch of text can be revoked or accepted and the appropriate roll-back of text and change-tracking information accomplished.  This is something the format provisions must enable.  The format does not require that this be done nor specify how it be done.

SubPrinciple #2.4 Ideally, the same conditions as (2.3) can be applied to undo, although there is no direct provision in the ODF format to provide undo when consuming a produced document.

SubPrinciple #2.5 If it is possible to disturb the integrity of change tracking by turning off tracking, making changes, and then continuing with further tracked changes, any effect in the format is one that a consumer can recover from automatically and gracefully.

> NEEDS-DISCUSSION: Public Comment: Proposal to improve change tracking in ODF
> ----------------------------------------------------------------------------
>                 Key: OFFICE-3312
>                 URL: http://tools.oasis-open.org/issues/browse/OFFICE-3312
>             Project: OASIS Open Document Format for Office Applications (OpenDocument) TC
>          Issue Type: Bug
>          Components: Lists, Part 1 (Schema), Schema and Datatypes, Styles, Table, Text
>    Affects Versions: ODF 1.2 CD 05
>         Environment: This proposal addresses issues around change-tracking as it has existed since ODF 1.0.  It is evidently offered in the context of ODF 1.2.
>            Reporter: Dennis Hamilton
>            Priority: Blocker
>             Fix For: ODF 1.2 CD 06
> Copied from office-comment list
> Original author: Robin LaFontaine <robin.lafontaine@deltaxml.com>
> Original dates: 2010-07-30-09:33Z to 2010-07-31-09:52Z
> Original URLs: 
>    http://lists.oasis-open.org/archives/office-comment/201007/msg00009.html
>    http://lists.oasis-open.org/archives/office-comment/201007/msg00010.html   
>    http://lists.oasis-open.org/archives/office-comment/201007/msg00011.html
> [Note: the office-comment issue scraper may have run but these came through at a time when the JIRA engine may have been blocked in some way.  I have created this issue as a placeholder until such time as the automated forwarder catches up.]

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]