• Updated Roles
• Updated Governance structure
• Distinction and clarity in roles and governance
• Updates in operational and functional processes 

Introduction

• Scheme is now known as iSHARE Trust Framework 
• Updated goals, scope, guiding principles and governance. 
• Federation of Trust Framework 

Functional

• Added new role: Satellite
• Scheme administrator is now Satellite administrator 
• Minor fixes in key functionality
•  

Technical 

• Updated Satellite role 
• Review of technical standards and minor fixes 

Legal 

• Updated Satellite role
• Updated Accession agreement and Terms of Use 

Operational

• New role - Satellite
• Updated the operational processes of admission, withdrawal and incident management processes
• Updated the service levels.

• Updated legal documents
• Added new role: Scheme Administrator
• Updated Governance structure
• Small technical improvements

Functional

• Added new role: Scheme Administrator
• Participant admission process
• Governance
• Scheme trust model
• Human authorization for IDPs is now optional and no longer mandatory

Technical

• Human authorization for IDPs is now optional and no longer mandatory. The associated CTT tests are no longer a requirement for certification. 
• Scheme administrators added and new attributes added to:
• Track which SA is responsible for the participant
• Express the level of adherence of the participant.

Operational

• Updated the admission process for Scheme Administrator:
• Admission of Scheme Administrator
• Withdrawal of Scheme Administrator
• Updated the admission process for Parties:
  • Admission through Scheme Administrator
  • reassignment of Scheme Administrator
• Governance structure changed to reflect the transition from project phase
• Added process of determining yearly participation fees.

Legal

Updates:

• Updated the Terms of Use to reflect the fact that Adhering Parties and Certified Parties are subject to an annual fee, added article 11 “Participation Fee” and updated the links to the Annexes.
• Updated the Accession Agreement for Certified Parties  to reflect the fact that Certified Parties are subject to an annual fee.
• Updated the Accession Agreement for Adhering Parties  to reflect the fact that Adhering Parties are subject to an annual fee.
• Renewed the standard NDA due to reflect the relation between the iSHARE foundation, Scheme Owner and Adoption.

• Updated the process for verifying eIDAS certificates
• Update the admission process for Certified Parties
• Added levels of assurance for Certified Parties
• Added support for the usecase where the Entitled Party is not an iSHARE Adhering Party, but is a customer of an iSHARE Service Provider
• Small technical improvements

Functional

• Updated the functional requirements for Certified Parties (references to eHerkenning have been removed and replaced by relevant requirements)

Technical

• Updated the process for verifying eIDAS certificates (now uses the same process as PKI-Overheid certificates)
• Added level of assurance to the Party Info endpoint at the Scheme Owner (for Certified Parties)
• Clarified the use of acr_values in the H2M flow to request a minimal level of assurance
• Clarified the headers used for JWE in the H2M flow

Operational

• Updated the admission process for Certified Parties, including the following changes:
  • Admission to eHerkenning is no longer required
  • Added the concept of Levels of Assurance for Certified Parties
  • Added the Assessment Framework for Certified Parties to determine the Level of Assurance of a Certified Party

Legal

• Updated the terms of use to reflect the usecase where the Entitled Party is not an iSHARE Adhering Party, but is a customer of an iSHARE Service Provider

Functional: 

• Updated primary Human to Machine use cases to reflect changes from RFC 010, which added the authorization flow to these cases

Technical:

• Added technical specifications on the generic authorization flow for Human to Machine (H2M) interactions as facilitated by Identity Providers in the iSHARE Scheme, to reflect changes from RFC 010
• Modified technical specifications for capabilities endpoint of all iSHARE Parties

Operational

• No changes

Legal

• Updated governance framework to reflect that Stichting iSHARE Foundation has been created

Miscellaneous

• Rearranged pages and sections to improve readability
• Material has been moved from the Scheme to the Developer Portal, to improve readability and usability of both

Functional: 

-        

Technical:

• Added technical specifications on the generic authentication flow for Human to Machine (H2M) interactions as facilitated by Identity Providers in the iSHARE Scheme.

Operational

-

Legal

• Minor modifications to Terms of Use and the Accession Agreements for Adhering Paries and Certified Parties
• Moved GDPR Factsheet and templates for Data Exchange Agreement and Data Processor Agreements to appendix of the scheme, since they serve merely as an inspiration for participants who want to make additional bilateral arrangements with others they are sharing data with.

Miscellaneous

• The governance framework is updated
• Rearranged pages and sections to improve readability

Functional: 

-        

Technical:

• The API technical specifications are moved to a dedicated developer portal.
• Adjusted specification for JSON Web Token (JWT) to facilitate certificate validation under eIDAS. 

Operational

• The service levels are now structured per participant type (Adhering Party/ Certified Party/ Scheme Owner) to give participants a better overview of their applicable service levels.

Legal

-  

Miscellaneous

• Rearranged pages and sections to improve readability
• The governance framework is updated
• The project history is updated

Functional: 

-        

Technical:

• For authentication purposes the use of digital certificates within iSHARE will be limited initially to certificates issued under PKIOverheid.

Operational

• The admission process for Certified Parties and Adhering Parties are merged to one generic process. Role-specific requirements may apply.
• The order of admission steps is changed to enable new iSHARE entrants to start testing before a contract is signed.

Legal

-  

Miscellaneous

• Rearranged pages and sections to improve readability
• The governance framework is updated

• Updated specifications for all content of the iSHARE Scheme:
• Functional
• Technical
• Operational
• Legal
• Significantly updated and rearranged sections for readability, including a main scheme aspects- and illustrative use cases chapter with new depictions; Integrated (technical) specifications, generic and per iSHARE role