Property talk:P3342
Documentation
person linked to the item in any possible way
List of violations of this constraint: Database reports/Constraint violations/P3342#allowed qualifiers, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P3342#Value type Q215627, Q115537581, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P3342#Scope, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P3342#Target required claim P21, SPARQL, SPARQL (by value)
List of violations of this constraint: Database reports/Constraint violations/P3342#Entity types
List of violations of this constraint: Database reports/Constraint violations/P3342#Conflicts with P31, search, SPARQL
This property is being used by:
Please notify projects that use this property before big changes (renaming, deletion, merge with another property, etc.) |
Queries[edit]
- https://w.wiki/5tuS - frequency of occurrence of different counts of numbers of values
- https://w.wiki/5tuT - items with the largest number of values
Discussion[edit]
Link "death of (person)" to item about (person)[edit]
significant person (P3342) seems preferable over participant (P710). What do you think?
--- Jura 11:58, 6 March 2018 (UTC)
Why are these mandatory constraints necessary? --Trade (talk) 21:24, 16 March 2019 (UTC)
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)
- 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)
@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)
- Salgo60, I didn 't offer this restriction, I shared what was already there : https://www.wikidata.org/w/index.php?title=Property:P3342&oldid=1123174646 .--Arbnos (talk) 12:17, 4 March 2020 (UTC)
- https://www.wikidata.org/w/index.php?title=Property:P3342&diff=next&oldid=1123174646 add, https://www.wikidata.org/w/index.php?title=Property:P3342&diff=next&oldid=1125622098 delete.--Arbnos (talk) 12:20, 4 March 2020 (UTC)
- ?!?! @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)
- Salgo60, returned the previous state.--Arbnos (talk) 13:11, 4 March 2020 (UTC)
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)
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)
- @Swpb: please motivate with some examples... then we maybe can easier request that possibility - Salgo60 (talk) 09:06, 28 March 2020 (UTC)
- 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)
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)
- 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)
- All Properties
- Properties with wikibase-item-datatype
- Properties used on 10000+ items
- Properties with qualifiers constraints
- Properties with constraints on type
- Properties with scope constraints
- Properties with target required claim constraints
- Properties with entity type constraints
- Properties with conflicts with constraints