Data value creation enablers#
Part of the LDT Governance and Trust Framework — instantiates the iSHARE Data Space Template pillar Data Value Creation Enablers (© iSHARE Foundation, see Legal notices).
Purpose#
A data space exists to create value, not only to share safely — and that requires participants to know what is available. Three blocks make it possible: descriptions of data, services and offerings in a form others can understand; publication & discovery so those descriptions can be found, over standardised endpoints and along FAIR lines; and value creation services — the enrichment, analytics and quality services that turn available data into something useful.
LDT instantiation — where we stand#
This is where the LDT stops being an interconnection exercise and becomes a market. The Marketplace of the EU LDT Toolbox (Nunsys), the CO₂ data products (LogiNex) and the tokenisation service sit here, and they raise the questions the rest of the scheme has to answer:
- A description is not complete when it says what the data is; in this scheme it is complete when it also says under which policy it may be used. That is the admission condition, so descriptions and enforcement are coupled by design — see Data, services & offerings descriptions.
- Discovery must not leak. What a city publishes about a restricted dataset (its existence, its shape) is itself a governance decision — see Publication & discovery.
- Services that make claims — CO₂ savings, in particular, because tokens and rewards depend on them — need a documented, auditable methodology and a stated liability position for wrong results. See Value creation services.
Blocks in this pillar#
| # | Block | Owner(s) | Status |
|---|---|---|---|
| V1 | Data, services & offerings descriptions · guiding questions | Nunsys + LogiNex + iLabs | OPEN |
| V2 | Publication & discovery · guiding questions | Nunsys + iLabs | OPEN |
| V3 | Value creation services · guiding questions | Nunsys + LogiNex + HyEnSys + Aegean | OPEN |
Naming note. The template publishes this block at the path
value-added-serviceswhile titling it Value Creation Services. This fork uses the title for both, so the page isvalue-creation-services.md. See Template parity.
PD4 mapping#
Feeds PD4 chapter 5 (data sharing), chapter 6 (licences in contracts) and chapter 8 (sustainability & replication).