Lay out the document hierarchy that will hold your data

Documents come in two kinds: containers, which hold child documents, and\n items. Northwind's domain gives you the container layout directly — one container per entity type\n (order line items live inside their order documents):

https://localhost:4443/\n├── categories/\n├── customers/\n├── employees/\n├── orders/\n├── products/\n├── regions/\n├── shippers/\n├── suppliers/\n└── territories/

\n \n \n

On the root document, click the Create dropdown and select Container. Enter Categories as the title, replace\n the generated relative URI with categories using the dropdown in the top-right corner of the form, and save. The\n Create documents guide walks through the form in detail.

A container is just a document whose description says it is one. categories.ttl:

@prefix dh:     <https://w3id.org/atomgraph/linkeddatahub/document-hierarchy#> .\n@prefix dct:    <http://purl.org/dc/terms/> .\n\n<> a dh:Container ;\n    dct:title \"Categories\" .

PUT it to the container URL, the same way the root document was updated:

ldh put \"${LDH_BASE}categories/\" categories.ttl

Repeat for the remaining eight containers — or skip to App as a repository, where one command replays a whole folder.

What you now see

The root document now lists the containers as its children, and each container URL resolves to an (empty) listing page. The URL space of your app is its information\n architecture.

\n $\"Root$ \n

How this works

Document hierarchy — how containers and items nest into the URL space

Next: Model