Skip to content
New issue

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

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

Already on GitHub? # to your account

Proposal to default to obofoundry.org ontology page for base purl #386

Open
cmungall opened this issue Nov 30, 2017 · 4 comments
Open

Proposal to default to obofoundry.org ontology page for base purl #386

cmungall opened this issue Nov 30, 2017 · 4 comments

Comments

@cmungall
Copy link
Contributor

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

@cmungall
Copy link
Contributor Author

cmungall commented Mar 9, 2018

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

@jamesaoverton
Copy link
Member

+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.

@zhengj2007
Copy link
Contributor

+1 Sounds good to me.

It would be nice to have a page to document it, such as, OBOFoundry wiki page.

@Public-Health-Bioinformatics
Copy link
Contributor

+1 too.

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants