Drag and drop should not add subclass axioms where owl:Thing is in the superclass position

[csnyulas]

From the SC:

In the class, somebody started by creating FoodStuff as a subclass of GroceryItem and NutritionalInformation as a subclass of FoodStuff. She fixed the problem by dragging and dropping them to be subclasses of OWL:Thing. Protege created subclass axioms of FoodStuff SubclassOf OWL:Thing and NutritionalInformation SubclassOf OWL:Thing. Her axiom counts therefore are different from what the instructor got. I see the same behavior with property hierarchy as well. Drag-and-drop a subproperty to the top creates a SubpropertyOf owl:topObjectProperty.

(reported by Samson)

[csnyulas]

Also from Samson:

I think the main thing is that Protege’s behavior should be consistent. If creating new classes at root level doesn’t create SubClassOf OWL:Thing, then drag-and-drop shouldn’t create the subclass axiom.

I see the same behavior with property hierarchy as well. Drag-and-drop a subproperty to the top creates a SubpropertyOf owl:topObjectProperty.

It’s not wrong to have such axioms, but they make axiom count metrics dependent on the history of a user’s interactions with the tool, and that’s not desirable.