n140502 nfoWorks nfoNote ODF 1.2 Change-Tracking Complexity Background

nfoWorks>notes> 2014>05> n140502d>  0.01 2017-06-14 20:22 -0700

{Ed.Note: This page will catalog material on the historical development and status of change-tracking in OpenDocument, starting with the 2002 contribution of schema to the OASIS Open Office XML TC.}

ODF TC JIRA Issues

These are issues related to change-tracking in OpenDocument format.  They are captured on the OASIS TC JIRA repository, started during development of ODF 1.2.  Issues raised before the use of JIRA that were not moved to JIRA are not covered.

• OFFICE-568 Public Comment: Change Tracking issue (2007-12-23)
  [moved to JIRA on 2009-05-09] This still unresolved new-status issue raises a concern about information leakage in documents when tracked-changes (and <office:change-info> elements) are retained from one document to the next as part of cloning to repurpose an existing document, for example.  This is an RCT invariant issue.  A companion concern is use as a covert channel as well, especially considering the current format of <office:change-info>.  See OFFICE-3383.
• OFFICE-1359 Public Comment: text:id vs xml:id (ODSF 1.2CD01) (2009-05-05)
  This is the origination of changes to allow xml:id and give it priority over other ID-valued attributes from earlier versions of ODF.  This is invariant with respect to RCT.
     
• OFFICE-2124 Member Proposal: format change tracking enhancement (2009-10-14)
  This unresolved new issue applies to a proposal on the ODF TC Wiki.  The proposal is to modify the handling of format changes so the before and after changes to style references are provided.  At the moment, there is no information in a <text:format-change> element that indicates what changed.   This is definitely an RCT concern.
     
• OFFICE-2180 Public comment: inconsistent use of change tracking, varying use of 'change-track' and 'track-change' element (2009-11-09)
  This comment is about wording and possibly erroneous mentions of the different elements.  This is invariant to RCT, where the ODF 1.2 element and attribute names are preserved, but change-tracking (the activity) and tracked changes (noun phrase) are both used in text.
• OFFICE-2359 5.5.[8,9,10] Change Marks, subdivisions of 5.5.7 (2010-01-27)
  This closed issue is an editorial change to the organization of the change-mark description.  There is no need for further concern.
    
• OFFICE-2360 5.5.7 Change Marks, Nesting and Rejection (2010-01-27)
  This issue was closed as out of scope.  It applies to cases when overlapping actions nest or cross-cut and sever change-mark pairs.  This is definitely a consideration for RCT, although perhaps expressed differently.
    
• OFFICE-2362 5.5 change tracking, tables in text documents (2010-01-27)
  This unresolved open issue was targeted to ODF 1.3 on 2010-03-21.  The proposed resolution is to allow <table:tracked-changes> in an <office:text> element along with <text:tracked-changes>.  It is unclear how RCT could allow for this and what impact RCT can have in support of <table:tracked-changes>.  This is important even though <table:tracked-changes> is out of scope for RCT at the moment.
     
• OFFICE-2621 Change Tracking of Lists: Storing Delete Fragments (2010-04-01)
  It is assumed that the resolution of OFFICE-2796 for section 1-5.5.4 solves this.  Subsequent investigation indicates that either 5.5.4 does not cover it or implementations are doing it wrong.
    
• OFFICE-2706 ODF 1.0/1.1 Section 5.1 Omits Exclusion of Change Tracking from in-line Text (2010-06-12)
  This unresolved new issue applies to a statement in ODF 1.0/1.1 (and IS 26300) that paragraph-content in <text:tracked-changes> is not to be regarded as in-line text when document text extraction is performed.  This was also missed in ODF 1.1 Errata 01 and the ODF 1.1/IS 26300 reconciliation.  This is invariant with respect to RCT. 
   
• OFFICE-2796 5.5.4 text:deletion ... adapt the end tags (2010-06-29)
  This resolved issue improves the restoration of <text:deletion> material by explaining that all leading start tags and all trailing end tags be remove, instead of just an enclosing <text:p> element tag pair.  This is still inadequate and does not handle the case where the deleted material started or ended at an element tag or that there might be more healing than rewriting one particular end tag beyond the <text:change-mark> element.  An useful stipulation might be that no deletion should be represented for which 5.5.4 does not provide perfect reversal, although this would rule out a surprising amount of currently implemented behavior.
    
• OFFICE-3312 Proposal to improve change tracking in ODF (2010-08-06)
  This is the open issue that includes the DeltaXML contribution via the ODF TC comment-submission list.  This issue was cloned to OFFICE-3680 for ODF 1.3, and since re-opened here.
     
• OFFICE-3317 1-5.5.2 <text:changed-region> ID attribute inconsistently available (2010-08-08)
  This issue addresses the schema and the specification with regard to the switch from use of text:id to xml:id while allowing text:id as well.  The final ODF 1.2 document schema reflects the appropriate solution.  The deprecation case is explained in ODF 1.2 Part 1 section 19.809.5.  This resolution has no impact on RCT.
• OFFICE-3373 1-5.5.1 <text:tracked-changes> not precise enough (2010-08-24)
  The association of <text:tracked-change> elements with particular scopes is clarified.  This resolution has no impact on RCT, which simply must respect it.
• OFFICE-3382 1-5.5.2 <text:changed-region> does not contain a list (2010-08-29)
  This issue resulted from public review prior to the advancement of ODF 1.2 on the track to OASIS Standard, concluded on 2011-09-29.  In the original schema brought to the Open Office XML TC in 2002, there was provision for a <text:deletion> child followed by an optional <text:insertion> child in the same <text:change-region> element.  That was not carried into any OASIS Standard for OpenDocument.
    
• OFFICE-3383 1-5.5.6 <office:change-info> content overkill (2010-08-29)
  This issue is resolved by deferral to ODF 1.3.  The <office:change-info> element is an optional element of every <text:changed-region> child for reporting the provenance of the change.  There is allowance for an arbitrary comment consisting of a sequence of any number of text-item components, including change-marks, tables, drawings, and other elaborate content.  This is relevant to RCT both for improved provenance and the prospect of change-tracking of such comments.
    
• OFFICE-3448 1-5.5.4 Text Deletion Interoperable Definition Required (2010-09-26)
  Resolved as deferred to ODF 1.3.  This issue asks important questions about selections and the healing of severed elements that remain unaddressed.  [Ed.Note: This is the first place that the notion of healing (cosmetic curing) and the reversibility of deletions were introduced.  These ideas are at the heart of RCT although this statement was forgotten at the time RCT was considered in May 2014.]
    
• OFFICE-3449 1-5.5.3 Text Insertion Interoperable Definition Required (2010-09-26)
  Resolved as deferred to ODF 1.3.  Introduces the need to heal removal of insertions as if they are deleted, along with other suggestions about selections and rough symmetry with deletion.
    
• OFFICE-3680 Proposal to improve change tracking in ODF (2011-04-04)
  This is a clone of OFFICE-3312 that is also targeted to ODF 1.3.  The only discussion on JIRA, so far, is at the earlier issue.
    
• OFFICE-3686 Public Comment: Proposal for new document element, "Document history" (2011-04-11)
  This proposal is for an automated derivation of a change report that could be presented as part of a document.  On reflection (2014-07-03), although there is a granularity issue, there might be a feasible approach using an extension/profile of <office:change-info> and a variation on provisions for defining user indexes.
    
• OFFICE-3716 Public Comment: Change tracking in the proposed ODF 1.2 standard (2011-08-22)
  This comment urged remedy in conjunction with the public review of ODF 1.2 Committee Specification 1.  The resolution as a "duplicate" explained that there are issues about this and a subcommittee working on change tracking.

Attribution:

Hamilton, Dennis E.

ODF 1.2 Change-Tracking Background.   nfoWorks nfoNote page n140502d 0.01, July 3, 2014.  Accessed at <http://nfoWorks.org/notes/2014/05/n140502c.htm>.

Revision History:

0.01 2014-07-03-14:04 Include JIRA Summaries

ODF TC JIRA issues relevant to change-tracking are catalogued with brief descriptions.

0.00 2014-07-02-15:22 Initial Placeholder Version

Provide initial placeholder version for cataloguing known issues, identify known JIRA issues.
 

You are navigating nfoWorks. This work is licensed under a Creative Commons Attribution 2.5 License.

created 2014-07-02-15:22 -0700 (pdt) by orcmid $$Author: Orcmid $ $$Date: 17-06-14 20:22 $ $$Revision: 25 $