Core Domain Ontology (CDO) is a semantic model developed to support the Informatics Domain Model IDM. The CDO is structured around five central nodes: objects, events, concepts, actions, and domain, which underpin various aspects of planning, reasoning, and execution in digital systems. It enables decentralized data representation, transformation, and alignment.
Copyright @ 2026 Paul Knowles, Bart Gajderowicz, Keith Dugas
relates a Domain to a Concept, indicating that a Domain is accessed by a Concept.
relates an Event to a Goal, indicating that an Event defines a Goal.
relates a Receipt to a Packet, inverse of acknowledges indicating that a Receipt acknowledges a Packet.
relates a Statement to a Fact, indicating that a Statement affirms a Fact.
relates a Text to a Chart, indicating that a Text annotates a Chart.
relates an Event to a Reason, indicating that an Event is attributed to a Reason.
relates a Domain to an Object, indicating that a Domain is captured as an Object.
relates a Receipt to a Notice, inverse of isConfirmedBy indicating that a Receipt is confirmed by a Notice.
relates a Mechanism to a Scheme, indicating that a Mechanism constructs a Scheme.
relates a Object to a Concept, indicating that a Concept contexualizes an Object.
relates a Packet to a Payload, indicating that a Packet conveys a Method.
relates a Packet to a Method, indicating that a Packet declares a Method.
relates a Term to a Concept, indicating that a Term defines a Concept.
relates a Schema to a Form, indicating that a Schema defines layout for a Form.
relates a Packet to a Statement, indicating that a Packet delivers a Statement.
relates a Function to a Payload, indicating that a Function encapsulates a Payload.
relates a Payload to a State, indicating that a Payload encodes a State.
relates a Domain to an Event, indicating that a Domain is entered as an Event.
relates a Domain to an Action, indicating that a Domain is exchanged through an Action.
relates a Method to a Purpose, indicating that a Method fulfills a Purpose.
relates a Text to a Stemma, indicating that a Text grounds a Stemma.
relates a Purpose to a Reason, indicating that a Purpose guides a Reason.
relates a Packet to a Note, indicating that a Packet has metadata captured in a Note.
relates a Cause to an Action, indicating that an Cuase initiates an Action.
relates a Token to a Function, indicating that a Token invokes a Function.
relates a Packet to a Receipt, inverse of acknowleges, indicating that a Packet is acknowledged by a Receipt.
relates an Action to a Token, indicating that an Action is activated by a Token.
relates a Field to an Index, indicating that a Field is addressed by an Index.
relates a Chart to a Text, indicating that a Chart is annotated by a Text.
relates a Card to a Schema, indicating that a Card is bundled in a Schema.
relates a Payload to a Record, indicating that a Payload is captured by a Record.
relates a Record to a Log, indicating that a Record is committed to a Log.
relates a Notice to a Receipt, inverse of confirms, indicating that a Notice confirms a Receipt.
relates a Form to a Mechanism, indicating that a Form is consumed by a Mechanism.
relates a Concept to a Term, indicating that a Concept is defined by a Term.
relates a Log to a Stemma, indicating that a Log is derived by a Stemma.
relates an Object to an Attribute, indicating that an Object is described by an Attribute.
relates an Action to a Reason, indicating that an Action is driven by a Reason.
relates a Policy to a Note, indicating that a Policy is explained by a Note.
relates a Attribute to a Card, indicating that an Attribute is expressed by a Card.
relates a Parameter to a Frame, indicating that a Parameter is framed by a Frame.
relates an Object to a Cause, indicating that an Object is impacted by a Cause.
relates an Action to a Cause, indicating that an Action is initiated by a Cause.
relates an Action to a Method, indicating that an Action is an instantiation of a Method.
relates a Receipt to a Policy, indicating that a Receipt is issued under (according to) a Policy.
relates a Note to a Packet, indicating that a Note is the metadata for a Packet.
relates a Goal to a Concept, indicating that a Goal is oriented by a Concept to be defined.
relates a Payload to a Package, indicating that a Payload is packaged as a Package.
relates an Effect to a Mechanism, indicating that an Effect is realized through a Mechanism.
relates a Ledger to a Track, indicating that a Ledger is recorded as a Track.
relates a Term to a Parameter, indicating that a Term is refined by a Parameter.
relates an Index to a Record, indicating that an Index is registered by a Record.
relates a State to a Chart, indicating that a State is represented by a Chart.
relates a Concept to a Scheme, indicating that a Concept is scoped by a Scheme.
relates an Object to a Scheme, indicating that an Object is structured by a Scheme.
relates a Package to a Packet, indicating that a Package is transmitted as a Packet.
relates a Stemma to a Ledger, indicating that a Stemma is written to a Ledger.
The recorded process logs of the schema synthesization and transformation pipeline.
relates an Event to a Field, indicating that an Event occurs in a Field.
relates a Stemma to an Effect, indicating that a Stemma orders an Effect.
relates a Concept to a Goal, indicating that a Concept orients a Goal.
relates an Action to an Event, indicating that an Action produces an Event.
relates an Event to an Effect, indicating that an Event realizes an Effect.
relates a Form to a State, indicating that a Form represents a State.
relates a Concept to a Method, indicating that a Concept specifies a Method.
relates a Record to a Form, indicating that a Record stores a Form.
relates a Fact to a Purpose, indicating that a Fact supports a Purpose.
relates a Track to a Stemma, indicating that a Track traces a Stemma.
relates an Object to an Effect, indicating that an Object undergoes an Effect.
relates a Frame to a Notice, indicating that a Frame yields a Notice.
an intentional operation performed within a computational system that acts upon data to achieve a specific outcome, such as creation, transformation, transmission, or deletion.
data that is currently in use, being processed, or engaged in real-time operations within a computational system, often contributing to immediate functions, decisions, or interactions.
a defined unit of information within a data object that expresses a specific property, characteristic, or qualifier used to describe, differentiate, or structure the underlying entity.
the observable pattern of responses, interactions, or state changes exhibited by data within a computational system in reaction to specific inputs, conditions, or stimuli.
the central structural element within a data object that governs how its attributes are organized, interpreted, or processed within a given computational or semantic framework.
an identified factor or trigger within a computational system that initiates or gives rise to a data event, state change, or processing action, often captured for traceability or causal analysis.
a visual representation of structured data within a computational system, expressed through tables, graphs, or diagrams to reveal patterns, trends, or relationships for interpretation or analysis.
an abstract, structured idea within a computational system that provides semantic meaning or contextual framing to data, enabling consistent interpretation, classification, and interoperability across domains.
facts and statistics entered into a computational system, structured for reference, processing, or analysis within a defined informational context.
a resulting change or outcome within a computational system that occurs as a consequence of a specific data cause, action, or condition, often used to evaluate impact or derive meaning.
a recorded occurrence within a computational system that captures a change of state, action, or condition in time, often triggering processes or serving as a reference point in data trails.
a verified unit of information within a computational system that represents an objective truth or observed reality, serving as a foundational element for analysis, inference, or decision-making.
a designated element within a data structure that holds a specific value corresponding to a defined attribute, enabling organized storage, access, and retrieval of information in a computational system.
a particular configuration or expression of data shaped by its structure, type, or representation within a computational system, often determining how it is stored, displayed, or exchanged.
a semantic structure within a computational system that organizes and contextualizes data by linking attributes to concepts, enabling meaningful interpretation, interoperability, and knowledge representation.
a discrete, executable operation within a computational system that performs a defined task on data—such as computation, transformation, retrieval, or validation—to support a broader process or outcome.
a defined objective or desired outcome that guides the collection, processing, or analysis of data within a computational system, often shaping methodologies, metrics, or system behavior.
a structured containment layer that encapsulates one or more fields, defining local boundaries, validation logic, and schema constraints within a form or data model.
an ordered and immutable collection of data logs or events maintained within a computational system to provide a verifiable record of actions, transactions, or changes over time.
a chronological record of system-generated or user-triggered events captured within a computational system to support monitoring, auditing, debugging, or traceability.
an established structural or procedural construct within a computational system that enables the flow, transformation, or enforcement of rules upon data as part of a broader operational process.
a defined and repeatable procedure within a computational system used to process, analyze, or manipulate data according to a systematic approach or established protocol.
a brief annotation or explanatory comment attached to a data element within a computational system, providing contextual insight, clarification, or guidance without altering the underlying data.
a time-sensitive notification within a computational system that conveys important information, conditions, or changes related to data, prompting awareness, preparation, or responsive action.
a structured data construct within a computational system that represents a defined entity or data model that encapsulates both its attributes and kernels for its structural interpretation or operation.
data that represents observable facts or measurable phenomena within a computational system, recorded without personal bias or interpretation and verifiable through consistent methods or standards.
a bundled collection of programs or subroutines within a computational system, organized for coherent transport, processing, or reuse as a functional unit.
a structured unit of data formatted for transmission within or between computational systems, containing both payload and control information to ensure proper delivery, interpretation, and routing.
a semantic modifier within a computational system that refines the intent, scope, or behavior of a term or command, enabling contextual interpretation and meaningful configuration.
data that resides in a computational system without actively influencing or participating in current processes, typically stored for reference, archival, or deferred analysis.
the core content or meaningful information carried within a data packet, excluding metadata or control structures, and intended for processing, storage, or interpretation by the receiving system.
a specific contextual or interpretive viewpoint applied to data within a computational system, shaping how it is understood, framed, or utilized based on user roles, objectives, or analytical models.
a defined set of principles or rules within a computational system that governs the collection, usage, access, sharing, or retention of data to ensure compliance, security, and ethical management.
the declared operational reason within a computational or analytical context for which data is collected, processed, or utilized, distinct from legal justification and focused on functional intent at the data layer.
an explanatory reference within a computational system that justifies or clarifies the motivation behind a specific data-related action, decision, or condition, distinct from legal or policy mandates.
a recorded acknowledgment within a computational system confirming the successful reception of a data object, message, or transaction, often including metadata such as timestamp, source, and verification status.
a structured collection of related data fields treated as a single unit within a computational system, typically representing an instance of an entity or event for storage, retrieval, or processing.
a structured framework that defines the organization, types, and relationships of data attributes within a data object, guiding its validation, interpretation, and integration in computational systems.
a defined and ordered arrangement of related data structures—such as schemas, fields, or classification systems—within a computational system, used to organize, relate, and standardize data across contexts.
the specific condition or configuration of a data object or system component at a given point in time, reflecting its current values, status, or operational context within a computational process.
a clearly defined expression of a fact, rule, or condition within a computational system, often used to declare, assert, or instruct how data should be processed, interpreted, or constrained.
a branching diagram or structural lineage within a computational system that traces the derivation, transformation, or version history of data across sources or processes.
data that reflects personal opinions, interpretations, emotions, or perceptions captured within a computational system, often influenced by individual experience or context rather than objective measurement.
a defined word or phrase used within a computational system to label, express, or reference a data concept, enabling standardized interpretation and communication across structured data environments.
alphanumeric content within a computational system that conveys human-readable information, typically used for labels, descriptions, entries, or communication in structured or unstructured formats.
a discrete invocation unit within a computational system that conveys delegated authority and actively initiates the execution of specific actions or functions, serving as a proximal trigger within controlled workflows.
a structured sequence of linked data points or events within a computational system that traces the progression, movement, or lifecycle of an entity or process over time.