Participation management#
Part of the LDT Governance and Trust Framework — instantiates the iSHARE Data Space Template block Participation management (© iSHARE Foundation, see Legal notices).
Purpose#
Smooth and secure participation: roles, onboarding/offboarding, readiness, inclusivity, compliance, sovereignty and scalability.
LDT instantiation — where we stand#
- Roles (iSHARE Trust Framework role model): Data Provider · Data Consumer/User · Data Rights Holder (incl. citizens for community data) · Service Provider · Scheme Owner · Registry/Operator roles (iLabs, Nunsys) · Observer (LDT-specific role for cities/organisations following via dashboards or the AI observer chatbot).
- Onboarding: application-based; eligibility per role; conformance check via ITB-S; registration in the Participant Registry; credentials issued as verifiable credentials (see Identity & attestation); listing on the Trusted List where applicable.
- Offboarding: credential revocation + registry status change propagate automatically to policy enforcement; data-handling obligations on exit come from the contractual framework.
- Citizens & community data: participation of residents (Aadorp PED, Cartagena LEZ) runs through Commons controls — see the 🧩 block below.
🧩 Building block requested — Owner: HyEnSys (with Almelo Energie; engagement input: University of the Aegean)#
What we need: the Commons participation model: how citizens/communities join, consent, delegate and leave; how community representatives are mandated; how Commons decisions map to scheme roles and credentials.
Format: Markdown section in this page (merge request) · Due: 26 Sep 2026 (v0.5) · Status: OPEN
🧩 Building block requested — Owner: iLabs#
What we need: the operational onboarding flow: application → ITB-S conformance → registry entry → credential issuance, with expected throughput times and the offboarding/revocation propagation mechanism.
Format: Markdown section in this page (merge request) · Due: 26 Sep 2026 (v0.5) · Status: OPEN
Guiding questions#
All 48 of the template's questions for this block, with the 16
LDT answerslots to fill, are on participation-management/guiding-questions.md. The digest below is the subset that most shapes this block.
- Who are the Data Providers, Users, Rights Holders, Intermediaries and Operators; should additional roles be defined; how are roles formalised in the rulebook?
- What common terms apply to all participants, what eligibility criteria and attestations per role, and is onboarding application-based or automatic?
- What are valid exit scenarios; how are obligations verified and credentials handled after exit?
- How do participation policies foster inclusivity while maintaining rigour?
PD4 mapping#
Feeds PD4 chapter 4 — Participation & onboarding.