Roles

This page must be considered part of the iSHARE Framework

This page is considered normative and is therefore compliant with RFC 2119.

One of the iSHARE Trust Framework's core features is its description of functional roles. These roles represent the different ways organisations can interact with each other. To assure federation of all aspects, and no single points of ‘failure’ or ‘power’ in the structure, all roles are defined and can be executed by multiple parties.

Role definition

The principle of a role is that its execution can be done by the same legal entity, but the interface specification assures that always level playing field / federation is possible. The Trust Framework introduces two core role types: "Adhering Parties" and "Certified Parties”

"Adhering parties" directly engage with data and include:

"Certified Parties" are certified to facilitate trusted exchanges between Adhering Parties. They encompass these specific roles:

Role identifiers

In certain situations, a role identifier is used to identify the role(s) of a participant. For this purpose, the Trust Framework specifies the following identifiers:

Role identifier
Role

ServiceConsumer

Service Consumer

ServiceProvider

Service Provider

EntitledParty

Entitled Party

AuthorisationRegistry

Authorisation Registry

IdentityProvider

Identity Provider

IdentityBroker

Identity Broker

ParticipantRegistry (former identifier iShareSatellite)

Participant Registry (former name iSHARE Satellite)

Last updated