Wikidata:Property proposal/Minimum wage
minimum wage edit
Originally proposed at Wikidata:Property proposal/Generic
| Description | lowest wage which can be paid legally in a state for working |
|---|---|
| Represents | minimum wage (Q186228) |
| Data type | Quantity |
| Domain | countries or their subdivisions |
| Allowed values | \d+ |
| Allowed units | currency |
| Example 1 | Ukraine (Q212) → 3723 hryvnia applies to part (P518) month |
| Example 2 | Belarus (Q184) → 330 Belarusian ruble applies to part (P518) month |
| Example 3 | Germany (Q183) → 1498 euro applies to part (P518) month |
| Example 4 | California (Q99) → 11 United States dollar applies to part (P518) hour |
| Format and edit filter validation | none |
| Planned use | putting that property into items about countries and then incorporating them into infoboxes |
| See also | median income (P3529) |
Motivation edit
Important economical information that should be in every item about country alongside median income (P3529). --Tohaomg (talk) 00:53, 12 December 2018 (UTC)
Discussion edit
- valid in period (P1264) as a qualifier would mean something very different than the examples use it to mean. I recommend either using a different unit ("dollars per hour" and such, perhaps), or using a different qualifier. --Yair rand (talk) 02:23, 12 December 2018 (UTC)
Support David (talk) 07:43, 12 December 2018 (UTC)
Comment As it’s likely we already have items for these, for example SMIC (Q751095) 
I’d say it’s probably a good idea to use an item datatype and to use a more generic property for the numerical value of it. It would avoid to bloat the item of the country as there may be many different values over time.
Proposition:
- / . It could also be two properties for the hourly and the monthly value to make stuff clearer, this represents different realities. There is also subteleties with the net and gross salaries … I think all this needs a little thought actually author TomT0m / talk page 20:02, 18 December 2018 (UTC)
- We don't actually have an "amount" property, though. Should one be created just for this? Using quantity (P1114) ("number of instances of this subject") would be misleading, I think. Are all minimum wages either delineated by hours or months? If they use a mix of whatever units of time, we presumably don't want a separate property for each. --Yair rand (talk) 19:48, 24 January 2019 (UTC)
- Support most countries have hourly or monthly minimum wages, however in Germany there is no monthly minimum wage but an hourly (please change it). Possibly use two properties as proposed by TomT0m Germartin1 (talk) 01:12, 21 December 2018 (UTC)
- Support However, I think using TomT0m proposition is a good idea. --Giovanni Alfredo Garciliano Díaz ★ diskutujo 01:50, 1 January 2019 (UTC)
- Support. Absolutely logical property.--Arbnos (talk) 23:11, 20 January 2019 (UTC)
- Comment given that TomT0m's suggestion seems popular I think the datatype and examples should be adjusted before creating this. − Pintoch (talk) 08:58, 24 January 2019 (UTC)
- Comment the samples above need a different qualifier: "valid in period" isn't meant for this. Maybe "applies to part" can do instead. --- Jura 12:29, 26 January 2019 (UTC)
- @Tohaomg: I have adjusted the units per what I interpret as TomT0m's proposal above; are you on board with this change? @Pintoch: I don't believe any datatype change is needed, quantity should work for this no? ArthurPSmith (talk) 17:55, 26 January 2019 (UTC)
- @ArthurPSmith: my understanding of TomT0m's proposal is that the property should be item-valued (not quantity-valued): the value would be an item about the minimum wage, which would itself contain statements about its value. I think this idea makes sense - we can probably add a lot of statements on items about minimum wages themselves (the values might depend on time / region / field, and we can add metadata such as which law introduced them, sitelinks). − Pintoch (talk) 23:16, 26 January 2019 (UTC)
- @Pintoch: Ah, I see he did have that suggestion, but I don't think that's practical to have an item for every case: minimum wage laws vary by detailed jurisdiction - cities and states in the US each may have their own values. But if we did go with items for minimum wage laws then I'm not sure we need this property anyway - the item for the law would surely specify the relevant jurisdiction, so we wouldn't really need the inverse property to find it. ArthurPSmith (talk) 14:10, 28 January 2019 (UTC)
- @ArthurPSmith: I lost a thread of understanding what is going on here, so do whatever you consider to be right. --Tohaomg (talk) 00:07, 27 January 2019 (UTC)
- @Tohaomg: I updated it above. Is that ok for you? It seems to be close what users actually supported. More detailed items such as Q751095 could be linked with the qualifier statement is subject of (P805) by interested contributors. --- Jura 06:22, 27 January 2019 (UTC)
- @Jura1: No, I don't think that's close to what anybody here supported except you. @TomT0m: Can you clarify what it is you were suggesting (see above discussions)? ArthurPSmith (talk) 14:04, 28 January 2019 (UTC)
- That's odd, I didn't support anything. @ديفيد عادل وهبة خليل 2, Arbnos, Germartin1: not sure why your support got ignored. --- Jura 16:25, 28 January 2019 (UTC)
- @ArthurPSmith: my understanding of TomT0m's proposal is that the property should be item-valued (not quantity-valued): the value would be an item about the minimum wage, which would itself contain statements about its value. I think this idea makes sense - we can probably add a lot of statements on items about minimum wages themselves (the values might depend on time / region / field, and we can add metadata such as which law introduced them, sitelinks). − Pintoch (talk) 23:16, 26 January 2019 (UTC)
- Support NMaia (talk) 02:30, 28 February 2019 (UTC)
- @Tohaomg, Yair rand, ديفيد عادل وهبة خليل 2, TomT0m, Germartin1: and @Giovanni Alfredo Garciliano Diaz, Arbnos, Pintoch, ArthurPSmith, NMaia: Property minimum wage (P6794)
Done. Good contributions, Ederporto (talk) 02:03, 30 May 2019 (UTC)
