Part of specification v0.46.0. Earlier versions are preserved as tagged releases.
OpenRiC API Vocabulary v1
Namespace IRI: https://openric.org/ns/v1#
Preferred prefix: openric
Issued: 2026-10-15 · Licence: CC-BY 4.0
Machine-readable vocabulary: v1.ttl (Turtle)
Purpose
OpenRiC uses two namespaces of its own, and neither is part of Records in Contexts:
openric:(this page) is for the API itself: how lists are paged, how a server describes itself, how errors are reported, how a viewer is given a subgraph, plus three annotations the profiles put on entities.openricx:, the extension ontology, is for archival meaning that RiC-O 1.1 does not yet model.
Every term below was already used by the profiles, schemas, fixtures and the reference service before this page was published on 2026-10-15; the namespace had been bound in responses without a vocabulary behind it (mapping O-6). Publishing it changed no response. CI now fails if a schema or fixture uses an openric: or openricx: term that neither vocabulary defines.
Entity annotations
| Term | Used on | Meaning |
|---|---|---|
openric:localType |
Places, rules, activities, functions, things | The implementation’s own subtype (country, law, production, box), next to the canonical rico: type. It never replaces a rico: type. |
openric:jurisdiction |
Rules | Free-text jurisdiction (Egypt). Where the jurisdiction is a known place, rico:hasOrHadJurisdiction to a rico:Place is preferred. |
openric:role |
Corporate bodies | Viewer convenience, e.g. repository for an ISDIAH institution. |
API terms
| Group | Terms | Defined by |
|---|---|---|
| List envelopes | openric:items, openric:total, openric:limit, openric:page, openric:next, openric:prev |
Core Discovery §3.3 |
| Vocabulary | openric:Vocabulary (emitted as ric:Vocabulary) |
Core Discovery §3.2 |
| Revision lists | openric:RevisionList |
Round-Trip Editing |
| Service description | openric:Service, openric:version, openric:implementation, openric:conformance, openric:endpoints |
Core Discovery §3.1 |
| Errors | openric:Error, openric:status, openric:code, openric:message, openric:detail |
Core Discovery §4 |
| Graph primitives | openric:Subgraph, openric:root, openric:depth, openric:nodes, openric:edges, openric:clusters, openric:hints, openric:layoutHint |
Graph Primitives |
The ric: alias in list envelopes
The record, agent, function and repository lists have always used ric:total, ric:page, ric:limit and ric:items, and GET /vocabulary has always been typed ric:Vocabulary; clients read those names. Those responses’ @context now binds ric to this namespace, so ric:items means openric:items. The other lists use openric: directly. ric here is an alias, not RiC-O, whose prefix is rico. It is deprecated: new servers SHOULD use openric:, and the alias will not be removed before the list keys are unified across all lists (Core Discovery §3.3, open).
Versioning
The /v1# path is stable. Terms are added within v1 and never removed from it; a term that is replaced is marked owl:deprecated with dcterms:isReplacedBy, as change control requires.