Types of Knowledge Systems: A Comprehensive Taxonomy

Knowledge systems span a wide range of architectures, from rule-based expert systems developed in the 1970s to modern knowledge graphs used by major technology platforms. This page maps the principal categories within that landscape, defines their structural boundaries, and identifies the professional and regulatory contexts in which each type operates. Distinguishing between system types is consequential: misclassification can lead to misapplied governance frameworks, inadequate validation protocols, and downstream failures in high-stakes domains such as healthcare and financial services.


Definition and scope

A knowledge system is a computational or organizational structure designed to capture, represent, store, retrieve, and apply knowledge to support decision-making, inference, or information access. The World Wide Web Consortium (W3C) distinguishes knowledge representation standards — including OWL (Web Ontology Language) and RDF (Resource Description Framework) — as formal instruments for encoding the semantics of a knowledge domain, providing one axis for classifying system types.

The taxonomy of knowledge systems is typically organized along three primary axes:

  1. Representation format — how knowledge is encoded (logical rules, graph structures, vectors, natural language)
  2. Inference mechanism — how the system derives new knowledge from existing facts (deductive, inductive, abductive)
  3. Knowledge origin — whether knowledge is explicitly authored by domain experts or learned from data

The knowledge representation methods available to system designers determine which downstream applications are feasible, making type identification a prerequisite for knowledge system architecture decisions.


How it works

Each major category of knowledge system operates through a distinct structural mechanism:

Rule-Based Systems

Rule-based systems encode knowledge as condition-action pairs (IF-THEN rules). An inference engine traverses the rule set using forward chaining (data-driven) or backward chaining (goal-driven) to reach conclusions. MYCIN, developed at Stanford University in the 1970s, remains the canonical historical example — a medical diagnosis system containing approximately 600 rules for identifying bacterial infections.

Semantic Networks

Semantic networks represent knowledge as directed graphs of nodes (concepts) and labeled edges (relationships). Inheritance hierarchies allow properties to propagate from parent to child nodes, enabling compact representation of large concept spaces. The W3C's RDF specification formalizes this structure for web-scale deployment.

Knowledge Bases

A knowledge base is a structured repository combining a fact store with mechanisms for retrieval and, in many implementations, inference. Enterprise knowledge bases such as those used in IT service management are governed by frameworks including the Information Technology Infrastructure Library (ITIL), published by AXELOS.

Ontologies and Taxonomies

Knowledge ontologies and taxonomies define the formal vocabulary and relationship structure of a domain. The Web Ontology Language (OWL 2), standardized by W3C, supports description logic reasoning over ontological assertions. Taxonomies impose a strictly hierarchical (IS-A) structure, while ontologies permit richer relation types including part-of, causes, and equivalent-to.

Knowledge Graphs

Knowledge graphs integrate large-scale entity data with semantic relationships and support multi-hop inference. Google's Knowledge Graph, launched in 2012, indexed over 500 million entities at launch, illustrating the scale achievable with this architecture. Knowledge graphs typically conform to linked data principles and are queryable via SPARQL, the W3C-standardized graph query language.

Machine Learning–Based Knowledge Systems

Systems in this category derive knowledge representations implicitly from training data. Refer to knowledge systems and machine learning for structural detail. These systems lack explicit, inspectable rule sets, which creates distinct challenges for knowledge validation and verification under regulatory frameworks such as FDA guidance on Software as a Medical Device (SaMD).


Common scenarios

The following scenarios illustrate where specific system types are deployed across regulated industries:


Decision boundaries

The choice between knowledge system types is governed by four criteria that define hard classification boundaries:

Criterion Rule-Based / Ontological Graph-Based ML-Based
Explainability requirement High — rules are auditable Medium — traversal paths visible Low — weights are opaque
Knowledge stability Static or slow-change domains Semi-dynamic Rapidly evolving data
Regulatory auditability Straightforward Moderate Complex; requires additional tooling
Scale of entity data Hundreds to thousands of rules Millions of entities Billions of data points

The explicit vs. tacit knowledge distinction cuts across all types: explicit knowledge is amenable to rule-based and ontological encoding, while tacit knowledge — procedural or experiential — resists formalization and typically requires machine learning approaches or knowledge acquisition through structured elicitation.

Knowledge system governance frameworks, including those based on ISO/IEC 25012 (Data Quality) and NIST's AI Risk Management Framework (AI RMF 1.0), apply differentially depending on system type. Rule-based systems satisfy auditability requirements more readily than ML-based systems, a distinction that shapes deployment decisions in regulated environments. The full scope of the knowledge systems landscape is indexed at the Knowledge Systems Authority.


References