§1 — The 6-State Lifecycle
Every plm:OntologyProduct instance transitions through well-defined states.
Illegal transitions are blocked at the RDF level.
no constraints enforced
peer validation
approved · live
still queryable
sealed forever
Rejection loop: IN_REVIEW → REJECTED → DRAFT
§2 — State Transitions
Each trigger is a plm:StateTransition instance in the knowledge graph —
machine-enforceable, SPARQL-queryable.
§3 — Governance Rules
Three SPARQL-enforced constraints protect every ontology product from governance failures.
Four-Eyes Principle
The ontology owner (plm:hasOwner) cannot be their own validator. The SHACL constraint
plm:FourEyesConstraintShape blocks self-approval at query time.
Quorum Approval
APPROVED status requires all assigned validators to have an APPROVED
plm:ValidationRecord. A single REJECTED vote triggers immediate rejection.
Temporal Sealing
ARCHIVED products must carry a plm:deprecatedAt timestamp.
The SHACL shape plm:ArchivedRequiresDeprecatedAtShape enforces this immutably.
Change Events
Every state transition generates an immutable plm:ChangeEvent in Jena Fuseki — who,
when, from which state, to which state, and why. Full sovereign audit trail.
SHACL Shapes
8 property constraints on plm:OntologyProductShape: ontologyId, namedGraph,
SemVer version pattern, closed-set lifecycleState, owner cardinality exactly-1, and more.
OLM Maturity Levels
FULL — complete contract, quorum validation, aligned to standards. PARTIAL — contract defined, validation incomplete. NONE — bootstrap product, governance not yet applied.
§4 — The OntologyContract
An plm:OntologyContract is a single executable Turtle document bundling
five sections into one machine-verifiable artefact.
§1 Metadata
contractId, namespace URI, approval gate (e.g. "ArcaQ_Architecture_Board"), status (active / draft / archived), SemVer version, provenance dates.
§2 Semantics T-Box
Fingerprint of all class + property URIs the contract covers. OWL axioms (disjointWith, TransitiveProperty, IrreflexiveProperty) embedded inline.
§3 Validation SHACL
Property shapes, cardinality rules, controlled vocabulary constraints, and SPARQL-based cross-instance constraints — all embedded in the contract TTL.
§4 Versioning Policy
Three modes: IMMUTABLE_INSTANCES, VERSIONED_SNAPSHOT, MUTABLE_WITH_AUDIT. Immutability rules seal specific properties with optional SPARQL pre-conditions.
§5 Interoperability
Standard alignments (DAMA-DMBOK, ISO-27001, GDPR-Art5, W3C-PROV, W3C-DCAT) with
plm:mappingConfidence 0–1 scores + gateway definitions (SPARQL, RML, SHACL).
Export Formats
Every contract can be exported from the ArcaQ dashboard as Turtle (.ttl), JSON-LD (.jsonld), or YAML (.yaml) — no tooling required.
§5 — Standard Alignments in arcaq-core
The reference contract arcaq-core-contract declares alignment confidence
for 5 industry standards.
§6 — 82 Ontologies · One Registry
ArcaQ's OLM registry tracks all 82 domain ontologies — from core governance to industry verticals, Moroccan legal frameworks, world religions, and geo-political regions.
🏗️ Core (8)
arcaq-core, governance, provenance, bitemporal, cultural, temporal-neurosymbolic, OLM schema, SHACL
🏭 Industries (22)
aerospace, agriculture, artisanat, automotive, construction, defense, education, energy, finance, food, healthcare…
⚖️ Moroccan Legal (20)
administrative, banking, civil, commercial, criminal, digital, family, fiscal, land, notarial, social, competition…
🫂 Moroccan Social (13)
health, education, housing, employment, youth, family_solidarity, disability, migration…
🕊️ Ethos (9)
bahai, buddhism, christianity, hinduism, islam, jainism, judaism, secular_ethics, sikhism
🌍 Regions (7)
africa, americas, asia, eu, gcc, luxembourg, mena
Manage Your Ontologies as Products
The ArcaQ OLM dashboard provides a full lifecycle view of all 82 ontologies, with one-click submit, approve, reject, deprecate, and export to Turtle / JSON-LD / YAML.