Wikidata:Property proposal/Archive/18

From Wikidata
Jump to navigation Jump to search
This page is an archive. Please do not modify it. Use the current page, even to continue an old discussion.

place made

Descriptionplace where the item was made
Data typeItem
Domainartificial physical object (Q15222213) ?
Allowed valuesinstance of geographic location (Q2221906)
ExampleMona Lisa (Q12418) -> Florence (Q2044)

We already have country of origin (P495), but we also need something that is not restricted to countries Zolo (talk) 14:59, 11 January 2014 (UTC)

I  Support but a related question is if Italy existed as a nation when Mona Lisa was painted? -- Lavallen (talk) 19:44, 11 January 2014 (UTC)
 Comment. I feel like "country of origin" like the country property should mostly be used as a sort of convenient high level shorthand, and "place made" could be used with more accurate value. For ancient stuff, "country" is indeed a bit problematic, we have a similar problem with country of citizenship (P27). Michelangelo is hardly an Italian citizen, still the usual way to present him is "Italian artist". --Zolo (talk) 19:13, 13 January 2014 (UTC)
Yes, the word "italian" can as far as I remember, be found in the bible. So the geograhic area is old, no matter if it was a country or not. -- Lavallen (talk) 20:04, 13 January 2014 (UTC)
I have added administrative territorial entity (Q56061) as this property's 'allowed values' parameter; specifically, that item is intended to be the property's range. Please support or oppose the proposals at Template_talk:Property_documentation#Parameter_enhancements to update the property parameters to use values like 'domain', 'range', 'one of' that are closer to Semantic Web conventions. Emw (talk) 22:39, 12 January 2014 (UTC)
That seems to be the idea, but I am not sure it can be applied rigorously. For archaeological artefacts for instance, I guess we can have values like "Mississippi Delta" because some material details suggest it is the region of origin, but we cannot really give a precise administrative division. --Zolo (talk) 19:13, 13 January 2014 (UTC)
Why not geographic location (Q2221906) instead of administrative territorial entity (Q56061)? (Note that the latter is a subclass of the former (via "region"). I think it would be better to have the range more generic, so you could allow, for example, specific factories. Klortho (talk) 03:11, 14 January 2014 (UTC)
Klortho, good point, updated. Emw (talk) 03:40, 14 January 2014 (UTC)

@Lavallen, Emw, Klortho, Paperoastro:: done location of creation (P1071) --Zolo (talk) 08:38, 18 January 2014 (UTC)

Danemark Job Code (DISCO-08)

DescriptionDanemark Job Code DISCO-08 maintained by the DST and derived from ISCO
Data typeString
Template parameternone so far
Domainprofession (Q28640),occupation (Q13516667), jobs
Allowed values6 digit numbers
Examplepharmacist (Q105186) => 226200
Format and edit filter validation6 digit numbers
Robot and gadget jobsimport would be nice to have
Proposed byTeolemon (talk)

Needed by the Occupation and Professions Taskforce. Teolemon (talk) 22:15, 29 November 2013 (UTC)

 Support --Micru (talk) 10:19, 5 December 2013 (UTC)
 Support. Emw (talk) 04:25, 3 January 2014 (UTC)

ERA Journal ID

   Done: ERA Journal ID (P1058) (Talk and documentation)
DescriptionA unique identifier for periodic academic/scientific journals, used by Australian government and all Australian universities.
Data typeString
Domaincreative work (constraint: periodical (Q1092563))
Allowed valuesThe specification is: string up to ten characters long ; the research council has in practise only used digits, and only used up to five digits.
ExampleNature (Q180445) => 17479
Sourcew:Excellence in Research for Australia (w:Australian Research Council);
Proposed byJohn Vandenberg (talk)

The Australian and Danish research assessment journal lists have been used by the Academic Journals project as useful indicators of notability (and prioritising our work of creating articles about journals). Both the Australian and Danish include some journals of only national significance, but the vast majority overlap and provide a comprehensive list of journals that are judged to be significant by their respective colleges of experts. Extracts of these lists can be found at w:Special:PrefixIndex/Wikipedia:WikiProject Academic Journals, such as w:Wikipedia:WikiProject Academic Journals/ERA PCE Astar. I mostly work with the ERA list, so I would like to tackle that one first. The Australian ERA journal list has ~15,000 entries. Several online databases of the ERA journal list exist, such as this.

Also once we have ERA IDs, we can use the ERA dataset to automatically determine which ISSNs are missing from Wikidata, and later we can assign 'fields of research' to journals using the ERA dataset. John Vandenberg (talk) 10:05, 30 November 2013 (UTC)

 Support--Micru (talk) 10:30, 5 December 2013 (UTC)
 Support. Emw (talk) 04:25, 3 January 2014 (UTC)


   Done: CVR number (P1059) (Talk and documentation)
DescriptionThe Central Business Register identifier. Number for the official database of Danish companies/organizations [1]
Data typeString
Template parameterCvr in w:da:Skabelon:Infoboks virksomhed
DomainCategory:Organizations based in Denmark (Q7314882) Danish organizations
Allowed values8-digit numbers [2]
Example"32859909" for Wikimedia Danmark. Det Danske Filmstudie (Q12308319) => 28516797
Format and edit filter validationCheck for 8 digits. (Is there any Special:AbuseFilter for that?)
Sourcew:da:Det Centrale Virksomhedsregister, English
Proposed byFinn Årup Nielsen (fnielsen) (talk)

Most larger Danish companies (i.e., companies with more than one employee) have a CVR-number that uniquely identifies the company or organization, e.g., the Danish Chapter of Wikimedia has a CVR number and the company Lundbeck (Q902171) has the number 56759913. The number can be resolved to a lookup on the Danish site, e.g., for Lundbeck (Q902171) it is This allows for further access to headquarters address, type, branch, starting date, board members, etc. Finn Årup Nielsen (fnielsen) (talk) 13:11, 8 November 2013 (UTC)

 Support seems straight-forward. Joshbaumgartner (talk) 11:34, 10 November 2013 (UTC)


   Done: rector (P1075) (Talk and documentation)
Descriptionthe rector of a university.
Data typeItem
Template parameter"Rettore" in it:Template:Università
ExamplePolytechnic University of Milan (Q392904) => Giovanni Azzone (Q3766511)
Proposed byYiyi .... (talk!)

Yiyi .... (talk!) 22:23, 20 November 2013 (UTC)

 Support --Tobias1984 (talk) 07:12, 13 January 2014 (UTC)

✓ Done --Tobias1984 (talk) 21:18, 20 January 2014 (UTC)

Thailand central administrative unit code

DescriptionUnique code for each of the Thai central administrative units, i.e. province, district, subdistrict and administrative village, and some municipalities. Based on the Thai Industrial Standard 1099-2548 (Q15477531), for provinces identical with the ISO3166-2 code.
Data typeString
Domaininstances of administrative divisions of Thailand (Q1077333)
Allowed values2, 4, 6 or 8 digits
ExampleTakuk Nuea (Q15185578) => 841902
Sourceen:ISO 3166-2:TH, (Thailand central administrative unit code (Q15477767))
Robot and gadget jobsCould be imported from the en-Wikipedia infoboxes (probably always blank_info_sec2). Building a bot myself for setting all the missing statements in the Thai administrative entities items, including this.
Proposed byAhoerstemeier (talk)

@Ahoerstemeier, Micru, Lavallen: ✓ Done --Ricordisamoa 20:46, 13 January 2014 (UTC)

Structural type

Rail gauge / Track gauge

   Done: track gauge (P1064) (Talk and documentation)
DescriptionTrack gauge is a technical term used in rail transport to define the spacing of the rails on a railway track.
Data typeItem
Template parameterInfobox public transit - track_gauge
Allowed valuesany item from w:Template:Navbox track gauge
ExampleLine C-1 (Q3239078) => 1668 mm track gauge (Q3319112)
Format and edit filter validationfilter Special:AbuseFilter/17)
SourceWikipedia list article (either infobox or source)
Proposed byB.Zsolt (talk)

--B.Zsolt (talk) 13:45, 13 October 2013 (UTC)

 Support Also sorted this under rail transport. Joshbaumgartner (talk) 00:57, 27 October 2013 (UTC)
 Support Changed to item. Most countries use an standard for their track gauge, so instead of using the dimension, it could refer to the standard they are using.--Micru (talk) 16:14, 9 November 2013 (UTC)
 Support --Konggaru (talk) 16:35, 3 January 2014 (UTC)
 Support Danrok (talk) 01:09, 9 January 2014 (UTC)
✓ Done Danrok (talk) 17:06, 9 January 2014 (UTC)


DescriptionTaxonId at The Plant List (Q625817)
Data typeString
Domainextant species of vascular plants and bryophytes
ExamplePlantList-ID for Amorphophallus titanum (Q431224) is kew-8323
SourceThe Plant List (Q625817)
Robot and gadget jobsAdd '$1' to Gadget-AuthorityControl.js
Proposed bySuccu (talk)

Motivation. At viwiki there are more than 300,000 bot generated articles based on this Id. So it might be helpful to have a direct reference. --Succu (talk) 21:49, 8 January 2014 (UTC)

Note: viwiki used a previous version (1.0) of his list, so a link to the present version (1.1) will not be a perfect match. - Brya (talk) 04:46, 9 January 2014 (UTC)

ICTV virus ID

   Done: no label (P1076) (Talk and documentation)
Descriptioncode for viruses from ICTV (
Data typeString
Template parameterinfobox virus "ICTV"-field
Allowed valuesexcact string
ExampleAdenoviridae (Q193447) = "00.001"
Format and edit filter validationformat, unique, single
Proposed by--Tobias1984 (talk) 15:39, 13 January 2014 (UTC)

WikiProject Taxonomy has more than 50 participants and couldn't be pinged. Please post on the WikiProject's talk page instead. --Tobias1984 (talk) 15:40, 13 January 2014 (UTC)

 Support --Succu (talk) 16:16, 13 January 2014 (UTC)

pathogen transmission process

DescriptionHow a pathogen is transmitted. Follows the pathogen transmission ontology from OBO.
Data typeItem
Domaindisease (Q12136)
Allowed valuespathogen transmission (Q525512), or any of its subclasses
Examplemalaria (Q12156) transmission process nodding disease (Q895930)
SourceScientific publications
Proposed by--Tobias1984 (talk) 10:37, 9 December 2013 (UTC)
Probably needs some discussion whether the process or the medium should be used. E.g. Is it the insect that transmits the disease, the insect sting, or the fluids transmitted during the insect sting? Same for HIV. Is it the different body fluids (e.g. blood), all bodily fluids together, sexual activity (or contaminated blood transfusion)? Is there a way we can or should split this information to another property? --Tobias1984 (talk) 10:37, 9 December 2013 (UTC)
Pinging WikiProject Medicine: @Jmh649:, @Bluerasberry:, @Wouterstomp:, @Gambo7:, @Daniel Mietchen:, @Andrew Su:, @Peter.C:, @Klortho:, @Remember:, @Matthiassamwald:, @Projekt ANA:, @Andrux: --Tobias1984 (talk) 10:40, 9 December 2013 (UTC)
  • Support If I understand correctly, this is a proposal to build the following hierarchy:
medical condition
probable cause (perhaps a virus or parasite)
transmitter of the cause (perhaps blood or mosquitoes, or any vector (Q107994))

I am not sure about this. It needs more thought. I was was wondering whether this could also be a property for genetic diseases, so the cause of the disease would be some change in body function, and the cause of that (or transmitter) would be a particular genetic abnormality. Other medical conditions like obesity (Q12174) could have behavioral causes, so I suppose a probable cause could be junk food (Q851384) and a transmitter of the cause could be overeating (Q331632). This scheme works with vector (Q107994) but I am not sure how it works for all medical conditions. Blue Rasberry (talk) 15:13, 9 December 2013 (UTC)

@Bluerasberry: The most helpful thing would be, what kind of questions you would like Wikidata to answer. A physician might notice that there are a lot of black flies in a village. A query to Wikidata for "diseases transmitted by black flies" would return this disease. This property also wouldn't be applied to all diseases. I don't think it makes semantic sense to talk about "transmission of obesity". But we definitely already have the capability to list likely causes for obesity. --Tobias1984 (talk) 15:41, 9 December 2013 (UTC)
Here's an ontology for disease transmission. Quite more complex than what is proposed above, even though only intended for transmission in humans. --Daniel Mietchen (talk) 17:39, 9 December 2013 (UTC)
That's really interesting and thorough. It is using the term "Pathogen transmission", and I think that name is better for this property than "transmitted by" because it clearly excludes genetics and behavioral causes. Also if we used this "Pathogen transmission scheme" we could adopt all the text and definitions there to create documentation for how this property could be used. Tobias1984, what do you think of Daniel's proposal? Is it what you had in mind? If so, could I work with you to take the documentation Daniel has and use it as a base to create documentation for this property? I am still learning Wikidata so I am not sure how these things work or what is to be done. Blue Rasberry (talk) 16:11, 10 December 2013 (UTC)
@Bluerasberry: Renaming to "pathogen transmission" sounds fine. But would it still allow linking to a carrier of parasites? I'm having trouble finding anything on the disease ontology website. Is there an example of something like Malaria? --Tobias1984 (talk) 16:27, 10 December 2013 (UTC)
 Comment Tobias, Bluerasberry, I think "transmitted by" "transmission process" (see below) would be an ideal label for this property. "Pathogen transmission" is slightly redundant, because transmission -- when used as a medical term -- implies a pathogen. To my understanding, the statement "a genetic mutation in BRCA1 transmits breast cancer" is an incorrect use of the word "transmit". Also, as you can see in, "pathogen transmission" is a class, not a property. The 'Pathogen transmission' OBO ontology would be good to use as a basis for a subclass hierarchy for types of pathogen transmission, but it suggests a different range than the one in the examples of this property proposal. (As an aside, I think adopting other OBO ontologies for other domains of ours like chemistry and genetics would be a great idea. The BFO upper ontology upon which OBO ontologies are based could also help resolve abstract questions that will likely come up in these domains.)
I'll take a closer look at the Pathogen Transmission ontology in the next day or so. Perhaps that can help suggest well-thought-out parameters for "allowed values" (i.e. range), etc. Emw (talk) 04:56, 12 December 2013 (UTC)
Wow user:Emw, I am not sure at all what is best and you seem to know more than me. I got the name "pathogen transmission" because that is what the ontology calls it, and it seemed authoritative to me, but if you say that this term belongs elsewhere in the hierarchy or that it is confusing then you likely know more than me. User:Tobias1984, I clicked in and saw some of the expected values. Look at where it says name, and here are some examples - "vector-borne, congenital, contact, vehicle-borne medical, vector-borne bite, vector-borne gastro-intestinal, insect borne, Anopheles gambiae borne, arachnid borne". I presume that for malaria, this property should be labeled "Anopheles gambiae borne", and that in labeling other diseases, people could be prompted to choose one of these other labels. EMW, if you have anything more to say about how these ontologies could be used or how they might be useful then please share. If you suggested some course of action then I would try to understand it, but right now and without seeing how Wikidata or these oncologies are supposed to work, I still find this entire process confusing even though I want to understand it. Blue Rasberry (talk) 19:32, 12 December 2013 (UTC)
Tobias, Bluerasberry, here is the class hierarchy of 'transmission process' per (You can explore it yourself with Protege, downloadable at

Pathogen transmission class hierarchy

I recommend using the pathogen transmission OBO ontology outlined above as the basis for this property. Because 'transmitted by' suggests values could be a subclass of (P279) pathogen (Q170065) and the OBO ontology is dealing with a subclass of (P279) pathogen transmission (Q525512) (itself a subclass of the BFO "process" class, outlined here), I think this property should be called "transmission process". Given that, I think it would be best to update the "allowed values" field of the property proposal template to subclass of (P279) pathogen transmission (Q525512) (e.g. , insect borne transmission (Qx)), not subclass of (P279) pathogen (Q170065) (e.g. insect (Q1390)). If those updates were made and this property were explicitly tied to the semantics of trans.owl, then I would support it. Emw (talk) 04:44, 13 December 2013 (UTC)
I am not aware of the procedure that would unambiguously "tie" a Wikidata property to an external ontology, but agree that we should aim for such a clear mapping here, so as to allow for interoperability beyond Wikidata. I also agree with @Emw:'s proposed changes to the allowed values. What I am not yet comfortable with is the naming of it all - why not rename pathogen transmission (Q525512) into "disease transmission" or "pathogen transmission" and, consequently, our property here into "disease transmission process" or "pathogen transmission process"? --Daniel Mietchen (talk) 23:55, 14 December 2013 (UTC)
  • I do not know what to say except that I support this on the basis of opinions of others and that I want to see how Wikidata can use schemes like this. This ontology has the support of Daniel Mietchen and EMW, plus it came from an authoritative source. Let's use it until and unless someone challenges it with something better. What does it mean to set up a Wikidata property with a hierarchy like this? I know nothing about setting this up. How does this work? What is to be done now? Blue Rasberry (talk) 21:02, 13 December 2013 (UTC)
Bluerasberry, Daniel, class hierarchies like the one above are created with the property subclass of (P279). Its semantics match those of the rdfs:subClassOf property, which you can see in trans.owl. The property is transitive, so if X is a subclass of Y, and Y is a subclass of Z, then X is a subclass of Z. For example check out acute lymphocytic leukemia (Q180664), then do an in-page search / Ctrl-F for 'acute lymphoblastic leukemia' in Wikidata's hierarchy of diseases.
I've copied the OBO pathogen transmission ontology to Wikidata. The items are linked above; you can also see it represented here. Emw (talk) 17:56, 14 December 2013 (UTC)


@Emw:, @Bluerasberry:, @Daniel Mietchen: I think a few examples would be helpful. I was thinking we should use it like this (using 'transmission process' as a property, not qualifier to another property):

I'm also still unsure what to put for has cause (P828) malaria is already a subclass of parasitic infectious diseases (Q1750273). So the cause would be a parasite (I don't think we have an item for that). --Tobias1984 (talk) 13:07, 15 December 2013 (UTC)

[Hi, I am also new to Wikidata.] Daniel wrote, above, "I am not aware of the procedure that would unambiguously "tie" a Wikidata property to an external ontology". I'm also curious about this. Emw, I looked at, for example, vector-borne transmission (Q15304520), and I see that you have linked it as stated in (P248) Pathogen Transmission Ontology (Q15304508), but I'm wondering if there isn't the equivalent of skos:exactMatch in Wikidata, and whether or not, when these ontologies get imported en-masse, each term shouldn't be linked directly to the corresponding ontology term. It seems to me that would go a long way towards integrating this with the wider linked data world. Regarding naming, I'd like to suggest that this property keep the originally proposed name of "transmitted by". The problem with "transmission process" is that it collides rather badly with pathogen transmission (Q525512). "Transmitted by", on the other hand, seems pretty clearly to be a property and not an item. Klortho (talk) 07:26, 16 December 2013 (UTC)

Klortho, as long as it's made clear that the range of this property is pathogen transmission (Q525512) (i.e. transmission process) and not vectors like Anopheles gambiae (Q135237), then I think the label "transmitted by" is OK. To your more interesting point: we don't have a formal property like skos:exactMatch (or owl:sameAs / owl:equivalentClass) on Wikidata. Such a property was proposed in September; the archived discussion is here. The comments from Markus Krötzsch there are insightful. Basically, we would only use our yet-to-exist owl:sameAs property to map to instances (owl:equivalentClass for classes) to entries that are exactly the same in other ontologies.
However, Tobias's example above indicates that we might not want a link that strong. If you search for TRANS_0000022 in trans.owl, you'll see that the concept is very sparsely annotated. To my understanding, if we used an equivalence property, then we could not have helpful extra information like that in Tobias's example -- we'd be able to import but not modify terms from other ontologies.
A slightly softer link might be better. Authority control properties are common in Wikidata, and seem like a good model here. This would mean having claims something like "OBO identifier (Px): TRANS_0000022" on Anopheles gambiae borne transmission (Q15304534). That way, we could indicate the class came from that OBO ontology, but we could add helpful information like Tobias suggests. Emw (talk) 13:40, 16 December 2013 (UTC)
I'm somewhat aware of these issues (though not an expert by any means) and that's why I suggested "skos:exactMatch" rather than "owl:sameAs". A good reference for this is the SKOS Primer (search in-page for "owl:sameAs"). I agree with what I read of @Markus Krötzsch: comments that you pointed me to, and I'd note that his last comment suggests that a vague "same as" property would be useful. skos:exactMatch is just what is called for, IMO. As it says in the SKOS primer, it is provided to "map concepts with equivalent meaning". I'll leave a comment over there, because I think that it would be more than just useful. If Wikidata is going to be incorporating other ontologies, such as this one, it seems to me it would be really critical that each term be properly linked back to it's origin, so as to maximize the power of linked data (and make true federated queries possible).
As to my less-interesting point, suggesting reverting to "transmitted by" -- I retract it. Klortho (talk) 05:05, 19 December 2013 (UTC)
Okay, I'm stumped. I clicked "save" on my last comment too soon, before I realized that the discussion you linked to, about the proposed "same as" property, was already archived, and has the note, "done as 'described at URL'". But now, I can't seem to find any such property as "described at URL". The closest I can find is said to be the same as (P460), which as an alias "same as", and a description "this item is said to be the same as that item, but the statement is disputed" -- all of which strikes me as horribly ambiguous and useless. Klortho (talk) 05:21, 19 December 2013 (UTC)

Discussion break

Votes are still missing so lets recap with a few examples.

  • transmission process = (im not sure in this case? maybe:vehicle-borne ingestion)
  • tuberkolosis
  • transmission process = airborne
Notified participants of WikiProject Medicine, @Emw:. To stay more compatible with Semanticweb we could also make all three properties regular statements (without any property beeing a qualifier). --Tobias1984 (talk) 20:54, 4 January 2014 (UTC)
Tobias, I think it would be much better to put the information that is in qualifiers above on a specific 'transmission process' class. If more classes are needed, then I think it makes sense to put that information in a class. For example, instead of:
I would create a class 'Anopheles-borne transmission', which is a subclass of mosquito borne transmission (Q15304532) and a superclass of Anopheles gambiae borne transmission (Q15304534), and put the claims that appear as qualifiers above as non-qualified claims of the new 'Anopheles-borne transmission' class. (Why not mosquito borne transmission (Q15304532)? Because perhaps a pathogen is transmitted by multiple species of Anopheles, not just Anopheles gambiae, and not any other species of Anopheles's parent taxon Culicidae. 'Mosquito' is a broad term that applies to any member of Culicidae.)
The underlying reason I prefer new classes to qualifiers is because qualifiers are not supported in W3C standards, and so will likely not be very usable in queries or inference engines. Emw (talk) 23:07, 5 January 2014 (UTC)
@Emw: I can see that these classes would have advantages. Could we use the qualifiers additionally (even if some redundancy would be created)? Im also having trouble which class would be more useful 'Anopheles-borne transmission' or 'mosquito-borne transmission of plasmodium' or 'anopheles-borne transmission of plasmodium'. --Tobias1984 (talk) 23:45, 5 January 2014 (UTC)
 Support. I think best practices can be refined as needed after creating this property. Bluerasberry, Daniel Mietchen, Klortho, others, please support or oppose this property. If noone opposes it by 00:00 UTC Tuesday, then I will create it. If anyone else wants to create the property before then, I would not object. Emw (talk) 23:17, 5 January 2014 (UTC)
 Support I'd still prefer the property to be called "pathogen transmission process" rather than "transmission process" or at least to refer to pathogens (rather than disease) in its description, but I agree it's about time to actually create it. Besides, I am wondering whether we should think about the distinction between the respective transmissions of pathogens and diseases here. --Daniel Mietchen (talk) 23:40, 5 January 2014 (UTC)
Daniel, good point. I support distinguishing between pathogen and disease: influenza != influenza virus. I have updated the title of the proposed property from "transmitted by" to "pathogen transmission process" to reflect that (diff). (I've also updated the examples to reflect discussions above.) Tobias or anyone else, if you object to any of those changes, please feel free to summarily revert or change. Emw (talk) 00:47, 6 January 2014 (UTC)
 Support I agree that it is time to go ahead and created it. However, in rereading the discussion above, and with a little more understanding of the Wikidata data model, I have a lot of concerns about the qualifier vs subclass discussion above (at the top of "Discussion break" here). First off, it seems to me that the pathogen transmission (Q525512) hierarchy already presupposes the "subclass" model, because the subtree under "vector borne" already has a hierarchy based on biological taxonomy. And that's where my concern is: it seems to me if you go this route, then you're asking the people creating these properties to recapitulate the biological taxonomy tree here, and that violates DRY, and would be very error-prone. Whereas, if you stopped at vector-borne transmission (Q15304520), and then used qualifiers to point to the organism(s) that serve as vectors, it would be cleaner. I don't agree that "qualifiers are not supported in W3C standards". For example, using a blank node, I think you could define the qualified relation above as (something like):
:malaria :transmission-process [ rdfs:subClassOf vector-borne transmission (Q15304520) , :parasite Plasmodium (Q130948) ]
Klortho (talk) 03:08, 6 January 2014 (UTC)
Klortho, in RDF and OWL, a property is a binary relation. Qualifiers transform properties into n-ary relations, which are not supported in W3C standards. There are ways to shoehorn n-ary relations into binary relations via "property reification", but no W3C recommendations describe a standard way to do so. The best we have is a non-normative, non-standard W3C working group note on the subject: Defining N-ary Relations on the Semantic Web. Q&A resources like Which type of reification do you use?, Avoid Reification? Other "bad" features?, Why is it difficult to use a reasoner on RDF reification? all convey the gist that reification techniques are generally all over the map and best to use in only a very minimal way, e.g. to capture information like when a statement was made and by whom -- for provenance and sourcing.
I totally agree that we should not be recapitulating the full biological taxonomic tree in these classes. In practice I think the broad classes that exist now will be enough expressive power for a while. Emw (talk) 04:59, 6 January 2014 (UTC)
I moved this discussion here, if anyone is interested. Klortho (talk) 14:22, 11 January 2014 (UTC)
 Support I am doing my best to understand this and the standing proposal seems well organized beyond what I anticipated. I am aware of nothing preventing the creation of this property and the benefits to doing so seem evident. Blue Rasberry (talk) 22:12, 6 January 2014 (UTC)
 Support proposition of Tobias1984 with qualifers for further details. Hope that the above tree can covered most cases. Snipre (talk) 22:51, 6 January 2014 (UTC)

deity of

   Done: worshipped by (P1049) (Talk and documentation)
Descriptionlinks to the religion, mythology or culture that worships this deity
Data typeItem
Template parameter"major deities" in en:template:infobox religion
Domainreligion (unsorted)
ExampleAhura Mazda (Q179575) => Zoroastrianism (Q9601) / Yemaja (Q1477162) => Yoruba religion (Q1086440) / Zeus (Q34201) => Ancient Greek religion (Q855270)
Proposed byPikolas (talk) 22:09, 1 September 2013 (UTC)

Pikolas (talk) 22:09, 1 September 2013 (UTC)

 Support. I've reworded the description a little as this property shouldn't 'list the ...deities'. It should link to one deity. If there are more than one deity then each should get a link using this property.  – The preceding unsigned comment was added by Filceolaire (talk • contribs).
 Support I have "inverted" this property because the number of deities is much larger than the number of religions, therefore it makes sense to link the deity to the religion an query how many deities belong to a religion in particular. With this, if there is no opposition, I think the property is ready for creation.--Micru (talk) 17:32, 23 November 2013 (UTC)
 Support -- Yiyi .... (talk!) 07:58, 25 November 2013 (UTC)
✓ Done @Pikolas, Filceolaire, Yiyi, Micru: --Jakob (Scream about the things I've broken) 14:44, 6 December 2013 (UTC)

Instruction Set

DescriptionInstruction Set which the CPU is compatible
Data typeItem
ExampleAtom D2700 (Q15220335): 64-bit computing (Q252132)
SourceIntel website, for Intel processors
Robot and gadget jobsRobots can gather info on the Intel website and fill the property with it.
Proposed byMisterSanderson (talk)

I want to add information to the CPU items, but there aren't enough properties to that. MisterSanderson (talk)

 Comment I would change the datatype to item. We have 64-bit computing (Q351893) and 32-bit computing (Q225147). That way no translation is needed. --Tobias1984 (talk) 10:26, 24 November 2013 (UTC)
Agree. Changed.--MisterSanderson (talk) 13:56, 24 November 2013 (UTC)
 Support --Tobias1984 (talk) 07:51, 25 November 2013 (UTC)

Publishing date

readable file format

Descriptionspilt from above.
Data typeItem
ExampleAdobe Photoshop (Q129793)=>JPEG (Q2195) and others
Proposed byGZWDer (talk) 12:15, 26 December 2013 (UTC)
 Support --Tobias1984 (talk) 22:50, 27 December 2013 (UTC)
 Support --Konggaru (talk) 16:37, 3 January 2014 (UTC)
 Support Danrok (talk) 15:24, 5 January 2014 (UTC)
 Support NaBUru38 (talk) 18:59, 12 January 2014 (UTC)

writable file format

Descriptionspilt from above.
Data typeItem
ExampleAdobe Photoshop (Q129793)=>JPEG (Q2195) and others
Proposed byGZWDer (talk) 12:15, 26 December 2013 (UTC)
 Support --Tobias1984 (talk) 22:50, 27 December 2013 (UTC)
 Support --Konggaru (talk) 16:59, 3 January 2014 (UTC)
 Support Danrok (talk) 15:25, 5 January 2014 (UTC)
 Support NaBUru38 (talk) 19:00, 12 January 2014 (UTC)

KOATUU identifier

   Done: KOATUU ID (P1077) (Talk and documentation)
DescriptionUnique code for each of the Ukrainian administrative units, i.e. oblast, raion, city under state jurisdiction and city under municipality jurisdiction. Based on the Classification of objects of the administrative-territorial system of Ukraine (Q1564708).
Data typeString
Domaininstances of administrative territorial entity of Ukraine (Q203323)
Allowed values9 or 10 digits
ExampleKoktebel (Q1743602) => 111645700
Sourceuk-Wikipedia infoboxes, database [3]
Robot and gadget jobsCould be imported from the uk-Wikipedia infoboxes (uk:Шаблон:Смт код КОАТУУ etc.). Building a bot myself for setting all the missing statements in the administrative entities items.
Proposed byVoll (talk)
 Support --Tobias1984 (talk) 07:18, 13 January 2014 (UTC)

department (qualifier)

Superceeds 'Expenditure by department' above.

Descriptionqualifier for the 'expenditure' property
Data typeItem
Template parameter"Expenditure by department"
DomainCountry, region and city articles for the Global Economic Map. Company articles
Allowed valuesnumber (currency)
Example 1MISSING
Example 2MISSING
Example 3MISSING
Robot and gadget jobsBots should be doing this task
Proposed byFilceolaire (talk) 20:56, 6 November 2013 (UTC)
Withdrawn. We can use 'applies to part (P518)' for this. Filceolaire (talk) 01:14, 14 December 2013 (UTC)

UN pictogram

 Comment A dangerous substance has an ADR classification, e.g. sodium azide (Q407577) = 6.1 and this classification has a symbol, e.g., 6.1 = file:ADR 6.1.svg. Thus, create items for each class and change the datatype of the proposed property to item. Each of these items then has a pictogram using simply image (P18).  — Felix Reimann (talk) 21:57, 25 August 2013 (UTC)

Human Development Index

DescriptionHuman Development Index value of country.
Data typeNumber (not available yet)
Template parameteren:Template:Infobox country HDI
Allowed values0 ≤ HDI ≤ 1
ExampleNorway → 0.955, with qualifier <as of> → 2012
Proposed byKwj2772 (talk)

Kwj2772 (talk) 06:54, 5 May 2013 (UTC)

Egyptian Universities Library (EUL)

   Done: EUL editions (P1084) (Talk and documentation)
DescriptionCatalogue number for books (editions) in the Egyptian union catalog.
Data typeString
Allowed valuesnumeric string
ExampleMiguel Ángel Asturias Rosales (Q75603): Los ojos de los enterrados (1982 edition). Control number: 11403819
SourceEgyptian Universities Library (EUL): Union catalog
Proposed byKolja21 (talk)

Important union catalog. (We should not only focus on European and US libraries.) --Kolja21 (talk) 15:31, 20 January 2014 (UTC)

LibraryThing work identifier

DescriptionID specifying an equivalent bibliographic work in the LibraryThing (Q742640) catalog
Data typeString
Template parameterfirst parameter in de:Vorlage:LibraryThing
Domainall books as creative works
Allowed valuesnumeric string (e.g. 337646)
ExampleThe 13½ Lives of Captain Bluebear (Q786908) => 337646
Format and edit filter validationmust be numeric
Robot and gadget jobs(semi-)automatic creation is possible given the LibraryThing API and links from LibraryThing works to Wikipedia articles
Proposed byJakobVoss (talk)

LibraryThing contains valuable information about bibliographic works, such as editions, authors, awards and much more. LibraryThing Common Knowledge is a kind of Freebase or Wikidata specialized for data about books. Both, Wikidata and LibraryThing would benefit a lot from a mapping. JakobVoss (talk) 19:56, 19 January 2014 (UTC)

 Support Gerne auch LibraryThing Autor-ID. --Kolja21 (talk) 23:37, 19 January 2014 (UTC)
 Support Yes, LibraryThing Author-ID could also be interesting. — Finn Årup Nielsen (fnielsen) (talk) 18:44, 22 January 2014 (UTC)
 Support - Husky (talk) 16:46, 30 January 2014 (UTC)

atomic number

   Done: atomic number (P1086) (Talk and documentation)
DescriptionThe w:atomic number of a chemical element
Data typeNumber (not available yet)
Template parameter"atomic number" in w:Template:Infobox element
Domainterms (chemical elements)
Allowed values1+
Examplehydrogen (Q556) - 1 barium (Q1112) - 56 oganesson (Q1307) - 118
Robot and gadget jobsA bot could help, but it is not a necessity, since there are under 150 items where this would be used, so a single human could probably do it in under an hour.
Proposed by--Jakob (Scream about the things I've broken) 17:48, 30 July 2013 (UTC)
 SupportSnipre (talk) 18:16, 30 July 2013 (UTC)
 Strong support --Tobias1984 (talk) 09:14, 31 July 2013 (UTC)
 Support TCN7JM 12:30, 6 August 2013 (UTC)
 Support LucaBiondi (talk) 12:35, 18 August 2013 (UTC)
 Support Mcnabber091 (talk) 23:15, 28 August 2013 (UTC)

Elo rating / Elo-Zahl / Points ELO

Status:    Done



DescriptionΤhe seating capacity of the venue. (we already have home venue)
Data typeNumber (not available yet)
Template parameteren:template:Infobox stadium capacity
Allowed values0-120000
SourceExternal reference, Wikipedia list article
Robot and gadget jobsthey should be allowed
Proposed byXaris333 (talk) 19:06, 5 May 2013 (UTC)
 Support --Чаховіч Уладзіслаў (talk) 12:57, 19 May 2013 (UTC)
This definitely needs a more specific name, in my opinion. --Yair rand (talk) 10:32, 6 June 2013 (UTC)
 Support but agree it should be renamed seating capacity so it is clear that it is a counter of the number of people a venue (or other item with limited seating) can hold. Joshbaumgartner (talk) 20:26, 12 October 2013 (UTC)


   Done: population (P1082) (Talk and documentation)
Descriptionnumber of people inhabiting the country
Data typeQuantity
Template parameteren:Infobox French commune (population + population date)
Domaingeographic features: places

  • I agree, "population" typically needs further clarification. It also needn't be restricted to census results. Statistical organisations regularly publish population estimates, based on other demographic indicators as well as census data. Historical populations may be derived from other sources too.--Avenue (talk) 10:02, 5 February 2013 (UTC)
  • No, but I don't think that's the right question. Areas are a better domain for human populations than places. (There are a few items with population data that aren't what I'd think of as an area, e.g. prisons, but they can be allowed as exceptional cases.) --Avenue (talk) 13:43, 9 February 2013 (UTC)
I suggest to add also parameters 'Year of census/estimation' and 'Population source' for link to population data. And also we may add 'Area' and 'Density' where density will calculate as Round(Population/Area,2).--Ahonc (talk) 10:03, 9 February 2013 (UTC)
Year is not fine-grained enough; population estimates are released where I live every quarter. Some population figures are given as the average over a certain period (often a year); others are as at a certain date. A field holding details of the population recorded (who is counted, and how) is needed too.--Avenue(talk) 13:43, 9 February 2013 (UTC)

 Support This should apply to administrative divisions, not just cities, where a census result is available. Danrok (talk) 04:53, 27 February 2013 (UTC)

  •  Support --Ahonc (talk) 22:48, 6 March 2013 (UTC)
  •  Oppose. Too generic. If it's a population for a certain year, there should be a mechanism to supply the year (as well as whether this is an estimate, census, etc.). If it is the most recent known population, it should be named accordingly (and knowing the year for which the population is reported would also be beneficial).—Ëzhiki (Igels Hérissonovich Ïzhakoff-Amursky) • (yo?); March 8, 2013; 19:27 (UTC)
I agree all these details should eventually be recorded, along with their sources. But we have created many properties despite the current lack of mechanisms for recording vital qualifying details (or sources) about the data they record, so I don't see why we can't do the same here. Would you prefer separate properties for population estimates and census figures? --Avenue (talk) 08:35, 13 March 2013 (UTC)
My preference would actually be to wait until the qualifiers are implemented, before implementing more properties the sole purpose of which seems to be making up for the absence of support for the qualifiers. I understand that we already have some such properties in place, and they were necessary in order for Phase II to have any kind of meaning, but I don't believe we should continue piling them up.—Ëzhiki (Igels Hérissonovich Ïzhakoff-Amursky) • (yo?); March 13, 2013; 18:20 (UTC)
I just found Q2062405 who is the name of two statistical areas. One urban area (tätort) and one "Dispersed settlement" (småort). They are located just next to each other, but the computers who work at Statistics Sweden prefer to refer to them as two different settlements. The Swedish article related to this item refers both the to the tätort and the småort. We would in cases like this need to have two different numbers for each of the settlements. And in cases when the urban area is located in more than one municipality to have separate numbers for each municipality together with the sum of all of the settlement. -- Lavallen (block) 09:40, 11 March 2013 (UTC)
 Comment, I removed the reference of the census, as there may be other sources, especially for historical data.

Mohs' hardness

   Done: Mohs' hardness (P1088) (Talk and documentation)
DescriptionMohs hardness
Data typeNumber (not available yet)
Template parameter"Mohs hardness" in w:Template:Infobox element, "mohs" in w:Template:Infobox mineral
Allowed valuesany solid substance
Examplediamond (Q5283) - 10 talc (Q134583) - 1
Source[4], [5]
Proposed by--Jakob (Scream about the things I've broken) 01:20, 5 August 2013 (UTC)
 Support - needs qualifier for crystal face and scratching direction. --Tobias1984 (talk) 09:14, 5 August 2013 (UTC)
 SupportSnipre (talk) 21:21, 7 August 2013 (UTC)
 SupportLucaBiondi (talk) 12:38, 25 August 2013 (UTC)
 Support Emw (talk) 03:11, 15 October 2013 (UTC)
 Support Macadamia1472 (talk) 08:30, 16 October 2013 (UTC)

Orbital eccentricity

DescriptionThe eccentricity of an orbit.
Data typeNumber (not available yet)
Template parameteren:Template:Infobox planet eccentricity
DomainAll orbiting objects.
Proposed byMER-C (talk) 13:37, 11 February 2013 (UTC)
 Support --Paperoastro (talk) 00:41, 14 February 2013 (UTC)
 Support --Nicolas M. Perrault (talk) 20:51, 24 March 2013 (UTC)

Total produced

   Done: total produced (P1092) (Talk and documentation)
DescriptionHow many made?
Data typeNumber (not available yet)
Template parameterput Wikipedia infobox parameters here. If existing, sample: "Total produced" in en:template:infobox locomotive
SourceExternal reference, Wikipedia list article (either infobox or source)
Proposed byB.Zsolt (talk) 14:32, 12 July 2013 (UTC)


   Done: redshift (P1090) (Talk and documentation)
Descriptionthe redshift of an astronomical object.
Data typeNumber (not available yet)
Template parameterTemplate:Infobox galaxy z
Domainastronomical object (Q6999) outside the Solar System
Example<Messier 82 (Q14026)> redshift <0.000677 ± 0.000013>
Sourcereferred articles, astronomical databases as SIMBAD (Q654724) and NASA/IPAC Extragalactic Database (Q488563)
 Support --Paperoastro (talk) 11:26, 9 February 2013 (UTC)
 Comment also stars have redshift measurements (see this example): this property can be useful also for them, or alternatively a new property for the Radial velocity of stars can be created. --Paperoastro (talk) 11:26, 9 February 2013 (UTC)
 Support -- MichaelSchoenitzer (talk) 01:19, 9 February 2013 (UTC)

gross tonnage

   Done: gross tonnage (P1093) (Talk and documentation)
DescriptionGross tonnage (GT) is a unitless index related to a ship's overall internal volume.
Data typeNumber (not available yet)
Proposed by18


   Done: g-factor (P1097) (Talk and documentation)
DescriptionCharacteristic property of any elementary particle (Lande factor)
Data typeNumber (not available yet)
Examplede:Vorlage:Infobox Teilchen
Proposed bySvebert (talk) 21:02, 15 March 2013 (UTC)
 Support -- MichaelSchoenitzer (talk) 16:03, 21 March 2013 (UTC)
 Support clearly defined statistical value. Joshbaumgartner (talk) 06:51, 13 May 2013 (UTC)


   Done: flattening (P1102) (Talk and documentation)
DescriptionThe flattening of a spherical body.
Data typenumeric-invalid datatype (not in Module:i18n/datatype)
Template parameteren:template:Infobox planet flattening
Domainany astronomic spherical object (astronomical object (Q6999))
Allowed values0 < flattening < 1
Example<Earth (Q2)> flattening <0.0033528>
Proposed by--Paperoastro (talk) 14:25, 9 February 2013 (UTC)


Descriptionnumber of masts
Data typeNumber (not available yet)

number of cylinders

Descriptionquantity of cylinders utilized in a piston engine design
Data typeNumber (not available yet)
Domainpiston engines
Allowed valuespositive integers
ExampleGnome-Rhône Mistral Major (Q902691) => number of cylinders => 14
Proposed byJoshbaumgartner (talk) 07:02, 2 October 2013 (UTC)
 Support This is a common data point for engine specs. Joshbaumgartner (talk) 07:02, 2 October 2013 (UTC)
 Support LucaBiondi (talk) 16:41, 7 October 2013 (UTC)


DescriptionThe electronegativity of a chemical element
Data typeNumber (not available yet)
Template parameter"electronegativity" in w:template:infobox element
Domainterms (chemical elements)
Examplehydrogen (Q556) - 2.2 francium (Q671) - 0.7 fluorine (Q650) - 3.98
SourceCRC HAndbook of chemistry and physics
Robot and gadget jobsProbably not needed since the property would (currently) be used on about 100 items
Proposed by--Jakob (Scream about the things I've broken) 12:16, 17 July 2013 (UTC)

Refractive index

Descriptionrefractive index of a substance with wavelength and temperature as qualifiers
Data typeNumber (not available yet)
Template parameteren, fr and de infoboxes about chemicals
Examplesee Wikidata:Chemistry_task_force/Properties.
Proposed byGZWDer (talk) 03:07, 7 June 2013 (UTC)
 Support Snipre (talk) 12:09, 7 June 2013 (UTC)
 Support --Kaligula (talk) 07:06, 19 June 2013 (UTC)
 Support--Saehrimnir (talk) 15:46, 24 June 2013 (UTC)


   Not done
DescriptionA child by marriage, but not a biological child; inverse of P43 (P43)/ P44 (P44).
Data typeItem
Template parameter"children" in en:template:infobox person and others.
ExampleClark Gable (Q71243) => Bunker Spreckels (Q15302241))
Proposed byAndy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits

More precise subset of "Child". Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 14:05, 12 December 2013 (UTC)

If I understand correctly, this is not a subset of "child" at all, and it's redundant data that can already be deduced from other properties.  Oppose. --Yair rand (talk) 23:29, 12 December 2013 (UTC)
I know someone with three children; two biological and one a step child. So no, you do not understand correctly, and "stepchildren" are a subset of "children". From which other properties do you think this relationship can be deduced? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 00:02, 13 December 2013 (UTC)
I've understood child (P40) to be specifically for the biological relationship. That some cultures may associate certain other relations as being socially equivalent has no bearing on the property's use in Wikidata, I would think. Stepchild relationship can be determined via the spouse and child properties, without any other statements needing to be added. --Yair rand (talk) 22:31, 15 December 2013 (UTC)
There is no reference in the description of P40 to it being limited to biological children; nor does common practice seem to reflect that. Often, we have no way of knowing. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 17:14, 21 December 2013 (UTC)
  •  Oppose Since in many cases we don't know if a daughter is a step-daughter, a daughter-in-law, an adopted daughter, a daughter via surrogate mother, a daughter via sperm or egg donor, etc. I think it is better to use 'child' for all of these with a qualifier where we have more specific information. The ambiguity in the property accurately reflects our lack of specific information. Filceolaire (talk) 14:06, 23 December 2013 (UTC)
 Oppose I feel this should be done via child with the qualifier of adopted
Jared Zimmerman (talk) 18:43, 16 January 2014 (UTC)
 Oppose see above--Oursana (talk) 22:31, 28 January 2014 (UTC)
 Not done --Tobias1984 (talk) 17:44, 31 January 2014 (UTC)

launch contractor

DescriptionCompany that launched the rocket.
Data typeItem
Template parameterInfobox space flight: launch_contractor
Allowed valuescontractors
ExampleGaia (Q767805) = Arianespace (Q309867)
Format and edit filter validationsubclass of company?
Sourcetechnical sources
Proposed by--Tobias1984 (talk) 17:40, 19 December 2013 (UTC)

OKTMO identifier

   Not done
Descriptioncode by Russian Classification on Territories of Municipal Division (similar to OKATO ID (P721))
Data typeString
Template parameterru:Шаблон:Сельское поселение ОКТМО, ru:Шаблон:Городское поселение ОКТМО
Domaininstances of administrative territorial entity of Russia (Q192287)
Allowed values8 or 11 digits
ExamplePlyos (Q179486) =>
Sourceruwiki infoboxes, open database by Federal State Statistics Service of Russian Federation [6]
Robot and gadget jobsI'm planing to write a bot to fill this property
Proposed byAlexander Sigachov (talk)

It's a bit confusing, but we use two geographical code systems in Russia: administrative and municipal. We have OKATO ID (P721) for administrative division, but property for municipal code is absent. Alexander Sigachov (talk) 11:52, 29 January 2014 (UTC)

Canceled. It's OKTMO ID (P764) --Alexander Sigachov (talk) 14:54, 29 January 2014 (UTC)

Chemical synthesis

   Not done
Descriptionthe name of the synthesis or the general synthesis process
Data typeItem
Template parameter?
Domainall chemicals
Allowed valuessynthesis methods
rifamycin (Q388565): chemical synthesis = biosynthesis (Q851162) & qualifier for bacteria = Amycolatopsis mediterranei (Q14640883)
ammonia (Q4087): chemical synthesis = Haber-Bosch process (Q213669)
aluminium oxide (Q177342): chemical synthesis = Bayer process (Q248670)
Format and edit filter validation?
Sourcescientific literature
Proposed by--Tobias1984 (talk) 09:56, 24 December 2013 (UTC)

Pinging relevant people:

Egon Willighagen
Denise Slenter
Daniel Mietchen
Emily Temple-Wood
Pablo Busatto (Almondega)
Antony Williams (EPA)
Devon Fyson
Samuel Clark
Tris T7
Robert Giessmann
Cord Wiljes
Adriano Rutz
Jonathan Bisson
Charles Tapley Hoyt
Peter Murray-Rust

Notified participants of WikiProject Chemistry,

Doc James
Daniel Mietchen
Andrew Su
Pavel Dušek
Chris Mungall
Netha Hussain
Abhijeet Safai
Shani Evenstein
ZI Jony
The Anome
Ameer Fauri

Notified participants of WikiProject Medicine, @Emw: --Tobias1984 (talk) WikiProject Molecular biology has more than 50 participants and couldn't be pinged. Please post on the WikiProject's talk page instead. 09:57, 24 December 2013 (UTC)

 Oppose we have already the property product or material produced or service provided (P1056) which can be used like this Haber-Bosch process (Q213669) product or material produced or service provided (P1056) ammonia (Q4087). This is the inverse property of the proposed one and if we have one relation we can retrieve all of them by a query instead of managing for all chemicals and processes the double relationships. Snipre (talk) 15:15, 28 December 2013 (UTC)
That is an interesting suggestion and I can't think of any disadvantages it would have. --Tobias1984 (talk) 15:21, 28 December 2013 (UTC)
+1 --Leyo 19:24, 5 January 2014 (UTC)
Agreed, good point Snipre. Emw (talk) 19:26, 5 January 2014 (UTC)

Electrical resistance

   Not done
Descriptionopposition to the passage of an electric current through
Data typeNumber (not available yet)
Domainall nonnegative numbers
Exampleohm (Q47083)
Proposed byTeleComNasSprVen (talk)

Motivation. TeleComNasSprVen (talk) 12:52, 27 December 2013 (UTC)

 Oppose - Already pending (link) --Tobias1984 (talk) 22:35, 27 December 2013 (UTC)
Hm, how bout electrical current and energy in joules? TeleComNasSprVen (talk) 02:54, 28 December 2013 (UTC)
Didn't find those two, but until the numeric datatype appears, it doesn't make much sense discussing the properties. The problem is that we don't know how units and SI-prefixes will work and to which units a property can be constrained. Those topics will require all proposals to be rediscussed in January or February 2014. --Tobias1984 (talk) 09:07, 28 December 2013 (UTC)
 Oppose per Tobias1984, and also, I can't see that, the way this is written, it makes any sense. The domain is given as "all nonnegative numbers". How does it make sense for a number to have an electrical resistance? And, if that's a mistake, and the domain really should be "substances", then this should be something more like resistivity than resistance. Klortho (talk) 13:01, 30 January 2014 (UTC)


   Not done
DescriptionA method that a particular disease may be treated with.
Data typeItem
Domaindisease (Q12136), (items related to wikipedia category Category:Diseases and disorders (Q7215431))
Allowed valuesinstances of chemical compound (Q11173)/drug (Q8386), surgical procedures, psychotherapy (Q183257)/physiotherapy (Q186005)/occupational therapy (Q380141) (or their types, to be more precise)
ExampleParkinson's disease (Q11085)levodopa (Q300989)), Parkinson's disease (Q11085)deep brain stimulation (Q618076), colorectal cancer (Q188874)colectomy (Q1779148) with type = causal, colorectal cancer (Q188874)colostomy (Q595453) with type = symptomatic
Sourcemedical literature, wikipedia articles
Proposed byPavel Dušek (talk)

Such as symptoms, medical conditions usually have their appropriate treatments. Since there is a symptoms and signs (P780) property, I find it quite useful to have also a therapy/treatment property. (For names in other languages, see medical treatment (Q179661)). --Pavel Dušek (talk) 22:10, 7 January 2014 (UTC)

 Question do you think that possible treatment (P924) could be used and "therapy2 added as a alias? Here is a overview of medical properties Wikidata:WikiProject_Medicine/Properties. You might be interested to join the WikiProject at Wikidata:WikiProject_Medicine. --Tobias1984 (talk) 07:32, 8 January 2014 (UTC) @Pavel Dušek: --Tobias1984 (talk) 10:52, 9 January 2014 (UTC)
Thank you for the notification — I missed the existence of the possible treatment (P924) property. Sorry about that. I think it would be appropriate to add "therapy" as an alias, if it is possible. I would be glad to join the WikiProject Medicine. --Pavel Dušek (talk) 11:08, 9 January 2014 (UTC)
Added the alias in English and German. I added you to the list of participants at Wikidata:WikiProject_Medicine and to the "ping project" list. --Tobias1984 (talk) 11:21, 9 January 2014 (UTC)

 Not done --Tobias1984 (talk) 11:50, 2 February 2014 (UTC)

ATVK identifier

   Done: ATVK ID (P1115) (Talk and documentation)
DescriptionUnique code for each of the Latvian administrative units, i.e. municipality, parish, city under state jurisdiction and city under municipality jurisdiction. Based on the Latvian Classification on Objects of Administrative Division (Q15621843).
Data typeString
Domaininstances of administrative territorial entity of Latvia (Q750277)
Allowed values7 digits
ExampleBauska Municipality (Q2365998) => 0400200
Robot and gadget jobsCould be imported from the source.
Proposed byVoll (talk)
 Support --Tobias1984 (talk) 07:18, 13 January 2014 (UTC)

✓ Done --Tobias1984 (talk) 11:54, 2 February 2014 (UTC)

Kallikratis geographical code

DescriptionKalikratis geographical code is one assigned by the National Statistics Authority of Greece to each administrative unit at all levels (from regions to settlements). The "Kallikratis" refers to the newest administrative division of Greece (after 2010) known as Kallikratis Plan, disambiguated from the older "Kapodistrias" administrative division (where the administrative units had other codes and we will need another property).
Data typeString
ExampleThessaloniki (Q17151) => 0701010001 , Kavala Municipality (Q12282294) => 0501, Kavala (Q187352) => 0501010101
Format and edit filter validation2 to 10 numerical digits
Source[8] [9] [10]
Proposed bygeraki talk

Motivation. geraki talk 09:27, 25 January 2014 (UTC)

 Support. -- Lavallen (talk) 10:47, 25 January 2014 (UTC)
 Support. -- GerardM (talk) 08:13, 1 February 2014 (UTC)

✓ Done --Tobias1984 (talk) 12:09, 2 February 2014 (UTC)

votes received

   Done: votes received (P1111) (Talk and documentation)
Descriptionnumber of votes candidate received in subject election
Data typeNumber (not available yet)
Domainelections for specific offices
Allowed valuespositive integers
Examplew:en:United States presidential election, 2012 candidate w:en:Mitt Romney votes received 206
Robot and gadget jobsallowed
Proposed byJoshbaumgartner (talk) 05:10, 13 May 2013 (UTC)
 Info This is a qualifier for candidates, providing the quantity of total votes recieved. The type of votes should be the type officially counted to determine the winner, so in the case of the US presidential election, it would be electoral votes. Joshbaumgartner (talk) 05:10, 13 May 2013 (UTC)
 Support --Nightwish62 (talk) 19:00, 29 July 2013 (UTC)


   Done: pKa (P1117) (Talk and documentation)
DescriptionХимический показатель (ru) – (Please translate this into English.)
Data typeNumber (not available yet)
Template parameteren, fr and de infoboxes about chemicals
Examplesee Wikidata:Chemistry_task_force/Properties.
Proposed byGZWDer (talk) 03:07, 7 June 2013 (UTC)
 Support Snipre (talk) 12:09, 7 June 2013 (UTC)
 Support --Kaligula (talk) 07:06, 19 June 2013 (UTC)
 Support--Saehrimnir (talk) 15:46, 24 June 2013 (UTC)

✓ Done --Tobias1984 (talk) 12:27, 2 February 2014 (UTC)

Number of speakers

Descriptionnumber of speakers
Data typeNumber (not available yet)
Template parameter"speakers" in w:en:Template:Infobox language
Domainlanguages, language families (?)
ExampleWelsh (Q9309) -> 720,000 (2004-2011, total), 560,000 (Wales (Q25), 2004-2006, total), 320,000 (Wales (Q25), 2004-2006, fluent only), 5,000 (Chubut Province (Q45007))
Sourcemany estimates on enwiki come from Ethnologue, particularly for languages with few speakers
Robot and gadget jobssimilar to above: bots can do well but not perfect
Proposed byKleptomaniacViolet (talk)

L1, L2, historical, geographical, etc stuff can be detailed with qualifiers. KleptomaniacViolet (talk) 16:40, 3 September 2013 (UTC)


   Done: proportion (P1107) (Talk and documentation)
Descriptionused as a qualifier. (contry to other quantity properties, I did not see any proposal about that, maybe because it is so obvious)
Data typeQuantity
Allowed valuesnumber between 0 and 1
Example(company X is 40 % owned by Y, Earth atmosphere is composed of 80% dinitrogen and 20% dioxygen)
Proposed byZolo (talk) 15:22, 16 August 2013 (UTC)

 Support Even if we cannot use it yet...--Micru (talk) 00:54, 17 August 2013 (UTC)

 Comment could be useful, but perhaps not for companies. In practice, ownership share can vary day-by-day. Danrok (talk) 14:47, 5 September 2013 (UTC)
It's normally only reported at the Q or annual reports, and larger owners normally stay for decades, or at least for some years. Daytraders are normally included in "others". -- Lavallentalk(block) 16:16, 5 September 2013 (UTC)
 Support I can see lots of places to use this as a qualifier. Filceolaire (talk) 17:21, 21 September 2013 (UTC)
 Support --Danrok (⧼-alkpagelinktext⧽) 18:34, 26 September 2013 (UTC)
@Micru, Danrok, Lavallen, Filceolaire: ✓ Done --Zolo (talk) 14:46, 31 January 2014 (UTC)

Pokédex Number

   Done: no label (P1112) (Talk and documentation)
DescriptionPokedex number
Data typeNumber (not available yet)
DomainAny Pokémon
Allowed valuesnumbers
Example<Bulbasaur> pokedex number <1> (qualifier National Pokédex)
SourceExternal reference, Wikipedia list article (either infobox or source)
Proposed byLegoktm

Saw the new Pokémon task force and was inspired :) Legoktm (talk) 12:59, 27 April 2013 (UTC)

 Support Ju gatsu mikka (talk) 13:55, 27 April 2013 (UTC)
 Support TiboF® 19:05, 27 April 2013 (UTC)
 Question: What do you mean by "(qualifier National Pokédex)"? What would be the property? You can't just make a qualifier out of an item, as far as I know. Also, shouldn't this be "Pokédex number", with an "é"? --Yair rand (talk) 17:12, 29 April 2013 (UTC)
I renamed it. --Ricordisamoa 17:45, 29 April 2013 (UTC)
The "National Pokédex" is opposed to "Regional Pokédex" (Kanto Pokédex, Johto Pokédex, Hoenn Pokédex, etc.). "Regional Pokédex" are composed only of Pokémon naturally catchable in those regions and reorganised the numbers of each Pokémon. "National Pokédex" is composed of every single Pokémon. Ju gatsu mikka (talk) 18:43, 29 April 2013 (UTC)
I understand that, but a qualifier needs a property and a value. I assume "National Pokédex" is the value, but what would the property be? "National Pokédex" alone can't be a qualifier. --Yair rand (talk) 21:47, 30 April 2013 (UTC)
No, the value will be a number (from 1 to 649 for now, but for Christmas there will be more). The property will be "Pokébex number" with "National Pokédex" (and eventually "Kanto Pokédex", "Johto Pokédex", "Hoenn Pokédex", "Sinnoh Pokédex", "Unova Pokédex", "Fiore Pokédex", "Almia Pokédex" and "Oblivia Pokédex") as a qualifier. Ju gatsu mikka (talk) 06:35, 1 May 2013 (UTC)
I'm apparently not explaining myself very clearly. Please take a look at File:Wikidata statement.png. Each qualifier has two parts, one of which functions like a property, and one of which functions as a value. (In the linked image, the first qualifier's property part is "as of" and its value is "2011", separate from the claim's value of 3500000 and its property "Population".) "National Pokédex" by itself can't be a full qualifier. If "National Pokédex" is to be the property part of the qualifier, then it needs an associated value, separate from the value for the main claim. If it is to be the value part of the qualifier, then it needs an associated property for the qualifier. --Yair rand (talk) 06:58, 1 May 2013 (UTC)
I think it would be overkill to create a separate property just to differentiate between Pokédex's, make we can use "stated in" --> "National Pokédex"? Legoktm (talk) 21:46, 1 May 2013 (UTC)

number of items in series

Descriptionthe number of items in a series
Data typeNumber (not available yet)
Domainitems that that are used as the object for Property part of the series (P179)
Allowed valuesnon-negative integers
ExampleThe Simpsons (Q886)
SourceWikipedia episode lists
Robot and gadget jobsnone
Proposed byMorten Haan (talk)

Some episode numbers are used in several Wikipedia articles (series article and corresponding episode list. In some cases templates are used but it's no good source code style to put templates in the middle of a sentence. Morten Haan (talk) 14:14, 19 September 2013 (UTC)

  •  Support but the name should be more generic so that it could be used for the number of films in a movie series (e.g. "8" for Harry Potter) or even the number of books in the same series, the number of tracks in a music album, etc. Also, the data type should be Number rather than String.--Underlying lk (talk) 18:09, 19 September 2013 (UTC)
    We can call it number of items but then we need another property item type (or something similar) which says what kind of items are counted. You're right, the datatype should be Number, I didn't knew there was such a type. --Morten Haan (talk) 20:05, 19 September 2013 (UTC)
It could be 'number of items in the series'. P179 is used for anything from videogames to aircraft, but within a single item it should be unambiguous enough.--Underlying lk (talk) 23:50, 19 September 2013 (UTC)
 Comment I believe string is the correct data type for this situation, it's just a reference which, hypothetically, may not always be a number, e.g. 3a, 3b, etc. I think the number data type will be for numbers which are more mathematical. --Danrok (talk) 23:38, 26 September 2013 (UTC)
If this is a property for the total number of episodes a series had then 'number' is the appropriate datatype.
If this is a reference for particular episodes then 'string' is the appropriate datatype. Please amend the description to make it clear which property this is. Filceolaire (talk) 22:46, 26 September 2013 (UTC)
Total number of episodes was previously proposed: number of episodes It was opposed to some extent, based on an invalid reason in my view. Danrok (talk) 23:45, 26 September 2013 (UTC)
It's a property for the total number of episodes of a series, so the datatype should be number. The property can also be used for tracks of an album, books of a book series and similar item types. --Morten Haan (talk) 12:41, 2 October 2013 (UTC)
Description and datatype changed as discussion above.  Support as new description and type. Filceolaire (talk) 11:56, 10 October 2013 (UTC)


   Done: attendance (P1110) (Talk and documentation)
Descriptionnumber of people who (passively) follow an event
Data typeQuantity
Template parameter"attendance" in en:template:Infobox International Football Competition
Domainall kinds of events
Example1982 FIFA World Cup => "2109723 " ...
Proposed byKompakt (talk) 10:15, 12 May 2013 (UTC)

The property can be further specified using a qualifier to express the "type" of attendance (e.g. at the location/visitor, TV viewer,...)--Kompakt (talk) 10:15, 12 May 2013 (UTC)

 Support This seems a useful and clear data point for events. Joshbaumgartner (talk) 00:37, 13 May 2013 (UTC)
 Support could be used with date qualifiers to show the attendance for each year, for annual events. Danrok (talk) 13:20, 24 May 2013 (UTC)

highest singles ranking (en) / höchste Weltranglistenplatzierung im Einzel (de)

   Not done
Descriptionhighest ranking a tennis player has achieved during his career in the world singles ranking
Data typeNumber (not available yet)
Template parameter"highestsinglesranking" in en:Template:Infobox tennis biography
Domaintennis players
ExampleRafael Nadal (Q10132) => "1"
Proposed byKompakt (talk)
  •  Support. That's what I've been waiting for long. This is much needed, because in the past (and till now) many users have updated this actively only on en-wiki, and many Wikipedias are not up-to-date. And now when there is a centralised place to do this task, everything will be much easier. --Stryn (talk) 12:30, 16 June 2013 (UTC)
  •  Support. Agree with Stryn. Unfortunately, on the Dutch wikipedia some people are actively frustrating the use of data from Wikidata :-( -- Edoderoo (talk) 07:53, 18 June 2013 (UTC)
  •  Not done I did not create this because the highest ranking can be queried from a list of rankings with time qualifiers. I think this is the most compatible solution with our current data model. --Tobias1984 (talk) 12:59, 2 February 2014 (UTC)

current singles ranking (en) / aktuelle Weltranglistenplatzierung im Einzel (de)

   Done: no label (P1118) (Talk and documentation)
Descriptioncurrent ranking a tennis player has in the world singles ranking
Data typeNumber (not available yet)
Template parameter"currentsinglesranking" in en:Template:Infobox tennis biography
Domaintennis players
ExampleRafael Nadal (Q10132) => "5"
Proposed byKompakt (talk)

highest doubles ranking (en) / höchste Weltranglistenplatzierung im Doppel (de)

   Not done
Descriptionhighest ranking a tennis player has achieved during his career in the world doubles ranking
Data typeNumber (not available yet)
Template parameter"highestdoublesranking" in en:Template:Infobox tennis biography
Domaintennis players
ExampleRafael Nadal (Q10132) => "26"
Proposed byKompakt (talk)

 Not done see "highest singles ranking" above for explanation. --Tobias1984 (talk) 13:23, 2 February 2014 (UTC)

current doubles ranking (en) / aktuelle Weltranglistenplatzierung im Doppel (de)

   Done: no label (P1119) (Talk and documentation)
Descriptioncurrent ranking a tennis player has in the world doubles ranking
Data typeNumber (not available yet)
Template parameter"currentdoublesranking" in en:Template:Infobox tennis biography
Domaintennis players
ExampleRafael Nadal (Q10132) => "404"
Proposed byKompakt (talk)

✓ Done --Tobias1984 (talk) 13:26, 2 February 2014 (UTC)

Number of deaths (en) / Anzahl der todesfälle (de)/ Nombre de décès (fr)/ Número de muertes (es)

DescriptionThe number of people who died in an event, as stated in reliable sources
Data typeNumber (not available yet)
Template parametercasualties in w:Infobox civilian attack and w:Infobox battle
DomainBattles, wars, massacres, disasters, etc.
ExamplePenn's Creek Massacre (Q14607541) --> 14 World War II (Q362) --> 73,000,000 Sugarloaf Massacre (Q14774038) --> 17
SourceUsually found in the infobox of the article.
Robot and gadget jobsBots would be helpful.
Proposed by--Jakob (Scream about the things I've broken) 15:57, 1 September 2013 (UTC)
If we have a separate statement for each 'participant' (see property above) then the 'number of deaths' property can be a qualifier to that statement (and we can have properties for number of wounded and for total number of soldiers as well) Filceolaire (talk) 23:17, 10 September 2013 (UTC)

✓ Done --Tobias1984 (talk) 13:31, 2 February 2014 (UTC)

Oxidation state / Oxidationsstufe / état d'oxydation / Oкисления / Estado de oxidación

DescriptionThe w:Oxidation states of an element
Data typeNumber (not available yet)
Template parameter'oxidation states' in w:Template:Infobox element
DomainChemical elements
Allowed values-4 to +8
Examplehydrogen (Q556) --> -1,1 silicon (Q670) --> -4,-3,-2,-1,1,2,3,4 barium (Q1112) --> 2
Sourcew:List of oxidation states of the elements
Robot and gadget jobsPossible, but not needed as it would be used in < 110 items.
Proposed by--Jakob (Scream about the things I've broken)

✓ Done --Tobias1984 (talk) 13:35, 2 February 2014 (UTC)

Spin quantum number/ Spinquantenzahl / Spin nombre quantique / Numero quantico di spin

DescriptionThe spin quantum number of a subatomic particle.
Data typeNumber (not available yet)
Domainall subatomic particles
Proposed byPaperoastro (talk) 12:02, 9 February 2013 (UTC)
You are right, but this information could be useful for the Infoboxes (see for example electron). --Paperoastro (talk) 23:36, 10 February 2013 (UTC)
Indeed, I was thinking about the property here on Wikidata rather than its place in the infobox. Ideally, there would be a connection between the two; either as two separate properties, or something else. Since the spin is important information, I'll add a
 Support --Njardarlogar (talk) 09:48, 11 February 2013 (UTC)
 Support Nurick (talk) 22:37, 4 March 2013 (UTC)
I'm for this generally but I see two Problems with this kind of formulation:
  • The Spin is not dimensionless, it has the dimension to ħ, so it ether has to bee renamed to "Spin quantumnumber" (witch is dimensionless) or it has to have a unit.
  • You have to make clear you mean the absolute value of the Spin, because the Spin of electrons for example can be +1/2 or -1/2, only the absolute value is a feature of a type of particles.
Please solve this issues, then you have my  Support -- MichaelSchoenitzer (talk) 15:31, 9 March 2013 (UTC)
Good questions! You have right: it is more correct to use the name spin quantum number, which is dimensionless. This should be solve also your second issue: in fact the spin quantum number is defined as s = n/2, where n is any non-negative integer (see this definition). The spin direction (that for the electron can be +1/2 or -1/2) is dependent by the spin quantum number. So, I have changed the name of the property following your suggestion. --Paperoastro (talk) 23:01, 10 March 2013 (UTC)

 Support--Svebert (talk) 22:26, 13 March 2013 (UTC)

Parity / Parität /

DescriptionCharacteristic property of any elementary particle
Data typeNumber (not available yet)
Template parameterde:Vorlage:Infobox Teilchen
Proposed bySvebert (talk) 21:02, 15 March 2013 (UTC)
 Support -- MichaelSchoenitzer (talk) 15:39, 21 March 2013 (UTC)
 Support clearly defined statistical value. Joshbaumgartner (talk) 06:51, 13 May 2013 (UTC)


   Done: no label (P1124) (Talk and documentation)
DescriptionTwenty-foot Equivalent Units (TEU or teu). An inexact unit of cargo capacity often used to describe the capacity of container ships and container terminals. It is based on the volume of a 20-foot-long (6.1 m) intermodal container, a standard-sized metal box which can be easily transferred between different modes of transportation, such as ships, trains and trucks.
Data typeNumber (not available yet)

Gini coefficient / Gini-Koeffizient / Coefficient de Gini / Коэффициент Джини

DescriptionMeasurement of income inequality of a country, region, etc. Number between 0 and 1
Data typeNumber (not available yet)
Domaincountry, region, etc., but not limited to those
Allowed valuesnumber between 0 and 1

Q30 (USA) → 0.469, as of: 2010, source: [11]
Q183 (Germany) → 0.27, as of: 2006, source: [12]

Format and edit filter validation(sample: 7 digit number can be validated with edit filter Special:AbuseFilter/17)
Sourcee.g. CIA
Robot and gadget jobscollect data
Proposed byPοωερZtalk

While the Gini coefficient is a statistical ratio that can be used on almost everything, it's mostly used to display income inequality. I also see no other uses for it on Wikidata so I propose to limit the property to this field. —PοωερZtalk 16:45, 16 May 2013 (UTC)

 Support --Tobias1984 (talk) 17:28, 16 May 2013 (UTC)
 Support If sources are available for most countries or regions. Snipre (talk) 11:54, 18 May 2013 (UTC)
 Support --Viscontino (talk) 08:59, 26 May 2013 (UTC)
 Support --Micru (talk) 04:35, 25 June 2013 (UTC)

Isospin quantum number / Isospin Quantenzahl/

DescriptionCharacteristic property of any elementary particle
Data typeNumber (not available yet)
Template parameterde:Vorlage:Infobox Teilchen
Proposed bySvebert (talk) 21:02, 15 March 2013 (UTC)
 Support clearly defined statistical value. Joshbaumgartner (talk) 06:51, 13 May 2013 (UTC)

Isospin z-component / Isospin z-Komponente/

DescriptionCharacteristic property of any elementary particle
Data typeNumber (not available yet)
Template parameterde:Vorlage:Infobox Teilchen
Proposed bySvebert (talk) 21:02, 15 March 2013 (UTC)
 Support clearly defined statistical value. Joshbaumgartner (talk) 06:51, 13 May 2013 (UTC)

Standings position (en)

   Not done
DescriptionThe position to which season refers
Data typeNumber (not available yet)
Template parameteren:template:Infobox football club position
Domainorganization (football clubs)
Allowed values1-50 (1st, 2nd, 3rd, 4th ...)
Example 1MISSING
Example 2MISSING
Example 3MISSING
SourceExternal reference, Wikipedia list article
Robot and gadget jobsthey should be allowed
Proposed byXaris333 (talk) 15:54, 3 May 2013 (UTC)

It appears this is intended to be the position in the standings at the end of the previous season. I think "standings position" could be a good sports property, and then we can use qualifiers for the position at the end of a given season. --Jfhutson (talk) 18:52, 5 May 2013 (UTC)

Done. Xaris333 (talk) 19:09, 5 May 2013 (UTC)

 Not done - I think that this is better handled using time and season qualifiers with a generic ranking property. --Tobias1984 (talk) 14:47, 2 February 2014 (UTC)