-
Notifications
You must be signed in to change notification settings - Fork 47
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
Ready to merge: Domain and range constraints #261
Conversation
cmungall
commented
Sep 26, 2018
•
edited
Loading
edited
- Adds multiple new domain and range constraints
- Brings in more external classes (still need to refactor import generation)
- Adding more obo foundry unique labels
- Adding additional metadata / AAs
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I looked at the changes to the Makefile and ran make
and make test
. There's a lot of noise but it seemed to work. Then I checked ro.owl
in Protege with ELK. Things look reasonable. The only significant problem I see is that GO_0004872 and GO_0048018 are under owl:Thing
without labels.
The Makefile just calls robot
for most things, which might not refer to the fetched robot.jar
. Would ./robot
be better?
I don't think the GO orphan issues were introduced with this PR, but this is a good time to fix this. robot: I've always used the robot on the path. We should switch the .travis.yml to use the odk docker container |
We keep the weaker D+R constraints in for EL purposes
…eneral 'anatomical structure' Broadening range for some developmental relations to AS. See obophenotype/uberon#1455