Corporate metadata
Glossary, functional and technical dictionary, lineage and ownership remain the responsibility of DATUM Core.
DATUM · Technical fit
How DATUM participates in sharing ecosystems
DATUM acts as the internal platform for governance, industrialisation and publication. The Data Space Gateway adds the external interoperability layer without breaking the internal model.
Three separation layers
DATUM Core
Internal governance unchanged
Gateway
Governed federated boundary
Ecosystem
Partners · Platforms · Europe
What DATUM keeps doing internally
Internal governance does not change. It extends.
DATUM remains the platform that governs data within the organisational perimeter. The Gateway does not replace that function; it projects it outward.
Governance and quality
Quality rules, scorecards and the internal governance model are not altered or outsourced.
DataOps and publication
The DataOps circuit continues to operate internally. Governed publication to the business does not change.
Data products
Data products to be shared are defined, certified and versioned within DATUM before being exposed.
The principle
DATUM does not replace internal governance.
It extends it outward.
What the Gateway adds
Three layers: DATUM Core · Gateway · External ecosystem
The Gateway acts as a governed boundary between the internal perimeter and the external ecosystem, without exposing the corporate core.
DATUM Core
Internal governance · Metadata · DataOps · Data products
Data Space Gateway
Negotiation · Policies · Identity · Agreement registry · Federated connectors
External ecosystem
Partners · Suppliers · Sectoral platforms · European data spaces
Separation of responsibilities
What stays inside and what is managed at the federated edge
Within the perimeter (DATUM Core)
Definition and governance of the data product
Internal metadata, quality and lineage
DataOps and production circuit
Functional ownership and internal policies
Internal catalogue and publication to the business
At the federated edge (Gateway)
External catalogue of published assets
Policy layer and usage policy model
Federated connector and interoperability
Agreement registry and evidence
Identity and trust validation
Governed entry of external assets
Benefits
Why this separation matters commercially and technically
No governance duplication
The catalog, metadata and quality rules exist only once in DATUM Core. The Gateway projects them outward without replicating them.
1 unified governance model
Projected, not fragmented governance
Internal policies translate automatically to the external ecosystem language. The organization keeps its model, it does not adapt to each participant.
Policies translated to ecosystem
Clearly delimited federated edge
What enters and leaves the perimeter is formalized: which assets are externalizable, under what conditions, with what identity. The boundary is decision, not accident.
External boundary formalized
Independent Core operation
The Gateway can be updated, scaled or evolved without touching DATUM Core. External capability does not compromise internal operation.
Decoupled deployment
What changes
When Core/Gateway separation is operational
Minimal latency between Core and Gateway
Projecting internal governance to the external ecosystem is virtually immediate. Internal policy changes reflect at the federated edge without parallel projects.
Synchronization in minutes
Cross-perimeter traceability
Shared data lineage connects the internal Core with the external ecosystem. Audit can walk the complete data path without jumps.
End-to-end lineage
Policy coverage over assets
Every publishable asset has its policy applied. No orphan assets remain at the federated edge.
100% assets with policy
Maturity of the extension model
Internal governance projects in a measured way: assets are not externalized before being ready. Progression is controlled, not opportunistic.
Auditable extension model
Keep exploring
Go deeper into how it works
dsg.como.related.lead
Next step