extraction-framework icon indicating copy to clipboard operation
extraction-framework copied to clipboard

some invalid domain, range, subPropertyOf

Open VladimirAlexiev opened this issue 11 years ago • 0 comments

  1. Consider http://mappings.dbpedia.org/index.php/OntologyProperty:FirstAscent: it specifies rdfs:domain Mountain, Volcano.

The author of that mapping probably thought this means that the property firstAscent should apply to Mountain or Volcano. But by RDFS semantics, when you specify multiple classes as domain/range for a property, then every subject/object of a property is inferred to have all these classes. Eg in the above case, any subject will be inferred to be both Mountain and Volcano.

Furthermore, the ontology generator doesn't emit two classes, but one invalid class URI:

dbo:firstAscent rdfs:domain <http://dbpedia.org/ontology/Mountain,Volcano> ;
  1. Some subProperty statements have an object spelt in Uppercase.
  • in some cases this leads to a statement that does not connect to the intended property (in this case dbo:medalist), e.g.:
dbo:silverMedalist rdfs:subPropertyOf dbo:Medalist
  • in other cases it leads to a statement which links to a class, which is a mistake
dbo:senator rdfs:subPropertyOf dbo:MemberOfParliament .

Out of 62 subProperty declarations, 20 have this problem:

dbo:bronzeMedalist rdfs:subPropertyOf dbo:Medalist . dbo:codeLandRegistry rdfs:subPropertyOf dbo:Code . dbo:codeMemorial rdfs:subPropertyOf dbo:Code . dbo:distanceToCapital rdfs:subPropertyOf dbo:Distance . dbo:dutchMIPCode rdfs:subPropertyOf dbo:Code . dbo:goldMedalist rdfs:subPropertyOf dbo:Medalist . dbo:iso6391Code rdfs:subPropertyOf dbo:LanguageCode . dbo:iso6392Code rdfs:subPropertyOf dbo:LanguageCode . dbo:iso6393Code rdfs:subPropertyOf dbo:LanguageCode . dbo:musicalKey rdfs:subPropertyOf dbo:Type . dbo:officialSchoolColour rdfs:subPropertyOf dbo:ColourName . dbo:otherWins rdfs:subPropertyOf dbo:Wins . dbo:politicGovernmentDepartment rdfs:subPropertyOf dbo:Department . dbo:protectionStatus rdfs:subPropertyOf dbo:Status . dbo:rankingWins rdfs:subPropertyOf dbo:Wins . dbo:senator rdfs:subPropertyOf dbo:MemberOfParliament . dbo:silCode rdfs:subPropertyOf dbo:LanguageCode . dbo:silverMedalist rdfs:subPropertyOf dbo:Medalist . dbo:subTribus rdfs:subPropertyOf dbo:Tribus . dbo:superTribus rdfs:subPropertyOf dbo:Tribus .

  1. I'm not sure whether it's a good idea to have classes and properties that have the same name, except capitalization. The mapping wiki uppercases properties, e.g. http://mappings.dbpedia.org/index.php/OntologyClass:MemberOfParliament http://mappings.dbpedia.org/index.php/OntologyProperty:MemberOfParliament So the difference between these two is lost on people. There are 152 terms with duplicate names (see attachment). But I don't imagine it's feasible to change all these now...

Would be nice if the mapping wiki and/or the ontology generator checks this:

  • no commas in domain/range
  • internal subPropertyOf are lowercase
  • internal subPropertyOf and subClassOf actually exist

VladimirAlexiev avatar Dec 05 '14 16:12 VladimirAlexiev