Jump to content

Property talk:P13146

Add topic
From Wikidata
Latest comment: 6 months ago by IagoQnsi in topic Single-value constraint

Documentation

image of this person doing their job
picture of a person in action, especially for a sportsperson, visual artist, musican, actor. P18 is normally used for portraits
Data typeCommons media file
Domainhuman (Q5)
ExampleChiara Kreuzer (Q5331554)20190226 Seefeld SJ 4720.jpg
Jakob Eiksund Sæthre (Q87721657)20200222 FIS NC COC Eisenerz PRC HS109 Men Jakob Eiksund Saethre 850 4504.jpg
María Ólafsdóttir (Q19264382)20150516 ESC 2015 Maria Olafs 9813.jpg
Cornelia Kreuter (Q87345351)20190315 Dancing Stars 1100.jpg
Lars Ulrich (Q106193)Lars Ulrich live in London 2008-09-15.jpg
Angela Merkel (Q567)President Joe Biden meets with German Chancellor Angela Merkel at the G7 Summit.jpg
Formatter URLhttps://commons.wikimedia.org/wiki/File:$1
Embed URLhttps://commons.wikimedia.org/wiki/File:$1
Lists
Proposal discussionProposal discussion
Current uses
Total87
Main statement7990.8% of uses
Qualifier66.9% of uses
Reference22.3% of uses
[create Create a translatable help page (preferably in English) for this property to be included here]
Single best value: this property generally contains a single value. If there are several, one would have preferred rank (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P13146#single best value, SPARQL
Link to Commons namespace “File”: this property should contain a well-formed link to an existing page on Wikimedia Commons. (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P13146#Commons link
Allowed entity types are Wikibase item (Q29934200): the property may only be used on a certain entity type (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P13146#Entity types
Scope is as main value (Q54828448): the property must be used by specified way only (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P13146#Scope, SPARQL
Type “human (Q5): item must contain property “instance of (P31)” with classes “human (Q5)” or their subclasses (defined using subclass of (P279)). (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P13146#Type Q5, SPARQL
Item “occupation (P106): Items with this property should also have “occupation (P106)”. (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P13146#Item P106, search, SPARQL

Single-value constraint

[edit]

I've removed the single-value constraint that was on this object and replaced it with a single-best-value constraint. There certainly exists more than one photo for most people doing most jobs; there is a need to make sure we have a best photo, but no need to prevent more photos from being added.

I also added a separator of occupation (P106) to the single-best-value constraint. This is needed because there are many people who have had multiple occupations that they are known for; for example, an athlete who later becomes a coach. You may want to retrieve a photo of them playing for a page about their playing career, and likewise for their coaching career. If you just want to retrieve a general photo of them at work and aren't concerned with which job it is, then any of the 'preferred rank' photos should be good enough.

So those are my thoughts behind those changes; I welcome discussion though! –IagoQnsi (talk) 23:29, 7 August 2025 (UTC)Reply