If a property requires a certain statement on an item, and that statement exists but is deprecated… should that be reported as a constraint violation? I’m not sure, because it seems to me that there’s no good fix for this violation (there’s probably a good reason the statement is deprecated, and undeprecating it or adding a normal-rank copy is probably not the right thing to do).
|Open||None||T167653 Consider ranks in constraint checks|
|Declined||None||T170398 Ignore deprecated statements when checking “inverse”, “symmetric”, “item requires claim”, and “value requires claim” constraints?|
With enough optimization by hand, it’s possible. This query finds “item requires claim” constraints only satisfied by a deprecated statement (2 results); this query finds “inverse” and “value requires claim” constraints only satisfied by a deprecated statement (83 results); and this query finds “symmetric” constraints only satisfied by a deprecated statement (0 results – perhaps I got the query wrong).