> For the complete documentation index, see [llms.txt](https://bdi.gitbook.io/bdi-public-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://bdi.gitbook.io/bdi-public-documentation/readme/introduction/bdi-technical-roles.md). # BDI Technical Roles ## 1. Introduction The building block aims to define BDI's technical roles, including Identity Provider, Identity Broker, Association Administrator, Data Owner, Data Service Provider, and Data Consumer. Each role plays a crucial part in managing identity, data control, and service provision within BDI's framework. ## 2. Purpose of this building block The purpose of this building block is to define the technical roles in BDI. ## 3. Concepts The technical roles of the BDI are given and explained below.

Role	Description
Identity Provider	The Identity Provider-role is fulfilled by a legal entity whose tooling identifies and authenticates humans (and specifically, Human Data Consumers representing Data Consumers).
Identity Broker	The Identity Broker-role is fulfilled by a legal entity that provides Data Service Providers access to different Identity Providers, and that offers humans the option to choose with which Identity Provider to identify and authenticate themselves.
Association Administrator	Functionary responsible for operating the services of a BDI Association reporting to its Members.
Data Owner	The data Owner is a legal entity who: Has control over data and access to data Controls decisions on Data Sovereignty and Trust Sovereignty Controls authorization policies, representation rules, professional qualification verification of staff and contractors Controls subscription to the Event Pub/Sub Service, and publishing of events to subscribers Controls discovery and endpoints Controls roles assumed by entity
Data Service Provider	A Data Service Provider that acts under supervision and on behalf of the Data Owner
Data Consumer	Requests access to data and/or Representation Register and/or Professional Qualification Register of the Data Owner Controls discovery and endpoints Requests subscription to Event Pub/Sub Service of the Data Owner, receives and evaluates events.

## 4. Implementation Considerations Implementation of the basic BDI mechanisms assumes the existence of these technical roles. ## 5. Interactions with other building blocks Digital Identity Authentication Authorization Association Register ## 6. Further reading --- # 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://bdi.gitbook.io/bdi-public-documentation/readme/introduction/bdi-technical-roles.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.