Situation

Each resource should have an rdf:type.

Problem

Some resources don't have a type except in some cases owl:NamedIndividual, which is not.

Solution

The editors need to add the missing types, with the help of the domain experts if necessary.

Situation

Each classified should belong to a catalogue.

Problem

Some classifieds don't belong to any catalogue.

Solution

The extractors need to add a catalogue for each such classified in the list.

Situation

Each software product should have at least one function.

Problem

Some software products may not have any functions.

Solution

The editors need to research and add features to the software products listed below.

Situation

If a concept is used as the object in some triple, then it should have its own attributes (occur as a subject).

Problem

Sometimes concepts occur as only as an object but not as a subject.

Solution

The responsible extractors for the respective subontologies need to add statements for the objects listed below.

Situation

Each HITO property has a domain that defines allowed subjects.

Problem

Some classes are used as a subject for a triple without being a direct or transitive subclass of the defined domain of the property.

Solution

The offending triples should be removed or remodelled to conform to the domain.

Situation

Each HITO property has a range that defines allowed objects.

Problem

Some classes are used as an object for a triple without being a direct or transitive subclass of the defined range of the property.

Solution

The offending triples should be removed or remodelled to conform to the range.

Situation

Classes are sets of individuals and can be subclasses (subsets) of other classes.

Problem

Subclass cycles (A subclass of B ... subclass of A) collapse all members of the cycle to the same set, which is assumed to be unintentional.

Solution

Find subclass cycles below and and manually remove at least one of them. Because of the limitiations of SPARQL 1.1 property paths, we cannot select the full cycle but only give all pairs of classes on a cycle.

Situation

Class URLs should conform to UpperCamelCase.

Problem

Naming conventions weren't clearly set from the beginning and some pecularities are not widely known, for example abbreviations such as IbmMachine, not IBMMachine.

Solution

Manually correct offending class URLs.

Situation

Property URLs should conform to lowerCamelCase.

Problem

Naming conventions weren't clearly set from the beginning and some pecularities are not widely known, for example abbreviations such as updatesAtm, not updatesATM.

Solution

Manually correct offending property URLs.

Situation

Our URIs begin with http://...

Problem

Tools like the OntoWiki sometimes fail to expand a prefix and thus create URIs that have an incorrect prefix.

Solution

List all triples with URIs that are neither HTTP URIs nor blanknodes.

Situation

Some URIs are used in the property position of a triple but are neither declared as owl:ObjectProperty, nor as owl:DataTypeProperty.

Problem

This violates the typing constraints of OWL 2 DL.

Solution

List all URIs are used in the property position of a triple but are neither declared as owl:ObjectProperty, nor as owl:DataTypeProperty. Exclude those defined in vocabularies like RDF, RDFS, OWL and so on.

Situation

Some URIs may be defined as more than one of owl:ObjectProperty, owl:DatatypeProperty and owl:AnnotationProperty.

Problem

This violates the typing constraints of OWL 2 DL.

Solution

List all URIs that are defined as more than one of owl:ObjectProperty, owl:DatatypeProperty and owl:AnnotationProperty.