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
http://purl.obolibrary.org/obo/obi is configured to go to the OBI home page
http://purl.obolibrary.org/obo/zfa is not configured and defaults to the amazon bucket we use for obo central build
proposal: unless explicitly overridden a base purl should go to the OBO info page, e.g. http://obofoundry.org/ontology/zfa.html
Note in future we may want a more semwebby approach, but may depend on e.g. OntoZoo/ontobee#122
The text was updated successfully, but these errors were encountered:
Also of note:
http://purl.obolibrary.org/obo/obi/OBI
goes to the home page, but via a circuitous route through OCLC
Also many semwebby folks expect to see
http://purl.obolibrary.org/obo/obi/OBI_
If this is declared to make OBI:nnnn CURIEs. This should be 30x'ed to the home page
Sorry, something went wrong.
+1 to the proposal.
I can fix to OBI redirect.
Do people really expect prefixes such as http://purl.obolibrary.org/obo/obi/OBI_ to resolve, and resolve to HTML pages?
Many common prefixes end in # and resolve to Turtle files. We don't do that for size reasons, and that's fine.
#
+1 Sounds good to me.
It would be nice to have a page to document it, such as, OBOFoundry wiki page.
+1 too.
No branches or pull requests
http://purl.obolibrary.org/obo/obi is configured to go to the OBI home page
http://purl.obolibrary.org/obo/zfa is not configured and defaults to the amazon bucket we use for obo central build
proposal: unless explicitly overridden a base purl should go to the OBO info page, e.g. http://obofoundry.org/ontology/zfa.html
Note in future we may want a more semwebby approach, but may depend on e.g.
OntoZoo/ontobee#122
The text was updated successfully, but these errors were encountered: