# Structured Data

## Structured Data: Things, SolidDataset, and Containers

Structured data in this system uses the [Resource Description Framework (RDF)](https://www.w3.org/TR/rdf11-concepts/) format. Data is around entities called [Things](/reference/glossary.md#thing). A Thing represents any object or concept you want to store information about. For example, if you're storing course information, you might create a Thing for a textbook, with properties like `title` and `author`. The `author` could be another Thing with its own properties.

Things don't exist independently; they must be part of a [SolidDataset](/reference/glossary.md#soliddataset). A SolidDataset is a collection that holds multiple related Things together.

You can organize SolidDatasets using [Containers](/reference/glossary.md#container), which work like folders in a file system. Containers can hold SolidDatasets and other resources, including additional Containers nested inside them.

To continue with the course example, your Wallet Storage could have a `Container` named `fall2021/`; `fall2021/` contains another `Container` named `courses/`; `courses/` contains a `SolidDataset` that corresponds to the course `Writing101`; and the `Writing101` contains data about the `Things` (such as the books) for that course.

<figure><img src="/files/HiGbjnKJORTneGqjghLI" alt=""><figcaption></figcaption></figure>

### URL as Identifiers

Every Container, SolidDataset, and Thing has a unique URL that serves as its identifier.

* Container URLs always ends with a forward slash ( `/` ). This slash indicates that the URL points to a Container rather than a specific file (Thing) or dataset (SolidDataset).
* SolidDataset URLs are built from their location within the container hierarchy, followed by the SolidDataset's name.
* Thing URLs are also built from their location within the container hierarchy, followed by the SolidDataset they belong to, with a hash fragment (`#`) added before the name of the Thing itself.

Consider the following content in a Pod where the Pod URL is `https://storage.inrupt.com/{rootContainer}/`:

<figure><img src="/files/HiGbjnKJORTneGqjghLI" alt=""><figcaption></figcaption></figure>

<table><thead><tr><th width="151.5">Name</th><th width="133">Type</th><th>URL</th></tr></thead><tbody><tr><td><code>fall2021/</code></td><td>Container</td><td><code>https://storage.inrupt.com/{rootContainer}/fall2021/</code></td></tr><tr><td><code>courses/</code></td><td>Container</td><td><code>https://storage.inrupt.com/{rootContainer}/fall2021/courses/</code></td></tr><tr><td><code>Writing101</code></td><td>SolidDataset</td><td><code>https://storage.inrupt.com/{rootContainer}/fall2021/courses/Writing101</code></td></tr><tr><td><code>book1</code></td><td>Thing</td><td><code>https://storage.inrupt.com/{rootContainer}/fall2021/courses/Writing101#book1</code></td></tr><tr><td><code>book2</code></td><td>Thing</td><td><code>https://storage.inrupt.com/{rootContainer}/fall2021/courses/Writing101#book2</code></td></tr><tr><td><code>otherThing</code></td><td>Thing</td><td><code>https://storage.inrupt.com/{rootContainer}/fall2021/courses/Writing101#otherThing</code></td></tr></tbody></table>


---

# Agent Instructions: 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:

```
GET https://docs.inrupt.com/reference/rdf/structured-data-rdf-resources.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.