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-3373) ODF 1.2 Part 1 5.5.1<text:tracked-changes> not precise enough

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

Dennis Hamilton commented on OFFICE-3373:

With regard to the change in 5.5.2 is that a fact?

I know I asked the question, but I was expecting a negative answer.

Thanks for clarifying this.

The implications that I see is that acceptance/rejection of any one change does not necessarily remove a <text:change-region> because the change might be accepted or rejected differently in other places and in still other places might still simply be left tracked.  (There seems no way to undo an accepted or rejected change when producing a document because there is no provision to differentiate tracking of accepted/rejected changes in ODF 1.2.)

So a consumer that implements operations on tracked changes has to avoid deleting a particular <text:changed-region> if it is not known whether or not there are any referencing change-mark elements that remain .  I suppose the easy way is not to delete any except on load, but then delete those for which there are found to be no referencing change-mark elements.  That's not too demanding.  It will probably lead to an OIC interoperability advisory though :).

I have talked myself into seeing that this is not burdensome.  

> ODF 1.2 Part 1 5.5.1 <text:tracked-changes> not precise enough
> --------------------------------------------------------------
>                 Key: OFFICE-3373
>                 URL: http://tools.oasis-open.org/issues/browse/OFFICE-3373
>             Project: OASIS Open Document Format for Office Applications (OpenDocument) TC
>          Issue Type: Bug
>          Components: Public Review, Text
>    Affects Versions: ODF 1.2 CD 05
>            Reporter: Dennis Hamilton
>            Assignee: Oliver-Rainer Wittmann
>            Priority: Minor
>             Fix For: ODF 1.2 CD 06
> The current statement of what the <text:tracked-changes> element is imprecise and does not establish the relationship between the different places <text:tracked-changes> can occur and the places where the corresponding <text:change>, <text:change-start> and <text:change-end> will occur.
> Each header-footer style element has  a  <text:tracked-changes> element child for the tracked changes corresponding to change marks within the other element children of the header-footer style element.
> Each <office:text> element has a <text:tracked-changes> element child for the tracked changes corresponding to change marks within the other element children of the <office:text> element.  [This may need to be even more specific.]
> There is more to be figured out if a <text:tracked-changes> element is absent or there are change marks that have no corresponding <text:changed-region> in the applicable <text:tracked-changes> element.

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]