OpenDocument - Adv Document Collab SC

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Jos, I was replaying the comments about WebODF and I don't think they are using an immutable document target. I say that because the point of the operations is to re-calculate the off-sets of each change against others and then make some sensible ordering of them. If they truly had an immutable target, no operation would change the offset of another operation, unless and until you decided to generate a new document instance. Yes? At that point you would have to calculate the offsets because you want a new ordering of the document. Up to that point, changes are just projections into the existing document, there are no "offsets" unless and until the changes are accepted. I am probably missing something but it sounds like WebODF is building a temporary "new" document, which does require the offsets for display to users. That is one strategy but projecting the changes into the text without actually changing the original text would avoid the recalculation unless and until a user accepts the change. Yes? Hope you are at the start of a great day! Patrick - -- Patrick Durusau patrick@durusau.net Technical Advisory Board, OASIS (TAB) OpenDocument Format TC (OASIS), Project Editor ISO/IEC 26300 Co-Editor 13250-5 (Topic Maps) Another Word For It (blog): http://tm.durusau.net Homepage: http://www.durusau.net Twitter: patrickDurusau -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBAgAGBQJWlxtSAAoJEFPGsgi3MgycHp0QAIM1y/+vM4EvyUsRUwNBYufT JJXB6oyIUH+1+X04ZCNs2WFd7syUdJ9V+0Iefiz+dyYjt8VToLhgkZ66/9USQ4z3 7VPrLiPGrAYm8vxD+Phs/GupPpG0yL2alYGqGd0X14Xss8w5vB4mmec+Vh34MYjL Ocnfymcr6FbJU7O8M5U7xbMMZkvKEZFJYN/mLbqRej48JktMb0V70cFKj+L12Rui Vg8m4vkQsTM2zxqMKIIqczH8bfFYSdBNv+lCuwLAyoOcHHf2Pt+62SdkKUcDnyMc oK5DHLJ2K18TmM2sSj/tUk+Ot9Oagej3NXEYY2biUgtEfSTzRAzHerCr12QHU0gn iAeeOPPKOQT6VwuRK7y6UsftLZVHXCQ0F165dd2uARz5nIdqOddto4RteGnMVZ54 u/ZjPYf+nz09Axmj704VTe3qRo8BalshveZtTNLxNdLVE7LT2YbgvX2em5UDFeFN OCHSz/SY0z1Zb9zIPSYa8qh5c9orsWEoAPOx4U2Q90bmCIuhss9LOh1UFJee+1Rn EcWqmTpFxTWLNs9feilG8+FKr01RpJ7u641v1bOHTXvDW4XeTDKIVVmV4HAvdVtq RqlXNaiJOE8vnw60HdMgnG1rX+vgy24HrLh+j5uKON//v5eBbp8j5rG5FhJVxEm4 /mN1dSfVlifJbkbQ7pDA =Inlw -----END PGP SIGNATURE-----

On Wednesday 13 January 2016 22:51:47 Patrick Durusau wrote: > I was replaying the comments about WebODF and I don't think they are > using an immutable document target. > > I say that because the point of the operations is to re-calculate the > off-sets of each change against others and then make some sensible > ordering of them. > > If they truly had an immutable target, no operation would change the > offset of another operation, unless and until you decided to generate > a new document instance. Yes? That is true. The current mode of WebODF is to create operations on the latest state of the document. It could have a mode where the operations work on the initial document. Operations usually are very small. Just typing 'h' is an operation. So the operation 'e' that follows it makes most sense as an operation that follows the 'h' operation. If both operations work on the initial document, the outcome would be indetermined. The operations could be merged: 'h' + 'e' = 'he'. Operations that are independent could be store relative to the original document. The server could even be clever and transform operations that work on a later version of the document back to work on the original document. > At that point you would have to calculate the offsets because you want > a new ordering of the document. > > Up to that point, changes are just projections into the existing > document, there are no "offsets" unless and until the changes are > accepted. > > I am probably missing something but it sounds like WebODF is building > a temporary "new" document, which does require the offsets for display > to users. > > That is one strategy but projecting the changes into the text without > actually changing the original text would avoid the recalculation > unless and until a user accepts the change. > > Yes? WebODF needs to have the latest version of the document in the user view because the document also includes the cursor positions. But it does keep an older version of the document and the stack of operations that have been applied to it around. In WebODF the document state is the DOM in the browser. Cheers, Jos