Property talk:P6607
Documentation
qualifier to provide details on the function or purpose of a property constraint on a given property
Data type | Monolingual text | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Domain | property namespace: statements for property constraint (note: this should be moved to the property statements) | ||||||||||||
Usage notes | Schreibe einen oder mehrere ganze Sätze und beende diese mit jeweils einem Satzpunkt. | ||||||||||||
See also | replacement property (P6824), syntax clarification (P2916), Wikidata usage instructions (P2559), replacement value (P9729) | ||||||||||||
Lists | |||||||||||||
Proposal discussion | Proposal discussion | ||||||||||||
Current uses |
|
List of violations of this constraint: Database reports/Constraint violations/P6607#Scope, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P6607#Entity types
Display in interface message
[edit]See phab:T219037. --- Jura 11:12, 28 May 2019 (UTC)
Additional info
[edit]See Property_proposal/replacement_property. --- Jura 11:12, 28 May 2019 (UTC)
Suggestion: Write constraint clarifications as full sentences
[edit]
Constraint clarifications are currently written in a variety of styles (query): they may be a sentence fragment (use a more specific item
), fragments of more than one sentence (unlikely to be the actual given name. Add exceptions if needed
), a full sentence without a full stop (Consider using P123 (publisher) in references
), a full sentence with a full stop (There can be several values, but they should differ by one of these qualifiers.
), several full sentences (Non mandatory constraint. Add only title of work in its original language. Multilingual works may have several.
), or something else. The Wikidata development team at WMDE will soon work on showing constraint clarifications in the constraint violation UI (T219037), and we plan to show the clarification as a separate paragraph below the usual violation message; for this reason, we suggest that there should be a recommendation to write constraint clarifications as one or more full sentences, and that existing clarifications should be updated to match this style where possible. Do you agree?
Notified participants of WikiProject property constraints Lucas Werkmeister (WMDE) (talk) 12:13, 27 January 2023 (UTC)
- Yes, one or more full sentences, and existing clarifications should be updated to one or more full sentences. Thadguidry (talk) 12:55, 27 January 2023 (UTC)
- I agree. People will see when constraint clarification messages are not specific enough and improve them so such improvement should happen naturally. Lectrician1 (talk) 15:14, 27 January 2023 (UTC)
- I agree that one or more full sentences is a good standard. I would prefer wikitext over normal text, so that it would be "Use unknown value Help instead of anonymous when the author is unknown." in the example. ChristianKl ❪✉❫ 15:36, 27 January 2023 (UTC)
- Support I agree that we need to standardize the way we write constraints. Full or longer sentences could be useful. John Samuel (talk) 19:04, 27 January 2023 (UTC)
- Agreed. PKM (talk) 05:08, 28 January 2023 (UTC)
- Support. Is there any indication yet on whether templates such as P and Q would be interpreted when displayed to users? Currently the references to items and properties in these constraint clarifications is highly inconsistent. Dhx1 (talk) 21:12, 29 January 2023 (UTC)
- Support Great to hear of this development. --99of9 (talk) 22:38, 29 January 2023 (UTC)
- I've just gone through and updated all the cases on properties with country=Australia. --99of9 (talk) 23:28, 29 January 2023 (UTC)