Skip to content

http://graph.build/ontology/

This is where the vocabulary lives

When you create an ontology in Studio, classes and properties are minted under this namespace unless you change it. If you followed a term such as Person, you are in the right place. That address has to resolve to something a person can read, and this page is what it resolves to.

The resource namespace Ontologies explained

Why this address exists

A term IRI is not a missing page

RDF gives every class and every property a URL. Tools, partners and people will open it. Most of those URLs were never meant to be a website; they are identifiers. This page is the human-readable end of ours.

the namespace

Classes and properties, not records

http://graph.build/ontology/ is the default prefix for the vocabulary you define in Studio. Person, worksFor, Organisation — the types and the relationships — are concatenated onto it, which is why http://graph.build/ontology/Person landed you here. The definition of Person lives in the ontology that minted it, in your own Studio project. This site cannot show that definition, because it is yours. What it can do is explain the namespace, and point you at how ontologies work.

The consequence: an identifier you can publish, and a page that does not 404 when somebody follows it.

gbo: vocabulary

gbo: vocabulary

Person class

Organisation class

worksFor property

name property

minted under http://graph.build/ontology/

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.

http://graph.build/ontology/

The vocabulary. Classes, properties and the relationships between them. A slash namespace: each term is a path of its own, which is why following one brings you here.

holds the types

http://graph.build/resource#

The instances. A specific person, a specific asset. A hash namespace: everything after the hash stays in the browser, so every such address already resolves to one page.

go to the resource namespace

Ontologies in short

A shared vocabulary, written down so a machine can use it

The longer version is the fundamentals guide. The three facts that matter for this namespace are these.

What an ontology is

A formally defined set of classes and properties for a domain. Not a database schema, which says a column is a varchar. A definition of what things are, how they relate, and which rules hold.

read ontologies explained

Why it needs a namespace

Two teams will both invent a Person. A namespace says whose Person you mean, and lets a standard vocabulary sit next to yours without a name collision. Studio's default is this one; you can point it at your own.

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, versioned with the ontology. Change it in the project before you publish, not after other systems have cited the old one.

in Studio

Next

See how the vocabulary is built

Studio is where the classes and properties are designed. Forty-five minutes on your own domain is the shortest way to see a namespace fill up with terms that are actually yours.

Book a demo See Studio
  • RDF and property graphs on one canvas
  • Your namespace, or this default
  • No obligation to buy anything