> For the complete documentation index, see [llms.txt](https://standards.spdci.org/standards/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://standards.spdci.org/standards/standards-for-interoperability-interfaces/common-standards-for-interoperability-interfaces/data/file-type-json-ld.md).

# File Type: JSON-LD

Central to the data standards is the use of [JSON-LD](https://json-ld.org/spec/latest/) (JavaScript Object Notation for Linked Data) as the data format of choice. JSON-LD is a lightweight, flexible, and web-friendly format designed to facilitate data interoperability among diverse systems. It extends the traditional JSON format by introducing the ability to contextualise data through linking, making it a compelling choice for representing and exchanging structured data in a decentralised environment like for DPI.

The use of JSON-LD promotes a semantic understanding of the data, ensuring that the exchanged information is not only machine-readable, but also meaningful and interpretable across different systems and stakeholders.

Find out more on the JSON-LD website:

{% embed url="<https://json-ld.org/>" %}


---

# 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://standards.spdci.org/standards/standards-for-interoperability-interfaces/common-standards-for-interoperability-interfaces/data/file-type-json-ld.md?ask=<question>&goal=<user_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.