Skip to content

Regulatory compliance#

Part of the LDT Governance and Trust Framework — instantiates the iSHARE Data Space Template block Regulatory compliance (© iSHARE Foundation, see Legal notices).

Purpose#

Legal certainty builds trust: identify which legal frameworks, obligations and regulatory triggers apply to the design, operation and participation in the data space.

LDT instantiation — where we stand#

Frameworks on the LDT's radar (to be confirmed and completed by the legal reviewers):

Framework Relevance for the LDT
eIDAS 2.0 wallets & verifiable credentials for organisations and representatives (via ITB-S identity modules)
GDPR citizen-related data in LEZ & PED contexts — handled in PD1 (Data Management Plan & Ethics), cross-referenced not duplicated
Data Governance Act / Data Act intermediation services, public-sector data reuse, B2B sharing terms
AI Act the AI-agent stack and observer chatbot — risk classification & transparency duties
ITS Directive / mobility rules LEZ enforcement and mobility data (ERTICO to advise)
Energy market rules (NL) PED flexibility & energy sharing (Almelo Energie to advise)
Non-EU transfer (Aruba) Aruba is a non-EU jurisdiction: transfer mechanisms and applicable-law clauses needed for airport data

What we need: per jurisdiction: confirm the applicable-framework table, flag sector-specific rules, and state per framework who carries the compliance duty (scheme vs participant) and what evidence is expected at onboarding.

Format: Markdown section in this page (merge request) · Due: 3–17 Oct 2026 (legal review window) · Status: OPEN

Guiding questions#

All 16 of the template's questions for this block, with the 6 LDT answer slots to fill, are on regulatory-compliance/guiding-questions.md. The digest below is the subset that most shapes this block.

  • Which EU and national regulations are directly relevant, and how does the governance authority track evolving obligations?
  • Which obligations rest with the authority vs participants; should baseline legal compliance be an entry requirement?
  • Should compliance be verified through certification, attestation or self-declaration, and how often?
  • How are breaches addressed and which body handles non-compliance?

PD4 mapping#

Feeds PD4 chapter 3 — Legal & regulatory framework.