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. Detailed descriptions
  2. Functional

Licenses

PreviousSecondary use casesNextDelegation paths

Last updated 2 months ago

Within the Trust Framework, 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 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 scheme rules, participants can appeal to each other to follow the provided licenses.

Additions to the licenses are proposed in the Change Advisory Board and processed after approval. This is part of the Process.

License code list

Purpose code
Description

0000

No limitations

0001

Re-sharing with Adhering Parties only

0002

Internal use only

0003

Non-commercial use only: licensee may not use the data to generate revenue

0004

Licensee may enrich received data with own data before re-sharing

0005

Licensee may enrich received data with data of others before re-sharing

0006

Licensee may enrich received data with own data before re-sharing on a non-commercial basis

0007

Licensee may enrich received data with data of others before re-sharing on a non-commercial basis

9996

Request the creation of delegations on behalf of the Entitled Party, bound to defined authorisation rules, liability lies with Delegation Policy Requestor

9997

Request the creation of delegations on behalf of the Entitled Party, bound to defined authorisation rules, liability lies with Entitled Party

9998

Request the creation of delegations on behalf of the Entitled Party, bound to defined authorisation rules, liability is subject to conditions or bilateral agreements

9999

As determined between Parties

Change Management