Wikidata:Property proposal/Generic
Shortcuts: WD:PP/GEN, WD:PP/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 policy.
| 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 2026/02. |
General
[edit]Gravestone Project Cemetery ID
[edit]| Description | identifier of a cemetery from the German project https://grabsteine.genealogy.net |
|---|---|
| Represents | cemetery (Q39614) |
| Data type | External identifier |
| Example 1 | Main cemetery Weimar (Q113552022) → 4660 |
| Example 2 | Jewish cemetery, Meiningen (Q27938126) → 8670 |
| Example 3 | Cemetery Espenfeld (Q113103189) → 7611 |
| Allowed values | [1-9]\d* |
| Number of IDs in source | >10000 and counting |
| Expected completeness | eventually complete (Q21873974) |
| Formatter URL | https://grabsteine.genealogy.net/namelist.php?cem=$1 |
| See also | Historical Gazetteer (GOV) ID (P2503), Find a Grave cemetery ID (P2025) |
| Single-value constraint | yes |
| Distinct-values constraint | yes |
Motivation
[edit]Wikidata items of cemeteries in Germany often have no external identifiers despite to OpenStreetMap. With grabsteine.genealogy.net there is database maintained by the Association for Computer Genealogy which maintains several other databases and projects around the topic of genealogy. They systematically record cemeteries including their tombstones in Germany (and other countries). By the way, the already established property Historical Gazetteer (GOV) ID (P2503) also references to a database of Association for Computer Genealogy. It seems to be a reliable source and, therefore, could be valuable when we connect to it. --Arnd (talk) 17:30, 30 January 2026 (UTC)
Discussion
[edit]
Support Nice. ArthurPSmith (talk) 16:54, 4 February 2026 (UTC)
thumbtime
[edit]| Description | Time for video thumbnail in seconds |
|---|---|
| Represents | video thumbnail (Q137086454) |
| Data type | Quantity |
| Domain | item |
| Example 1 | xenobot (Q82309052)video (P10)c:File:Xenobots - Building the First-Ever Self-Replicating Living Robots.webm |
| Example 2 | Copenhagen Metro (Q212741)video (P10)c:File:Automatic Copenhagen Metro - Hitachi Rail Italy Driverless Metro - U-Bahn - Subway - Bahn.webm |
| Example 3 | Roman aqueduct (Q13218676)video (P10)c:File:How did Roman Aqueducts work.webm |
| Allowed units | second (Q11574) |
Motivation
[edit]With the thumbtime parameter one can set the thumbnail of videos at the places they're embedded such as Wikipedia articles on the Commons frontpage. See c:Commons:Video#Setting a video thumbnail image.
I'm proposing a new thumbtime property is used as a qualifier for video (P10) which can then be used to:
- eventually display a good fitting thumbnail in the Wikidata item (this may require some code changes)
- display the specified thumbnail for videos in the Wikidata infobox that's shown in Commons category pages
- include this in the thumbtime parameter of video suggestions if videos set on Wikidata items are suggested for Wikipedia articles that are linked to that item
- see W310: Suggest media set in Wikidata items for their Wikipedia articles (voting on it open; this would make contributions to Wikidata much more valuable as the videos specified there find their way into Wikipedia articles that lack media and because few people adding media to WD items also add them to the linked Wikipedia articles…I recommend you check that page out which has more info on this)
Furthermore, I suggest that the readily-available thumbtime data of Commons' Media of the Day videos is imported to where these videos are used. This would set a good thumbtime to maybe 100 items or so – see this Commons search query that shows the pages this could be imported from (note: it uses two formats 01:01 and 61). Maybe somebody knows how this could be done. Maybe one could show all WD items that have a video in the Media of the Day category set that has its thumbtime specified so that one can then copy the thumbtimes over manually.
Data type should be the number in seconds but I could not find it in datatypes.
--Prototyperspective (talk) 01:08, 22 November 2025 (UTC)
- Changed datatype to quantity. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 13:24, 22 November 2025 (UTC)
Notified participants of WikiProject Commons --Prototyperspective (talk) 13:09, 22 November 2025 (UTC)
Discussion
[edit]
Support. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 13:24, 22 November 2025 (UTC)
Support John Samuel (talk) 14:08, 22 November 2025 (UTC)
Support Useful. --Yann (talk) 15:54, 22 November 2025 (UTC)
Support Jerimee (talk) 16:57, 22 November 2025 (UTC)
Comment I would like to know how the Phabricator ticket T22647 is meant to relate to this proposal. Ainali (talk) 20:42, 24 November 2025 (UTC)
- It would be Commons' way to set the thumbnail – if that ever becomes possible, the thumbtimes set there could maybe largely be imported to this property. I didn't link this issue and it's relating to this proposal in that it's also about the image thumbnail preview image (there: which thumbnail shows e.g. in Commons category pages). Prototyperspective (talk) 23:38, 24 November 2025 (UTC)
- Do we have confirmation from developers that this is the way they want it to be done or might we end up with two separate ways of doing this in the end? Ainali (talk) 07:42, 25 November 2025 (UTC)
- Again, I didn't link to this issue in this proposal. It's not part of the proposal. And I just clarified that this is a separate issue. Please see It would be Commons' way [not Wikidata's and/or Wikipedia's] to set the thumbnail – if that ever becomes possible, the thumbtimes set there could maybe largely be imported to this property […] (there: which thumbnail shows e.g. in Commons category pages [here: for Wikidata items and maybe/hopefully eventually their Wikipedia articles]. (added implicit things for clarity). Prototyperspective (talk) 12:55, 25 November 2025 (UTC)
- I must be missing something here, because exactly that is what confuses me. If we create this property, and then later the devs choose to implement another solution, then this has all been made redundant. Ainali (talk) 21:27, 25 November 2025 (UTC)
- Devs of which software? If you mean devs of the Wikidata software: the thumbtime of the videos has to be stored somewhere at the place where the video is used. If it's stored differently than via a qualifier – which afaik is how all things regarding statements in Wikidata items are stored – then the qualifiers could be imported.
- If these were used for Wikipedia or for the Commons Wikidata infobox, the qualifier could already be used.
- For the potential application of setting the thumbtime of the video within Wikidata item webpages and in sparql query results: if the qualifier is not used (seems rather unlikely) then one could use the values written to there and set them in whatever other method of setting the thumbnail is built.
- Prototyperspective (talk) 23:56, 25 November 2025 (UTC)
- I think I meant the Mediawiki developers. If they implement a solution so that the thumbtimes can be set for the video on file page itself, and then reused everywhere where a video is being used, then this solution could become redundant. Ainali (talk) 22:52, 26 November 2025 (UTC)
- This is based on the speculation that this is possible and if it is that it will be done. I don't think there is anything else on file description pages that can be used at the places where videos are being used so this would be a novum. By the way, the best thumbnail may vary per item/subject so it's an advantage to be able to set this on a per item basis (probably quite rare though). Maybe you could ask developers whether this could/will become possible. Seeing that the issue, as with many code problems, is open since 2009, I doubt that it will be implemented any time soon. In contrast, the Wikidata infobox could I think use the thumbtime as soon as it's implemented here. Prototyperspective (talk) 23:16, 26 November 2025 (UTC)
- Wait, this was not meant to be in SDC but on items? Then everything I said can be disregarded. I would support the proposal if this was possible to understand from the template, but there's way too many empty parameters in that one still. Ainali (talk) 09:15, 27 November 2025 (UTC)
- It was meant to be set as a qualifier on items. Note: I don't object for this to be used instead or additionally as structured data on Commons if that's identified as the better method to use this property. That currently can't be queried as well and can't be used by the Wikidata infobox etc so I think use as qualifier would be better. I thought the examples (the statements) make this clear. As far as I can see, all but the status parameter (which shouldn't be set by me) are set in the property proposal template but if there's more than these and I should set some of them (or if you mean another template), please tell me which. Prototyperspective (talk) 13:52, 27 November 2025 (UTC)
- I think the parameter
domainwould help a lot,subject itemwouldn't hurt either, and explicitly addingallowed unitsto the template would also make it clearer to understand at a glance. Ainali (talk) 22:22, 27 November 2025 (UTC)
Done--Prototyperspective (talk) 00:04, 28 November 2025 (UTC)
- I am a bit confused by "property" as value for
domain. I would have expected "item", because isn't it on items we will use this rather than on properties? If so, to express that it should be used as a qualifier, I thinkother-constraintscould have property constraint (P2302)property scope constraint (Q53869507)property scope (P5314)as qualifier (Q54828449) . Ainali (talk) 15:53, 28 November 2025 (UTC)- Probably just a mistake on my side; the template documentation is imo difficult to understand: I meant it should be used on Wikidata items' properties, namely the properties into which video files on Commons are entered (video (P10) is the one I'm aware and which would be the main property). Will edit the domain – please let me know if I got it wrong. Prototyperspective (talk) 15:55, 1 December 2025 (UTC)
- I am a bit confused by "property" as value for
- I think the parameter
- It was meant to be set as a qualifier on items. Note: I don't object for this to be used instead or additionally as structured data on Commons if that's identified as the better method to use this property. That currently can't be queried as well and can't be used by the Wikidata infobox etc so I think use as qualifier would be better. I thought the examples (the statements) make this clear. As far as I can see, all but the status parameter (which shouldn't be set by me) are set in the property proposal template but if there's more than these and I should set some of them (or if you mean another template), please tell me which. Prototyperspective (talk) 13:52, 27 November 2025 (UTC)
- Wait, this was not meant to be in SDC but on items? Then everything I said can be disregarded. I would support the proposal if this was possible to understand from the template, but there's way too many empty parameters in that one still. Ainali (talk) 09:15, 27 November 2025 (UTC)
- This is based on the speculation that this is possible and if it is that it will be done. I don't think there is anything else on file description pages that can be used at the places where videos are being used so this would be a novum. By the way, the best thumbnail may vary per item/subject so it's an advantage to be able to set this on a per item basis (probably quite rare though). Maybe you could ask developers whether this could/will become possible. Seeing that the issue, as with many code problems, is open since 2009, I doubt that it will be implemented any time soon. In contrast, the Wikidata infobox could I think use the thumbtime as soon as it's implemented here. Prototyperspective (talk) 23:16, 26 November 2025 (UTC)
- I think I meant the Mediawiki developers. If they implement a solution so that the thumbtimes can be set for the video on file page itself, and then reused everywhere where a video is being used, then this solution could become redundant. Ainali (talk) 22:52, 26 November 2025 (UTC)
- Devs of which software? If you mean devs of the Wikidata software: the thumbtime of the videos has to be stored somewhere at the place where the video is used. If it's stored differently than via a qualifier – which afaik is how all things regarding statements in Wikidata items are stored – then the qualifiers could be imported.
- I must be missing something here, because exactly that is what confuses me. If we create this property, and then later the devs choose to implement another solution, then this has all been made redundant. Ainali (talk) 21:27, 25 November 2025 (UTC)
- Again, I didn't link to this issue in this proposal. It's not part of the proposal. And I just clarified that this is a separate issue. Please see It would be Commons' way [not Wikidata's and/or Wikipedia's] to set the thumbnail – if that ever becomes possible, the thumbtimes set there could maybe largely be imported to this property […] (there: which thumbnail shows e.g. in Commons category pages [here: for Wikidata items and maybe/hopefully eventually their Wikipedia articles]. (added implicit things for clarity). Prototyperspective (talk) 12:55, 25 November 2025 (UTC)
- Do we have confirmation from developers that this is the way they want it to be done or might we end up with two separate ways of doing this in the end? Ainali (talk) 07:42, 25 November 2025 (UTC)
- It would be Commons' way to set the thumbnail – if that ever becomes possible, the thumbtimes set there could maybe largely be imported to this property. I didn't link this issue and it's relating to this proposal in that it's also about the image thumbnail preview image (there: which thumbnail shows e.g. in Commons category pages). Prototyperspective (talk) 23:38, 24 November 2025 (UTC)
award category or rank
[edit]Motivation
[edit]Many awards have categories (besides the type of work rewarded, which is handled by awarded for type of work (P13713)) or ranks (e.g. gold/silver/bronze) that are currently expressed with a variety of inappropriate qualifiers (see queries in the examples). Different from ranking (P1352), which is numeric-valued. (Note: where the value of P166 is improperly a competition, with the award given as a qualifier, e.g. this statement, the statement should be reworked with P166 as main property and league or competition (P118) qualifying, rather than using the proposed property.) Swpb (talk) 20:23, 17 October 2025 (UTC)
Discussion
[edit]
Support if there isn't a way to do this already, but I don't think the value should be the element gold (Q897). -wd-Ryan (Talk/Edits) 21:01, 18 October 2025 (UTC)
- There's gold medal of the order (Q71322190) -wd-Ryan (Talk/Edits) 21:13, 18 October 2025 (UTC)
- Agreed, changed. Swpb (talk) 14:30, 20 October 2025 (UTC)
Comment Can we just create a new item for every possible award categories? Midleading (talk) 12:34, 19 October 2025 (UTC)
- We could, but I don't think that would be particularly efficient. Every award with a gold, silver, and bronze rank would become three items instead of one. Swpb (talk) 14:26, 11 December 2025 (UTC)
Oppose As per Midleading JhowieNitnek (talk) 15:37, 9 January 2026 (UTC)
- Midleading didn't oppose, they asked a question, which I answered. If you don't think that answer was satisfactory, explaining why might add some value to your vote. Swpb (talk) 21:20, 9 January 2026 (UTC)
- @JhowieNitnek: Swpb (talk) 19:12, 12 January 2026 (UTC)
DE-BIAS ID
[edit]Motivation
[edit]Scholarly resource resulting from a finished project by Europeana, to help with more inclusive and respectful labeling. Adding this identifier to both Wikidata items (for the concepts behind the terms) and Lexemes (for the exact words) will help in analyzing where Wikimedia projects touch upon these topics. Some remarks which I couldn't fit into the proposal above:
- I indeed recommend to use this property for both Items (concepts) and Lexemes (words).
- The data URIs are not the easiest to parse (see the examples above), but there is an equivalent set of human-readable PDF files (CC BY-SA, available on Wikimedia Commons too) which contain URIs as well and can be used as references.
- In the next months, as time allows, I plan to start with a basic mapping of the terms to Wikidata items (not yet Lexemes) using labels and aliases in the five languages, using batch editing tools. I will do this slowly and with care, but errors may occur. Help is welcome.
- I have started building a prototype overview tool to help us Wikimedians check coverage of the terms in this vocabulary in Wikimedia projects. I may slowly work on this more, making sure the tool points to Wikidata items and Lexemes if this property gets approved. As I am not a coder and am developing this with "vibe coding" I would welcome help here too (or even a skilled coder who would take over).
Spinster 💬 16:40, 13 June 2025 (UTC)
Discussion
[edit]- @Spinster: I think I would need to better understand what this is about - why are there separate 'en' and 'nl' identifiers? Wouldn't it make more sense to just use the number (13, 19, etc.) as the ID here, or are there other reasons the full c_... identifier is meaningful? Also, a lexeme and a concept are quite different things - a concept is more closely related to a specific sense of the lexeme. Should this be a property for senses then? ArthurPSmith (talk) 19:19, 21 June 2025 (UTC)
- Hi @ArthurPSmith, thanks for your questions! I've dived into this resource pretty deeply. It's built in a complicated way, it takes a while to grasp it unfortunately. The best instrument to "grasp" it is probably the set of PDFs in this Commons category, where you compare the lists per language and the identifier links at the bottom of each page.
- The resource has five languages, and different lists of terms/concepts per language. Single numbers don't correspond with the same concept across languages, as you can see in the example above. 'Slaaf' in Dutch has a different number than 'slave' in English. Not every language lists the same terms/concepts. To be able to build persistent URIs pointing to this resource, we do need the full identifier string as I suggested above.
- The resource describes both concepts and words, as I mentioned above. It's not just about (a single sense of) the Lexeme "slave" but also about how the concept of "enslaved person" (its Wikidata item) is labeled in various languages. I think it's useful for us, the Wikidata and Wikimedia community, to be able to compare this resource to both Wikidata items (with labels in various languages), Lexemes, and also to be able to connect it to Wikipedia articles (partly through Wikidata). Hence my suggestion to connect this property to both Lexemes and Wikidata items.
- I agree that on the Lexeme side, it would be most correct to connect the identifier to a specific Sense of a certain Lexeme. But I think that's not technically possible (?); hence a compromise to (for now) connect it to the Lexeme as a whole.
- I really wish it were more simple; that would allow us to have more clear conversations on this topic. But it is what it is. I think that actually adding the identifiers to Wikidata items and Lexemes will clarify a lot :-) Spinster 💬 19:37, 21 June 2025 (UTC)
- Properties can be specific to senses of lexemes - item for this sense (P5137) is specifically just for senses for example. ArthurPSmith (talk) 19:46, 21 June 2025 (UTC)
- It may be given the complexity you mention that this should be several distinct properties, not just one. ArthurPSmith (talk) 19:47, 21 June 2025 (UTC)
- If properties specific for senses of lexemes are possible, then I am all for that. Thanks for the suggestion!
- I've been thinking about the idea to split this into several properties but I think it has more drawbacks than advantages. It is one single resource with one single formatter URL. Potential users/re-users would need to know about all (probably five) properties to know what to retrieve. Same with querying; that would become more complex and similarly queriers would need to know that five properties exist. I am in strong favor of keeping this as one proposal. Thanks, Spinster 💬 06:40, 3 July 2025 (UTC)
- It may be given the complexity you mention that this should be several distinct properties, not just one. ArthurPSmith (talk) 19:47, 21 June 2025 (UTC)
- Properties can be specific to senses of lexemes - item for this sense (P5137) is specifically just for senses for example. ArthurPSmith (talk) 19:46, 21 June 2025 (UTC)
- Hi @ArthurPSmith, thanks for your questions! I've dived into this resource pretty deeply. It's built in a complicated way, it takes a while to grasp it unfortunately. The best instrument to "grasp" it is probably the set of PDFs in this Commons category, where you compare the lists per language and the identifier links at the bottom of each page.
Minfin company ID for banks
[edit]| Description | identifier for an organization, in the database of banks in Ukraine, operated by Minfin |
|---|---|
| Data type | External identifier |
| Domain | organisations |
| Example 1 | Poltava-Bank (Q123579535)→ poltava-bank |
| Example 2 | PrivatBank (Q1515015)→ privatbank |
| Example 3 | A-Bank (Q28705400)→ a-bank |
| Allowed values | Valid Minfin URL slugs |
| Source | Wikipedia external links |
| Formatter URL | https://minfin.com.ua/ua/company/$1 |
Motivation
[edit]Minfin is a useful and widely used financial database in Ukraine. It provides up-to-date information about banks, non-bank financial institutions, and insurance companies, and also hosts the largest database of user reviews in this sector. Adding a Minfin ID property will allow linking Wikidata items about financial organizations to their authoritative Minfin profiles, improving verifiability, data integration, and access to user feedback and current financial information. – The preceding unsigned comment was added by TPoklad (talk • contribs) at 13:45, August 26, 2025 (UTC).
Discussion
[edit]
Comment @TPoklad: I'm always in favor of more organization ID's like this - however your examples should be specific, not generic. On the left hand side an actual company listed in Wikidata, on the right hand side the actual ID for that company. Also if there's a formatter URL or something like that a link to the relevant page showing that ID corresponds to that company, for verification. ArthurPSmith (talk) 17:08, 26 August 2025 (UTC)
- @ArthurPSmith Thank you. I've added more specific examples. However, I noticed that the Minfin URL contains the industry (credits, invest, insurance). Should I use the entire URL as the ID? TPoklad (talk) 07:31, 28 August 2025 (UTC)
- For banks I've created a Mix'n'Match catalog 7321. For the other companies isn't so easy. Gerwoman (talk) 10:22, 29 August 2025 (UTC)
- Thank you TPoklad (talk) 19:18, 4 September 2025 (UTC)
- @Gerwoman@ArthurPSmith I’ve completed the Mix'n'Match catalog. What is the next step? TPoklad (talk) 14:09, 10 February 2026 (UTC)
- For banks I've created a Mix'n'Match catalog 7321. For the other companies isn't so easy. Gerwoman (talk) 10:22, 29 August 2025 (UTC)
- @ArthurPSmith Thank you. I've added more specific examples. However, I noticed that the Minfin URL contains the industry (credits, invest, insurance). Should I use the entire URL as the ID? TPoklad (talk) 07:31, 28 August 2025 (UTC)
- @TPoklad: are the id's actually unique, or could the same id be used for different organizations because they are in different industry categories? Also, including the industry as part of the id will allow a formatter URL to be defined using the links you have now; otherwise they won't be linked in the Wikidata UI. So it's probably best to specify the id's in a way that includes the industry. ArthurPSmith (talk) 18:01, 10 February 2026 (UTC)
- @ArthurPSmith As mentioned earlier, the catalog includes only banks. There are no organizations from other industries, so the IDs are unique and cannot overlap across categories.
- So, including the industry in the ID is not necessary in our case. TPoklad (talk) 06:42, 11 February 2026 (UTC)
- @TPoklad: I have updated the proposal template above to restrict it to just banks. If you could add one or two more examples for banks to the template that would make this ready I think. ArthurPSmith (talk) 21:43, 11 February 2026 (UTC)
- @ArthurPSmith Thanks, I've added a couple more examples for banks TPoklad (talk) 19:55, 12 February 2026 (UTC)
Picture composition
[edit]| Description | Key compositional features (design rules) used/observable in an image |
|---|---|
| Represents | composition (Q462437) |
| Data type | Item |
| Domain | two-dimensional visual artwork (Q110304307) |
| Example 1 | Girl with a Pearl Earring (Q185372)→diagonal method (Q1208211) [as demonstrated in File:Diagonal on Girl with Pearl Earring.jpg] |
| Example 2 | Champ de coquelicots (Q19926059)→Rabatment of the rectangle (Q7278506) [as demonstated in File:Monet - Mohnblumenfeld rabatment study.jpg] |
| Example 3 | Girl on the beach (Q112066391)→Rule of thirds (Q327905) [as demonstated in File:Rule of thirds applied on Mädchen am Strand.jpg] |
Motivation
[edit]Ähnliche Eigenschaften gibt es zum Beispiel für genre (P136) oder fabrication method (P2079), es fehlt nur eine für Gestaltungsregeln. --XRay (talk) 09:40, 17 April 2025 (UTC)
English: There are similar properties for genre (P136) or fabrication method (P2079), for example, only one is missing for design rules. --XRay (talk) 09:18, 18 April 2025 (UTC)
Discussion
[edit]
Comment The proposal template data seems jumbled, and is missing examples. ArthurPSmith (talk) 17:14, 17 April 2025 (UTC)
- Sorry, I don't know how to set suitable examples. --XRay (talk) 19:30, 17 April 2025 (UTC)
- It may be easy for someone to make a suggestion here if they are familiar with things. In any case, I found it difficult to apply the given scheme to what I felt was missing. The whole thing may seem jumbled, but I hope that someone who knows their way around here can formulate it correctly. --XRay (talk) 09:21, 18 April 2025 (UTC)
- I have tried to update the proposal; it's kind of super important, but I wonder how it can be implemented. Will there be bots adding linear perspective (Q11815761) to thousands of items? Is there overlap with Wikipedia:No original research (Q4656524) and will there be a sourcing requirement? Presumably the golden ratio (Q41690) was enjoyed before it was named. Should this proposed property be renamed Compositional features or similar as there may be many at work/play in any one image? Or Pictorial composition? Thanks, Maculosae tegmine lyncis (talk) 06:56, 7 December 2025 (UTC)
Measuring point uuid
[edit]Motivation
[edit]In Germany, for example, the measuring point uuid is used as a unique identifier for water level measuring points (Stream gauge). At these points, the current level of the water of rivers, channels, lakes or the sea will be collected. These Measuring points have a coordinate. This will belong to the Project Germany, WikiProject Rivers and WikiProject Geology. These Measurement points indicates the difference between standard sea level and actual water level. As alternativ a general uuid value can be implemented. There are already uuid properties, but they are to specific, either people World Rowing UUID or books BHCL UUID. If a universal uuid is implemented, it would be fine for my project. I like to add all wate level measurement point in Germany. They are used at rivers, Canals, at North- and Baltic Sea. In Germany there are more than 650 measurement points. See also extern: [1] GodeNehler (talk) 16:13, 7 November 2024 (UTC)
Discussion
[edit]- Take a look at how property descriptions are usually written, and write one for this property in the same form. Currently, it's not clear to me whether this is supposed to be a property about a certain German identifer (so a standard external ID property) or supposed to be something more general.
- Is there some regulation that codifies these measuring points? ChristianKl ❪✉❫ 21:38, 7 November 2024 (UTC)
- Sorry for the late response. The problem is, that I don't know, where outside Germany this identifier is use. But to my understanding a uuid is a global unique identifier. So it can be used everywhere else for this purpose. And: to my understanding an uuid is a global unique identifier and can be used for everything as long as it is global unique. [2]. The problem in WD is, that we have already uuid but to specific. So, please add either a specific uuid for Measuring points or an general uuid. I hope this explantation helps. --GodeNehler (talk) 20:55, 10 March 2025 (UTC)
Open Library Collection
[edit]| Description | Link to Open Library Collection which contain manually and automaticallly collections of editions and works on certain topics |
|---|---|
| Data type | URL |
| Example 1 | Meyers Reisebücher (Q1429532)→https://openlibrary.org/collections/meyers-reiseb%C3%BCcher |
| Example 2 | Star Wars (Q462)→https://openlibrary.org/collections/star-wars |
| Example 3 | subject→value |
| Planned use | Sie soll dazu dienen Themen in der WD mit Collections in der OL zu verlinken. Das würde ich gerne nutzen. |
| Formatter URL | https://openlibrary.org/collections/$1 |
| See also | Open Library ID (P648), Open Library subject ID (P3847), Open Library publisher ID (P12088) |
Motivation
[edit]Bessere Verlinkung der DAten in der OpenLibrary. – The preceding unsigned comment was added by Ogmios (talk • contribs) at 11:09, 13 November 2024 (UTC).
Discussion
[edit]
Support Note that example 1 is wrong, since it links to wikisource --Yuriklim (Talk) 17:46, 27 April 2025 (UTC)
Support Ok, warum nicht? Flanierer (talk) 07:21, 12 August 2025 (UTC)
Comment @Ogmios: I don't understand this proposal. Maybe some more examples would help. If this property is intended to refer to things at openlibrary.org then what is the meaning of the first example? ArthurPSmith (talk) 20:25, 14 August 2025 (UTC)
- @ArthurPSmith:, thank you for your question. I made a copy & paste error and corrected it, thanks for noticing. Ogmios (Tratsch) 12:57, 15 August 2025 (UTC)
- Ah, ok that makes more sense. This then sounds like a property that should be an external id - the id value would be for example the string 'star-wars', and Wikidata could link to it with the formatter URL you have specified. Is that what you intended here? ArthurPSmith (talk) 01:43, 16 August 2025 (UTC)
- @ArthurPSmith:, thank you for your question. I made a copy & paste error and corrected it, thanks for noticing. Ogmios (Tratsch) 12:57, 15 August 2025 (UTC)
Comment I'm confused by the combination of datatype (URL) and the URL formatter. Couldn't the datatype be "String", and the complete URL would be generated by the formatter? Schmidt Fu (talk) 17:10, 7 December 2025 (UTC)
outcome (resolution, disposition)
[edit]Motivation
[edit]For conclusion of criminal charges and civil complaints: we have verdict (P:P11922) but this is not sufficient, as charges can also go away in other ways: charges 'dropped' (dismissed by prosecutor's motion); charges dismissed (by defence's motion); AFAIA, the judge can even discretionally dismiss the entire case without a motion for reasons like clear and unmitigable prosecutorial misconduct); mistrial (hung jury etc); jury nullification (where jury validates the elements of the charge but give a 'not guilty' verdict); in civil cases, the claimant could withdraw or the parties could settle at any point; the defendant could die or become unfit to stand trial while the trial is underway; and if the trial goes tits up for any reason, prosecution could refrain from bringing the charges to another trial...
Perhaps "verdict" property should be renamed and modified to cover and allow all these non-verdict conclusions? --Pitke (talk) 01:43, 6 April 2025 (UTC)
- Comment: Upon further reflection, I feel the only sensible solution is to keep
trialoutcome and verdict separate, since 'verdict' will still be needed as a type oftrialoutcome, or a superset oftrialoutcomes like 'not guilty', 'not proven', and 'guilty'. Withdrawing my hairbrained suggestion to repurpose 'verdict'. --Pitke (talk) 10:02, 20 September 2025 (UTC)- And by 'trial outcome' I of course meant legal case outcome. Many cases end before a trial. --Pitke (talk) 10:32, 20 September 2025 (UTC)
Discussion
[edit]
Weak support I think changing the property scope is a better choice, but there is no clear process for discussing such cases. Circeus (talk)- I opened a discussion about broadening the definition of the verdict property at https://www.wikidata.org/wiki/Property_talk:P11922 ChristianKl ❪✉❫ 09:42, 20 September 2025 (UTC)
identifiant HAL d'une collection
[edit]| Description | identifier for a collection in the HAL (Hyper Articles en Ligne) open access repository |
|---|---|
| Data type | External identifier |
| Example 1 | Biblissima (Q105079519)identifiant HAL d'une collectionBIBLISSIMA |
| Example 2 | Archives nationales (Q182542)identifiant HAL d'une collectionANF |
| Example 3 | Centre for Advanced Renaissance Studies (Q2945233)identifiant HAL d'une collectionCESR |
| Formatter URL | https://hal.science/$1 |
Motivation
[edit]The idea is to have a new identifier property related to the HAL open archive to be able to point to a given HAL collection (see https://doc.hal.science/gerer-une-collection/?h=collection). This new property complements the already existing ones devoted to authors, articles, journals and institutions in HAL (https://www.wikidata.org/wiki/Q3144107). – The preceding unsigned comment was added by Regisrob (talk • contribs) at 11:05, June 19, 2025 (UTC).
Discussion
[edit]
Not done, no support for creation. Regards, ZI Jony (Talk) 14:11, 7 December 2025 (UTC)
- Great, any reason why? Where does the "no support" come from? Authority decision? The kind of comment that encourages one to contribute to Wikidata... And, regards! 😬 Regisrob (talk) 17:16, 7 December 2025 (UTC)
contains nutrient / reference amount
[edit]| Description | Food contains nutrient |
|---|---|
| Represents | nutrient (Q181394) |
| Data type | Item |
| Domain | item |
| Example 1 | Golden Delicious (Q201996)→magnesium (Q660) |
| Example 2 | Golden Delicious (Q201996)→water (Q283) |
| Example 3 | Golden Delicious (Q201996)→protein (Q8054) |
| Source | https://fdc.nal.usda.gov/ |
| See also | food energy (P7971) |
Motivation
[edit]I've been thinking how FoodData Central (Q7866379) may face defunding or becoming unavalible outside of the US in the future. But this data is public domain and we could import it, right? So here I am proposing how this data could be mapped. I assume we need two properties: contains nutrient and reference amount. The USDA api also returns the sample size for each value which might also be a useful piece of information.
Discussion
[edit]Any suggestions? –Shisma (talk) 14:44, 28 April 2025 (UTC)
- Previous proposal: Wikidata:Property_proposal/food_composition. GZWDer (talk) 16:55, 28 April 2025 (UTC)
Notified participants of WikiProject Food
Support Very important if I understood it correctly now but aren't there other properties that can be used for this? Also see this issue in the largest open source food/calorie tracker app where I mentioned wikidata as a potential way to fix one of its biggest issues (and downsides compared to proprietary MyFitnessPal). --Prototyperspective (talk) 17:29, 28 April 2025 (UTC)
Support This is awesome. Would we be able to source real life Nutrition Facts labels? -wd-Ryan (Talk/Edits) 00:30, 29 April 2025 (UTC)
- well, I would personally only apply this to staple foods and broad food categories as oppose to branded food products. data for those is probably better suited for openfoodfacts.org. But as far as I know, there is nothing stopping you from creating items for individual products 🤷 –Shisma (talk) 08:22, 29 April 2025 (UTC)
- @Prototyperspective, Wd-Ryan: I changed the qualifier from quantity (P1114) to mass (P2067) since the former shall not be used with a unit. –Shisma (talk) 09:56, 1 May 2025 (UTC)
Comment If you want to create a new property for reference mass, then please fill out Template:Property proposal for it. Since nutritional values are almost always given in relation to 100g, it probably suffices to create a new unit akin to gram per 100 gram of solvent (Q21127659) so we don't need to create another property. --Dexxor (talk) 15:30, 5 May 2025 (UTC)
- @User:Dexxor yes, lets use units like gram per 100 gram of solvent (Q21127659) instead – Shisma (talk) 07:13, 12 July 2025 (UTC)
- @Prototyperspective: Please don't cast support votes if you think "there might be other properties that can be used for this". Casting support votes before the question is answered, is bad for the property creation process. Only cast support votes, when all the outstanding questions are answered to your satisfaction and the property is well-defined and it's clear that the property is needed and existing properties can't do the job.
Oppose with current description and four word label. The description should define what it means with nutrient. Does USDA have a controlled vocabulary here? What are their terms and how are they are defined? What terms do European authorities use? Are there any nongovernmental sources that should be referenced as well? ChristianKl ❪✉❫ 11:52, 15 July 2025 (UTC)
- I'm no expert but I assume that, if the USDA lists something as a nutrient, then it is a nutrient. The example API call above lists the following nutrients for honycrisp apples:
- Iron, Fe
- Magnesium, Mg
- Phosphorus, P
- Potassium, K
- Sodium, Na
- Zinc, Zn
- Copper, Cu
- Manganese, Mn
- Thiamin
- Riboflavin
- Niacin
- Total Sugars
- Vitamin B-6
- Folate, total
- Water
- Nitrogen
- Total lipid (fat)
- Ash
- Sucrose
- Glucose
- Fructose
- Lactose
- Maltose
- Fiber, total dietary
- Calcium, Ca
- Protein
- Carbohydrate, by difference
- Energy (Atwater General Factors)
- Energy (Atwater Specific Factors)
- Carbohydrate, by summation
- Sugars, Total
- Fatty acids, total trans
- Vitamin B-6
- Choline, total
- Isoleucine
- Leucine
- Lysine
- Cystine
- Valine
- Arginine
- Histidine
- Aspartic acid
- Serine
- Total lipid (fat)
- Carbohydrate, by difference
- Energy
- Sucrose
- Glucose
- Maltose
- Water
- Total Sugars
- Calcium, Ca
- Potassium, K
- Zinc, Zn
- Selenium, Se
- Vitamin E (alpha-tocopherol)
- Lutein + zeaxanthin
- Niacin
- Pantothenic acid
- Protein
- Ash
- Starch
- Fructose
- Lactose
- Energy
- Galactose
- Fiber, total dietary
- Iron, Fe
- Magnesium, Mg
- Phosphorus, P
- Sodium, Na
- Copper, Cu
- Manganese, Mn
- Vitamin A, IU
- Vitamin A, RAE
- Carotene, beta
- Carotene, alpha
- Cryptoxanthin, beta
- Lycopene
- Thiamin
- Riboflavin
- Folate, total
- Vitamin K (Dihydrophylloquinone)
- Vitamin K (phylloquinone)
- Folate, food
- Tryptophan
- Threonine
- Methionine
- Phenylalanine
- Tyrosine
- Alanine
- Glutamic acid
- Glycine
- Proline
- Each of them has a unique ID. I suppose that counts as a controlled vocabulary, does it? – Shisma (talk) 15:31, 16 July 2025 (UTC)
- merriam-webster defines a nutrient as
a substance or ingredient that promotes growth, provides energy, and maintains life
- I don't know it this is a good definition. – Shisma (talk) 15:36, 16 July 2025 (UTC)
- @Shisma
- Generally, it's unlikely that a dictionary provides a good definition in a case like this. Dictionaries are not created to provide controlled vocabulary with terms for purposes like this.
- According to ChatGPT, meaningful definitions are:
- USDA: “A chemical substance in food that provides energy; forms body structures; or regulates body processes.”
- FDA: “any substance of nutritional value found in food, such as carbohydrates, fats, proteins, vitamins, and minerals.”
- EU Regulation (EC) No 1924/2006: "“Nutrient” means a protein, carbohydrate, fat, fibre, sodium, vitamins and minerals listed in the Annex to Regulation (EC) No 1925/2006, and substances which belong to, or are components of, one of these groups."
- IOM: dietary substances required for normal physiological function, growth, and maintenance of health
- WHO: substances obtained from food that are used in the body to provide energy, structural materials, and regulating agent
- Codex Alimentarius Commission: any substance normally consumed as a constituent of food, necessary for growth, development, and maintenance of health
- Academy of Nutrition and Dietetics: chemical substances in food that nourish the body by contributing to energy production, maintenance, and growth
- These are all organizations who actually developed controlled vocabulary and likely had committees who thought long and part about how to define the term and what gets kept in and out by the definition. ChristianKl ❪✉❫ 13:35, 21 August 2025 (UTC)
- What label and description do you propose? – Shisma (talk) 14:04, 21 August 2025 (UTC)
- I'm proposing that someone does the work of thinking through what label/description would make sense for Wikidata given the prior art that exists. That's what the work of proposing a property is about. ChristianKl ❪✉❫ 15:09, 19 September 2025 (UTC)
- What label and description do you propose? – Shisma (talk) 14:04, 21 August 2025 (UTC)
- If there are some nutrients that the FDC has no data on then this would just mean that the data would have to come from other sources. I think the link in Source in the proposal is not exclusive – if there are other sources, these could be added alongside. A problem that becomes clear by the above list is that foods usually would have a long list of nutrients. But it's more or less the most valuable data for foods and well-worth it. It needs to be added in one edit though instead of for example 50 successive ones. Also it would be good to lock such fields so they can't be vandalized and reliably show what data FDC has. Prototyperspective (talk) 21:55, 24 July 2025 (UTC)
- Here is a list of nutrients that can be added to a product in openfoodfacts: Translations - Names of nutrients – Shisma (talk) 17:37, 25 July 2025 (UTC)
- someone does the work of thinking through what label/description would make sense for Wikidata given the prior art that exists See also https://raw.githubusercontent.com/openfoodfacts/openfoodfacts-server/refs/heads/main/taxonomies/food/ingredients.txt and https://wiki.openfoodfacts.org/Ingredients_taxonomy OpenFoodFacts already did it. Doesn't this make this more or less solved? It could be that for some of the ingredients there's not yet a Wikidata property. And also USDA seems to list amino acids like glycine alongside while OFF has them separated (not in the ingredients.txt there). Maybe it remains to be clarified whether amino acids should be a complementary new Wikidata property. Prototyperspective (talk) 13:45, 22 November 2025 (UTC)
- Here is a list of nutrients that can be added to a product in openfoodfacts: Translations - Names of nutrients – Shisma (talk) 17:37, 25 July 2025 (UTC)
- I'm no expert but I assume that, if the USDA lists something as a nutrient, then it is a nutrient. The example API call above lists the following nutrients for honycrisp apples:
motive
[edit]| Description | verified reasoning behind an action |
|---|---|
| Aliases | motive |
| Represents | motive (Q4583280) |
| Data type | Item |
| Template parameter | motive |
| Domain | item |
| Example 1 | Pittsburgh synagogue shooting (Q57830735)motiveantisemitism (Q22649) |
| Example 2 | Horse murders (Q5905629)motiveinsurance fraud (Q838081) |
| Example 3 | Tate murders (Q24930704)motiveunknown value |
| See also | has cause (P828), has goal (P3712) |
Motivation
[edit]This would be a subproperty of has cause (P828), which is too generic. The cause can be separated from the motive of a crime. A cause could be entrapment (Q1066302), but a motive cannot be. This can also be useful for specifying 'unknown value' in cases that have not yet concluded. Only reasonings of a crime by the suspect would be valid, and sources would be necessary to verify the claims. -wd-Ryan (Talk/Edits) 03:40, 18 May 2025 (UTC)
Discussion
[edit]
Support. Seems useful to distinguish between causes related to the perpetrator and causes related to other agents. Another example where this would be useful might be something like criminal motiverevenge (Q1712140) has cause (P828)adultery (Q234213). –IagoQnsi (talk) 02:28, 22 July 2025 (UTC)
- Good example! -wd-Ryan (Talk/Edits) 16:10, 22 July 2025 (UTC)
Comment Hmm, does this need to be restricted to "criminal"? I think any time you want to describe the reasoning of the person doing the action then "motive" or "motivation" works. ArthurPSmith (talk) 21:21, 22 July 2025 (UTC)
- That's a good point, I agree, I updated the proposal, feel free to add any examples you were thinking of. -wd-Ryan (Talk/Edits) 22:18, 22 July 2025 (UTC)
- Hmm, nothing specific, but I think life events like marriage or relocation (immigration) or change of careers etc. are things that you might often have a stated motive for that would be useful to record. But criminal actions are probably by far the most common case, I just didn't see that it needed to be restricted.
Support by the way. ArthurPSmith (talk) 21:42, 23 July 2025 (UTC)
- Hmm, nothing specific, but I think life events like marriage or relocation (immigration) or change of careers etc. are things that you might often have a stated motive for that would be useful to record. But criminal actions are probably by far the most common case, I just didn't see that it needed to be restricted.
- That's a good point, I agree, I updated the proposal, feel free to add any examples you were thinking of. -wd-Ryan (Talk/Edits) 22:18, 22 July 2025 (UTC)
- Slippery slope, I'm leaning towards an
Oppose. If there is potential for abuse it will be abused, so I think we should stick to documented facts. I think for people who have been accused of something we should explicitly forbid using such a property unless there is a conviction. I don't think any admins want to spend their day cleaning up claims that break the LP policy or links to gossip magazines. There's already plenty of people that abuse Wikidata to call people rapists etc. Maybe that's true in some of the cases, but the same people don't spend any time making sure such statements are entered in the proper manner and making sure they are policy compliant. Infrastruktur (talk) 08:24, 23 July 2025 (UTC)
- Anyone who is looking to abuse Wikidata can already use the broader has cause (P828) property. I don't think this should be a valid reason to stop well-intentioned editors from modeling this data. I specified that sources would be required, and they'd have to be reliable of course. I'll happily check in on the property often to catch abuse. -wd-Ryan (Talk/Edits) 15:05, 23 July 2025 (UTC)
- Just about every property on Wikidata can be abused in one way or another. This information is also documented on countless Wikipedia articles via infobox fields and various categories (e.g. en:Category:Racially motivated violence by target, en:Category:Religiously motivated violence by target, en:Category:Special-interest terrorism, etc), so it doesn't seem controversial to be tracking this info. With a citation-needed constraint (Q54554025) I don't see the issue. Might also help to have property constraint (P2302)conflicts-with constraint (Q21502838)
property (P2306)instance of (P31) . –IagoQnsi (talk) 06:40, 24 July 2025 (UTC)item of property constraint (P2305)human (Q5)
Honji Buddha
[edit]| Description | Buddha that this kami is identified with |
|---|---|
| Represents | honji suijaku (Q3080781) |
| Data type | Item |
| Example 1 | Nyakuichi Ōji (Q11616186)→Eleven-Faced Avalokiteśvara (Q11404731) |
| Example 2 | Izanami (Q682306)→Thousand-Armed Thousand-Eyed Avalokiteśvara (Q10904910) |
| Example 3 | Izanagi (Q813858)→Amitābha Buddha (Q236242) |
| Example 4 | Ame no Oshihomimi (Q462555)→Kṣitigarbha (Q604687) |
| Example 5 | Ninigi (Q1056017)→Nagarjuna (Q171195) |
| Example 6 | Hoori (Q1051960)→Cintāmaṇicakra (Q11446712) |
| Planned use | Add this to the major kami that have known Honji Buddhas |
Motivation
[edit]Honji Buddhas (本地仏、Honjibutsu) are Buddhas that are identified with Kami in Shinbutsu Shugo. I am also proposing the inverse property of a Suijakugami 垂迹本
Discussion
[edit]
Question Could you explain how this differs from incarnation of (P3701)? Bovlb (talk) 21:42, 5 July 2025 (UTC)
- @Bovlb they are similar. But I think the main difference is that an incarnation of implies a mortal person identified as the deity or something like that.
- In this case the kami is not mortal, but is seen as an aspect of the Buddha, or vice versa in some cases.
- Likewise such kami themselves sometimes either are deified humans or incarnated as humans such as Ame-no-Oshikumone or Hachiman.
- I have noticed that the incarnation of property seems to be used for broader purposes than these though. Immanuelle (talk) 22:29, 5 July 2025 (UTC)
- extent of P3701
- I see a few references to "kami" and "buddha" in this list. Bovlb (talk) 23:43, 5 July 2025 (UTC)
- @Bovlb I think you are right on this and that property fulfills the purpose of this one Immanuelle (talk) 00:02, 6 July 2025 (UTC)
- I am still not sure what to do this with Immanuelle (talk) 05:25, 28 November 2025 (UTC)
- I withdrew Wikidata:Property proposal/Suijaku Kami since I think the relationship is a bit asymmetric too Immanuelle (talk) 05:32, 28 November 2025 (UTC)
- @Trade do you have thoughts on the ontology of this one in comparison with Wikidata:Property proposal/Source Shrine Immanuelle (talk) 05:36, 28 November 2025 (UTC)
- I withdrew Wikidata:Property proposal/Suijaku Kami since I think the relationship is a bit asymmetric too Immanuelle (talk) 05:32, 28 November 2025 (UTC)
- I am still not sure what to do this with Immanuelle (talk) 05:25, 28 November 2025 (UTC)
- @Bovlb I think you are right on this and that property fulfills the purpose of this one Immanuelle (talk) 00:02, 6 July 2025 (UTC)
What is the main obstacle to propery creation right now?Immanuelle (talk) 08:43, 2 December 2025 (UTC)
- What is the main obstacle to property creation right now? Immanuelle (talk) 19:08, 1 February 2026 (UTC)
product comes with
[edit]| Description | object which is included with this object, but is not part of it |
|---|---|
| Aliases | comes with|includes|included part(s)|in the box|ships with|sold with |
| Data type | Item |
| Domain | product (Q2424752) |
| Example 1 | Logitech M510 (Q135904184)→Logitech Unifying receiver (Q6667696) |
| Example 2 | Wii (Q8079)→Wii Sports (Q71936) |
| Example 3 | iPhone 4 (Q300890)→Apple Inc. stickers (Q135916340) |
| Example 4 | PlayStation 2 (Q10680)→PlayStation A/V (Composite) cable (Q135916651) |
| Example 5 | PlayStation 2 (Q10680)→DualShock 2 (Q22224358) |
| See also | has part(s) (P527) |
Motivation
[edit]Sources for product models often will detail accessories, adapters, and other items that are packed in with the product. This information is often important for understanding the usefulness and compatibility of an item. If an item has claims that indicate an obscure value for connector (P2935), source of energy (P618), network bands (P8097), etc, it may imply that it is only compatible with very specialized hardware, but often this is not the case if the device comes with adapters/cables/chargers/etc that make it compatible with more common standards. More broadly, this property would also be useful for describing the customer experience of this product, and may tie in to the cultural impact and societal perception of this product.
The scope of this property needs some clarity – I think it should be limited to items that are included all or most of the time, and are considered a fundamental part of the experience of buying this product. For items that are only included as part of limited/special bundles/promotions (such as the numerous games that the Xbox One was bundled with), those are probably better not to include in this property. This is somewhat subjective, but I think in most cases it will be intuitive. –IagoQnsi (talk) 23:20, 20 August 2025 (UTC)
Discussion
[edit]
Support Interesting property for device models. -wd-Ryan (Talk/Edits) 22:58, 21 August 2025 (UTC)
Comment
Support I would definitely change the label to "product comes with" to head off improper use, or make a case for use outside the products domain. With that change, I would be a support.Items that are not always included can be qualified with nature of statement (P5102), point in time (P585), etc. Property should list contains (P4330), connects with (P2789), and maybe operating system (P306) as related (and vice versa), and together with (P1706) as "different from". Swpb (talk) 17:23, 25 August 2025 (UTC)- That all sounds good to me; "product comes with" seems like a good main label. I agree with using qualifiers like that for sometimes-included items; my concern was to make sure this property doesn't end up being a cluttered mess of dozens or hundreds of insignificant one-off deals that certain products have had. Like for the example I gave of Xbox One's numerous bundles – I think that rather than having a link from Xbox One (Q13361286) to every one of those games, it would be more useful to have a more generalized statement like Xbox One (Q13361286)comes withvideo game (Q7889)
nature of statement (P5102)often (Q28962312) . If we really wanted all those individual games listed somewhere, it seems like it'd be better to have, say, a new item called "list of games bundled with the Xbox One" or something (and then we could add a statement is subject of (P805) qualifier to the previous statement to link to the list). But I'm not deadset on this model; would love to hear your thoughts. –IagoQnsi (talk) 19:26, 25 August 2025 (UTC)
- That all sounds good to me; "product comes with" seems like a good main label. I agree with using qualifiers like that for sometimes-included items; my concern was to make sure this property doesn't end up being a cluttered mess of dozens or hundreds of insignificant one-off deals that certain products have had. Like for the example I gave of Xbox One's numerous bundles – I think that rather than having a link from Xbox One (Q13361286) to every one of those games, it would be more useful to have a more generalized statement like Xbox One (Q13361286)comes withvideo game (Q7889)
Question How would this property work with video games? @IagoQnsi:--Trade (talk) 04:49, 4 September 2025 (UTC)
- Like for video games themselves? You could probably say "some game->comes with->user manual" or "some game->comes with->some controller" for games that come with a special controller. Is that what you had in mind? –IagoQnsi (talk) 04:58, 4 September 2025 (UTC)
- You can look at https://www.mobygames.com/game/genre:physical-extras/ to see what i am referring to
- Also some digital games comes with the soundtrack included in a folder so we need to consider that as well. The soundtrack itself is located in a folder in the game directory after you install it Trade (talk) 05:09, 4 September 2025 (UTC)
- Yeah those could definitely be included. For digital soundtracks, we could link to the item for the soundtrack (or just soundtrack (Q217199) if it doesn't have its own item), and have a qualifier "distribution format: digital download". –IagoQnsi (talk) 14:27, 4 September 2025 (UTC)
- Well actually, thinking about it a bit more, if the game is also distributed as a digital download, it seems redundant/unnecessary to have that qualifier. There should probably only be a 'distribution format' qualifier on the 'product comes with' statement if the game has multiple distribution formats, but the object is exclusive to a specific distribution format(s). –IagoQnsi (talk) 19:26, 4 September 2025 (UTC)
- Like for video games themselves? You could probably say "some game->comes with->user manual" or "some game->comes with->some controller" for games that come with a special controller. Is that what you had in mind? –IagoQnsi (talk) 04:58, 4 September 2025 (UTC)
Support --Trade (talk) 19:14, 4 September 2025 (UTC)
Comment: changed the title from 'comes with' to 'product comes with' based on suggestion from User:Swpb. –IagoQnsi (talk) 19:28, 4 September 2025 (UTC)
Oppose What if a single product is sold in many 'package editions'? I think the best way to model this is creating an item for each package, so we can cover all cases in the same way:
| has part(s) |
| ||||||||||||||||||||||||||||||
| add value | |||||||||||||||||||||||||||||||
. --Tinker Bell ★ ♥ 19:56, 5 September 2025 (UTC)
- @Tinker Bell: In cases where a product has many editions and there are good sources that detail those editions, such as major video game consoles, I think having product bundle (Q1020767) instances makes a lot of sense. But the vast majority of products are not documented so thoroughly. For the Logitech M510 (Q135904184), for example, I can find sources (e.g. retail listings, user manuals, etc) to show that it always comes with a Logitech Unifying receiver (Q6667696). But I don't have any data about all the editions it came in in the 14 years it was on the market. Anecdotally, I've seen that the logo on it changed at least twice, that red and blue editions existed at some point, that they switched to a matte finish at some point, and that there are numerous versions of the packaging; however, I wouldn't be able to find reliable sources providing concrete info about these versions that we could use in Wikidata. And even for those few products that do have well-documented editions, there are still some objects that are always included that would be nice to have linked from the main item, as they can give hints about compatibility or the most common ways the product was experienced (e.g. all editions of the PlayStation 2 always came with a Composite cable, which confirms that it's compatible with Composite and gives a hint that that may have been a common way to connect the PS2 to a TV). –IagoQnsi (talk) 21:04, 5 September 2025 (UTC)
formally denounced by
[edit]Motivation
[edit]We have endorsed by (P8001) for when someone makes a public announcement approving of someone/something; it seems valuable to be able to make the same connection for public announcements of disapproval.
I listed determination method or standard (P459) as a required qualifier to discourage trivial uses of this property. It should only be used in cases where the denouncement has been made explicit and formalized in some way – it should be possible to describe the method/standard by which it was formalized. –IagoQnsi (talk) 20:52, 29 September 2025 (UTC)
Discussion
[edit]
Support --Trade (talk) 12:33, 2 October 2025 (UTC)- we could add the obligation of putting a deprecated rank when this is sone by organizations that don't have any evidence to support their claims. ON the contrary this could be used/look like legit denunciation when it's actually only a communication strategy (for example in the case of Anti-abortion movements) --Haymillefolium (talk) 21:02, 23 November 2025 (UTC)
- What are you talking about @Haymillefolium:--Trade (talk) 01:56, 28 November 2025 (UTC)
- for example, I'm an anti-abortion activist, I denounce pro-abortion group from killing babies. This could appear on wikidata using this property, but they are unfounded denunciations. So the statement should have a deprecated rank.
- We also have a lot of politician doing SLAPP https://en.wikipedia.org/wiki/Strategic_lawsuit_against_public_participation. They should have a deprecated rank Haymillefolium (talk) 18:18, 30 November 2025 (UTC)
- this seem related to this property proposal that aims to avoid creating statements that are not based on reliable sources. Haymillefolium (talk) 18:22, 30 November 2025 (UTC)
- The point of the property is not to try to say whether or not the denunciation was fair and just, but just to say whether it happened. We as Wikidata are not saying "the invasion of Ukraine was bad"; we're just saying "the United Nations passed a resolution saying the invasion of Ukraine was bad". By their nature, most denunciations will be seen as unfounded or unfair by someone (why bother to denounce something that everyone already agrees is bad?), but that doesn't mean they're not worth documenting.
- I think the "formally" part is really important – there should be the expectation that the entity making the denunciation has some sort of formal process for doing so. So an individual or activist group simply putting out a press release against an abortion care provider wouldn't belong in this property, because it's just a one-off publication; there was no process used to make that decision. But if there was an activist group that maintained a list of care providers that they do/don't oppose based on some criteria, that would be more likely to be appropriate for this property.
- That's not to say that we are assuming that whatever formal process they have is good or fair or unbiased. For example, we might use this property for the Extremist Files maintained by the Southern Poverty Law Center, even though the SPLC has faced some political opposition in recent years and is certainly not a neutral party. The point is not for us to say "Andrew Tate is an extremist", which is an opinion, but rather to say "SPLC has included Andrew Tate in their Extremist Files", which is a fact. We'd just be tracking who has denounced whom, and it's up to the data consumer/reader to decide whose denunciations carry any weight. –IagoQnsi (talk) 17:36, 1 December 2025 (UTC)
- yes I totally agree with all this. I was just saying that the statement can be confusing and formulating the necessity to add a deprecated rank for unfounded denunciations seems an important thing to me. Even a institutions can "formally" denounce another one for political or communication reason that had nothing to do with facts (facts are reported by independent medias). Haymillefolium (talk) 22:18, 1 December 2025 (UTC)
Credibly accused of
[edit]| Description | entity (person or organization) that has been credibly accused of a crime or serious misconduct, but is not (yet) convicted |
|---|---|
| Represents | suspect (Q224952) |
| Data type | Item |
| Example 1 | LIBI fund (Q12411149)→misappropriation of public funds (Q3045366) |
| Example 2 | Alliance Forêts Bois (Q107418411)→deforestation (Q169940) |
| Example 3 | Energoatom (Q938225)→corruption (Q366) |
| Allowed values | Q83267 |
Motivation
[edit]Wikidata currently provides the property convicted of (P1399), which models crimes only after a formal judicial conviction. However, convictions alone do not fully capture the social, historical, or political significance of many cases where individuals or organizations are credibly accused but not convicted, sometimes due to reasons unrelated to truth or evidence.
Large corporations or powerful personalities often use vast financial and legal resources to delay or fragment judicial processes for years or decades. These delays prevent convictions from being issued even when accusations are widely substantiated through investigations, whistleblower reports, or NGO findings.
Examples and sources:
- Corporations strategically prolong litigation (“slow justice”) https://www.sciencedirect.com/science/article/pii/S0959378023001280
- Corporate accountability mechanisms show major obstacles in bringing multinational firms to justice https://media.business-humanrights.org/media/documents/files/documents/New_Mechanisms_for_Accountability.pdf
- “Stalled litigation” used as a tactic that undermines judicial process https://lexlaw.co.uk/solicitors-london/when-stalled-litigation-is-an-abuse-of-the-proper-process-of-the-court/
- Historical example: **Wiwa v. Royal Dutch Shell Co.**, where Shell delayed litigation for over 10 years. Well-documented case illustrating obstruction through procedural tactics https://en.wikipedia.org/wiki/Wiwa_v._Royal_Dutch_Shell_Co. There is also the case of dupont and pfoa : https://en.wikipedia.org/wiki/DuPont#Perfluorooctanoic_acid_(PFOA;_C8;_%22forever_chemicals%22).
- Israel files : when a government influence the outcome of juridical process : https://www.mediapart.fr/journal/dossier/international/israel-files
On top of that research shows that:
- socio-economic bias influences who gets arrested or prosecuted. The crime of being poor (arXiv:2303.14128)
- systemic racial disparities in criminal justice are documented. https://en.wikipedia.org/wiki/Lammy_Review
These cases show that powerful companies can avoid judicial outcomes for extremely long periods meaning that Wikidata cannot represent credible, well-documented accusations for decades if it relies only on the convicted of (P1399) property.
We should also note that absence of conviction is not a reliable indicator of absence of wrongdoing. Focusing only on convictions creates a structural blind spot in Wikidata. We should also raise that a tribunal can be wrong and can be corrupt. We need wikidata to stay a reliable place to find informations about criminals and the judicial system is not the only source that exist.
An important point is also to note that you can be convicted of things that are not crimes. For example homosexuality is a crime according to some tribunals : https://www.wikidata.org/wiki/Q113867078. This also reflect the need to have a more generic and neutral property, allowing only rational allegations.
Therefore, the proposed property would allow Wikidata to capture credible allegations with reliable sources (NGO reports, regulatory filings, investigative journalism, court documents, etc.) without waiting for convictions that may be delayed, obstructed, or rendered impossible due to power inequality.
Has a summary this property:
- complements (but does not replace) convicted of (P1399)
- allows Wikidata to represent socially relevant accusations
- reduces bias created by strict reliance on convictions
- improves representation of corporate wrongdoing that remains unconvicted for procedural reasons
- increases transparency for researchers, journalists, NGOs, and the public
For reference a related proposition was made here https://www.wikidata.org/wiki/Wikidata:Property_proposal/accused, it's not the same proposition but it's closely related. – The preceding unsigned comment was added by Haymillefolium (talk • contribs) at 21:48, 23 November 2025 (UTC).
Discussion
[edit]- As I explained in the other discussion, I do not think WD can host this information, for both legal reasons and because the term "credible" means very different things to people on each side of an issue. So
Oppose. Vicarage (talk) 18:27, 24 November 2025 (UTC)
- which legal reason are you refering to ? "credible" could be defined as a source that follows the conditions from https://www.wikidata.org/wiki/Help:Sources Haymillefolium (talk) 12:59, 27 November 2025 (UTC)
- I don't know where WD is based legally (Germany?) but you'd be very unwise to repeat here a claim from a source in a different legal jurisdiction. And that source might have the legal resources to fight libel claims that WD does not have. I would want to see a formal opinion from WD's legal team on this matter before lifting my opposition. Vicarage (talk) 13:46, 27 November 2025 (UTC)
- it make no sense to accuse wikidata of defamation, wikidata is a db, it doesn't say anything, it save data. If a complain would be made it would be against the source that is actually making the statement.
- I doubt you will be able to have an opinion from a lawyer from the wikimedia foundation. Feel free to try if you want.
- Take into account that defamation is used has a way to silence critical voices. Opposing the property here using this argument seems to go on the road of censorship. It blocks the possibility to save and analyse publicly available information. see https://en.wikipedia.org/wiki/Defamation#Criticism Haymillefolium (talk) 14:55, 27 November 2025 (UTC)
- also see : https://en.wikipedia.org/wiki/Strategic_lawsuit_against_public_participation. This is interesting and also demonstrated that the other property that could be used (charged) is not enough to show credible accusations since big organizations use tribunals as a tool to silence oppositions. Haymillefolium (talk) 14:58, 27 November 2025 (UTC)
- I don't know where WD is based legally (Germany?) but you'd be very unwise to repeat here a claim from a source in a different legal jurisdiction. And that source might have the legal resources to fight libel claims that WD does not have. I would want to see a formal opinion from WD's legal team on this matter before lifting my opposition. Vicarage (talk) 13:46, 27 November 2025 (UTC)
- which legal reason are you refering to ? "credible" could be defined as a source that follows the conditions from https://www.wikidata.org/wiki/Help:Sources Haymillefolium (talk) 12:59, 27 November 2025 (UTC)
Comment It's notable that after so many tries, and such a lengthy proposal, it doesn't address anything from Wikidata:Living people. Please take the time to make sure that this proposal have a thoughful approach to this. Ainali (talk) 20:38, 24 November 2025 (UTC)
- I cannot find a proper debate around the living people policy in the past proposition (nobody explain which part of the policy the propositon would go again). In the current case I don't think there is a risk to go again privacy because we would only allow sourced statements. If there is a reliable source it mean it's public knowledge. Which is explicitly allowed by the living person policy.
- Since wikidata allow primary source we could force a deprecated rank for them or even forbid them on the property (and make secondary or tertiary source mandatory).
- We could also add on the property description that this property is meant for organizations/institutions and for public personalities. Living people would be protected by the living people policy anyways. Haymillefolium (talk) 13:14, 27 November 2025 (UTC)
- Zelensky is credibly accused of supporting neo-Nazism, Biden is credibly accused of electorial fraud, Netanyahu is credibly accused of genocide. Yeah, they are so credible as promoted by brainless media, but in the context of legal dispute, it should be the court to decide which is credible and which is fake, not media. If a court ruling does not exist, then by definition it is both completely credible and completely void at the same time, depending on whether one supports defendants or plantiffs, rather than the law. Midleading (talk) 03:55, 5 December 2025 (UTC)
- let's use your examples, can you give a source that show that "Zelensky is credibly accused of supporting neo-Nazism" or "Biden is credibly accused of electorial fraud" ? I doubt you will find any credible source. So this property could not be used for these false claims. I don't ask about Netanyahu because there is too much sources that show there is a genocide in Gaza. So yeah I suppose their must be credible sources that state "Netanyahu is credibly accused of genocide".
- Also you didn't not respond to any arguments again the fact that only relying on tribunals to state who did a crime is subject to a lot of biases. For example there are tribunals that consider homosexuality is a crime. Haymillefolium (talk) 11:33, 6 December 2025 (UTC)
Strong oppose Who says that? —Eihel (talk) 00:17, 19 December 2025 (UTC)
- who says what ? Haymillefolium (talk) 22:03, 19 December 2025 (UTC)
- What do you think my question might be about, Haymillefolium? —Eihel (talk) 16:47, 21 December 2025 (UTC)
- if I knew I wouldn't ask ^^' Haymillefolium (talk) 13:50, 23 December 2025 (UTC)
- What do you think my question might be about, Haymillefolium? —Eihel (talk) 16:47, 21 December 2025 (UTC)
- who says what ? Haymillefolium (talk) 22:03, 19 December 2025 (UTC)
- Oppose this is going to cause problems. Who is deciding what's credible? Secretlondon (talk) 07:45, 16 January 2026 (UTC)
- Secondary sources has state in the proposal Haymillefolium (talk) 09:06, 14 February 2026 (UTC)
public key
[edit]| Description | cryptographic public key (some ASCII encoding of it) |
|---|---|
| Data type | String |
| Example 1 | OpenBSD (Q34215)RWQQC1M9dhm/tja/ktitJs/QVI1kGTQr7W7jtUmdZ4uTp+4yZJ6RRHb5 |
| Example 2 | OpenWrt (Q1140401)RWTTEMbygz6X95lKDAulctZy3aj15823THXfyrfXgwGbxZlXBd2brNcw |
| Example 3 | CalyxOS (Q105543963)RWQTW06MSf6MS4v/jKlIadiOuj4eO3OVRkU7e06qwoBIErmXapAs3iSP |
| Example 4 | James Bond (Q2009573)ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIELDJGi+7kchVkEJNgqGvLOT2UOS4CP5HUSUBdyATdfc |
Motivation
[edit]We have public key fingerprint P3721 property, but not yet more fundamental public key one, which is often used directly, especially e.g. for elliptic curve crypto, because of significantly shorter keys when compared to traditional RSA.
Example of direct public key usage is SSH keys or some operating system package repository signing keys.
—Mykhal (talk) 13:24, 19 October 2025 (UTC)
Discussion
[edit]The SSH example would probably have to have the key type like ssh-ed25519 as a qualifier separately. If we want to allow it included (as in the original James Bond example; btw found here) or not depends also on if we would like to allow white space characters or not. —Mykhal (talk) 13:29, 19 October 2025 (UTC)
- What qualifier would you use to indicate which algorithm is being used? Vicarage (talk) 15:43, 20 October 2025 (UTC)
- Not sure yet. E.g. checksum uses determination method or standard. I don't see "algorithm" or even "key type" among existing qualifiers (of total 290, currently). Not sure if we want specific ones like these. —Mykhal (talk) 16:05, 20 October 2025 (UTC)
Comment I have several things to note about this:
- String fields in Wikidata have a maximum length of 1500 characters - that limits the key length that can be represented, but maybe we don't need to worry about that yet.
- If these Wikidata statements are used to confirm identities it seems likely that malicious actors may try to abuse this by changing the values.
- Wasn't there a development effort to add "signed statements" to Wikidata? This seems relevant/related...
- ArthurPSmith (talk) 16:02, 20 October 2025 (UTC)
Comment Not sure if Wikidata is a place for such data. Sourcing keys from identifier of a specialized database like Keybase username (P6837) is more reliable. Midleading (talk) 08:25, 21 October 2025 (UTC)
Comment I support it in general but think it may need some technical changes before it can be implemented well such as a tool that makes sure it's in sync with public key databases and locking the value to a certain group of users or things like that. Prototyperspective (talk) 22:35, 23 October 2025 (UTC)
neuter form of label
[edit]| Description | neuter form of name or title |
|---|---|
| Represents | neuter (Q1775461) |
| Data type | Monolingual text |
| Domain | occupation (Q12737077) and position (Q4164871) |
| Example 1 | blogger (Q8246794)→blogueur·euse (French) |
| Example 2 | hetaera (Q466118)→no value |
| Example 3 | niece or nephew (Q76477)→nibling (English) |
| Example 4 | entrepreneur (Q131524)→ondernemer (Dutch) |
| Planned use | I plan to introduce a neutral form of label for titles and functions that are currently marked as either feminine or masculine, as some gender-neutral terms are still assigned gendered labels at the moment. This work will be carried out mainly in French and Dutch. |
| Expected completeness | always incomplete (Q21873886) |
| See also | female form of label (P2521) and male form of label (P3321) |
Motivation
[edit]In Dutch, many words are neuter, or the masculine form also serves as the neuter form. For example, ondernemer can be both masculine and neuter, while onderneemster is feminine. In French, a recent trend has emerged to create explicitly neutral forms, such as entrepreneur·euse, which serves as a neutral alternative to the masculine entrepreneur and the feminine entrepreneuse. Jhowie Nitnek 10:29, 7 November 2025 (UTC)
Discussion
[edit]
Support if there isn't a property for this already. Applicable to English sometimes, too. -wd-Ryan (Talk/Edits) 01:04, 8 November 2025 (UTC)
Oppose lexemes are a better place for this information. ChristianKl ❪✉❫ 21:52, 10 November 2025 (UTC)
Support Necessary complement of female form of label (P2521) and male form of label (P3321), see Property talk:P2521. Midleading (talk) 14:01, 7 January 2026 (UTC)
flag carrier of
[edit]| Description | country of which the airline is the flag carrier |
|---|---|
| Aliases | national carrier of |
| Represents | flag carrier (Q721639) |
| Data type | Item |
| Domain | airline (Q46970) |
| Example 1 | Singapore Airlines (Q32245)→Singapore (Q334) |
| Example 2 | Emirates (Q180432)→United Arab Emirates (Q878) |
| Example 3 | Malaysia Airlines (Q308952)→Malaysia (Q833) |
| Example 4 | British Airways (Q8766)→United Kingdom (Q145) |
| Example 5 | Air France (Q131005)→France (Q142) |
| Example 6 | Lufthansa (Q9325)→Germany (Q183) |
| Source | Flag carrier on English Wikipedia |
| Property constraint | property constraint (P2302)subject type constraint (Q21503250) |
| Wikidata project | WikiProject Aviation (Q53054) |
Motivation
[edit]Useful for what airline is the flag carrier of a country.
See also this archived discussion: Wikidata:Property proposal/Archive/2#National Carrier of
Notified participants of WikiProject Aviation
DinhHuy2010 (talk) 14:31, 8 November 2025 (UTC)
Discussion
[edit]
Comment The enwiki page on this indicates it could be used for shipping as well as airlines, although it doesn't list any specific examples and the page is mostly focused on airlines. It also suggest this designation is somewhat obsolete as many formerly national airlines have privatized, and international routes now enjoy significant competition. Anyway it would be nice to maybe add some examples here to be clearer what is covered (does this include shipping, can one country have multiple flag carriers?) ArthurPSmith (talk) 17:38, 8 November 2025 (UTC)
- @ArthurPSmith, this property is only restricted to airlines and one country can multiple flag carriers (like the UAE with Emirates and Eithad Airways) DinhHuy2010 (talk) 03:00, 9 November 2025 (UTC)
- Ok, I think
Support as proposed, this is fine. ArthurPSmith (talk) 16:59, 10 November 2025 (UTC)
- Ok, I think
- @ArthurPSmith, this property is only restricted to airlines and one country can multiple flag carriers (like the UAE with Emirates and Eithad Airways) DinhHuy2010 (talk) 03:00, 9 November 2025 (UTC)
Comment I might be wrong, but wouldn't this be more useful on the country itself? So, Singapore (Q334)flag carrierSingapore Airlines (Q32245). -wd-Ryan (Talk/Edits) 15:44, 10 November 2025 (UTC)
Oppose When I ask ChatGPT whether the term is well-defined or is used by different people to mean different things I get as an answer "“Flag carrier” isn’t one single, universally defined legal category. People use it in a few different ways." A Wikidata property needs a well-defined meaning. ChristianKl ❪✉❫ 23:42, 10 November 2025 (UTC)
Oppose Not a clear definition for what a flag carrier is. @User:DinhHuy2010 Who is setting the requirement and criterias for an airline to be a flag carrier?Pmt (talk) 16:15, 17 November 2025 (UTC)
Yandex Object Answer id
[edit]| Description | identifier for an entry in Yandex Object Answer database |
|---|---|
| Represents | no label (Q24936061) |
| Data type | External identifier |
| Domain | generic |
| Example 1 | Yandex (Q5281)→0oCgdydXc5NzQ0GAJdVXKu |
| Example 2 | Moscow (Q649)→0oCgVydXc3MRgC4YVa5Q |
| Example 3 | Microsoft Windows (Q1406)→0oCgdydXc5ODc5GAJ0pr8K |
| Example 4 | Eiffel Tower (Q243)→0oCghydXczNTUzMxgCYGIWkg |
| Example 5 | Steve Jobs (Q19837)→0oCghydXc1NTk0NBgChTEysQ |
| Allowed values | /[a-z0-9-]+/i |
| Expected completeness | always incomplete (Q21873886) |
| Formatter URL | https://yandex.com/search?text=1&ento=$1 |
| See also | Google Knowledge Graph ID (P2671) |
| Single-value constraint | yes |
Motivation
[edit]Object Answer (previously Entity Search) is a knowledge database by Yandex (Q5281) similar to Google Knowledge Graph (Q648625) which allows for displaying a card or rich snippet with a summary of a searched topic referencing different websites, including Wikimedia projects. The id of a topic can be obtained by opening the Network tab in the browser’s Developer Tools while viewing a page that contains such a snippet, and then searching for \"name":"ento","value":\.
One caveat is that Yandex doesn't allow the empty search queries. Therefore, when retrieving a card by id, some additional ?text= should be included in the query (e.g. [3]).
The tech doesn't have a proper English name; however, "Object Answer" seems to be the best fit. Vonavy (talk) 03:23, 16 November 2025 (UTC)
Discussion
[edit]SignWriting transcription
[edit]| Description | representation in SignWriting |
|---|---|
| Represents | SignWriting (Q1497335) |
| Data type | String |
| Example 1 | beckoning sign (Q17067098) → M517x516S16e30494x496S22114484x485 |
| Example 2 | ILY sign (Q5971828) → M514x515S19c20486x486 |
| Example 3 | headshake (Q1761394) → M518x524S30122482x476 |
| Example 4 | blowing a raspberry with tongue out and hands beside head (Q118368427) M545x518S35a04482x483S33530476x496S14c20518x484S14c28459x484S22520513x470S22520455x471 |
| Allowed values | (M(2[5-9][0-9]|[3-6][0-9]{2}|7[0-4][0-9])x(2[5-9][0-9]|[3-6][0-9]{2}|7[0-4][0-9])(S[123][0-9a-f]{2}[0-5][0-9a-f](2[5-9][0-9]|[3-6][0-9]{2}|7[0-4][0-9])x(2[5-9][0-9]|[3-6][0-9]{2}|7[0-4][0-9]))+( )*)+ |
| Planned use | To be used primarily as main value in instances of gesture (Q371174), facial expression (Q327968), and sign (Q20921471). |
| Formatter URL | https://steveslevinski.me/demo/fsw.html?text=$1 |
Motivation
[edit]Especially useful for items that do not yet have a visual representation available in Commons. The symbols can be properly visualized using the FSW Viewer (URL above; example: [4]) or, without leaving Wikidata, through this script. It's kinda similar to those chemistry properties like canonical SMILES (P233). Enaldo(discussão) 08:53, 20 November 2025 (UTC)
Discussion
[edit]
Comment I edited the regular expression to also match compound signs, wether or not separated by space (" "), as pointed out by Slevinski in the talk page of this proposal. Enaldo(discussão) 10:14, 4 December 2025 (UTC)
Comment why not use the Unicode symbols as deffiend in Sutton SignWriting (Q21040766)? JhowieNitnek (talk) 16:22, 9 January 2026 (UTC)
- The official Unicode SignWriting block is not sufficient to fully define a sign. Unicode encodes individual symbols only; it does not include the characters needed to represent structural markers or spatial relationships, which are essential for defining a complete sign.
- In addition, the Unicode encoding is not compatible with existing community data because it includes facial diacritics that are not used in current datasets.
- Finally, there is currently no real-world SignWriting data that uses the official Unicode encoding, whereas FSW is already widely used and supported by existing tools and data. -Slevinski (talk) 20:41, 15 January 2026 (UTC)
- Thank you for the clarification, I wasn’t aware of these limitations. In any case, I still
Support this, as it feels essential for Deaf and hard-of-hearing communities, and for representing movement in a way that is computer-readable. JhowieNitnek (talk) 21:24, 15 January 2026 (UTC)
- Thank you for the clarification, I wasn’t aware of these limitations. In any case, I still
Kvinnehistorie.no topics ID
[edit]| Description | Identifier for a person in Kvinnehistorie.no Identifier for a topic in the internet encyclopedia Kvinnehistorie.no |
|---|---|
| Represents | online encyclopedia (Q615699) internettensyklopedi |
| Data type | External identifier |
| Template parameter | identifier |
| Domain | All kind of types within items related to women's history (Q1279400) |
| Example 1 | Sigrid Boo (Q4131954) → Sigrid Boo |
| Example 2 | Eli Aanjesen (Q15972364) → Eli Aanjesen |
| Example 3 | Hagbard Berner (Q955114) → Hagbart Emanuel Berner |
| Allowed values | [A-Za-z0-9_-]+ |
| Source | https://www.kvinnehistorie.no/ |
| Planned use | in Template:Authority control (Q3907614) |
| Number of IDs in source | xxxxx |
| Expected completeness | always incomplete (Q21873886) |
| Formatter URL | https://www.kvinnehistorie.no/person/$1 |
| Robot and gadget jobs | Mix 'n' Match |
| Applicable "stated in"-value | no label (Q136881278) |
| Distinct-values constraint | yes |
Motivation
[edit]Usefull identifier for norvegian persons and for documenting norvegian female history (Legg inn motivering/begrunnelse for forslaget til denne egenskapen her.) – The preceding unsigned comment was added by Pmt (talk • contribs) at 11:57, November 21, 2025 (UTC).
Discussion
[edit]
Comment Since this seems to have been duplicated as Wikidata:Property proposal/Kvinnehistorie.no persons ID, I guess this proposal should be aborted somehow. (But I don't know the procedure.) Bergenga (talk) 20:46, 8 January 2026 (UTC)
- Never mind what I just wrote. I only looked at the examples, that were identical to the other one. But I now see that the URLs are different and it is a different namespace. One different example I figured out is:
- International Women's Day in Norway (Q117454463) → 8. mars
- Looking at the full list of topics, there are only 27 in total so far. How many of them can we actually connect to a WD item?
- I will not give my support before a full set of examples has been made (that are different from the other proposal) and it is clear how many IDs we can actually use. Bergenga (talk) 21:08, 8 January 2026 (UTC)
Kvinnehistorie.no persons ID
[edit]| Description | identifier for an item in the internet encyclopedia Kvinnehistorie.no |
|---|---|
| Represents | online encyclopedia (Q615699) internettensyklopedi |
| Data type | External identifier |
| Template parameter | identifier |
| Domain | All kind of types within items related to women's history (Q1279400) |
| Example 1 | Sigrid Boo (Q4131954) → Sigrid Boo |
| Example 2 | Eli Aanjesen (Q15972364) → Eli Aanjesen |
| Example 3 | Hagbard Berner (Q955114) → Hagbart Emanuel Berner |
| Allowed values | [A-Za-z0-9_-]+ |
| Source | https://www.kvinnehistorie.no/ |
| Planned use | in Template:Authority control (Q3907614) |
| Number of IDs in source | 33 |
| Expected completeness | always incomplete (Q21873886) |
| Formatter URL | https://www.kvinnehistorie.no/person/$1 |
| Robot and gadget jobs | Mix 'n' Match |
| Applicable "stated in"-value | no label (Q136881278) |
| Distinct-values constraint | yes |
Motivation
[edit]Usefull identifier for norvegian persons and for documenting norvegian female history (Legg inn motivering/begrunnelse for forslaget til denne egenskapen her.) – The preceding unsigned comment was added by Pmt (talk • contribs) at 17:15, November 20, 2025 (UTC).
Discussion
[edit]
Support. --Wyslijp16 (talk) 16:10, 25 December 2025 (UTC)
Support Bergenga (talk) 20:42, 8 January 2026 (UTC)
Comment 33 is a very small number for an external id in wikidata. Generally described at URL (P973) works for limited cases like this. ArthurPSmith (talk) 17:50, 9 January 2026 (UTC)
Support Rzuwig► 09:22, 23 January 2026 (UTC)
Support. Geagea (talk) 12:04, 30 January 2026 (UTC)
concurring opinion by
[edit]| Description | judicial opinion agreed to by less than half of the members of a court agreeing with the majority's final decision but providing different or additional reasons |
|---|---|
| Represents | concurring opinion (Q1087840) |
| Data type | Item |
| Template parameter | |concurring= in w:en:Template:Infobox court case|Concurrence= in w:en:Template:Infobox SCOTUS case |
| Domain | court decision (Q327000) legal case (Q2334719) |
| Example 1 | Roe v. Wade (Q300950)concurring opinion byWarren E. Burger (Q346685) |
| Example 2 | Citizens United v. Federal Election Commission (Q1092602)concurring opinion byJohn Roberts (Q11153) |
| Example 3 | Dred Scott v. Sandford (Q690462)concurring opinion byJames Moore Wayne (Q1250079) |
| Expected completeness | eventually complete (Q21873974) |
| See also | majority opinion by (P5826) |
Motivation
[edit]Similar to majority opinion by (P5826) in justification (see the proposal). I also plan to make a proposal for 'dissenting opinion by' at some point later today when I have time, which I don't imagine will have any issues if this is accepted for creation. GTink911 (talk) 23:47, 24 November 2025 (UTC)
Discussion
[edit]MJ character glyph name
[edit]| Description | Chinese character glyph identifier issued by Moji Joho Kiban Project |
|---|---|
| Represents | Moji Joho Kiban Ideographs (Q65229515) |
| Issued by | Information-technology Promotion Agency (Q4346801) |
| Data type | External identifier |
| Domain | item, sinogram (Q17300291) |
| Example 1 | 辺 (Q54884396)→MJ025758,MJ025759 |
| Example 2 | 𩼪 (Q109882614)→MJ055352,MJ055353 |
| Example 3 | 㐇 (Q109781882)→MJ067953 |
| Example 4 | 塚 (Q55407990)→MJ009215,MJ009216 |
| Example 5 | 塚 (U+FA10) (Q87541848)→MJ030194,MJ030195 |
| Allowed values | MJ[0-9]{6} |
| Source | https://moji.or.jp/mojikibansearch/basic |
| Number of IDs in source | 58862 |
| Expected completeness | eventually complete (Q21873974) |
| Implied notability | Wikidata property for an identifier that suggests notability (Q62589316) |
| Formatter URL | https://moji.or.jp/mojikibansearch/info?MJ%E6%96%87%E5%AD%97%E5%9B%B3%E5%BD%A2%E5%90%8D=$1 |
| Country | Japan (Q17) |
| Applicable "stated in"-value | Moji Joho Kiban Ideographs (Q65229515) |
| Distinct-values constraint | yes |
| Wikidata project | WikiProject CJKV character (Q114615731) |
Motivation
[edit]Currently, only Kanjipedia kanji ID (P11318) exists as an identifier for kanji (Q82772). It is expected that this property will complement the information regarding kanji (Q82772).TAKA647 (talk) 08:35, 25 November 2025 (UTC)
Discussion
[edit]
Notified participants of WikiProject Nihongo
@TAKA647: is there no unicode codepoint for MJ025759 (辺 with two drops in the upper left corner)?Shisma (talk)
- MJ025758 and MJ025759 are same unicode codepoint U+8FBA (see also https://unicode.org/L2/L2010/10038-fcd10646-main.pdf page 118). To distinguish these, it is necessary to use Variation Selectors Supplement (Q2494109).--TAKA647 (talk) 04:13, 4 December 2025 (UTC)
- @TAKA647: I was just thinking that perhaps there should be a separate entity representing each of the variants, independently of the unified glyph. -Shisma (talk) 19:28, 14 December 2025 (UTC)
- I think creating other entities for characters to which VS is applied is inconvenient. Some characters to which IVD is applied have fewer properties, so they are not particularly noteworthy. TAKA647 (talk) 09:43, 18 December 2025 (UTC)
- @TAKA647: I was just thinking that perhaps there should be a separate entity representing each of the variants, independently of the unified glyph. -Shisma (talk) 19:28, 14 December 2025 (UTC)
Notified participants of WikiProject CJKV character
Cookpad Recipe ID
[edit]| Description | numeric identifier for a recipe on Cookpad, an established cooking website |
|---|---|
| Represents | Cookpad Inc. (Q5167165) |
| Data type | External identifier |
| Domain | recipe (Q219239) |
| Example 1 | focaccia (Q832791) → 25061473 |
| Example 2 | onigiri (Q13393) → 21356906 |
| Example 3 | tres leches cake (Q1579751) → 15161295 |
| Allowed values | \d+ |
| Source | https://cookpad.com/eng/ |
| Expected completeness | always incomplete (Q21873886) |
| Formatter URL | https://cookpad.com/eng/recipes/$1 |
| See also | Food.com ID (P9840), Marmiton ID (P9769) |
| Single-value constraint | yes |
Motivation
[edit]I think this Wikidata property related to food and eating (Q23038310) would be useful as a reference for international recipe documentation. Dianaah89 (talk) 14:32, 1 December 2025 (UTC)
Discussion
[edit]
Support --Kdkeller (talk) 20:49, 9 December 2025 (UTC)
Oppose not sure what this property is useful for as it is. Plus the examples seem very wrong; the item is about a general food but the identifiers are for specific recipes. If you look at the website, there is 224 recipes for focaccia (Q832791): https://cookpad.com/eng/search/focaccia?event=search.suggestion&order=recent If you compare with Marmiton ID (P9769) (which is barely used), the link is to the general 'category' for the food, not to a specific recipe. Cheers, VIGNERON (talk) 15:53, 4 January 2026 (UTC)
Oppose agree with VIGNERON. Sjoerd de Bruin (talk) 17:34, 4 January 2026 (UTC)
Oppose Empat Tilda (talk) 18:19, 4 January 2026 (UTC)
Oppose similar to what VIGNERON said, it seems does not represent authority files in recipes, look at this recipes for rendang theres only one entity of rendang (Q1520293) and using this property would ended up chaining multiple values from the site, each recipe created by some user, cluster perhaps?. Happy New Year 2026!Yamato Shiya大和 士也 (Talk • Contribs) 02:56, 5 January 2026 (UTC)
Not done Lack of support --Trade (talk) 15:13, 15 February 2026 (UTC)
Braille represents
[edit]| Description | graphene or phone that the Braille cell represents |
|---|---|
| Represents | Braille script (Q79894) |
| Data type | Item |
| Domain | grapheme (Q2545446) and phone (Q202064) |
| Example 1 | Braille pattern dots-0 (Q17021457)→space (Q380933) |
| Example 2 | Braille pattern dots-13 (Q17021759)→K/k (Q9922) |
| Example 3 | Braille pattern dots-13 (Q17021759)→ક (Q4208907) |
| Example 4 | Braille pattern dots-1 (Q17021474)→open front unrounded vowel (Q845073) |
| Allowed values | Braille cell (Q135261272) |
| Planned use | Adding the grapheme or phone to the corresponding Braille cell. |
| Expected completeness | eventually complete (Q21873974) |
| See also | Wikidata:Property proposal/Braille transcription |
Motivation
[edit]I believe it would be valuable for Braille cells to have their corresponding graphemes and phones (for IPA). Since Braille differs across languages, the writing system (P282) should be a mandatory qualifier. This would improve accessibility and provide a structured way to link written characters with their tactile representations. JhowieNitnek (talk) 20:06, 4 January 2026 (UTC)
Discussion
[edit]
Comment: Couldn't this be done now with represents (P1268)? Trivialist (talk) 22:13, 4 January 2026 (UTC)
- It does seem this is handled now with represents (P1268). ArthurPSmith (talk) 20:18, 5 January 2026 (UTC)
Oppose It would be more valuable to link to the braille from the character's item instead, as represents (P1268) is already widely used. -wd-Ryan (Talk/Edits) 15:13, 9 January 2026 (UTC)
- Thats why I also propposed Wikidata:Property proposal/Braille transcription JhowieNitnek (talk) 15:24, 9 January 2026 (UTC)
Uni24k indentifier
[edit]| Description | Identifier Uni24k (universities) |
|---|---|
| Represents | university (Q3918) |
| Data type | External identifier |
| Example 1 | Harvard University (Q13371) → 16283 |
| Example 2 | Sorbonne University (Q41497113) → 4405 |
| Example 3 | Paris Diderot University (Q1235608) → 4386 |
| Formatter URL | https://uni24k.com/u/$1 |
Motivation
[edit]Identifier that might be usefull for universites. The website shows informations of domains, exigences degrees, date, website, price... --Tasye24 (talk) 12:55, 7 January 2026 (UTC)
Discussion
[edit]
Support Nice, I wasn't aware of this university id. ArthurPSmith (talk) 19:03, 8 January 2026 (UTC)
Wikifunctions object
[edit]| Description | ZID of the Wikifunctions object |
|---|---|
| Represents | Wikifunctions object (Q121306412) |
| Data type | External identifier |
| Domain | object (Q216601) |
| Example 1 | Wikifunctions object (Q121306412)→Z1 |
| Example 2 | data type (Q190087)→Z4 |
| Example 3 | Boolean data type (Q520777)→Z40 |
| Example 4 | conditional (Q817862)→Z802 |
| Expected completeness | always incomplete (Q21873886) |
| Formatter URL | https://www.wikifunctions.org/wiki/$1 |
| See also | Commons category (P373) |
| Single-value constraint | yes |
| Distinct-values constraint | yes |
Motivation
[edit]I think it would be useful to have the Wikifunctions object linked directly on the corresponding Wikidata item, in the same way as the Commons category (P373), even though it is already available in the Multilingual sites section at the bottom of the Wikidata item.
Improvements or suggestions to refine this proposal are always welcome, as I am not entirely sure how to propose this properly.
JhowieNitnek (talk) 14:58, 9 January 2026 (UTC)
Discussion
[edit]- I think we should wait until we have a datatype for that (see phab:T344618).--GZWDer (talk) 16:10, 9 January 2026 (UTC)
Strong oppose In my opinion, P373 is a shortcut that should have never existed, it exists only because some Wikipedia people just wanted a fast way for transcluding a Commons category into a Wikipedia page, regardless of the data model. P373 was meant to be a temporary fix, and since then, there are 5 proposals to delete it (and you can see them: the main reasons for not deleting it are just technical ones that should be addressed in the future, nothing to do with the data model). We must not repeat the same mistakes, and not create properties for "Wikimedia project page for this item": sitelinks are just for that. --Tinker Bell ★ ♥ 17:37, 9 January 2026 (UTC)ArthurPSmith (talk) 17:41, 9 January 2026 (UTC)
Oppose I hadn't realized the sitelink to wikifunctions existed - but given that it does, we should be using the sitelinks, not a property like this.- I have dropped my oppose comment as the discussion below does indicate the sitelink is not sufficient for this. ArthurPSmith (talk) 16:59, 4 February 2026 (UTC)
Oppose - Salgo60 (talk) 17:47, 12 January 2026 (UTC)
Comment We will need some way to link a single Item to multiple ZObjects. For example, sum (Q218005) corresponds to f:Z14038, f:Z20080, f:Z22579, etc. Maybe a sitelink to a dedicated page f:WF:Q218005 or category f:Category:Q218005? YoshiRulz (talk) 19:58, 13 January 2026 (UTC)
- @YoshiRulz: then Z14038 is not "sum" (sum (Q218005)) but "sum of elements of a list of natural numbers", so this proposal is not the relationship you are looking for. Maybe Q<Z14038>implements main functionsum (Q218005)
definition domain (P1568)Q<list-of-natural-numbers> , restricting for the main functions (although this is subjective)? The same for the other two examples. --Tinker Bell ★ ♥ 21:16, 13 January 2026 (UTC)- Are you suggesting that all such functions (those specialised to one WF datatype) get their own items on Wikidata? I think that might upset the WikiLambda developers...
- For reference, how functions should be linked to each other on Wikifunctions is still an open question, but it will likely include an "equivalent function(s) on other type(s):" list. YoshiRulz (talk) 11:22, 15 January 2026 (UTC)
- Not all WF functions would be WD-notable. Arlo Barnes (talk) 14:38, 16 January 2026 (UTC)
- Some more examples that wouldn't work as sitelinks:
- palindrome (Q12321)WF object for this itemf:Z10096
- palindrome (Q12321)WF object for this itemf:Z10553
- palindrome (Q12321)WF object for this itemf:Z21572
iteration (Q651022)WF object for this itemf:Z17958- iteration (Q651022)WF object for this itemf:Z26394
- fixed point (Q217608)WF object for this itemf:Z26394
- fixed point (Q217608)WF object for this itemf:Z12875
Open Location Code (Q23582265)WF object for this itemf:Z25963 YoshiRulz (talk) 10:03, 16 January 2026 (UTC)- Hmm, then it's not really an external identifier either; at least far from single-valued. How is it anticipated that these relationships will be used? ArthurPSmith (talk) 21:21, 16 January 2026 (UTC)
- (I was wondering why this is extID when Commons category (P373) is string.) I can only speak for myself, but I'm making no assumptions about future usage.
- For the Plus Code example, my thought process was that it "naturally follows" from reading the Wikipedia article, but the encoding algorithm itself is clearly not the subject of the article (or Item). Similarly for the fixed points example, none of those Functions embody the concept of 'fixed point', they're algorithms pertaining to it. YoshiRulz (talk) 21:54, 16 January 2026 (UTC)
- Another one: Template:0 (Q5409700) has f:Template:0 as the sitelink, so how can we link f:Z31205 which reimplements it? YoshiRulz (talk) 21:37, 20 January 2026 (UTC)
- Hmm, then it's not really an external identifier either; at least far from single-valued. How is it anticipated that these relationships will be used? ArthurPSmith (talk) 21:21, 16 January 2026 (UTC)
- @YoshiRulz: then Z14038 is not "sum" (sum (Q218005)) but "sum of elements of a list of natural numbers", so this proposal is not the relationship you are looking for. Maybe Q<Z14038>implements main functionsum (Q218005)
Oppose Rzuwig► 08:28, 4 February 2026 (UTC)
UMC rating
[edit]| Description | Age rating category as designated by the UAE Media Council (UMC) |
|---|---|
| Represents | UMC rating (Q130573492) |
| Data type | Item |
| Example 1 | UMC video game rating category (Q130569354)part ofUMC video game classification system (Q130569331) |
| Example 2 | subject→value |
| Example 3 | subject→value |
| See also | MPA film rating (P1657), USK rating (P914) |
| Wikidata project | Category:Pages using Wikidata property P1657 (Q126375150) |
Motivation
[edit](Add another rating system property. FireDragonValo) – The preceding unsigned comment was added by FireDragonValo (talk • contribs).
Discussion
[edit]
Oppose Please fill out the proposal @FireDragonValo:--Trade (talk) 23:48, 1 February 2025 (UTC)
Comment The example does not make sense - the example should be a subject (item where this property could be used - a video game), the proposed property, and the target value for the property. Please include at least 3 examples with existing Wikidata items in the proposal. ArthurPSmith (talk) 00:20, 16 January 2026 (UTC)
Oppose, even if this proposal is filled out, since the proposer has a long-standing practice of not providing references for ratings (example). If we create this property, this abusive practice will continue. @FireDragonValo: When you understand why each of these properties (see 1, 2, 3, 4, 5, 6, 7) has a citation-needed constraint (Q54554025) and when you start providing sources, you can re-propose this property, but for now sorry, no thanks. Regards Kirilloparma (talk) 02:05, 27 January 2026 (UTC)
Wikidata:Property proposal/Gmedia rating
incompatible type
[edit]| Description | instances of this type or of its subclasses cannot be simultaneously instances of that type nor of its subclasses, subclasses of this type cannot be simultaneously subclasses of that type |
|---|---|
| Data type | Item |
| Domain | item |
| Example 1 | audio track (Q7302866) → song (Q7366) |
| Example 2 | release group (Q108346082) → audio track (Q7302866) |
| Example 3 | organization (Q43229) → human (Q5) |
| Planned use | constraint on types |
| See also | disjoint union of (P2738), property proposal/instances must not have, property constraint (P2302)conflicts-with constraint (Q21502838) |
| Wikidata project | WikiProject Property constraints (Q56162322), WikiProject Ontology (Q60005226) |
Motivation
[edit]This can replace some ad hoc negative domain constraints on individual properties. For example, the domain of MetroLyrics ID (P2624) includes audio track (Q7302866) and explicitly excludes song (Q7366):
- MetroLyrics ID (P2624)property constraint (P2302)conflicts-with constraint (Q21502838)
property (P2306)instance of (P31) item of property constraint (P2305)song (Q7366)
However, this negative constraint is not specific to MetroLyrics ID (P2624). It is just a consequence of mutual incompatibility of the mentioned types. It can be expressed independently from the property as statement
- audio track (Q7302866)incompatible typesong (Q7366). — Petr Matas 05:39, 19 January 2026 (UTC)
Addition: Property proposal/instances must not have is a generalization of this property. It cannot replace it completely however, because the statement instances must not haveinstance of (P31)
Discussion
[edit]
Comment @Petr Matas: This seems similar to what was intended with disjoint union of (P2738) which I think came out of the logic of the OWL ontology system. The difference is that requires an encompassing class which covers the types being distinguished. I don't think it's been used much here though, and the approach proposed here may be a little easier to understand (though it has combinatorial issues if there are many different types we want to distinguish as exclusive of one another). ArthurPSmith (talk) 20:22, 20 January 2026 (UTC)
- Thanks for pointing this out. The encompassing class for disjoint union of (P2738) requires the mutually exclusive types to be its direct subclasses. In contrast, my proposal is intended for unrelated types. I don't expect the sets of mutually incompatible types to be large in this case. — Petr Matas 04:41, 21 January 2026 (UTC)
Notified participants of WikiProject property constraints. Message left on the talk page of WikiProject Ontology. — Petr Matas 04:32, 26 January 2026 (UTC)
Comment The name of the current proposal is somewhat similar to others that have been previously proposed, see Wikidata:Property proposal/incompatible with and Wikidata:Property proposal/not compatible with. If this case involves property constraints, then the name should be changed to at least "incompatible type constraint" or something similar. Regards Kirilloparma (talk) 03:11, 27 January 2026 (UTC)
- The previous proposals concern compatibility of technologies, whereas this proposal concerns compatibility of classes upon instantiation using instance of (P31). It is not a property constraint however, because it does not apply to properties, but to the classes/types (i.e. items). WikiProject property constraints is mentioned just because I am not aware of another project concerning constraints. Your proposed name incompatible type constraint seems sensible to me, but I am afraid of confusion with actual property constraints. — Petr Matas 04:10, 27 January 2026 (UTC)
- How about incompatible class or disjoint class? — Petr Matas 08:09, 27 January 2026 (UTC) (Updated)
- Ah, I overlooked that. In that case, I have no particular objections to the current name or the alternatives suggested above. Regards Kirilloparma (talk) 01:38, 28 January 2026 (UTC)
Question This can replace some ad hoc negative domain constraints on individual properties. So you imagine this being respected by the constraint system? Did you ask developers (e.g. on Wikidata:Report a technical problem) how feasible this is? The property may make sense even if the software cannot respect it (it makes users or bots aware, who can copy it to the properties), but far less convenient. —Tacsipacsi (talk) 08:05, 29 January 2026 (UTC)
- Exactly. I did not ask the developers yet, because I believe that first we should discuss the need here and make the request to the developers if we get a positive result. The feasibility can be an important input to this discussion though.
Can you suggest where I should ask?— Petr Matas 10:09, 29 January 2026 (UTC) - Request to developers filed. — Petr Matas 13:44, 30 January 2026 (UTC)
- Exactly. I did not ask the developers yet, because I believe that first we should discuss the need here and make the request to the developers if we get a positive result. The feasibility can be an important input to this discussion though.
Comment The description and motivation has been expanded. — Petr Matas 10:09, 29 January 2026 (UTC)- Edited description: In addition to instances, the constraint should also apply to subclasses of the two types. It is because if a type is a subclass of two mutually incompatible types, then also every its instance will be an instance of two incompatible types and thus it will violate the original constraint.
TC Infos network identifier
[edit]| Description | TC Infos transport network |
|---|---|
| Data type | External identifier |
| Example 1 | Cergy-Pontoise Confluence bus network (Q125467072) → 472 |
| Example 2 | Bus RATP (Q474674) → 45 |
| Example 3 | Transports en commun lyonnais (Q8700) → 897 |
| Formatter URL | https://tc-infos.fr/reseau/$1 |
| Single-value constraint | yes |
Motivation
[edit]This identifier seems interessant because it contains lines informations, materials with number and dates which might be usefull. – The preceding unsigned comment was added by Tasye24 (talk • contribs) at 10:28, January 25, 2026 (UTC).
Discussion
[edit]Hentaigana for Academic Information Exchange ID
[edit]| Description | Chinese character glyph identifier issued by Moji Joho Kiban Project |
|---|---|
| Represents | no label (Q137908265) |
| Issued by | National Institute for Japanese Language and Linguistics (Q4853049) |
| Data type | External identifier |
| Domain | item, hentaigana (Q607460) |
| Example 1 | 𛀂 (Q87565869)→010010010 |
| Example 2 | 𛀆 (Q87565878)→020010010 |
| Example 3 | 𛄜 (Q87566540)→470050020 |
| Allowed values | [0-9]{9} |
| Source | https://cid.ninjal.ac.jp/kana/ |
| Number of IDs in source | 293 |
| Expected completeness | eventually complete (Q21873974) |
| Implied notability | Wikidata property for an identifier that suggests notability (Q62589316) |
| Formatter URL | https://cid.ninjal.ac.jp/kana/detail/$1/ |
| Country | Japan (Q17) |
| Applicable "stated in"-value | no label (Q137908265) |
| Single-value constraint | yes |
| Distinct-values constraint | yes |
Motivation
[edit]This is identifer of hentaigana (Q607460) given by National Institute for Japanese Language and Linguistics (Q4853049). It gives hentaigana (Q607460) useful informations. – The preceding unsigned comment was added by TAKA647 (talk • contribs) at 07:56, January 27, 2026 (UTC).
Discussion
[edit]Identifiant inventaire Nouvelle-Aquitaine (fr) – (Please translate this into English.)
[edit]| Description | identifiant de l'inventaire du patrimoine de la région nouvelle-Aquitaine (fr) – (Please translate this into English.) |
|---|---|
| Data type | External identifier |
| Domain | être humain(5) |
| Example 1 | église Saint-Pierre d'Oeyreluy(Q22920439) → 4326db2f-7c10-4c54-aa5e-14b24250140c |
| Example 2 | citadelle de Blaye(Q2974390) → 4a53587e-dc3c-4c91-ba36-3036b78364d6 |
| Example 3 | grotte de Lascaux(Q172125) → 3b4c93e9-9c30-436a-901a-82f140a37f67 |
| Formatter URL | https://www.patrimoine-nouvelle-aquitaine.fr/default/doc/Dossier/$1 |
Motivation
[edit]
Notified participants of WikiProject France
BAse de donnée très utile et fiable pour les objets mobiliers et immobiliers de Nouvelle-Aquitaine. --Uchroniste 40 (talk) 18:59, 27 January 2026 (UTC)
Discussion
[edit]
Support, même si on continue de regretter l'absence d'initiative d'ensemble au niveau national dans ce domaine. Maxime 19:13, 27 January 2026 (UTC)
Oppose @Uchroniste 40, Maxime Ravel: English:it already exists as Nouvelle-Aquitaine Inventory ID (P11133), it seems they have changed the interface and they now hide the true identifier behind an UUID tho (which makes it painful to find, to see eventually to adapt the existing property?). And it exists for each and every French region, as well at the national level on Mérimée.Français :Cela existe déjà Nouvelle-Aquitaine Inventory ID (P11133), il semble qu'ils ont changé l'interface, ceci dit ils cachent le vrai identifiant derrière un UUID (ce qui le rend difficile à trouver, à voir pour adapter éventuellement la propriété existante ?). Et cela existe pour toutes les régions françaises et aussi au niveau national dans Mérimée. Pour info, @Ayack, Kolja21, Arpyia, Fralambert:. Cheers/Cdlt, VIGNERON (talk) 19:47, 27 January 2026 (UTC)
Oppose. I agree with @VIGNERON. The property already exists, and it is preferable to use the actual identifier (IAxxxxxxxx) rather than the one generated on the site. In the absence of a better option, we have to rely on the search urls. — Baidax 💬 11:22, 28 January 2026 (UTC)
GiveSendGo fundraising ID
[edit]| Description | identifier for this person, event or project on the GiveSendGo fundraising platform |
|---|---|
| Data type | External identifier |
| Domain | human (Q5) |
| Example 1 | Luigi Mangione (Q131411648)GiveSendGo fundraising IDluigi-defense-fund |
| Example 2 | Charlie Kirk (Q30121972)GiveSendGo fundraising IDinlovingmemoryofcharlie |
| Example 3 | Shiloh Hendrix (Q134377663)GiveSendGo fundraising IDShilohHendrix |
| Example 4 | Daniel Penny (Q118177833)GiveSendGo fundraising IDdaniel_penny |
| Source | https://www.givesendgo.com/campaigns |
| Number of IDs in source | Unknown |
| Implied notability | Wikidata property for an identifier that does not imply notability (Q62589320) |
| Formatter URL | https://www.gofundme.com/f/$1 |
| Applicable "stated in"-value | GiveSendGo (Q110938034) |
| Single-value constraint | yes |
| Distinct-values constraint | yes |
Motivation
[edit]GiveSendGo is the most popular crowdfunding site for campaigns that would otherwise violate GoFundMe's ToS regarding legal funds for people convicted of violent crimes. Some campaigns like the one for Mangione have received a substantial amount of media coverage and it would be a loss for WIkidata if we could not link it here.--Trade (talk) 02:03, 28 January 2026 (UTC)
Discussion
[edit]@Prototyperspective, Wd-Ryan:--Trade (talk) 02:03, 28 January 2026 (UTC)
CrowdRepublic project ID
[edit]| Description | identifier for a project on the CrowdRepulic platform |
|---|---|
| Represents | CrowdRepublic (Q125560330) |
| Data type | External identifier |
| Domain | CrowdRepublic (Q125560330) |
| Example 1 | Cryptic Nature (Q137916981) → 1072890 |
| Example 2 | The Thing: The Boardgame (Q124480481) → 1044575 |
| Example 3 | Black Book: The Board Game (Q133798414) → 1067397 |
| Allowed values | [0-9]+ |
| Expected completeness | always incomplete (Q21873886) |
| Formatter URL | https://crowdrepublic.ru/projects/$1 |
| See also | Kickstarter project ID (P8019) |
| Proposed by | CupIvan |
Motivation
[edit]The russian crowfunding platform with popular boardgame projects. A identifier would be useful to have. – The preceding unsigned comment was added by CupIvan (talk • contribs) at 07:41, January 28, 2026 (UTC).
Notified participants of WikiProject Board Games
Discussion
[edit]instances must not have
[edit]| Description | instances of this class or of its subclasses must not have given property or statement |
|---|---|
| Data type | Property |
| Domain | item |
| Example 1 | audio track (Q7302866)instances must not haveinstance of (P31) |
| Example 2 | audiovisual work (Q2431196)instances must not havecountry (P17) |
| Example 3 | help me ☺ |
| Planned use | type constraint, generalization of property proposal/incompatible type |
| See also | properties for this type (P1963) a.k.a. "instances may have", property proposal/incompatible type, conflicts-with constraint (Q21502838) |
| Wikidata project | WikiProject Property constraints (Q56162322), WikiProject Ontology (Q60005226) |
Motivation
[edit]This proposal is a generalization of property proposal/incompatible type. Both aim to replace property constraints, which naturally belong to the domain of the property.
For example, constraints on country (P17) are a mess. Constraints like
- country (P17)property constraint (P2302)conflicts-with constraint (Q21502838)
property (P2306)instance of (P31) item of property constraint (P2305)film (Q11424) replacement property (P6824)country of origin (P495)
should be replaced with
- audiovisual work (Q2431196)instances must not havecountry (P17)
replacement property (P6824)country of origin (P495) .
Note that unlike the property constraint, the new statement needs to be added only to audiovisual work (Q2431196) and not to its subclasses like film (Q11424), because it applies to them automatically.
Discussion
[edit]
Notified participants of WikiProject property constraints. Message left on the talk page of WikiProject Ontology. — Petr Matas 10:49, 29 January 2026 (UTC)
radeberger-stadtgeschichte.de Object Identificator
[edit]| Description | radeberger-stadtgeschichte.de Object |
|---|---|
| Data type | External identifier |
| Example 1 | Stadtkirche Zum Heiligen Namen Gottes Radeberg (Q55736367) → anki004 |
| Example 2 | Q49147210 → freu001 |
| Example 3 | Klippenstein Castle (Q2241888) → schs006 |
| Allowed values | [a-z0-9]+ |
| Planned use | yes |
| Number of IDs in source | >2000 |
| Single-value constraint | yes |
| Distinct-values constraint | yes |
Motivation
[edit]For the town Radeberg (Q81729) in Saxony, Germany exits a very good website with a citymap https://radeberger-stadtgeschichte.de/stadtplan . There you get for nearly every building in this city the history. This website is a clone of https://www.altesdresden.de. There we have property altesdresden.de object ID (P11855). Now we want to add to every Rabeberg-Object in Wikidata also a similarly property, so that we can connect this cool website. --sk (talk) 11:41, 5 February 2026 (UTC)
Discussion
[edit]
Support - local ID for historic content. Conny (talk) 13:41, 5 February 2026 (UTC).
Support --Printstream (talk) 18:31, 5 February 2026 (UTC)
Support Jeb (talk) 12:17, 6 February 2026 (UTC)
Support super project by Dr. Rohland Q109550735, Jörg and Stefan --Erfurth (talk) 20:39, 9 February 2026 (UTC)
Master Ideographs Seeker Character ID
[edit]| Description | Character ID of Master Ideographs Seeker for CNS 11643 Chinese Standard Interchange Code in URL |
|---|---|
| Represents | Master Ideographs Seeker (Q136643781) |
| Issued by | Ministry of Digital Affairs (Q109260060) |
| Data type | External identifier |
| Domain | item, Unicode character (Q29654788) |
| Example 1 | 寧 (Q55408483)→92239 |
| Example 2 | 寧 (U+2F86F) (Q87585928)→416802 |
| Example 3 | A (Q87496158)→532802 |
| Example 4 | 椬 (Q109750474)→222510,998250 |
| Example 5 | 𫇥 (Q109899715)→739414,1188129 |
| Allowed values | \d{5,7} |
| Source | https://www.cns11643.gov.tw/ |
| Number of IDs in source | 114,537 |
| Expected completeness | eventually complete (Q21873974) |
| Implied notability | Wikidata property for an identifier that suggests notability (Q62589316) |
| Formatter URL | https://www.cns11643.gov.tw/wordView.jsp?ID=$1 |
| Country | Taiwan (Q865) |
| Applicable "stated in"-value | Master Ideographs Seeker (Q136643781) |
| Distinct-values constraint | yes |
Motivation
[edit]This property shows character ID in Master Ideographs Seeker (Q136643781). I think the best way is using CNS 11643 (Q573121) code such as 1-684F, but I don't know how to do it.--TAKA647 (talk) 13:25, 5 February 2026 (UTC)
Discussion
[edit]Kotobank Japanese ID
[edit]| Description | The identifier in the Japanese article URL on Kotobank |
|---|---|
| Represents | Kotobank (Q11302260) |
| Data type | External identifier |
| Domain | item, lexeme |
| Example 1 | Japan (Q17)→109930,3212087 |
| Example 2 | 日本/にほん (L5108)→109930 |
| Example 3 | Iah (Q946657)→23561 |
| Example 4 | 絵 (Q54552713)→442803 |
| Example 5 | JUNGLIA OKINAWA (Q133878783)→3242580 |
| Example 6 | Digitalis purpurea (Q157555)→3155343,3148923,474830 |
| Allowed values | \d{5,7} |
| Source | https://kotobank.jp |
| Expected completeness | eventually complete (Q21873974) |
| Implied notability | Wikidata property for an identifier that suggests notability (Q62589316) |
| Formatter URL | https://kotobank.jp/word/ID-$1 |
| Country | Japan (Q17) |
| Applicable "stated in"-value | Kotobank (Q11302260) |
Motivation
[edit]Kotobank (Q11302260) is an integrated online Japanese dictionary/encyclopedia. It features many dictionaries/encyclopedias as listed. It's very known and widely used as usage on Japanese Wikipedia. Also it's very often shown in the top of the Google search results. See also Wikidata:Property proposal/Kotobank ID--TAKA647 (talk) 09:40, 8 February 2026 (UTC)
Discussion
[edit]
Comment @TAKA647: What do you make of the concern raised by Midleading (and the reply to that concern by Laftp0) in the previous proposal for this property? Mahir256 (talk) 16:11, 8 February 2026 (UTC)
- Kotobank mixes dictionaries and encyclopedias on the same page, so it can't limit the scope to just lexemes or just items. I believe this property gives useful information in Japanese. TAKA647 (talk) 05:29, 9 February 2026 (UTC)
Oppose external ids for items should not be mixed with those for lexemes and it seems as if its not meant for lexemes. 109930 shows two different lexemes (にほん【日本】and にっぽん【日本】). Ic you merged them in wikidata? 😔 –Shisma (talk) 19:09, 9 February 2026 (UTC)
- I can't understand a disadvantages to use the property for items and lexemes (see also Lur Encyclopedic Dictionary ID (P10242)). にほん【日本】and にっぽん【日本】share the same origin, and there is no difference in meaning between them. So they are just different forms. TAKA647 (talk) 03:05, 10 February 2026 (UTC)
- okay, the 日本 example is debatable. Here's a different one 143996 refers to both 山/やま (L5121) and 山/さん (L1313770). As far as I understand they aren't related. This could actually be solved by changing the proposal slightly (include a hash):
- I am not familiar with Lur Encyclopedic Dictionary ID (P10242). Is there a way to distinguish which kotoba articles are clearly lexicographical, and which aren't? –Shisma (talk) 18:49, 10 February 2026 (UTC)
- The reason that I don't use "#w-" is proper noun item needs a lot of identifier such as:
- However, I think using "#w-" is one way to go. About 山, 143996#w-512769 is about just character, not suffix. So correct linc is this:
- If the word isn't proper noun, the way to judge it is better for item or for lexeme is sourse book. Using identifier shared with (P4070) and identifier shared with lexeme (P9531) might be a good idea. TAKA647 (talk) 07:54, 11 February 2026 (UTC)
- I'd refrain from using identifier shared with lexeme (P9531) when it can be avoided. If you update the proposal to include the hash for homograph lexemes I would remove my oppose vote. If only we could solve the issue of this being mixed item/lexeme property. My initial concern was, that a particular software expects an id-property either be for lexemes or items but maybe that is an issue of this software rather than this proposal. Maybe it makes writing constraints more complicated? I wonder what @Laftp0: concerns were when withdrawing their proposal? – Shisma (talk) 16:36, 14 February 2026 (UTC)
- I can't understand a disadvantages to use the property for items and lexemes (see also Lur Encyclopedic Dictionary ID (P10242)). にほん【日本】and にっぽん【日本】share the same origin, and there is no difference in meaning between them. So they are just different forms. TAKA647 (talk) 03:05, 10 February 2026 (UTC)
Bolivian INE Unique Code
[edit]| Description | Official hierarchical identifier of the National Institute of Statistics of Bolivia for administrative entities such as departments, provinces and municipalities. |
|---|---|
| Data type | External identifier |
| Example 1 | 02 Departamento de La Paz |
| Example 2 | 0201 Provincia Murillo |
| Example 3 | 020101 Municipio de Nuestra Señora de La Paz |
Motivation
[edit]Facilitar la interoperabilidad y enlazado de datos estadísticos y administrativos de Bolivia con otras fuentes y sistemas, preservando la codificación oficial. – The preceding unsigned comment was added by Lizondo chirinos andres (talk • contribs) at 16:54, August 13, 2025 (UTC).
Detalles
[edit]Identificador jerárquico oficial del Instituto Nacional de Estadística de Bolivia para entidades administrativas como departamentos, provincias y municipios.
Tipo de valor: cadena de texto (string)
Formato:
- Departamento:
DD(2 dígitos) - Provincia:
DDPP(4 dígitos) - Municipio:
DDPPMM(6 dígitos) - Los ceros a la izquierda son significativos. Dominio (se aplica a):
- Entidad territorial de segundo nivel de Bolivia https://es.wikipedia.org/wiki/Departamentos_de_Bolivia
- Entidad territorial de tercer nivel de Bolivia https://es.wikipedia.org/wiki/Anexo:Municipios_de_Bolivia
- Departamento de Bolivia Ejemplos:
- Departamento de La Paz →
02 - Provincia Murillo →
0201 - Municipio de Nuestra Señora de La Paz →
020101Fuente oficial: Instituto Nacional de Estadística de Bolivia - División político-administrativa https://anda.ine.gob.bo/index.php/catalog/71/ https://fichacomunidad.ine.gob.bo/
Discussion
[edit]Si bien esta será muy util para compartir datos y relacionar datos nacionales de bolivia con otras fuentes usando wikidata de por medio, siendo que este identificador evoluciona con los municipios del pais, añadiendose más o detallando las comunidades dentro de cada uno
Support Si es del instituto nacional de estadística es un dato oficial, que estaría muy bien tener a disposición en Wikidata. Hiperterminal (talk) 11:42, 19 August 2025 (UTC)
Comment Why isn’t this an external identifier? —Tacsipacsi (talk) 08:44, 23 August 2025 (UTC)
Support This is a basic identifier that persists across time. Several Bolivian municipalities have non-unique names, and a handful have two alternate names. Unique identifiers make aligning data much easier. / Este es un identificador único básico que persiste a lo largo del tiempo. Varios municipios bolivianos tienen nombres no únicos, y unos pocos tienen dos nombres alternativos. Los identificadores únicos facilitan enormemente la alineación de datos. -- Carwil (talk) 03:15, 10 February 2026 (UTC)- @Lizondo chirinos andres, Hiperterminal, Tacsipacsi, Carwil: I have modified the datatype. Can somebody please fix the examples so that they follow our standard example format (wikidata item, then id value). Also the proposal could be filled out more completely. Thanks. ArthurPSmith (talk) 18:15, 10 February 2026 (UTC)
- Me imagino que el ejemplo que piden es algo como ésto: "| example 1 = {{Statement|Q272784|→|[02]}}", pero no puedo encontrar un enlace persistente a "Departamento de La Paz". Hiperterminal (talk) 23:02, 10 February 2026 (UTC)
Number of translations
[edit]| Description | Number of translations |
|---|---|
| Data type | Quantity |
| Example 1 | The Little Prince (Q25338)→610. |
| Example 2 | Minecraft (Q49740)→ca. 100. |
| Example 3 | The Adventures of Pinocchio (Q8065468)→ca 240. |
Motivation
[edit]Number of translations of a book, game etc.
Discussion
[edit]Panoramax instance URL
[edit]| Description | the Panoramax instance of/about the subject |
|---|---|
| Represents | Panoramax instance (Q138297906) |
| Data type | URL |
| Domain | item |
| Example 1 | Institut national de l'information géographique et forestière (Q1665102)→https://panoramax.ign.fr/ |
| Example 2 | OpenStreetMap France (Q26996641)→https://panoramax.openstreetmap.fr/ |
| Example 3 | MapComplete (Q135440522)→https://panoramax.mapcomplete.org/ |
| Source | https://panoramax.fr/ |
| Expected completeness | always incomplete (Q21873886) |
Motivation
[edit]Panoramax is a collaborative database of street-level imagery, designed to be federated. Multiple instances have popped out, with 8 being listed currently on their website, and the number is set to grow. I have based this proposal mirroring Wikidata:Property proposal/Mastodon instance URL. Robot8A (talk) 10:21, 14 February 2026 (UTC)
Discussion
[edit]
Support --Waldyrious (talk) 08:01, 15 February 2026 (UTC)
Wait A property should should have at least 100 possible values; 8 is far too low. Dexxor (talk) 11:43, 15 February 2026 (UTC)
Fragplace brands ID
[edit]Motivation
[edit]Fragplace (Q138304188) is a free online perfume database with information about tens of thousands of perfumes, perfume brands, and perfume notes. From a brand's page in the website, users can view all of the perfumes from that brand or can limit their search by perfume notes, perfumer, and year of release. AdamSeattle (talk) 05:46, 15 February 2026 (UTC)
Discussion
[edit]Fragplace fragrances ID
[edit]Motivation
[edit]Fragplace (Q138304188) is a free online perfume database with information about tens of thousands of perfumes, perfume brands, and perfume notes. Perfume listings include information about the brand, year of release, notes, longevity, sillage, gender, season for wearing, perfumer, and similar fragrances. AdamSeattle (talk) 06:09, 15 February 2026 (UTC)
Discussion
[edit]Fragplace notes ID
[edit]Motivation
[edit]Fragplace (Q138304188) is a free online perfume website and database with information about perfumes, perfume brands, and perfume notes. Notes pages include a description of the note and listings of perfumes that include that note. Users can also limit their searches by combining a note with other notes, brands, perfumers, and release dates. AdamSeattle (talk) 06:45, 15 February 2026 (UTC)
Discussion
[edit]News website tag
[edit]Les Inrockuptibles subject tag
[edit]| Description | tag identifying a subject on the site Les Inrockuptibles |
|---|---|
| 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
[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)
Oppose Not very effective as a tag (not id) : this is without Trump tag. Why ? —Eihel (talk) 11:26, 29 January 2025 (UTC)
- wdym? Trade (talk) 04:20, 5 February 2025 (UTC)
Support --Tinker Bell ★ ♥ 17:29, 3 October 2025 (UTC)
RFI topic ID
[edit]Motivation
[edit]
Notified participants of WikiProject France: I propose to create a new property for topics on the RFI (Q30097346) (https://www.rfi.fr/). --Soufiyouns (talk) 07:29, 2 February 2025 (UTC)
Discussion
[edit]
Support. Maxime 08:18, 2 February 2025 (UTC)
Comment separate properties per language would be better, unless these items only appear in one language (which I doubt). ArthurPSmith (talk) 20:25, 3 February 2025 (UTC)
- If you change the language of the entries you can see that not all tags are available in all languages nor does all languages contain the same articles or amount of articles Trade (talk) 15:10, 18 February 2025 (UTC)
- @ArthurPSmith: We have the choice between an integrated design and an expanded one. If we opt for a single identifier for RFI (Q30097346) supporting about 17 languages, we have the model of Vikidia article ID (P12800) with 2 parameters and the model of Fandom article ID (P6262) with 3 parameters. If on the other hand we lean towards the distributed choice, we have the model of the 4 multilingual identifiers of France 24 (Q166180): France 24 topic ID (French) (P9346), France 24 topic ID (English) (P9347), France 24 topic ID (Spanish) (P9348), France 24 topic ID (Arabic) (P9349). Regards. --Soufiyouns (talk) 06:43, 4 February 2025 (UTC)
Support --Trade (talk) 15:10, 18 February 2025 (UTC)
Comment Please just use the last portion of the URL as the id so we can use https://www.rfi.fr/$1 as the formatter URL. This only adds the three letters ("tag") to the ID's and replaces the ':' with '/' characters - i.e. 'fr/tag/ségolène-royal' instead of 'fr:ségolène-royal'. ArthurPSmith (talk) 21:08, 5 May 2025 (UTC)
Conditional support Without language prefix. We can add other formatters with qualifiers to specify language. -wd-Ryan (Talk/Edits) 23:18, 2 September 2025 (UTC)
- I changed it Trade (talk) 00:11, 4 September 2025 (UTC)
Algeria Press Service topic ID
[edit]Motivation
[edit]
Notified participants of WikiProject Algeria: I propose to create a new property for the tags on the website of the news agency Algeria Press Service (Q1162323) (https://www.aps.dz/). --Soufiyouns (talk) 07:58, 2 February 2025 (UTC)
Discussion
[edit]- I'm unfamiliar with APS. Is it anything like the Associated Press in the U. S.? Eric Schucht (talk) 12:51, 3 February 2025 (UTC)
- @Eric Schucht: Algeria Press Service (Q1162323) is a government news agency in Algeria, and it publishes articles in several languages (Arabic, English, French, etc.). Soufiyouns (talk) 13:06, 3 February 2025 (UTC)
- Gotcha. Well, if it's a big deal, then it should have it's own tag like you propose. Eric Schucht (talk) 13:09, 3 February 2025 (UTC)
- @Eric Schucht: Now, we have to implement this property the choice between an integrated design and an expanded one. If we opt for a single identifier for Algeria Press Service (Q1162323) supporting about 8 languages, we have the model of Fandom article ID (P6262) with 3 parameters. If on the other hand we lean towards the distributed choice, we have the model of the 4 multilingual identifiers of France 24 (Q166180): France 24 topic ID (French) (P9346), France 24 topic ID (English) (P9347), France 24 topic ID (Spanish) (P9348), France 24 topic ID (Arabic) (P9349). Regards. --Soufiyouns (talk) 17:03, 5 February 2025 (UTC)
- Gotcha. Well, if it's a big deal, then it should have it's own tag like you propose. Eric Schucht (talk) 13:09, 3 February 2025 (UTC)
- @Eric Schucht: Algeria Press Service (Q1162323) is a government news agency in Algeria, and it publishes articles in several languages (Arabic, English, French, etc.). Soufiyouns (talk) 13:06, 3 February 2025 (UTC)
Support --Trade (talk) 15:08, 18 February 2025 (UTC)
Comment Wikidata currently does not support $2, $3 and $4 in URL formatter. Midleading (talk) 04:05, 27 March 2025 (UTC)
Comment Please just use the portion of the URL after https://www.aps.dz/ as the ID; this only adds the word "tag" so not greatly increasing the length of the ids, and it allows the simple formatter URL https://www.aps.dz/$1. ArthurPSmith (talk) 02:38, 4 May 2025 (UTC)
Comment: The current formatter URL is no longer operational (example). Regards Kirilloparma (talk) 04:56, 28 December 2025 (UTC)
Breitbart News tag ID
[edit]| Description | identifier for a topic on Breibart News' website |
|---|---|
| Represents | Breitbart News (Q4960434) |
| Data type | External identifier |
| Example 1 | Donald Trump (Q22686)→donald-trump |
| Example 2 | video game (Q7889)→video-games |
| Example 3 | Wikipedia (Q52)→wikipedia |
| Example 4 | Bitcoin (Q131723)→bitcoin |
| Source | https://www.google.com/search?q=site%3Ahttps%3A%2F%2Fwww.breitbart.com%2Ftag |
| External links | Use in sister projects: [ar] • [az] • [bn] • [de] • [en] • [es] • [fa] • [fr] • [he] • [hi] • [it] • [ja] • [ka] • [kn] • [ko] • [ml] • [mr] • [nl] • [pl] • [pt] • [ro] • [ru] • [sv] • [te] • [tr] • [ur] • [vi] • [zh] • [commons] • [species] • [wd] • [en.wikt] • [fr.wikt]. |
| Number of IDs in source | Unknown |
| Expected completeness | eventually complete (Q21873974) |
| Formatter URL | https://www.breitbart.com/tag/$1/ |
| Applicable "stated in"-value | Breitbart News (Q4960434) |
| Single-value constraint | yes |
| Distinct-values constraint | yes |
Motivation
[edit]Breitbart News is one of the most well-known news websites in the United States (if not the English-speaking world) so it will fit well on Wikidata along with all the other news website tag identifiers
I'm just gonna point it out before anyone else. Having this identifier does not mean that either i or Wikidata endorses the website or it's content or opinions – The preceding unsigned comment was added by Trade (talk • contribs) at 16:06, February 18, 2025 (UTC).
Discussion
[edit]
Oppose Just because it's a frequented website doesn't make it useful to interconnect it here. Not useful. --Prototyperspective (talk) 17:22, 18 February 2025 (UTC)
Support. Unfortunately a valid Wikidata property to identify news website topics (Q105946994) just like any other. Necessary for a balanced coverage of news website topics. --Lewis Hulbert (talk) 04:26, 19 February 2025 (UTC)
- Whether or not it's necessary kind of depends on how the properties to identify news website topics are being used. If they are actually used in some way where adding this one would be useful, e.g. similar to Ground News then adding this one may make sense and I may revoke my opposition / a new proposal could be made. Prototyperspective (talk) 16:06, 19 February 2025 (UTC)
Support: While this news website has obvious problems, it is still an influential news website. Susmuffin (talk) 09:35, 28 June 2025 (UTC)
Support Looks good to me. -wd-Ryan (Talk/Edits) 23:22, 2 September 2025 (UTC)
Oppose Quoting enwiki: Its content has been described as misogynistic, xenophobic, and racist by various academics and journalists. The site has published a number of conspiracy theories and intentionally misleading stories, as well as having promoted climate change denial and COVID-19 misinformation. Trivialist (talk) 03:03, 1 November 2025 (UTC)
Oppose per above, and also don't think it brings any additional value here. Germartin1 (talk) 04:27, 9 January 2026 (UTC)
Oppose I don't think linking to targeted misinformation, from either side of the political spectrum, has any benefit in the name of impartiality. The website is spam filtered in enwiki for a reason. Jotamide (talk) 21:01, 27 January 2026 (UTC)
Delfi.lv theme ID
[edit]| Description | identifier of a theme in the Delfi.lv database |
|---|---|
| Data type | External identifier |
| Example 1 | Novak Djokovic (Q5812) → 35402640 |
| Example 2 | Baltic Basketball League (Q805695) → 35400606 |
| Example 3 | Latvijas Basketbola līga (Q1640536) → 35417134 |
| Allowed values | [1-9][0-9]+ |
| Source | https://www.delfi.lv/ |
| Planned use | add to mix'n'match |
| Number of IDs in source | 10,901 (at least) |
| Expected completeness | always incomplete (Q21873886) |
| Formatter URL | https://www.delfi.lv/temas/$1 |
| See also | Postimees topic ID (P9937), ERR keyword ID (P13295), Delfi.ee topic ID (P13403) |
| Applicable "stated in"-value | Delfi (Q1184119) |
Motivation
[edit]This is a natural follow-up to the proposal for Delfi.ee topic ID (P13403), with respect to the Latvian version of that site. Mahir256 (talk) 19:21, 14 May 2025 (UTC)
Discussion
[edit]- Looks like there are separate topic IDs for Latvian and Russian versions, e.g. https://www.delfi.lv/temas/35525519/krievija and https://rus.delfi.lv/temi/49798467/rossiya for Russia (Q159). So maybe it also makes sense to have another property for Russian version. —putnik 19:56, 1 June 2025 (UTC)
- @Putnik: That's an interesting idea; the Wayback Machine has captures for 6,014 IDs in the Russian version. Mahir256 (talk) 21:00, 2 June 2025 (UTC)
Support --Trade (talk) 15:13, 15 February 2026 (UTC)
Autostraddle tag ID
[edit]| Description | identifier of a tag at the website of the Autostraddle magazine |
|---|---|
| Represents | Autostraddle (Q4827011) |
| Data type | External identifier |
| Domain | entity (Q35120) |
| Example 1 | reproductive health (Q1981388)→reproductive-health |
| Example 2 | Hunter Schafer (Q59248250)→hunter-schafer |
| Example 3 | Stardew Valley (Q23013817)→stardew-valley |
| Source | https://www.autostraddle.com |
| External links | Use in sister projects: [ar] • [az] • [bn] • [de] • [en] • [es] • [fa] • [fr] • [he] • [hi] • [it] • [ja] • [ka] • [kn] • [ko] • [ml] • [mr] • [nl] • [pl] • [pt] • [ro] • [ru] • [sv] • [te] • [tr] • [ur] • [vi] • [zh] • [commons] • [species] • [wd] • [en.wikt] • [fr.wikt]. |
| Mix'n'match | 7267 (Autostraddle topic) |
| Number of IDs in source | 2737 |
| Expected completeness | always incomplete (Q21873886) |
| Implied notability | Wikidata property for an identifier that does not imply notability (Q62589320) |
| Formatter URL | https://www.autostraddle.com/tag/$1/ |
| Applicable "stated in"-value | Autostraddle (Q4827011) |
| Single-value constraint | yes |
| Distinct-values constraint | yes |
Motivation
[edit]--Trade (talk) 17:05, 24 August 2025 (UTC)
Weak support Seems like a niche website but proposal looks good. -wd-Ryan (Talk/Edits) 23:24, 2 September 2025 (UTC)
Discussion
[edit]
Oppose The website seems minor and it's not clear to me what Wikidata gains by adding the tag. No reasoning is provided for why creating the tag would be a good idea. On the other hand the costs of adding a tag are clear. They make items bigger and thus increase load time and also take up user time by showing up on watchlists. ChristianKl ❪✉❫ 08:14, 23 September 2025 (UTC)
LGBTQ Nation tag ID
[edit]| Description | identifier of a tag in the LGBTQ Nation online magazine |
|---|---|
| Represents | LGBTQ Nation (Q85775305) |
| Data type | External identifier |
| Domain | entity (Q35120) |
| Example 1 | Zohran Mamdani (Q28034971)→zohran-mamdani |
| Example 2 | Wikipedia (Q52)→wikipedia |
| Example 3 | Twitch (Q4555537)→twitch |
| Source | https://www.lgbtqnation.com/ |
| External links | Use in sister projects: [ar] • [az] • [bn] • [de] • [en] • [es] • [fa] • [fr] • [he] • [hi] • [it] • [ja] • [ka] • [kn] • [ko] • [ml] • [mr] • [nl] • [pl] • [pt] • [ro] • [ru] • [sv] • [te] • [tr] • [ur] • [vi] • [zh] • [commons] • [species] • [wd] • [en.wikt] • [fr.wikt]. |
| Mix'n'match | 7290 (LGBTQ Nation topic) |
| Number of IDs in source | 9473 |
| Expected completeness | LGBTQ Nation (Q85775305) |
| Implied notability | Wikidata property for an identifier that does not imply notability (Q62589320) |
| Formatter URL | https://www.lgbtqnation.com/tag/$1/ |
| Applicable "stated in"-value | LGBTQ Nation (Q85775305) |
| Single-value constraint | yes |
| Distinct-values constraint | yes |
Motivation
[edit]--Trade (talk) 17:24, 24 August 2025 (UTC)
Discussion
[edit]
Comment Why isn’t the source website https://www.lgbtqnation.com/? AdamSeattle (talk) 03:49, 26 August 2025 (UTC)
- is now Trade (talk) 19:02, 27 August 2025 (UTC)
Support --Tinker Bell ★ ♥ 13:27, 10 September 2025 (UTC)
Oppose The website seems minor and it's not clear to me what Wikidata gains by adding the tag. No reasoning is provided for why creating the tag would be a good idea. On the other hand the costs of adding a tag are clear. They make items bigger and thus increase load time and also take up user time by showing up on watchlists. ChristianKl ❪✉❫ 08:16, 23 September 2025 (UTC)
- Showing up on users watchlist is a bit of a silly concern Trade (talk) 01:48, 29 September 2025 (UTC)
MediaWiki wiki
[edit]Enpedia ID
[edit]| Description | identifier for an article on Enpedia |
|---|---|
| Represents | Enpedia (Q131736854) |
| Data type | External identifier |
| Domain | item |
| Example 1 | Japanese New Year (Q701398) → 正月 |
| Example 2 | Bloom Into You (Q22932761) → やがて君になる |
| Example 3 | Ai Kayano (Q1187078) → 茅野愛衣 |
| Example 4 | citation needed (Q3544030) → 要出典 |
| Example 5 | 2024 in rail transport (Q60542990) → 2024年の鉄道 |
| Allowed values | string |
| External links | Use in sister projects: [ar] • [az] • [bn] • [de] • [en] • [es] • [fa] • [fr] • [he] • [hi] • [it] • [ja] • [ka] • [kn] • [ko] • [ml] • [mr] • [nl] • [pl] • [pt] • [ro] • [ru] • [sv] • [te] • [tr] • [ur] • [vi] • [zh] • [commons] • [species] • [wd] • [en.wikt] • [fr.wikt]. |
| Number of IDs in source | 110753 |
| Formatter URL | https://enpedia.rxy.jp/wiki/$1 |
| See also | NicoNicoPedia ID (P6900), Moegirlpedia ID (P5737), Namuwiki ID (P8885), Pixiv Encyclopedia ID (P11408) |
| Single-value constraint | yes |
| Distinct-values constraint | yes |
Motivation
[edit]Enpedia is a Japanese encyclopedia website. It has a lot of articles of Japanese railways and Hyogo. Sometimes it might have more information than relevant Wikipedia articles.Shapez (talk) 16:59, 11 January 2025 (UTC)
Discussion
[edit]
Support --Trade (talk) 02:15, 2 February 2025 (UTC)
Strong oppose : Enpedia […] includes information that cannot be published under Wikipedia's strict publication standards, such as rumors and speculations that there are few sources that can be clearly identified. Here. So it is far from an authority. —Eihel (talk) 17:01, 10 February 2025 (UTC)
- NicoNicoPedia ID (P6900) and Pixiv Encyclopedia ID (P11408) are far from authorities. But they are adopted as properties. So I think it's okay. --Shapez (talk) 15:43, 15 February 2025 (UTC)
- Better now? Trade (talk) 21:14, 6 March 2025 (UTC)
- Yes, Enpedia is as authoritative a site as Niconico Pedia (Q10856286) and Pixiv Encyclopedia (Q108472060). -- 特急いよのたみ (talk) 13:48, 14 March 2025 (UTC)
Support Seems useful and similar properties that already exist indicate that not being an authority is not a problem. Warudo (talk) 22:51, 7 September 2025 (UTC)
ENTSO-E resource type
[edit]| Description | ENTSO-E code for type of Power System Resource. Alias: PSR type, electrical aset type |
|---|---|
| Data type | String |
| Domain | energy resource: Wikidata:WikiProject_Energy/Sector_Assets |
| Example 1 | busbar (Q1030817)→A08 |
| Example 2 | coal-fired power station (Q6558431)→B02, B05 |
| Example 3 | oil-fired power station (Q261604)→B06 |
| Allowed values | [AB]\d{2} |
| Source | https://eepublicdownloads.entsoe.eu/clean-documents/EDI/Library/Core/entso-e-code-list-v36r0.pdf "StandardAssetTypeList" |
| Planned use | Match to Wikidata:WikiProject_Energy/Sector_Assets |
| Number of IDs in source | 65 |
| Expected completeness | eventually complete (Q21873974) |
| See also | Energy Identification Code (P8645) |
| Distinct-values constraint | yes |
| Wikidata project | WikiProject Energy (Q15106301) |
Motivation
[edit]
Notified participants of WikiProject Energy
A standard code list by ENTSO-E, who regulate electricity data exchange in Europe (and more).
Exported 65 rows from https://transparency.ontotext.com/graphdb/sparql to https://gist.github.com/VladimirAlexiev/49aab79c9819a3d161f131ce424bbfc6 using this query:
PREFIX tr: <https://transparency.ontotext.com/resource/tr/>
PREFIX type: <https://transparency.ontotext.com/resource/type/>
select * {
?x tr:codeList type:Asset;
tr:notation ?entsoe;
tr:name ?name;
tr:description ?descr;
optional {?x tr:fuelTypeClassification ?class}
} order by ?x
This conforms with these ENTSO-E pages https://uat-transparency.entsoe.eu/content/static_content/Static%20content/web%20api/psr_type.html and https://transparencyplatform.zendesk.com/hc/en-us/articles/15856995130004-PsrType, but they list only 28 rows.
Google eg "B07 Fossil Oil shale" and you may find other sites with the same codes, eg https://github.com/timurka43/entsoe-py/blob/main/mappings.py#L169
Vladimir Alexiev (talk) 15:08, 27 June 2025 (UTC)
Discussion
[edit]
Comment 65 is kind of a small number. Is this part of some larger ontology that might be better described by a more widely scoped property? No chance of a formatter URL for this is there? ArthurPSmith (talk) 18:57, 2 July 2025 (UTC)
- Hmm, now I'm not sure - is this intended as an external id or a string-valued property that would be applied to individual power sources? ArthurPSmith (talk) 18:58, 2 July 2025 (UTC)
MediaWiki page revision ID
[edit]| Description | ID for a MediaWiki wiki revision, Wikimedia projects should use Wikimedia page-version URL (P7569) |
|---|---|
| Represents | MediaWiki page version ID (Q83336212) |
| Data type | String |
| Example 1 | subject→value |
| Example 2 | subject→value |
| Example 3 | subject→value |
| Source | https://www.mediawiki.org/wiki/Help:History |
| Expected completeness | always incomplete (Q21873886) |
| Implied notability | Wikidata property for an identifier that does not imply notability (Q62589320) |
| See also | Wikimedia page-version URL (P7569), MediaWiki page ID (P9675) |
| Single-value constraint | yes |
| Distinct-values constraint | yes |
Motivation
[edit]Currently there no property for a MediaWiki revision (except for Wikimedia projects where Wikimedia page-version URL (P7569) exists), this page propose a property that is similar to P7569, but for any MediaWiki wiki (Q15633582). – The preceding unsigned comment was added by DinhHuy2010 (talk • contribs) at 11:17, July 1, 2025 (UTC).
Discussion
[edit]
Support as a reference property, I assume. -wd-Ryan (Talk/Edits) 19:23, 1 July 2025 (UTC)- this would be a qualifier associated with a link or ID for a mediawiki page? I'm not quite clear on how this would be used, filled out examples in the proposal template or the motivation section would be very helpful. ArthurPSmith (talk) 18:55, 2 July 2025 (UTC)
- this would be a qualifier associated with a link or ID for a mediawiki page?
- An ID (aka the id after the oldid= parameter) DinhHuy2010 (talk) 07:29, 3 July 2025 (UTC)
Oppose No examples, no support--Trade (talk) 20:15, 7 July 2025 (UTC)
- @Trade Property could be use for reference to MediaWiki instances/wikis.
- courtesy pinging property creator(s): @ArthurPSmith DinhHuy2010 (talk) 15:02, 12 July 2025 (UTC)
- You still need to add examples. Prototyperspective (talk) 17:29, 28 July 2025 (UTC)
- @DinhHuy2010:--Trade (talk) 00:23, 23 November 2025 (UTC)
Support, but I wouldn't like having two systems for linking MediaWiki revisions. If this is created, I think we should deprecate and migrate P7569. Therefore, since its complete meaning (i.e. the site where the id would be valid) would depend of another property, it must have <property>property constraint (P2302)property scope constraint (Q53869507)property scope (P5314)as qualifier (Q54828449) . --Tinker Bell ★ ♥ 21:25, 23 November 2025 (UTC)
Wikimini article ID
[edit]| Description | identifier for an article on Wikimini (format "lang-code:title") |
|---|---|
| Represents | Wikimini (Q3568032) |
| Data type | External identifier |
| Example 1 | France (Q142) → fr:France |
| Example 2 | France (Q142) → en:France |
| Example 3 | Serbian (Q9299) → fr:Serbe |
| Example 4 | badminton (Q7291) → sv:Badminton |
| Formatter URL | https://fr.wikimini.org/wiki/$1 (French)
https://en.wikimini.org/wiki/$1 (English) https://sv.wikimini.org/wiki/$1 (Swedish) |
Motivation
[edit]We have Vikidia article ID (P12800), so why shouldn't we have this? I wonder why this isn't on Wikidata. Plus, Swedish, English and French are popular languages: QwertyZ34 (talk)
Discussion
[edit]
Support --Tinker Bell ★ ♥ 18:56, 12 October 2025 (UTC)
Support --Venca24 (talk) 09:32, 14 October 2025 (UTC)
Comment The formatter URL's won't work with the ID format you are proposing. Are there just 3 languages involved here? It could be 3 properties I suppose. ArthurPSmith (talk) 16:55, 20 October 2025 (UTC)
- Note that Vikidia has a central resolver that takes their language:name format and resolves to the right language server. ArthurPSmith (talk) 16:57, 20 October 2025 (UTC)
- There is 3 languages that are working, the others (like Spanish, Italian, Arabic) are suspended and/or don't work, like: https://es.wikimini.org/; maybe we can create items for French Wikimini, English Wikimini and Swedish Wikimini so they can be used better with applicable 'stated in' value (P9073) - like in Vikidia article ID - applicable 'stated in' value. QwertyZ34 (talk) 15:40, 21 October 2025 (UTC)
Support useful. But why aren't Vikidia and Wikimini joining forces and just one project? That would be difficult enough. Having separate projects duplicates work, makes it less efficient, and makes things harder to be found. Wikimini is a much better name than Vikidia but also not a good name. I suggest "Children's Wiki" or something like it that people searching the Web will actually find and which if linked is self-explanatory. --Prototyperspective (talk) 14:09, 1 December 2025 (UTC)
- True. It would be better if Vikidia and Wikimini decided to merge as a single project QwertyZ34 (talk) 22:07, 1 December 2025 (UTC)
Comment I removed the "ready" status. The format of the ID's is not compatible with the proposed formatter URL's, please propose a solution or make this 3 separate proposals. ArthurPSmith (talk) 20:26, 11 December 2025 (UTC)
- applies if regular expression matches (P8460) ^(?!en:).* for english and applies if regular expression matches (P8460) ^en:.* for other languages QwertyZ34 (talk) 21:58, 11 December 2025 (UTC)
SetesdalWiki ID
[edit]| Description | Identifier for an item in Setesdalwiki Identifier for an item in the internet encyclopedia Setesdalwiki |
|---|---|
| Represents | online encyclopedia (Q615699) internettensyklopedi |
| Data type | External identifier |
| Template parameter | identifier |
| Domain | All kind of types within items related to Setesdalswiki (Q136556080) |
| Example 1 | Bykle Municipality (Q88806) → Bykle_kommune |
| Example 2 | Osmund Faremo (Q4585848) → Osmund_Faremo |
| Example 3 | Oslo (Q585) → Oslo |
| Allowed values | [A-Za-z0-9_-]+ |
| Source | https://www.setesdalswiki.no |
| Planned use | in Template:Authority control (Q3907614) |
| Number of IDs in source | 97939 |
| Expected completeness | always incomplete (Q21873886) |
| Formatter URL | https://www.setesdalswiki.no/wiki/$1 |
| Robot and gadget jobs | Mix 'n' Match |
| Applicable "stated in"-value | Setesdalswiki (Q136556080) |
| Distinct-values constraint | yes |
Motivering/begrunnelse
[edit]Valuable internet encyclopedia for items covering the Setesdalarea of Norway Pmt (talk) 08:01, 22 October 2025 (UTC)
(Legg inn motivering/begrunnelse for forslaget til denne egenskapen her.)
Discussion
[edit]Marking the ID as ready, there has been no oponents to the proposal Pmt (talk) 17:09, 5 November 2025 (UTC)
Comment You shouldn't set ready on your own proposals; generally property creators look for some sort of positive support, not just lack of opposition. On this one, the proposal definitely isn't ready because your example links don't match the formatter URL. Also there seem to be some extraneous space (' ') characters in the template values. Please double check the proposal template. Otherwise, this seems fine to me, so count this as
Support when the template has been fixed up. ArthurPSmith (talk) 00:44, 14 November 2025 (UTC)
- Seems resolved? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 12:42, 11 February 2026 (UTC)
Oppose No item for the website exists--Trade (talk) 02:04, 28 January 2026 (UTC)
- That is easily resolved; and not a reason to block property creation. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 12:42, 11 February 2026 (UTC)
Support. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 12:41, 11 February 2026 (UTC)
Ruwiki ID
[edit]| Description | identifier of an article in the Russian multilingual online encyclopedia Ruwiki |
|---|---|
| Represents | Ruwiki (Q118995957) |
| Data type | External identifier |
| Domain | entity (Q35120) |
| Example 1 | Russia (Q159)→ru:Россия |
| Example 2 | Russia (Q159)→alt:Россия |
| Example 3 | Wikipedia (Q52)→ru:Википедия |
| Source | https://ru.ruwiki.ru/wiki/Заглавная_страница |
| External links | Use in sister projects: [ar] • [az] • [bn] • [de] • [en] • [es] • [fa] • [fr] • [he] • [hi] • [it] • [ja] • [ka] • [kn] • [ko] • [ml] • [mr] • [nl] • [pl] • [pt] • [ro] • [ru] • [sv] • [te] • [tr] • [ur] • [vi] • [zh] • [commons] • [species] • [wd] • [en.wikt] • [fr.wikt]. |
| Number of IDs in source | 2,185,627 (Russian) |
| Expected completeness | always incomplete (Q21873886) |
| Implied notability | Wikidata property for an identifier that does not imply notability (Q62589320) |
| Formatter URL | https://$1.ruwiki.ru/wiki/$2 |
| Applicable "stated in"-value | Ruwiki (Q118995957) |
| Single-value constraint | yes |
| Distinct-values constraint | yes |
Motivation
[edit]While the site was initially a fork of various Russian-language (and Russian minority language) Wikipedia's it still contains a significant amount of rewriting from their originals. – The preceding unsigned comment was added by Trade (talk • contribs) at 23:49, January 28, 2026 (UTC).
Discussion
[edit]- See also some discussions at m:Talk:Interwiki_map/Archives/2024#Ruwiki.ru. This would be one of cases similar to Wikidata:Project_chat/Archive/2020/02#Is_Wikidata's_purpose_to_provide_links_to_every_(open)_wiki?.--GZWDer (talk) 13:11, 29 January 2026 (UTC)
- See also Wikidata:Properties for deletion/P10725 for PFD for a property for another Wikipedia fork. GZWDer (talk) 13:12, 29 January 2026 (UTC)
Oppose - duplicative, not useful. Also the proposed formatter URL will need external support, it will not work natively. ArthurPSmith (talk) 21:15, 3 February 2026 (UTC)