> For the complete documentation index, see [llms.txt](https://i4trust.ishare.eu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://i4trust.ishare.eu/open-call-1/dare.md).

# DARE

The energy crisis and surging fossil fuel prices have prompted a need for improved energy management in residential and commercial buildings. Traditional energy-saving methods fall short, demanding continuous, real-time management specific to individual consumer habits. 

Faults in equipment or energy leaks require swift detection for energy efficiency. This is possible with contextual data from IoT devices and sensors located in smart buildings, which operate within specific vendor ecosystems, resulting in data silos and limited interoperability across systems.\
\
Data Spaces for smaRt Energy (DARE) addresses these challenges by enabling the delivery of sectoral services in vendor-specific buildings, improving energy management and efficiency. DARE creates a data space for data from smart energy equipment and contextual data from smart sensors within buildings, offering a robust access control system with defined access policies and the ability to “revoke” access rights as needed. [i4Trust building blocks](https://github.com/i4Trust/building-blocks) were pivotal in developing DARE's envisioned data space. This is facilitated by configuring the iSHARE Authorisation Registry and storing data in the FIWARE Context Broker using transcoders to make access control decisions using data. This is included in auxiliary information provided by the [iSHARE Participant Registry](https://trustbok.ishare.eu/apply-ishare/participant-registry).

Learn more about DARE in the Impact Story.

{% file src="/files/pMPdLg2DvJawTxhtFjmP" %}

#### Contributors:

<table data-view="cards"><thead><tr><th></th><th></th><th></th></tr></thead><tbody><tr><td><img src="/files/yVdPzIl1mxaRZZTyI28u" alt="" data-size="original"></td><td></td><td></td></tr><tr><td><img src="/files/TMknNklaSoOzyAhCq1MI" alt="" data-size="original"></td><td></td><td></td></tr><tr><td><img src="/files/cL5s0B2WU0tPL11Bw8B0" alt="" data-size="original"></td><td></td><td></td></tr><tr><td><img src="/files/DGyBom19SvgRI30wjV3L" alt="" data-size="original"></td><td></td><td></td></tr><tr><td><img src="/files/uT4Jd1ERKS7u8uxwIDpO" alt="" data-size="original"></td><td></td><td></td></tr><tr><td><img src="/files/YLOPOR8SBSBb3uiTAb3p" alt="" data-size="original"></td><td></td><td></td></tr></tbody></table>


---

# 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://i4trust.ishare.eu/open-call-1/dare.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.