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

Links to https://obofoundry.org do not resolve #680

Open
pgaudet opened this issue Feb 21, 2023 · 3 comments
Open

Links to https://obofoundry.org do not resolve #680

pgaudet opened this issue Feb 21, 2023 · 3 comments
Labels

Comments

@pgaudet
Copy link
Collaborator

pgaudet commented Feb 21, 2023

Hi,

This is to notify RO that there are 4 instances of links in RO that go to https://obofoundry.org

These do not resolve (give a 404 error)

image

Thanks, Pascale

@pgaudet pgaudet added the bug label Feb 21, 2023
@nlharris
Copy link
Contributor

Hi @pgaudet, can you provide an example of a link to RO that does resolve?
Also, where did you find those bad links?

@pgaudet
Copy link
Collaborator Author

pgaudet commented Feb 28, 2023

I found these in the ontology (RO-edit.owl in Protégé)

image

A link that works from RO-edit.owl can be found in the term 'occurs in': http://purl.obolibrary.org/obo/bfo.owl
image

Thanks, Pascale

@matentzn
Copy link
Contributor

Thank you @pgaudet - I personally don't think this is a problem - these are most likely ancient PURLS that were used prior to the normal OBO purls coming into existence. The oio:source property signifies that this "resource" was the source of the current RO relation - if it was rdfs:seeAlso, I would agree with you and recommend changing it to oio:source. All that said, this Information does not seem very important to me, and if others agree, it could be removed, or relegated to a comment.

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

No branches or pull requests

3 participants