Frameworks & Standards
Assess data products with DPROD
DPROD is the Data Products Ontology specification from OMG. As checked on 18 October 2026, OMG lists version 1.0 beta 2 as an in-process specification, with an ontology and SHACL constraints. Select a version before assessing conformance.
The EKGF DPROD introduction explains its use of Linked Data to describe products, their owners and ports. The mapping below is a Legra assessment, not an OMG certification.
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 | Workspace owners can publish governed data products for use across organizations. | Native fit |
| Catalog metadata | Legra publishes workspace and Data Product metadata through DCAT-oriented federated catalogs. | Native fit |
| 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. | Native fit |
| 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. | Partial fit |
| Contract formation and acceptance | Identities, catalogs, offers, workspaces, branches, and signed activity form one offer-to-contract flow with explicit bilateral acceptance. | Native fit |
| Contract use and settlement | Agreed permissions govern product use, while usage records support review of contractual obligations and charges. | Native fit |
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, usage evidence, and settlement require separate assessment. Choose the DPROD profile relevant to your product and verify its requirements against the publication and contract workflow you operate.
Start with a small dataset
Use the first graph walkthrough to upload and query a named graph. Then review a change on a branch. These exercises establish the data and change-review workflow; they do not constitute DPROD publication or conformance testing.
For the business explanation, see governed data products.