Entity is a snapshot of a server-side entity instance. It is an immutable object associated with an entity instance which has some of its attributes materialized during a load operation. The set of loaded attributes depends on the projection used in load operation. Entities are created using a creator object of the corresponding type and entity attributes are updated using the corresponding updater object. From an object model point of view, an entity is a tuple with a globally unique entity ID and an optional name. An entity's name is mutable. Virtually all manipulable objects are entities. Access to every entity is controlled through access control rules. Basically, each entity can define one or more operations that can be performed on it and for each operation specify one or more privileges that the requesting actor must carry in order to be allowed to perform the operation. Note that we allow owner to be either a single actor, or a group. The actor that made the entity come into existence is the creator of the entity and this value cannot be changed. Each entity can have zero or more labels associated with it.

Below are examples in XML formats. All examples are shown with all inherited members. Quoting when required is part of the examples, but you must obviously populate with your own data.