http://graph.build/resource#
The instances. A specific person, a specific asset. A hash namespace: everything after the hash stays in the browser, so this one page is already the destination.
http://graph.build/resource#
This is where the things themselves live
When you create an ontology in Studio, instances — a specific person, a specific asset — are minted under this namespace unless you change it. The hash is deliberate. Everything after it stays in the browser, so every such address already resolves to this page.
Why the hash
The identifier never leaves the address bar
A hash URI is one document with many names inside it. The browser asks for /resource and keeps the rest locally. That is why there is one page here rather than one page per record, and why following a specific instance still lands you in the right place.
the namespace
Records, not the types they belong to
http://graph.build/resource# is the default prefix for the things the vocabulary describes. person-1842, org-acme, asset-77 — the instances — are appended after the hash. The type of those things, Person or Organisation, lives under http://graph.build/ontology/. Splitting them is ordinary RDF practice: the schema can be published, versioned and reused without carrying every record with it, and the records can grow without rewriting the schema.
The consequence: a graph you can show someone, and a vocabulary they can adopt, without handing them the contents of the database.
resource#
instances
resource# instances
person-1842 a Person
org-acme an Organisation
asset-77 an Asset
contract-9 a Contract
minted under http://graph.build/resource#
The pair
Two namespaces, because types and things are different
Studio ships two defaults. One is for what things mean. The other is for the things themselves. Mixing them is how a graph becomes impossible to reuse.
Ontologies in short
The vocabulary names the types. This namespace holds the members.
The longer version is the fundamentals guide. The three facts that matter for this namespace are these.
What an instance is
A particular thing the ontology can talk about. Person is a class; person-1842 is one person. The class is reused. The instance is not. That distinction is the whole reason there are two namespaces.
read ontologies explained
Why it needs its own namespace
If instances shared the vocabulary namespace, a record named Person would collide with the class Person. Keeping them apart means a term always means the same kind of thing, which is what lets an outside tool read the graph without a glossary.
see vocabularies in Studio
You can change it
The default is a starting point, not a lock-in. If the graph is yours, the namespace should be too — a domain you control. Change it in the project before other systems start citing the identifiers, because those citations do not update themselves.
in Studio
Next
See how the instances get there
Studio holds the types. Transformers mint the records from the systems you already run, under this namespace or under one you set. Forty-five minutes on your own data is the shortest way to see both fill in.
- Mapped from sources you already have
- Your namespace, or this default
- No obligation to buy anything