> For the complete documentation index, see [llms.txt](https://template.ishare.eu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://template.ishare.eu/technical-building-blocks/data-sovereignty-and-trust/trust-framework/guiding-questions.md).

# Guiding questions

{% hint style="success" %}
**Purpose:** Define the roles and recognition of trust anchors, providers, and accredited entities in the data space.
{% endhint %}

1. **Trust Entities & Roles**

* *Which Trust Anchors will the data space recognise (e.g., EU authorities, accredited certification bodies)?*
* *What roles will Trust Service Providers play in the ecosystem?*
* *Will the data space maintain its own accredited trust entities or federate from existing frameworks?*

{% hint style="success" %}
**Purpose:** Specify baseline and sectoral criteria for trust entities, aligned with the data space rulebook.
{% endhint %}

2. **Criteria & Rulebook Alignment**

* *What baseline criteria must a trust entity meet to be recognised in the data space?*
* *How will sector-specific or regulation-driven trust requirements be added to the rulebook?*
* *Will the data space adopt existing cross-sector rules (e.g., Gaia-X trust principles) or develop bespoke ones?*
* *How will conformity with these criteria be evidenced (e.g., ISO/IEC 17000-based attestations, certificates)?*

{% hint style="success" %}
**Purpose:** Establish how claims and attestations will be validated, exchanged, and revoked when necessary.
{% endhint %}

3. **Validation & Verification Processes**

* *How will claims and attestations be collected, exchanged, and validated?*
* *What technical standards (e.g., W3C VC, ISO CASCO) will the data space require for claims formatting?*
* *How will revocation and suspension of trust entities or credentials be handled?*
* *Will verification support dynamic attributes (e.g., DAT) where applicable to usage control?*

{% hint style="success" %}
**Purpose:** Create transparent, discoverable registries of trust entities to support verification and compliance.
{% endhint %}

4. **Registry & Transparency**

* *What type of registry will store accredited and revoked trust entities?*
* *How will participants and third parties discover and verify trust entities?*
* *Will registry entries be machine-readable for automated compliance checks?*

{% hint style="success" %}
**Purpose:** Integrate and adapt existing trust frameworks to meet high-risk requirements.
{% endhint %}

5. **Leveraging Existing Frameworks**

* *Which existing trust frameworks will the data space leverage (Gaia-X, iSHARE, IDSA, domain-specific)?*
* *How will the data space extend these frameworks for domain-specific needs?*
* *Will stricter trust criteria be applied for high-risk data or sensitive transactions?*
* *How will cross-framework interoperability be proven (conformance testing, cross-certification, or mapped profiles)?*


---

# 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://template.ishare.eu/technical-building-blocks/data-sovereignty-and-trust/trust-framework/guiding-questions.md?ask=<question>&goal=<endgoal>
```

`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.