You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
From an email by Pavel Klinov which was posted to the mailing list:
I've noticed that when a user clicks on a class (on the Classes tab)
and if the option "Class members" is set in the "Displayed Inferences"
configuration, Protege 4.3 issues a call
OWLReasoner.getInstances(class_expression, *false*) to the reasoner.
This means that all inferred instances, direct and indirect, are
requested. I wonder if that is really necessary when browsing the
class hierarchy since it can quickly get very slow on
ontologies with large ABox (or even large TBox, if the reasoner first
goes through all subclasses).
I searched the archive and found this:
https://mailman.stanford.edu/pipermail/p4-feedback/2010-October/003321.html
so it seems like the problem of retrieving indirect instances has been
recognized. So perhaps it's better to always request only direct ones?
Or at least converge to some consistent behaviour.
The text was updated successfully, but these errors were encountered:
From an email by Pavel Klinov which was posted to the mailing list:
The text was updated successfully, but these errors were encountered: