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
equivalentClass/subClassOf issues #180
Comments
Looks like #135 is the more relevant ticket What's your configuration - are you using a reasoner? |
Reasoner is off (havn't gotten nifstd into reasonable state yet). Configuration is essentially as seen here: https://github.com/SciCrunch/NIF-Ontology/blob/master/scigraph/make_yamls.sh |
In that case, this is expected (if undocumented) behavior. Although in principle we could implement a reasonerless relaxation step, Even if the ontology is messy, I'd recommend using Elk as part of the SG On 6 May 2016, at 18:04, Tom Gillespie wrote:
|
Additional note: It should not be related to #135 as it is only activated when this configuration type is specified. |
Adding the reasoner results in the following warning |
There's an option to remove disjointness and domain/range axioms prior to loading. These are usually the cause, and they don't really buy you much at the SciGraph level |
Do you happen to have the reference for that option on hand, or know where I can look? (I checked the Elk documentation but nothing jumped out at me). |
We have encountered unexpected behavior when dealing with some of our old defined classes.
In the definition of NIFNEURNT:nlx_neuron_nt_090803 here the equivalence statement is sufficient in Protege for NIFNEURNT:nlx_neuron_nt_090803 to be inferred as subClassOf NIFCELL:sao1417703748. However when looking at the scigraph output for a neighbors query with depth of 2 this relation does not appear. Running the query with relationshipType=equivalentClass set returns nothing (I think this is expected behavior?)
This seems to be related to #135 and #42 but I'm not entirely sure if it is the same issue.
The text was updated successfully, but these errors were encountered: