> 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/business-and-organisational-building-blocks/business-building-blocks/data-space-offerings/guiding-questions.md).

# Guiding Questions

{% hint style="success" %}
**Purpose of this Building Block Component:** The offering comprises data assets and associated services that enable use cases. This includes: data products and services.
{% endhint %}

{% hint style="info" %}
It is essential to bundle offerings in a way that reflects user needs (e.g. emissions dashboard for real estate owners; API-based footprint verification for consultants). 

**This should also account for:**

* Licensing models
* Terms of use
* User support services
* Interoperability with EU data infrastructure (e.g. Data4Sustainability, EUDR registries)

A well-structured offering enhances usability, legal certainty, and trust, increasing uptake and long-term engagement.
{% endhint %}

**Data products:** structured environmental, spatial, emissions, material flow, or asset-level data

**Services:** access control, consent management, data quality assurance, enrichment tools, compliance reporting modules

{% hint style="success" %}
**Purpose:** Clearly structured environmental, spatial, emissions, material flow, and asset-level data.
{% endhint %}

1. **Data Products**

* *What key data assets will be initially offered?*
* *How will data assets be standardised and validated?*
* *How frequently will data be updated and shared?*
* *How can data products be designed to be modular and reusable across multiple use cases?*
* *How can data assets be standardized and validated efficiently?*
* *How can offerings remain aligned with participant needs over time?*

2. **Functional Questions:**

* *What data model will be used?* 

3. **Functional/Technical Questions:**

* *How can offerings remain aligned with participant needs over time?*
* *What is the source of the data?* 

{% hint style="success" %}
**Purpose:** 

* Data access control & consent management
* Data quality assurance & validation
* Data enrichment tools (e.g., analytics, visualisation)
* Compliance reporting modules (aligned with CSRD, etc)
  {% endhint %}

4. **Associated Services**

* *Which services are critical to the initial use cases?*
* *How will compliance and consent management be technically enforced?*
* *What are the minimum standards for data quality assurance?*
* *Which services add the most value to participants while remaining interoperable?*
* *How should services be prioritized based on current and future use cases?*

{% hint style="success" %}
**Purpose:** Licensing models clearly aligned with open data standards or commercial/regulated usage. Define clear terms of use, including IP rights, access rights, and permitted usage.
{% endhint %}

5. **Licensing and Terms of Use**

* *Under which license models will data be provided?*
* *Are there specific data-usage restrictions or access tiers?*

{% hint style="success" %}
**Purpose:** Define helpdesk, training resources, and dedicated support channels.
{% endhint %}

6. **User Support**

* *How will support needs differ across stakeholders (public/private, technical/non-technical)?*
* *Who will deliver these support services (in-house, third-party)?*
* *How can support resources be tailored to different types of participants?*
* *How can training ensure quality data contribution?*

{% hint style="success" %}
**Purpose:** Alignment with EU-wide data infrastructures  (Data4Sustainability, EUDR registries, Copernicus) and Common EU Data Spaces (CEADS, EMDS, etc). Define Standardised data formats and APIs.
{% endhint %}

7\. **Interoperability**

* *Which external EU registries and frameworks should be integrated to ensure compliance and interoperability?*
* *How will ongoing alignment with evolving EU data interoperability standards be ensured?*

<br>


---

# 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/business-and-organisational-building-blocks/business-building-blocks/data-space-offerings/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.