[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Additional use case for change tracking
Greetings! Apologies for the slow posting! The only additional requirement uncovered by the select committee is:Nested change tracking, which the committee takes to mean, with change tracking on:
1st case: 1st author creates a text, saves it and transfers it to 2nd Author. The 2nd author makes changes. The 2nd author transfers the text back to the original author.
The 1st author makes changes to the changes made by the 2nd author.2nd case: Author creates a text and saves it (not auto-save). After manual save, author makes changes to the text. After another manual save, the author makes changes to their changes. (The manual save was suggested as a session marker for engagement of change tracking.)
Advocates of change tracking proposals should post (email is fine) examples of how their proposals handle nested change tracking as illustrated by these two cases.
Hope everyone is having a great week! Patrick -- Patrick Durusau email@example.com Former Chair, V1 - US TAG to JTC 1/SC 34 Convener, JTC 1/SC 34/WG 3 (Topic Maps) Editor, OpenDocument Format TC (OASIS), Project Editor ISO/IEC 26300 Co-Editor, ISO/IEC 13250-1, 13250-5 (Topic Maps) Another Word For It (blog): http://tm.durusau.net Homepage: http://www.durusau.net Twitter: patrickDurusau