Topic on User talk:Mbch331/Structured Discussions Archive 1

The problem is that the schematic property is not permitted on Wikibase senses, and senses are not valid as exception constraints either. So if you use an image that has "diagram" in it even for a lexicographic sense that simply means "diagram," then you end up with an unresolveable constraint violation on lexeme senses. I don't understand the purpose of your reversion to this end. --~~~~

My reversion was because constraint scope (P4680) wasn't allowed as a qualifier there. It caused a constraint violation. And that caused this.

Hmm well that seems like a problem with the way the constraint violations are set up for format constraint, or suggests that format constraint isn't appropriate at all on the image property. At the page Help:Property constraints portal/Format, it seems clear that constraint scopes are supposed to be allowed in combination with format constraints:

> If no constraint scope (P4680) is specified, this constraint is checked everywhere.

Maybe this is an error with the constraint bot? See User_talk:Ivan_A._Krestinin#multi-value_constraint_and_constraint_scope: --Middle river exports (talk) 09:18, 26 July 2022 (UTC)

It is definitely a problem with Ivan's bot. Wikidata's constraint system supports constraint scope (P4680) anywhere. Ivan could implement support in the bot, make the bot ignore the qualifier or skip constraints with that qualifier so that the constraints report is still generated, but, for whatever reason, they seem stubbornly determined to not change the bot's behaviour. constraint scope (P4680) was created 4 and a half years ago, they were aware of the problem at least three years ago and it was brought to their attention again a year ago. It seems unlikely that they're going to fix it, and their code isn't public either, so I can only recommend finding alternatives whenever possible (saved SPARQL, PetScan or Quarry queries, SPARQL queries turned into reports via the complex constraint template or Listeria, etc).