n140501 nfoWorks nfoNote RCT: ODF 1.2 Change-Tracking Repair Development Roadmap: Initial Sketch

nfoWorks>notes> 2014>05> n140501c>  0.04 2017-06-14 20:22 -0700

Development of the RCT: Repaired Change-Tracking ODF 1.2 Extension Profile proceeds at several level.  The work is iterative and cross-cutting among the levels.  All of the effort is reflected on nfoWorks web pages with progressive additions and refinements. 

These are the objectives:

• RCT: Repaired Change-Tracking ODF 1.2 Extension Profile
  The hypertext document of the profile itself, implemented in web pages, unfolded in an organization managed here..
    
• Suites of Test Documents
  Developed progressively, with crossovers, to support
  • Verification of Down-Level Resiliency to Extensions
    ensuring that existing implementations robustly treat extensions for which they are not designed
  • Assessment of Conformance to Application Profiles
    particularly at a level beyond the minimum behavior
  • Assessment of Interoperability
    generally in targeted contexts

These end points depend on results of extensive analysis and progressive development:

• Establishment of RCT Principles for ODF 1.2 Extension
  The initial position is to assume that ODF 1.2 producers are confined to producing tracked changes that an ODF 1.2 consumer can interpret and accept/reject based solely on provisions of ODF 1.2.  This is not accurate with respect to implementation behavior.  It is a starting point.  RCT embarks from that position to establish what producers could do, via RCT, to accomplish what is actually done, and more, in a manner that is reversible and may be superior even when a consumer is not RCT-aware.
   
• Development of the RCT Structural Model
  defining a conceptual model within which tracked-changes can be related to actions on the part of authors and their reflection in the emitted ODF representation of the user's document and in the recovery and presentation of the intended document from that representation.  The conceptualization takes advantage of Blue Sky Office (BSO), a theoretical WYSIWYG processor as a means of characterizing possible interpretations between the document format and the document manifestation used and manipulated by users.   BSO is not prescriptive, but representative to how representations in the document format may connect with the document as envisioned and manifest to users.
    
• Analysis of OpenDocument Format Provisions
  identifying the complexities inherent in the ODF 1.2 allowance of tracked changes and the interdependencies with other provisions of the representation of documents in ODF.
    
• Profiling of RCT Tracked-Change Cases
  establishing a finite, comprehensible case enumeration by which repaired change tracking is effective.

Attribution:

Hamilton, Dennis E.

RCT ODF 1.2 Change-Tracking Repair Development Initial Sketch.   nfoWorks nfoNote page n140501c 0.04, November 6, 2014.  Accessed at <http://nfoWorks.org/notes/2014/05/n140501c.htm>.

Revision History:

0.04 2014-11-06-09:16 Light Editing

Use roadmap and sketch consistently

0.03 2014-07-10-21:13 Tie in Blue Sky Office

Connect to Blue Sky Office for providing representative cases without compelling particular behavior.

0.02 2014-07-08-09:04 Clarify Initial Conditions and Contrasts

The initial relationship with ODF 1.2 reversibility is established.

0.01 2014-07-01-17:29 Provide Initial Sketch

0.00 2014-05-04-12:54 Initial Placeholder Version

Provide initial placeholder version for holding initial conceptualization notes.

 

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

created 2014-05-04-12:54 -0700 (pdt) by orcmid $$Author: Orcmid $ $$Date: 17-06-14 20:22 $ $$Revision: 120 $