All Classes and Interfaces
Class
Description
The bridges and readings authored beside the model files: what a retrievable class stands
for in IKE's own terms, and which statement reading each of its elements answers.
What a retrievable class stands for.
Which statement reading an element answers.
Where every imported model component gets its identity (IKE-Network/ike-issues#1115):
derived, never random.
Reads a model information file into the store as knowledge (IKE-Network/ike-issues#1115):
a concept for the model under the Data model parent, a concept for each class under its
base class, its name and label read in the model's dialect, its definition as the file
writes it, a class that extends a System type or has no base under the model's concept, since
nothing hangs under the catalog's types, a record for the model and for each class with every field verbatim and IKE's
resolution beside it, a record for each element with its type as a tree of the catalog's
type specifiers, and records for the contexts, the relationships, the conversions, and the
required models.
What an import did.
A model information file that cannot be imported, refused with its place: which file, which
class or element, and what was missing or could not be resolved.
A model information file as the CQL translator writes it, read as it is: the model's own
facts, the models it requires, its classes with their elements, its contexts, and its
conversions, every attribute verbatim.
One class as the file writes it.
A context a library may run in.
A conversion between two types.
One element of a class, every attribute as written.
The forms a type specifier takes in a shipped file.
How a class reaches a context.
A model this model requires.
A type as the file gives it, in one of its four forms.
Writes a family of IKE's own patterns as model information (IKE-Network/ike-issues#1115),
so that a library can be written against IKE's own knowledge.
The data models as the store holds them after import: each model with its name, version,
and url, each class with its model and its base, so that a type name met in a library
resolves to the class concept and a class concept writes back as the name a library uses.
A class in the store.
A model in the store.