Perhaps I haven't absorbed all this sufficiently yet, but I've had a reservation about MCT I've never understood enough to fully prove. Doesn't all this relative positional referencing cause difficulty for an implementation? As Svante noted early in the thread:
>As result to this the numbers of the arguments might be increased (or decreased) when the operation is being moved up/down, as components earlier counted have or have not existed before. So each time an arbitrary change is rejected or the document content is altered (change-tracked or not), the numerical references of some/all the change tracking markup may be invalidated and must be recalculated by the application, right? That seems like a significant and unavoidable burden. I was a hardware guy in school, not a software/algorithms guy, but that has to be unpleasant big-O behavior! Or am I (hopefully!) wrong in my understanding? John
