Data interoperability#
Part of the LDT Governance and Trust Framework — instantiates the iSHARE Data Space Template pillar Data Interoperability (© iSHARE Foundation, see Legal notices).
Purpose#
For a data space to function, people and systems must interpret shared data the same way. That has two sides: semantic interoperability — agreeing what a term means — and technical interoperability — agreeing on syntax, formats and interfaces. On top of that sits the evidence question: where data came from, how it has been used and by whom, which is what provenance and traceability provide for auditing and regulated use.
LDT instantiation — where we stand#
The LDT interconnects twins that were not built to a common model: two city twins, an airport and a port, on different stacks. The scheme therefore does not mandate one canonical twin model. Instead it fixes the boundary:
- Common semantics apply to what crosses between twins — indicators, emissions figures, locations, time — not to each twin's internals. Alignment targets are the iSHARE vocabulary for scheme-level concepts and established domain models for the rest; see Data models.
- Every cross-twin flow is exchanged over a documented, open interface and is subject to the scheme's enforcement layer; see Data exchange.
- Where a figure is used as evidence — a CO₂ saving, a policy effect, a token issuance — provenance is not optional; see Provenance, traceability & observability.
That third point is the one most likely to be underestimated: the Marketplace of the EU LDT Toolbox and the CO₂ tokenisation service turn twin outputs into claims with financial consequences, and a claim without provenance cannot be audited.
Blocks in this pillar#
| # | Block | Owner(s) | Status |
|---|---|---|---|
| T1 | Data models · guiding questions | iLabs + LogiNex + cities | OPEN |
| T2 | Data exchange · guiding questions | iLabs | OPEN |
| T3 | Provenance, traceability & observability · guiding questions | iLabs + iSHARE | OPEN |
PD4 mapping#
Feeds PD4 chapter 5 (data & data-model sharing) and chapter 7 (assurance, compliance & operations).