Data sovereignty & trust#
Part of the LDT Governance and Trust Framework — instantiates the iSHARE Data Space Template pillar Data Sovereignty & Trust (© iSHARE Foundation, see Legal notices).
Purpose#
Trust is the foundation of any data space: participants need to know who they are dealing with, and must be able to keep control over their own data. Three blocks provide the technical capability — identity & attestation management (who a participant is, and verifiable proof of their attributes or roles), trust framework (the shared baseline everyone follows), and access & usage policies enforcement (who may use data, under which conditions, enforced rather than merely promised).
LDT instantiation — where we stand#
This pillar is the core of the LDT and the part where the scheme is most nearly complete, because it is adopted rather than invented: the trust layer is the iSHARE (DataRights) Trust Framework 3.x, applied to the digital-twin domain, with iSHARE Foundation as Scheme Owner and sole party performing Trusted List and certification functions.
Two LDT-specific extensions carry real weight and are still open:
- Commons controls — community-level control over citizen and community data, on top of standard access and usage policies. Standard participant-to-participant policy language does not express "the neighbourhood decides"; see Access & usage policies enforcement.
- Non-EU credentials — Aruba Airport participates from outside the EU, so wallet and credential flows must hold up across that boundary; see Identity & attestation management.
The scheme's own rule: an operating condition that cannot be enforced by a credential check, an ODRL policy or a registry entry should be treated as a contract clause and named as such, not left as a technical aspiration.
Blocks in this pillar#
| # | Block | Owner(s) | Status |
|---|---|---|---|
| T4 | Identity & attestation management · guiding questions | iSHARE + FHC Corp + iLabs | DRAFTED |
| T5 | Trust framework · guiding questions | iSHARE | DRAFTED |
| T6 | Access & usage policies enforcement · guiding questions | iSHARE + HyEnSys (cities sign-off) | DRAFTED |
PD4 mapping#
Feeds PD4 chapter 4 (participation & onboarding) and chapter 5 (data sharing, DataRights).