ControlledVocabularyManager
ControlledVocabularyManager copied to clipboard
fix broken rdf:type values
Describe the bug Many resources in opaquenamespace.org are typed* using the following RDF classes which do not exist:
http://www.w3.org/2004/02/skos/core#CorporateName
http://www.w3.org/2004/02/skos/core#PersonalName
http://www.w3.org/2004/02/skos/core#Geographic
http://www.w3.org/2004/02/skos/core#Title
http://www.w3.org/2004/02/skos/core#Topic
*That is, resources where the description includes a triple like the following:
<ons_resource> rdf:type <instance_of_class> .
To Reproduce A little Python notebook which parses all ONS vocabs into a graph and counts resources in each which are typed using the above classes is available in this secret gist.
Expected behavior I would expect resources in ONS to be typed using classes which:
- exist, and are taken from a vocabulary which adheres to linked data best practices (for example, meet criteria in the Vocabulary Checklist from Best Practices for Publishing Linked Data > 6. Standard Vocabularies)
- are compatible with the other statements made about the resource (for example, no conflicts with restrictions on the class)
Screenshots n/a
Related work Additional details available in this secret gist. This issue does not seem to be affecting retrieval of labels for display in Oregon Digital.