ATLAS core DB meeting.
We have equated sharing and placement categories.
Added "dataset".
Data access is by EDO. EDO's are stored in self-describing files. Relational DB's help to located files and data in files.
HES support multiple file formats (start with root).
HES EDO references are handled in a layer above the different file formats.
Introduce HES store view which exposes a well-defined subset of the data for a given event. This is the visible input data.
Within a view, type-keys are unique and data is accessed in this manner.
References between objects in EDO's are expressed as an EDO ID plus an index givin the location of the object in that EDO.
References can be followed beyond visible data. This scope is also defined by the store view.
An EDO reference may be satisfied by the original EDO or by a replica in another file.
Output data can include visible input and new data.
Athena/StoreGate supports store types beyond HES (ZEBRA, Oby?)
Possibility of references between store types is foreseen but implementation may be limited or may have the possibility of ambiguity.