A record may look as follows:
(root) title Mountain hike time start 2015-08-05 09:00:00 UTC end 2015-08-05 17:00:00 UTC confirmed attendees John # 34bf..7e Bob # a529..10
Each tree node of a record contains:
- a byte sequence of length 0 or more
- an optional hash, linking another Condensation object
Nodes are ordered, but the order does not always matter. The root node is not stored.
Byte sequences may contain arbitrary data. Their encoding and interpretation is protocol- or application-specific. The following encodings are suggested:
|Data type||Value (byte sequence)|
|Text||A UTF-8 sequence of Unicode characters.|
|Boolean value||true: a non-zero-length byte sequence, usually 0x79 (ASCII "y")
false: a zero-length byte sequence
|Integer with sign||A big-endian signed integer.|
|Integer||A big-endian unsigned integer.|
|Fixed-point number||A signed or unsigned integer shifted by a predefined number of bits.|
|Floating-point number||A single-precision (4 bytes) or double-precision (8 bytes) IEEE floating point number.|
|Reference to an
|An empty byte sequence, and the object hash.|
|Reference to an
|The AES key (32 bytes), and the object hash.|
|Date||A signed integer, denoting the number of milliseconds that have passed since epoch.|
|Revision||An unsigned integer, denoting the number of milliseconds that have passed since epoch, or 0 to indicate that no revision has been stored yet (far past).|
Since the overhead of a node is small, it is usually not worth packing multiple values into a single node, and easier to create a small subtree. An exception are arrays of a fixed-length data type, such as arrays of 4-byte integers.
Records, or parts thereof, may be interpreted as key-value dictionaries:
(root or parent) key 1 value 1 key 2 value 2 ...
Key nodes usually hold a short ASCII sequence — preferably using lowercase characters, spaces and dashes only — and must be unique. Their order has no importance.
The corresponding value is stored in the child nodes. Often, there is only one such value node for each key.
Records, or parts thereof, may be interpreted as tables:
(root or parent) primary key of row 1 content of cell A1 content of cell B1 ... primary key of row 2 content of cell A2 content of cell B2 ... ...
The first row may contain column headers.
A record object has the following structure:
Nodes are stored in depth-first traversal order. The root node is omitted. Each node is encoded as follows:
The bits of F have the following meaning:
Bits 6 and 7 along with the node order encode the tree structure.
L and H are stored as unsigned big-endian integers of the indicated length. H is the index of a hash in the object header. Multiple nodes may refer to the same hash.
Merge semantics are application- or protocol-specific.