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

Update goref-0000116.md #1671

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open

Update goref-0000116.md #1671

wants to merge 2 commits into from

Conversation

cmungall
Copy link
Member

@cmungall cmungall commented Apr 1, 2021

Always use standard URLs.. maybe should use PURLs?

cmungall and others added 2 commits April 1, 2021 08:40
Always use standard URLs.. maybe should use PURLs?
@kltm
Copy link
Member

kltm commented Apr 1, 2021

@cmungall I'm curious about this. I don't think I would have considered http://geneontology.org/external2go/ontology/external2go/rhea2go to be a purl really--just a file on a site that we've passed forward through time. http://current.geneontology.org/ontology/external2go/rhea2go seems like a more logical place for the file, in with the rest of them and as part of a release package. Naturally, things like current and snapshot are not really purls either, but they are where we generally send people (and likely what our purls would generally resolve to).
It might be good to have a list of the resources that we have that are regarded as purls, so we (I) don't confuse them with "just" files, etc.? Also, do you think it might also be worth considering either rolling our own (purl.geneontology.org) for important things or using OBO? I think there can sometimes be confusion (with migrations, redirects, maintenance) when critical and normal paths get mixed.

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

Successfully merging this pull request may close these issues.

2 participants