Scheme overview — how this forks the iSHARE Template#
Lineage#
DSSC Blueprint ──► iSHARE Trust Framework 3.x ──► iSHARE Data Space Template v2 ──► LDT Governance and Trust Framework (this repo)
framework.ishare.eu template.ishare.eu EUTwinLink instantiation
The iSHARE Data Space Template is the generic document set data-space initiatives use to instantiate an iSHARE-compliant scheme. This repository is the official EUTwinLink fork, created by iSHARE Foundation as Scheme Owner: same building-block structure, same guiding questions — but every block either answered for the LDT or assigned to the partner who owns the answer.
The fork is complete rather than selective: all 47 template pages have a counterpart here and all 386 guiding questions are carried over verbatim. Template parity audits that page by page and is checked in CI, so the claim is verifiable rather than asserted.
Update rule (mirrors the template's own): when iSHARE Foundation publishes changes to the Trust Framework or Template, the TIPS Committee reviews this fork block-by-block and adopts what is relevant. Where this scheme aligns with the iSHARE Trust Framework, the framework's documentation is normative supporting material; where the LDT makes scheme-specific choices, this repo says so explicitly. The mechanics — and the adopted / profiled / extended test each block must satisfy — are in Alignment with the iSHARE Trust Framework.
Page anatomy#
Every building block is two pages. The block page holds the decisions; the guiding-questions page holds the work.
The block page has five parts:
- Purpose — why the block exists (from the template).
- LDT instantiation — what is already decided or known for EUTwinLink (from the Grant Agreement, Consortium Agreement and WP4 plan). This is the part that grows into PD4.
- 🧩 Building blocks requested — the pieces a named partner must contribute, with format and due date.
- Guiding questions — a digest of the questions that most shape this block, and a pointer to the full set.
- PD4 mapping — which chapter of the PD4 Governance Scheme deliverable the block feeds.
The guiding-questions.md page carries the template's questions unchanged, grouped by theme, each theme followed by a LDT answer slot naming its owner and due date. That slot is the unit of contribution — see CONTRIBUTING. The pages are generated by tools/sync_template_questions.py, which preserves partner text between the answer markers, so an upstream template release produces a reviewable diff instead of a rewrite.
Above the blocks sit pillar pages (README.md per pillar), each with the template's purpose, where the LDT stands across that pillar, and a status table for its blocks.
PD4 mapping at a glance#
| PD4 chapter | Building blocks that feed it |
|---|---|
| 1. Introduction & scope | Scheme overview · Use-case profiles |
| 2. Governance structure & roles | Governance design layers · Organisational form & governance authority |
| 3. Legal & regulatory framework | Regulatory compliance |
| 4. Participation & onboarding | Participation management · Identity & attestation · Trust framework |
| 5. Data & data-model sharing (DataRights) | Access & usage policies · Data models · Data exchange |
| 6. Contracts & legal clauses | Contractual framework · Data space offerings (licences) |
| 7. Assurance, compliance & operations | Provenance & observability · Intermediaries & operators |
| 8. Sustainability, replication & scalability | Business model · Value creation services · Publication & discovery |
| 9. Annexes | All — templates, example policies, compliance matrix |
Naming#
LDT = Local Digital Twin. This scheme is the LDT Governance and Trust Framework: the governance and trust rules under which Local Digital Twins interconnect. "The LDT network" — or simply "the LDT" in the answer slots — is the interconnected network of Local Digital Twins that EUTwinLink builds. The scheme covers both the city twins (Cartagena, Almelo/Aadorp) and the operational twins (Aruba Airport, Hamburg Port), plus the Marketplace of the EU LDT Toolbox and AI-agent services on top.