This most important part of the Functional descriptions explains the following in detail:
- The iSHARE frameworkThe iSHARE Trust Framework functional description, including the Scheme Owner Satellite and and what role can hold what types of information;
- The three primary use cases: Machine to Machine, Human to Machine with authorization info and identity info held at the Service Provider, and Human to Machine with identity info held at an Identity Provider;
- The possible variations to the three primary use cases, depending on where identity information, authorization information and/or delegation information is held.
...
iSHARE Trust Framework functional description
The iSHARE Trust framework was first explained under use cases. It consists of six roles that, depending on the situation, interact with each other based on the iSHARE Scheme Trust Framework agreements. Each role has a certain function in the scheme Framework and bears certain responsibilities. To fulfil an any other role in the frameworkFramework, a party must fulfil specific admittance criteria, as explained.
What was not explained under use cases was how the iSHARE and the Scheme Owner-role provide a trust framework. The Scheme Owner-role is fulfilled by the legal entity that governs the iSHARE Scheme Trust Framework and its participant network. To be admitted, a one must first be admitted to the Scheme data space/network by a Scheme Administror Satellite and must then sign an accession agreement with the SchemeSatellite. The fact that every legal entity fulfilling a role in the iSHARE Scheme Trust Framework agrees to the scheme rules - as proven by its agreement with the Scheme Satellite - creates trust between parties in the data space/iSHARE network. This is why the following depiction of the iSHARE framework, showing the mandatory relation between the Scheme Owner and every other role, can be called the trust framework:
In order to know whether a party is an iSHARE participant before sharing data with it, the Scheme Owner Satellite can be asked about this party's adherence/certification (as detailed in secondary use case 5a). This and the trust framework as a whole are is not reflected in the primary use cases because every relation or interaction within iSHARE is build upon the trust frameworkFramework. The framework used to depict Framework use cases was already are presented as follows:
It was stated that all of iSHARE's use cases can be depicted in the above framework. 
Their complexity is dependent on:
...
- Entitlement info: information indicating what Entitled Parties are entitled to what (parts of) services;
- Delegation info: information indicating which (parts of) an Entitled Party's rights (as registered at the Service Provider or the Authorization Registry) are delegated to a Service Consumer;
- Authorization info: information indicating which Human Service Consumers are authorized to act on a Service ConumerConsumer's behalf;
- Identity info: information about a Human Service Consumer's identity (only applicable in H2M use cases).
...