COINS Building Information Model (CBIM)

COINS Building Information Model (CBIM)
COINS Building Information Model (CBIM)
Ontology languages
Ontology format
See alignments

Evaluation results

The following evaluation results have been generated by the RESTFul web service provided by OOPS! (OntOlogy Pitfall Scanner!).

OOPS! logoIt is obvious that not all the pitfalls are equally important; their impact in the ontology will depend on multiple factors. For this reason, each pitfall has an importance level attached indicating how important it is. We have identified three levels:

It is crucial to correct the pitfall. Otherwise, it could affect the ontology consistency, reasoning, applicability, etc.
Though not critical for ontology function, it is important to correct this type of pitfall.
It is not really a problem, but by correcting it we will make the ontology nicer.

A class is created whose identifier is referring to two or more different concepts. An example of this type of pitfall is to create the class "StyleAndPeriod", or "ProductOrService".

This pitfall affects to the following ontology elements:

Ontology terms lack annotations properties. This kind of properties improves the ontology understanding and usability from a user point of view.

This pitfall affects to the following ontology elements:

Relationships and/or attributes without domain or range (or none of them) are included in the ontology. There are situations in which the relation is very general and the range should be the most general concept "Thing". However, in other cases, the relations are more specific and it could be a good practice to specify its domain and/or range. An example of this type of pitfall is to create the relationship "hasWritten" in an ontology about art in which the relationship domain should be "Writer" and the relationship range should be "LiteraryWork". This pitfall is related to the common error when defining ranges and domains described in [3].

This pitfall affects to the following ontology elements:

Guidelines in [5] suggest avoiding file extension in persistent URIs, particularly those related to the technology used, as for example ".php" or ".py". In our case we have adapted it to the ontology web languages used to formalized ontologies and their serializations. In this regard, we consider as pitfall including file extensions as ".owl", ".rdf", ".ttl", ".n3" and ".rdfxml" in an ontology URI. An example of this pitfall (at 29th June, 2012) could be found in the "BioPAX Level 3 ontology (biopax)" ontology��s URI ( that contains the extension ".owl" related to the technology used.

*This pitfall applies to the ontology in general instead of specific elements and it appears in the ontology URI: