Property talk:P101
Latest comment: 2 months ago by Vicarage in topic Relation to interested in
Documentation
field of work
specialization of a person or organization; see P106 for the occupation
specialization of a person or organization; see P106 for the occupation
[create Create a translatable help page (preferably in English) for this property to be included here]
Type “human (Q5), person or organization (Q106559804), group of humans (Q16334295), animal (Q729), position (Q4164871), fictional character (Q95074), person (Q215627), periodical (Q1002697), fictional organization (Q14623646), project (Q170584), industrial sector (Q8148), museum (Q33506), award (Q618779), convention (Q625994), service (Q7406919), collective (Q13473501), mythical character (Q4271324), art (Q735), center (Q68773434), festival (Q132241), test (Q1003030), public policy (Q546113), professional (Q702269), theatre building (Q24354), fair (Q288514), exhibition (Q464980), facility (Q13226383), scholarly work (Q55915575), scholarly article (Q13442814), academic journal (Q737498), academic journal article (Q18918145), book (Q571), academic chapter (Q21481766), work of science (Q11826511), human activity (Q61788060), recurring event (Q15275719), research (Q42240), database (Q8513), creative work (Q17537576), memory institution (Q1497649), industry (Q268592), group action (Q3533467), human whose existence is disputed (Q21070568)”: item must contain property “instance of (P31), subclass of (P279)” with classes “human (Q5), person or organization (Q106559804), group of humans (Q16334295), animal (Q729), position (Q4164871), fictional character (Q95074), person (Q215627), periodical (Q1002697), fictional organization (Q14623646), project (Q170584), industrial sector (Q8148), museum (Q33506), award (Q618779), convention (Q625994), service (Q7406919), collective (Q13473501), mythical character (Q4271324), art (Q735), center (Q68773434), festival (Q132241), test (Q1003030), public policy (Q546113), professional (Q702269), theatre building (Q24354), fair (Q288514), exhibition (Q464980), facility (Q13226383), scholarly work (Q55915575), scholarly article (Q13442814), academic journal (Q737498), academic journal article (Q18918145), book (Q571), academic chapter (Q21481766), work of science (Q11826511), human activity (Q61788060), recurring event (Q15275719), research (Q42240), database (Q8513), creative work (Q17537576), memory institution (Q1497649), industry (Q268592), group action (Q3533467), human whose existence is disputed (Q21070568)” or their subclasses (defined using subclass of (P279)). (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/P101#Type Q5, Q106559804, Q16334295, Q729, Q4164871, Q95074, Q215627, Q1002697, Q14623646, Q170584, Q8148, Q33506, Q618779, Q625994, Q7406919, Q13473501, Q4271324, Q735, Q68773434, Q132241, Q1003030, Q546113, Q702269, Q24354, Q288514, Q464980, Q13226383, Q55915575, Q13442814, Q737498, Q18918145, Q571, Q21481766, Q11826511, Q61788060, Q15275719, Q42240, Q8513, Q17537576, Q1497649, Q268592, Q3533467, Q21070568, 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/P101#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/P101#Scope, SPARQL
None of josei (Q503106), shōjo (Q242492), children's anime and manga (Q478804), shōnen (Q231302), seinen (Q237338): value must not be any of the specified items.
Replacement property: intended public (P2360)
Replacement values: (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303). Replacement property: intended public (P2360)
Replacement values: (Help)
List of violations of this constraint: Database reports/Constraint violations/P101#none of, SPARQL
None of scholarly article (Q13442814): value must not be any of the specified items.
Replacement property:
Replacement values: (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303). Replacement property:
Replacement values: (Help)
List of violations of this constraint: Database reports/Constraint violations/P101#none of, SPARQL
None of musical work/composition (Q105543609): value must not be any of the specified items.
Replacement property:
Replacement values: music composing (Q11895763), music composition (Q105107008) (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303). Replacement property:
Replacement values: music composing (Q11895763), music composition (Q105107008) (Help)
List of violations of this constraint: Database reports/Constraint violations/P101#none of, SPARQL
None of composed musical work (Q207628): value must not be any of the specified items.
Replacement property:
Replacement values: music composing (Q11895763), music composition (Q105107008) (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303). Replacement property:
Replacement values: music composing (Q11895763), music composition (Q105107008) (Help)
List of violations of this constraint: Database reports/Constraint violations/P101#none of, SPARQL
Conflicts with “instance of (P31): occupation (Q12737077)”: this property must not be used with the listed properties and values. (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/P101#Conflicts with P31, search, SPARQL
None of illustration (Q178659): value must not be any of the specified items.
Replacement property:
Replacement values: illustration (Q21550668) (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303). Replacement property:
Replacement values: illustration (Q21550668) (Help)
List of violations of this constraint: Database reports/Constraint violations/P101#none of, SPARQL
|
Value differential equation (Q11214) will be automatically replaced to value theory of differential equations (Q28575007). 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.) |
| ||||||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
label edit
Changed from "field" to "field of work", as that was ambiguous. --Zolo (talk) 06:27, 10 February 2013 (UTC)
field of profession (P425) edit
For the analogus property where the domain is a profession, see field of profession (P425). For example, on the lawyer item, use <field of profession> law. Superm401 - Talk 19:52, 15 April 2013 (UTC)
Qualifier edit
Should this property be used a qualifier of property "profession"? --Viscontino (talk) 10:30, 21 April 2013 (UTC)
I ask myself too. Conny (talk) 10:29, 21 February 2015 (UTC). I asked here also. Conny (talk) 10:35, 21 February 2015 (UTC).
Used it in Antonia Mills (Q16499798) as property - looks good. Are there other optionons? Conny (talk) 10:50, 21 February 2015 (UTC).
Specificity edit
Should we use very broad terms like "mathematics" and "history" or more specific one like "differential equations" and "archaeology of India". I would prefer the latter, as it is more informative and minimizes redundancy with occupation (P106), but it is not the way it is done in en.wikipedia. --Zolo (talk) 06:00, 17 June 2013 (UTC)
- I think it should be as specific as possible/reasonable. — Finn Årup Nielsen (fnielsen) (talk) 12:18, 19 July 2016 (UTC)
- Finn Årup Nielsen (fnielsen), Zolo specificity might have some issue with the lack of plural forms. For example here I have to write "liquid crystal" instead of "liquid crystals". It sounds a little strange.--Alexmar983 (talk) 02:41, 29 October 2017 (UTC)
Extend the domain of application of this property to processes edit
A physical process acts on some objects, like plant reproducion applies on plants. I think we could extend the domain of this property to add processes, does this seem a good idea ? Like a reasearcher domain of study, a process has a domain of application. TomT0m (talk) 20:16, 14 April 2014 (UTC)
- In my humble opinion it doesn't. We shouldn't mix two different relations ("[person] works in" and "[process] studied by") in one property. They should have absolutely different inverse properties (e. g., physics (Q413) to physicist (Q169470) vs. physical phenomenon (Q15257329) and physical system (Q1454986); note that the latter is a manifestation of (P1557) physics (Q413), but the former isn't). That confuses both machines and people. Ain92 (talk) 17:52, 2 January 2015 (UTC)
Person reference removed edit
see [1].--GZWDer (talk) 13:04, 23 May 2014 (UTC)
- I do not understand this note. What does @GZWDer: mean? — Finn Årup Nielsen (fnielsen) (talk) 12:20, 19 July 2016 (UTC)
I suppose that this relates to the removal of the restriction of field of work (P101) to only work for persons. Where is this discussed? Some of the language labels has "field of work" which pertains to persons only and the initial domain was "Person". Has this edit been discussed? It erases "domain=person"? — Finn Årup Nielsen (fnielsen) (talk) 12:32, 19 July 2016 (UTC)
needs cleanup edit
As is, this property is fairly messed up. Its English description seems to indicate that this links some unspecified items to fields of work (i.e. job specializations), the example links some item to some other item, none of the related to jobs in any way, while at least the German description, the instance of (P31) property and the vast majority of uses seem to indicate that this links persons to their specializations. Lets fix this by restoring the example, English description, and qualifiers to this rationale. Any objections? --Srittau (talk) 12:56, 23 August 2016 (UTC)
Use for programming package edit
I came across Apache Spark (Q7573619) where field of work (P101) was used big data (Q858810) and distributed computing (Q180634). To me, this doesn't sound as a right application? — Finn Årup Nielsen (fnielsen) (talk) 08:20, 5 September 2016 (UTC)
Values about sports edit
Compare sports discipline competed in (P2416) with field of work (P101) at Haile Gebrselassie (Q171500).
Should we use field of work (P101) with athletes? d1g (talk) 12:25, 15 January 2017 (UTC)
Use only for people edit
Documentation of industry (P452) says to use field of work (P101) for people, but field of work (P101) is used both for people and organizations:
- industry (P452) is a subproperty of field of work (P101) OR
- field of work (P101) should be limited to people?
Constraint extension to instances, not only subclasses edit
I'm currently getting a warning for the statement Maurice Krafft (Q15052805) field of work (P101) volcanology (Q102904), apparently because volcanology (Q102904) does not have the subclass of (P279) property, and field of work (P101) requires as a constraint that its values have it. However, in my opinion, it makes no sense to apply the "subclass" attribute to volcanology (Q102904), as it is not a class itself (there are no instances of class "volcanology"). At the same time, it makes perfect sense to have a statement of the form Maurice Krafft (Q15052805) field of work (P101) volcanology (Q102904). Therefore, I propose to broaden the constraint of field of work (P101) so it includes subclass of (P279) or instance of (P31) (as it is the case here). --Rohieb (talk) 17:15, 6 August 2018 (UTC)
- The subclass statements are used throughout the sciences etc., e.g., geology (Q1069) is a subclass of natural science (Q7991). You may be right, and perhaps part of (P361) would be a better fit, and constraints like the one here should be improved or droppped. Ghouston (talk) 23:42, 31 August 2018 (UTC)
- Should be a ping @Rohieb:, given the time elapsed. Ghouston (talk) 23:43, 31 August 2018 (UTC)
- @Ghouston: OK, thanks for the feedback, I have included instance of (P31) in the value constraint for now. I've not yet seen any reason to also include part of (P361), but that bridge can easily be crossed once someone gets to it. (BTW, there also seems to be a lot of confusion between the properties subclass of (P279) and instance of (P31) on several items I looked at… but that's another story.) --Rohieb (talk) 19:59, 1 September 2018 (UTC)
Books and journals ? edit
Can we use this property for books and journals ? We also have main subject (P921) but it seems somewhat different. For example the same item could have main subject (P921): "poverty" and field of work (P101) economics or sociology.--Zolo (talk) 10:57, 5 November 2018 (UTC)
- @Zolo You are right: the field of a publication is not the same thing as its subject headings. As @Valentina.Anitnelav pointed out in this property proposal discussion: "The discipline in which a paper was written is usually not the central topic - e.g. a paper written in the field of musicology (Q164204) is usually not about musicology (Q164204)."
- Until a more suited property is available, I think you may use P101 on books and journals. Fjjulien (talk) 17:41, 30 November 2023 (UTC)
Use on classes edit
This property is sometimes uses on subclasses rather than instances of organization (Q43229), eg. scientific organization (Q45103187)field of work (P101)science (Q336). This currently violates its type constraint. Is there a better way to model this relationship or should the type constraint be changed? Daask (talk) 16:54, 21 May 2020 (UTC)
- It can be done by changing the relation (P2309) on the constraint to instance or subclass of (Q30208840). I can't see any alternative way of expressing the relationship on scientific organization (Q45103187), the alternative would be to omit it or add it as an exception on the constraint. Ghouston (talk) 23:59, 21 May 2020 (UTC)
- relation (P2309) turned out to have multiple values; it seems that the type constraint therefore hasn't been operational since May. I have now replaced instance of (Q21503252) and subclass of (Q21514624) with instance or subclass of (Q30208840).
- I also removed a few redundant classes that are subclasses of fictional organization (Q14623646), which remains in the list, trying to make the list more manageable. As subclass of (P279) is a transitive relation, the constraint checker should be satisfied if any ancestral class of the item is mentioned in the list, not necessarily the immediate parent class. If you identify another class that ought to be an allowed type, verify first that it has its appropriate subclass of (P279) statements. --SM5POR (talk) 19:41, 2 August 2020 (UTC)
Use for YouTube channels edit
You get a warning for YouTube channel (Q17558136), but field of work (P101) seems better than main subject (P921) as a video channel seems more in common with an organisation than a literary work. Vicarage (talk) 15:41, 11 December 2022 (UTC)
- I've added creative work (Q17537576) to the restriction list here to avoid this problem for all creative works. Vicarage (talk) 09:49, 18 July 2023 (UTC)
Field of worh vs Way how to do it edit
I do have and organization which has defined in some other catalog:
- Area of actions (What areas they do) - filled into this field of work (for example Conflict Resolution, Peace and Reconciliation, Interreligious Dialogue, Intercultural Dialogue, Children and Youth, Women's Rights, Humanitarian Aid, Freedom of Religion, Democracy, Social Cohesion, Citizenship, Environment, Human Values, Migration)
- Form of actions (How do they do it) - ??? (for example Advocacy, Capacity Building and Empowerment, Diplomacy, Information Distribution, Networking, Social Work, Community Service)
- which property to choose?
Thank you in advance --Dee (talk) 20:00, 30 December 2022 (UTC)
Relation to interested in edit
There is a discussion about the relationship between field of work (P101) and interested in (P2650), including a proposal to merge these properties, at Wikidata:Project chat#Interested in vs. Field of work. Daask (talk) 19:32, 22 October 2023 (UTC)
- archived at https://www.wikidata.org/wiki/Wikidata:Project_chat/Archive/2023/10#h-Interested_in_vs._Field_of_work-20231018123200, no conclusion reached. Vicarage (talk) 16:53, 3 February 2024 (UTC)