Property talk:P425

Documentation

field of this occupation
field corresponding to this occupation or profession (use only for occupations/professions - for people use Property:P101, for companies use P452)
Representsfield of work (Q627436), occupation (Q12737077)
Data typeItem
Domainoccupation (Q12737077), profession (Q28640), fictional profession (Q17305127) or activity (Q1914636)
Examplebodyboarder (Q17362882)bodyboarding (Q890097)
sculptor (Q1281618)art of sculpture (Q11634)
painter (Q1028181)art of painting (Q11629)
chemical engineer (Q7888586)chemical engineering (Q83588)
scholar of Native American studies (Q104421445)Native American studies (Q27752)
cellist (Q13219637)cello music performance (Q105279359)
Robot and gadget jobsDeltaBot does the following jobs:
Tracking: usageCategory:Pages using Wikidata property P425 (Q26250060)
See alsofield of work (P101), industry (P452), practiced by (P3095), occupation (P106), members have occupation (P3989)
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/P425
  • Map
  • Random list
  • Proposal discussionProposal discussion
    Current uses
    Total8,374
    Main statement7,31787.4% of uses
    Qualifier1,04912.5% of uses
    Reference8<0.1% of uses
    Search for values
    [create Create a translatable help page (preferably in English) for this property to be included here]
    Conflicts with “field of work (P101): this property must not be used with the listed properties and values. (Help)
    List of violations of this constraint: Database reports/Constraint violations/P425#Conflicts with P101, hourly updated report, search, SPARQL
    Conflicts with “occupation (P106): this property must not be used with the listed properties and values. (Help)
    List of violations of this constraint: Database reports/Constraint violations/P425#Conflicts with P106, hourly updated report, search, SPARQL
    Inverse property of “practiced by (P3095):
    if [item A] has this property (field of this occupation (P425)) linked to [item B],
    then [item B] should also have property “practiced by (P3095)” linked to [item A]. (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/P425#inverse, 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/P425#Entity types
    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/P425#Scope, SPARQL
    Contemporaries:
    if [item A] has this property (field of this occupation (P425)) linked to [item B],
    then [item A] and [item B] have to coincide or coexist at some point of history. (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/P425#Contemporary, SPARQL

    Please notify projects that use this property before big changes (renaming, deletion, merge with another property, etc.)

    Discussion edit

    Untitled edit

    Discussed at Talk:Q28640 (profession).

    Constraint edit

    Can this be extended to allow not only professions but also occupations, i.e. instances of occupation (Q13516667), too? -- Gymel (talk) 07:24, 9 September 2014 (UTC)Reply

    I think so. Let's try. --Infovarius (talk) 06:50, 13 September 2014 (UTC)Reply
    That was not very convincing (diff). I'm changing the template parameter to "subclass" now, perhaps that still includes instances. -- Gymel (talk) 17:04, 18 September 2014 (UTC)Reply
    @@Infovarius: No, that didn't include instances, thus the report became dramatically worse. Reverted it. -- Gymel (talk) 09:37, 20 September 2014 (UTC)Reply

    "Field of" qualifications or degrees? edit

    Doktor Nauk in Architecture (Q16698078) is neither profession nor occupation, therefore

    is not allowed. But certainly Doktor Nauk in Architecture (Q16698078) is strongly related to architecture (Q12271) as a field. Any clues how to denote this? -- Gymel (talk) 10:44, 30 January 2015 (UTC)Reply

    Similar issue is with hatter (Q1639239)'s relation to hatmaking (Q663375). --Infovarius (talk) 11:47, 4 February 2015 (UTC)Reply
    I wouldn't say so: , (where ) and therefore is exactly as intended. -- Gymel (talk) 16:36, 4 February 2015 (UTC)Reply


    Occupation or profession? edit

    Items for people use P106. This has the English label "occupation".

    Sample: Nigel Richards (Q3341367) > occupation > Scrabble player (Q20708269)

    If this should be used on such items, should we change the label to "field of this occupation"?

    Sample: Scrabble player (Q20708269) > field of this occupation > Scrabble (Q170436)

    How should be proceed? --- Jura 14:55, 21 July 2015 (UTC)Reply

    Why can't civil servants work in civil service? edit

    I don't have the answer but someone evidently does, otherwise there'd be no protest at Q9844795 (civil servant), stating: "Values of field of this occupation statements should be instances or subclasses of one of the following classes (or of one of their subclasses), but civil service currently isn't:

    • industry
    • academic discipline
    • activity
    • knowledge
    • area of law".

    I don't have a solution but this needs fixing. --Ehitaja (talk) 20:40, 7 January 2019 (UTC)Reply

    Inverse property not working well edit

    See discussion at Property talk:P3095#Inverse property not working well. {{u|Sdkb}}talk 20:38, 24 June 2020 (UTC)Reply

    Constraint conflicts when industry is also an activity edit

    Right now, both of the following claims exist:

    1. field of this occupation (P425)property constraint (P2302)conflicts-with constraint (Q21502838)property (P2306)industry (P452)constraint status (P2316)mandatory constraint (Q21502408)
    2. practiced by (P3095)property constraint (P2302)inverse constraint (Q21510855)property (P2306)field of this occupation (P425)

    This causes a conflict for some items which are instance of (P31)activity (Q1914636) and instance of (P31)industry (Q268592).

    For example, candle-maker (Q1739737)field of this occupation (P425)candlemaking (Q29349255). This claim could certainly be omitted from the perspective of candlemaking (Q29349255), since there is already candle-maker (Q1739737)industry (P452)candlemaking (Q29349255) and it seems repetitive, but that would cause a constraint violation on candlemaking (Q29349255)practiced by (P3095)candle-maker (Q1739737) because it would missing the inverse statement. I think removing this last claim from candlemaking (Q29349255) would be a loss of relevant information.

    I propose removing the first constraint, so that items could have both field of this occupation (P425) and industry (P452). What do others think? Daask (talk) 13:49, 9 March 2021 (UTC)Reply

    @Daask: I am removing candle-maker (Q1739737)industry (P452)candlemaking (Q29349255). As its description states, industry (P452) should have an organization as subject. --GrandEscogriffe (talk) 15:47, 3 February 2023 (UTC)Reply
    That should resolve my concern. Thank you! Daask (talk) 16:45, 3 February 2023 (UTC)Reply
    Return to "P425" page.