> 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-interoperability/data-models/guiding-questions.md).

# Guiding questions

{% hint style="success" %}
**Purpose:** Define the key concepts and relationships that must be standardised to ensure semantic alignment across use cases.
{% endhint %}

1. **Understanding Scope & Semantics**

* *Which data products require semantic expression through a shared data model?*
* *Which concepts, entities, and relationships must be standardised for your use case?*

{% hint style="success" %}
**Purpose:** Decide whether to reuse, extend, or develop new data models based on adoption, compatibility, and domain standards.
{% endhint %}

2. **Selecting or Creating Models**

* *Can existing data models be reused directly? If not, can they be extended rather than replaced?*
* *Which standards organisations or communities maintain the most relevant models for your domain?*
* *What factors (adoption level, integration compatibility, constraints) influence model selection?*

{% hint style="success" %}
**Purpose:** Choose meta-standards and reference vocabularies to ensure consistent, machine-readable representation of data models.
{% endhint %}

3. **Expressing the Models**

* *Which meta-standards will be used to represent data models? (e.g., RDF/OWL, SKOS, JSON Schema, XML Schema, CSVW)?*
* *What reference datasets or controlled vocabularies (e.g., EU vocabularies, ISO codes) will be linked?*
* *Does your dataspace use W3C as a recognized standards for Identity Management?* 
* *Does Dataspace use JSON-LD type as a recognized standard of Identity & Access Management?* 
* *Are vocabularies in RDF (Resource Description Framework OWL complaint?* 

{% hint style="success" %}
**Purpose:** Establish processes for managing ownership, versioning, and stakeholder engagement around data models.
{% endhint %}

4. **Governance and Maintenance**

* *Who will act as the data model provider for each model (e.g., Standards Development Organisation, The governance team, sectoral community)?*
* *How will versioning, change approval, and stakeholder engagement be managed?*
* *What processes will be in place for resolving conflicts or inconsistencies between models?*

{% hint style="success" %}
**Purpose:** Provide accessible platforms and services to host, discover, and link data models with exchange schemas and APIs.
{% endhint %}

5. **Tooling and Accessibility**

* *Which Vocabulary Service platform will host the data models?*
* *How will models be made discoverable across other EU data spaces?*
* *How will models be linked to actual data exchange schemas and APIs?*
* *Does your dataspace have a browser-based UI & API?*
* *Does your dataspace provide a vocabulary service?*


---

# 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-interoperability/data-models/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.