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

Ontologies that don't resolve #18

Closed
simonjupp opened this issue Aug 6, 2015 · 5 comments
Closed

Ontologies that don't resolve #18

simonjupp opened this issue Aug 6, 2015 · 5 comments
Labels
ontology metadata Issues related to ontology metadata

Comments

@cmungall
Copy link
Contributor

cmungall commented Aug 6, 2015

@dosumis do you recall why we made the purl for dpo be http://purl.obolibrary.org/obo/fbcv/dpo.owl

We could make this a subset of the main http://obofoundry.github.io/ontology/fbcv.html - but we decided to mark this as obsolete at some point

It's probably too much churn to change this now, I suggest we have http://obofoundry.github.io/ontology/dpo.html as its own top level and live with the fact the ontology and class purls aren't derived in exactly the same way

@dosumis
Copy link
Contributor

dosumis commented Aug 6, 2015

@dosumis do you recall why we made the purl for dpo be http://purl.obolibrary.org/obo/fbcv/dpo.owl

Probably because we never got around to making a foundry request for dpo. Puting it under fbcv made sense as dpo is a subontology of fbcv and we didn't want the churn at FlyBase caused by splitting it out. I guess there's no reason not to put in a foundry request http://purl.obolibrary.org/obo/dpo.owl . We could keep the old PURL too. CC @mmc46

cmungall added a commit that referenced this issue Aug 6, 2015
@cmungall cmungall added the ontology metadata Issues related to ontology metadata label Aug 8, 2015
@cmungall cmungall added this to the v1.0 release milestone Aug 8, 2015
cmungall added a commit that referenced this issue Aug 17, 2015
cmungall added a commit that referenced this issue Aug 17, 2015
@cmungall
Copy link
Contributor

Note to site developers: you can now do the following:

make valid-purl-report.txt

to validate all product purls (ie the canonical product for an ontology project, as well as each individual registered product)

@dosumis
Copy link
Contributor

dosumis commented Sep 22, 2015

Why the berkeleybop URL for dpo?

On Tue, Sep 22, 2015 at 1:49 AM, Chris Mungall notifications@github.com
wrote:

http://www.berkeleybop.org/ontologies/dpo.owl
registered product is http://purl.obolibrary.org/obo/fbcv/dpo.owl
resolves
http://www.berkeleybop.org/ontologies/kisao.owl
http://purl.obolibrary.org/obo/kisao.owl resolves
(but note the ontologyID is not a purl. Consider deregister?
http://www.berkeleybop.org/ontologies/lipro.owl
product deregistered

http://www.berkeleybop.org/ontologies/nmr.owl
obsolete
http://www.berkeleybop.org/ontologies/ovao.owl
typo. Entry removed

http://www.berkeleybop.org/ontologies/resid.owl
obsolete
http://www.berkeleybop.org/ontologies/rnao.owl
works
http://www.berkeleybop.org/ontologies/xso.owl
typo. Removed.


Reply to this email directly or view it on GitHub
#18 (comment)
.

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

No branches or pull requests

3 participants