Property talk:P971
Documentation
this category combines (intersects) these two or more topics
List of violations of this constraint: Database reports/Constraint violations/P971#allowed qualifiers, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P971#Conflicts with P31, search, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P971#Conflicts with P31, search, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P971#Scope, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P971#Conflicts with P279, search, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P971#Entity types
List of violations of this constraint: Database reports/Constraint violations/P971#Multi value, SPARQL
to do: remove it from either category's main topic (P301) or category combines topics (P971) (Help)
Violations query:
SELECT ?item ?value { ?item wdt:P971 ?value . ?item wdt:P301 ?value . } LIMIT 500List of this constraint violations: Database reports/Complex constraint violations/P971#Values shouldn't be the same for P301 and P971
|
If property value equals to film, by year of publication only (Q38078930) then claim category contains (P4224) = film (Q11424) will be created automatically. Testing: TODO list |
|
|
If property value equals to Wikimedia template (Q11266439) then claim category contains (P4224) = Wikimedia template (Q11266439) will be created automatically. Testing: TODO list |
|
|
If property value equals to Wikimedia navigational template (Q11753321) then claim category contains (P4224) = Wikimedia navigational template (Q11753321) will be created automatically. Testing: TODO list |
|
|
If property value equals to Wikimedia navigational template (Q11753321) then claim instance of (P31) = Wikimedia navboxes category (Q13331174) will be created automatically. Testing: TODO list |
|
This property is being used by:
Please notify projects that use this property before big changes (renaming, deletion, merge with another property, etc.) |
Discussion[edit]
Single value[edit]
For single value (one-on-one mappings) use category's main topic (P301) (and topic's main category (P910) to link back). Multichill (talk) 10:40, 19 October 2013 (UTC)
- Why do we need two or three properties for one single goal? Edoderoo (talk) 16:45, 24 July 2019 (UTC)
Why only categories?[edit]
Why is this property restricted to categories? They are not the only pages combining topics. For instance, politics of the Netherlands (Q877631) combines Netherlands (Q55) and politics (Q7163), in much the same way as Category:Dutch politicians (Q7068416) combines Netherlands (Q55) and politician (Q82955). --Avenue (talk) 12:06, 26 October 2013 (UTC)
Support I second this. Furthermore, the main label should be "topic".
Eg I want to mark categories *and list pages* relevant to food and drink with category combines topics (P971) Europeana Food and Drink (Q19723898) but right now cannot do that. --Vladimir Alexiev (talk) 09:31, 1 April 2015 (UTC)
Nature of combination[edit]
Can we indicate the nature of the combination somehow, e.g. through qualifiers? It could be useful to distinguish between Category:American fiction (Q8245550) and Category:United States in fiction (Q8788365), for instance. --Avenue (talk) 12:38, 26 October 2013 (UTC)
- We could add the something like the "see also" qualifier at Q8881537#P971. This could help working through lists like this. --- Jura 20:29, 12 November 2015 (UTC)
- For lists like Wikidata:Database reports/items without claims categories/ltwiki this could be useful. --- Jura 23:06, 2 February 2016 (UTC)
- At Wikidata:Property_proposal/Sister_projects#cct_applicable_property, I suggested a dedicated property. --- Jura 07:55, 3 February 2016 (UTC)
- Archived: Wikidata:Property_proposal/Archive/49#cct_applicable_property, existing qualifier should do.
--- Jura 10:05, 4 May 2016 (UTC)
- New proposal: Wikidata:Property proposal/map with property.
--- Jura 11:58, 14 December 2017 (UTC)
- See section #Qualifiers below, for proposal to use relation (P2309) rather than related property (P1659). I think it would be a lot more natural. Jheald (talk) 17:47, 1 February 2018 (UTC)
I don't think category combines topics (P971)property constraint (P2302)distinct-values constraint (Q21502410) is true. --Mr. Ibrahem (talk) 20:19, 22 August 2017 (UTC)
- I think so, but I wan to try it, if I found some merge candidates. JAn Dudík (talk) 05:11, 23 August 2017 (UTC)
I think we can try with sparql like
SELECT
?value
?item2Label ?item2
?itemLabel ?item
WHERE
{
?item wdt:P971 ?value .
?item2 wdt:P971 ?value .
SERVICE wikibase:label { bd:serviceParam wikibase:language "ar,en". }
}
LIMIT 10Mr. Ibrahem (talk) 00:11, 24 August 2017 (UTC)
Qualifiers[edit]
Two suggestions in relation to qualifiers:
Firstly, the property related property (P1659) seems particularly ill-suited and unintuitive to use for this. Would anyone object if we changed to use relation (P2309) instead? The semantics here would exactly parallel its use for constraints. In each case, its meaning as a qualifier would be to indicate the property required to join an item to the value of the main statement in order for a requirement to be met -- in the case of a constraint, the test for the constraint to be satisfied; here the part of the test for an item to be a member of the category.
Secondly, can I suggest that it would be useful to be able to capture a requirement that a statement might need to be qualified in some way to support category membership -- for example, perhaps a statement might have to have an end time (P582) or a particular end cause (P1534) to be appropriate. One great advantage of this property over category contains (P4224) is that this property has the potential to allow that. I suggest that it would be a very natural fit to allow such qualifiers here.
As a result, I think there is a case for dropping the current constraint on allowed qualifiers, to allow any qualifier to be included as part of the specification. Jheald (talk) 15:42, 1 February 2018 (UTC)
- There is a proposal to replace "see also". Maybe you want to comment there. Would you have a sample for a use of P582 or P1534 ?
--- Jura 15:46, 1 February 2018 (UTC)
- @Jura1: An example of a category needing use of a qualifier for specification would be Category:Deputies of the 15th National Assembly of the French Fifth Republic (Q30230937), which could be specified:
- (This example originally came up last year in the context of the UK parliament. The data structure there has since changed, to define each term as a separate position held. However the French politicians still uses the more condensed system).
- Where was the proposal to replace "see also" ? Ah, I've found it now, further up the page. I'll add a note to 'see below'. Jheald (talk) 17:44, 1 February 2018 (UTC)
- And for P582 or P1534 ? From my experience with cleaning up qualifiers, people mostly try to do with them what category contains (P4224) is meant to do.
"relation" has (IMHO) the same problem as "property" discussed in the proposal: it was made for constraints. And also: it requires items, not properties as values.
--- Jura 18:44, 1 February 2018 (UTC)
- @Jura1: Hmm. You're right. :-(
- Do we know why relation (P2309) is item-valued rather than property-valued? Were property-valued properties not available when it was proposed? Or is there some useful example of flexibility that was gained by making it item-valued? If it's the latter, then perhaps the same might be a reason to prefer something item-valued here.
- I am not so worried about it having been made for constraints. If the same concept is useful here too, then it doesn't seem such a big deal to widen the properties it can be applied to. On the other hand, the properties it can take as values currently seem quite limited; I can see that that might make for valid objections to widening its domain, if that preserving that current restriction is useful in its present role.
- As for examples using P582 or P1534, I thought I could come up with some -- eg particular categories of politicians who might have died in office, or resigned; or things that ceased to apply at a particular date -- but so far I haven't identified any. (Not that I have looked very much, they could well still be out there). Jheald (talk) 19:55, 2 February 2018 (UTC)
- And for P582 or P1534 ? From my experience with cleaning up qualifiers, people mostly try to do with them what category contains (P4224) is meant to do.
Use with Commons categories[edit]
Category:Ceramic jugs (Q98184763) and c:Category:Ceramic jugs is the first time I've used this property - did I do this right? Should all similar categories in Commons have items like this? - PKM (talk) 21:40, 9 August 2020 (UTC)
- Never mind, got the answer (no!) - PKM (talk) 22:33, 11 August 2020 (UTC)
Combines three topics[edit]
I’m looking at Category:History of Ukrainian literature (Q9892526). Do we decompose this triplet into:
- three elements: = history (Q309) + Ukraine (Q212) + literature (Q8242)
- three overlapping duplets: history of Ukraine (Q210701), Ukrainian literature (Q1276062), history of literature (Q6497044)
- list all six (as I have done, tentatively), because, logically, each from the second list combines with one from the first.
Thanks. —Michael Z. 22:12, 16 December 2020 (UTC)
Broading P971 scope to inclute templates[edit]
There is a suggestion of broading P971 scope to inclute templates. Please see Wikidata:Property proposal/Template combines topics. Data Gamer play 13:04, 16 January 2021 (UTC)
Using with main topic (P301)[edit]
@Florentyna: don't this property and category's main topic (P301) have the same purpose, of defining the topic of the category? If a category has one specific topic then there is no need for P971; it's duplicating information. It was also mentioned in the property proposal discussion that as few items as possible should contain both properties, so I don't know why this constraint wasn't added in the first place. I just did a query showing that 107,782 items currently have both properties. ―Jochem van Hees (talk) 09:25, 21 July 2022 (UTC)
- It is not the same. Example: Category:1983 Badminton World Championships (Q8165981) has as main topic 1983 Badminton World Championships (i.e. often main topic and category consist of the same wording without the word category). But, category combines (let's ignore the word topic, this seems to confuse) means, that the category combines the year 1983 with Badminton World Championships. Another example: Category:1985 in badminton (Q8167883) has as main topic 1985 in badminton, and combines badminton and 1985. --Florentyna (talk) 09:41, 21 July 2022 (UTC)
- All Properties
- Properties with wikibase-item-datatype
- Properties used on 1000000+ items
- Properties with constraints on type
- Properties with qualifiers constraints
- Properties with conflicts with constraints
- Properties with scope constraints
- Properties with entity type constraints
- Properties with multi value constraints
- Properties with complex constraints