d140801b6.txt 0.01                    UTF-8                     dh:2015-02-01

                 PROGRESS REPORT: PROTECTED CHANGE-TRACKING
                 ==========================================

                   DCHANGES 2014 POST-PROCEEDING REVISION
                   --------------------------------------

The files  provided for the post-workshop revised submission of the
paper are in the package

    d140801b6-PCT-2014-10-17-1848-Revision.zip

The 4 components are

d140801b6.txt This manifest and description

PCT-2014-10-17-1848-ProtectedCT-Revision.doc
    Microsoft Office Word 97-2003 document file of the post-workshop
    revision submission. 3 pages.

PCT-2014-10-17-1848-ProtectedCT-Revision.pdf
    PDF/A of the post-workshop revision that was submitted for the
    revision review.

PCT-2015-01-09-1550-RevisionReviews.txt
    E-mail acceptance of the Revision for the post-workshop procedings
    abridged to exclude the previous review comments and present the
    new ones that are to be reflected in the final "camera ready" version.

ABSTRACT

    Change-tracking of digital documents leads to document altera-
    tion in some manner. Protected Change-Tracking (PCT) is a
    response to the question, “How can one protect word-processing
    documents against alteration, verifiable by digital signature,
    and make signed amendments that are verified to be allowed modifi-
    cations of the original document?”  A genealogical model is iden-
    tified that preserves the digital signature of the ancestor and
    each change-tracked descendant. PCT achieves a subset of genealogi-
    cal cases having practical simplicity. Applicability to documents
    in ODF format is sketched.

CONTENT
Abstract
 1. INTRODUCTION
 2. GENEALOGICAL PROTECTION
    2.1 Document Genealogy
    2.2 Manifest Equivalence
    2.3 Practical Constraints for Interchange
 3. PCT APPROACH
    3.1 Limiting Conditions
    3.2 Authentication
 4. SUPPORTING PCT IN ODF
    4.1 Preparing the First Generation
    4.2 Subsequent Generations
 5. CONCLUSION
 6. ACKNOWLEDGMENTS
 7. REFERENCES
    [1]	Donald Eastlake, Joseph Reagle, David Solo, Frederick Hirsch, and
        Thomas Roessler (editors).  XML Signature Syntax and Processing
        (Second Edition), W3C Recommendation 10 June 2008.
        http://www.w3.org/TR/2008/REC-xmldsig-core-20080610/
    [2]	ETSI. XML Advanced Electronic Signatures (XAdES), ETSI TS 101 903
        v1.4.1 2009-06-15.
        http://webapp.etsi.org/workprogram/Report_WorkItem.asp?WKI_ID=28064
    [3]	Dennis E. Hamilton. Tracked Changes: Navigating the Document-Format
        Anti-Pattern. DChanges 2014, September 16, 2014, Fort Collins,
        Colorado, USA. To appear.
    [4]	OASIS. Open Document Format for Office Applications (OpenDocument)
        Version 1.2 Part 1: OpenDocument Schema. 29 September 2011 OASIS
        Standard.  Available at http://docs.oasis-open.org/office/v1.2/os/
    [5]	OASIS. Open Document Format for Office Applications (OpenDocument)
        Version 1.2 Part 3: Packages. 29 September 2011 OASIS Standard.
        Available at http://docs.oasis-open.org/office/v1.2/os/
    [6]	PKWARE. APPNOTE.TXT - .ZIP File Format Specification Version 6.2.0,
        2004-04-26. Available at
        http://www.pkware.com/support/application-note-archives


0.01 2015-02-01-14:43 Incorporate Reviews of the Revision
     The reviews of the revision are added.  These are to be reflected
     in the final "camera ready" version.
0.00 2014-11-03-13:36 Collect the Revision Material
    The two forms are packaged with a manifest for archival preservation
    on the nfoWorks.org site.

                         *** end of d140801b6.txt ***