Conceptual Semantics

Go up to Terms and Definitions

Discussion

Conceptual semantics defines meaning at the level of domain concepts, relationships, distinctions, and constraints before an architecture selects implementation technology.

Conceptual semantics establishes domain meaning independently of schemas, databases, programming languages, RDF graphs, OWL ontologies, message formats, APIs, reports, or runtime logic. A conceptual model expresses conceptual semantics when it identifies the things in a domain, the relationships among those things, the distinctions that matter, and the constraints that govern interpretation.

Conceptual semantic content includes:

Domain conceptsBusiness termsRelationships among conceptsRoles played by participantsClassifications and distinctionsConstraints on valid meaningLifecycle statesEvents and state transitionsBusiness rulesReporting facts and dimensionsPolicies and governance conceptsDomain assumptionsA governed architecture preserves traceability from conceptual semantics to downstream artefacts. Traceability prevents implementation artefacts from replacing the intended domain meaning.

Definition

meaning defined through domain concepts, relationships, distinctions, and constraints before selection of implementation technology

Source

DIDO Solutions usage, informed by conceptual modelling, terminology practice, semantic modelling practice, and model-driven architecture principles.

Note

Conceptual semantics is not equivalent to OWL, RDF, RDF graph structure, schema structure, datatype structure, or implementation logic. Those artefacts express selected conceptual meaning after the architecture establishes the underlying domain meaning.

Example

An FX conceptual model defines concepts such as Trade, Counterparty, Currency Pair, Notional Amount, Trade Date, Settlement Date, and Settlement Obligation. These concepts establish conceptual semantics before the architecture represents selected content in schemas, reports, RDF graphs, OWL ontologies, DDS topics, databases, or executable validation logic.

© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.