Wikidata:Property proposal/squadron embarked

squadron embarked

Originally proposed at Wikidata:Property proposal/Generic

   Done: squadron embarked (P4624) (Talk and documentation)

Description	the aircraft squadrons that served/serving on an aircraft carrier.
Data type	Item
Domain	INS Vikrant (Q2283194), USS Ronald Reagan (Q211658), HMS Ocean (Q1201247)
Allowed values	INAS 300 (Q19563096), INAS 310 (Q19891833), VFA-41 (Q2680746), Strike Fighter Squadron 14 (Q7906832)
Example	INS Vikrant (Q2283194) → INAS 300 (Q19563096), INAS 310 (Q19891833), ...
Source	W:List of Indian naval air squadrons
Planned use	Within one month of creation, I intend to use it on 100 items
Robot and gadget jobs	No
See also	item operated (P121)

Motivation

This is structured statement that can be given definite values. This is different from the property, item operated item operated (P121), because that related to equipment, whereas this related to the military unit. Krishna Chaitanya Velaga (talk) 14:09, 6 October 2017 (UTC)

Discussion

•  Support ديفيد عادل وهبة خليل 2 (talk) 15:39, 7 October 2017 (UTC)
•  Oppose. Use the dedicated type of passengers/cargo (P3437). Thierry Caro (talk) 23:49, 9 October 2017 (UTC)

@Thierry Caro: I don't cargo or people will be right option. A an operational unit in an air force or naval air wing consisting of two or more flights of aircraft and the personnel required to fly them. So a squadron has its own name and emblem, can comprise to more than one type of aircraft. --Krishna Chaitanya Velaga (talk) 08:41, 10 October 2017 (UTC)

@Krishna Chaitanya Velaga: Sorry, but for me this is exactly what the existing property is about. Thierry Caro (talk) 21:45, 16 November 2017 (UTC)

•  Support Not really the same thing as type of passengers/cargo (P3437). Danrok (talk) 17:14, 4 November 2017 (UTC)

@Krishna Chaitanya Velaga: The datatype suggests string yet your example suggests items. What's meant? ChristianKl (✉) 19:13, 30 November 2017 (UTC)

@ChristianKl: Sorry, fixed that. Thanks for pointing out. Krishna Chaitanya Velaga (talk) 04:31, 1 December 2017 (UTC)

@Krishna Chaitanya Velaga: before creation it would also be good to have a description that's in line with other descriptions of properties. What's currently in the field is more the motivation of why you want the property. ChristianKl (✉) 09:48, 1 December 2017 (UTC)

@ChristianKl: I am sorry that I did not understand your concern, please elaborate. Krishna Chaitanya Velaga (talk) 13:02, 1 December 2017 (UTC)

@Krishna Chaitanya Velaga: The description currently read "This property will help us to list the aircraft squadrons that served from an aircraft carrier". If you look at the description of type of passengers/cargo (P3437) that Thierry talked about, it's "the type of passengers or cargo a vehicle actually carries/carried". The audience for the description isn't the people who read the property proposal but the one who will actually use it once it's created. ChristianKl (✉) 17:23, 1 December 2017 (UTC)

@ChristianKl: Thanks for the explanation, I changed the description. Please see if it is OK. Krishna Chaitanya Velaga (talk) 03:16, 2 December 2017 (UTC)

• @Krishna Chaitanya Velaga, Danrok, Thierry Caro, ديفيد عادل وهبة خليل 2:  Done Created as squadron embarked (P4624). ChristianKl (✉) 15:37, 8 December 2017 (UTC)

@ChristianKl: Thanks for creating the property, and the ping. I added a few statements, but unable to set the constraints. Please let me know how to do it. Krishna Chaitanya Velaga (talk) 16:02, 8 December 2017 (UTC)

Even through constaints are listed in their own section they get added like normal statements. Take a look at a similar property for inspiration about what constraints are appropriate. ChristianKl (✉) 16:19, 8 December 2017 (UTC)