Skip to content

Guiding questions — Contractual framework#

Fork notice. The questions below are reproduced from the iSHARE Data Space Template page Contractual framework → Guiding questions — © iSHARE Foundation, used under the EUTwinLink Consortium Agreement (see Legal notices). The template's question text is carried over unchanged so this fork stays comparable to its upstream.

Everything between the LDT answer markers is the EUTwinLink instantiation — that is what partners fill in. Decisions already taken live on the block page: Contractual framework.

Building block L2 · owner(s) iSHARE (Nunsys terms of use; sign-off: cities) · due 26 Sep 2026 · block status DRAFTED · see the Building-block register.

Answer provenance. Every answer below is tagged with where it comes from, because a governance scheme that cannot be traced is not a governance scheme:

  • Decided — already fixed by the Grant Agreement, the Consortium Agreement or a recorded decision elsewhere in this scheme. Change it only through the change procedure.
  • Proposed — a defensible default, derived from the iSHARE Trust Framework, the DSSC Blueprint and the decisions this scheme has already taken. Drafted for the owner to confirm, correct or reject at TIPS. It is not an agreed position until TIPS approves it.
  • Needs owner — cannot be answered without the named owner: a fact about their systems, their legal position or their commercial intent. The text states what is needed and why.

Open points across the whole scheme are collected in Open questions for partners.

1. Core Structure of Agreements#

Purpose: Standardize essential contractual terms to ensure clarity and fairness across all participants.

  • What standard contractual elements should every participant agreement include (e.g. roles, rights, obligations, liability)?
  • Should there be a universal participation agreement or differentiated agreements depending on participant role (e.g. provider, consumer, intermediary)?

LDT answer DRAFTED · owner: iSHARE (Nunsys terms of use; sign-off: cities) · due 26 Sep 2026

Decided A universal accession agreement, not differentiated per role: one signature binds a participant to the whole scheme, with role- and activity-specific obligations attaching as annex modules. The alternative — a separate agreement per role — multiplies documents without multiplying content, and breaks as soon as one organisation holds two roles, which in the LDT most do.

Proposed Standard elements in every participant agreement:

  • identification and the roles assumed;
  • adherence to this scheme as amended through the change procedure;
  • obligations on data contributed (lawful basis, accurate description, stated quality) and on data received (honour the attached policy, including after exit);
  • credential maintenance and acceptance of the audit trail;
  • liability allocation and caps;
  • suspension and termination conditions;
  • the dispute ladder;
  • IP and attribution — notably the iSHARE terms in Legal notices, which are not negotiable at participant level.

Decided The Marketplace annex, previously an open request to Nunsys, is specified in PD4 §5. The Marketplace of the EU LDT Toolbox carries two versioned sets of terms — Terms of Participation (accepted at registration) and Terms of Publication (accepted before publishing an offering) — with recorded acceptance, plus a Privacy Policy and a Cookie Policy. Nunsys acts as operator and data controller and has its legal team approve the production versions and align them with the iSHARE accession and model agreements. The current texts are working drafts; producing the production versions is PD4 Table 3, owner Nunsys, target M9. (Source: PD4 v1.0 §5 and Table 3 — text as in PD4 v0.96, 29 Oct 2026.)

Decided The instrument exists and is named. Under the iSHARE Data Ecosystem Agreement, the data space governance body must ensure that every organisation participating as an Adhering Party concludes the applicable iSHARE Accession Agreement — directly with the Scheme Owner or the Participant Registry, or through an authorised onboarding party — and accepts the iSHARE Terms of Use, and may not onboard in a way that circumvents iSHARE admission requirements. Parties operating a registry, authorisation registry, identity broker or identity provider sign the separate Certified Party Accession Agreement. The Terms of Use and the framework documentation at framework.ishare.eu are incorporated by reference, with a stated order of precedence. (Source: iSHARE Data Ecosystem Agreement, clauses 1.3, 1.5, 5.3 and 5.4.)

Needs owner iSHARE legal: whether that Accession Agreement carries the six elements listed above as drafted, and whether the cities can sign it under municipal contracting rules. The Data Ecosystem Agreement names the instrument but does not reproduce it, and the copy consulted here is the Scheme Owner template, not an executed EUTwinLink agreement.

2. Alignment with Governance#

Purpose: Ensure that contractual arrangements reinforce overarching governance principles and adapt to evolving governance decisions.

  • How can the contractual framework reflect and reinforce the governance principles (e.g., fairness, interoperability, accountability)?
  • Should governance decisions automatically amend contractual terms, or require explicit participant consent?

LDT answer DRAFTED · owner: iSHARE (Nunsys terms of use; sign-off: cities) · due 26 Sep 2026

Proposed The contractual framework reinforces governance principles by referencing rather than restating them: the agreement binds a participant to this scheme as amended, so fairness, interoperability and accountability are enforceable because the scheme defines them operationally — a licence from the Licence Catalog, an ITB-S conformance requirement, an audit-trail obligation. Principles restated as contract prose would be unenforceable duplicates that drift from the scheme over time.

Decided Governance decisions amend annexed terms automatically through the change procedure; the block page records this. The accession agreement binds the participant to the scheme as it evolves, not as it stood on signature.

Proposed That is the right default and it needs one limit, which the scheme does not currently state: a change that materially increases a participant's obligations should require notice and a right to withdraw without penalty, rather than binding automatically. Without that limit, automatic amendment means a participant can be bound to terms it would never have signed, which is exactly the fairness problem the template's "fairness in data contracts" question points at.

Decided The Consortium Agreement answers all three, in different words than this page used. The threshold is "substantial", not "material": on a breach, the Coordinator gives formal notice requiring remedy within 30 calendar days; if the breach is substantial and either not remedied in that period or not capable of remedy, the General Assembly may declare the party a Defaulting Party and decide the consequences, up to termination of its participation. The withdrawal right exists and is a General Assembly decision — "withdrawal of a party from the consortium and the approval of the settlement on the conditions of the withdrawal" — and a party requesting to leave may not veto decisions about its own departure. (Source: LDT4SSC–EUTwinLink pilot Consortium Agreement, signed by all eleven parties.)

Needs owner iSHARE legal: whether the accession agreement for a scheme participant that is not a consortium party adopts the same threshold and the same 30-day window, or sets its own. The consortium instrument cannot bind a party that never signed it.

3. Onboarding and Offboarding#

Purpose: Design contractual entry and exit processes that safeguard trust, compliance, and continuity.

  • What contractual processes should regulate entry into the data space (e.g., signature of framework contract, compliance verification)?
  • How should termination or exit of participants be managed contractually, including data handling and ongoing obligations?

LDT answer DRAFTED · owner: iSHARE (Nunsys terms of use; sign-off: cities) · due 26 Sep 2026

Decided Entry: signature of the accession agreement plus the annexes for the activities undertaken, preceded by identity verification and ITB-S conformance, followed by registry entry and credential issuance. The contractual act and the technical act are deliberately coupled — a signature without a credential grants nothing, and a credential without a signature is not issued.

Decided Exit is managed contractually by the accession agreement; the mechanism (revocation, registry status change, propagation) is in Participation management section 4.

Proposed The clause that matters most and is currently missing: usage policies attached to data survive the exit of the party that received it. Without it, leaving the scheme launders the terms — a participant could receive data under a purpose limitation, exit, and treat the data as unencumbered. The agreement should state survival explicitly, name the retention or deletion duty per tier, and say which obligations end at exit and which do not.

Needs owner iSHARE legal. This is the single most consequential gap in the contract stack as it stands.

4. Flexibility vs. Standardisation#

Purpose: Balance the need for uniformity with customizable modules to address sector-specific requirements.

  • To what extent should the contractual framework allow customization by participants versus enforcing strict uniformity?
  • Should industry-specific annexes or modules be foreseen (e.g., CO₂ reporting standards for real estate, technical protocols for energy data)?

LDT answer DRAFTED · owner: iSHARE (Nunsys terms of use; sign-off: cities) · due 26 Sep 2026

Decided Standard terms cover the standard cases; bespoke clauses only for genuinely bespoke situations. Data-sharing terms are composed rather than drafted: a licence from the iSHARE Licence Catalog (licenses.ishare.eu, binding — not paraphrased or translated without iSHARE Foundation's written consent) plus an ODRL policy, with a bilateral annex only where needed.

Proposed The discipline to hold: every bilateral annex is a transaction cost the scheme failed to absorb. A recurring annex is a signal that the standard set is missing a case, and should be brought to TIPS as a proposed addition to the catalogue rather than copied between deals.

Annex modules already foreseen, which is where legitimate sector variation lives:

  • marketplace and tokenisation ToU (Nunsys);
  • ITB-S terms of use (iLabs);
  • observer and AI-agent service terms;
  • non-EU transfer clauses (Aruba);
  • citizen and community data under Commons controls (PED, LEZ);
  • grid-party flexibility data (PED).

Needs owner Nunsys for the marketplace annex; Almelo Energie / HyEnSys for the grid-party annex, which is assumed here and confirmed nowhere.

5. Dispute Prevention and Resolution#

Purpose: Provide clear mechanisms for conflict resolution to maintain trust and minimize disruption.

  • How should contracts define mechanisms for conflict resolution (e.g., escalation procedures, mediation, arbitration)?
  • Should dispute-handling be centralized via a governance authority or decentralized among participants?

LDT answer DRAFTED · owner: iSHARE (Nunsys terms of use; sign-off: cities) · due 26 Sep 2026

Decided Escalation follows the Consortium Agreement ladder: amicable resolution, then the Steering Committee, then the jurisdiction named in the CA.

Proposed Dispute handling is centralised for scheme matters, decentralised for bilateral ones, and the line between them is what the agreement must draw clearly:

  • A disagreement about what the scheme means — whether a policy permits a use, whether a methodology meets the auditability requirement — goes to TIPS, because an interpretation that binds one pair of participants binds all of them.
  • A disagreement about performance between two participants under a bilateral annex is theirs, with the CA ladder available.

Prevention does more work than resolution here, and it is structural: standard licences, machine-enforceable policies and an audit trail mean most disputes about what was permitted can be settled by inspection rather than argument. That is the practical case for insisting policies be machine-enforceable.

Decided The ladder the accession agreement has to match is now on the record. The Consortium Agreement, section 11.8: the parties first endeavour to settle amicably; failing that, the dispute goes to mediation under the WIPO Mediation Rules, seated in Brussels and conducted in English; if it is not settled within 60 calendar days of the mediation commencing, the courts of Brussels have exclusive jurisdiction. Belgian law governs, and nothing limits a party's right to seek injunctive relief elsewhere. (Source: LDT4SSC–EUTwinLink pilot Consortium Agreement, signed by all eleven parties.)

Needs owner iSHARE legal: whether the accession agreement adopts that ladder for participants who never signed the Consortium Agreement, or points at a different forum. The gap is real — the question is now which of two known answers it gets, not what the alternative looks like.

6. Compliance and Enforcement#

Purpose: Define how contractual compliance will be monitored, enforced, and sanctioned in case of breaches.

  • How should contractual obligations be monitored and enforced (e.g., audits, sanctions, suspension)?
  • What should be the consequences of non-compliance with contractual terms, especially in relation to data misuse or sustainability targets?

LDT answer DRAFTED · owner: iSHARE (Nunsys terms of use; sign-off: cities) · due 26 Sep 2026

Proposed Monitoring is the audit trail plus the registry, not a separate contractual audit regime. Policy decisions leave entries; conformance status and credential validity are machine-readable; the marketplace exposes whether a listing's evidence is current. A contractual audit right exists as a backstop for cases the automatic record cannot settle — a participant's internal handling of data it already received, above all, which is the one place the scheme's instrumentation cannot see.

Proposed Consequences of non-compliance follow the graduated ladder in Regulatory compliance section 6: warning, suspension, termination, contractual and legal remedies. Two cases deserve naming explicitly in the agreement because they damage the scheme rather than a counterparty:

  • Data misuse — use outside the attached policy. Suspension is the default immediate response, because the harm continues while the data flows.
  • Unfounded sustainability claims — a CO₂ figure presented as verified without a documented, auditable methodology. The reputational exposure here falls on every participant, which is why the methodology requirement is a scheme rule and not a LogiNex preference.

Needs owner Nunsys + LogiNex: liability for incorrect reward calculations, which the marketplace 🧩 asks for and which has no answer in the scheme today.