An ontology and conceptual framework designed to represent the semantics of cultural‑heritage information (objects, actors, events, temporal and spatial contexts) so that heterogeneous museum, archive, and collection records can interoperate and support provenance, contextualization, and integrated queries across institutions.

Principle

Modeling cultural heritage with an event‑ and relationship‑centered ontology (rather than purely object‑centric records) enables explicit representation of provenance, transformations, and contextual links that support semantic interoperability between disparate systems.

Demonstration

Illustrative scenario → Two institutions map their catalogue fields to CIDOC CRM classes: one records an object’s creation event and associated artist, the other records acquisition and restoration events. When records are published as CRM‑aligned triples, a researcher can query the combined graph to trace creation→ownership→conservation chains across both collections (Action), enabling integrated provenance reconstruction (Consequence).

Misapplication

Using CIDOC CRM as if it were an input form or a fixed data schema and populating classes with unstructured literal strings, which conflates semantic modeling with display practice; the error is treating ontology classes as presentation fields rather than formal semantic types and relations, undermining interoperability.

Consequence

Correctly used, CIDOC CRM provides a formal, machine‑interpretable basis for unifying disparate cultural heritage descriptions, supporting advanced queries and inference about provenance and relationships. Misuse yields inconsistent mappings, semantic drift, and loss of intended inferential power across datasets.

Reversal

CIDOC CRM is an ontology for semantic description, not a user interface or cataloguing standard; for small collections or simple display needs its formalism may be disproportionate, and some curatorial details may still require local extensions—adoption implies modeling cost and a commitment to semantic mapping practices.

Boundary

Clearly within: representing creation, modification, ownership, and exhibition events and their actors to support cross‑collection queries. Boundary case: very simple inventory lists where only minimal descriptive strings exist—mapping may be partial. Clearly outside: a presentation template or display‑only record that does not expose formalized relations for machine processing.

Semantic Tension

Formal semantic interoperability ↔ Local descriptive practice and curatorial autonomy: the CRM’s standardized ontology encourages shared semantics but can conflict with institution‑specific vocabularies or practical workflows.

Synthesis

CIDOC CRM supplies an event‑oriented formal vocabulary that makes provenance and contextual relations explicit, turning heterogeneous descriptive statements into a common semantic substrate for cross‑institutional reasoning.