You should probably just use geo json on top of sharejs. But...
The documentation is better than you'd expect - OT types (including
json0) implement the API defined here:
https://github.com/ottypes/docs
Its O(j*k) where j and k are the complexities of the two operations
being transformed. In practice, its not a big problem. Very few
operations are actually concurrent. But yeah - I'm still looking
forward to doing json2 with you sometime jeremy... I have some time
now too...
I made a little toy using the JSON OT type directly to (in memory)
share a document between the client and server. Its here:
https://github.com/josephg/appstate
.. It turns out it only takes a few hundred lines to get something
working with OT without using sharejs.
-J