1.1 Glossary

This document uses the following terms:

clock vector: A replica key/tick count pair that represents updates to a replica. Any change that occurs between 0 and the tick count is contained in the vector.

knowledge: The metadata that is maintained by each participant that describes all the changes it has tracked. In its simplest form, known as a watermark, a knowledge item is a clock vector that consists of pairs of replica keys and replica tick counts.

range: A set of continuous item identifiers to which the same clock vector applies. A range is represented by a starting point, an ending point, and a clock vector that applies to all IDs that are in between.

replica: A particular repository of file and directory information to be synchronized, and the metadata store that represents that repository.

synchronization community: A set of replicas that keep their data synchronized with one another.

tick count: A monotonically increasing number that is specific to a replica and combined with a replica key to make a version.

version: A marker that is used to represent an item that has been deleted. A tombstone is used to track deleted items and prevent their reintroduction into the synchronization community.

MAY, SHOULD, MUST, SHOULD NOT, MUST NOT: These terms (in all caps) are used as defined in [RFC2119]. All statements of optional behavior use either MAY, SHOULD, or SHOULD NOT.