A Chronicle records the state of some subject at different times. It consists of {@link Series} and {@link Attribute}s.
An example of a subject for a chronicle is a traded security, like a share, with price and trading volume changing all the time, and with company information and trading currency remaining constant. Another example is the climate at a location, with varying temperature, humidity, pressure, wind speed, and wind direction, and with fixed geographic coordinates.
A chronicle, seen as a collection, can include other chronicles as members, and the members can in turn include more members. All chronicles in a database form a tree, with the root known as the top chronicle. This structure is reflected in the {@link NamingPolicy}of the database, which defines the syntax for naming chronicles. The tree structure allows the design of very large collections of chronicles using only a few schemas.
Fast access to chronicles using attribute values is provided by {@link Property#getChronicles(Object,int)}.
@author Jean-Paul Vetterli
@version 1.0.0