Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix broken rdf:type values #624

Open
briesenberg07 opened this issue Jul 22, 2024 · 1 comment
Open

fix broken rdf:type values #624

briesenberg07 opened this issue Jul 22, 2024 · 1 comment

Comments

@briesenberg07
Copy link

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.

@briesenberg07
Copy link
Author

This is primarily a data issue, not a platform issue (although involves the type options that that platform provides [1], and probably has other implications for the CVM app)... could be moved to opaquenamespace-data

[1]
image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant