We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Here's the version IRI according to the latest release
<owl:Ontology rdf:about="http://purl.obolibrary.org/obo/cl.owl"> <owl:versionIRI rdf:resource="http://purl.obolibrary.org/obo/cl/releases/2023-06-22/cl.owl"/>
This does not resolve!
Looking at the Config - & comparing to links from the release page, it looks like maybe it needs to redirect to https://github.com/obophenotype/cell-ontology/releases/download/2023-06-22/cl.owl
Wondering if this is a general issue for version IRIs where we've switched to using release assets due to large file sizes.
The text was updated successfully, but these errors were encountered:
http://purl.obolibrary.org/obo/cl/releases/2023-06-22/cl.owl is resolving now.
Sorry, something went wrong.
Uberon is broken too. Is this a general issue due to changes at GitHub?
Uberon is already correct the config. http://purl.obolibrary.org/obo/uberon/releases/2023-06-28/uberon.owl is resolving.
Yes, CL was missing the configuration for the releases only.
anitacaron
No branches or pull requests
Here's the version IRI according to the latest release
<owl:Ontology rdf:about="http://purl.obolibrary.org/obo/cl.owl">
<owl:versionIRI rdf:resource="http://purl.obolibrary.org/obo/cl/releases/2023-06-22/cl.owl"/>
This does not resolve!
Looking at the Config - & comparing to links from the release page, it looks like maybe it needs to redirect to https://github.com/obophenotype/cell-ontology/releases/download/2023-06-22/cl.owl
Wondering if this is a general issue for version IRIs where we've switched to using release assets due to large file sizes.
The text was updated successfully, but these errors were encountered: