Wikidata talk:WikiProject property constraints

Latest comment: 7 days ago by SM5POR in topic A sense constraint for the parent lexeme
On this page, old discussions are archived after 60 days. An overview of all archives can be found at this page's archive index. The current archive is located at Wikidata talk:WikiProject property constraints/Archive 2.

add no-instances-of constraint edit

Currently instance of (P31) has a lot of none-of constraint (Q52558054) constraints that list instances of a class and replace the instance of (P31) link with a special link. For example various instances of studio album (Q208569) cause a replacement with the property form of creative work (P7937). This causes the constraints to be large and require updating whenever a new instance of the class is created. It seems to me that these constraints should instead use a constraint that uses the class directly, instead of its instances. This would be easier to create, easier to understand, and easier to update. https://www.wikidata.org/wiki/Wikidata:WikiProject_Ships is set in a way where it would be useful to have this new kind of constraint. There are thousands of instances of ship class (Q559026) like Olympic-class ocean liner (Q767166) that are not supposed to be used as values for instance of (P31) instead using vessel class (P289) but adding them all as a replacing none-of constraint would be very difficult, and new ship classes are created frequently. So a no-instances-of constraint would be very useful for ships. Is this the correct place to argue for the creation of a new constraint type, or is there some better place? Peter F. Patel-Schneider (talk) 15:57, 6 December 2023 (UTC)Reply

allowed units constraint (Q21514353) allowing all currencies edit

It looks necessary for now to enumerate all currencies allowed for various financial properties (eg. Property:P2769#P2302). How to allow all elements that are currency (Q8142) ? Louperivois (talk) 18:23, 21 December 2023 (UTC)Reply

@Louperivois,@Lokal Profil@FoeNyx,@Emu:Seems like a reasonable idea to me [(it has been discussedbefore), unfortunately I don't know either how to write
such a constraint. I tried adding a rule like [[d:Special:EntityPage/21514353} WITH PROPERTY (P2306) {P|21514353} WITH PROPERTY (P2306) {P]] [[Property:P2305]} {Q|P2305]} {Q (P2305]} {Q)]] but the property editor didn't provide me with a field to enter the value instance of (P31) as the value of property (P2306). --SM5POR (talk) 18:12, 5 February 2024 (UTC)Reply

Interpreting replacement property (P6824) and replacement value (P9729) in the same constraint edit

1. When a constraint has both replacement property (P6824) and replacement value (P9729), should those be interpreted as applying to the same replacement statement, or two separate statements?

2. What is the right way to make the correct interpretation clear? Two separate constraints whenever two replacement statements are intended? A constraint clarification (P6607) on every constraint that uses both replacement property (P6824) and replacement value (P9729)?

3. Have the answers to 1 and 2 been established by consensus, and written down somewhere?

Examples:

This query should show all constraints that have both replacement property (P6824) and replacement value (P9729). Swpb (talk) 15:21, 1 April 2024 (UTC)Reply

A sense constraint for the parent lexeme edit

  Notified participants of WikiProject property constraints

The newly created Duden sense ID (P12641) has a subject type constraint. But this is a property for lexeme senses and the constraint is meant to be applied to the associated lexeme. What can be done here?– Shisma (talk) 08:08, 19 April 2024 (UTC)Reply

@Shisma First of all I think this should preferrably be disccussed on [Property̜̙talkːP12641 the talk page corresponding to that property. Unfortunately,I seem to have forgot how to link to such pages,but I hope you can find it anyway.--̃-̃-̃-̃ SM5POR (talk) 15:10, 19 April 2024 (UTC)Reply
Return to the project page "WikiProject property constraints".