n130301a: SCT: Savage Change-Tracking

Status

Date

Description

done

2013-03-16

This material conforms to the 2008-02-18 styles for Site Bootstrapping. Check those pages for additional details of the approach and the styles. Contact the nfoWorks technical coordinator with questions and to report any defects that you notice.

2014-07-09

RighteousOffice might also have hypothetical use of whole-package signing and encryption. This probably does not have to figure in SCT, but the use of embedded signed packages might be superior in many respects.

2014-07-07

Create a position paper on SCT and the challenge. There is a July 15 deadline.

2014-07-07

In addition to recalculation changes, this also applies for any refreshing that causes automatic updates (such as date-time stamps and random-number generations). So the identification of a signed and preserved manifestation must be clear, and it must be clear what happens if a document is saved after any change. It must be easy to see the changes.

2014-07-07

If BlueSkyOffice (.blu) is used for RCT, we need something different for SCT illustration. It probably doesn't start with S, because of StarOffice. I am choosing RighteousOffice (.rto) for this strong arrangement.

2014-07-07

A consequence for turnaround documents, including forms and spreadsheets, is that the entries and derived results are captured apart from the core document, which may be both protected and signed. It is critical that viewing documents presents them as-signed, and any recalculate differences show up a tracked changes for review and if committed (re-signed or not). It is always clear what is being watched.

2014-07-07

A critical quality of SCT's signature preservation is that someone who opens a document for viewing will see it as read-only and in the form that it was signed. This means that all entered values and computation-derived values are preserved as committed with signature. It also means that a recalculate will track any changes that result, by default.

2014-07-07

A critical quality of SCT is that it is signature preserving. That is, changes are external to the signed document that is being changed and the combinatiion can then be signed, and so on. This is important for negotiated documents, collaborative changes, and turnaround documents of many kinds.

2014-07-06

#72.51 The ability to save local commits and also retain conflicts seems like an interesting problem, especially with various contributors going off-line, coming back on, etc. Is this different that a cache?

2014-07-06

#72.51 Is distributed collaboration a form of commit synchronization, even though the various document instances are "live." It looks like decentralized synchronization and Lamport's approach need to be understood.

2014-07-06

#72.51 It appears that SCT is more appropriate for collaboration, since something like Git collision-resolution can be applied to the externally-tracked changes.

2013-03-16

Consider Jailbreaking my OASIS and my W3C contributions, and relate to that with respect to SCT. [dh:2014-05-04 These might best be handled in n140501 and linked from here as related material.]

2013-03-16

Review the ODF TC for related SCT work, and the ODF specifications as well, treat as resources

2013-03-16

Review diary for SCT-related materials, the Operational Change work, etc.

2013-03-16

Consolidate other work items related to Change-Tracking in the SCT Groundwork work items.

2013-03-16

Start bringing over notes from notebooks, starting backwards from #70 [dh:2014-06-10 and now #27].

done
2014-07-08

2014-06-10

Motivate the difference between RCT and SCT. SCT operates under serious constraints that preserved the integrity of the document on which changes are injected, and this is recursive. Although proposed as an option, given RCT, SCT can be even more savage. At the same time, the same complexity issues apply.

done

2014-06-10

n130301c: Repair the dangling <dl> at the bottom of the page

done

2014-06-10

Simplify the title to SCT: Savage Change-Tracking and leave groundwork to the first folio: n130301, n130301a, n130301b, n130301c, n000001

done
2014-06-10

2014-05-04

The folio catalog might better be Related Material?

done

2014-05-04

n130301-cache/ Include in n130301 Related Material

done

2014-05-04

Remove work-items that were left here from boilerplate and off-topic for this folio.

done
2013-05-08

2013-03-16

Bring over relevant notes from n000000, d000000 [none], and nfoWare.com/notes/n000000

done

2014-04-27

n130301-cache: Add index.htm and stitch into Construction Structure

done
2013-03-20

2013-03-16

n130301c: Preserve the mail notes to public-change @w3.org and the ODF TC

done
2013-03-18

2013-03-16

Consider creation of a cache folder when there are extensive materials to hold onto that are relevant to SCT.

done

2013-03-16

Add to the catalog

done

2013-03-16

Make placeholders for n130301, n130301a, n130301b, and n130301c

done

2013-03-16

Create this page ready for recording Diary & Job Jar items of this nfoNote.