Skip to content

Alignment with the iSHARE Trust Framework 3.x#

Part of the LDT Governance and Trust Framework — instantiates the iSHARE Data Space Template page Refers to the iSHARE Trust Framework 3.0 (© iSHARE Foundation, see Legal notices).

Purpose#

The iSHARE Data Space Template takes the iSHARE Trust Framework 3.0 as its reference point, so that a data space can see which parts of its scheme are already covered by the framework and where it still has to make its own choices.

This fork inherits that relationship and makes it stricter, because the LDT is not merely informed by the framework — it is an iSHARE-based scheme with iSHARE Foundation as Scheme Owner.

How to read this scheme against the framework#

Three cases, and every block page is expected to fall into one of them:

Case What it means How the page says so
Adopted The framework's rule applies unchanged. The framework documentation is the normative supporting material; this repo does not restate it. The block cites the framework and records only the LDT-specific parameters (which registry, which credential, which role).
Profiled The framework's rule applies, narrowed or tightened for the LDT. The block states the baseline and the narrowing, explicitly — e.g. stricter criteria for citizen-related twin data.
Extended The LDT needs something the framework does not cover. The block says so in as many words and names the owner of the extension. Current extensions: Commons controls, the Observer role, and non-EU credential flows for Aruba.

Where this scheme and the framework conflict, the framework wins on trust and identity mechanics; this scheme wins on LDT-specific governance. A conflict that cannot be resolved that way is a TIPS Committee item, not an editorial decision.

What certification does and does not follow from this#

Alignment is not conformance. The Trusted List, the certification of parties and the iSHARE-compliant designation are performed exclusively by iSHARE Foundation under its own scheme, and nothing in this repository grants them. ITB-S testing in WP2 produces evidence towards certification; it is not certification. See Legal notices and Trust framework.

How updates are handled#

Upstream, per the template:

  1. iSHARE Foundation publishes framework updates and documents them in the release notes.
  2. The iSHARE Data Space Template is reviewed and updated to reflect those changes, taking relevant DSSC Blueprint updates into account.

Downstream, in this fork — the concrete form of the update rule in Scheme overview:

  1. Re-run python3 tools/sync_template_questions.py to pull the template's current guiding questions. Partner answers are preserved; only the question text and structure change, so the diff is the change report.
  2. Run python3 tools/sync_template_questions.py --check in CI to detect drift without writing.
  3. The WP4 lead takes the diff to the TIPS Committee block by block; TIPS decides what the LDT adopts, profiles or declines.
  4. Declined adoptions are recorded on the block page with a reason. Silence is not a decision.

PD4 mapping#

Feeds PD4 chapter 1 (introduction & scope) and the compliance matrix in chapter 9 (annexes).