Change-Tracking Draft Structure

[Svante Schubert <svante.schubert@gmail.com>]

Dear group,

The main deliverable of our subcommittee is the specification of the
new  ODF change-tracking (CT).
To be able to track our progress and estimate the future delivery date,
it seems reasonable to already start with a draft.

I remember that Patrick and Rob discussed once in a TC meeting that the
definition of change-tracking might be suited to become a new part of
the ODF spec due to its distinction and volume.
In addition Patrick noted on last SC call, that a main structure could
look like:

1. New CT
2. Old CT             // deprecated
3. Transition from old to new

I have added some more details to the first part of our new change-tracking:

1.1 Concepts
1.1.1 ODF Document as Component Tree
1.1.2 Component & Properties
1.1.3 Component Operations

1.2 ODF 1.3 Feature Set // ECT feature proposal as our given default
feature set for ODF 1.3
1.2.1 Components & Properties   // detailed specification, e.g. root
element and XML nodes
1.2.2 Component Operations  // detailed specification, i.e. ODF XML
change based on an ODF normalization

1.3 Change Serialization in ODF

Have I overseen something? Any improvements to be made?

PS: Just a small reminder, today is our SC change-tracking call!

Best regards,
Svante