# A Framework for the Evaluation of the Cultural Heritage Information Ontology
## 4 Discussion and Conclusions
\begin{table}
\begin{tabular}{l} \hline P07 [1 time]: Merging different concepts in the same class (Minor). \\ This pitfall affects: CLARITY \\ \(\bullet\) & A class whose name refers to two or more different concepts is created. \\ \(\bullet\) & This pitfall affects the element \\ \(\bullet\) & This pitfall affects: different concepts \\ \(\bullet\) & This pitfall affects: different concepts \\ \(\bullet\) & This pitfall affects: CLARITY, COMPLETENESS \\ \(\bullet\) & This pitfall consists of creating an ontology element and failing to provide human readable annotations attached to it. Consequently, ontology elements lack annotation properties that label them (e.g., _rdfs:label_, _lemm:LexicalEntry_, _skos:prefLabel_ or _skos:sultLabel_) or define them (e.g., _rdfs:comment_ or _d:clacscrip_). \\ \(\bullet\) & Example: [[http://www.cidoc-crm.org/cidoc-crm/P70i_is_documented_in](http://www.cidoc-crm.org/cidoc-crm/P70i_is_documented_in)]([http://www.cidoc-crm.org/cidoc-crm/P70i_is_documented_in](http://www.cidoc-crm.org/cidoc-crm/P70i_is_documented_in)), \\  & [[http://www.cidoc-crm.org/cidoc-crm/E93_Place](http://www.cidoc-crm.org/cidoc-crm/E93_Place)]([http://www.cidoc-crm.org/cidoc-crm/E93_Place](http://www.cidoc-crm.org/cidoc-crm/E93_Place)) doesn’t have _rdfs:comment_ defined. \\ \hline \multicolumn{2}{l}{P10: Missing disjointness (Important).} \\ This pitfall affects: COMPLETENESS \\ \(\bullet\) & The ontology lacks disjoint axioms between classes or between properties that should be defined as disjointed. \\ \(\bullet\) & Example for the [[http://www.cidoc-crm.org/cidoc-crm/E2_Temporal_Entity](http://www.cidoc-crm.org/cidoc-crm/E2_Temporal_Entity)]([http://www.cidoc-crm.org/cidoc-crm/E2_Temporal_Entity](http://www.cidoc-crm.org/cidoc-crm/E2_Temporal_Entity)) is textual (_rdfs:comment_), stating that “this class is disjoint from _E77_Persistent Item”_. Instead, _owl:differentFrom_ should be used. \\ \hline \multicolumn{2}{l}{P13 [275 times]: Inverse relationships not explicitly declared (Minor).} \\ This pitfall affects: COMPLETENESS \\ \(\bullet\) & This pitfall appears when any relationship (except for those that are defined as symmetric properties using _owl:SymmetricProperty_) does not have an inverse relationship (_owl:inverseOf_) defined within the ontology. \\ \(\bullet\) & Example: [[http://www.cidoc-crm.org/cidoc-crm/P94i_was_created_by](http://www.cidoc-crm.org/cidoc-crm/P94i_was_created_by)]([http://www.cidoc-crm.org/cidoc-crm/P94i_was_created_by](http://www.cidoc-crm.org/cidoc-crm/P94i_was_created_by)) and should have an inverse relationship, e.g., [[http://www.cidoc-crm.org/cidoc-crm/P94a_has_created](http://www.cidoc-crm.org/cidoc-crm/P94a_has_created)]([http://www.cidoc-crm.org/cidoc-crm/P94a_has_created](http://www.cidoc-crm.org/cidoc-crm/P94a_has_created)) \\ \hline \multicolumn{2}{l}{P30 [2 times]: Equivalent classes not explicitly declared (Important).} \\ This pitfall affects: COMPLETENESS \\ \(\bullet\) & This pitfall consists of missing the definition of equivalent classes (_owl:equivalentClass_) in the case of duplicated concepts. When an ontology reuses terms from other ontologies, classes that have the same meaning should be defined as equivalent to benefit the interoperability between both ontologies. \\ \(\bullet\) & Example: [[http://www.cidoc-crm.org/cidoc-crm/E69_Death](http://www.cidoc-crm.org/cidoc-crm/E69_Death)]([http://www.cidoc-crm.org/cidoc-crm/E69_Death](http://www.cidoc-crm.org/cidoc-crm/E69_Death)), \\  & [[http://www.cidoc-crm.org/cidoc-crm/E6](http://www.cidoc-crm.org/cidoc-crm/E6)]([http://www.cidoc-crm.org/cidoc-crm/E6](http://www.cidoc-crm.org/cidoc-crm/E6))\_Destruction \\ \hline \end{tabular}
\end{table} 
Table 6: Ontology pitfalls for the CIDOC CRM. of knowledge, facilitating sharing and reuse among all personnel involved in heritage building projects. Conceptualization, A.T. and S.G.d.O. ; methodology, A.T. and S.G.d.O. ; software, A.T.; validation, A.T. and S.G.d.O. ; formal analysis, A.T. and S.G.d.O. ; investigation, A.T. and S.G.d.O. ; resources, A.T. and S.G.d.O.