iSHARE Trust Framework
Other resources
Version 2.1 (current version)
Version 2.1 (current version)
  • iSHARE Trust Framework
  • Introduction
    • Goals and scope of the iSHARE Trust Framework
    • Guiding principles
    • Governance
  • Releases
    • Release notes
    • Release planning
    • Version history
  • Main aspects of the iSHARE Trust Framework
    • Key functionality
      • Support Machine to Machine (M2M) interaction
      • Support Human to Machine (H2M) interaction
      • Facilitate portable identity(s) for parties and humans
      • Facilitate flexible authorizations, applicable in any context
      • Enable data exchange based on delegations - even between unknown parties
      • Enable control over own data through management of consent
      • Provide a Trust Framework
    • Technical overview
    • Framework and roles
    • Legal provisions
    • Operational provisions
  • Use cases
    • Use case: M2M interaction (with fine-grained authorization)
    • Use case: H2M interaction (with coarse-grained authorization)
    • Use case: portable identity
    • Use case: delegation (and management of consent)
  • Detailed descriptions
    • Functional
      • Primary use cases
        • 1. M2M service provision
          • 1b. M2M service provision with the EP as the delegation info PIP
          • 1c. M2M service provision with the AR as the delegation info PIP
          • M2M service provision including an app
        • 2. H2M service provision with identity info at the IP
          • Without Identity Broker
          • With Identity Broker
      • Secondary use cases
      • Licenses
      • Delegation paths
      • Functional requirements per role
        • Party identification
        • User interface requirements
    • Technical
      • Technical standards
      • Structure of delegation evidence
        • Example cases
    • Operational
      • Operational processes
        • Admission
        • Withdrawal or Downgrade
        • Warnings, Suspension and Exclusion
        • Incident Management
        • Change Management
        • Management reporting
      • Service levels
        • Service levels for Adhering Parties
        • Service levels for Certified Parties
      • Communication
    • Legal
      • Legal context
        • Dutch Civil Code
        • Regulation on Electronic Identification and Trust Services (eIDAS)
        • Applicable competition law
        • General Data Protection Regulation (GDPR)
  • Glossary and legal notices
    • Glossary
    • Legal notices
    • Assumptions
Powered by GitBook
LogoLogo

  • Cookie Policy

  • Privacy Policy

  • Imprint

  • Contact Us

Copyright © 2024 iSHARE Foundation

On this page
  1. Main aspects of the iSHARE Trust Framework

Legal provisions

PreviousFramework and rolesNextOperational provisions

Last updated 2 months ago

The legal underpinning of iSHARE Trust Framework consists of a contract between all iSHARE participants and the iSHARE Scheme Owner (the so-called Accession Agreement). This contract can be signed with the Participant Registry instead. Based on this one contract with the Scheme Owner or Participant Registry, all participants are bound to the common iSHARE terms of use and can appeal to each other to abide by these rules (in legal terms this is called perfection (Dutch: derdenwerking)).

Two main documents make up iSHARE's legal provisions:

  1. The Accession Agreement The main contract between the participant and the iSHARE Scheme Owner/Participant Registry. This contract refers to the terms of use, including all iSHARE specifications, to which all participants must abide. After signing the Accession Agreement, a party becomes a participant of the iSHARE network either as an Adhering Party or a Certified Party. There are two separate Accession Agreements: one for Adhering Parties and one for Certified Parties.

  2. The Terms of Use The Terms of Use further define the rights and obligations of every iSHARE Participant and the Scheme Owner/Participant Registry. The Terms of Use apply to any party that has signed the Accession Agreement. The Terms of Use also state that participants fully abide by the iSHARE specifications.

Data space agreements - The data space can choose to embed the Accession Agreement and Terms of Use in its data space specific agreements. The data spaces can also have additional agreements for its members.

For the details of the Accession Agreements, the full version of the Terms of Use and the information available on legal context, please refer to the .

Licenses

Within the iSHARE network, it is possible to explicitly provide instructions on how a service may be consumed or under which conditions data is exchanged. These instructions or conditions are called 'licenses'. Licenses are a crucial part of the iSHARE Trust Framework, because they provide its participants the possibility to clearly state what is and what is not allowed. Since all participants are bound to the same contract and underlying Trust Framework rules, participants can appeal to each other to follow the provided licenses. Please refer to the iSHARE Terms of Use for a detailed legal explanation.

detailed Legal descriptions