-
Notifications
You must be signed in to change notification settings - Fork 4
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
CMO completely broken right now due to parsing issues #13
Comments
As suggested we have added another file in OWL functional format .ofn. The files is available here: https://download.rgd.mcw.edu/ontology/clinical_measurement/clinical_measurement.ofn Please let us know if that fixes your problem. PS. The .ofn file is generated from obo file just like mentioned above :-) |
@tutajm sorry I should have made myself clearer - we do not need a OFN release. I merely provided a test for you to run so you can fix the broken parts of CMO. What matters that all the errors in the latest CMO release are fixed, and you can test this using:
CMO.owl should definitely be RDF/XML syntax, not OFN. But, from what I can see, the OFN file looks great! I spot-checked for errors and it seems all working now. THANK YOU! |
The files http://purl.obolibrary.org/obo/cmo.owl and http://purl.obolibrary.org/obo/cmo.obo are very old: from Feb 2019. Since then, the ontology has been updated numerous times. The latest version of cmo ontology (updated weekly) you can always find here: Now I'm trying to figure out how to update cmo ontology at purl.obolibrary.org. |
Change these two rows: https://github.com/OBOFoundry/purl.obolibrary.org/blob/master/config/cmo.yml#L7 ! |
Created a pull-request to update cmo.yml. Thanks for help! |
Hello!
Right now CMO cannot be processed at all:
As a minimum, please try to use ROBOT with the OWL release file (which is the most important one):
Or open it with Protege!
The text was updated successfully, but these errors were encountered: