> 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/authorisation/delegation-chains/context-matters.md).
# Context Matters
Simulation and case studies (including logistics, healthcare, and cross-border data spaces) confirm that no single model solves all challenges. Recursive models provide flexibility and revocation robustness, but require multiple lookups. Concatenation models improve efficiency, but at the cost of privacy and adaptability. Macaroons excel in privacy and speed, but complicate governance and auditing.
The choice of model depends on context: logistics chains may favour flexibility (Previous Party ID), regulated sectors may prioritise auditability (Previous Delegation ID), performance-driven IoT exchanges may prefer concatenation, and privacy-sensitive domains may lean towards macaroons.
For iSHARE, the key is not to prescribe a single approach, but to ensure interoperability across models. The frameworkâs attributes (`delegation_path`, `previous_steps`) and clarifications (e.g., rules must not contain targets in delegation evidence) provide the baseline for compatibility. This allows ARs and participants to adopt the model that best fits their context without fragmenting the ecosystem. The following Table gives a final overview of the benefits and limitations of each model:
Table 5: Consolidated strengths and weaknesses across delegation models.
### A Continued Commitment to Optimisation
The models presented illustrate that there are several valid methods to manage delegation chains, each with their own strengths and trade-offs. Recursive approaches emphasise resilience and flexibility, concatenation offers speed and implementation ease, and macaroons provide strong privacy and cryptographic efficiency.
By documenting these patterns side by side, implementers can make informed choices suited to their requirements, while ensuring interoperability across data spaces. This approach reinforces that the data spaces remains secure.
---
# 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/authorisation/delegation-chains/context-matters.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.