Wikidata:Property proposal/exception to constraint (lexeme)
exception to constraint (lexeme)
editOriginally proposed at Wikidata:Property proposal/Generic
Not done
Description | lexeme that is an exception to the constraint, qualifier to define a property constraint in combination with P2302 |
---|---|
Data type | Lexeme |
Domain | property |
Example 1 | Breton Favereau dictionary lexeme ID (P11068)single-value constraint (Q19474404) except korrandon (L628622) |
Example 2 | Breton Favereau dictionary lexeme ID (P11068)single-value constraint (Q19474404) except kaoc'h (L627729) |
Example 3 | |
Example 4 | |
Example 5 | |
See also | exception to constraint (P2303) |
Motivation
editFor constraints, we need the equivalent of exception to constraint (P2303), but for lexemes. In particular, it is necessary for identifier properties used on lexemes (usually linking to dictionaries which often have a few weird exceptions like natural languages often have).
Notified participants of WikiProject property constraints
Cheers, VIGNERON (talk) 12:37, 1 October 2023 (UTC)
Discussion
edit- Support - of course, since "element type" properties cannot be used on lexemes, this would be necessary --Hsarrazin (talk) 16:13, 1 October 2023 (UTC)
- Support ―Eihel (talk) 16:28, 1 October 2023 (UTC)
- Makes sense. I'm only leaving out the vote because that will make it easier for me to create the property. Infrastruktur (talk) 18:40, 1 October 2023 (UTC)
- Support --Sannita - not just another it.wiki sysop 11:03, 2 October 2023 (UTC)
- Support AdamSeattle (talk) 16:52, 2 October 2023 (UTC)
- Support --99of9 (talk) 05:25, 3 October 2023 (UTC)
- Support --So9q (talk) 06:51, 4 October 2023 (UTC)
- Comment Please keep in mind that, until the necessary software changes (in WikibaseQualityConstraints and/or KrBot) have been made, this property will have no effect except to confuse users why it isn’t working. There should at the very least be an associated Phabricator task, and IMHO the property should only be created once the Wikidata team has committed to implementing the support in WBQC soon. I’d like to avoid a repeat of Wikidata:Property proposal/applies if regular expression matches. --Lucas Werkmeister (WMDE) (talk) 11:15, 5 October 2023 (UTC)
- @Lucas Werkmeister (WMDE): I figured that pretty much, thanks for the reminder and yes, indeed, we should absolutely Wait to hear from the dev team. Cheers, VIGNERON (talk) 18:36, 7 October 2023 (UTC)
- Strong support Useful for some Lexemes. Solaris5296 (talk) 20:28, 15 January 2024 (UTC)
- I'm marking this as Not done:
- This is not necessary for distinct-values constraint (Q21502410), you can add separator (P4155) identifier shared with lexeme (P9531) to the constraint, and then use identifier shared with lexeme (P9531) as a qualifier. You could probably do something similar for single-value constraint (Q19474404) too (perhaps using subject form (P5830)). There are probably still cases where this could be useful, but it needs better examples.
- We shouldn't create this until the developers are willing to add support for it. As was already pointed out, there should be a Phabricator ticket, and one has not yet been linked here.
- I don't think it's helpful to have proposals on hold indefinitely. If we still agree that we want a property by the time the developers are willing to work on it, a new proposal should have no problems being approved.
- - Nikki (talk) 05:32, 14 August 2024 (UTC)