Document Metadata

# Document Metadata Design Proposal

> This feature isn't implemented yet

I'm planning on adding metadata support to documents. The idea is to add a sidechannel for data like creation time, cursor positions, connected users, etc.

## New document interface

A document will consist of:

• Version: A version number counting from 0

• Snapshot: The current document contents

• Meta: (NEW) An object containing misc data about the document: - Arbitrary user data, set when an object is created. Editable by the server only. - creator: Name of the user agent which created the document, if the user agent has agent.name set. - ctime: Time the document was created - mtime: Time the last operation was applied. This is updated automatically on each client when it sees a document operation. - (Removed) _**contributors**: List of users which have ever edited the document._ - sessions: An object with an entry for every agent that is currently connected. Map agent.sessionId to:

  • name (optional, filled in by agent.name)
  • Cursor position(s) (type dependant - for text it'll be a number, for JSON it'll be a path)
  • Connection time maybe?

  • Any other application-specific data. This can be filled in by the auth function when a client connects. (And maybe clients should be able to edit this as well?)

Unlike the document data, metadata changes will not be persisted. Metadata changes will not bump the document's version number.

Initial document metadata can be set at document creation time.

Some metadata fields like last modified time and cursor positions will be updated automatically on all clients whenever an operation is submitted.

## Metadata operations

We also add a new kind of operation, a meta operation. I've thought about using the JSON OT type for this, but it means that if someone wants to implement the sharejs wire protocol, they have to implement JSON OT (which is really complicated). So I'm going to keep it simple. I'll use a simplified version of the JSON OT type.

Metadata operations express changes in the metadata object. They look like this:

• Version: Document version number on which the metadata change is based
• Path: List of object keys to reach the target of the change. All path elements except the last must already exist. An empty path
• New value: (optional) JSON object which replaces whatever was at the metadata object before. If this is missing, the object is removed.

Eg:

Add session 'abc123': {v:100, p:['sessions', 'abc123'], v:{name: 'sam', ctime: 123, cursor:0}}

Metadata gets consistency guarantees by restricting which sections of the metadata document each client is allowed to access.

## Transforming cursor positions

Types can also specify cursor transforms. This is important to make cursors move as you edit content surrounding them.

TYPE.transformCursor = (position, operation) -> newPosition

Clients are responsible for updating cursor positions in two scenarios:

• When they generate operations locally they transform everyone's cursor position by the operation
• When they receive updated cursor positions from the server against an old version

The server will pre-transform cursor positions before rebroadcasting them.

## Expected usage

• A new client connects - the server will add an entry corresponding to the client in the session data
• A user moves their cursor - they send a metadata op which is broadcast via the server to indicate their new cursor position. (Note that cursor positions may be more complicated than just a number. Imagine a user exploring a spreadsheet...)
• The client sees a new document operation It updates the last modified time of the session data using its local clock. It doesn't tell anyone else - they'll each have each made the same change locally as well.

#### Still to figure out

• Are clients allowed to make arbitrary changes to the document's metadata?
• What is the client API for querying cursor positions and getting notified of metadata changes?