> 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/understand-ishare/role-mapping/eudi-wallet-arf-actor-mapping.md).

# EUDI Wallet ARF actor mapping

This page maps iSHARE roles to the closest actor terms used in the **EUDI Wallet Architecture and Reference Framework (ARF)**. The mapping is only applicable in wallet-based interaction patterns (e.g., a service requests/receives attributes from an EUDI Wallet). It is not intended as a general-purpose crosswalk between iSHARE and data space initiatives already covered on the[ Role Nomenclature](/understand-ishare/role-mapping.md) page.

{% hint style="info" %}
This mapping is based on the **latest tagged ARF release:** [**v2.7.3**.](https://eudi.dev/2.7.3/#architecture-and-reference-framework)
{% endhint %}

<table><thead><tr><th width="173.1484375">iSHARE role</th><th width="218.57421875">Closest ARF actor term(s)</th><th>Notes / when this applies</th></tr></thead><tbody><tr><td><strong>Service Provider</strong> </td><td><strong>Relying Party</strong>, <strong>Relying Party Instance</strong></td><td>When the Service Provider requests/receives PID or attestations from a Wallet Unit to deliver a service.</td></tr><tr><td><strong>Service Consumer</strong> </td><td><strong>User</strong> (often: <strong>Wallet User</strong>)</td><td>When the consumer interacts using a Wallet Unit (directly or via a solution acting on the user's behalf).</td></tr><tr><td><strong>Human Service Consumer</strong> </td><td><strong>Wallet User</strong></td><td>The human actor controlling/using the Wallet Unit in the interaction flow.</td></tr><tr><td><strong>Identity Provider</strong> </td><td><strong>PID Provider</strong> and/or <strong>Attestation Provider</strong></td><td>Depends on what is issued/managed: PID (identity) vs attestations (attributes).</td></tr><tr><td><strong>Participant Registry</strong> </td><td><strong>Registrar</strong> (e.g., for relying parties); related <strong>Trusted List</strong> concepts</td><td>Only for wallet-ecosystem registration/listing (not a full equivalent of iSHARE participant lifecycle governance).</td></tr><tr><td><strong>Certified Party</strong></td><td><strong>Conformity Assessment Body (CAB)</strong> (closest concept)</td><td>Only in the sense of conformity assessment/certification used in the EUDI Wallet ecosystem.</td></tr><tr><td><strong>Trust Anchor</strong></td><td><strong>Trust Anchor</strong></td><td>Same term in ARF; used for anchors that support verification/trust decisions in wallet interactions.</td></tr></tbody></table>

The following iSHARE roles are primarily data-space governance/federation roles out of scope for wallet interaction actor mapping (see [Glossary](https://framework.ishare.eu/glossary-and-legal-notices/glossary)) :

* **Scheme Owner**&#x20;
* **Data Space Governance Body**&#x20;
* **Authorisation Registry**&#x20;
* **Identity Broker**&#x20;


---

# 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:

```
GET https://trustbok.ishare.eu/understand-ishare/role-mapping/eudi-wallet-arf-actor-mapping.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.