RA-005 · Research Report · 2026-05-16 · DOI 10.5281/zenodo.20185059

Semantic Web & Knowledge Representation

Cameisha Smith

The Inquiry

The Inquiry: The Semantic Web provides mature, standardized infrastructure for representing, reasoning over, and querying structured knowledge — OWL 2 (2012), RDF 1.1 (2014), PROV-O (2013), SKOS (2009), SPARQL (2013), OWL-Time (2017). Foundational ontologies (BFO, DOLCE, SUMO, GFO) have demonstrated that domain-independent upper ontologies can integrate hundreds of domain ontologies at scale (BFO: hundreds of biomedical ontologies, ISO/IEC 21838 standardization). Yet no existing ontology, knowledge graph architecture, or semantic framework addresses organizational decision governance — capturing why decisions were made, under what authority, with what evidence, subject to which constraints, and how decisions relate to the governance chain. Is this an oversight (solvable by applying existing standards) or a genuine application gap requiring novel ontological contribution?

Falsifiable formulation: If any existing ontology, knowledge graph, or semantic framework provides the formal infrastructure to capture, reason over, and validate organizational decision governance — including authority traceability, evidence provenance, constraint compliance, and temporal validity — then the application gap claimed here does not exist.

Executive Summary

The Semantic Web has solved the technical infrastructure problem; organizational decision governance is the unsolved application.

Three decades of W3C standardization, description logic research, and foundational ontology work have produced remarkably mature infrastructure. OWL 2 provides decidable reasoning with computational guarantees. RDF provides a universal data model. PROV-O provides provenance tracking. SKOS provides vocabulary management. SPARQL provides query infrastructure. BFO demonstrates that upper ontologies can integrate hundreds of domain ontologies at scale (through OBO Foundry). Description logic research has fully characterized the tractability-expressiveness trade-off. Ontology engineering methodologies (METHONTOLOGY, NeOn, competency questions, design patterns) provide validated construction approaches.

The application gap is specific: no existing ontology captures the semantics of organizational decision governance. Enterprise knowledge graphs model entities for query and discovery. PROV-O tracks provenance. Business process ontologies capture workflows. But none captures why a decision was made, under what authority, with what evidence, subject to which constraints, and how it relates to the governance chain. This gap persists not because the technical infrastructure is insufficient but because the domain has been modeled procedurally (BPM, workflow systems) rather than ontologically (formal KR with decidable reasoning).

![Figure 1. Six W3C standards provide mature knowledge infrastructure. No equivalent exists for organizational decision governance.](images/rr-005-fig-01.png)

Knowledge representation is not neutral — it constitutes a theory of governance.

Davis, Shrobe & Szolovits's (1993) five-role framework reveals that a governance ontology is not merely a data format but a theory of what governance means. The choice of primitives determines what the system can "see" (ontological commitments). The sanctioned inferences define what counts as valid governance reasoning. The computational profile determines what governance questions can be answered in bounded time. The human expression requirement ensures that governance conclusions remain interpretable. Gruber's (1993) ontological commitment concept adds: adopting a governance ontology is a social contract — organizations agree to represent governance using shared vocabulary, enabling interoperability not through data format conversion but through shared conceptualization.

![Figure 2. Davis et al.'s five roles reveal that governance representation choices constitute a theory of governance, not merely a data format.](images/rr-005-fig-02.png)

The passive-to-active transition: from knowledge graph to governance substrate.

Enterprise knowledge graphs and Graph RAG represent the current state of the art in organizational knowledge infrastructure — but they are passive. They represent what is, not what should be. They answer "what happened?" not "was it authorized?" The transition from passive knowledge graph to active governance substrate — where the ontology doesn't just describe governance but constrains, validates, and enables reasoning over governance actions — represents the novel application of mature semantic web infrastructure to an underserved domain.

![Figure 3. The transition from descriptive to normative infrastructure applies mature semantic web technology to an underserved organizational domain.](images/rr-005-fig-03.png)

Abstract

The Semantic Web ecosystem — OWL 2, RDF, PROV-O, SKOS, SPARQL, OWL-Time — provides technically mature infrastructure for representing, reasoning over, and querying structured knowledge. Foundational ontologies, led by BFO's integration of hundreds of biomedical ontologies and ISO/IEC 21838 standardization, demonstrate that domain-independent upper categories can anchor entire disciplinary ecosystems. Description logic research has fully characterized the tractability-expressiveness trade-off, establishing proven computational guarantees for governance-relevant query classes. Yet no existing ontology, knowledge graph, or semantic framework captures organizational decision governance — why decisions were made, under what authority, with what evidence, subject to which constraints. Knowledge representation theory reveals this is not merely a technical gap: Davis, Shrobe & Szolovits (1993) establish that representation choices constitute a theory of the domain, and Gruber (1993) frames ontology adoption as ontological commitment — a social contract about shared conceptualization. The transition from passive knowledge graph (what happened) to active governance substrate (was it authorized) applies mature infrastructure to an underserved domain.

"A knowledge representation is most fundamentally a surrogate, a substitute for the thing itself, used to enable an entity to determine the consequences of action by thinking rather than acting." — Davis, Shrobe & Szolovits (1993), AI Magazine
Findings14
F-RA-005-01 · structural-mapping · lab-originated
OWL 2 (W3C Recommendation, 2012) provides decidable reasoning infrastructure based on the description logic SROIQ(D), with three profiles trading expressiveness for tractability — OWL 2 EL (polynomial classification for large ontologies, basis for SNOMED CT's extensive clinical terminology), OWL 2 QL (database-speed conjunctive query answering through first-order rewriting), OWL 2 RL (rule-based forward chaining for business logic) — plus governance-relevant constructs (property chain axioms for authority delegation `R₁ ∘ R₂ ⊑ R₃`, HasKey for decision identity, qualified cardinality restrictions for structural constraints, dual Direct/RDF-Based semantics).
F-RA-005-02 · structural-mapping · lab-originated
RDF 1.1's triple model (subject-predicate-object) and Named Graphs (triple collections identified by an IRI) provide a more flexible data architecture than relational tables for governance relationships — enabling grouping by source, graph-level provenance tracking, trust-by-graph-association, and versioning by new-graph creation (preserving originals); JSON-LD serialization enables semantic governance data consumption via standard JSON APIs without full RDF stack adoption — a critical enterprise-adoption consideration.
F-RA-005-03 · gap-identification · lab-originated
PROV-O (W3C, 2013) captures "who did what, when, why, and how" through six core properties (wasGeneratedBy, wasDerivedFrom, wasAttributedTo, wasAssociatedWith, actedOnBehalfOf, used) plus Bundles for recursive provenance, with PROV-CONSTRAINTS for temporal ordering/lifecycle validation; actedOnBehalfOf directly models authority delegation chains. But PROV-O provides tracking without governing — it answers "where did this come from?" not "was this properly authorized, adequately evidenced, and consistent with constraints?"
F-RA-005-04 · structural-mapping · lab-originated
SKOS (W3C, 2009) represents knowledge organization systems (thesauri, taxonomies, controlled vocabularies) as linked data, with concept-centric design (skos:Concept/ConceptScheme/Collection), hierarchical/associative relations (broader/narrower/related), cross-scheme mapping (exactMatch/closeMatch/broadMatch), multilingual labeling (prefLabel/altLabel), and documentation properties (definition/scopeNote/historyNote); design principles include minimal ontological commitment (concepts are not classes), no strict transitivity, and open-world assumption (Isaac et al. 2013).
F-RA-005-05 · architectural-framing · lab-originated
Gruber (1993; see also Gruber 1995) defined ontology as "explicit specification of a conceptualization" and gave five design criteria (clarity, coherence, extendibility, minimal encoding bias, minimal ontological commitment); the "ontological commitment" concept frames ontologies as social contracts about terminology — adopting one means committing to shared conceptualization, not asserting the world matches the model.
F-RA-005-06 · architectural-framing · lab-originated
Davis, Shrobe & Szolovits (1993) argued KR simultaneously serves five roles: (1) surrogate, (2) set of ontological commitments, (3) theory of intelligent reasoning, (4) medium for efficient computation, (5) medium for human expression — each with a governance implication (omission as governance choice, primitive choice determines what is "seen," sanctioned inferences define valid governance reasoning, tractability bounds query time, comprehensibility enables accountability).
F-RA-005-07 · gap-identification · lab-originated
Foundational upper ontologies (BFO — Arp/Smith/Spear 2015, ISO/IEC 21838-2:2021; DOLCE — Masolo et al. 2003; SUMO — Niles & Pease 2001; GFO — Herre 2010) demonstrate that domain-independent upper categories integrate hundreds of domain ontologies at scale (BFO anchors hundreds of biomedical ontologies via OBO Foundry, achieved ISO standardization, frames the Industrial Ontology Foundry and Common Core Ontology). SUMO is among the largest formal upper ontologies with deontic categories (Obligation, Permission, Prohibition); GFO distinguishes material/mental/social levels (governance structures as real social objects). But no comparable instantiation exists for organizational decision governance — the domain is modeled procedurally (workflow/BPM), never ontologically.
F-RA-005-08 · structural-mapping · lab-originated
OntoClean (Guarino & Welty 2002) introduced four meta-properties for evaluating ontological choices — rigidity (+R: every instance necessarily has the property), identity (+I: provides individuation criteria), unity (+U: a common unifying relation binds parts), dependence (+D: instances require other individuals) — with validation rules (anti-rigid cannot subsume rigid; identity carries to all subclasses; non-unity cannot subsume unity).
F-RA-005-09 · design-requirement-derivation · lab-originated
Description-logic research (Baader et al. 2003; W3C OWL 2, 2012) establishes the tractability-expressiveness trade-off: the DL family ranges from ALC (EXPTIME-complete) through SHIQ/SHOIQ to SROIQ(D) underlying OWL 2 DL (2-NEXPTIME); DL-Lite (OWL 2 QL) achieves AC₀ conjunctive query answering (≈ SQL evaluation); EL++ (OWL 2 EL) achieves polynomial classification.
F-RA-005-10 · structural-mapping · lab-originated
Allen's Interval Algebra (Allen 1983) provides 13 mutually exclusive temporal relations between intervals (before/after/meets/overlaps/starts/during/finishes + inverses + equals) with a composition table for constraint propagation; combined with W3C OWL-Time (2017) formal temporal concepts (Instant, Interval, Duration).
F-RA-005-11 · structural-mapping · lab-originated
Ontology-engineering methodologies and design patterns provide validated construction approaches: Noy & McGuinness (2001) seven-step methodology with competency questions; METHONTOLOGY (Fernández-López et al. 1997) lifecycle; NeOn (Suárez-Figueroa et al. 2012) nine networked-engineering scenarios; Gangemi (2005) Ontology Design Patterns including the Situation pattern and Description & Situation; plus the N-ary Relation pattern (W3C SWBPD, 2006) and Provenance patterns (broader ODP community).
F-RA-005-12 · structural-mapping · lab-originated
Linked Data principles (Berners-Lee 2006 — URIs as names, HTTP URIs for lookup, standards-based information, links for discovery; 5-star deployment scheme) and ontology alignment (Euzenat & Shvaiko 2013 — equivalence/subsumption/disjointness/overlap via string-, structure-, instance-, semantic-, and background-knowledge techniques) provide the interoperability foundation.
F-RA-005-13 · gap-identification · lab-originated
Enterprise knowledge graphs implement a three-layer architecture (storage = graph databases; semantic layer = ontologies + reasoning; consumption = applications + AI); Graph RAG (2024-2025) grounds LLM retrieval in KG structure (reduced hallucination, explainable paths, multi-hop reasoning, consistent entity references); the OMG Enterprise Knowledge Graph Task Force (est. 2023) signals mainstream enterprise recognition. But enterprise KGs are passive — they represent what is, not what should be; they answer "what happened?" not "was what happened authorized?"
F-RA-005-17 · convergent-validation · lab-originated
Sprint S5 (semantic-web technical foundation) makes the governance arguments of sprints S1–S4/S6 formally representable: PROV-O + RDF Named Graphs underpin S1 (decision lineage); OWL class hierarchies with constraint axioms formalize S4 (accountability frameworks COSO/COBIT/Three Lines); knowledge-graph storage patterns map S3 (organizational memory, Walsh & Ungson; Star & Ruhleder); OWL 2 QL / SPARQL / Allen+OWL-Time underpin S6 (audit query and authority-validity reasoning).
Open Questions2
OQ-014How does W3C SHACL extend OWL 2 for governance constraint validation?
OQ-015Has any ontology for organizational governance been published since the existing sprint?
Bibliography29
{W3C} (2012) · OWL 2 Web Ontology Language Document Overview
{W3C} (2014) · RDF 1.1 Concepts and Abstract Syntax
{W3C} (2013) · PROV-O: The PROV Ontology
{W3C} (2009) · SKOS Simple Knowledge Organization System Reference
{W3C} (2017) · Time Ontology in OWL
{W3C} (2013) · SPARQL 1.1 Query Language
{Dublin Core Metadata Initiative} (2020) · DCMI Metadata Terms
Gruber, Thomas R. (1993) · A Translation Approach to Portable Ontology Specifications
Davis, Randall and Shrobe, Howard and Szolovits, Peter (1993) · What is a Knowledge Representation?
Studer, Rudi and Benjamins, V. Richard and Fensel, Dieter (1998) · Knowledge Engineering: Principles and Methods
Allen, James F. (1983) · Maintaining Knowledge about Temporal Intervals
Arp, Robert and Smith, Barry and Spear, Andrew D. (2015) · Building Ontologies with Basic Formal Ontology
+17 more citations