The Ccon Ontology

The Ccon Ontology
The Ccon represents the main concepts about the Cerrado plant communities structure and dynamics. This ontology will be part of the GeoLinked Data Ontology network to enrich the web of data with geospatial information of the Cerrado Biome, especially with regard the wood plant dynamics.
Creation Date
Last modified
en ru fr es pt

The following evaluation results have been generated by the RESTFul web service provided by OOPS! (OntOlogy Pitfall Scanner!). OOPS! is a software on development, and we will be happy to receive your feedbak. If you notice any issue in the evaluation, please contact us at

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.

Evaluation results

This pitfall consists in 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, lemon:LexicalEntry, skos:prefLabel or skos:altLabel) or that define them (e.g. rdfs:comment or dc:description). This pitfall is related to the guidelines provided in [5].

This pitfall affects to the following ontology elements:

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.

This pitfall affects to the following ontology elements:

The ontology elements are not named following the same convention (for example CamelCase or use of delimiters as "-" or "_") . Some notions about naming conventions are provided in [2].

*This pitfall applies to the ontology in general instead of specific elements

Two classes are defined as equivalent, using owl:equivalentClass, when they are not necessarily equivalent.

This pitfall affects to the following ontology elements:

It refers to reusing or referring to terms from another namespace that are not defined in such namespace. This is an undesirable situation as no information can be retrieved when looking up those undefined terms. This pitfall is related to the Linked Data publishing guidelines provided in [11]: "Only define new terms in a namespace that you control" and to the guidelines provided in [5].

This pitfall affects to the following ontology elements: