Property talk:P7047

Latest comment: 1 year ago by OmegaFallon in topic Why "enemy of" and not "enemy"?

Documentation

enemy
opponent character or group of this fictive character or group
[create Create a translatable help page (preferably in English) for this property to be included here]
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/P7047#Type Q95074, Q4271324, Q14514600, Q20830276, Q21070598, Q1145276, 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/P7047#Entity types
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/P7047#Scope, SPARQL
Item “present in work (P1441): Items with this property should also have “present in work (P1441)”. (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/P7047#Item P1441, search, SPARQL
Property “present in work (P1441)” declared by target items of “enemy (P7047): If [item A] has this property with value [item B], [item B] is required to have property “present in work (P1441)”. (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/P7047#Target required claim P1441, SPARQL, SPARQL (by value)
Symmetric property: if [item A] has this property linked to [item B], then [item B] should also have this property 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/P7047#Symmetric, SPARQL
 

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

Expanding beyond fiction edit

Would anyone be open to using this property to capture other rivalry relationships in the real world? Is there a better property that captures this? Should I propose a new one?

I'm sure there are other domains, but this seems like a good place to start. Wskent (talk) 23:29, 27 January 2020 (UTC)Reply

I've no idea how to make complex constraints, but I think if both object and subject lack a subclass of / instance of an entity that is a child of fictional entity, there should be a qualifier 'statement is subject of' that describes the enmity, and to which sitelinks/sources could be more comprehensively attached. That said, I've already used this property for real life antagonisms 'under the radar', but it's always better to make the property more amenable to a use where appropriate. Arlo Barnes (talk) 19:52, 13 August 2020 (UTC)Reply
'enemy' is far too strong a word. Should probably rename the property to 'enemy or rival'--Trade (talk) 20:05, 13 August 2020 (UTC)Reply

Why "enemy of" and not "enemy"? edit

The phrasing "enemy of" is a bit confusing. To be the "enemy of" someone implies that they consider you their enemy. So, really, every statement with this property is actually saying something about the object not the subject. The object is an enemy of the subject; the object considers the subject an enemy. Combined with the fact that the original proposal says that "reverse statement should be added automatically" I'm going to be bold and just change the name of this property and add a symmetric constraint. It makes sense and the symmetric constraint specifically is in line with the proposal. OmegaFallon (talk) 14:42, 8 February 2023 (UTC)Reply

Return to "P7047" page.