[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [office-collab] Use Case - H.1 Formula and Number Modification Example - MCT - 1. Draft
Svante, Quick question on volatile elements: On 02/21/2012 07:46 PM, Svante Schubert wrote: <snip>
By the above dependencies the XML changes are mapped into basicallytwo state changes, which can be mapped to two operations to be serialized using Merge-Enabled Change Tracking (MCT): 1. The change of cell value [.B4] 2. The change of the formula of cell [.C4] and the resulting cell value& paragraph text changeUnfortunately this only suffices as long as the office:value change is a deterministic consequence of a formula change. Simple recalculation of a document could change values without any accompanying formula changes (think of random number generation or other volatile functions such as date, time,....)You are right. Not only the change of a formula, but as well the recalculation will trigger the described changes. In addition due to random functions it will never be sufficient to have an operation indicating the recalculation of formula, but the results are important.
Question: Wouldn't the question of recalculation be covered in part by Part 2, section 3.5 When recalculation occurs?
That is change tracking would be constrained by the definitions for formulas therein?
Yes? Hope you are having a great day! Patrick -- Patrick Durusau email@example.com 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) OASIS Technical Advisory Board (TAB) - member Another Word For It (blog): http://tm.durusau.net Homepage: http://www.durusau.net Twitter: patrickDurusau