Property talk:P1423

From Wikidata
Jump to navigation Jump to search

Documentation

Descriptionprimary topic of the subject template or infobox
Data typeItem
Domain
According to this template: instances of Wikimedia template (Q11266439)
According to statements in the property:
MediaWiki template (Q114747576) or Scribunto module (Q11382506)
When possible, data should only be stored as statements
ExampleTemplate:Taxonomy/Syngnathiformes (Q14464882)Syngnathiformes (Q650692)
Template:Shaman King (Q13581244)Shaman King (Q219610)
Robot and gadget jobsDeltaBot does the following jobs:
See alsocategory's main topic (P301), Wikimedia portal's main topic (P1204), is a list of (P360)
Lists
  • 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
  • By value of property
  • Items with no other statements
  • Most recently created items
  • Items with novalue claims
  • Items with unknown value claims
  • Usage history (total)
  • Chart by item creation date
  • Database reports/Constraint violations/P1423
  • Map
  • Random list
  • Proposal discussionProposal discussion
    Current uses
    Total41,319
    Main statement41,311>99.9% of uses
    Qualifier4<0.1% of uses
    Reference4<0.1% of uses
    Search for values
    [create Create a translatable help page (preferably in English) for this property to be included here]
    Scope is as main value (Q54828448): 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/P1423#Scope, 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/P1423#Entity types

    Example[edit]

    When a template has a topic with a specified geographical area ( Template: <topic> in <location>) I would use a qualifier as done in Template:South Holland Province (Q7778113). Michiel1972 (talk) 09:38, 6 October 2014 (UTC)[reply]

    Domain[edit]

    @Jura1, TomT0m, Closeapple, Soulkeeper, UV, Micru: I've changed the domain of this template and been asked about discussion. So I'd like to understand why the domain was initially narrowed to infobox templates instead of any templates. Personally I see the link between Template:Chaerophyllum (Q11007820) and Chaerophyllum (Q278358) as very appropriate and believe that P1423 is good for this. --Infovarius (talk) 13:01, 11 October 2014 (UTC)[reply]

    Until you changed the domain of this property today, this property corresponded to its inverse property, topic's main template (P1424). If this property remains as you changed it, then it would be logical to change as well the property description of the corresponding, inverse topic's main template (P1424) accordingly from "topic's main infobox" to "topic's main template". But while a topic can have a "main infobox", I wonder whether a topic has a "main template". The alternative would be to disjoin template has topic (P1423) from topic's main template (P1424) and remove the "inverse" relationship between these two properties. --UV (talk) 13:28, 11 October 2014 (UTC)[reply]
    Ok, I've changed labels in some languages in topic's main template (P1424) to accent inverse relation with this property. --Infovarius (talk) 19:50, 14 October 2014 (UTC)[reply]
    @Infovarius: The problem with this lies in your change above... It makes no sense to call something "main template" - which implies there is one template - and open this up then for an inverse relationship with any template that has this as main topic. If as in the cited case there are two templates (an Infobox Q5827917 and a navigation template Q11878230) about the same topic, what should be the main template for the topic, the Infobox or the navigation template? That just doesn't work! --S.K. (talk) 18:44, 21 May 2019 (UTC)[reply]
    "what should be the main template for the topic, the Infobox or the navigation template?" Both. It is not too much to have a couple of main templates (and reversibility doesn't crash anything here). --Infovarius (talk) 13:03, 23 May 2019 (UTC)[reply]
    @Infovarius: "It is not too much to have a couple of main templates“. Wrong. At the moment this property template has topic (P1423) has a clear {{Constraint:Single value}}. You are violating this with your statement. If you want to change this semantic you should go via WD:Property proposal or similar mechanism to change the specification, but not simply "misusing" it compared to the current specification of the property. --S.K. (talk) 17:11, 23 May 2019 (UTC)[reply]
    @S.K.: this property has a clear {{Constraint:Inverse}} so you are violating it with your deletion of statement. --Infovarius (talk) 14:24, 28 May 2019 (UTC)[reply]
    @Infovarius: You see, it's a mess. Your reply doesn't add any content that advances the discussion regarding this property, but this mess needs a clear clarification of content. --S.K. (talk) 14:48, 28 May 2019 (UTC)[reply]

    Intersection of topics[edit]

    Now some templates have several topics as value (e.g. Q7745703). Problem is that it implies reverse property (topic's main template (P1424)). It seems that there is a need of another property ("template combines topics") like a pair category combines topics (P971) to category's main topic (P301). And this new property would allow not-reversible values. --Infovarius (talk) 12:59, 23 May 2019 (UTC)[reply]

    Here is that proposal for anyone interested: Wikidata:Property_proposal/Template_combines_topics Lectrician1 (talk) 04:21, 18 January 2021 (UTC)[reply]

    Property change proposed[edit]

    I suggested as part of the Wikidata:Property_proposal/Change_template-topic_property_names_and_scopes that we should rename this property to template has topic.

    Many templates cover a number of topics, as mentioned in the proposal and the section of above.

    Inversely, a topic can have many templates.

    That is why I think the current proposal should include renaming this property and renaming the inverse property topic's main template (P1424) to topic has template.

    This establishes a system comparable to that of part of (P361)/has part(s) (P527).

    Please see the proposal and discuss this change on the Proposal.

    --Lectrician1 (talk) 20:32, 27 January 2021 (UTC)[reply]

    Done. Property scope expanded and property constraints updated. --Lectrician1 (talk) 14:06, 4 February 2021 (UTC)[reply]