DPROD
DPROD is the Data Product Ontology work initiated by the EKGF Data Product Workgroup and carried forward through the OMG Enterprise Knowledge Graph Forum. The EKGF DPROD page describes the proposed OMG standard for describing data products using W3C Linked Data technologies. DPROD builds on DCAT and adds data-product concepts such as input ports, output ports, quality, governance, and accountability.
Buyer question
“Can Legra publish workspaces as governed data products instead of just storing graph data?”
Legra fit
| Assessment area | Legra fit | Status |
|---|---|---|
| Data product identity | A Legra workspace can be treated as the operational unit behind a data product: encrypted, versioned, queryable, and owned. | Native fit |
| Decentralized publishing | Legra’s peer-to-peer architecture and workspace model match DPROD’s decentralized data-product intent. | Native fit |
| Catalog metadata | Legra publishes workspace and Data Product metadata through DCAT-oriented federated catalogs. | Integrated |
| Product ports | Query endpoints, graph services, exports, and Workspace App surfaces serve as output ports. Loaders, ETL workflows, and branch-based imports serve as input ports. | Integrated |
| Contract vocabulary | DPROD Contracts describes data offers, bilateral data contracts, permissions, duties, prohibitions, schedules, deadlines, and deterministic policy evaluation as an ODRL profile. Legra applies that model to graph-based agreements. | Emerging standard |
| Contract formation and acceptance | Identities, catalogs, offers, workspaces, branches, and signed activity form one offer-to-contract flow with explicit bilateral acceptance. | Integrated |
| Runtime enforcement and settlement | Story execution enforces contract authority while Journal evidence and token accounting connect usage to contract-driven settlement. | Integrated |
What Legra can say
Legra makes a workspace publishable as a data product: data, schema, rules, provenance, ownership, access, and versions can all live in the same graph-controlled asset.
That gives a buyer a clean operating model:
- The workspace is the controlled data-product boundary.
- Branches and commits describe product versions and change history.
- SHACL and validation rules describe product quality requirements.
- PROV-style provenance records who created, changed, reviewed, and merged product content.
- Encryption and workspace membership describe who can read the product.
- DCAT/DPROD metadata can describe the product for discovery and marketplace use.
Assessment boundary
DPROD conformance is not one binary feature. Vocabulary support, catalog publication, contract authoring, bilateral acceptance, policy evaluation, runtime enforcement, usage evidence, and economic settlement remain distinct layers. Legra connects them through workspaces, catalogs, validation, provenance, Stories, the Journal, identity, and token accounting while DPROD itself continues to evolve as a standard.