Property talk:P2868

From Wikidata
Jump to navigation Jump to search

Documentation

subject has role
role/generic identity of the item ("subject"), also in the context of a statement. For the role of the value of the statement ("object"), use P3831 ("object has role"). For acting roles, use P453 ("character role"). For persons, use P39.
Representsrole (Q4897819)
Data typeItem
Usage notesUse this property to define the role of an item, also as part of a relation. Use for "subject" as in "concept", not "person" (use P3831 instead). For character roles (e.g. of actors) use P453.
Examplevemurafenib (Q423111) → antineoplastic (Q2853144)
Wikimedia disambiguation page (Q4167410) → word-sense disambiguation (Q48522)
Fritz Hellwig (Q71949) → centenarian (Q2944360)
Tracking: usageCategory:Pages using Wikidata property P2868 (Q118210232)
<complementary property>object has role (P3831)
See alsocharacter role (P453), has use (P366), narrative role (P5800), identity of subject in context (P4649), reference has role (P6184)
Lists
Proposal discussionProposal discussion
Current uses
Total1,260,549
Main statement397,99431.6% of uses
Qualifier862,44268.4% of uses
Reference113<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 “instance of (P31): film (Q11424), Wikimedia disambiguation page (Q4167410)”: 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/P2868#Conflicts with P31, SPARQL
Scope is as qualifier (Q54828449), as main value (Q54828448), as reference (Q54828450): the property must be used by specified way only (Help)
List of violations of this constraint: Database reports/Constraint violations/P2868#Scope, hourly updated report, SPARQL
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/P2868#Entity types
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/P2868#none of, SPARQL
None of unnamed character (Q109934238): value must not be any of the specified items.
Replacement property: has characteristic (P1552)
Replacement 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/P2868#none of, SPARQL
None of human voice (Q7390): value must not be any of the specified items.
Replacement property:
Replacement values: vocalist (Q2643890) (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/P2868#none of, SPARQL
None of death (Q4): 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).
List of violations of this constraint: Database reports/Constraint violations/P2868#none of, SPARQL
None of music video (Q193977): value must not be any of the specified items.
Replacement property: has characteristic (P1552)
Replacement 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/P2868#none of, SPARQL
None of Wikimedia redirect (Q21528878): 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).
List of violations of this constraint: Database reports/Constraint violations/P2868#none of, SPARQL
None of cancer survivor (Q5031456): value must not be any of the specified items.
Replacement property: medical condition (P1050)
Replacement values: cancer (Q12078) (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/P2868#none of, SPARQL
This property is being used by:

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

Value protagonist (Q215972) will be automatically replaced to value protagonist (Q215972) and moved to narrative role (P5800) property.
Testing: TODO list
Value unseen character (Q526231) will be automatically replaced to value unseen character (Q526231) and moved to narrative role (P5800) property.
Testing: TODO list
Value antagonist (Q245204) will be automatically replaced to value antagonist (Q245204) and moved to narrative role (P5800) property.
Testing: TODO list
Value main antagonist (Q55712911) will be automatically replaced to value main antagonist (Q55712911) and moved to narrative role (P5800) property.
Testing: TODO list
Value supporting character (Q2595584) will be automatically replaced to value supporting character (Q2595584) and moved to narrative role (P5800) property.
Testing: TODO list
Value main character (Q12317360) will be automatically replaced to value main character (Q12317360) and moved to narrative role (P5800) property.
Testing: TODO list
Value minor character (Q27623618) will be automatically replaced to value minor character (Q27623618) and moved to narrative role (P5800) property.
Testing: TODO list
Value title character (Q3246821) will be automatically replaced to value title character (Q3246821) and moved to narrative role (P5800) property.
Testing: TODO list
Value secondary antagonist (Q105078199) will be automatically replaced to value secondary antagonist (Q105078199) and moved to narrative role (P5800) property.
Testing: TODO list
Value hero (Q162244) will be automatically replaced to value hero (Q162244) and moved to character type (P9071) property.
Testing: TODO list
Value villain (Q290691) will be automatically replaced to value villain (Q290691) and moved to character type (P9071) property.
Testing: TODO list
Value supervillain (Q6498903) will be automatically replaced to value supervillain (Q6498903) and moved to character type (P9071) property.
Testing: TODO list
Value antihero (Q110910) will be automatically replaced to value antihero (Q110910) and moved to character type (P9071) property.
Testing: TODO list
Value anti-villain (Q65622867) will be automatically replaced to value anti-villain (Q65622867) and moved to character type (P9071) property.
Testing: TODO list
Value superhero (Q188784) will be automatically replaced to value unseen character (Q526231) and moved to character type (P9071) property.
Testing: TODO list
Value superhero (Q188784) will be automatically replaced to value unseen character (Q526231) and moved to character type (P9071) property.
Testing: TODO list

Propose removing "has" from English label[edit]

The verb conjugation does not cover the full range of uses of the property. The property may be used, and is used, to indicate "[plural subjects] have role", or "[subject] had role". The label should cover all these cases, which "role" alone does. I was reverted on this change, but as yet there has been no valid reason given. --Swpb (talk) 15:54, 10 February 2017 (UTC)[reply]

The relationship ontology uses "has role" in "RO_0000087". There's value in having a name that's consistent with their name. Could you give specific examples where you currently see a problem? ChristianKl (talk) 20:02, 10 February 2017 (UTC)[reply]
Newclare Primary School (Q28739587). Swpb (talk) 06:14, 11 February 2017 (UTC)[reply]
Newclare Primary School (Q28739587)participant (P710)Black people (Q817393)
That seems like an odd use of participant (P710), which I'd expect to see used on an event. Bovlb (talk) 16:19, 15 February 2017 (UTC)[reply]
Given the domain that's agreed on for participant (P710) is events and schools aren't events, I don't think it should be expressed this way in the first place. ChristianKl (talk) 19:06, 15 February 2017 (UTC)[reply]
How would you express it instead? --Swpb (talk) 13:34, 16 February 2017 (UTC)[reply]
has part(s) of the class (P2670) with an item for "Black student" maybe. ChristianKl (talk) 11:30, 22 February 2017 (UTC)[reply]

Difference from P366?[edit]

@ChristianKl, Jura1: What's the difference from has use (P366) "role"?

Do we have an overlap? --Vladimir Alexiev (talk) 17:34, 7 March 2017 (UTC)[reply]

You might want to ping the proposer of this property. Personally, I'm mainly worried about the risk of a possible confusion with character role (P453).
--- Jura 08:42, 10 March 2017 (UTC)[reply]
My understanding is that "main use of the subject" (P366) is about planned usage whereas P2868 "role or purpose of item" also includes occasional uses.
Leonardo da Vinci is not "used" (P366) by anyone, he takes a specific responsibility/role. d1g (talk) 16:40, 8 May 2017 (UTC)[reply]
vemurafenib (Q423111) can be used as antineoplastic (Q23987513), so property should be has use (P366). d1g (talk) 16:45, 8 May 2017 (UTC)[reply]

used as qualifier constraint[edit]

Has there been any discussion to use this only as a qualifier? This doesn't seem to be the intention of the original proposal[1] and there are 77.422 violations, right now[2]. - Valentina.Anitnelav (talk) 15:25, 1 December 2017 (UTC)[reply]

Swpb, Derick Chan, do you think that this constraint is necessary? Why? There are roles that are significant for certain entities, so that they should be recorded in a main claim. If this should not be necessary, I will just restore the previous version. -Valentina.Anitnelav (talk) 15:49, 4 December 2017 (UTC)[reply]
No strong opinion. I think this property should primarily be a qualifier; it was implemented with the constraint, even if that wasn't part of the proposal, and there are plenty of properties available for main statements, such as instance of (P31), position held (P39), occupation (P106), participant in (P1344), and field of work (P101). But if someone wants to use this as a primary property, I don't see anything hugely wrong with that. Swpb (talk) 16:12, 4 December 2017 (UTC)[reply]
Thank you. I see that my interpretation of [3] was wrong (I didn't notice before that this should be used as a qualifier only). (But I would still support the removal of the constraint - it is heavily used on taxa (Tillandsia rubra (Q3528494)) and also useful in other cases) - Valentina.Anitnelav (talk) 17:16, 4 December 2017 (UTC)[reply]
(Edit: It is not of high importance, but the statement "it was implemented with the constraint" is false. The constraint was only added last week. The "history" of property constraints on the property talk's history is misleading, as it shows the status quo in addition to the past constraints.) - Valentina.Anitnelav (talk) 08:00, 5 December 2017 (UTC)[reply]

This point is also discussed at Wikidata:Project chat/Archive/2019/09#"Subject has role" as statement (from August 27th 2019) - Valentina.Anitnelav (talk) 07:06, 28 August 2019 (UTC)[reply]

Since 1. no one has an argument against this being used as a main property, and 2. there is no property that can be used e.g. for parts of chemical processes where no person uses the item but the item has a role nevertheless, and 3. because the creation with a constraint created tens of thousands of useless conflicts I will remove the constraint tomorrow at the latest. --SCIdude (talk) 14:34, 27 November 2019 (UTC)[reply]
@Deryck Chan@SCIdude@Swpb@Valentina.Anitnelav
The main reason against it being used as a main statement property is that people are using it as a coping mechanism when no property is available. So instead of going for a well-defined property for the use case subject has role (P2868) gets used.
I queried for values. The first hit was Siluriformes (Q59576)subject has role (P2868)fish (Q152). That information is already available from the taxon tree. Having it here is just messy. The second hit is Globcal International (Q5570947)subject has role (P2868)peace (Q454). While The organization might cause peace to happen, calling that a role is wrong. The third is Internet police (Q2668518)subject has role (P2868)censorship (Q543) which is also wrong. Maybe it could have censor (Q12377291) as a role but as censorship is an activity or a result but not a role. The forth is Constitution of Venezuela (Q891364)subject has role (P2868)Venezuela (Q717) and that's no good way to speak about the realtionship. The fifth is chloroform (Q172275)subject has role (P2868)weapon (Q728) and while it's better than the previous ones has use (P366) would be better.
Given how the lack of constraint gets the property used we should readd the constraint. ChristianKl ❪✉❫ 11:35, 30 May 2024 (UTC)[reply]
I agree subject has role (P2868) should only be a qualifier. All current uses of subject has role (P2868) as a main statement should have better matching properties, often has use (P366) or main subject (P921). Deryck Chan (talk) 12:21, 30 May 2024 (UTC)[reply]
I agree as well; allowing subject has role (P2868) to be used for main statements inevitably leads to these sorts of misuses. All history aside (including my own 2017 comment above), the main and best use of this property – complementary to object has role (P3831) – is to identify the role of an item in the context of a particular relation: in other words, as a qualifier. I have yet to see a main statement that would not be more appropriately modeled with another property. Re-add the constraint. Swpb (talk) 13:51, 30 May 2024 (UTC)[reply]
In 2022, seing that the use as main value was allowed and that it was very frequent for victims (i.e. subject has role (P2868)Holocaust victim (Q5883980); as of now, nearly 130k results! Special:Search/haswbstatement:P2868=Q5883980), I proposed to Wikidata:WikiProject Religions to adopt subject has role (P2868) in their data model of martyrs (so subject has role (P2868)martyr (Q6498826) and subclasses). We need to find a good solution for these cases ( Notified participants of WikiProject Religions) before restoring qualifier as the only allowed use. As of now I have no better ideas, so suggestions are welcome for these cases. Thanks, Epìdosis 15:59, 31 May 2024 (UTC)[reply]

Add 'task' as alias as well as 'role' or 'duty'[edit]

Add task as alias, this is important to distinguish from formal roles, but specific tasks people are asked to do

none of constraint: Wikimedia redirect page (Q21528878) [edit]

This new constraint should avoid uses like [4]. But maybe I'm missing something.

BTW dewiki can't have any "permanent duplicate items" afaik, as it doesn't have articles about the same topic in different dialects/scripts/langoids

@Fidoez: FYI. --- Jura 10:11, 30 November 2021 (UTC)[reply]

Retrieved from "https://www.wikidata.org/w/index.php?title=Property_talk:P2868&oldid=2169556795"