VocBench Logo

Home Documentation Downloads Support About us

ICV (Integrity Constraint Validation)

VocBench features a set of Integrity Constraint Validation (ICV) checks that can be run on the ontologies and thesauri being edited, in order to validate their content.

Currently most of the checks are for SKOS and SKOS-XL thesauri, as the SKOS standard includes many constraints which are not expressed through OWL axioms and which need thus dedicated machinery in order to be verified. In the near future more checks for OWL ontologies will be implemented.

All of the available entries are actually not just validation checks, but each of them provide fixing utilities for any inconsistency found.

icv screenshot

Basically in ST the ICVs are separated in two main set of checks:

Structural checks

The structural checks, as the name suggests, allow to identify and fix structural problems as the presence of dangling concepts in any scheme (i.e. concepts that, for any given scheme, have no broader concept belonging to the same scheme and that are not top concepts of that scheme ), structural cycles, skos schemes that have no top concept and so on. Note that, despite their name, not all checks correspond to a real integrity corruption. In the following figure, the used check reports that a concept is both a top concept of a scheme and has a broader concept in the same scheme. This situation is perfectly legal in SKOS, though many thesauri developers might want to avoid this situation, so we have provided the test, and it is up to the project administrator decide what is admitted and what is not in the thesaurus they manage.

structural checks

Labeling checks

The labeling checks concerns integrity breaks such as: concepts that haven't a preferred label, concepts with more than one preferred label in the same language, concepts with identical labels in the same language and so on.

Other checks

Currently the onyl available check here is the one that allows users to fix concepts having URIs with whitespaces.