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. Glossary and legal notices

Assumptions

PreviousLegal notices

Last updated 2 months ago

The iSHARE Trust Framework was developed with the following assumptions in mind:

  1. Conditions for the exchange of data are assumed to be established; The iSHARE Trust Framework needs to rely upon the responsibility of participants to know what rights they have to what data. The Framework is meant as an instrument to exchange data in a uniform, controlled and straightforward way; it is not meant as a means to resolve questions of data ownership. In practice this means that a party sharing data bears responsibility to sufficiently establish whether the party receiving the data is authorized to receive it.

  2. Data formats and semantics are assumed to be in place; In order to be able to exchange data, a mutual understanding of the meaning of data and the way data is structured is required. Within the data spaces/iSHARE network, it is assumed that this mutual understanding exists and thus the exchange of data between involved parties is possible (in line with ). Please note that this assumption emphasises the need for industry initiatives on data standards and formats.

  3. Data classification has taken place; It is assumed that within the iSHARE Trust Framework , participants have sufficiently identified and classified their data. iSHARE participants are responsible for the classification of their data; the iSHARE Trust Framework does not prescribe its participants how to classify their resources. Please refer to for further detail.

Operational assumptions:

The Operational details of the iSHARE Trust Framework were developed with the following assumptions in mind:

  1. There will be a Scheme Owner of a yet to be defined form; This can be an existing body or a new body, and/or responsibilities can be split between different bodies.

  2. The Scheme Owner is financed through some type of financing constellation; This can be through participants paying some type of fee or in any other feasible way. The Operational working group did not decide upon the financing constellation of the Scheme Owner.

  3. The complexity of the operational processes is expected to be as follows:

    • It is considered reasonable to expect between 1000 and 10000 Adhering Parties in the first 5 years after data spaces goes live;

    • It is considered reasonable to expect between 20 and 50 Certified Parties in the first 5 years after data spaces goes live;

    • It is considered reasonable to expect parties to participate from countries all over the world in the first 5 years;

    • The Scheme Owner aims to keep effort needed for admission as low as possible for both Adhering- and Certified Parties without compromising the integrity of the iSHARE Trust Framework and -network;

    • The Scheme Owner regularly tests the robustness of the Trust Framework and plans for mitigation of risks/threats (e.g. identifying Single Points of Failure);

    • The Scheme Owner is assumed to have at least some responsibility in realising sustainable growth of the data space/iSHARE network;

    • The management of disputes regarding the contents of the data shared is not a core role of the Scheme Owner; disputes should be handled by involved parties.

These assumptions are, in NO WAY, ambitions. They were simply defined to base processes and service levels upon.

guiding principle 4
data classification in the glossary