Property talk:P22

From Wikidata
Jump to navigation Jump to search

Documentation

father
male parent of the subject. For stepfather, use "stepparent" (P3448)
Representsfather (Q7565)
Data typeItem
Template parameter|parents= in w:Template:Infobox person
Domain
According to statements in the property:
human (Q5), sibling group (Q16979650), fictional character (Q95074), mythical character (Q4271324), animal (Q729), human who may be fictional (Q21070568) and deity (Q178885)
When possible, data should only be stored as statements
Allowed valuesperson (Q215627) / fictional character (Q95074) / mythical character (Q4271324):male (Q6581097) / male organism (Q44148) (note: this should be moved to the property statements)
ExampleJane Fonda (Q41142)Henry Fonda (Q19155)
Sveinn Björnsson (Q207206)Björn Jónsson (Q879667)
Indira Gandhi (Q1149)Jawaharlal Nehru (Q1047)
Eros (Q121973)Ares (Q40901) and Zephyrus (Q467515)
daughter of Adrian II (Q22348311)Adrian II (Q173995)
Michael Douglas (Q119798)Kirk Douglas (Q104027)
Felipe VI of Spain (Q191045)Juan Carlos I (Q19943)
Robot and gadget jobsDeltaBot does the following jobs: The consistency check gadget (see code) checks if the linked objects are linking back to the analyzed page as child (asymmetric reciprocal relations), but does currently not discover if father or mother links are missing from the analyzed page to objects that are linking to it as child.
Tracking: sameno label (Q42533250)
Tracking: usageCategory:Pages using Wikidata property P22 (Q22913739)
See alsomother (P25), relative (P1038), godparent (P1290), stepparent (P3448)
Lists
Proposal discussionProperty proposal/Archive/1#P22
Current uses141,204
Search for values
[create] Create a translatable help page (preferably in English) for this property to be included here
Conflicts with “instance of (P31): Wikimedia disambiguation page (Q4167410), family name (Q101352), male given name (Q12308941), female given name (Q11879590), unisex given name (Q3409032), given name (Q202444), year (Q577): this property must not be used with the listed properties and values. (Help)
List of this constraint violations: Database reports/Constraint violations/P22#Conflicts with P31, hourly updated report, SPARQL, SPARQL (new)
Property “sex or gender (P21): male (Q6581097), male organism (Q44148), transgender male (Q2449503), cisgender male (Q15145778)” declared by target items of “father (P22): If [item A] has this property with value [item B], [item B] is required to have property “sex or gender (P21): male (Q6581097), male organism (Q44148), transgender male (Q2449503), cisgender male (Q15145778)”. (Help)
Exceptions are possible as rare values may exist.
List of this constraint violations: Database reports/Constraint violations/P22#Target required claim P21, SPARQL, SPARQL (new)
Inverse property of “child (P40):
if [item A] has this property (father (P22)) linked to [item B],
then [item B] should also have property “child (P40)” linked to [item A]. (Help)
Exceptions are possible as rare values may exist.
List of this constraint violations: Database reports/Constraint violations/P22#Inverse, SPARQL, SPARQL (new)
Type “human (Q5), sibling group (Q16979650), fictional character (Q95074), mythical character (Q4271324), animal (Q729), human who may be fictional (Q21070568), deity (Q178885): element must contain property “instance of (P31)” with classes “human (Q5), sibling group (Q16979650), fictional character (Q95074), mythical character (Q4271324), animal (Q729), human who may be fictional (Q21070568), deity (Q178885)” or their subclasses (defined using subclass of (P279)). (Help)
Exceptions are possible as rare values may exist.
List of this constraint violations: Database reports/Constraint violations/P22#Type Q5, Q16979650, Q95074, Q4271324, Q729, Q21070568, Q178885, SPARQL, SPARQL (new)
Item “sex or gender (P21): Items with this property should also have “sex or gender (P21)”. (Help)
Exceptions are possible as rare values may exist.
List of this constraint violations: Database reports/Constraint violations/P22#Item P21, search, SPARQL, SPARQL (new)
Value type “person (Q215627), fictional character (Q95074), mythical character (Q4271324), animal (Q729), human who may be fictional (Q21070568): This property should use items as value that contain property “instance of (P31)”. On these, the value for instance of (P31) should be an item that uses subclass of (P279) with value person (Q215627), fictional character (Q95074), mythical character (Q4271324), animal (Q729), human who may be fictional (Q21070568) (or a subclass thereof). (Help)
Exceptions are possible as rare values may exist.
List of this constraint violations: Database reports/Constraint violations/P22#Value type Q215627, Q95074, Q4271324, Q729, Q21070568, SPARQL, SPARQL (new)
Qualifiers “type of kinship (P1039), nature of statement (P5102), sourcing circumstances (P1480): this property should be used only with the listed qualifiers. (Help)
Exceptions are possible as rare values may exist. Known exceptions: Eros (Q121973)
List of this constraint violations: Database reports/Constraint violations/P22#Allowed qualifiers, SPARQL, SPARQL (new)
Scope is: the property must be used by specified way only (Help)
Exceptions are possible as rare values may exist.
List of this constraint violations: Database reports/Constraint violations/P22#scope, SPARQL (new)
Contemporaries:
if [item A] has this property (father (P22)) linked to [item B],
then [item A] and [item B] have to coincide or coexist at some point of history. (Help)
Exceptions are possible as rare values may exist. Known exceptions: John I of France (Q8404), Alexander IV of Macedon (Q207847), Agrippa Postumus (Q325906), Ladislaus the Posthumous (Q116382), Przemysł II (Q54017), Theobald I of Navarre (Q314562), Baldwin V of Jerusalem (Q345687), Henry VII (Q675493), Sebastian of Portugal (Q272899), Isaac Newton (Q935), Caroline Matilda of Great Britain (Q57668), Jonathan Swift (Q41166), Andrew Jackson (Q11817), Henri, Count of Chambord (Q88851), Alfonso XIII of Spain (Q18363), Tomasz Szarota (Q2440511), Bill Clinton (Q1124)
List of this constraint violations: Database reports/Constraint violations/P22#Contemporary, SPARQL (new)
Single value: this property generally contains a single value. (Help)
Exceptions are possible as rare values may exist. Known exceptions: Q302, Q7203, Q8666, Q9324, Q128267, Q718210, Q1265711, Q1279924, Q4778707, Q6790050, Q7166519, Q10941912, Q165938, Q2307, Q33477, Q35500, Q58779, Q62024, Q77822, Q79015, Q128576, Q121973, Q498007, Q15933921, Q486308, Q983266, Q774772, Q14621389, Q7643821, Q2428427, Q4111541
List of this constraint violations: Database reports/Constraint violations/P22#Single value, SPARQL, SPARQL (new)
Pictogram voting comment.svg Father was born after his child was born
birth date of person A is after birth date of person B (Help)
Violations query: SELECT * { { SELECT ?item WHERE { ?item wdt:P22 ?item2 . ?item p:P569/psv:P569 ?birth1_node . ?birth1_node wikibase:timeValue ?birth1 . ?birth1_node wikibase:timePrecision "11"^^xsd:integer . ?item2 p:P569/psv:P569 ?birth2_node . ?birth2_node wikibase:timeValue ?birth2 . ?birth2_node wikibase:timePrecision "11"^^xsd:integer . FILTER (?birth1 < ?birth2) } } }
List of this constraint violations: Database reports/Complex constraint violations/P22#Father was born after his child was born
Pictogram voting comment.svg People that are both father and mother
(Help)
Violations query: SELECT DISTINCT ?item WHERE { ?item ^wdt:P22 []; ^wdt:P25 [] }
List of this constraint violations: Database reports/Complex constraint violations/P22#People that are both father and mother
Pictogram voting comment.svg For stepfathers, use "stepparent"
use stepparent (P3448) not father (P22) for stepfathers (Help)
Violations query: SELECT ?item ?itemLabel ?value ?valueLabel ?pq ?pqLabel WHERE { VALUES ?pq { wd:Q1282201 wd:Q19822352 } ?item p:P22 [ps:P22 ?value; pq:P1039 ?pq ] ; wdt:P31 wd:Q5 SERVICE wikibase:label { bd:serviceParam wikibase:language "[AUTO_LANGUAGE],en". } }
List of this constraint violations: Database reports/Complex constraint violations/P22#For stepfathers, use "stepparent"


This property is being used by:

Please notify projects that use this property before big changes (renaming, deletion, merge with another property, etc.)

Entity being their own ancestor[edit]

Duke Huai of Qin (Q553786)'s father's father's father's father's father appears to be Duke Huai of Qin (Q553786) himself, according to the items. Presumably, this is an error. Would it be possible to add a constraint to this property so that situations like this are easier to identify? --Yair rand (talk) 09:34, 15 January 2014 (UTC)

Merging[edit]

I've proposed merging this with mother (P25). Please leave comments at Wikidata:Requests for comment/Merging relationship properties. Andrew Gray (talk) 20:55, 24 August 2015 (UTC)

grandfather property[edit]

Can a property be added for grandfather? Ping me back. Cheers! {{u|Checkingfax}} {Talk} 11:22, 13 January 2016 (UTC)

Such a property would be actively harmful, in my opinion, for workload and therefore data consistency reasons. The grandfather is easily queried, using appropriate queries. --Srittau (talk) 16:21, 13 January 2016 (UTC)

Examples[edit]

I reduced the number of examples to two: one for a real persons and one for a fictional person. We don't need multiple examples that all just say the same thing. --Srittau (talk) 20:31, 2 February 2016 (UTC)

Maybe someone could also add a racehorse, so we have all three allowed types as examples. --Srittau (talk) 20:32, 2 February 2016 (UTC)
  • More samples are generally better, unless they all illustrate the same.
    The Icelandic one was has the advantage of illustrating patronymic naming. Maybe we could add one with several fathers as well.
    --- Jura 07:59, 3 February 2016 (UTC)
    • In this case all examples illustrated the same. This property does not need to "illustrate patronymic naming" or any naming convention, because this is not a Wikipedia article about naming conventions. --Srittau (talk) 13:35, 3 February 2016 (UTC)
      • Normally a property has just one use, so all sample are somehow the same. I think we should have some obvious samples (as the Jane Fonda one to mid-aged Americans) and some less obvious ones.
        I think your limitation to the Apollo sample is problematic. Why didn't you choose Q4649 as father?
        --- Jura 13:44, 3 February 2016 (UTC)
        • I didn't change that example. If you think another example would be better suited instead, go ahead and change it. --Srittau (talk) 14:59, 3 February 2016 (UTC)
          • ✓ Done I completed the samples.
            --- Jura 16:58, 3 February 2016 (UTC)
          • Not sure if Apollo (Q37340) is a useful sample at all (see Talk:Q37340). Finally, I think it should be removed from here.
            --- Jura 05:42, 9 February 2016 (UTC)

Single value ?[edit]

There are many examples of people that have several fathers, including

  • those persons that have been adopted, or after their mother divorced and were remarried with a man that became also legally a new father: date qualifiers could disambiguate these cases that are not errors, but one is generally the "genetic" father, the others are "adopting fathers".
  • in real life today with homosexual male parents (they are "co-fathers"): a qualifier could indicate that fact "co-father".
  • for persons whose father is not known precisely but is cited differently according to old historical sources: a qualifier could state this "uncertain" fact but another qualifier should indicate the source.
  • or because of mythological reasons: originally these were real persons, but later they gained the rank of god/goddess or children of god/goddess with a mythological or religious father (e.g. with J.C), these are not the same kinds of "fathers".
  • or because of another mythological reason: gods/goddesses also have different mythological fathers depending on traditions (e.g. Greek and Roman gods), or because mythology allows them to be born several times.

In summary we should have some qualifiers (for uncertain sources), but it would be preferable to have some other classes (not derived classes) for "adopting father", "co-father", "mythological or religious father", and allow those people to have instances of several of these classes (but still only one instance of the "father" class), except if there's an "uncertain" qualifier

As those properties are inversible, these would also require the distinction of (natural) "child" with "adopted child" and "co-child" (even if by law in many countries they have now the same rights as natural children), and with "religious or mythological child" (all of them possibly with an "uncertain/probable" qualifier, possibly completed with another qualifier giving at least one source, such as "according to: <Person name>", or the tradition of this fatherhood assertion, such as "according to: Roman mythology", "according to: Greek mythology").

All the remaining conflicts on "single value" would need to be solved by reclassing the father types, and adding enough disambiguating properties.

All this about fathers, is also true for mothers (and their own children), or with brothers/sisters. and other family ranks. Verdy p (talk) 02:56, 4 April 2016 (UTC)

And there are similar exceptions about sex gender (transgender people can change their sex during life and still have (natural or adopted) children: are they "fathers" or "mothers" ?

We'll have soon really too many exceptions to these familial relation constraints: we won't be able to list them all as exceptions, except by creating specific classes for these special cases. Verdy p (talk) 03:09, 4 April 2016 (UTC)

English alias "is child of"[edit]

The alias "child of" leads to property suggestions frequently suggesting "father" instead of child (P40) when typing "child". Thus I changed the alias to "is child of". It's a known issue, but apparently the devs can't solve it.
--- Jura 08:06, 21 May 2016 (UTC)

"Fathers"[edit]

How does it reflect the fact that the father of a person is not precisely known? For example, it hesitates between two or more candidates. --Romulanus (talk) 09:01, 22 May 2017 (UTC)