Description: a constraint that bans values of a certain type

Use: Many of the none-of constraints on "instance of" ban items of the same class. Because there is no constraint to ban items by class, items are individually added and significantly inflate the number of property constraints and their qualifiers. Using a "none-of value-type constraint" could simplify banning "qualities" - items that are supposed to be used on other describing properties and not "instance of".

Example use:

occupations are not supposed to be used with "instance of", so "instance of" should have this constraint:

• none-of value-type constraint
  • class: occupation
  • relation: instance of
  • replacement property: occupation
  • replacement value: human

This proposal was also posted here.