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
Comments
@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 |
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 |
Note to site developers: you can now do the following:
to validate all product purls (ie the canonical product for an ontology project, as well as each individual registered product) |
|
Why the berkeleybop URL for dpo? On Tue, Sep 22, 2015 at 1:49 AM, Chris Mungall notifications@github.com
|
These ontologies don't resolve from the yaml file
http://www.berkeleybop.org/ontologies/dpo.owl
http://www.berkeleybop.org/ontologies/kisao.owl
http://www.berkeleybop.org/ontologies/lipro.owl
http://www.berkeleybop.org/ontologies/nmr.owl
http://www.berkeleybop.org/ontologies/ovao.owl
http://www.berkeleybop.org/ontologies/resid.owl
http://www.berkeleybop.org/ontologies/rnao.owl
http://www.berkeleybop.org/ontologies/xso.owl
The text was updated successfully, but these errors were encountered: