> For the complete documentation index, see [llms.txt](https://trustbok.ishare.eu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://trustbok.ishare.eu/apply-ishare/participant-registry/deployment-and-use-cases.md). # Deployment & Use Cases The iSHARE Trust Framework allows flexibility in how the Participant Registry is implemented and operated across data spaces. Depending on governance, scale, and technical preferences, different deployment models can be adopted. #### 1. Centralised model In a pilot or earlier phase, single Participant Registry cab be responsible for managing all participants within a data space. * One common registry acts as the primary source of trust assurance * Simplifies governance and onboarding processes * Easier to manage consistency and compliance This model is typically suitable for: * Organisations piloting trusted data exchange in sectors with tightly governed or sensitive data. * Highly secure environments with a single governance authority #### 2. Federated model In a federated model, multiple Participant Registries coexist, each responsible for a subset of participants or domains. * Each registry operates under its own governance context * Participant information can be shared across registries * Claims may be maintained across registries when allowed This model supports: * collaboration between multiple data spaces * domain-specific governance structures #### 3. Distributed / decentralised model The iSHARE Trust Framework supports a distributed approach, where Participant Registries operate as nodes within a broader network. * No single central authority controls all participant data * Registries contribute to a shared trust infrastructure * Interoperability is enabled through common standards and governance This model aligns with: * cross-data space interoperability * scalability across sectors and geographies
#### Considerations When choosing a deployment model, data spaces typically consider: * governance structure and responsibilities * level of trust required between domains * scalability and performance needs * interoperability requirements Regardless of the model, all Participant Registries must operate in accordance with the iSHARE Trust Framework to ensure consistent trust and verification. ### Use Cases (See more [here](https://ishare.eu/ecosystem/ishare-in-data-spaces/)) This section illustrates how the Participant Registry is applied in practice, focusing on its role in enabling trust, verification, and discoverability. #### 1. DVU ([Datastelsel Verduurzaming Utiliteit - Data System for Sustainability in Utility Buildings](https://ishare.eu/ecosystem/ishare-in-data-spaces/dvu/)) DVU focuses on enabling trusted data sharing to support the sustainability and energy optimisation of utility buildings and non-residential buildings, involving stakeholders such as building owners, service providers, technology providers, and public authorities. Role of the Participant Registry: * Ensures that organisations participating in the DVU data space are validated and onboarded according to governance and sustainability-related criteria * Maintains participant information and claims, such as roles (e.g. building owner, energy service provider) and relevant capabilities * Enables participants to discover and verify trusted counterparts before exchanging building, energy, or performance data Value: * Supports secure and trusted collaboration across stakeholders involved in building sustainability * Reduces onboarding complexity for new participants in the ecosystem * Enables scalable data sharing to support energy optimisation, monitoring, and reporting use cases #### 2. DMI ([Dutch Metropolitan Innovations](https://dmi-ecosysteem.nl/)) DMI focuses on enabling data-driven collaboration within metropolitan environments, involving public authorities, infrastructure operators, and private organisations working on mobility, infrastructure, and urban development. Role of the Participant Registry: * Ensures that organisations participating in the DMI data space are properly onboarded and validated according to governance rules * Maintains participant information and claims, including roles (e.g. public authority, service provider) and capabilities * Enables participants to discover and verify trusted partners before exchanging data or services Value: * Supports trusted collaboration across public and private stakeholders in urban environments * Reduces friction in onboarding new participants into the ecosystem * Enables scalable and interoperable data sharing for mobility and infrastructure use cases #### 3. BDI ([Basic Data Infrastructure](https://ishare.eu/home/ecosystem/data-spaces/bdi/)) The Basic Data Infrastructure (BDI) is a Dutch initiative designed as a federative, “soft” infrastructure, a set of agreements that enables secure, trusted, and automated data sharing across the logistics and supply chain sector. It connects a wide range of stakeholders, including shippers, logistics service providers, ports, and authorities, without requiring a central platform. Role of the Participant Registry: * Supports the federative model by enabling trusted identification and verification of participants across organisational boundaries * Maintains claims related to roles, participation, and compliance within the logistics ecosystem * Enables participants to discover and validate trusted partners before initiating data exchange * Supports interoperability across domains by allowing claims to be recognised beyond a single registry Value: * Enables trust without centralisation, aligning with the federative nature of BDI * Reduces the need for bilateral agreements between supply chain partners * Supports scalable and automated data sharing across complex logistics networks * Facilitates interoperability between different systems and data spaces #### 4. SAGE/ GDDS (Data Space for a Sustainable Green Europe) SAGE focuses on enabling trusted data sharing to support sustainability goals across Europe, involving a wide range of participants such as public authorities, private organisations, and service providers. Role of the Participant Registry: * Ensures that participants are onboarded according to governance rules aligned with sustainability objectives * Maintains claims related to roles, compliance, and potentially sustainability-related attributes * Enables participants to verify trusted counterparts across organisational and national boundaries Value: * Supports trustworthy collaboration in sustainability-driven ecosystems * Enables controlled and transparent participation aligned with policy and regulatory requirements * Facilitates interoperability between diverse stakeholders contributing to green initiatives #### 5. WEBUILD (Wallet Ecosystem for Business and payments Use cases on Identification, Legal representation and Data sharing) In ecosystems using Verifiable Credentials: Role of the Participant Registry: * Issues Participant Credentials as Verifiable Credentials * Acts as a trusted issuer within the ecosystem * Enables verification of credentials across data spaces Value: * Supports portability of trust across different environments * Reduces reliance on registry lookups alone * Enables participants to prove attributes independently --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://trustbok.ishare.eu/apply-ishare/participant-registry/deployment-and-use-cases.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.