Property talk:P726

Latest comment: 1 year ago by PAC2 in topic French label

Documentation

candidate
person or party that is an option for an office in this election
Descriptionperson or party listed as an option for office in an election.
 Info This property is for use with elections to indicate the competing parties (political parties or individuals). In cases where where votes are for lists of candidates and where seats are apportioned, the item should be the party or list instead of individual candidates.
RepresentsPublic Speaker (Q19772737)
Data typeItem
Domainpublic election (Q40231), political campaign (Q847301), election campaign (Q11642595) or electoral result (Q19571328)
Allowed valuesperson or party (note: this should be moved to the property statements)
Usage notesqualify with votes received (P1111)
Example
(note: this information should be moved to a property statement; use property Wikidata property example (P1855), Wikidata property example for properties (P2271), Wikidata property example for lexemes (P5192), Wikidata property example for forms (P5193) or Wikidata property example for senses (P5977))
Tracking: usageCategory:Pages using Wikidata property P726 (Q26250046)
See alsosuccessful candidate (P991), votes received (P1111), candidacy in election (P3602), candidate number (P4243), running mate (P6149)
Lists
Proposal discussionProposal discussion
Current uses
Total119,301
Main statement112,24494.1% of uses
Qualifier7,0575.9% of uses
Search for values
[create Create a translatable help page (preferably in English) for this property to be included here]
Item “office contested (P541): Items with this property should also have “office contested (P541)”. (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/P726#Item P541, search, SPARQL
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/P726#Entity types
Scope is as main value (Q54828448), as qualifier (Q54828449): 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/P726#Scope, SPARQL
This property is being used by:

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

Qualifier object has role (P3831) should have a value of the class candidate status (Q26696044)
FIXME: Sample values: nominated candidate (Q26696038), candidate featured in polls (Q26696048); sample item: Q22676594#P726 (Help)
Violations query: SELECT ?item ?value ?qualifiervalue WHERE { ?item p:P726 ?statement . ?statement ps:P726 ?value . ?statement pq:P3831 ?qualifiervalue . MINUS { ?statement pq:P3831 ?qualifiervalue . ?qualifiervalue wdt:P31 wd:Q26696044 } }
List of this constraint violations: [[Wikidata:Database reports/Complex constraint violations/P726#Qualifier object has role (P3831) should have a value of the class candidate status (Q26696044)|Database reports/Complex constraint violations/P726#Qualifier object has role (P3831) should have a value of the class candidate status (Q26696044)]]

Discussion edit

Do we need "candidature" items ? edit

See the discussion Do we need "candidature" items ?.--Dom (talk) 05:59, 27 November 2013 (UTC)Reply

Wrong approach edit

Hoi, given that a candidate can be hundreds of people per election per office it is the wrong approach. A person is a candidate for an office on a given date maybe for a given electoral district. Having it as a statement for the person informs about the person and using query you can have all the details in any order that you like. Better still, it scales. GerardM (talk) 06:03, 16 April 2015 (UTC)Reply

Eligible candidates edit

For many offices, the field of candidates may be large and formal requirements vary from one country to another. As Innocent bystander noted , one might even become the candidate for a party without being a member of that party. A property for a candidate status before this was rejected [1]. As P726 is the only property for candidates, the exact status may need to be reflected with qualifiers.
--- Jura 08:14, 22 April 2016 (UTC)Reply

I added made two items (Special:WhatLinksHere/Q26696044) that can be used with P794 (P794) to clarify the status of the candidacy. Sample at Q22676594#726.
--- Jura 09:21, 25 August 2016 (UTC)Reply

Property used for electoral district? edit

Originally, this property was meant to be used to link Public Speaker (Q19772737) to public election (Q40231). However, equally needed is a property to link Public Speaker (Q19772737) to electoral unit (Q192611). Actually, this property is already used in such a way, violating the subject type constraint (Q21503250). Is there any reasons for not making that an 'official use' by adding electoral unit (Q192611) to the subject type constraint (Q21503250), and requiring the use of the qualifier elected in (P2715).--Tdombos (talk) 12:37, 2 April 2018 (UTC)Reply

Mainz (electoral district) (Q1008388)--Tdombos (talk) 13:14, 2 April 2018 (UTC)Reply
I try to visualize what happens when the electoral district is an item like Rhineland-Palatinate (Q1200).
--- Jura 13:47, 2 April 2018 (UTC)Reply
In general, there is a legitimate discussion whether it would be better to record candidacy data in the Public Speaker (Q19772737) item via candidacy in election (P3602), rather then recording this data on the public election (Q40231) or electoral unit (Q192611) (see discussion above). But as long as we have it for public election (Q40231) we can also have it for electoral unit (Q192611) as the number of candidates will be significantly lower for electoral unit (Q192611). --Tdombos (talk) 14:42, 2 April 2018 (UTC)Reply
I think the use on items for elections is not for items about countless positions to fill. For general elections, recording it on the items for candidates seems preferable. I think for Finland, it was done recently.
--- Jura 14:52, 2 April 2018 (UTC)Reply

Leader of a party for general elections edit

@Jura1: When elections are "person oriented" as presidential elections, the successful candidate (P991) in the election item contains the name of person with a qualifier member of political party (P102), optionally. However, when elections are party oriented and there are one (or more) candidate elegible for each circumscription, as in parlamentary elections, values of successful candidate (P991) in the election item are the won parties. In these case, may we use P726 as a qualifier to inform who is the main leader for each party for this elections ?. Any other property suggested ?. Thanks, Amadalvarez (talk) 15:25, 5 July 2020 (UTC)Reply

@Jura1, Yair rand, Oravrattas: I rebuild previous question. When elections are "person oriented" as presidential elections, the candidate (P726) & successful candidate (P991) in the election item contains the name of person with a qualifier member of political party (P102), optionally. However, when elections are party oriented and there are one (or more) candidate elegible for each circumscription, as in parlamentary elections, values of P726 & P991 in the election item are, respectively, the candidate party & won party. In these cases, what could be the qualifier to inform the "party leader"?. I can ask for a new property called "party leader" or "list leader",... or try to use any other like participant (P710) or significant person (P3342), as an alternative. However, both of them are too much generic and P3342 can't be use as qualifier. Any suggestion ? Thanks, Amadalvarez (talk) 12:09, 21 July 2020 (UTC)Reply
@Amadalvarez: we need to be careful here generally, as in many countries, parliamentary elections are also person oriented, not party oriented, even though the results are often aggregated to display the number of seats or votes that each party won. But that aside, the current way party leaders are modelled is via a position held (P39) statement on the item for the leader to a position such as leader of the Green Party of Canada (Q73682606), rather than storing it on something like an election result.--Oravrattas (talk) 14:37, 21 July 2020 (UTC)Reply
@Oravrattas: What you say is correct under the domain of a person who has obtained the P39 after the election. However, I am talking about the electoral domain where the "main leader" among the different lists or constituencies in which the party participates is, de facto, its candidate for the presidency of the territory (state, region, ...) or spokesman for the group or whatelse, if they finally have enough seats in the chamber. I need it for the Infobox elections, and then the position at stake is as defined in office contested (P541). After the election, it will be time to assign to the elected person the P39 defined by P541 or some other as a result of subsequent processes. In short, I'm looking for the right way to report to candidate (P726) of a party, who is its "principal leader" for the whole election, regardless of the result it ultimately obtained. Thanks, Amadalvarez (talk) 15:07, 21 July 2020 (UTC)Reply
@Amadalvarez: I'm afraid I'm not following. If you look at, for example, Jeremy Corbyn's P39s, it shows that he was the leader of the Labour Party from September 2015 to April 2020. As such it can be calculated that he was the party leader at the time of 2019 United Kingdom general election (Q30173038) in December 2019. --Oravrattas (talk) 12:53, 22 July 2020 (UTC)Reply
@Oravrattas: I'sorry for my poor explanations, may be are caused by my language limitations. Look, in an elections the leader of the list is "the leader of the list" for that election, beside if he were the leader of the party at that moment or he will be the candidate for president among the members of the chamber for that party. Behaviour of political parties are not allways coherent. In the 2015 Catalan regional election (Q17082048), Junts pel Sí (Q20687291) won the elections and the parliament choose the #4 of the list as a new President, and the #1 was just a Member of the Parliament of Catalonia (Q18714088), it is, the office contested (P541) for these election. Therefore, trying to deduce who is the leader of the list from the information of other items not specifically related to the election, is risky.
For me, qualifiers are used to collect information that does not belong 100% to the main item or 100% to the property, but defines the characteristics of the item-property relationship. In this case, the qualifiers are not from the party listed as the value of P726, but from the candidacy submitted by that party for those elections, specifically. Anyway, I believe this is an easy situation, because only happens on proportional elections to party list, and not for the rest of election types. If we accept qualifiers member of political party (P102) or represents (P1268) in person oriented elections, why do not accept a person (P3342 or whatever) in a party oriented election ?. Thanks for your attention, Amadalvarez (talk) 19:31, 22 July 2020 (UTC)Reply
@Amadalvarez: If I'm understanding correctly, the issue with setting a position held (P39) statement on the person is that the this "leader of the list' is not necessarily the same person as the 'leader of the party'? If that is the case could you not create a new position for, say, 'list leader in 2015 Catalan regional election' and use that instead? (Note, I'm not saying that this is the best approach: just seeing how we could do this without having a new property. It may well turn out that requesting a new property is the way to go, but that's going to require figuring out what the right level of abstraction of that would be, as this sort of electoral process is very different in different countries.) --Oravrattas (talk) 08:40, 23 July 2020 (UTC)Reply
@Oravrattas: I see your good will, I appreciate. You are giving to me solutions for the person domain. The P39 is to define the positions of a person. This is not the object of my petition. I need to fill the election item, this is, who was the person that was the list leader for the party of one instance of P726 only for this specific election; don't matter who were he, which P39 had or even if he were an independent, without militancy on the party. Is an information only related to one specific edition of the election. If after election he becomes successful candidate (P991), it's the time to create -in the person item- the corresponding P39 with the position assigned. Creating a position called "team leader for...." as you suggest, we'll be able to fill the CV of the person even before elections, but it is useless to be used (or linked) within the instance of the P726 related with it. I don't really want to create a new property. Actually, I like "wildcard properties" that can have a "complement of the name" like applies to part (P518) or object has role (P3831), for instance. That's cause I propose to use significant person (P3342) or, secondarily, participant (P710). Thanks, Amadalvarez (talk) 09:32, 23 July 2020 (UTC)Reply
@Oravrattas: You may see here some examples of the concept I try to use. In these cases they use director / manager (P1037); it was not my initial idea, it's an option accepted as a qualifier without P726 constraints, however the P1037 requires that the subject were an organitzation or similar, not an event. Thanks, Amadalvarez (talk) 04:26, 25 July 2020 (UTC)Reply
@Amadalvarez: I suspect this is stretching the original definition a bit, but I noticed today that party chief representative (P210) has been used occasionally for this sort of purpose, e.g. on the candidates in 2015 Canadian federal election (Q3586271) --Oravrattas (talk) 09:38, 4 August 2020 (UTC)Reply
@Oravrattas: Ooooh! at first, it made me laugh because the label in Catalan says "secretary of the communist party". In fact, when I checked the qualifiers used on the candidate (P726) I had seen it, but I found it inappropriate, because of its specificity. Now, reading his description in other languages, it seems reasonable. I put P3342 in the sample cases I used to test the new infobox, but I will change them to P210. I invite you to visit the infobox demo page with the different types of choices it deals with, 100% WD. It is multilingual and responds to the language of preferences. In a few days I will finish the ontology documentation for each case and I would like to share it on the project page and have your experience and opinion. Thanks a lot ! Amadalvarez (talk) 12:43, 4 August 2020 (UTC)Reply

Only official candidates or all people who are discussed as candidates edit

When looking at a page like 2020 United States presidential election (Q22923830) it lists a bunch of candidates that run for a primary of a political party but that aren't registered as candidats for the general election. Should those candidates that are not registered for an election still be listed? ChristianKl13:18, 18 August 2020 (UTC)Reply

allowed qualifiers constraint edit

If the candidate is a lesser‐known newcomer, I want to add a name value without creating an item. ( He does not meet the notability policy). I think you should add applies to name of subject (P5168) as the allowed qualifier constraint.

candidate
  no value
applies to name of subject 無名太郎 (japanese)
votes received 3330
0 references
add reference


add value

--Camillu87 (talk) 23:41, 23 August 2021 (UTC)Reply

French label edit

Following this request for comments, the French label now includes the male and the female form. PAC2 (talk) 05:39, 16 June 2022 (UTC)Reply

Return to "P726" page.