[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: XLIFF 2.1 csprd02: Comments on text in section 5.6.1
Because the Change Tracking Feature is an optional module that can be legally ignored by Core only Modifiers, the only safe way how to record a version of content that can be reintroduced as result of a roll back is to store the whole unit data within the Change track item element. Contrary to generic change tracking or versioning approaches, it's not enough to store just your changes. Alternatively, you can store the whole unit content as a revision before you start making your own changes and store just your changes as the most recent revision.
Because the Change Tracking Module is optional and can be legally ignored by Core only Modifiers, the only safe way to record a version of content that can be reintroduced as the result of a rollback is to store the whole unit data within the Change Track item element. Contrary to generic change tracking or versioning approaches, it's not enough to store just your changes. Alternatively, you can store the whole unit content as a revision before you start making your own changes and store just your changes as the most recent revision.
Alternatively, you can store the whole unit content as a revision before you start making your own changes and store just your changes as the most recent revision.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]