Skip to main content
Version: 2.0.0

Glossary

Model Forge uses a small, fixed vocabulary. Code and documentation use only these terms, defined below. The decision behind this vocabulary is ADR 060. For platform-wide terms (outside Model Forge's own vocabulary), see the site-wide Glossary.

Core terms​

Model Artefakt (artifact)​

Umbrella term for any persistable CORE unit: Element, DataStructure, Mapping, DataSource, DataSink, Pipeline, DataSetDatasetA data-related element that contains processed data and makes it available for consumption. A Dataset is populated via Pipelines and carries Metadata and access permissions.. Every artifact has a stable CORE URN identity and is versioned.

Element​

The umbrella for a single modelled domain type — a Class, an Enumeration, etc. An Element is a JSON Schema 2020-12 document whose $id is a versioned CORE URNCORE URNThe global identity Model Management assigns to every model artifact: a unique, stable and versionable URN that exists independently of storage location, file names or registry technology.. It carries version, name, description, URN.

DataStructure​

A stored grouping of Elements. Importing one JSON Schema document (a root, optionally with $defs) automatically creates one DataStructure that references the resulting Elements by URN — the module / provenance grouping ("these Elements were authored and imported together"). The DataStructure is named after the imported document's title and is managed as its own registry artifact through the ModelForge facade. A DataStructure is a stored artifact, not a View — it carries no content of its own and its members are fetched individually by URN (see ADR 060).

Mapping​

A declarative field mapping from a source Element to a target Element, both referenced by URN. Per target field it describes an operation (copy, concat, const, format, …) over the source payload. A Mapping is a stored, versioned artifact with its own CORE URNCORE URNThe global identity Model Management assigns to every model artifact: a unique, stable and versionable URN that exists independently of storage location, file names or registry technology..

DataSource​

The declaration of an inbound data sourceData sourceA data-related element that represents the origin of data. It defines how data is connected, accessed, and ingested into the Platform, such as an external database or sensor network. (e.g. an MQTT topic or a database query) whose payload binds to an Element by URN. A DataSource is a stored, versioned artifact with its own CORE URNCORE URNThe global identity Model Management assigns to every model artifact: a unique, stable and versionable URN that exists independently of storage location, file names or registry technology..

DataSink​

The declaration of an outbound target (e.g. an HTTP endpoint) whose payload binds to an Element by URN. A DataSink is a stored, versioned artifact with its own CORE URNCORE URNThe global identity Model Management assigns to every model artifact: a unique, stable and versionable URN that exists independently of storage location, file names or registry technology..

Pipeline​

A dataflow graph of nodes and edges that wires DataSources through Mappings into DataSinks. A Pipeline references the participating artifacts by URN and is itself a stored, versioned artifact with its own CORE URNCORE URNThe global identity Model Management assigns to every model artifact: a unique, stable and versionable URN that exists independently of storage location, file names or registry technology..

DataSet​

An integration composition: a manifest that references Elements, Mappings, Pipelines, DataSources and DataSinks by URN (the *Refs arrays). Where a DataStructure groups Elements by provenance, a DataSetDatasetA data-related element that contains processed data and makes it available for consumption. A Dataset is populated via Pipelines and carries Metadata and access permissions. composes artifacts of all types into a deployable unit (see ADR 051).

Bundle​

A View that renders an artifact together with the (complete) graph of the artifacts it connects to, as one self-contained document. The bundled (embedded $defs) and inlined schema projections are both Bundles.

Format​

A View that serialises an Element in a chosen representation — JSON Schema or XSD. An Element's format is recorded per version (see ADR 058).

View​

Umbrella for a read-side projection of stored artifacts — currently Bundle and Format. Views are generated on demand and never stored (see ADR 055).

Relationships at a glance​

  • DataStructure and DataSetDatasetA data-related element that contains processed data and makes it available for consumption. A Dataset is populated via Pipelines and carries Metadata and access permissions. are both manifests of artifact URNs: DataStructure is Element-only and import-scoped; DataSetDatasetA data-related element that contains processed data and makes it available for consumption. A Dataset is populated via Pipelines and carries Metadata and access permissions. is all-types and composition-scoped.
  • A Bundle is a View over an artifact and its dependency graph; Format is a View choosing the serialisation. Both are kinds of View.
  • There is no RDF/Linked-Data (JSON-LD) projection.