Template parity — is this still a full fork?#
Generated by
tools/check_parity.pyfrom the upstream index at https://template.ishare.eu/llms.txt. Do not edit by hand; re-run the script.
One row per page of the iSHARE Data Space Template (© iSHARE Foundation, see Legal notices), and the page in this fork that instantiates it. tools/check_parity.py --check fails the pipeline when an upstream page has no counterpart here, so a template update cannot quietly leave the fork incomplete.
Coverage: 47 of 47 upstream pages.
What this fork adds on top of the template#
The template is the floor, not the ceiling. These pages have no upstream counterpart and are EUTwinLink's own:
- Building-block register — one row per requested contribution, with owner, due date and status. The template maps stakeholders to building blocks (co-creation step 2); this is that map, kept live.
- Use-case profiles — the six LDT applications worked through individually against the template's Use Case Development skeleton.
- Scheme overview — lineage, page anatomy and the PD4 chapter mapping.
- This page, and
tools/— the machinery that keeps the fork honest.
Deliberate deviations#
- Guiding questions carry answer slots. Upstream, a guiding-questions page is a list of questions. Here each theme also has a
LDT answerblock with an owner and a due date, because in this fork the questions are work assignments. The question text itself is unchanged. - Pillar overviews are
README.mdin a directory rather than a sibling file, so the block pages nest under them. - Governance design layers has no guiding-questions page — neither does upstream; the template states nine principles instead, and those are applied directly on the block page.
value-added-servicesis namedvalue-creation-servicesafter the block's own title.