-
Notifications
You must be signed in to change notification settings - Fork 74
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
884 fix patch #889
884 fix patch #889
Conversation
Something is wrong wait a moment.. |
Ok now |
|
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.
Thanks! I just see two things:
- Remove
FILTER ( ?value != oboInOwl:ObsoleteClass )
at line 32; a deprecated class should never be equivalent or disjoint withoboInOwl:ObsoleteClass
, only a subclass of it - The anonymous expression check is duplicated. The first one should be removed, and just use the one where you're binding the string as
?entity
.
I wanted to increase the readability of cases where the axiom in question is a simple existential restriction; if you check the FILTER() expressions in both cases, you will find that one of these "duplicates" looks for cases were the entity is named, and then can be printed as part of the robot command.. Does this make sense? |
Edit: I totally missed that one uses
|
Two suggestions @beckyjackson :
some-obsolete subclassOf Thing.
this error is so frequent, it will totally pollute the test.