Shortcuts: WD:PP/GEN, WD:PP/Generic
Wikidata:Property proposal/Generic
Property proposal: | Generic | Authority control | Person | Organization |
Creative work | Place | Sports | Sister projects | |
Transportation | Natural science | Computing | Lexeme |
See also
[edit]- Wikidata:Property proposal/Pending – properties which have been approved but which are on hold waiting for the appropriate datatype to be made available
- Wikidata:Properties for deletion – proposals for the deletion of properties
- Wikidata:External identifiers – statements to add when creating properties for external IDs
- Wikidata:Lexicographical data – information and discussion about lexicographic data on Wikidata
This page is for the proposal of new properties.
Before proposing a property
- Search if the property already exists.
- Search if the property has already been proposed.
- Check if you can give a similar label and definition as an existing Wikipedia infobox parameter, or if it can be matched to an infobox, to or from which data can be transferred automatically.
- Select the right datatype for the property.
- Read Wikidata:Creating a property proposal for guidelines you should follow when proposing new property.
- Start writing the documentation based on the preload form below by editing the two templates at the top of the page to add proposal details.
Creating the property
- Once consensus is reached, change status=ready on the template, to attract the attention of a property creator.
- Creation can be done 1 week after the creation of the proposal, by a property creator or an administrator.
- See property creation 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 2024/09. |
General
[edit]Initialism
[edit]Description | abbreviation containing only first letters of an expression (regardless if pronounced as letters or as a word) |
---|---|
Data type | Monolingual text |
Example 1 | United States of America (Q30)initialismUSA |
Example 2 | Holy Roman Empire (Q12548)initialismHRE |
Example 3 | National Aeronautics and Space Administration (Q23548)initialismNASA |
Example 4 | Foreign, Commonwealth and Development Office (Q358834)initialismFCDO |
Example 5 | Changpeng Zhao (Q52714313)initialismCZ |
Source | https://en.wikipedia.org/wiki/Acronym#Nomenclature |
Planned use | being able to relocate the initialisms from short name (P1813) in order to change them to "longer" short names, like "United Kingdom" |
See also | short name (P1813) |
Motivation
[edit]The reaction of my question Wikidata:Project_chat#Property:P1813_short_name_with_countries was, that there should be a new property, to be able to move the initialisms used in short name (P1813) to there and to restrict that one to actual short names without using initialisms. This is what I'm trying to do here. Although I have been active on Wikipedia for over a decade, I'm a novice to Wikidata. Therefore this is my first request of this kind. I didn't know how to fill in some of the fields and I would really appreciate someone helping out there.
The further motivation is being able to use short country names for generation of historical place names in the browser extension WikiTree BEE, but I assume others might be happy to have more "handy" names as well, that are not completely abbreviated.
Thanks and kind regards --Flominator (talk) 10:02, 30 August 2024 (UTC)
Discussion
[edit]An initialism should be just initials, so Orange is a bad example. It includes acronyms (which you should be able to pronounce as words), but also tongue-twisting jumbles of letters. Its key requirement is that its a sequence of initial letters extracted from a title that are commonly used to describe it. Normally all capitals, but sometimes mixed (eg SoHo (Q461572))
Some short name (P1813) are initialisms, but not all, and it will help for countries like United States of America (Q30) (United States, States, US, USA), or organisation like the Foreign, Commonwealth and Development Office (Q358834) ("Foreign Office", "FCO", "FCDO" ect)
it need not be single valued. I'd see it being used in addition to short name (P1813), not replacing it. The key question is whether there are enough examples to make it worth having a new property, rather than having a initialism (Q918270) qualifier to the existing property. What property should be used for the qualifier? Vicarage (talk) 10:26, 30 August 2024 (UTC)
- Thanks. I removed Orange (that was an example for short name (P1813), my bad) and added FCDO instead. Yes, the idea would not be to replace short name (P1813), but be able to completely remove the abbreviation aspect from it, in order to only use it for shorted forms. --Flominator (talk) 11:16, 30 August 2024 (UTC)
- Support This seems reasonable to me - I do have a question about the domain for this property. The examples are all organizations (or a country), but presumably anything that is (sometimes) referred to only by initials would qualify? Like CZ for Changpeng Zhao (Q52714313)? ArthurPSmith (talk) 16:56, 30 August 2024 (UTC)
- I must admit, that I had never heard of CZ, but instantly came up with JFK instead. Good point, though. I added CZ as example. --Flominator (talk) 07:44, 31 August 2024 (UTC)
- Neutral Those that created short name (P1813) should be aware of this property proposal as it aiming at splitting "short but not too short words" // "very short or only first letters" that are currently inside short name (P1813). Would there be people doing the job of splitting the current content of short name (P1813) ?Bouzinac 💬●✒️●💛 14:21, 31 August 2024 (UTC)
- Oppose I wouldn't mind a separate property for abbreviations, but this won't achieve what you want it to achieve. There are various ways to make abbreviations which are not initialisms, and a single abbreviation can combine more than one method. Those would not belong in this property and creating a separate property for every single type (and combination of types) that can be used would make the data hard to enter/use. I think it would make more sense to use something like object of statement has role (P3831) as a qualifier. - Nikki (talk) 06:45, 1 September 2024 (UTC)
- Oppose your argument has convinced me that documenting qualifiers to short name (P1813) is the way to go. Vicarage (talk) 07:24, 1 September 2024 (UTC)
- Can you please show me as example, how that would look like for UK or USA? --Flominator (talk) 14:09, 1 September 2024 (UTC)
- United States of America (Q30) modified. Vicarage (talk) 14:19, 1 September 2024 (UTC)
- That's also a way. Thank you. Should this be put in the property documentation? Flominator (talk) 16:00, 1 September 2024 (UTC)
- United States of America (Q30) modified. Vicarage (talk) 14:19, 1 September 2024 (UTC)
- Can you please show me as example, how that would look like for UK or USA? --Flominator (talk) 14:09, 1 September 2024 (UTC)
- Oppose your argument has convinced me that documenting qualifiers to short name (P1813) is the way to go. Vicarage (talk) 07:24, 1 September 2024 (UTC)

SELECT DISTINCT ?item ?itemLabel ?initials WHERE {
SERVICE wikibase:label { bd:serviceParam wikibase:language "en-GB,en,mul". }
?item wdt:P31 wd:Q6256;
p:P1813 [ ps:P1813 ?initials; pq:P3831 wd:Q918270].
}
Vicarage (talk) 16:37, 1 September 2024 (UTC)
Publication type of scholarly article
[edit]Description | Publication type of scholarly article |
---|---|
Data type | Item |
Template parameter | Different from publication type as used for example in w:Template:Infobox short story |
Domain | Instances of scholarly article (Q13442814) and its subclasses. |
Allowed values | Permitted values typically should be potential subclasses of scholarly work (Q55915575). In practice there is diversity in instance of (P31) statements additional to scholarly article (Q13442814) items, which number in tens of millions, and some cleanup work is anticipated for both domain and range. |
Example 1 | Malaria and the microbiome: a systematic review (Q56383548) → systematic review (Q1504425) |
Example 2 | NIH Consensus conference. Gallstones and laparoscopic cholecystectomy (Q70552083) → NIH consensus development conference summary (Q27718083) |
Example 3 | Practice guidelines for the management of bacterial meningitis (Q33982444) → medical guideline (Q878041) |
Source | The new statements initially will be generated by rules from existing statements, as followup to the WDQS split. |
Robot and gadget jobs | Bots will be used heavily to implement the migration from instance of (P31) statements. |
Wikidata project | Wikidata:WikiCite |
Motivation
[edit]Currently these publication types of articles are added as instance of (P31) statements, but better data modelling can follow from having a separate property. For example, on clinical trial (Q30612) under MeSH descriptor ID (P486) the publication type meaning is at present given preferred rank over the "clinical trials as topic" meaning. It would be better not to overload the item in this way, given the importance of clinical trials in medical research. We should have two items, one of which should only be used in "publication type of scholarly article" statements.
This idea was mentioned already several years ago. It comes up now because of the graph split treating the scholarly article items as a graph in their own right. See Wikidata talk:WikiCite#Community input into WDQS graph split: a publication type property proposal for a preliminary discussion. That thread links to a graph split page which goes into fuller details of the technical side. I've been asked by the developers working on the split to make this proposal. @Daniel Mietchen: @Bluerasberry: @Sj:
While the graph split will make SPARQL queries more complex, good can come of it if this proposed property is created, and some systematic work goes on to sort out the current overloading of dozens of items. Charles Matthews (talk) 10:35, 12 September 2024 (UTC)
Discussion
[edit]- Support Would most (all?) subclasses of scholarly article (Q13442814) be replaced by this new property then, and their instances updated to just be instances of scholarly article (Q13442814)? ArthurPSmith (talk) 13:23, 12 September 2024 (UTC)
- Not part of the original plan anyway, which was simply to create new triples from old, with new object items where, for example, "clinical trial" had become either an item for the real-life testing, or for a publication type. Charles Matthews (talk) 15:07, 12 September 2024 (UTC)
- Comment The existing set of rules has already raised some concerns and confusions at Wikidata_talk:SPARQL_query_service/WDQS_graph_split/Rules and I think this proposal is going to help to reduce these confusions/ambiguities. From a technical standpoint what is important is that this new property will help the system to determine if an item should be part of the scholarly_articles subgraph or not. My current understanding (but please let me know if I'm wrong) is that the fact that an entity has a non-deprecated statement with this new property will be sufficient to classify it as a scholarly article (it would not even have to look at the value of this property). From a practical point of view, assuming this proposal is accepted, we should update the WDQS software with this new rule before any migration is attempted. During the migration we might have to keep both types of rules (the one based on P31 and the one based on this property). DCausse (WMF) (talk) 07:05, 13 September 2024 (UTC)
- @DCausse (WMF): So there can be a case analysis with a few cases. An example that is clear is the case of multicenter study report (Q91901000), label "class of publication", and multicenter clinical trial (Q6934595). I have checked just now, and nothing that is instance of multicenter clinical trial (Q6934595) is also instance of scholarly article (Q13442814). On Study of GLS-5700 in Dengue Virus Seropositive Adults (Q26762063) there is another P31 statement, but for another type of trial. I have worked through the 28 hits for multicenter study report (Q91901000):
SELECT ?item ?itemLabel
WHERE {?item wdt:P31 wd:Q91901000;
wdt:P31 wd:Q13442814.
SERVICE wikibase:label { bd:serviceParam wikibase:language "[AUTO_LANGUAGE],mul,en". }
}
- I see a case where controlled clinical trial (Q70447452) is used instead of controlled clinical trial (Q58897597). So as an example for your question, a P31 statement with controlled clinical trial (Q58897597) ought to be enough to classify as a scholarly article. I find no hits like that, so perhaps all those items have already been split out. One hit for Role of lopinavir/ritonavir in the treatment of SARS: initial virological and clinical findings. (Q35536588) which is "wrong", twice. But really this can't be discussed fully here. Charles Matthews (talk) 10:23, 13 September 2024 (UTC)
characteristic of (aliases: quality of | property of | inheres in )
[edit]Description | (qualifier only) statement value is a characteristic, quality, property, or state of this item |
---|---|
Data type | Item |
Domain | quality (Q1207505), property (Q937228), state (Q3505845), relation (Q930933), type of property (Q96253971) |
Example 1 | battery management system (Q810938)measures (P2575)temperature (Q11466) |
Example 2 | terminal velocity (Q614981)has contributing factor (P1479)orientation (Q2235286) |
Example 3 | The Unconscious of a Conservative (Q52945586)main subject (P921)mental health (Q317309) |
Example 4 | tetrachromacy (Q94556)has characteristic (P1552)dimension (Q4440864) |
See also | of (P642), applies to part (P518), facet of (P1269), part of (P361), has characteristic (P1552) |
Motivation
[edit]This common relation is widely expressed with the massively overloaded (and to-be-deprecated) of (P642), and sometimes (erroneously) with applies to part (P518), facet of (P1269), part of (P361), and possibly a few other properties. Although it is semantically an inverse of has characteristic (P1552), constraining this property to the qualifier scope will prevent introduction of redundant inverses of has characteristic (P1552) statements. Swpb (talk) 18:03, 12 September 2024 (UTC)