| Lucas_Werkmeister_WMDE added a comment. |
The data model would be fairly simple – a single triple, as I already mentioned.
wds:Q42-45E1E647-4941-42E1-8428-A6F6C848276A wikibase:hasViolationForConstraint wds:P463-6F6E17F0-2650-4835-9250-2F893C77B301.
Both the subject and the object are statement nodes. The exact name of the predicate is still up for discussion. To keep the data model simple, I think we can squash constraint violations for the main snak, qualifiers, and references all into the same predicate (which is why I’m proposing “has violation” and not “violates” now), and people can see where exactly the violation is when they visit the entity.
Example query (the one in the task description: mandatory constraint violations for “IMDb ID” on actors living in Germany born before 1945):
SELECT ?item ?itemLabel ?constraintTypeLabel WHERE { wd:P345 p:P2302 ?constraint. ?constraint ps:P2302 ?constraintType; pq:P2316 wd:Q21502408. ?item wdt:P31 wd:Q5; wdt:P106 wd:Q33999; wdt:P551/wdt:P17 wd:Q183; wdt:P569 ?dob. FILTER(?dob < "1945-01-01"^^xsd:dateTime) ?item p:P345/wikibase:hasViolationForConstraint ?constraint. SERVICE wikibase:label { bd:serviceParam wikibase:language "[AUTO_LANGUAGE],en". } }There are some more requested example queries in T172380: Query constraint violations with WDQS (I just made that task a parent task of this one).
Cc: Micru, Agabi10, Lucas_Werkmeister_WMDE, Gehel, Smalyshev, Jonas, Aklapper, Lahi, Gq86, Darkminds3113, GoranSMilovanovic, QZanden, EBjune, merbst, LawExplorer, Avner, FloNight, Xmlizer, jkroll, Wikidata-bugs, Jdouglas, aude, Tobias1984, Manybubbles, Mbch331
_______________________________________________ Wikidata-bugs mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs
