Core Domain Ontology
type: Ontology
imports: time
license: http://creativecommons.org/licenses/by/3.0/
creator: Bart Gajderowicz (bartg@secours.ai)
creator: Keith Dugas (keith.dugas@secours.ai)
creator: Paul Knowles (paul@secours.ai)
description: 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.
issued: 2025-05-26
modified: 2026-03-27
rights: Copyright @ 2026 Paul Knowles, Bart Gajderowicz, Keith Dugas
preferred namespace prefix: cdo
version info: Version 1 May 26, 2026

accessedBy
type: ObjectProperty
domain: Domain
range: Concept
comment: relates a Domain to a Concept, indicating that a Domain is accessed by a Concept.

achieves
type: ObjectProperty
domain: Event
range: Goal
comment: relates an Event to a Goal, indicating that an Event defines a Goal.

acknowledges
type: ObjectProperty
domain: Receipt
range: Packet
comment: relates a Receipt to a Packet, inverse of acknowledges indicating that a Receipt acknowledges a Packet.

affirms
type: ObjectProperty
domain: Statement
range: Fact
comment: relates a Statement to a Fact, indicating that a Statement affirms a Fact.

annotates
type: ObjectProperty
inverse of: isAnnotatedBy
domain: Text
range: Chart
comment: relates a Text to a Chart, indicating that a Text annotates a Chart.

attributedTo
type: ObjectProperty
domain: Event
range: Reason
comment: relates an Event to a Reason, indicating that an Event is attributed to a Reason.

capturedAs
type: ObjectProperty
domain: Domain
range: Object
comment: relates a Domain to an Object, indicating that a Domain is captured as an Object.

confirms
type: ObjectProperty
domain: Receipt
range: Notice
comment: relates a Receipt to a Notice, inverse of isConfirmedBy indicating that a Receipt is confirmed by a Notice.

constructs
type: ObjectProperty
domain: Mechanism
range: Scheme
comment: relates a Mechanism to a Scheme, indicating that a Mechanism constructs a Scheme.

contextualizes
type: ObjectProperty
domain: Concept
range: Object
comment: relates a Object to a Concept, indicating that a Concept contexualizes an Object.

conveys
type: ObjectProperty
domain: Packet
range: Payload
comment: relates a Packet to a Payload, indicating that a Packet conveys a Method.

declares
type: ObjectProperty
domain: Packet
range: Method
comment: relates a Packet to a Method, indicating that a Packet declares a Method.

defines
type: ObjectProperty
inverse of: isDefinedBy
domain: Term
range: Concept
comment: relates a Term to a Concept, indicating that a Term defines a Concept.

definesLayoutFor
type: ObjectProperty
domain: Schema
range: Form
comment: relates a Schema to a Form, indicating that a Schema defines layout for a Form.

delivers
type: ObjectProperty
domain: Packet
range: Statement
comment: relates a Packet to a Statement, indicating that a Packet delivers a Statement.

encapsulates
type: ObjectProperty
domain: Function
range: Payload
comment: relates a Function to a Payload, indicating that a Function encapsulates a Payload.

encodes
type: ObjectProperty
domain: Payload
range: State
comment: relates a Payload to a State, indicating that a Payload encodes a State.

enteredAs
type: ObjectProperty
domain: Domain
range: Event
comment: relates a Domain to an Event, indicating that a Domain is entered as an Event.

exchangedThrough
type: ObjectProperty
domain: Domain
range: Action
comment: relates a Domain to an Action, indicating that a Domain is exchanged through an Action.

fulfills
type: ObjectProperty
domain: Method
range: Purpose
comment: relates a Method to a Purpose, indicating that a Method fulfills a Purpose.

grounds
type: ObjectProperty
domain: Text
range: Stemma
comment: relates a Text to a Stemma, indicating that a Text grounds a Stemma.

guides
type: ObjectProperty
domain: Purpose
range: Reason
comment: relates a Purpose to a Reason, indicating that a Purpose guides a Reason.

hasMetadata
type: ObjectProperty
domain: Packet
range: Note
comment: relates a Packet to a Note, indicating that a Packet has metadata captured in a Note.

initiates
type: ObjectProperty
inverse of: isInitiatedBy
domain: Cause
range: Action
comment: relates a Cause to an Action, indicating that an Cuase initiates an Action.

invokes
type: ObjectProperty
domain: Token
range: Function
comment: relates a Token to a Function, indicating that a Token invokes a Function.

isAcknowledgedBy
type: ObjectProperty
inverse of: acknowledges
domain: Packet
range: Receipt
comment: relates a Packet to a Receipt, inverse of acknowleges, indicating that a Packet is acknowledged by a Receipt.

isActivatedBy
type: ObjectProperty
domain: Action
range: Token
comment: relates an Action to a Token, indicating that an Action is activated by a Token.

isAddressedBy
type: ObjectProperty
domain: Field
range: Index
comment: relates a Field to an Index, indicating that a Field is addressed by an Index.

isAnnotatedBy
type: ObjectProperty
domain: Chart
range: Text
comment: relates a Chart to a Text, indicating that a Chart is annotated by a Text.

isBundledIn
type: ObjectProperty
domain: Card
range: Schema
comment: relates a Card to a Schema, indicating that a Card is bundled in a Schema.

isCapturedBy
type: ObjectProperty
domain: Payload
range: Record
comment: relates a Payload to a Record, indicating that a Payload is captured by a Record.

isCommittedTo
type: ObjectProperty
domain: Record
range: Log
comment: relates a Record to a Log, indicating that a Record is committed to a Log.

isConfirmedBy
type: ObjectProperty
inverse of: confirms
domain: Notice
range: Receipt
comment: relates a Notice to a Receipt, inverse of confirms, indicating that a Notice confirms a Receipt.

isConsumedBy
type: ObjectProperty
domain: Form
range: Mechanism
comment: relates a Form to a Mechanism, indicating that a Form is consumed by a Mechanism.

isDefinedBy
type: ObjectProperty
domain: Concept
range: Term
comment: relates a Concept to a Term, indicating that a Concept is defined by a Term.

isDerivedBy
type: ObjectProperty
domain: Log
range: Stemma
comment: relates a Log to a Stemma, indicating that a Log is derived by a Stemma.

isDescribedBy
type: ObjectProperty
domain: Object
range: Attribute
comment: relates an Object to an Attribute, indicating that an Object is described by an Attribute.

isDrivenBy
type: ObjectProperty
domain: Action
range: Reason
comment: relates an Action to a Reason, indicating that an Action is driven by a Reason.

isExplainedBy
type: ObjectProperty
domain: Policy
range: Note
comment: relates a Policy to a Note, indicating that a Policy is explained by a Note.

isExpressedBy
type: ObjectProperty
domain: Attribute
range: Card
comment: relates a Attribute to a Card, indicating that an Attribute is expressed by a Card.

isFramedBy
type: ObjectProperty
domain: Parameter
range: Frame
comment: relates a Parameter to a Frame, indicating that a Parameter is framed by a Frame.

isImpactedBy
type: ObjectProperty
domain: Object
range: Cause
comment: relates an Object to a Cause, indicating that an Object is impacted by a Cause.

isInitiatedBy
type: ObjectProperty
domain: Action
range: Cause
comment: relates an Action to a Cause, indicating that an Action is initiated by a Cause.

isInstantiationOf
type: ObjectProperty
domain: Action
range: Method
comment: relates an Action to a Method, indicating that an Action is an instantiation of a Method.

isIssuedUnder
type: ObjectProperty
domain: Receipt
range: Policy
comment: relates a Receipt to a Policy, indicating that a Receipt is issued under (according to) a Policy.

isMetadataFor
type: ObjectProperty
inverse of: hasMetadata
domain: Note
range: Packet
comment: relates a Note to a Packet, indicating that a Note is the metadata for a Packet.

isOrientedBy
type: ObjectProperty
inverse of: orients
domain: Goal
range: Concept
comment: relates a Goal to a Concept, indicating that a Goal is oriented by a Concept to be defined.

isPackagedAs
type: ObjectProperty
domain: Payload
range: Package
comment: relates a Payload to a Package, indicating that a Payload is packaged as a Package.

isRealizedThrough
type: ObjectProperty
domain: Effect
range: Mechanism
comment: relates an Effect to a Mechanism, indicating that an Effect is realized through a Mechanism.

isRecordedAs
type: ObjectProperty
domain: Ledger
range: Track
comment: relates a Ledger to a Track, indicating that a Ledger is recorded as a Track.

isRefinedBy
type: ObjectProperty
domain: Term
range: Parameter
comment: relates a Term to a Parameter, indicating that a Term is refined by a Parameter.

isRegisteredBy
type: ObjectProperty
domain: Index
range: Record
comment: relates an Index to a Record, indicating that an Index is registered by a Record.

isRepresentedBy
type: ObjectProperty
domain: State
range: Chart
comment: relates a State to a Chart, indicating that a State is represented by a Chart.

isScopedBy
type: ObjectProperty
domain: Concept
range: Scheme
comment: relates a Concept to a Scheme, indicating that a Concept is scoped by a Scheme.

isStructuredBy
type: ObjectProperty
domain: Object
range: Scheme
comment: relates an Object to a Scheme, indicating that an Object is structured by a Scheme.

isTransmittedAs
type: ObjectProperty
domain: Package
range: Packet
comment: relates a Package to a Packet, indicating that a Package is transmitted as a Packet.

isWrittenTo
type: ObjectProperty
domain: Stemma
range: Ledger
comment: relates a Stemma to a Ledger, indicating that a Stemma is written to a Ledger.

loggedAt
type: ObjectProperty
domain: Log
range: Instant
comment: The recorded process logs of the schema synthesization and transformation pipeline.

occursIn
type: ObjectProperty
domain: Event
range: Field
comment: relates an Event to a Field, indicating that an Event occurs in a Field.

orders
type: ObjectProperty
domain: Stemma
range: Effect
comment: relates a Stemma to an Effect, indicating that a Stemma orders an Effect.

orients
type: ObjectProperty
domain: Concept
range: Goal
comment: relates a Concept to a Goal, indicating that a Concept orients a Goal.

produces
type: ObjectProperty
domain: Action
range: Event
comment: relates an Action to an Event, indicating that an Action produces an Event.

realizes
type: ObjectProperty
domain: Event
range: Effect
comment: relates an Event to an Effect, indicating that an Event realizes an Effect.

represents
type: ObjectProperty
domain: Form
range: State
comment: relates a Form to a State, indicating that a Form represents a State.

specifies
type: ObjectProperty
domain: Concept
range: Method
comment: relates a Concept to a Method, indicating that a Concept specifies a Method.

stores
type: ObjectProperty
domain: Record
range: Form
comment: relates a Record to a Form, indicating that a Record stores a Form.

supports
type: ObjectProperty
domain: Fact
range: Purpose
comment: relates a Fact to a Purpose, indicating that a Fact supports a Purpose.

traces
type: ObjectProperty
domain: Track
range: Stemma
comment: relates a Track to a Stemma, indicating that a Track traces a Stemma.

undergoes
type: ObjectProperty
domain: Object
range: Effect
comment: relates an Object to an Effect, indicating that an Object undergoes an Effect.

yields
type: ObjectProperty
domain: Frame
range: Notice
comment: relates a Frame to a Notice, indicating that a Frame yields a Notice.

Action
type: Class
subclass of: Active
comment: an intentional operation performed within a computational system that acts upon data to achieve a specific outcome, such as creation, transformation, transmission, or deletion.

Active
type: Class
subclass of: Behaviour
comment: 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.

Attribute
type: Class
comment: 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.

Behaviour
type: Class
comment: the observable pattern of responses, interactions, or state changes exhibited by data within a computational system in reaction to specific inputs, conditions, or stimuli.

Card
type: Class
comment: 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.

Cause
type: Class
comment: 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.

Chart
type: Class
comment: 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.

Concept
type: Class
subclass of: Subjective
comment: 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.

Domain
type: Class
comment: facts and statistics entered into a computational system, structured for reference, processing, or analysis within a defined informational context.

Effect
type: Class
comment: 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.

Event
type: Class
subclass of: Objective
comment: 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.

Fact
type: Class
comment: 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.

Field
type: Class
comment: 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.

Form
type: Class
comment: 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.

Frame
type: Class
comment: a semantic structure within a computational system that organizes and contextualizes data by linking attributes to concepts, enabling meaningful interpretation, interoperability, and knowledge representation.

Function
type: Class
comment: 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.

Goal
type: Class
comment: 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.

Index
type: Class
comment: a structured containment layer that encapsulates one or more fields, defining local boundaries, validation logic, and schema constraints within a form or data model.

Ledger
type: Class
comment: 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.

Log
type: Class
comment: a chronological record of system-generated or user-triggered events captured within a computational system to support monitoring, auditing, debugging, or traceability.

Mechanism
type: Class
comment: 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.

Method
type: Class
comment: a defined and repeatable procedure within a computational system used to process, analyze, or manipulate data according to a systematic approach or established protocol.

Note
type: Class
comment: 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.

Notice
type: Class
comment: a time-sensitive notification within a computational system that conveys important information, conditions, or changes related to data, prompting awareness, preparation, or responsive action.

Object
type: Class
subclass of: Passive
comment: 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.

Objective
type: Class
subclass of: Perspective
comment: 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.

Package
type: Class
comment: a bundled collection of programs or subroutines within a computational system, organized for coherent transport, processing, or reuse as a functional unit.

Packet
type: Class
comment: 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.

Parameter
type: Class
comment: 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.

Passive
type: Class
subclass of: Behaviour
comment: data that resides in a computational system without actively influencing or participating in current processes, typically stored for reference, archival, or deferred analysis.

Payload
type: Class
comment: 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.

Perspective
type: Class
comment: 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.

Policy
type: Class
comment: 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.

Purpose
type: Class
comment: 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.

Reason
type: Class
comment: 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.

Receipt
type: Class
comment: 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.

Record
type: Class
comment: 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.

Schema
type: Class
comment: 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.

Scheme
type: Class
comment: 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.

State
type: Class
comment: 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.

Statement
type: Class
comment: 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.

Stemma
type: Class
comment: a branching diagram or structural lineage within a computational system that traces the derivation, transformation, or version history of data across sources or processes.

Subjective
type: Class
subclass of: Perspective
comment: 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.

Term
type: Class
comment: 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.

Text
type: Class
comment: alphanumeric content within a computational system that conveys human-readable information, typically used for labels, descriptions, entries, or communication in structured or unstructured formats.

Token
type: Class
comment: 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.

Track
type: Class
comment: 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.