Closed KonradHoeffner closed 3 years ago
Those are all features that support functions, they shouldn't be in that table at all but instead in feature_supports_function. And the features that have subfeatures need to be included instead, find out why that doesn't work.
Added in 119322718a74625d0795132eb1362df86265c772.
In https://github.com/hitontology/csv2rdf, the property hito:subFeatureOf is used. The ontology defines:
### http://hitontology.eu/ontology/subFeatureOf
:featureClassifiedComponent rdf:type owl:ObjectProperty ;
rdfs:subPropertyOf :subClassifiedOf ;
rdfs:domain :FeatureClassified;
rdfs:range :FeatureClassified;
rdfs:label "subfeature of"@en .
There is a mismatch between the URI on the one hand, and the comment and label on the other hand. The problem lies in https://github.com/hitontology/ontology/commit/508f231c6ad57631a51a69b73544e1dc8c9bba51, hito:subFeatureOf is the correct one.
I corrected that in the ontology and uploaded the new hito.ttl in the SPARQL endpoint conductor interface. https://hitontology.eu/ontology/subFeatureOf is now defined. Rerunning the download script now includes subfeatures.
All the subFeatures and support entries are now in the database.
classified_has_child.sql
Shouldn't there be much more?