> 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/identity-and-attestation-management/guiding-questions.md).

# Guiding questions

{% hint style="success" %}
**Purpose:** Define how legal entities and representatives will be uniquely and reliably identified.
{% endhint %}

1. **Participant Identification**

* *What identifiers (EORI, VAT ID, DUNS, DID, etc.) will be accepted for legal entities?*
* *How will natural persons be identified and cryptographically bound to their role as authorised representatives of legal entities (e.g., Verifiable Credentials such as W3C/OpenID?*
* *Will eIDAS-compliant solutions be mandatory, optional, or one of several supported schemes?*
* *Will authentication rely on PKI?*

{% hint style="success" %}
**Purpose:** Establish the credentials and attestations required for onboarding, compliance, and sector-specific participation.
{% endhint %}

2. **Credential Types & Attestations**

* *Which credential types are required for onboarding (identity, membership, compliance)?*
* *Will W3C/OpenID Verifiable Credentials be the primary format for organisational identity and representative roles?*
* *What sector-specific or regulation-driven attestations will participants need to provide?*
* *Will conformity assessments based on ISO/IEC 17000 be recognised for certain claims/attestations?*
* *How will validity periods, renewals, and revocations be managed?*

{% hint style="success" %}
**Purpose:** Determine who issues credentials, how trust anchors are structured, and how verification will operate.
{% endhint %}

3. **Credential Issuance & Verification**

* *Who acts as the Trust Anchor(s) for credential issuance?*
* *Will credential issuance be centralised under DSGA or federated across multiple accredited providers?*
* *How will the verification process be implemented (centralised compliance service vs. distributed verification)?*
* *How are credential issuance, renewal, and revocation managed (trust anchors, revocation lists/registries)?*
* *Will verification align with eIDAS/ETSI trust lists and support automated status/revocation checks?*

{% hint style="success" %}
**Purpose:** Adopt interoperable standards to ensure credentials are machine-readable and compatible across data spaces.
{% endhint %}

4. **Standards & Interoperability**

* *Which technical standards (W3C VC, DIDs, OIDC4VC, SHACL, ETSI Trusted Lists) will be adopted*
* *Will JSON-LD be used for credential data models and metadata?*
* *How will interoperability with other data spaces and trust frameworks be ensured?*
* *Will machine-readable rulebooks be published for automated compliance checks?*
* *Will PKI profiles and secure-channel requirements be defined for credential transport?*

{% hint style="success" %}
**Purpose:** Set rules for managing credential changes, revocations, and disputes to maintain trustworthiness.
{% endhint %}

5. **Governance & Lifecycle Management**

* *How will credential revocation, suspension, and reinstatement processes be triggered and managed?*
* *How will changes in participant status (mergers, closures, ownership changes) be handled in credential records?*
* *What is the escalation process for identity disputes or fraudulent credential usage?*
* *Where and how will conformance evidence (certificates, manifests, audits) be published for discovery (e.g., in catalogs/registries)?*


---

# 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/identity-and-attestation-management/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.