OpenRiC Extension Ontology v1

Namespace IRI: https://openric.org/ns/ext/v1# Preferred prefix: openricx Status: Active (v0.37.0) · Issued: 2026-04-25 · Licence: CC-BY 4.0 Machine-readable ontology: v1.ttl (Turtle) Catalyst: RiC-O 1.1 conformance audit, April 2026.

Purpose

OpenRiC commits never to mint new terms in the ICA RiC-O namespace. This extension namespace holds 48 terms that OpenRiC implementations need but RiC-O 1.1 does not define. They fall into three categories:

1. Response-envelope classes for paginated JSON-LD list endpoints (e.g. openricx:RecordList, openricx:AgentList). These are protocol concerns, not archival semantics, and would not normally be upstream candidates.
2. Pragmatic API shortcuts that have a clean canonical RDF expansion in RiC-O 1.1 (e.g. openricx:hasOccupation → SKOS Concept of rico:OccupationType; openricx:DateRange → native RiC-O Date pattern). These are kept for API ergonomics.
3. Candidate upstream proposals for ICA-EGAD — terms with genuine archival semantics that RiC-O 1.1 does not yet model (e.g. openricx:ContactPoint, openricx:hasAppraisalInformation, openricx:containsPersonalData).

The full per-term disposition with confidence flags is in the audit document.

Classes

Response-envelope (8)

Semantic extension (5)

Properties (35)

Grouped by purpose. Full domain/range and rdfs:comment for each is in the Turtle ontology.

Address & contact (7)

openricx:contact, openricx:streetAddress, openricx:city, openricx:postalCode, openricx:country, openricx:telephone, openricx:email

Date ranges (2)

openricx:hasDateRange, openricx:hasDateRangeSet

Description / notes (5)

openricx:description, openricx:descriptiveNote, openricx:generalContext, openricx:arrangement, openricx:publicationInformation

Internal structure / policy (2)

openricx:hasInternalStructure, openricx:hasOrHadPolicy

Geographical context (3)

openricx:hasBroaderGeographicalContext, openricx:hasNarrowerGeographicalContext, openricx:jurisdiction

Names / labels (4)

openricx:alternativeForm, openricx:normalizedForm, openricx:otherName, openricx:languageCode

Privacy & appraisal (2)

openricx:containsPersonalData, openricx:hasAppraisalInformation

Occupation (1)

openricx:hasOccupation

Format / carrier / size (5)

openricx:hasMimeType, openricx:mimeType, openricx:size, openricx:hasPhysicalCharacteristics, openricx:technicalCharacteristics, openricx:productionTechnicalCharacteristics

Checksum (3)

openricx:hasChecksum, openricx:algorithm, openricx:checksumValue

Versioning policy

• The /v1# namespace path is stable. Breaking changes (term removed, semantics changed, domain/range narrowed) MUST happen at /v2#.
• Additive changes (new classes, new properties, expanded domain/range, looser constraints) MAY land within /v1# and bump the owl:versionInfo minor or patch number.
• Every term in /v1# is versioned through OpenRiC’s CHANGELOG and audit doc.
• Implementations MAY pin a specific version (e.g. https://openric.org/ns/ext/v1.1.0#) when they need exact stability, but the unversioned /v1# namespace is the recommended default.

Upstream proposal status

OpenRiC tracks open upstream-proposal candidates against ICA-EGAD/RiC-O GitHub issues. Current candidates (April 2026):

• openricx:ContactPoint + address fields → propose rico:ContactPoint class.
• openricx:hasAppraisalInformation → propose rico:hasAppraisalInformation (ISAD(G) 3.3.2 backing).
• openricx:containsPersonalData → propose rico:containsPersonalData (privacy-compliance flag).

The rest are pragmatic API surface and are not expected to migrate upstream.

See also

• OpenRiC mapping spec — the canonical use of each term in context
• RiC-O 1.1 conformance audit — per-term disposition table with audit history
• Turtle ontology — machine-readable form