Property proposal:	Generic	Authority control	Person	Organization
	Creative work	Place	Sports	Sister projects
	Transportation	Natural science	Computing	Lexeme

General

L'Humanité topic ID

Under discussion

Description	identifier for a topic on the L'Humanité website
Represents	L'Humanité (Q1137404)
Data type	External identifier
Domain	item
Example 1	French Communist Party (Q192821)→pcf
Example 2	Dominique de Villepin (Q131660)→dominique-de-villepin
Example 3	2024 United States presidential election (Q101110072)→presidentielle-americaine-2024
Expected completeness	always incomplete (Q21873886)
Formatter URL	https://www.humanite.fr/mot-cle/$1
See also	L'Humanité journalist ID (P10569)
Wikidata project	WikiProject France (Q10816832)

Motivation

Beauciup de "tag" réunissant tous les articles. – The preceding unsigned comment was added by Legonin (talk • contribs) at 06:00, September 17, 2024‎ (UTC).

Discussion

Notified participants of WikiProject France – The preceding unsigned comment was added by Legonin (talk • contribs) at 08:09, 21 September 2024 (UTC).[reply]

Notified participants of WikiProject France - re-pinging, since the previous one was unsigned (and therefore didn't work). --Lewis Hulbert (talk) 09:53, 7 October 2024 (UTC)[reply]

Support, riche idée ! Maxime 10:05, 7 October 2024 (UTC)[reply]
Support — Baidax ^💬 11:04, 7 October 2024 (UTC)[reply]
Comment pas totalement convaincu, est-ce vraiment un identifiant pérenne ? (combien y en a-t-il ? depuis combien de temps ? etc.) En plus, je vois que pour chaque mot-clef, il n'y a qu'un petit nombre d'articles les plus récents (et une ligne d'information dans le cas du PCF). Au final, je m'interroge un peu sur l'utilité de cette propriété, qu'apporte-t-elle ? Une propriété générale comme hashtag (P2572) me semble suffisant, non ? Cdlt, VIGNERON (talk) 14:07, 7 October 2024 (UTC)[reply]
@Legonin, could you please clarify the comment? Regards, ZI Jony ^(Talk) 08:52, 10 October 2024 (UTC)[reply]
Pas mal d'articles (ex. 1, 2, 3, 4, ..), pas mal de sujet couverts (regarder les tags en bas des articles). Permet de savoir l'actu de l'époque sur ces sujets et d'en savoir plus. Legonin (talk) 17:22, 10 October 2024 (UTC)[reply]
@VIGNERON, would you like to give your opinion? Regards, ZI Jony ^(Talk) 06:56, 18 October 2024 (UTC)[reply]
Still not full convinced that this property is useful or needed, I guess I'm Weak oppose. Cheers, VIGNERON (talk) 07:42, 18 October 2024 (UTC)[reply]
Support — Rémi sim (talk) 22:21, 14 October 2024 (UTC)[reply]

‎beer style

Under discussion

Description	classification of a beer based on its style
Represents	beer style (Q1998962)
Data type	Item
Domain	beer (Q44)
Allowed values	subclasses or instances of beer style (Q1998962)
Example 1	Hertog Jan Grand Prestige (Q2176488) → barley wine (Q808329)
Example 2	Coors Light (Q5168060) → light beer (Q1814622)
Example 3	Grolsch 0.0% (Q61043304) → low-alcohol beer (Q524679)
Example 4	Brand IPA (Q19884261) → India Pale Ale (Q1543214)
See also	beer bitterness (P6088), beer color (P6089)

Motivation

Beer style is a key classification for differentiating beers by their characteristics, complementing existing properties like beer color and bitterness. – The preceding unsigned comment was added by Mitsjol (talk • contribs) at 10:43, September 30, 2024‎ (UTC).

Discussion

Comment This seems related to the proposal here: Wikidata:Requests for comment/object vs design class vs functional class for manufactured objects - it sounds like your intent is to replace overspecifity of subclass of (P279)/instance of (P31) in this domain? ArthurPSmith (talk) 20:02, 30 September 2024 (UTC)[reply]
Yes, that's correct, the intent is to reduce the overspecificity of subclass of (P279) and instance of (P31) by introducing a clear "beer style" property, similar to cuisine (P2012) for food or genre (P136) for media. Mitsjol (talk) 07:52, 1 October 2024 (UTC)[reply]
Oppose on those grounds, instance of (P31) and subclass of (P279) are sufficient, we don't need special subclass items for types of object. Vicarage (talk) 17:56, 7 October 2024 (UTC)[reply]
Comment Why do we need this property for beer specifically? Why not "alcohol style" or "beverage style"? The other beer properties in "See Also" have quantity values for a specific standard, so it would make sense for them to exist. -wd-Ryan (Talk/Edits) 21:39, 30 September 2024 (UTC)[reply]
You raise good points about beverage classification. My proposal for a "beer style" property stems from the wide variety of distinct beer styles. However, I recognize the value in exploring broader categories like "alcohol style" or "beverage style." That said, using "alcohol style" for instances of vodka, for example, may not be beneficial due to its limited recognized styles. Mitsjol (talk) 09:18, 1 October 2024 (UTC)[reply]
Grolsch 0.0% is indeed a low-alcohol beer; but that is not its style, which is Pilsner. Guinness 0.0% is a stout. The two beers are not of the same style. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 17:42, 7 October 2024 (UTC)[reply]
I think a shared property with food would be more useful, since we have quite a few of type of food or dish (Q19861951): type of pizza (Q116392487), type of cheese (Q3546121), type of cooked meat (Q129175686). There's also type of drink (Q116861721) for drinks, but no specific classes have been created for this yet, and the metaclass itself doesn't have much use as well yet. Although I can find lots of items with description "type of cocktail" and the like, so there is a great potential to extend both branches. And I think we can distinguish basic types for all of them - sort of genres or broad groups. Well, we can use "genre" for this purpose, but I'm not sure if it's really appropriate for food. Solidest (talk) 07:16, 8 October 2024 (UTC)[reply]
subclass of (P279) could be used with all of those. No need for a property tree Vicarage (talk) 09:09, 8 October 2024 (UTC)[reply]
Sorry, I didn't word what I meant precisely. That the new shared property could be used to specify food types for branded food\beverages and such. Something that is not a specific type, but rather an implementation of a specific sort. For example, Mukuzani (Q4306822) -> sort/type -> red dry wine; Bavaria Pilsener (Q13436879) -> sort/type -> pilsner (Q152281); César Régalis (Q23211927) -> sort/type -> sheep milk cheese (Q1411808); Coca-Cola Zero (Q937783) -> sort/type -> diet cola (Q50425277). At the moment the link between brands and meal/beverage types is specified via p31 or p279 and I'm not sure if this is correct for branded reproduction of a particular type. For example, here you can see how often p31/p279 of "beer style" are used in p31: https://w.wiki/BThF . These are mostly sorts of beer used by the brands. It would be much more orderly to mark all of them with the class "beverage brand" or something like that. Using multiple types in p31 is not really database friendly, and continuing the type hierarchy through p279 with brands is definitely clogging it up. You may have hundreds of varieties of one product, for example cheese. And you may have 2-3 varieties each placed in p31 for a particular cheese product under its own name, whereas it's just a branded reproduction of a particular type of cheese. If we have hundreds of types filled randomly in p31 or p279 - it's definitely less usable than if it was just p31 = "branded food" or "branded dairy product" or "branded cheese". And at this point, the hierarchy of types and sorts is already heavily cluttered with commercial branded reproductions. Compared to other realms, it's like if you use music genres in p31/p279 for individual songs - something the Music project dealt with by creating a single metaclass. And, as I said, we can use "genre" to refer to types of branded food, but that seems like a stretch for the realm of food. Solidest (talk) 15:07, 8 October 2024 (UTC)[reply]
See the RFC mentioned at the top which explains how product_model is currently used. It works for brands without the need for extra properties. Your approach goes against that. Vicarage (talk) 20:13, 8 October 2024 (UTC)[reply]

‎Department of Defense Identification Code

Ready ^Create

Description	identification code for ordnance of the United States military
Represents	Department of Defense Identification Code (Q130394184)
Data type	External identifier
Domain	weapon model (Q15142894)
Allowed values	([A-Z]\d{3}\|[A-Z]{2}\d{s})
Example 1	BLU-109B/B (Q130394989)→EC72
Example 2	BLU-109C/B (Q130394999)→ED49
Example 3	M718A1 (Q130411460)→D515
Example 4	M741A1 (Q130411473)→D514
Source	https://web.archive.org/web/20240930063511/https://www.quantico.marines.mil/portals/147/docs/safety/yellow%20book%20rev%2019%20dated%20february%202021.pdf
Planned use	Uniquely identify variants of models of American manufactured bomb, missile, rocket, small arms munitions, etc by DODIC and associated NSN and other labels supplied in the "Yellow Book".
Expected completeness	eventually complete (Q21873974)
Applicable "stated in"-value	Joint Hazard Classification System (Q130394198)
Single-value constraint	yes
Distinct-values constraint	yes

Motivation

Wikipedia and Wikidata have only very basic information on military ordnance (missiles, bombs, rockets, small arms munitions, tank and artillery rounds, etc) even though publications such as the Yellow Book and public NSN part information provides detail on exact variants of ordnance. For example, Wikipedia may have a page on a "Mk 82 bomb" but this is a highly conflated item which may include different variants of a bomb casing (with varying amounts of explosive) and with different guidance systems attached. Applying a DODIC code allows these variants to be listed out as separate Wikidata items, avoiding conflation of topics. --Dhx1 (talk) 06:29, 2 October 2024 (UTC)[reply]

Discussion

@Dhx1: your examples should have Wikidata items on the left, not string values, can you fix? ArthurPSmith (talk) 23:03, 3 October 2024 (UTC)[reply]
Examples changed to include existing items. --Dhx1 (talk) 02:23, 4 October 2024 (UTC)[reply]
ArthurPSmith, would you like to give your opinion? Regards, ZI Jony ^(Talk) 08:42, 10 October 2024 (UTC)[reply]
@Dhx1: Hmm, so you just added these items as examples? Do we actually have any existing items to which this identifier would apply? If not I don't see it as being very useful. ArthurPSmith (talk) 20:40, 14 October 2024 (UTC)[reply]
Wikidata currently only knows a few items (other than many I have added to date) for variants of US ordnance. However, English Wikipedia (others too) have extensively listed and provided some documentation of the often significant differences in variants, for example https://en.wikipedia.org/wiki/Tomahawk_(missile_family)#Variants has a list of variants most of which I have added Wikidata items for. The variants are also something which Wikimedia Commons cares about, for example, https://commons.wikimedia.org/wiki/Category:BGM-109_Tomahawk_Block_IV and https://commons.wikimedia.org/wiki/Category:BGM-109G_Gryphon versus https://commons.wikimedia.org/wiki/Category:BGM-109_Tomahawk or also https://commons.wikimedia.org/wiki/Category:AMRAAM-ER and https://commons.wikimedia.org/wiki/Category:CATM-120C and https://commons.wikimedia.org/wiki/Category:SLAMRAAM versus https://commons.wikimedia.org/wiki/Category:AIM-120_AMRAAM Dhx1 (talk) 21:59, 15 October 2024 (UTC)[reply]
Support OK, I guess the specific details are important for identification. I hope new items created based on this will be well structured and linked to their related items. ArthurPSmith (talk) 17:29, 18 October 2024 (UTC)[reply]

Comment If this is limited to ordnance, shouldn't ordnance be in the name of the property? AdamSeattle (talk) 04:04, 26 October 2024 (UTC)[reply]
Comment "DODIC" is the official name of the identifier that people interested in this property would search for. It is unhelpfully non-descriptive as many military acronyms are. Rather than the name being clear in purpose, the description of the property (which Wikidata controls) makes clear what this identifier achieves. Dhx1 (talk) 22:49, 28 October 2024 (UTC)[reply]
Comment Is the source pdf a complete list, if not how will other values be found? How many values are expected in total?
Comment It's an ever expanding list. There is a database YellowBook.sqlite as part of a now-defunct Android app YellowBook v2.1.0 (APK still available online on non-official app stores) which lists 5288 DODIC codes per query "SELECT COUNT(*) FROM (SELECT DODIC FROM MunitionsHazardClass GROUP BY DODIC);". Future changes would have to be obtained through means such as being mentioned in official budget papers for Army, Air Force, Navy, Marines, etc for the type of ordnance budgeted to be procured, or a new app or new PDF publication. --Dhx1 (talk) 22:46, 28 October 2024 (UTC)[reply]

Support proposer has a good plan. Vicarage (talk) 03:45, 29 October 2024 (UTC)[reply]

Libération topic ID

Done: Libération topic ID (P13113) (Talk and documentation)

Description	identifier for a topic on the website of Libération
Represents	Libération (Q13717)
Data type	External identifier
Domain	item
Example 1	Gabriel Attal (Q30339350)→gabriel-attal
Example 2	flood (Q8068)→inondation
Example 3	Nobel Prize (Q7191)→prix-nobel
Expected completeness	always incomplete (Q21873886)
Formatter URL	https://www.liberation.fr/tags/$1/
See also	Libération journalist ID (P10575)
Wikidata project	WikiProject France (Q10816832)

Motivation

Comme les propriétés correspondant aux mots-clés des sites web des grands périodiques français sont progressivement ajoutées (Le Monde ID (P5558), Le Figaro tag ID (P6621), une proposition récente pour L'Humanité), il est cohérent d'ajouter celle pour le site web de Libération. Les articles répertoriés sont certes récents à l'année, mais offrent toutefois une perspective sur le cœur de l'actualité médiatique. Certaines pages proposent, en plus, une phrase, voire un paragraphe, de présentation du sujet. — Baidax ^💬 14:48, 7 October 2024 (UTC)[reply]

Discussion

Notified participants of WikiProject France

Support également JDD (ex.), Mediapart tag ID (P6813), L'Express person ID (P6620), Le Parisien tag ID (P6622), Courrier international topic ID (P5551), Le Monde diplomatique subject ID (P3612), France 24 topic ID (French) (P9346) et autres langues, Objectif Gard topic ID (P6277), Mediapart tag ID (P6813), La Croix (ex.), Ouest-France (ex.), 20 Minutes (France, ex.), les échos (ex.), L'Opinion (ex.), Le Point (ex.), Le Canard Enchainé (ex.), Télérama (ex.), Capital (ex.), L'équipe sujet (a ne pas confondre avec les fiches, ex.), Marianne (ex., la plupart visible dans les rubriques dans le menu à dérouler), Le Pèlerin (ex., idem), Challenges (ex.), La Vie (ex.), Les Inrocks (ex.), Paris Match (ex.), Elle (ex.), L'alsace (ex.), Le Berry (ex.), Le Dauphiné libéré (ex.)...

@Legonin: le problème avec Le JDD, c'est qu'il propose plusieurs autres formats avec des sous-pages, par exemple lejdd.fr/Tags/Parti-socialiste ou lejdd.fr/dossiers/afrique. — Baidax ^💬 12:48, 8 October 2024 (UTC)[reply]

On pourrait résoudre ça avec la possibilité de mettre ses sous pages.Legonin (talk) 16:43, 8 October 2024 (UTC)[reply]

@Baidax, Legonin:

Done: Libération topic ID (P13113). --Lewis Hulbert (talk) 13:35, 31 October 2024 (UTC)[reply]

identifiant Les Inrockuptibles d'un sujet

Under discussion

Description	identifiant d'un sujet sur le site Les Inrockuptibles (fr) – (Please translate this into English.)
Represents	Les Inrockuptibles (Q2758142)
Data type	External identifier
Domain	item
Example 1	Donald Trump (Q22686)→donald-trump
Example 2	Netflix (Q907311)→netflix
Example 3	2024 Cannes Film Festival (Q119141934)→cannes-2024
Example 4	Yelle (Q18574071)→yelle
Example 5	Anatomy of a Fall (Q117037697)→anatomie-dune-chute
Example 6	Emily in Paris (Q64584978)→emily-in-paris
Expected completeness	always incomplete (Q21873886)
Formatter URL	http://www.lesinrocks.com/tag/$1
Wikidata project	WikiProject France (Q10816832)

Motivation

Plein d'IDs et articles très intéressant. Pas mal de sujet/tags de journaux proposé et déjà sur Wikidata. – The preceding unsigned comment was added by Legonin (talk • contribs) at 07:15, 16 October 2024 (UTC).[reply]

Discussion

Notified participants of WikiProject France – The preceding unsigned comment was added by Legonin (talk • contribs) at 07:15, 16 October 2024 (UTC).[reply]

VIGNERON
Ayack
Ash Crow
Tubezlob
PAC2
Thierry Caro
Pymouss
Alphos
GAllegre
Jean-Frédéric
Manu1400
Marianne Casamance
Nattes à chat
Pierre André
Bouzinac
Jsamwrites
Baidax
LearnKnowGive1
Mathieu Kappler
Daieuxetdailleurs
Archives nationales DJI
Jmax
LearnKnowGive1
Koxinga
Maxime
Framawiki
Legonin
Rémi sim
Notified participants of WikiProject France - repinging, signing is required to send pings. --Lewis Hulbert (talk) 00:06, 17 October 2024 (UTC)[reply]
Support. Maxime 05:47, 17 October 2024 (UTC)[reply]
Oppose not convinced, this is a tag more than an identifier (which probably means it won't be perennial). I'm not really sure what value it brings. Cheers, VIGNERON (talk) 06:18, 17 October 2024 (UTC)[reply]
Support Rémi sim (talk) 07:20, 17 October 2024 (UTC)[reply]
Oppose I agree with VIGNERON. -Ash Crow (talk) 09:23, 17 October 2024 (UTC)[reply]
Support. This proposal aligns with a series of other identifiers of the same kind, giving the articles of a sufficiently important periodical on a given theme. As the theme itself is stable enough, the identifier will, in practice, be perennial, even though it is not numerical, and it is assumed to be unique for each theme. — Baidax ^💬 12:50, 18 October 2024 (UTC)[reply]

‎European Legislation Identifier (EU)

Under discussion

Description	EU legislation identifier for documents published by the EU
Data type	External identifier
Example 1	directive on open data and the re-use of public sector information (Q98399993)→dir/2019/1024/oj
Example 2	Capital Requirements Directive (Q1034661)→dir/2013/36/oj
Example 3	Solvency II Directive (Q1255619)→dir/2009/138/oj
Source	https://en.wikipedia.org/wiki/European_Legislation_Identifier https://eur-lex.europa.eu/eli-register/about.html https://op.europa.eu/en/publication-detail/-/publication/8159b75d-5efc-11e8-ab9c-01aa75ed71a1
Formatter URL	http://data.europa.eu/eli/$1
Robot and gadget jobs	Import from Eur-lex by So9qBot is planned for existing items.
Single-value constraint	yes
Distinct-values constraint	yes

Motivation

This is an important identifier for EU legislation.--So9q (talk) 10:43, 18 October 2024 (UTC)[reply]

Discussion

Support Arpyia (talk) 08:36, 19 October 2024 (UTC)[reply]
What makes you think that this is the identifer for the document and not 32013L0036? Does the European Union have a documentation that says that "dir" is part of the name of the identifer? ChristianKl ❪✉❫ 20:26, 21 October 2024 (UTC)[reply]
It is the document type in the implementation by EU institutions. See https://op.europa.eu/en/publication-detail/-/publication/8159b75d-5efc-11e8-ab9c-01aa75ed71a1. French ELI ids look like this: http://legifrance.gouv.fr/eli/loi/2014/10/13/2014-1170/jo/texte and the general prefix seems to be: {typedoc}/{year}/{natural_number}/ followed by implementation specific endings e.g. "http://data.europa.eu/eli/{typedoc}/{year}/{natural_number}/oj <- canonical ELI to identify a directive or regulation in EU" So9q (talk) 09:14, 22 October 2024 (UTC)[reply]

Notified participants of WikiProject European Union, @Ainali, Belteshassar: Redoing the ping because it requires a signature after it. Samoasambia ✎ 14:33, 22 October 2024 (UTC)[reply]

Weak oppose I'm not really sure why would we need this property because we already have CELEX number (P476) (it's the "32013L0036" ChristianKl mentioned) and full work available at URL (P953) where we could add the ELI URL. P953 is useful because it is used e.g. by Template:Cite Q (Q22321052). Samoasambia ✎ 14:33, 22 October 2024 (UTC)[reply]

European Legislation Identifier is basically a common URL and metadata format for laws in EU member states and the EU itself. Here's a few examples: http://data.finlex.fi/eli/sd/1734/4, http://data.europa.eu/eli/dir/2013/36/oj, https://www.legifrance.gouv.fr/eli/loi/2023/4/14/2023-270/jo/texte, https://www.retsinformation.dk/eli/lta/2014/1603. Some of the URLs are actual pages and some of them just redirects. Unfortunately there does not seem to be any central domain from which you could be redirected to the right national database, so ELI properties would have to be done separately for each country (and the EU itself). Samoasambia ✎ 15:09, 22 October 2024 (UTC)[reply]

French environmental protection classification

Under discussion

Description	Industrial or agricultural operations generating risks to health and the environment are regulated in France. The various risks are organized into headings in the nomenclature of installations classified for environmental protection. The dangers, pollution and nuisances of each operation are listed by public authorities.
Data type	Item
Domain	Q3151661
Allowed values	Q125631811
Example 1	Raffinerie de Feyzin (Q3417389) → Q125635166
Example 2	Chemical factory, Balan (Q16511667) → Q125639692
Example 3	ArcelorMittal Dunkerque (Q21164927) → Q125636796
Example 4	Q130526075 → Q125635500
Example 5	Q123267504 → Q125635414

Motivation

Cette propriété est importante pour recenser les dangers pour la santé et l'environnement associés aux activités économiques. Une propriété dédiée permettra d'ajouter les qualificatifs pertinents (dates, références, etc.) pour chaque risque. Arpyia (talk) 08:53, 19 October 2024 (UTC)[reply]

Notified participants of WikiProject France

Discussion

Notified participants of WikiProject France. Ping needs a signature to work. Samoasambia ✎ 14:07, 22 October 2024 (UTC)*[reply]

Support — Baidax ^💬 14:19, 22 October 2024 (UTC)[reply]
Comment Arpyia is there no other property that could be used? this proposal seems too specific without reason. If not, why not create a more general property? Something like "industrial classification" would make more sense. Also, about ICPE, 2. we should model the "régime" before the "rubrique", this is way more important ; the SEVESO status would be also more useful. Cheers, VIGNERON (talk) 15:20, 22 October 2024 (UTC)[reply]
Oppose en l'état, car trop spécifique. Maxime 15:31, 22 October 2024 (UTC)[reply]
Comment C'est pas plutôt une classe qu'une propriété ? Alphos (talk) 23:18, 22 October 2024 (UTC)[reply]

‎operating cost

Under discussion

Description	ongoing recurring cost for operating or using an object
Represents	operating cost (Q831940)
Data type	Quantity
Domain	activity (Q1914636), architectural structure (Q811979), facility (Q13226383), artificial object (Q16686448)
Allowed values	0-10000000000000
Allowed units	currency (Q8142) per unit of time (USD/year, EUR/month, etc)
Example 1	F-35A Lightning II (Q17519093)→USD$6.6m/year
Example 2	swimming pool (Q1501)→USD$1450/year
Example 3	Tesla Model 3 (Q7705507)→USD$623/year
Expected completeness	always incomplete (Q21873886)
See also	capital cost (P2130)

Motivation

capital cost (P2130) already captures the initial capital cost of an object (building, vehicle, etc) but there is no equivalent property for capturing the recurring ongoing costs of maintaining and operating an object.

Qualifiers such as determination method or standard (P459) and valid in period (P1264) would be very important to use with this property as there are many ways to calculate an operating cost for equipment or a building. In the Tesla Model 3 example provided (USD$623/year) this was only an estimate valid at a point in time, for the first five years of ownership of a car, and excluding a number of other operating costs such as electricity and insurance.

--Dhx1 (talk) 03:22, 25 October 2024 (UTC)[reply]

Discussion

Weak support A week support from me, because I think it needs a qualifier of sort. I think the cost of annual ownership can benefit from qualifier of a country, region, city, where it's owned. For example, cost of ownership of Tesla car in Norway and US differ tremendously. Also, I think it would benefit from more time periods like 5 year and so on, but I'm not certain about it. --David Osipov (talk) 12:11, 26 October 2024 (UTC)[reply]
Comment The time span should be specified using duration (P2047) qualifier; otherwise you need to create items for every combination of currencies with day/week/month/year, which would be a nightmare for editors and data consumers. Dexxor (talk) 17:57, 27 October 2024 (UTC)[reply]

‎effective life of asset

Under discussion

Description	duration of time which an object/asset is expected to be used before needing to be disposed of or replaced
Data type	Quantity
Domain	artificial object (Q16686448)
Allowed units	unit of time (Q1790144) or any other useful unit of measurement for lifespan of an object (kilometres traveled, engine hours, flight hours, etc)
Example 1	CT scanner (Q128486784)→10 years
Example 2	combine harvester (Q26886)→12 years
Example 3	laptop (Q3962)→2 years
Source	Example: https://www.ato.gov.au/law/view/document?DocID=ITD/EF20151C8/00001&PiT=99991231235958
Expected completeness	always incomplete (Q21873886)
See also	discontinued date (P2669), service retirement (P730), life expectancy (P2250)

Motivation

There is no property existing for the expected useful lifespan of an artificial object (such as a machine, tool, vehicle or building) after which it is expected the object needs replacing due to wear and tear, obsolescence, lack of support and lack of maintainability.

This concept is useful in finance for determining the current value of a purchased asset for taxation and financial reporting reasons. It is also useful for consumer items such as toothbrushes, phones, computers which are replaced regularly for reasons of wear and tear and obsolescence of technology.

--Dhx1 (talk) 03:23, 25 October 2024 (UTC)[reply]

Discussion

Oppose This varies per product and also the lifespan of a laptop obviously is not just 2 years. --Prototyperspective (talk) 09:46, 25 October 2024 (UTC)[reply]
My thought with this property proposal is that qualifiers such as determination method or standard (P459) and the references are critical. This property could be used 10 times on laptop (Q3962) all with different sources such as standards for asset management and taxation depreciation schedules of different governments. Thus the users of this property have to pick and choose whichever of these 10 statements is most useful to them. For example, the life of a laptop (Q3962) could be 5 years after first product release until it is typically expected to be obsolete and would be scrapped, could by 3 years as determined by continuous use causing battery degradation and wear and tear typically requiring replacement, could differ in expectations between a government in country X versus country Y depending on affluence of the country and wiliness to adopt newer technologies and scrap older ones seen as obsolete, etc. Dhx1 (talk) 12:42, 25 October 2024 (UTC)[reply]
I don't know of anybody who would replace a laptop after just 5 years. Moreover, the planned obsolescence of laptops, smartphones, several plastic products, and so on are a major problem and WD should not normalize or reinforce that by suggesting this is how long these products inherently last. They can last much longer, for example via standardized replacement parts + requirement to be somewhat modular and having parts (such as battery) offered individually. Prototyperspective (talk) 12:13, 26 October 2024 (UTC)[reply]
Weak support It's connected to depreciation of an item, which is a correct accounting notion. But weak support from me, because it needs to have qualifiers like Determination method, Usage frequency of some sort. I would suggest looking up various calculation methods of the effective life of a depreciating asset, writing them out and starting to propose these qualifiers along with this property. Without these qualifiers, the property alone is deceiving. --David Osipov (talk) 12:18, 26 October 2024 (UTC)[reply]
Oppose something like "depreciation period" would be a better way to store information on the legal depreciation period than a more generally named property. ChristianKl ❪✉❫ 09:01, 31 October 2024 (UTC)[reply]

‎ITV News topic ID

Under discussion

Description	identifier for a topic on the ITV News website
Represents	ITV News (Q4189762)
Data type	External identifier
Example 1	Europe (Q46)→europe
Example 2	Boris Johnson (Q180589)→boris-johnson
Example 3	M5 motorway (Q1824663)→m5-motorway
Example 4	Wales (Q25)→wales
Example 5	science (Q336)→science
Expected completeness	always incomplete (Q21873886)
Formatter URL	https://www.itv.com/news/topic/$1
URL match pattern	^https?:\/\/(?:www\.)?itv\.com\/news\/topic\/([a-z0-9]+) web page title extract pattern (P10999) ^ITV\ News\ :\ The\ Latest\ (.+)\ News$
See also	Guardian topic ID (P3106), BBC News topic ID (P6200), Sky News topic ID (P11632)
Single-value constraint	yes
Distinct-values constraint	yes

Motivation

A Wikidata property to identify news website topics (Q105946994) for ITV News (Q4189762), one of the most significant news sources in the United Kingdom.

The IDs seem stable, going back to at least 2012. --Lewis Hulbert (talk) 12:44, 25 October 2024 (UTC)[reply]

Discussion

Jheald (talk) 09:48, 11 January 2015 (UTC) PKM (talk) 19:09, 11 January 2015 (UTC) Fabian Tompsett (WMUK) (talk) 08:51, 12 January 2015 (UTC) Charles Matthews (talk) 09:27, 15 January 2015 (UTC) Filceolaire (talk) 16:27, 4 February 2015 (UTC) Danrok (talk) 13:01, 19 October 2015 (UTC) Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits JJBullet (talk) 10:55, 27 June 2019 (UTC) Yirba (talk) 09:53, 10 August 2023 (UTC) Lewis Hulbert (talk) 12:58, 25 October 2024 (UTC)[reply]
Notified participants of WikiProject UK and Ireland. --Lewis Hulbert (talk) 12:57, 25 October 2024 (UTC)[reply]

‎Toki Pona headnoun

Under discussion

Description	Toki Pona common noun for which the name serves as a proper modifier
Data type	Lexeme
Allowed values	language=tok
Example 1	Sonja Lang (Q12854)Toki Pona headnounjan (L220656)
Example 2	Tamzin Hadasa Kelly (Q127401579)Toki Pona headnounwan (L220805)
Example 3	United States of America (Q30)Toki Pona headnounma (L220703)

Motivation

First of all, no, I don't know why there's an item about me, but I might as well use it as an example! So, in Toki Pona, names only ever serve as adjectives. So even though my name is Tansin, one can't refer to me as just that. Instead, a name must modify a common noun, which essentially serves as Toki Pona's own "instance of" statement. So it's not Mewika, but rather ma Mewika 'country called Mewika'. The ma there, is not however semantically part of the name of the country, and contextually could be replaced with some other word (for instance, a critic of the U.S. could say ike Mewika, 'bad thing called Mewika').

This common noun is called a headnoun. Some people refer to themselves with a headnoun other than jan 'person', which thereby functions as something between a courtesy title and preferred pronoun. For instance, I usually use wan 'union' to refer to myself, and that's the name I'm credited under in the acknowledgments to Toki Pona Dictionary (Q108617357). My item thus gives a name (P2561) of wan Tansin, but that's akin to saying my name in English is "person named Tamzin". One solution would be to simply remove wan, but that word is required information to understand how to refer to me in Toki Pona.

My understanding is that language-specific properties have been approved in the past, e.g. Vietnamese middle name (P8500) and second family name in Spanish name (P1950). -- Tamzin^{[cetacean needed]} (they|xe) 23:18, 27 October 2024 (UTC)[reply]

Discussion

Comment Hmm, this seems like it should be attached to the "class", not the instances. Especially if several different ones could be used (as in your "ma"/"ike" example). ArthurPSmith (talk) 21:18, 29 October 2024 (UTC)[reply]
Vietnamese middle name (P8500) and second family name in Spanish name (P1950) exist because there's semantic content that's expressed. second family name in Spanish name (P1950) is about expressing that a name is inherited from the mother. Can you explain why you think name (P2561) doesn't work here and what you think the property would add? ChristianKl ❪✉❫ 08:41, 31 October 2024 (UTC)[reply]

‎Provides data for property

Under discussion

Description	the dataset associated with this external id usually contains data applicable to this other wikidata property
Data type	Property
Domain	external id properties
Example 1	Deku Deals ID (P8364)→price (P2284)
Example 2	MyWaifuList character ID (P13031)→height (P2048)
Example 3	IMDb ID (P345)→title (P1476)
Example 4	Fandom article ID (P6262)→unknown
See also	stated in (P248)

Motivation

I was asked by @Kirilloparma: to save certain references not with reference URL (P854) but instead (for instance) ‎Playdate Catalog ID (P12125) in Wikidata:Tools/Wikidata for Web.

My concerns regarding this was that, I cannot automatically distinguish between data provided by the database item behind ‎Playdate Catalog ID (P12125) and information that just happens to be found under the same url.

Let's say the footer of a page might contain an email address, that is not related to the person reviewed in the page.

Or isbnsearch.org would tell me the title of a book but I wouldn't use ISBN-13 (P212) as the reference.

Now if I had an indication that a url that resolves to (for instance) an IMDb ID (P345) usually holds the information that applies to title (P1476), then I could make the assumption that it would make for a fitting reference statement when extracting this property from the url.

This information could be useful for other tools like:

A tool that tells you that an item should have a title and that you could find it on the IMDB
A tool that highlights a reference that might be faulty because it occours in an unusual context. Let's say Deku Deals ID (P8364) is used on a date of birth (P569) statement.

If an ID points to a wiki, that could hold all kinds of statements, it should be set to unknown.

Discussion

@Addshore: –Shisma (talk) 10:00, 28 October 2024 (UTC)[reply]

Support I quite like the idea, and it falls in line with what I am trying to do with more visual cues on items for the viability of references / sources and notability ·addshore· ^{talk to me!} 10:23, 28 October 2024 (UTC)[reply]

Question Same as supported metadata (P8203)? Midleading (talk) 15:06, 28 October 2024 (UTC)[reply]

I'm not sure what this is meant for but the datatype is different. So it's definitely not the same. – Shisma (talk) 15:14, 28 October 2024 (UTC)[reply]

supported metadata (P8203) can be used to tell what kind of data a database stores, and not being limited to data that Wikidata has a property for. The example PubMed ID (Q2082879)supported metadata (P8203)digital object identifier (Q25670) is no different from the examples given here except that it accepts items which can be created by anyone. Midleading (talk) 04:03, 29 October 2024 (UTC)[reply]

Support -wd-Ryan (Talk/Edits) 16:56, 28 October 2024 (UTC)[reply]

Support Knowing the data a property may hold would be helpful for sourcing statements on items. --Lewis Hulbert (talk) 01:03, 29 October 2024 (UTC)[reply]

Support Useful. --Prototyperspective (talk) 12:14, 29 October 2024 (UTC)[reply]

Resistance in Belgium ID

Under discussion

Description	identifier of persons, administrative areas, resistance organizations of world war 2,... on https://data.arch.be/
Represents	no label (Q130564724)
Data type	External identifier
Domain	human (Q5), organization (Q43229), country (Q6256)
Example 1	Groupe G (Q1767773)→Q3790
Example 2	Walthère Dewé (Q631073)→Q7400
Example 3	Ixelles - Elsene (Q208713)→Q104
Example 4	Belgium (Q31)→Q5
Source	https://data.arch.be/, https://query.data.arch.be/,
Planned use	Add the identifier to already created Wikidata Qid's.
Expected completeness	always incomplete (Q21873886)
Formatter URL	https://data.arch.be/wiki/Item:$1
Country	Belgium (Q31)
Applicable "stated in"-value	Q130564724
Single-value constraint	yes
Wikidata project	WikiProject World War II (Q10653810)

Motivation

Resistance in Belgium is a platform that makes it possible to do research on the resistance in Belgium during the Second World War.
Comment: This database contains mostly persons, but most of them are only known in this database (Wikidata:Notability). That's why I said in the 'planned use' section that I will only use the ID for already created Wikidata QIDs. – The preceding unsigned comment was added by RVA2869 (talk • contribs) at 10:51, 28 October 2024 (UTC).[reply]

Discussion

Wikidata:Property proposal/Generic

See also

General

L'Humanité topic ID

Motivation

Discussion

‎beer style

Motivation

Discussion

‎Department of Defense Identification Code

Motivation

Discussion

Libération topic ID

Motivation

Discussion

identifiant Les Inrockuptibles d'un sujet

Motivation

Discussion

‎European Legislation Identifier (EU)

Motivation

Discussion

French environmental protection classification

Motivation

Discussion

‎operating cost

Motivation

Discussion

‎effective life of asset

Motivation

Discussion

‎ITV News topic ID

Motivation

Discussion

‎Toki Pona headnoun

Motivation

Discussion

‎Provides data for property

Motivation

Discussion

Resistance in Belgium ID

Motivation

Discussion

Navigation menu

Search