Instantiation

How class hierarchies materialise; particulars and classes

Instantiation and materialization

Instantiation connects class hierarchies to individuals: which particulars—or, in multi-level settings, which classes—stand in an instance-of relationship to which class. The treatise’s central clarification is that both particulars and classes can be instantiated, and that particulars and classes can sometimes be “cast” into each other’s roles—yet, with the sole exception of horizontal instantiation, particulars never instantiate other particulars. The word instance is not used uniformly in the literature; TAoKE ties it to class hierarchies and to data property inherence.

See [FoAl2021] and [AlCa2018] for multi-level and conceptual-structure background.

Instance-of and class assertions

Typical patterns use ◊iof (instance-of) between a particular and a class, combined with ◊subClassOf links that constrain which DPs and OPs apply. The canonical text develops this alongside layers (schema vs. particulars) and DPI restrictions sketched on the Classes page.

deriver.app

Session facts and rule conclusions correspond to instantiated knowledge: keep identifiers traceable to the class-level model so exports and audits remain coherent.

Source: taoke.de — Instantiation.

References

  1. [FoAl2021] Claudenir M. Fonseca, João Paulo A. Almeida, Giancarlo Guizzardi, Victorio A. Carvalho, Multi-level conceptual modeling: Theory, language and application, Data & Knowledge Engineering 134(1):101894 , 2021, DOI: 10.1016/j.datak.2021.101894, https://www.researchgate.net/publication/351567433_Multi-level_conceptual_modeling_Theory_language_and_application, last visit: 09.04.2026
  2. [AlCa2018] Joao Paulo A. Almeida, Victorio A. Carvalho, Freddy Brasileiro, Claudenir M. Fonseca, Giancarlo Guizzardi, Multi-Level Conceptual Modeling: Theory and Applications , 2019, https://www.researchgate.net/publication/328141389_Multi-Level_Conceptual_Modeling_Theory_and_Applications, last visit: 09.04.2026