Wikidata:Property proposal/constraint clarification
constraint clarification[edit]
Originally proposed at Wikidata:Property proposal/Generic
| Description | qualifier to provide details on the function or purpose of a property constraint |
|---|---|
| Data type | Monolingual text |
| Domain | property namespace: statements for property constraint |
| Example 1 | item for this sense (P5137)property constraint (P2302)allowed-entity-types constraint (Q52004125) |
| Example 2 | season (P4908)property constraint (P2302)conflicts-with constraint (Q21502838) |
| Example 3 | Special:WhatLinksHere/Property:P2916&namespace=120 |
| Planned use | migration of statements from syntax clarification (P2916) |
Motivation[edit]
Split from syntax clarification (P2916), which was originally created as a qualifier "primarily" for format as a regular expression (P1793). As far as I can tell, the uses of syntax clarification (P2916) fall into three distinct categories:
- Qualification of format as a regular expression (P1793) (its original purpose)
- Qualification of property constraints (the purpose for which the new property is proposed; a separate property was previously rejected here)
- Qualification of random statements as a multi-purpose free text field (clearly a misuse)
The use of syntax clarification (P2916) for case (2), rather than a separate property, was suggested here by User:Thryduulf and implemented by User:Jura1, but I don't think that's a wise choice. In particular, the property covering case (1) should have property constraint (P2302)item-requires-statement constraint (Q21503247)
Discussion[edit]
Support David (talk) 05:11, 15 February 2019 (UTC)
Neutral P2916 has the advantage that it would also be displayed in the interface. Agree about (#3): I think we dropped the general comment field to avoid that specifically. :( --- Jura 16:45, 15 February 2019 (UTC)
- @Jura1: I’m not sure what interface you refer to, but as far as I’m aware WikibaseQualityConstraints only uses syntax clarification (P2916) for its original purpose (if defined on a format constraint, it’s used in the violation message). If a new constraint clarification property is added, I’m sure we can also display it on other constraint violations. --Lucas Werkmeister (WMDE) (talk) 14:36, 12 March 2019 (UTC)
- Interesting. I don't think there would be cases where syntax of a format constraint needs to be clarified in two different ways. So we could still use P2916 for all constraints. --- Jura 09:19, 16 March 2019 (UTC)
- Well, they’re different things in my opinion – constraint clarifications aren’t really about the syntax. And this has implications for the error message too: the current format constraint violation message uses the syntax clarification as in
The value for … should match
– this doesn’t work out well if the clarification is something like “use blah instead”. --Lucas Werkmeister (WMDE) (talk) 11:29, 18 March 2019 (UTC)6 hexadecimal digits
(regex:[0-9A-Fa-f]{6})
- Well, they’re different things in my opinion – constraint clarifications aren’t really about the syntax. And this has implications for the error message too: the current format constraint violation message uses the syntax clarification as in
- @Jura1: I’m not sure what interface you refer to, but as far as I’m aware WikibaseQualityConstraints only uses syntax clarification (P2916) for its original purpose (if defined on a format constraint, it’s used in the violation message). If a new constraint clarification property is added, I’m sure we can also display it on other constraint violations. --Lucas Werkmeister (WMDE) (talk) 14:36, 12 March 2019 (UTC)
![The value for image (335 years war locations.png) should match “Please use P242 (locator map) instead” (regex: [cannot be transcribed]).](/wiki/File:Format_constraint_with_constraint_clarification_as_syntax_clarification.png)
- I just found an actual example of this on Three Hundred and Thirty Five Years' War (Q1054482) – see the image on the side. The violation message is confusing because a constraint clarification is not something that the value could match or not match. --Lucas Werkmeister (WMDE) (talk) 11:08, 21 March 2019 (UTC)
Notified participants of WikiProject property constraints --Lucas Werkmeister (WMDE) (talk) 14:40, 12 March 2019 (UTC)
- Support ArthurPSmith (talk) 17:02, 21 March 2019 (UTC)
- @Swpb, ديفيد عادل وهبة خليل 2, Jura1, Lucas Werkmeister (WMDE):
Done ArthurPSmith (talk) 20:45, 22 March 2019 (UTC)
- @Swpb, ديفيد عادل وهبة خليل 2, Jura1, Lucas Werkmeister (WMDE), ArthurPSmith: for syntax clarification (P2916) I add some guidance now in the property description about how it's being used in the interface. Maybe we could do the same for this one, even if it isn't displayed now. Supposedly that guidance would vary by language. --- Jura 17:51, 1 April 2019 (UTC)