Model
Core Concepts
The building blocks of every DPROD description. Each concept links to its normative definition in the specification.
Data Product
A rational, managed, and governed collection of data with purpose, value, and ownership, meeting consumer needs over a planned lifecycle. Data products have input and output ports, code, and metadata.
Normative definition in the specPorts (Data Services)
Digital interfaces that provide access to datasets. Input ports bring data into the product, while output ports share generated data. Ports specify connection details, formats, and link to datasets with shared schemas.
Normative definition in the specDistributions
Physical representations of data — CSV, JSON, Parquet, and access methods. A single dataset may have multiple distributions to serve different consumer needs without duplicating the underlying information.
Normative definition in the specDatasets
Logical models of the data that can conform to shared standards like FIBO, CDM, or custom ontologies using SHACL or OWL. The schema lives with the data, not in out-of-band documentation.
Normative definition in the specUse cases
Where DPROD delivers its value. Each use case is reinforced by the same small vocabulary — no per-project extensions required.