Wikidata:Property proposal/significant person
Jump to navigation
Jump to search
significant person[edit]
Originally proposed at Wikidata:Property proposal/Person
| Description | person linked to the item in any possible way |
|---|---|
| Data type | Item |
| Domain | human (Q5), object (Q488383) or whatever else |
| Allowed values | human (Q5) |
| Example | |
| See also | significant event (P793) |
- Motivation
We have significant event (P793) for X-to-event relations but do not have an equivalent for people. I suggest we create this so that we can document any kind of relation between someone and someone else or something else. Of course, you should keep using more specific existing properties like father (P22), killed by (P157) or musical conductor (P3300) when possible. This is only for more subtle relations when no other X-to-person property is available. Thierry Caro (talk) 09:10, 23 October 2016 (UTC)
- Discussion
Support But the description should specify that it has to be used with a qualifier. ChristianKl (talk) 08:51, 29 October 2016 (UTC)- Support Valentina.Anitnelav (talk) 19:21, 2 November 2016 (UTC)
Comment some time ago, we had proposals for "friend of" and "enemy of". This got rejected. How can we avoid that this gets used for it instead? For items on 20th/21st century people, this could create potential problems. Maybe for these, this property shouldn't have any statements without references.
--- Jura 10:57, 11 November 2016 (UTC)
- If a certain relationship between two people is both relevant and documented, it should certainly be stored here, whatever was said about having a specific property just for that. Thierry Caro (talk) 20:01, 12 November 2016 (UTC)
- Support. CC0 (talk)
- Support. Beeyan (talk) 05:33, 13 November 2016 (UTC)
- @Thierry Caro, Valentina.Anitnelav, CC0, Beeyan, Jura1:
Done ChristianKl (talk) 19:39, 15 November 2016 (UTC) - Comment This creation makes me feel unconfortable. This makes another option to substitute to "any" property and makes pretty much any subsequent relationship modelable with this bypassing the property creation step. This create maintenance tasks without any way provided to maintain this - if the item mapped to a relation is used instead of the correct property there is two way to express the relation. The "key" (?) person is left to common sense ... This is also hard to exploit as similar concept can be used as very close meaning but still with different items ... this can very soon become out of control. author TomT0m / talk page 20:51, 15 November 2016 (UTC)
