Property talk:P3342

From Wikidata
Jump to navigation Jump to search

Documentation

significant person
person linked to the item in any possible way
Descriptionperson linked to the item in any possible way
Representsperson (Q215627), human whose existence is disputed (Q21070568)
Data typeItem
Domainhuman (Q5), object (Q488383) or whatever else (note: this should be moved to the property statements)
Allowed valueshuman (Q5) (note: this should be moved to the property statements)
Example
According to statements in the property:
Louis XI of France (Q8058)Jean Bouchard (Q3170866)
Costa Serena (Q1136377)Marion Cotillard (Q8927)
2015 State of the Union Address (Q18740986)Anthony Foxx (Q4772543)
When possible, data should only be stored as statements
Tracking: usageCategory:Pages using Wikidata property P3342 (Q27865669)
Tracking: local yes, WD nono label (Q101364367)
See alsosignificant event (P793), significant place (P7153), partner in business or sport (P1327)
Lists
Proposal discussionProposal discussion
Current uses
Total35,407
Main statement35,29999.7% of uses
Qualifier980.3% of uses
Reference10<0.1% of uses
Search for values
[create Create a translatable help page (preferably in English) for this property to be included here]
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303). Known exceptions: Robb Elementary School shooting (Q112123052)
List of violations of this constraint: Database reports/Constraint violations/P3342#allowed qualifiers, SPARQL
Value type “person (Q215627), imaginary character (Q115537581): 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), imaginary character (Q115537581) (or a subclass thereof). (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/P3342#Value type Q215627, Q115537581, SPARQL
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/P3342#Scope, SPARQL
Property “sex or gender (P21)” declared by target items of “significant person (P3342): If [item A] has this property with value [item B], [item B] is required to have property “sex or gender (P21)”. (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/P3342#Target required claim P21, SPARQL, SPARQL (by value)
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/P3342#Entity types
Conflicts with “instance of (P31): literary work (Q7725634): this property must not be used with the listed properties and values. (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/P3342#Conflicts with P31, search, SPARQL

Queries[edit]

Discussion[edit]

significant person (P3342) seems preferable over participant (P710). What do you think?
--- Jura 11:58, 6 March 2018 (UTC)[reply]

Why are these mandatory constraints necessary? --Trade (talk) 21:24, 16 March 2019 (UTC)[reply]

Qualifiers[edit]

In key people of a parliaments I need to included the parliamentary group (P4100) as a qualifier. If it is too much specific, it could be use represents (P1268) instead. Do you agree to add it in a constraint list ?. Thanks, Amadalvarez (talk) 05:30, 4 April 2019 (UTC)[reply]

I don't think using significant person (P3342) to indicate people holding positions of significance in parliament in general is a good idea. Positions should be indicated by position held (P39). --Yair rand (talk) 07:05, 4 April 2019 (UTC)[reply]

@Arbnos: change added subject has role (P2868) we already have required qualifier constraint (Q21510856) = object has role (P3831) what is your idea how both should be used please give us examples - Salgo60 (talk) 11:58, 4 March 2020 (UTC)[reply]

?!?! @Arbnos: I dont follow you when we now look on all items with both subject has role (P2868) and object has role (P3831) does it make sense see list for me it looks like people adds the same value twice in most cases... - Salgo60 (talk) 12:37, 4 March 2020 (UTC)[reply]

new swap of required qualifier constraint (Q21510856)[edit]

Change @Jroakes: we cant change this every second week please motivate the change we undid 1 week ago see above - Salgo60 (talk) 01:38, 11 March 2020 (UTC)[reply]

Custom constraint[edit]

Can someone create a custom constraint that accepts either subject has role (P2868) or object has role (P3831)? Swpb (talk) 14:56, 13 March 2020 (UTC)[reply]

@Swpb: please motivate with some examples... then we maybe can easier request that possibility - Salgo60 (talk) 09:06, 28 March 2020 (UTC)[reply]
BoJack Horseman (Q65090308) and the items it connects to with this property. But also, given that this entire talk section is a fight over which qualifier the property should take, isn't it obvious that editors sometimes find one qualifier works better, and sometimes the other? Swpb (talk) 18:51, 30 March 2020 (UTC)[reply]

Allow organizations[edit]

Should the scope of this property be broadened to include significant organizations? See my question here. Or do we need a new property? --Azertus (talk) 13:46, 8 September 2021 (UTC)[reply]

I support a new property. I think we have enough situations where it can be used @Azertus:--Trade (talk) 14:53, 8 September 2021 (UTC)[reply]