Using the generic algorithm to generate (logical) explanations for why is owl:Nothing a subclass of a class expression in the DL Query tab starts an infinite process that the user will need to interrupt in order to regain control, and returns a long list of results that are very difficult to interpret.
I would suggest that we treat owl:Nothing as a special case, and generate a "smarter", i.e. a more meaningful, explanation for why is owl:Nothing listed among the subclasses of any given class expression (e.g. "because owl:Nothing is the bottom class (and it is equal to the empty set) and therefore it is subclass of every class").
Using the generic algorithm to generate (logical) explanations for why is owl:Nothing a subclass of a class expression in the
DL Query
tab starts an infinite process that the user will need to interrupt in order to regain control, and returns a long list of results that are very difficult to interpret.I would suggest that we treat
owl:Nothing
as a special case, and generate a "smarter", i.e. a more meaningful, explanation for why isowl:Nothing
listed among the subclasses of any given class expression (e.g. "because owl:Nothing is the bottom class (and it is equal to the empty set) and therefore it is subclass of every class").