Unidirectionally Related Concepts and Disconnected Concept Clusters

[titoBouzout]

Hi there!

The tool is persistently reporting this error "Disconnected Concept Clusters", and I can't understand why, as it looks correct to me. Two things may happen, or I'm misinterpreting what a "Disconnected Concept Clusters" means, or we may consider the tool may have a bug. Very likely the first one.. but let's check!

In the following test RDF, https://dl.dropboxusercontent.com/u/9303546/directory/structure.rdf

1. The tool was reporting that I had a problem with "Unidirectionally Related Concepts" because the four Concepts were not defining a reciprocal "topConceptOf" to the ConceptScheme. However the ConceptScheme was defining the "hasTopConcept" for the four Concepts. I fixed this issue by defining the reciprocal "topConceptOf" in the Concepts.
2. ... Now.. the tool is reporting "Disconnected Concept Clusters (2)" .. and my guess is that the tool knows that the last two Concepts (#related_category_(1/2)") have no narrower/broader properties... these are just Top Concepts already defined in the ConceptScheme...

Is somewhat contradictory, the inconsistency comes from: The tool is not telling that there is two "Unidirectionally Related" concepts, but tells that there are two "Disconnected Concepts".

I understand this is a QC tool... but may the message can be improved; I imagine that "Disconnected Concepts" are valid if these at least are defined as topConceptOf of a ConceptScheme, or the ConceptScheme defines these Concepts as hasTopConcept.

What do you think? In that situation may a "WARN" instead of "FAIL" can be displayed.

[cmader]

Thanks for pointing this out! You're right, concept clusters might not be interpreted as disconnected if they include at least one top concept. A WARN log message sounds like a good idea in that case indeed. I will consider this in the next releases!