Property talk:P241

From Wikidata
Jump to navigation Jump to search

Documentation

military branch
branch to which this military unit, award, office, or person belongs, e.g. Royal Navy
DescriptionUnit is part of military branch
Representsmilitary branch (Q781132)
Data typeItem
Template parameteren:Template:Infobox military unit field branch
Domain
According to this template: instances of military unit (Q176799)
According to statements in the property:
military unit (Q176799), human (Q5), military facility (Q18691599), individual animal (Q26401003), fictional character (Q95074), military unit class (Q62934160), group of humans (Q16334295), police squad (Q64353859), military rank (Q56019), military uniform (Q1196123), military technology (Q329864), weapon (Q728), military unit designation (Q91197994), military profession (Q6857706), military equipment (Q18643213), military position (Q16631188), collection (Q2668072) or law enforcement agency (Q732717)
When possible, data should only be stored as statements
Allowed valuesinstances of military branch (Q781132) (note: this should be moved to the property statements)
Example
According to this template: Carrier Strike Group Three is part of Navy
According to statements in the property:
Prince Harry, Duke of Sussex (Q152316)British Army (Q222595)
Ronald Reagan (Q9960)United States Army (Q9212)
Royal Gurkha Rifles (Q2289772)British Army (Q222595)
Tadeusz Bór-Komorowski (Q170356)cavalry of Second Polish Republic (Q11737524)
Volodymyr Zelenskyy (Q3874799)Armed Forces of Ukraine (Q936105)
When possible, data should only be stored as statements
Tracking: sameno label (Q42533335)
Tracking: usageCategory:Pages using Wikidata property P241 (Q20990006)
See alsomilitary unit (P7779), conflict (P607), military or police rank (P410), military casualty classification (P1347)
Lists
Proposal discussionProposal discussion
Current uses
Total146,393
Main statement144,04698.4% of uses
Qualifier2,3391.6% 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]
Type “military unit (Q176799), human (Q5), military facility (Q18691599), individual animal (Q26401003), fictional character (Q95074), military unit class (Q62934160), group of humans (Q16334295), police squad (Q64353859), military rank (Q56019), military uniform (Q1196123), military technology (Q329864), weapon (Q728), military unit designation (Q91197994), military profession (Q6857706), military equipment (Q18643213), military position (Q16631188), collection (Q2668072), law enforcement agency (Q732717): item must contain property “instance of (P31)” with classes “military unit (Q176799), human (Q5), military facility (Q18691599), individual animal (Q26401003), fictional character (Q95074), military unit class (Q62934160), group of humans (Q16334295), police squad (Q64353859), military rank (Q56019), military uniform (Q1196123), military technology (Q329864), weapon (Q728), military unit designation (Q91197994), military profession (Q6857706), military equipment (Q18643213), military position (Q16631188), collection (Q2668072), law enforcement agency (Q732717)” 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/P241#Type Q176799, Q5, Q18691599, Q26401003, Q95074, Q62934160, Q16334295, Q64353859, Q56019, Q1196123, Q329864, Q728, Q91197994, Q6857706, Q18643213, Q16631188, Q2668072, Q732717, SPARQL
Single value: this property generally contains a single value. (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/P241#Single value, SPARQL
Contemporaries:
if [item A] has this property (military branch (P241)) 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/P241#Contemporary, 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/P241#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/P241#Scope, SPARQL
None of artillery (Q64418): value must not be any of the specified items.
Replacement property:
Replacement values: artillery (Q1116728) (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/P241#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.)

For the time being, at least, can we use this for all military affiliations, not just branches? Such as saying en:Black Watch Armoury in Montreal is part of en:The Black Watch (Royal Highland Regiment) of Canada? Shawn in Montreal (talk) 11:28, 7 March 2013 (UTC)[reply]

Not sure what you're getting at? "Branch" and "part of" are two different properties in military units. I don't think we want to lump them together. The Black Watch (Royal Highland Regiment) of Canada is branch = Canadian Army-Primary Reserves. Part of = Royal Canadian Infantry Corps. That armoury looks like it was a garrison, so could be specified as a HQ. Danrok (talk) 11:41, 7 March 2013 (UTC)[reply]

Overused with individual people

[edit]

The new constraint on type military unit (Q176799) reveals that this property is already in use for nearly 7500 human (Q5) items... Is this an adequate use that should be allowed? LaddΩ chat ;) 14:18, 15 March 2014 (UTC)[reply]

"Military unit" and "branch of service" don't quite align - one is the specific assignment ("Fooian 1st Division"), the other is the overall force to which they belong ("Fooian Army"). It's possible, though unusual, for units to contain people from multiple branches. Andrew Gray (talk) 10:43, 10 May 2014 (UTC)[reply]

Is the single-value constraint a good idea?

[edit]

A person being a member of only one military branch is indeed the common case, but legitimate violations of this constraint aren't all that rare. Two common cases in which it happens: 1) a country's armed force branches may be reorganized, so people are members of different branches at different points in their career, and 2) countries may cease to exist and/or people may move between them. For example, around 1917, a number of members of the Imperial Russian Army (Q1078222) became members of the Red Army (Q251395). --Delirium (talk) 20:47, 27 April 2018 (UTC)[reply]

Looks like this has now been removed, thanks! --Delirium (talk) 23:57, 6 May 2018 (UTC)[reply]
separator (P4155) = start time (P580), end time (P582) parameter allows to handle such cases correctly. — Ivan A. Krestinin (talk) 05:06, 7 May 2018 (UTC)[reply]
Yes, but it doesn't solve the problem. It's a fact that there have been many people who served in more than one army at the same time. F.e. Q62507 who served in both Q520220 since 1664 and Q2240425 since 1672. Roelof Hendrickx (talk) 18:35, 14 November 2021 (UTC)[reply]