# Release notes

The release notes show the release history and the main differences between releases.

<table><thead><tr><th width="225.333251953125">Release 3.0</th><th></th></tr></thead><tbody><tr><td>Purpose</td><td>Improve support and separation of responsibilities between components, increase flexibility in delegation and tokens, enhance discoverability and client portability across data spaces, and prepare for broader adoption of emerging standards such as Verifiable Credentials.</td></tr><tr><td>Release date</td><td>21 November 2025</td></tr><tr><td>Change log</td><td><p><strong>Functional</strong></p><ul><li>Participants can now assign different Authorisation Registries per Service Provider or capability.</li><li>Delegation evidence supports conditions, that may be evaluated by the Authorisation Registry or by the Service Provider at the time of service consumption.</li><li>Participants can expose a Data Space Description for improved discovery.</li><li>Improved client portability across multiple data spaces by introducing the "claims" concept.</li><li>Clarified participant adherence indicators under a revamped section: Criteria for Participation (instead of Levels of Assurance).</li><li>Introduces Verifiable Credentials (W3C standard) as an additional, interoperable means for participants to authenticate, authorise, and interact across data spaces.</li></ul><p><strong>Technical</strong></p><ul><li>/parties and /capabilities endpoints are updated to declare multiple ARs.</li><li>Delegation evidence now supports conditions, which may reference attributes such as validFrom, validUntil, or certifications.</li><li>Party-related endpoints have been redesigned with a new parties-and-claims structure to improve portability across data spaces.</li><li>Verifiable Credentials support added, including standardised credential formats and presentation flows for identity and authorisation.</li></ul><p><strong>Operational</strong></p><ul><li>With introduction of Verifiable Credentials the roles and responsibilities are updated in the iSHARE Role model.</li><li>Updated and clarified onboarding process for participants.</li><li>Capability and Participant Registry metadata now support advanced configuration of AR per service provider.</li><li>Optional specifications can now be published via dataspace descriptions, enabling discovery while keeping core interoperability unchanged.</li><li>Improved documentation for multi-service AR setup and delegation path discovery models, including fallback logic and resolution priorities.</li><li>Documented rules on what fields can be locally overwritten (limited to SLA).</li></ul><p><strong>Legal</strong></p><ul><li>The assessment framework has been improved for all certified roles, making it role specific.</li></ul></td></tr></tbody></table>

<table><thead><tr><th width="225">Release 2.2</th><th></th></tr></thead><tbody><tr><td>Purpose</td><td><ul><li>Improve interoperability among global data ecosystems</li></ul></td></tr><tr><td>Release date</td><td>13 June 2025</td></tr><tr><td>Change log</td><td><p>All included RFCs are available <a href="https://gitlab.com/groups/ishare-foundation/cab/-/issues/?label_name%5B%5D=Release%202.2">here</a>.</p><p><strong>Functional</strong></p><ul><li>Improved iSHARE licenses and released a dedicated licenses portal on https://licenses.ishare.eu..</li></ul><p><strong>Technical</strong></p><ul><li>Added create and update specifications for managing parties at Participant Registry</li></ul><p><strong>Legal</strong></p><ul><li>Updates to license agreements</li></ul></td></tr></tbody></table>

<table><thead><tr><th width="225">Release 2.1</th><th></th></tr></thead><tbody><tr><td>Purpose</td><td><ul><li>Introduction of iSHARE-ID to enhance interoperability.</li><li>Update of terminology.</li><li>Introduction of standardised delegation creation requests.</li><li>Respecification of the /capabilities endpoint.</li><li>Decommissioning of PKIOverheid certificates.</li><li>Alternative onboarding for service consumers without PKI certificates.</li></ul></td></tr><tr><td>Release date</td><td>7 March 2025</td></tr><tr><td>Change log</td><td><p>All included RFCs are available <a href="https://gitlab.com/groups/ishare-foundation/cab/-/issues/?label_name%5B%5D=Release%202.1">here</a>.</p><p><strong>Functional</strong></p><ul><li>Supporting multiple identifiers and the Introduction of iSHARE-ID</li><li>Updated terminology (Data Space Governance Body and Participant Registry)</li><li>Standardised delegation requests</li></ul><p><strong>Technical</strong></p><ul><li>Multiple party identifiers and iSHARE DID Method</li><li>Respecification of /capabilities endpoint</li><li>Onboarding service consumers without PKI certificates</li></ul><p><strong>Operational</strong></p><ul><li>Updated onboarding processes</li><li>Decommissioning PKIOverheid certificates</li><li>Addition of Brand Guidelines to UI Guidelines</li></ul><p><strong>Legal</strong></p><ul><li>Updates to legal agreements</li></ul></td></tr></tbody></table>

<table><thead><tr><th width="225">Release 2.0.1</th><th></th></tr></thead><tbody><tr><td>Purpose</td><td><ul><li>Release of new framework website</li></ul></td></tr><tr><td>Release date</td><td>3 July 2024</td></tr><tr><td>Change log</td><td><ul><li>Minor typos only</li><li>All content has been copied to the new framework website</li></ul></td></tr></tbody></table>

<table><thead><tr><th width="225">Release 2.0</th><th></th></tr></thead><tbody><tr><td>Purpose</td><td><ul><li>Updated Roles</li><li>Updated Governance structure</li><li>Distinction and clarity in roles and governance</li><li>Updates in operational and functional processes</li></ul></td></tr><tr><td>Release Date</td><td>30 October 2023</td></tr><tr><td>Change log</td><td><p><strong>Introduction</strong></p><ul><li>The scheme is now known as the iSHARE Trust Framework</li><li>Updated goals, scope, guiding principles and governance.</li><li>Federation of Trust Framework</li></ul><p><strong>Functional</strong></p><ul><li>Added new role: Satellite</li><li>The scheme administrator is now the Satellite administrator</li><li>Minor fixes in key functionality</li></ul><p><strong>Technical</strong></p><ul><li>Updated Satellite role</li><li>Review of technical standards and minor fixes</li></ul><p><strong>Legal</strong></p><ul><li>Updated Satellite role</li><li>Updated Accession agreement and Terms of Use</li></ul><p><strong>Operational</strong></p><ul><li>New role - Satellite</li><li>Updated the operational processes of admission, withdrawal and incident management processes</li><li>Updated the service levels.</li></ul></td></tr></tbody></table>

<table><thead><tr><th width="225">Release 1.11</th><th></th></tr></thead><tbody><tr><td>Purpose</td><td><ul><li>Updated legal documents</li><li>Added new role: Scheme Administrator</li><li>Updated Governance structure</li><li>Small technical improvements</li></ul></td></tr><tr><td>Release date</td><td>16 November 2020</td></tr><tr><td>Change log</td><td><p><strong>Functional</strong></p><ul><li><p>Added new role: Scheme Administrator</p><ul><li>Participant admission process</li><li>Governance</li><li>Scheme trust model</li></ul></li><li>Human authorisation for IDPs is now optional and no longer mandatory</li></ul><p><strong>Technical</strong></p><ul><li>Human authorisation for IDPs is now optional and no longer mandatory. The associated CTT tests are no longer a requirement for certification.</li><li><p>Scheme administrators added and new attributes added to:</p><ul><li>Track which SA is responsible for the participant</li><li>Express the level of adherence of the participant.</li></ul></li></ul><p><strong>Operational</strong></p><ul><li><p>Updated the admission process for the Scheme Administrator:</p><ul><li>Admission of Scheme Administrator</li><li>Withdrawal of Scheme Administrator</li></ul></li><li><p>Updated the admission process for Parties:</p><ul><li>Admission through the Scheme Administrator</li><li>Reassignment of Scheme Administrator</li></ul></li><li>The governance structure changed to reflect the transition from the project phase</li><li>Added process of determining yearly participation fees.</li></ul><p><strong>Legal</strong></p><p>Updates:</p><ul><li>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.</li><li>Updated the Accession Agreement for Certified Parties to reflect the fact that Certified Parties are subject to an annual fee.</li><li>Updated the Accession Agreement for Adhering Parties to reflect the fact that Adhering Parties are subject to an annual fee.</li><li>Renewed the standard NDA to reflect the relation between the iSHARE foundation, Scheme Owner and Adoption.</li></ul></td></tr></tbody></table>

<table><thead><tr><th width="225">Release 1.10</th><th></th></tr></thead><tbody><tr><td>Purpose</td><td><ul><li>Updated the process for verifying eIDAS certificates</li><li>Update the admission process for Certified Parties</li><li>Added levels of assurance for Certified Parties</li><li>Added support for the use case where the Entitled Party is not an iSHARE Adhering Party, but is a customer of an iSHARE Service Provider</li><li>Small technical improvements</li></ul></td></tr><tr><td>Release date</td><td>24 June 2019</td></tr><tr><td>Change log</td><td><p><strong>Functional</strong></p><ul><li>Updated the functional requirements for Certified Parties (references to eHerkenning have been removed and replaced by relevant requirements)</li></ul><p><strong>Technical</strong></p><ul><li>Updated the process for verifying eIDAS certificates (now uses the same process as PKI-Overheid certificates)</li><li>Added level of assurance to the Party Info endpoint at the Scheme Owner (for Certified Parties)</li><li>Clarified the use of acr_values in the H2M flow to request a minimal level of assurance</li><li>Clarified the headers used for JWE in the H2M flow</li></ul><p><strong>Operational</strong></p><ul><li><p>Updated the admission process for Certified Parties, including the following changes:</p><ul><li>Admission to eHerkenning is no longer required</li><li>Added the concept of Levels of Assurance for Certified Parties</li><li>Added the Assessment Framework for Certified Parties to determine the Level of Assurance of a Certified Party</li></ul></li></ul><p><strong>Legal</strong></p><ul><li>Updated the terms of use to reflect the use case where the Entitled Party is not an iSHARE Adhering Party, but is a customer of an iSHARE Service Provider</li></ul></td></tr></tbody></table>

<table><thead><tr><th width="225">Release 1.9</th><th></th></tr></thead><tbody><tr><td>Purpose</td><td>Enable Human to Machine (H2M) authorisations</td></tr><tr><td>Release date</td><td>5 April 2019</td></tr><tr><td>Change log</td><td><p><strong>Functional:</strong></p><ul><li>Updated primary Human to Machine use cases to reflect changes from RFC 010, which added the authorisation flow to these cases</li></ul><p><strong>Technical:</strong></p><ul><li>Added technical specifications on the generic authorisation flow for Human to Machine (H2M) interactions as facilitated by Identity Providers in the iSHARE Scheme, to reflect changes from RFC 010</li><li>Modified technical specifications for the capabilities endpoint of all iSHARE Parties</li></ul><p><strong>Operational</strong></p><ul><li>No changes</li></ul><p><strong>Legal</strong></p><ul><li>Updated governance framework to reflect that Stichting iSHARE Foundation has been created</li></ul><p><strong>Miscellaneous</strong></p><ul><li>Rearranged pages and sections to improve readability</li><li>Material has been moved from the Scheme to the Developer Portal to improve the readability and usability of both</li></ul></td></tr></tbody></table>

<table><thead><tr><th width="225">Release 1.8</th><th></th></tr></thead><tbody><tr><td>Purpose</td><td>Enable Human to Machine (H2M) interactions and finalise contracts for signing between iSHARE Foundation and iSHARE Participants.</td></tr><tr><td>Release date</td><td>31 October 2018</td></tr><tr><td>Change log</td><td><p><strong>Functional:</strong></p><p>-</p><p><strong>Technical:</strong></p><ul><li>Added technical specifications on the generic authentication flow for Human to Machine (H2M) interactions as facilitated by Identity Providers in the iSHARE Scheme.</li></ul><p><strong>Operational</strong></p><p><strong>-</strong></p><p><strong>Legal</strong></p><ul><li>Minor modifications to Terms of Use and the Accession Agreements for Adhering Paries and Certified Parties</li><li>Moved GDPR Factsheet and templates for Data Exchange Agreement and Data Processor Agreements to the 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.</li></ul><p><strong>Miscellaneous</strong></p><ul><li>The governance framework is updated</li><li>Rearranged pages and sections to improve readability</li></ul></td></tr></tbody></table>

<table><thead><tr><th width="225">Release 1.7</th><th></th></tr></thead><tbody><tr><td>Purpose</td><td>Create a better overview of all API specs in a singular space, to make it easier for developers to implement iSHARE and to improve the readability of the iSHARE Scheme</td></tr><tr><td>Release date</td><td>28 June 2018</td></tr><tr><td>Change log</td><td><p><strong>Functional:</strong></p><p>-</p><p><strong>Technical:</strong></p><ul><li>The API technical specifications have been moved to a dedicated developer portal.</li><li>Adjusted specification for JSON Web Token (JWT) to facilitate certificate validation under eIDAS.</li></ul><p><strong>Operational</strong></p><ul><li>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.</li></ul><p><strong>Legal</strong></p><p>-</p><p><strong>Miscellaneous</strong></p><ul><li>Rearranged pages and sections to improve readability</li><li>The governance framework is updated</li><li>The project history is updated</li></ul></td></tr></tbody></table>

<table><thead><tr><th width="225">Release 1.6</th><th></th></tr></thead><tbody><tr><td>Purpose</td><td>Lowering barriers for parties to start using iSHARE</td></tr><tr><td>Release date</td><td>11 May 2018</td></tr><tr><td>Change log</td><td><p><strong>Functional:</strong></p><p>-</p><p><strong>Technical:</strong></p><ul><li>For authentication purposes, the use of digital certificates within iSHARE will be limited initially to certificates issued under PKIOverheid.</li></ul><p><strong>Operational</strong></p><ul><li>The admission process for Certified Parties and Adhering Parties is merged into one generic process. Role-specific requirements may apply.</li><li>The order of admission steps is changed to enable new iSHARE entrants to start testing before a contract is signed.</li></ul><p><strong>Legal</strong></p><p>-</p><p><strong>Miscellaneous</strong></p><ul><li>Rearranged pages and sections to improve readability</li><li>The governance framework is updated</li></ul></td></tr></tbody></table>

<table><thead><tr><th width="225">Release 1.5</th><th></th></tr></thead><tbody><tr><td>Purpose</td><td>First public version of the iSHARE Scheme that can be used by launching customers</td></tr><tr><td>Release date</td><td>14 December 2017</td></tr><tr><td>Change log</td><td><ul><li><p>Updated specifications for all content of the iSHARE Scheme:</p><ul><li>Functional</li><li>Technical</li><li>Operational</li><li>Legal</li></ul></li><li>Significantly updated and rearranged sections for readability, including a <a href="../main-aspects-of-the-ishare-trust-framework">main scheme aspects</a>- and illustrative <a href="../use-cases">use cases</a> chapter with new depictions; Integrated (technical) specifications, generic and per iSHARE role.</li></ul></td></tr></tbody></table>