Property talk:P301

Active discussions


category's main topic
primary topic of the subject Wikimedia category
DescriptionMain item of this category. See also category combines topics (P971).
RepresentsWikimedia article page (Q15138389), Wikimedia category (Q4167836)
Data typeItem
Corresponding templateTemplate:Cat main (Q6383110)
Template parametersee w:en:Template:Cat main usage.
DomainWikimedia category (Q4167836)
Allowed valuesitems that are not Wikimedia category (Q4167836) (note: this should be moved to the property statements)
ExampleCategory:Germany (Q1410828)Germany (Q183)
Category:Ungulates (Q4333)ungulate (Q1231177)
Robot and gadget jobsDeltaBot does the following jobs:
Tracking: sameCategory:P301 equal to Wikidata (Q16267132)
Tracking: differencesCategory:P301 different from Wikidata (Q16267130)
Tracking: usageCategory:Pages using Wikidata property P301 (Q27043533)
Tracking: local yes, WD noCategory:Category's main topic not in Wikidata, but available on Wikipedia (Q16267131)
See alsolist related to category (P1753), category combines topics (P971), category contains (P4224), template or module that populates category (P4329), template has topic (P1423), Wikimedia portal's main topic (P1204), is a list of (P360)
  • Wikidata:Database reports/basic category numbers
  • Items with the most statements of this property
  • Count of items by number of statements (chart)
  • Count of items by number of sitelinks (chart)
  • Items with the most identifier properties
  • Items with no other statements
  • Most recently created items
  • Items with novalue claims
  • Items with unknown value claims
  • Usage history
  • Database reports/Complex constraint violations/P301
  • Database reports/Constraint violations/P301
  • Map
  • Random list
  • Proposal discussionProposal discussion
    Current uses
    Main statement656,258>99.9% of uses
    Qualifier10<0.1% of uses
    Reference12<0.1% of uses
    Search for values
    [create Create a translatable help page (preferably in English) for this property to be included here]
    Type “Wikimedia category (Q4167836): element must contain property “instance of (P31)” with classes “Wikimedia category (Q4167836)” or their subclasses (defined using subclass of (P279)). (Help)
    List of this constraint violations: Database reports/Constraint violations/P301#type Q4167836, hourly updated report, SPARQL, SPARQL (new)
    Inverse property of “topic's main category (P910):
    if [item A] has this property (category's main topic (P301)) linked to [item B],
    then [item B] should also have property “topic's main category (P910)” linked to [item A]. (Help)
    Exceptions are possible as rare values may exist.
    List of this constraint violations: Database reports/Constraint violations/P301#Inverse, SPARQL, SPARQL (new)
    Single value: this property generally contains a single value. (Help)
    Exceptions are possible as rare values may exist. Known exceptions: Category:Rugs and carpets (Q7030809), Category:Public universities and colleges (Q9533604), Category:Thomas Jefferson University (Q8852585)
    List of this constraint violations: Database reports/Constraint violations/P301#Single value, SPARQL, SPARQL (new)
    Conflicts with “subclass of (P279): this property must not be used with the listed properties and values. (Help)
    List of this constraint violations: Database reports/Constraint violations/P301#Conflicts with P279, hourly updated report, search, SPARQL, SPARQL (new)
    Conflicts with “topic's main category (P910): this property must not be used with the listed properties and values. (Help)
    Exceptions are possible as rare values may exist.
    List of this constraint violations: Database reports/Constraint violations/P301#Conflicts with P910, search, SPARQL, SPARQL (new)
    Distinct values: this property likely contains a value that is different from all other items. (Help)
    Exceptions are possible as rare values may exist. Known exceptions: Q9521861, Q8783516, Q9521962, Q9521739, Q8783363, Q9521773, Q5637066, Q7286260, Q8783487, Q9521893, Q8783411, Q9521823, Q8783379, Q10171284, Q9478208, Q9478220, Q9478225, Q6522683, Q8635080, Q8783497, Q9521924, Q7320756, Q8645467, Q6375507, Q7148487, Q8649294, Q9603725, Q6214716, Q10227182, Q7144527, Q8740325, Q8334849, Q11710037, Q8271732, Q8591258, Q6488956, Q8441054, Q8647211, Q8783474, Q7216199, Q9614495, Q8738756, Q9542308, Q7280231, Q9411442, Q8853369, Q8469198, Q8641736, Q8338108, Q8338117, Q8783303, Q10170587, Q6971227, Q7029110, Q7348428, Q8740480, Q7145194, Q9525714, Q8733376, Q8733430, Q8398181, Q8398182, Q8600300, Q8600608, Q8849607, Q8849609, Q9151113, Q7191678, Q8369193, Q7294955, Q8219350, Q8823482, Q8823484, Q8848648, Q8848650, Q8848654, Q9480326, Q9496016, Q6018382, Q6509583, Q8703625, Q7141720, Q6375729, Q8829446, Q7016511, Q8882740, Q8374986, Q8374987, Q8653999, Q8315712, Q8654693, Q8355224, Q8355236, Q6290208, Q8600512, Q6966040, Q7153707, Q8413691, Q8619151, Q8266451, Q8685872, Q7239596, Q8507547, Q8507548, Q8718868, Q8718871, Q7481452, Q8867024, Q7143955, Q7990029, Q8255161, Q8365707, Q8423377, Q8358293, Q8358298, Q8358461, Q8358462, Q8756866, Q9579902, Q6595902, Q6916093, Q8617548, Q5837092, Q8857950, Q6956075, Q8854416, Q6911736, Q6975864, Q8464798, Q8967563, Q8312868, Q8365294, Q7469251, Q8672545, Q8672567, Q8419632, Q8420052, Q8376860, Q8911413, Q9653356, Q9545474, Q9585717, Q8505389, Q8545244, Q8545259, Q8660133, Q6755467, Q8717241, Q6769705, Q8755608, Q4884546, Q7131101, Q7145850, Q7139354, Q9086059, Q4057258, Q8544221, Q14524494, Q8921363, Q8522770, Q8522771, Q2944929, Q6312078, Q8684714, Q8684718, Q7104133, Q8949803, Q5649447, Q8958140, Q7006838, Q8985567, Q7053013
    List of this constraint violations: Database reports/Constraint violations/P301#Unique value, SPARQL (every item), SPARQL (by value), SPARQL (new)
    Pictogram voting comment.svg Value can't be an individual Wikimedia category item.
    Value of category's main topic (P301) shouldn't be an instance of (P31) Wikimedia category (Q4167836) or any of its subclasses. This can happen as a result of an incorrect merge, or because a category sitelink is linked to a non-category item. In the later case, bots might change that non-category item into a category item. (Help)
    Violations query: SELECT ?item WHERE { ?item (wdt:P301/wdt:P31/wdt:P279*) wd:Q4167836 . }
    List of this constraint violations: Database reports/Complex constraint violations/P301#Value can't be an individual Wikimedia category item.


    Main article or item ?Edit

    Can I change main article to main item ? Q7789980 should probably have this property set to Q11703715, but it seems that there is no Wikipedia article for that. --Zolo (talk) 15:03, 21 April 2013 (UTC)

      Support seems reasonable.--Stevenliuyi (talk) 07:15, 8 May 2013 (UTC)
    I see that it has been changed to "main topic", that seems alright, maybe just "topic", as a category is supposed to be about just one topic ? --Zolo (talk) 08:46, 15 May 2013 (UTC)

    Use for creative worksEdit

    I would like to extend the use of this property for use with creative works. It would represent the Aboutness (Q4668613) or what the main topic of a work would be. In paintings it also could be used in addition to depicts (P180). Some examples:

    --Micru (talk) 16:01, 13 June 2013 (UTC)

    Yes, there is some issue about the redundancy with P180. I suppose that we have two questions:
    • Should we mix "topic of category" be mixed with "topic of creative work". The issue is that we do not want Wikipedia category to show up in normal queries, so we need to be able to segregate it. Presumable "instance of: Wikipedia category" is enough for this. We have the same kind of issue as with fictional items, so it may make sense to solve them in the same way.
    • Should we have different properties for "main subject" and for "depicted in". I am not sure the difference is sufficiently clear cut to warrant different properties, but I do not see real alternatives. Possibly mark the main topics as "preferred" once it is possible ? --Zolo (talk) 07:27, 23 June 2013 (UTC)
    Regarding (1) I think we should wait for the outcome of the RfC about P107. About (2), that is hard to say... maybe depicts (P180) could be stretched? Something like "depicts/main topic"?--Micru (talk) 14:07, 6 July 2013 (UTC)

    Strange propertyEdit

    The original intention was that Q subjects at Wikidata represent items, not articles. The article of certain item and the category of the same item are both related directly to the identic item. An identic item should not have two Q subjects, one for articles and second one for categories. --ŠJů (talk) 14:27, 6 August 2013 (UTC)

    You can propose this one for deletion if you wish. I am going to propose another property for the "main topic of creative work", since it would be unclear if "category items" would show up while doing searches about "main topic".--Micru (talk) 20:44, 19 August 2013 (UTC)
    ŠJů: While this is a strange topic we need it as long as we have items for Category pages. If you can persuade people to delete all the category: items then this property can follow them off of wikidata. Until then I think we need to keep it. Filceolaire (talk) 05:28, 28 August 2013 (UTC)

    unknown values for category's main topicEdit

    soon: Basically one should be able to detect pages where the value is "unknown". Similar feature one should be able to detect "no value". לערי ריינהארט (talk) 11:00, 4 November 2013 (UTC)

    template main topicEdit

    In the same way that Category:Syngnathiformes (Q7165189) has category's main topic (P301)=Syngnathiformes (Q650692), I think the template item Template:Syngnathiformes (Q14464882) should have a statement like template main topic=Syngnathiformes (Q650692). But would it be better to rename P301 to just "main topic" so that it could be used in both cases, or are there any good reasons to use separate properties? - Soulkeeper (talk) 19:43, 30 November 2013 (UTC)

    Soulkeeper, I think that would bring confusion and it wouldn't let use the same constraints. I have started a property proposal Wikidata:Property_proposal/Generic for templates.--Micru (talk) 15:00, 23 June 2014 (UTC)

    Confusion about purpose - "primary topic of the subject category" means the main thing a category is about, no?Edit

    Just thought I'd get something clarified since I've now edited values of this property in many items. Are these correct? In other words, do categories which refer to some facts about something else deserve to have that something else set as category's main topic (P301)? I'll list examples of where I did this:

    If these are not correct, I think the documentation should be changed to make it clearer, and I'll fix my (eleven) mistakes --BurritoBazooka (talk) 21:42, 13 September 2015 (UTC)

      Done I fixed them by using category combines topics (P971). Still think docs can be clearer on this property. --BurritoBazooka (talk) 04:27, 14 September 2015 (UTC)

    Distinct value constraint exceptions listEdit

    There is a long list of exceptions listed under the distinct value constraint. I think that many of them shouldn't be there. Those exceptions might have been necessary in the past, when category's main topic (P301) was the only property that could be used to describe topics of Wikimedia category items. However, now that we also have category combines topics (P971) and category contains (P4224), that is no longer the case. Topics of category items like Category:Gymnasts by nationality (Q6970633), Category:Deep Purple songs (Q6429035) and Category:People from Płock (Q9237811) can, and are, now described using those properties. Therefore, there is no longer a need to include them as constraint exceptions in this property.

    The constraint violation gadget also shows that, at the moment, the exceptions list causes a "Bad parameters" error with an explanation: "The parameters of this constraint could not be imported because they were too long.". So, it seems that the unnecessarily high number of exception parameters are already causing some problems. Additionally, because P301 is an inverse property of topic's main category (P910), every distinct value exception in P301 causes a single value exception (or inverse value exception) in P910, if they are not listed as exceptions in that P910 constraint.

    If there are no objections, I would like to remove all unnecessary distinct value exceptions from this property. Starting from items that no longer use this property. --Shinnin (talk) 20:12, 18 December 2017 (UTC)

    I've now removed a number of items from the distinct value exceptions list. Here is a query that shows the remaining items that are marked as distinct value exceptions, but no longer use this property. These should probably be removed as well.
    SELECT ?item ?itemLabel ?exception ?exceptionLabel
      ?item wdt:P31 wd:Q18667213;
            p:P2302 ?constraint.
      FILTER(?item = wd:P301)
      ?constraint ps:P2302 wd:Q21502410;
                  pq:P2303 ?exception.
        ?exception wdt:P301 ?value.
      SERVICE wikibase:label { bd:serviceParam wikibase:language "[AUTO_LANGUAGE],en". }
    Try it! Shinnin (talk) 15:36, 19 January 2018 (UTC)
    Return to "P301" page.