Skip to content

Trust framework#

Part of the LDT Governance and Trust Framework — instantiates the iSHARE Data Space Template block Trust framework (© iSHARE Foundation, see Legal notices).

Purpose#

Define the trust entities, criteria, validation processes and registries that let participants rely on each other — leveraging existing frameworks rather than inventing new ones.

LDT instantiation — drafted by iSHARE#

  • Foundation: the LDT trust layer is the iSHARE (DataRights) Trust Framework 3.x, applied to the digital-twin domain — not a bespoke framework. Gaia-X alignment is maintained at the descriptive level (offerings/self-descriptions).
  • Trust anchors: iSHARE Foundation (Scheme Owner) + eIDAS trust lists; the Trusted List and certification of parties are performed exclusively by iSHARE Foundation (Consortium Agreement).
  • Registries: the iSHARE Participant Registry, operated by iSHARE Foundation as part of its standing scheme operations and the scheme's only authoritative trust anchor — machine-readable, supports automated compliance checks; revoked/suspended entities visible. iLabs operates the ITB-S conformance lab, the development sandbox and the reference trust gateway; it issues no Participant or CO₂ Credentials and provides no organisational wallets, so that its testing stays neutral (Source: PD4 v1.0 §2 Table 1 and §3 — text as in PD4 v0.96, 29 Oct 2026).
  • Conformance: ITB-S testing produces the evidence; certification/iSHARE-compliant designation is granted only via iSHARE Foundation's scheme.
  • High-risk data: stricter criteria (e.g. for citizen-related or commercially sensitive twin data) are set per use-case profile on top of the baseline.

Status: DRAFTED — TIPS review 9 Sep. Remaining open point: whether any LDT-specific accredited trust entity is needed beyond the iSHARE anchors (expected: no).

Guiding questions#

All 18 of the template's questions for this block, with the 5 LDT answer slots to fill, are on trust-framework/guiding-questions.md. The digest below is the subset that most shapes this block.

  • Which trust anchors does the LDT recognise, and will it federate from existing frameworks (iSHARE, Gaia-X, IDSA) rather than run its own?
  • What baseline criteria must a trust entity meet, and how is conformity evidenced?
  • How are claims validated and revoked; does verification support dynamic attributes for usage control?
  • How is cross-framework interoperability proven (conformance testing, mapped profiles)?

PD4 mapping#

Feeds PD4 chapters 2 and 4 (trust roles & onboarding trust chain).