> 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 #### What this template is The iSHARE Data Space Template helps data space initiatives in their development along 17 distinct Building Blocks. It follows [Blueprint 3.0](https://blueprint.dssc.eu/) of the Data Spaces Support Centre (DSSC), which itself builds on the [OpenDEI Design Principles for Data Spaces](https://design-principles-for-data-spaces.org/). The difference of this Template is the lens. For every DSSC Building Block, the template explains how the [iSHARE Trust Framework](https://framework.ishare.eu/) addresses it: what iSHARE already covers and how to implement it, what the Framework supports, and which decisions stay with your data space. The DSSC Blueprint tells you what a data space needs. This Template guides data space initiatives how those needs can be met by implementing the iSHARE Trust Framework. #### Who it is for The template is written for data space initiators, governance authorities, and technical leads who are developping a data space. Regardless if the iSHARE Framework is being considering, this template serves as a usefule guide to understand where, and how, trust can be insured withinin a Data Space. #### How the template is structured The template follows the DSSC Building Blocks. A building block is a basic unit that can be implemented and combined with others to deliver the functionality of a data space. The building blocks fall into two categories: Business / Organisational Building Blocks, and Technical Building Blocks.

Figure 1. Overview of DSSC Data Spaces Blueprint v2.0 Building Blocks.

#### How to read the building block pages Each building block page discusses the following elements: an overview of the DSSC definition of each Building Block, how this Building Block relates to the iSHARE Trust Framework, guiding questions data space initiatives should consider, and further resources. You can read the template from start to finish or go straight to the building block you need. The guiding questions are the practical core. Working through them with your stakeholders acts as a useful excersise to identify your priorities. In general, the iSHARE Trust Framework relates to the Building Blocks in a varying degree: * **Fully supported.** In the Data Sovereignty & Trust Building Block, and in large parts of the legal and governance building blocks, the iSHARE Trust Framework offers ready-made agreements, roles and specifications. Examples include identification, authentication and authorisation, the Participant Registry and Authorisation Registry, and a harmonised legal framework. Here the template shows what you can adopt directly. * **Partially supported.** For building blocks such as Participation Management, Data Exchange, and Provenance, Traceability & Observability, iSHARE provides references on how these building blocks interact with the elements needed to ensure trust. The data space, however, still makes its own design decisions. * **Defined by your Data Space.** Business models, use cases, data models and value creation services are specific to each data space and need to be defined internally, case by case. iSHARE does not prescribe them, but the template places them in a wider context so you can see how they connect to the trust layer * **iSHARE supports your choices with references.** For building blocks such as Participation Management, Data Exchange, and Provenance, Traceability & Observability, iSHARE provides references on how these building blocks interact with the elements needed to ensure trust. The data space, however, still makes its own design decisions. * **iSHARE offers suggestions.** Business models, use cases, data models and value creation services are specific to each data space and need to be defined internally, case by case. iSHARE does not prescribe them, but the template places them in a wider context so you can see how they connect to the trust layer The template is not a substitute for the DSSC Blueprint or the iSHARE Trust Framework. This template is a guide that connects to the iSHARE Trust Framework. ### How to use this template for your data space **Step 1: Get to know the building blocks.** Start with Figure 1 to familiarise yourself with the full set of building blocks. Then read through the Building Blocks in this Template to get a complete understanding of what a complete data space involves, and where iSHARE already does the work for you. **Step 2: Take stock of where you are.** Go through the building blocks to get an initial idea where you stand and mark each one as *in place*, *partly in place* or *not yet addressed*. The result is a clear overview of the gaps you still need to close in your Data Space development process. **Step 3: Set your priorities.** Decide which building blocks to tackle first. A practical order is to: * adopt what iSHARE already provides, so your trust foundation is in place early; * then make the design choices where iSHARE supports you; * in parallel, develop only the elements your data space needs to define for (a) simple, yet sustainable use case(s). **Step 4: Work through the guiding questions together.** For each priority building block, use the adjacent guiding questions as the agenda for sessions with your stakeholders. The [Co-Creation & Change Management Methodology](https://template.ishare.eu/supporting-tools-and-methodologies/co-creation-and-change-management-methodology) helps you plan and run these sessions, and handle the changes they bring. Ensure that each building block has been assigned an owner and record decisions as you go. **Step 5: Turn your answers into agreements.** Bring your answers together into a first version of your rulebook. Where iSHARE provides the answer, refer to or adopt the relevant iSHARE agreements and specifications. Where you made your own choices, document them clearly so participants know what applies to them. **Step 6: Implement using the further resources.** Use the further resources on each page to move from decision to implementation. They link to the relevant sections of the iSHARE Trust Framework, DSSC material, or other supporting tools. **Step 7: Review and iterate.** A data space evolves as participants, use cases, and regulations change. Return to the template when you add new use cases or participants, or when your context changes, and update your agreements accordingly. #### Supporting tools and methodologies The [Co-Creation & Change Management Methodology](https://template.ishare.eu/supporting-tools-and-methodologies/co-creation-and-change-management-methodology) offers a practical approach to developing your rulebook together with your participants. It complements the DSSC’s own co-creation method and the DSSC Toolbox. Additionally, the iSHARE [Glossary](https://template.ishare.eu/glossary) provides descriptions of core terminology. The [Operational Processes](https://framework.ishare.eu/detailed-descriptions/operational/operational-processes) of the iSHARE Trust Framework presents all the operational processes necessary to administer the iSHARE Trust Framework (specifications), network and brand. --- # 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.