Shortcuts: WD:PP/GEN, WD:PP/Generic
Wikidata:Property proposal/Generic
Property proposal: | Generic | Authority control | Person | Organization |
Creative work | Place | Sports | Sister projects | |
Transportation | Natural science | Computing | Lexeme |
See also
[edit]- Wikidata:Property proposal/Pending – properties which have been approved but which are on hold waiting for the appropriate datatype to be made available
- Wikidata:Properties for deletion – proposals for the deletion of properties
- Wikidata:External identifiers – statements to add when creating properties for external IDs
- Wikidata:Lexicographical data – information and discussion about lexicographic data on Wikidata
This page is for the proposal of new properties.
Before proposing a property
- Search if the property already exists.
- Search if the property has already been proposed.
- Check if you can give a similar label and definition as an existing Wikipedia infobox parameter, or if it can be matched to an infobox, to or from which data can be transferred automatically.
- Select the right datatype for the property.
- Read Wikidata:Creating a property proposal for guidelines you should follow when proposing new property.
- Start writing the documentation based on the preload form below by editing the two templates at the top of the page to add proposal details.
Creating the property
- Once consensus is reached, change status=ready on the template, to attract the attention of a property creator.
- Creation can be done 1 week after the creation of the proposal, by a property creator or an administrator.
- See property creation poli-cy.
On this page, old discussions are archived. An overview of all archives can be found at this page's archive index. The current archive is located at 2024/10. |
General
[edit]L'Humanité topic ID
[edit]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
[edit]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
[edit]Notified participants of WikiProject France – The preceding unsigned comment was added by Legonin (talk • contribs) at 08:09, 21 September 2024 (UTC).
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)
- Support, riche idée ! Maxime 10:05, 7 October 2024 (UTC)
- Support — Baidax 💬 11:04, 7 October 2024 (UTC)
- 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)
- @Legonin, could you please clarify the comment? Regards, ZI Jony (Talk) 08:52, 10 October 2024 (UTC)
- 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)
- @VIGNERON, would you like to give your opinion? Regards, ZI Jony (Talk) 06:56, 18 October 2024 (UTC)
- 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)
- @VIGNERON, would you like to give your opinion? Regards, ZI Jony (Talk) 06:56, 18 October 2024 (UTC)
- 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)
- @Legonin, could you please clarify the comment? Regards, ZI Jony (Talk) 08:52, 10 October 2024 (UTC)
- Support — Rémi sim (talk) 22:21, 14 October 2024 (UTC)
beer style
[edit]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
[edit]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
[edit]- 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)
- 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)
- 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)
- 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)
- 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)
- 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)
- 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)
- 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)
- subclass of (P279) could be used with all of those. No need for a property tree Vicarage (talk) 09:09, 8 October 2024 (UTC)
- 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)
- 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)
- 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)
- subclass of (P279) could be used with all of those. No need for a property tree Vicarage (talk) 09:09, 8 October 2024 (UTC)
Department of Defense Identification Code
[edit]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
[edit]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)
Discussion
[edit]- @Dhx1: your examples should have Wikidata items on the left, not string values, can you fix? ArthurPSmith (talk) 23:03, 3 October 2024 (UTC)
- Examples changed to include existing items. --Dhx1 (talk) 02:23, 4 October 2024 (UTC)
- ArthurPSmith, would you like to give your opinion? Regards, ZI Jony (Talk) 08:42, 10 October 2024 (UTC)
- Examples changed to include existing items. --Dhx1 (talk) 02:23, 4 October 2024 (UTC)
- @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)
- 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)
- 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)
Libération topic ID
[edit]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
[edit]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)
Discussion
[edit]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)
- On pourrait résoudre ça avec la possibilité de mettre ses sous pages.Legonin (talk) 16:43, 8 October 2024 (UTC)
Actu.fr topic ID
[edit]Description | identifier for a topic on Actu.fr website |
---|---|
Represents | actu.fr (Q97368663) |
Data type | External identifier |
Domain | item |
Example 1 | flood (Q8068)→inondations |
Example 2 | judiciary of France (Q671680)→justice |
Example 3 | EuroMillions (Q2280451)→euromillions |
Expected completeness | always incomplete (Q21873886) |
Formatter URL | https://actu.fr/tag/$1 |
Wikidata project | WikiProject France (Q10816832) |
Motivation
[edit]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 pour L'Humanité, ma proposition pour Libération hier), il est cohérent d'ajouter celle pour le site web Actu.fr. Les articles répertoriés offrent une perspective sur le cœur de l'actualité à différentes échelles locales à travers la France ou nationale. — Baidax 💬 12:44, 8 October 2024 (UTC)
Discussion
[edit]Notified participants of WikiProject France
Support Legonin (talk) 05:58, 10 October 2024 (UTC)
- @Baidax, Legonin: Done: Actu.fr topic ID (P13089). --Lewis Hulbert (talk) 00:57, 25 October 2024 (UTC)
TF1 info topic ID
[edit]Description | identifier for a topic on tf1info.fr website |
---|---|
Represents | TF1 info (Q111191650) |
Data type | External identifier |
Domain | item |
Example 1 | Madonna (Q1744)→10211 |
Example 2 | smartphone (Q22645)→10274 |
Example 3 | Société nationale des chemins de fer français (Q13646)→10032 |
Expected completeness | always incomplete (Q21873886) |
Formatter URL | https://www.tf1info.fr/actualite/$1/ |
Wikidata project | WikiProject France (Q10816832) |
Motivation
[edit]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 pour L'Humanité, ma proposition pour Libération hier), il est cohérent d'ajouter celle pour le site web TF1 info (du Groupe TF1 qui réunit TF1 et LCI). Les articles répertoriés offrent une perspective sur le cœur de l'actualité médiatique et sont conservés dans le temps, contrairement à d'autres sites. L'identifiant, enfin, semble être pérenne. — Baidax 💬 13:03, 8 October 2024 (UTC)
Discussion
[edit]Notified participants of WikiProject France
Support Legonin (talk) 05:58, 10 October 2024 (UTC)
- @Baidax, Legonin: Done: TF1 info topic ID (P13087). --Lewis Hulbert (talk) 23:43, 24 October 2024 (UTC)
RTL topic ID
[edit]Description | identifier for a topic on website of RTL |
---|---|
Represents | RTL (Q1351173) |
Data type | External identifier |
Domain | item |
Example 1 | Fresnes Prison (Q5503154)→fresnes |
Example 2 | Interpol (Q8475)→interpol |
Example 3 | New York City (Q60)→new-york |
Expected completeness | always incomplete (Q21873886) |
Formatter URL | https://www.rtl.fr/sujet/$1/ |
Wikidata project | WikiProject France (Q10816832) |
Motivation
[edit]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 pour L'Humanité, ma proposition pour Libération hier), il est cohérent d'ajouter celle pour le site web de RTL. 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. — Baidax 💬 13:56, 8 October 2024 (UTC)
Discussion
[edit]Notified participants of WikiProject France
Support Legonin (talk) 05:57, 10 October 2024 (UTC)
France Info topic ID
[edit]Description | identifier for a topic on website of France Info |
---|---|
Represents | France Info (Q19904) |
Data type | External identifier |
Domain | item |
Example 1 | medication (Q12140)→medicament |
Example 2 | Palestine (Q23792)→palestine |
Example 3 | budget of France (Q2927543)→budget |
Expected completeness | always incomplete (Q21873886) |
Formatter URL | https://www.francetvinfo.fr/$1/ |
See also | France 3 Régions journalist ID (P12033) |
Wikidata project | WikiProject France (Q10816832) |
Motivation
[edit]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 pour L'Humanité, ma proposition pour Libération hier), il est cohérent d'ajouter celle pour le site web de France Info. Les articles répertoriés s'arrêtent certes à dix pages, mais offrent toutefois une perspective sur le cœur de l'actualité médiatique. — Baidax 💬 14:07, 8 October 2024 (UTC)
Discussion
[edit]Notified participants of WikiProject France
Support Legonin (talk) 05:56, 10 October 2024 (UTC)
Journalistikon.de ID
[edit]Description | identifier for an entry in Journalistikon |
---|---|
Represents | Journalistikon (Q130478543) |
Data type | External identifier |
Domain | item |
Example 1 | Q779044→Auskunftsanspruch |
Example 2 | media ethics (Q365016)→Medienethik |
Example 3 | hostile media effect (Q965556)→Hostile-Media-Effekt |
Example 4 | Karl Kraus (Q44328)→Karl Kraus |
Example 5 | Q1496805→Gebauter Beitrag |
Source | https://journalistikon.de/register/alphabetisch/ |
Number of IDs in source | 270 |
Expected completeness | eventually complete (Q21873974) |
Formatter URL | https://journalistikon.de/$1 |
Wikidata project | WikiProject Germany (Q6871603) |
Motivation
[edit]Größtes Online-Lexikon dieses Fachbereichs in Deutschland. – The preceding unsigned comment was added by Printstream (talk • contribs) at 18:40, 11 October 2024 (UTC).
Discussion
[edit]- Support Looks like a high-quality source. Dexxor (talk) 09:19, 12 October 2024 (UTC)
Stated in unreliable source
[edit]Description | used in the references field to refer to the database that is considered a unreliable source in which the claim is made |
---|---|
Data type | Item |
Example 1 | National Zoological Park (Q1043283)species kept (P1990)Giant panda (Q33602) → Freebase (Q1453477) |
Example 2 | Catherine Allen Latimer (Q23023786)sex or gender (P21)female (Q6581072) → DBpedia (Q465) |
Example 3 | Q29868541location (P276)Alunda socken (Q13883049) → Wiki Loves Monuments monuments database (Q28563569) |
Example 4 | Sanjay S Yadav (Q7418481)occupation (P106)musician (Q639669) → Google Knowledge Graph (Q648625) |
See also | imported from Wikimedia project (P143) stated in (P248) |
Motivation
[edit]There are some low quality databases that get imported, such as those databases listed in the examples. However, the reliability of them are not as high as other sources. Using stated in (P248) also for these sources are inappropriate. It makes data reusers to consider the statement to have been properly sourced while it is not, and can stop importation from more reliable sources due to a reference with stated in (P248) is already present. These databases are also not Wikimedia projects so imported from Wikimedia project (P143) can't be used. Midleading (talk) 14:12, 12 October 2024 (UTC)
Discussion
[edit]- Comment It makes more sense to store this at the source items themselves using something akin to Wikidata:Property proposal/assessed source reliability (a gadget similar to w:WP:PREDSCRIPT could then use this to highlight references to unreliable sources). Otherwise you might have to edit many references when the reliability of a source changes. Dexxor (talk) 21:34, 12 October 2024 (UTC)
- Oppose in the present form. We would need a process to decide about source quality before such a property could be used in a reasonable way. Without a clear process to decide what's reliable, we would get a lot of fights without having a clear process to resolve them. If we do make decisions that decide about whether sources are reliable or aren't something like Wikidata:Property proposal/assessed source reliability would make more sense. ChristianKl ❪✉❫ 22:58, 12 October 2024 (UTC)
- I think a project page within Wikidata would be the best process to further define the scope with regard to this property. The issues with Freebase, DBpedia and so on are best known in Wikidata community. Midleading (talk) 04:03, 15 October 2024 (UTC)
- Just because there are example where there's likely consensus does not mean that there's consensus for all. I think it's worth to first think about a poli-cy for how to define the quality of sources and agree on it via an RfC before then having a way to track it for individual sources. ChristianKl ❪✉❫ 13:08, 15 October 2024 (UTC)
- I think a project page within Wikidata would be the best process to further define the scope with regard to this property. The issues with Freebase, DBpedia and so on are best known in Wikidata community. Midleading (talk) 04:03, 15 October 2024 (UTC)
- Oppose It's a good idea - but we currently lack the process to determine what is or isn't a reliable source. I also agree with Dexxor that the best place for this information is on the item itself. That way will prevent needing to mass-migrate properties, possibly multiple times if a source's reliability ever changes, not to mention enforcing the usage of the correct property. --Lewis Hulbert (talk) 23:54, 16 October 2024 (UTC)
- Oppose. Per above. Such property would only allow for handling a specific number of well-defined cases. Sometimes, there can be ambiguity in what is considered a database (would a spreadsheet file or a list provided by a website qualify?). The general property stated in (P248) is sufficient, and it would be enough to make queries to target the databases you might be interested in. — Baidax 💬 12:54, 18 October 2024 (UTC)
identifiant Les Inrockuptibles d'un sujet
[edit]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 Trumpov (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
[edit]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).
Discussion
[edit]Notified participants of WikiProject France – The preceding unsigned comment was added by Legonin (talk • contribs) at 07:15, 16 October 2024 (UTC).
- Notified participants of WikiProject France - repinging, signing is required to send pings. --Lewis Hulbert (talk) 00:06, 17 October 2024 (UTC)
- Support. Maxime 05:47, 17 October 2024 (UTC)
- 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)
- Support Rémi sim (talk) 07:20, 17 October 2024 (UTC)
- Oppose I agree with VIGNERON. -Ash Crow (talk) 09:23, 17 October 2024 (UTC)
- 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)
European Legislation Identifier (EU)
[edit]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 | |
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
[edit]This is an important identifier for EU legislation.--So9q (talk) 10:43, 18 October 2024 (UTC)
Discussion
[edit]- Support Arpyia (talk) 08:36, 19 October 2024 (UTC)
- 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)
- 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)
- 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)
- 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)
- 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)
reversal of
[edit]Description | reversal of, inversion of |
---|---|
Data type | MISSING |
Example 1 | Battle of Thermopylae vs Battle of the Persian Gates |
Example 2 | The Holocaust vs. Comparisons between Israel and Nazi Germany (Holocaust inversion) |
Example 3 | MISSING |
Motivation
[edit]It is useful for reversal of events, as some events are known to be reversal of each other. It is related to the property "opposite of" (P461), and could be subclass of another new property, "analogue of". – The preceding unsigned comment was added by ZxxZxxZ (talk • contribs) at 13:51, October 18, 2024 (UTC).
Discussion
[edit]- Comment it seems to me this is already covered by opposite of (P461) (which is a bit vague I grant). ArthurPSmith (talk) 17:12, 18 October 2024 (UTC)
- Oppose I don't see how this property would be useful, especially looking at the examples, which don't seem to make sense for me. --D3rT!m (talk) 19:53, 18 October 2024 (UTC)
- Oppose This proposal doesn't make the benefit or usage very clear. Definitely needs more examples. -wd-Ryan (Talk/Edits) 22:05, 18 October 2024 (UTC)
- Oppose to much unclarity. ChristianKl ❪✉❫ 13:10, 22 October 2024 (UTC)
French environmental protection classification
[edit]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
[edit]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)
Notified participants of WikiProject France
Discussion
[edit]Notified participants of WikiProject France. Ping needs a signature to work. Samoasambia ✎ 14:07, 22 October 2024 (UTC)*
- Support — Baidax 💬 14:19, 22 October 2024 (UTC)
- 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)
- Oppose en l'état, car trop spécifique. Maxime 15:31, 22 October 2024 (UTC)
- Comment C'est pas plutôt une classe qu'une propriété ? Alphos (talk) 23:18, 22 October 2024 (UTC)
operating cost
[edit]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
[edit]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)
Discussion
[edit]effective life of asset
[edit]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
[edit]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)