office-collab — archive
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
— [Date Index]
| [Thread Index]
| [Month Index]
| [List Home]
Groups - Conference call to discuss use case solutions UC4-UC8 added
Agreed that producers often consolidate changes that can be viewed as single ones into a single change. However, when different users do it, that is generally not allowable, including when the original user does more that involves change by the intermediate author. I don't know how to make that statement about ECT. It might be true, but I am not confident about it. There is probably something that can be done with a graph-theoretic depiction of the cases that might demonstrate closure on this question. I haven't undertaken anything like that. I was only commenting about interdependent attributes and what happens when they are changed (by inheritance even) and then changed more. This is not about the broader problem you raise in your reply. I think that is an interesting problem. I wasn't going there. Just pointing out that semantics and interdependence are inescapable in ODF, even at the attribute level.
- Dennis PS: Since ODF 1.2 does not track moves, there is no experience with that in current implementations of ODF. I believe those are very interesting cases, and they impinge on cut-and-paste rules too, perhaps. It is interesting to see how clip-board involvement is handled now, although there is no clue in the ODF 1.2 specification of tracked changes.
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
— [Date Index]
| [Thread Index]
| [Month Index]
| [List Home]