Fix semantics of UndefinedClassesOrProperties metric about quality HOT 5 OPEN

I have improved the documentation of the compute method in 1c1aaa5, but identified some more issues, so I'll keep this issue open for now, and will rewrite the description.

from quality.

@muhammadaliqasmi I saw you have already made some progress, which is great.

However let me remind you that when doing checks of the type “the predicate of the triple is ”, one always has to compare the full URI of the property, and it's case-sensitive. Considering https://github.com/diachron/quality/blob/master/src/main/java/de/unibonn/iai/eis/diachron/qualitymetrics/intrinsic/consistency/UndefinedClassesOrProperties.java#L111 it would be correct to to something like "http://www.w3.org/1999/02/22-rdf-syntax-ns#type".equals(tmpURI). Similar to the way you implemented LabelsUsingCapitals, just that this time we can really hard-code the names of the properties instead of using a configuration file. When I use the notation rdf:type above, it's really just because I'm too lazy to type out the full URI.

In the next few minutes I will add a list of OWL properties above.

from quality.

To the description above I have now added the OWL properties that indicate that the expected object should be a defined class or property.

from quality.

I'm sorry I didn't post this earlier, but when I inspected this class once more (in this version) I noticed that property names are not handled in a case-sensitive way (e.g. here). However in the RDF data model all URIs are case sensitive. When fixing these, please also think of other metrics where the same thing may need fixing – thanks!

from quality.

I created two different metrics: one fpr undefined classes and one for the undefined properties. Important to notice: the undefined classes metric as it is defined below computes ratio of undefined classes in object position.

from quality.