> 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/documentation-structure.md).
# Introduction to the iSHARE Data Space Template
This page provides an overview of the Data Space Template's Building Blocks.
This documentation is primarily structured around the bulding blocks defined in the [Data Spaces Blueprint 3.0 by the Data Spaces Support Centre](https://blueprint.dssc.eu/), which is based on the[ Open DEI project](https://design-principles-for-data-spaces.org/).
Building blocks are basic units or components that can be implemented and combined with other building blocks to achieve the functionality of a data space.
Figure 1. Overview of DSSC Data Spaces Blueprint v2.0 Building Blocks.
{% hint style="info" %}
Data spaces are allowed to publish agreements on topics other than the topics above. iSHARE provides the following extra topics, which are also covered in the iSHARE Trust Framework
* [Operational processes](https://framework.ishare.eu/detailed-descriptions/operational/operational-processes)
* [Glossary](/glossary.md)
{% endhint %}
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://template.ishare.eu/documentation-structure.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
