You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
*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.
The text was updated successfully, but these errors were encountered:
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
Describe the bug
Many resources in opaquenamespace.org are typed* using the following RDF classes which do not exist:
*That is, resources where the description includes a triple like the following:
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:
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.
The text was updated successfully, but these errors were encountered: