Wikidata:Property proposal/Archive/18

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

place made

   Done: location of creation (P1071) (Talk and documentation)

Description	place where the item was made
Data type	Item
Domain	artificial physical object (Q15222213) ?
Allowed values	instance of geographic location (Q2221906)
Example	Mona Lisa (Q12418) -> Florence (Q2044)

Discussion

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)

•  Support. Emw (talk) 22:30, 12 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)

•  Support this new version (with geographic location (Q2221906)) --Paperoastro (talk) 11:49, 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)

   Done: Statistics Denmarks classification of occupation (DISCO-08) (P1069) (Talk and documentation)

Description	Danemark Job Code DISCO-08 maintained by the DST and derived from ISCO
Data type	String
Template parameter	none so far
Domain	profession (Q28640),occupation (Q13516667), jobs
Allowed values	6 digit numbers
Example	pharmacist (Q105186) => 226200
Format and edit filter validation	6 digit numbers
Source	http://www.dst.dk/pukora/epub/upload/16711/disco.pdf
Robot and gadget jobs	import would be nice to have
Proposed by	Teolemon (talk)

Discussion

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)

•  Done --Tobias1984 (talk) 16:16, 15 January 2014 (UTC)

ERA Journal ID

   Done: ERA Journal ID (P1058) (Talk and documentation)

Description	A unique identifier for periodic academic/scientific journals, used by Australian government and all Australian universities.
Data type	String
Domain	creative work (constraint: periodical (Q1092563))
Allowed values	The specification is: string up to ten characters long ; the research council has in practise only used digits, and only used up to five digits.
Example	Nature (Q180445) => 17479
Source	w:Excellence in Research for Australia (w:Australian Research Council); http://www.arc.gov.au/era/era_2012/archive/era_journal_list.htm
Proposed by	John Vandenberg (talk)

Discussion

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 --Jakob (talk) 16:57, 5 January 2014 (UTC)

CVR

   Done: CVR number (P1059) (Talk and documentation)

Description	The Central Business Register identifier. Number for the official database of Danish companies/organizations [1]
Data type	String
Template parameter	Cvr in w:da:Skabelon:Infoboks virksomhed
Domain	Category:Organizations based in Denmark (Q7314882) Danish organizations
Allowed values	8-digit numbers [2]
Example	"32859909" for Wikimedia Danmark. Det Danske Filmstudie (Q12308319) => 28516797
Format and edit filter validation	Check for 8 digits. (Is there any Special:AbuseFilter for that?)
Source	w:da:Det Centrale Virksomhedsregister, English cvr.dk
Proposed by	Finn Årup Nielsen (fnielsen) (talk)

Discussion

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 cvr.dk, e.g., for Lundbeck (Q902171) it is http://cvr.dk/Site/Forms/PublicService/DisplayCompany.aspx?cvrnr=56759913. 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)

Rector

   Done: rector (P1075) (Talk and documentation)

Description	the rector of a university.
Data type	Item
Template parameter	"Rettore" in it:Template:Università
Example	Polytechnic University of Milan (Q392904) => Giovanni Azzone (Q3766511)
Proposed by	Yiyi .... (talk!)

Discussion

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

•  Support--Micru (talk) 18:00, 22 November 2013 (UTC)

•  Comment can director / manager (P1037) not be used? Holger1959 (talk) 22:34, 3 January 2014 (UTC)
  • Rector is just one, like the CEO or chairman of a company. P1037 is generic, so it's not useful for an infobox. --NaBUru38 (talk) 18:57, 12 January 2014 (UTC)

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

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

Thailand central administrative unit code

   Done: Thailand central administrative unit code (P1067) (Talk and documentation)

Description	Unique 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 type	String
Domain	instances of administrative divisions of Thailand (Q1077333)
Allowed values	2, 4, 6 or 8 digits
Example	Takuk Nuea (Q15185578) => 841902
Source	en:ISO 3166-2:TH, http://stat.bora.dopa.go.th/dload/fccaa.htm (Thailand central administrative unit code (Q15477767))
Robot and gadget jobs	Could 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 by	Ahoerstemeier (talk)

Discussion

•  Support obviously as being the one to propose the property. Ahoerstemeier (talk) 20:46, 16 November 2013 (UTC)
• Ahoerstemeier, is this proposal not redundant with ISO 3166-2 code (P300)--Micru (talk) 13:10, 25 November 2013 (UTC)

  No, it is not, only the provinces share the same code as ISO3166 (because ISO3166 for Thailand is based on the national standard TIS1099), but this code system goes down all four levels of administrative subdivisions. It is thus a superset of ISO3166-2:TH as well as TIS1099, covering more entities than both. Ahoerstemeier (talk) 21:18, 25 November 2013 (UTC)

• I will create this property in 1 week. --Ricordisamoa 16:59, 27 December 2013 (UTC)

  @Ricordisamoa:, is it done yet? -- Lavallen (talk) 13:00, 13 January 2014 (UTC)

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

Rail gauge / Track gauge

   Done: track gauge (P1064) (Talk and documentation)

Description	Track gauge is a technical term used in rail transport to define the spacing of the rails on a railway track.
Data type	Item
Template parameter	Infobox public transit - track_gauge
Domain	transportation
Allowed values	any item from w:Template:Navbox track gauge
Example	Line C-1 (Q3239078) => 1668 mm track gauge (Q3319112)
Format and edit filter validation	filter Special:AbuseFilter/17)
Source	Wikipedia list article (either infobox or source)
Proposed by	B.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)

PlantList-ID

   Done: Plant List ID (Royal Botanic Gardens, Kew) (P1070) (Talk and documentation)

Description	TaxonId at The Plant List (Q625817)
Data type	String
Domain	extant species of vascular plants and bryophytes
Example	PlantList-ID for Amorphophallus titanum (Q431224) is kew-8323
Source	The Plant List (Q625817)
Robot and gadget jobs	Add 'http://www.theplantlist.org/tpl/record/$1' to Gadget-AuthorityControl.js
Proposed by	Succu (talk)

Discussion

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)

•  Support. Emw (talk) 00:07, 9 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) 10:50, 9 January 2014 (UTC)
•  Support --Tobias1984 (talk) 10:50, 9 January 2014 (UTC)
•  Support  — Felix Reimann (talk) 12:29, 10 January 2014 (UTC)
•  Done --Tobias1984 (talk) 16:25, 15 January 2014 (UTC)

ICTV virus ID

   Done: ICTV virus ID (P1076) (Talk and documentation)

Description	code for viruses from ICTV (http://ictvonline.org/)
Data type	String
Template parameter	infobox virus "ICTV"-field
Domain	viruses
Allowed values	excact string
Example	Adenoviridae (Q193447) = "00.001"
Format and edit filter validation	format, unique, single
Source	ICTV
Proposed by	--Tobias1984 (talk) 15:39, 13 January 2014 (UTC)

Discussion

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)

•  Done --Tobias1984 (talk) 21:38, 20 January 2014 (UTC)

pathogen transmission process

   Done: disease transmission process (P1060) (Talk and documentation)

Description	How a pathogen is transmitted. Follows the pathogen transmission ontology from OBO.
Data type	Item
Domain	disease (Q12136)
Allowed values	pathogen transmission (Q525512), or any of its subclasses
Example	malaria (Q12156) transmission process nodding disease (Q895930)
Source	Scientific publications
Proposed by	--Tobias1984 (talk) 10:37, 9 December 2013 (UTC)

Discussion

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 http://www.berkeleybop.org/ontologies/trans.owl, "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 http://www.berkeleybop.org/ontologies/trans.owl. (You can explore it yourself with Protege, downloadable at http://protege.stanford.edu/download/protege/4.3/installanywhere/Web_Installers/.)

Pathogen transmission class hierarchy

• transmission
  • direct
    • congenital
      • placental
    • contact
    • droplet spread
  • indirect
    • airborne
    • vector-borne
      • arthropod borne
        • arachnid borne
          • tick borne
        • insect borne
          • flea borne
          • mosquito borne
            • Anopheles gambiae borne
      • mechanical
      • vector-borne bite
      • vector-borne gastro-intestinal
        • copepod borne
          • Dracunculus medinensis borne
      • vehicle-borne
        • vehicle-borne fomite
        • vehicle-borne ingestion
        • vehicle-borne medical

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)

Examples

@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):

• malaria (Q12156)

• transmission process = mosquito borne transmission (Q15304532)

• parasite = Plasmodium (Q130948) (genus) ((a additional property))
• vector = Anopheles (Q158597) (genus - and actually only the females) ((an additional 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.

• malaria (Q12156)

• transmission process = mosquito borne transmission (Q15304532)

• parasite = Plasmodium (Q130948) (genus) ((a additional property))
• vector = Anopheles (Q158597) (genus - and actually only the females) ((an additional property))

• Hepatozoonosis (Q1607641)

• transmission process = (im not sure in this case? maybe:vehicle-borne ingestion)

• parasite = Hepatozoon (Q1153950) (genus) ((a additional property))
• vector = Ixodoidea (Q82645) (suborder - and actually only the females) ((an additional property))

• tuberkolosis

• transmission process = airborne

Tobias1984
Doc James
Bluerasberry
Gambo7
Daniel Mietchen
Andrew Su
Andrux
Pavel Dušek
Mvolz
User:Jtuom
Chris Mungall
ChristianKl
Gstupp
Sintakso
علاء
Adert
CFCF
Jtuom
Drchriswilliams
Okkn
CAPTAIN RAJU
LeadSongDog
Ozzie10aaaa
Marsupium
Netha Hussain
Abhijeet Safai
Seppi333
Shani Evenstein
Csisc
Morgankevinj
TiagoLubiana
ZI Jony
Antoine2711
JustScienceJS
Scossin
Josegustavomartins
Zeromonk
The Anome
Kasyap
JMagalhães

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:

• transmission process = mosquito borne transmission (Q15304532)

• parasite = Plasmodium (Q130948) (genus) ((a additional property))
• vector = Anopheles (Q158597) (genus - and actually only the females) ((an additional property))

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)

•  Done archiving in a couple of days. --Tobias1984 (talk) 10:46, 7 January 2014 (UTC)

deity of

   Done: worshipped by (P1049) (Talk and documentation)

Description	links to the religion, mythology or culture that worships this deity
Data type	Item
Template parameter	"major deities" in en:template:infobox religion
Domain	religion (unsorted)
Example	Ahura Mazda (Q179575) => Zoroastrianism (Q9601) / Yemaja (Q1477162) => Yoruba religion (Q1086440) / Zeus (Q34201) => Ancient Greek religion (Q855270)
Proposed by	Pikolas (talk) 22:09, 1 September 2013 (UTC)

Discussion

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

   Done: instruction set (P1068) (Talk and documentation)

Description	Instruction Set which the CPU is compatible
Data type	Item
Domain	CPU
Example	Atom D2700 (Q15220335): 64-bit computing (Q252132)
Source	Intel website, for Intel processors
Robot and gadget jobs	Robots can gather info on the Intel website and fill the property with it.
Proposed by	MisterSanderson (talk)

Discussion

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)

•  Done --Tobias1984 (talk) 16:10, 15 January 2014 (UTC)

readable file format

   Done: readable file format (P1072) (Talk and documentation)

Description	spilt from above.
Data type	Item
Example	Adobe Photoshop (Q129793)=>JPEG (Q2195) and others
Proposed by	GZWDer (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)

•  Done --Tobias1984 (talk) 17:24, 18 January 2014 (UTC)

writable file format

   Done: writable file format (P1073) (Talk and documentation)

Description	spilt from above.
Data type	Item
Example	Adobe Photoshop (Q129793)=>JPEG (Q2195) and others
Proposed by	GZWDer (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)

•  Done --Tobias1984 (talk) 17:24, 18 January 2014 (UTC)

KOATUU identifier

   Done: KOATUU ID (P1077) (Talk and documentation)

Description	Unique 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 type	String
Domain	instances of administrative territorial entity of Ukraine (Q203323)
Allowed values	9 or 10 digits
Example	Koktebel (Q1743602) => 111645700
Source	uk-Wikipedia infoboxes, database [3]
Robot and gadget jobs	Could 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 by	Voll (talk)

Discussion

•  Support It is an important geographical code that identifies every administrative unit in Ukraine. Voll (talk) 16:02, 12 January 2014 (UTC)

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

•  Support --RLuts (talk) 14:15, 13 January 2014 (UTC)
•  Support --Zuphilip (talk) 11:25, 15 January 2014 (UTC)

department (qualifier)

Superceeds 'Expenditure by department' above.

   Withdrawn

Description	qualifier for the 'expenditure' property
Data type	Item
Template parameter	"Expenditure by department"
Domain	Country, region and city articles for the Global Economic Map. Company articles
Allowed values	number (currency)
Example 1	MISSING
Example 2	MISSING
Example 3	MISSING
Source	http://www.census.gov/govs/local/
Robot and gadget jobs	Bots should be doing this task
Proposed by	Filceolaire (talk) 20:56, 6 November 2013 (UTC)

Discussion

•  Support I think this is the way to do Expenditure by department. Filceolaire (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

   Not done

Description	UN hazard pictogram
Data type	Commons media file
Template parameter	fr:infobox chimie, en:chembox, de:Chemikalien
Domain	chemistry
Allowed values	file:ADR 1.4.svg, file:ADR 1.5.svg, file:ADR 1.6.svg, file:ADR 2.1.svg, file:ADR 2.2.svg, file:ADR 2.3.svg,file:ADR 3.svg, file:ADR 4.1.svg, file:ADR 4.2.svg, file:ADR 4.3.svg, file:ADR 5.1.svg, file:ADR 5.2.svg, file:ADR 6.1.svg, file:ADR 6.2.svg, file:ADR 7A.svg,file:ADR 7B.svg,file:ADR 7C.svg,file:ADR 7E.svg,file:ADR 8.svg, file:ADR 9.svg,
Example	sodium azide (Q407577) = file:ADR 6.1.svg
Source	ADR 2011
Proposed by	141.6.11.21 12:00, 9 July 2013 (UTC)

Discussion

•  Wait - We should wait for this RfC first: Wikidata:Requests_for_comment/Image_properties:_many_properties_or_many_qualifiers. --Tobias1984 (talk) 12:12, 10 July 2013 (UTC)

 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)

•  Not done per Wikidata:Requests_for_comment/Image_properties:_many_properties_or_many_qualifiers.--GZWDer (talk) 13:25, 24 November 2013 (UTC)

Human Development Index

   Done: Human Development Index (P1081) (Talk and documentation)

Description	Human Development Index value of country.
Data type	Number (not available yet)
Template parameter	en:Template:Infobox country HDI
Domain	Nations
Allowed values	0 ≤ HDI ≤ 1
Example	Norway → 0.955, with qualifier <as of> → 2012
Source	http://hdrstats.undp.org/en/indicators/103106.html
Proposed by	Kwj2772 (talk)

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

•  Support -geraki ^talk 22:06, 8 May 2013 (UTC)
•  Support —★PοωερZ_talk 22:11, 8 May 2013 (UTC)
•  Support But I propose to get the data directly from the UNO http://hdrstats.undp.org/en/tables/ It is a better source and you can add data with qualifiers for many years. --Pyfisch (talk) 06:58, 9 May 2013 (UTC)
•  Support --Ricordisamoa 11:19, 10 May 2013 (UTC)
•  Support --Nightwish62 (talk) 10:28, 11 May 2013 (UTC)
• There are a lot of indexes like the HDI. Perhaps it would be better to use a more generic property? --Yair rand (talk) 22:01, 12 May 2013 (UTC)
• I'm in agree with Yair - دوستدار ایران بزرگ (talk) 09:01, 15 May 2013 (UTC)
• Moved to pending by Sven Manguard Wha? -- 20:18, 15 June 2013 (UTC)
•  Done First quantity property, enjoy! John F. Lewis (talk) 23:39, 30 January 2014 (UTC)

Egyptian Universities Library (EUL)

   Done: EUL editions (P1084) (Talk and documentation)

Description	Catalogue number for books (editions) in the Egyptian union catalog.
Data type	String
Domain	books
Allowed values	numeric string
Example	Miguel Ángel Asturias Rosales. (Q75603): Los ojos de los enterrados (1982 edition). Control number: 11403819
Source	Egyptian Universities Library (EUL): Union catalog
Proposed by	Kolja21 (talk)

Discussion

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

LibraryThing work identifier

   Done: LibraryThing work ID (P1085) (Talk and documentation)

Description	ID specifying an equivalent bibliographic work in the LibraryThing (Q742640) catalog
Data type	String
Template parameter	first parameter in de:Vorlage:LibraryThing
Domain	all books as creative works
Allowed values	numeric string (e.g. 337646)
Example	The 13½ Lives of Captain Bluebear (Q786908) => 337646
Format and edit filter validation	must be numeric
Source	http://www.librarything.com/services/librarything.ck.getwork.php
Robot and gadget jobs	(semi-)automatic creation is possible given the LibraryThing API and links from LibraryThing works to Wikipedia articles
Proposed by	JakobVoss (talk)

Discussion

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)

Description	The w:atomic number of a chemical element
Data type	Number (not available yet)
Template parameter	"atomic number" in w:Template:Infobox element
Domain	terms (chemical elements)
Allowed values	1+
Example	hydrogen (Q556) - 1 barium (Q1112) - 56 oganesson (Q1307) - 118
Source	http://www.rsc.org/periodic-table
Robot and gadget jobs	A 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)

•  Done --Tobias1984 (talk) 07:23, 31 January 2014 (UTC)

Elo rating / Elo-Zahl / Points ELO

Status:    Done

→ Property:P1087

• Description: Elo rating from FIDE for every chess player
• Datatype: txt-file / numbers
• Links: Mit de:Vorlage:Elo-Punkte is already something similar implemented in german wikipedia.
• Domain: Persons
• Infobox parameter example:
• Comments: Steak (talk) 20:59, 2 February 2013 (UTC)
  • Is there some bot who can import Elo rating? How often Elo rating is updated? --Stryn (talk) 07:53, 6 February 2013 (UTC)
  • Doesn't the ELO rating evolve every month? How do you reflect that in the item? Do you put the best rating, the most recent? --NaBUru38 (talk) 21:26, 8 February 2013 (UTC)
    • No, my intend was, that a bot updates the elo ratings every month. In de:wp, DrTrigonBot does this at de:template:Elo-Punkte. World chess federation FIDE provides a text-file at its homepage, and the bot uses this to fill in the monthly updated elo ratings. Advantage of wikidata would be, that storage of ratings would be centralized and all wikipedias could use them. Steak (talk) 20:56, 10 February 2013 (UTC)
      • Ok, that's fine to me. I support the property. --NaBUru38 (talk) 14:36, 13 February 2013 (UTC)
      • DrTrigonBot is awaiting botflag here too, so I think he could do this here to. If there are qualifiers it might be also possible to store the history of elo-ratings.  Support --Sk!d (talk) 00:46, 17 February 2013 (UTC)
•  Support especially if a bot can update ratings. Anyway I don't know if it would be better to have "best ELO recorded" or "current ELO" (or both)--Arnaugir (talk) 19:31, 19 February 2013 (UTC)
•  Support For the record, the data type should simply be a number, not a string.--Jasper Deng (talk) 07:11, 27 February 2013 (UTC)
• In my opinion the historical ELO numbers should be available on Wikidata too. Each entry should have a tag with the month it's valid for. That way you could iterate through the entries to find the highest ELO number or use the most current date to have the most recent ELO number. --Slomox (talk) 10:29, 28 February 2013 (UTC)
  • I agree with Slomox. --NaBUru38 (talk) 18:30, 8 March 2013 (UTC)
•  Support I support this: "Advantage of wikidata would be, that storage of ratings would be centralized and all wikipedias could use them." That's our purpose, after all. — ΛΧΣ²¹ 04:47, 26 March 2013 (UTC)
•  Support Keeping one page up-to-date versus dozens of language pages. Yep, that's what we're here for. Courcelles (talk) 19:58, 5 April 2013 (UTC)
•  Support Auto-updating is setup in Template:Elo rating and added as first example to Q106807. Please enjoy! ;) Greetings --DrTrigon (talk) 22:19, 23 April 2013 (UTC)
• For me 2 interesting points where mentioned: using Qualifiers and making a History. Could you explain a little bit more the concept? Would may be a cool thing (or even necessary) thing for the bot. Thanks a lot and Greetings --DrTrigon (talk) 22:35, 23 April 2013 (UTC)
  • Why did your bot add an alias? Thanks, FrigidNinja 11:58, 27 April 2013 (UTC)
    • The bot did not add an alias - I added it because it is needed in order to point the bot to the item. Greetings --DrTrigon (talk) 19:21, 27 April 2013 (UTC)
•  Support - this is typically something I would expect Wikidata to do. Edoderoo (talk) 19:30, 27 April 2013 (UTC)
•  Support. Conny (talk) 14:02, 28 April 2013 (UTC).
•  Support —★PοωερZ_talk 14:45, 28 April 2013 (UTC)
•  Done --Tobias1984 (talk) 07:23, 31 January 2014 (UTC)

Capacity

   Done: maximum capacity (P1083) (Talk and documentation)

Description	Τhe seating capacity of the venue. (we already have home venue)
Data type	Number (not available yet)
Template parameter	en:template:Infobox stadium capacity
Domain	place
Allowed values	0-120000
Source	External reference, Wikipedia list article
Robot and gadget jobs	they should be allowed
Proposed by	Xaris333 (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)

Population

   Done: population (P1082) (Talk and documentation)

Description	number of people inhabiting the country
Data type	Quantity
Template parameter	en:Infobox French commune (population + population date)
Domain	geographic features: places

• Description: Population according to published censuses
• Datatype: Quantity Value
• Links: only where census results are available, dependent on the country; most are already in Wikipedia(s)
• Infobox parameter example: en:Infobox French commune (population + population date)
• Comments: --Ymblanter (talk) 22:25, 31 January 2013 (UTC)

• Should be combined with village / Dorf / village. --Kolja21 (talk) 18:11, 2 February 2013 (UTC)

• And country Snipre (talk) 19:54, 2 February 2013 (UTC)

• Also valid for states, territories, regions, districts, neighbourhoods, etc. --Avenue (talk) 10:02, 5 February 2013 (UTC)

• That sounds like a basic thing to have, but who exactly is counted may vary across countries and times - see for instance en:Population without double counting. So a basic "population" property, plus other properties with more specifically defined meaning ? --Zolo (talk) 12:42, 3 February 2013 (UTC)

• 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)

• I just added this for country, agree this needs to be generic, but does not make sense for road, train stations and so on! Is a road a place??SilkyShark (talk) 00:50, 8 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)

• • Must be used with some date. JAn Dudík (talk) 18:50, 8 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)

•  Question Is this only meant for human populations? --Avenue (talk) 13:43, 9 February 2013 (UTC)
  • Very good question. This property should be renamed to "human population". Another relevant property could be "livestock population", which would need a qualifier for the animal. --NaBUru38 (talk) 23:30, 25 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)

•  Support, as long as the name or description makes clear this is for human populations. --Avenue (talk) 08:35, 13 March 2013 (UTC)
•  Support Espeso (talk) 18:48, 13 March 2013 (UTC)
•  Support, very good property. -- Klinglton358 (talk) 12:39, 24 March 2013 (UTC)
•  Support Emw (talk) 00:21, 28 March 2013 (UTC)
•  Support --Nightwish62 (talk) 15:44, 31 March 2013 (UTC)
•  Support This property is very usefull for infoboxies of wikipedia and wikidata can manage this tipe of data.--dega180 (talk) 18:59, 8 April 2013 (UTC)
•  Comment With qualifiers now available, the main objection to this property seems like it can be addressed. See the proposed 'from time' and 'to time' qualifiers. Emw (talk) 13:55, 20 April 2013 (UTC)

•  Comment added Template:Property_documentation above. --  Docu  at 12:02, 27 April 2013 (UTC)

 Comment, I removed the reference of the census, as there may be other sources, especially for historical data.

•  Support, but we need to make sure that we have a date qualifier on the property. I also agree that this should be on Administrative division instead of just cities.
  • Or both! -- Lavallen (block) 18:17, 3 May 2013 (UTC)
•  Support along with Avenue's comment above ·addshore· ^{talk to me!} 14:29, 22 June 2013 (UTC)
•  Support Can't wait to use that at Wikivoyage. Right now we duplicate the information in all languages Wikivoyages, so it is often out-of-date. Nicolas1981 (talk) 05:39, 27 August 2013 (UTC)

Mohs' hardness

   Done: Mohs' hardness (P1088) (Talk and documentation)

Description	Mohs hardness
Data type	Number (not available yet)
Template parameter	"Mohs hardness" in w:Template:Infobox element, "mohs" in w:Template:Infobox mineral
Domain	term
Allowed values	any solid substance
Example	diamond (Q5283) - 10 talc (Q134583) - 1
Source	[4], [5]
Proposed by	--Jakob (Scream about the things I've broken) 01:20, 5 August 2013 (UTC)

Discussion

 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)

•  Done --Tobias1984 (talk) 07:35, 31 January 2014 (UTC)

Orbital eccentricity

   Done: orbital eccentricity (P1096) (Talk and documentation)

Description	The eccentricity of an orbit.
Data type	Number (not available yet)
Template parameter	en:Template:Infobox planet eccentricity
Domain	All orbiting objects.
Proposed by	MER-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)

•  Done --Tobias1984 (talk) 07:41, 31 January 2014 (UTC)

Total produced

   Done: total produced (P1092) (Talk and documentation)

Description	How many made?
Data type	Number (not available yet)
Template parameter	put Wikipedia infobox parameters here. If existing, sample: "Total produced" in en:template:infobox locomotive
Source	External reference, Wikipedia list article (either infobox or source)
Proposed by	B.Zsolt (talk) 14:32, 12 July 2013 (UTC)

Discussion

• Shouldn't the datatype be 'number'? Filceolaire (talk) 06:15, 13 July 2013 (UTC)
  • Number is O.K.! --B.Zsolt (talk) 21:33, 16 July 2013 (UTC)
•  Support --Nightwish62 (talk) 08:09, 1 August 2013 (UTC)
•  Done --Tobias1984 (talk) 08:52, 31 January 2014 (UTC)

Redshift

   Done: redshift (P1090) (Talk and documentation)

Description	the redshift of an astronomical object.
Data type	Number (not available yet)
Template parameter	Template:Infobox galaxy z
Domain	astronomical object (Q6999) outside the Solar System
Example	<Messier 82 (Q14026)> redshift <0.000677 ± 0.000013>
Source	referred articles, astronomical databases as SIMBAD (Q654724) and NASA/IPAC Extragalactic Database (Q488563)

Discussion

• Comments: Directly observable quantity which serves as a proxy for distance, all distances in cosmology depend on the contents of the universe and the Hubble constant. MER-C (talk) 13:32, 8 February 2013 (UTC)

 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)

Description	Gross tonnage (GT) is a unitless index related to a ship's overall internal volume.
Data type	Number (not available yet)
Proposed by	18

•  Support as seen in infoboxes. Danrok (talk) 00:28, 28 May 2013 (UTC)
•  Support PMG (talk) 13:08, 19 August 2013 (UTC)
•  Support Pikolas (talk) 05:30, 12 November 2013 (UTC)
•  Done --Tobias1984 (talk) 09:04, 31 January 2014 (UTC)

g-factor

   Done: g-factor (P1097) (Talk and documentation)

Description	Characteristic property of any elementary particle (Lande factor)
Data type	Number (not available yet)
Domain	particles
Example	de:Vorlage:Infobox Teilchen
Proposed by	Svebert (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)

Flattening

   Done: flattening (P1102) (Talk and documentation)

Description	The flattening of a spherical body.
Data type	numeric-invalid datatype (not in Module:i18n/datatype)
Template parameter	en:template:Infobox planet flattening
Domain	any astronomic spherical object (astronomical object (Q6999))
Allowed values	0 < flattening < 1
Example	<Earth (Q2)> flattening <0.0033528>
Proposed by	--Paperoastro (talk) 14:25, 9 February 2013 (UTC)

•  Done --Paperoastro (talk) 13:25, 31 January 2014 (UTC)

masts

   Done: number of masts (P1099) (Talk and documentation)

Description	number of masts
Data type	Number (not available yet)

•  Support Danrok (talk) 20:10, 24 June 2013 (UTC)
•  Support PMG (talk) 13:03, 19 August 2013 (UTC)
•  Support Pikolas (talk) 05:30, 12 November 2013 (UTC)

•  Done --Jakob (talk) 13:06, 31 January 2014 (UTC)

number of cylinders

   Done: number of cylinders (P1100) (Talk and documentation)

Description	quantity of cylinders utilized in a piston engine design
Data type	Number (not available yet)
Domain	piston engines
Allowed values	positive integers
Example	Gnome-Rhône Mistral Major (Q902691) => number of cylinders => 14
Proposed by	Joshbaumgartner (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)

•  Done --Jakob (talk) 13:09, 31 January 2014 (UTC)

Electronegativity

   Done: electronegativity (P1108) (Talk and documentation)

Description	The electronegativity of a chemical element
Data type	Number (not available yet)
Template parameter	"electronegativity" in w:template:infobox element
Domain	terms (chemical elements)
Example	hydrogen (Q556) - 2.2 francium (Q671) - 0.7 fluorine (Q650) - 3.98
Source	CRC HAndbook of chemistry and physics
Robot and gadget jobs	Probably 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)

Discussion

•  Support --Tobias1984 (talk) 08:45, 19 July 2013 (UTC)
•  Support Snipre (talk) 09:52, 29 July 2013 (UTC)
•  Support TCN7JM 12:31, 6 August 2013 (UTC)
•  Support LucaBiondi (talk) 12:37, 18 August 2013 (UTC)
•  Support Emw (talk) 03:13, 15 October 2013 (UTC)
•  Support To be technical could specify in the description that it is using the Pauling Scale. Macadamia1472 (talk) 06:31, 16 October 2013 (UTC)

•  Done --Tobias1984 (talk) 17:20, 31 January 2014 (UTC)

Refractive index

   Done: refractive index (P1109) (Talk and documentation)

Description	refractive index of a substance with wavelength and temperature as qualifiers
Data type	Number (not available yet)
Template parameter	en, fr and de infoboxes about chemicals
Domain	term
Example	see Wikidata:Chemistry_task_force/Properties.
Proposed by	GZWDer (talk) 03:07, 7 June 2013 (UTC)

Discussion

 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) 17:25, 31 January 2014 (UTC)

Stepchild

   Not done

Description	A child by marriage, but not a biological child; inverse of P43 (P43)/ P44 (P44).
Data type	Item
Template parameter	"children" in en:template:infobox person and others.
Domain	person
Example	Clark Gable (Q71243) => Bunker Spreckels (Q15302241))
Proposed by	Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits

Discussion

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)

The following discussion is closed. Please do not modify it. Subsequent comments should be made in a new section. A summary of the conclusions reached follows.

I'm going to close this property as no consensus, for a few reasons. Firstly, it's pairing property "coordinates of the end" was closed without creation. Secondly, I find it persuasive that we should not be representing any objects which have a general "direction" as a pair of points—some objects will loop on themselves, some will split and rejoin, while in some cases there is neither beginning nor end but simply two ends (if that makes sense). Additionally, with all this talk of complexity, it seems rather odd to me that someone would try to get data on a river or street and think that such data wouldn't be complex. This property certainly wouldn't model the real-world object very well. --Izno (talk) 03:09, 31 January 2014 (UTC)

---

coordinates of the beginning

   Not done

Description	coordinates of beginning of long object e.g. street or river (it's source). Was discussed a bit at Wikidata:Project_chat/Archive/2013/06#Coordinates_for_streets.
Data type	Geographic coordinates
Template parameter	uk:Шаблон:Вулиця's координати п; ru:Шаблон:Улица Киева's координаты н; de:Vorlage:Infobox Fluss's QUELLE_LAT_GRAD and QUELLE_LONG_GRAD; fr:Modèle:Infobox Cours d'eau's source altitude, source latitude and source longitude etc.
Domain	geographical objects
Allowed values	coordinates
Example	Ivana Mazepy Street, Kyiv (Q3406887) => 50°26′37.4″N 30°32′43.3″E
Source	see infobox parameter section
Robot and gadget jobs	could be imported from infoboxes via bots
Proposed by	Base (talk) 12:36, 28 June 2013 (UTC)

Discussion

•  Support as a nominator. Even if we will support the whole shape of such objects in future its good to have such data separately. uk: Підтримую як номінатор. Навіть якщо у майбутньому ми будемо підтримувати повні форми таких об'єктів все одно добре мати ці дані окремо. --Base (talk) 12:43, 28 June 2013 (UTC)
•  Support Can be used in several infoboxes.--Ahonc (talk) 12:50, 28 June 2013 (UTC)
•  Support. Maybe create two properties: "Coordinates of beginning of the street / Координаты начала улицы" and "Springhead coordinates / Координаты истока"? This simplifies property naming, data extraction and validation. — Ivan A. Krestinin (talk) 20:32, 2 July 2013 (UTC)
•  Oppose not a good idea to promote. --Rschen7754 20:53, 2 July 2013 (UTC)
  • Could you explain in details that you mean? — Ivan A. Krestinin (talk) 21:14, 2 July 2013 (UTC)
    • We do not want to encourage using point objects to accurately represent linear objects. Also, I don't see why we couldn't just use a qualifier with the existing terminus (P559), regardless. --Rschen7754 21:50, 2 July 2013 (UTC)
      • Discussed property does not represent the object. It represent only one important point of the object. If you need all object`s point please propose new property. terminus (P559) can not be used with rivers, it is named "конечная остановка", that mean "end station", but river have no "end" and have no "stations". There are athother problems in qualifier way too. — Ivan A. Krestinin (talk) 04:00, 3 July 2013 (UTC)
        • Then there's the headwater property that has been proposed, and one could certainly create one for the mouth too. --Rschen7754 04:47, 3 July 2013 (UTC)
          • Sorry, I do not understand your idea. — Ivan A. Krestinin (talk) 17:50, 3 July 2013 (UTC)
            • There is already a headwaters property proposed on this page, why not use that and have a qualifier? --Rschen7754 19:47, 3 July 2013 (UTC)
              • Well, but if we will use qualifiers, item will have at least two coordinate values, however, coordinate location (P625) should have single value.--Ahonc (talk) 22:51, 3 July 2013 (UTC)
                • Are you sure? Even if you use P625 as the qualifier of terminus (P559)? --Rschen7754 22:58, 3 July 2013 (UTC)
                  • I do not understand too. Can you add for example coordinates of beginning and ending for the main street of Kiev Khreshchatyk (Q1076911)? It begins at 50° 27′ 8″ N, 30° 31′ 38″ E and ends at 50° 26′ 33″ N, 30° 31′ 13″ E.--Ahonc (talk) 00:30, 4 July 2013 (UTC)
                    • What are the terminii? --Rschen7754 01:06, 4 July 2013 (UTC)
                      • European Square (Q2997168), Bessarabska Square (Q2667365).--Ahonc (talk) 11:06, 4 July 2013 (UTC)
                        • Okay, it's been added. --Rschen7754 18:57, 4 July 2013 (UTC)
                          • And how can I know from what you added what point is actually start point and what is the end? It's important data for streets since it says where the building №1 and it's extremely important for rivers to know where is the source and where is the mouth. But that's not all. Khreshchatyk it's ok - it's a main street that starts and ends in squares that are definitely notable. But e.g. Hertsena Street (Q4471893) starts from Yuriia Illienka Street (Q4473151) but ends just in end of it's buildings. This poit has coordinates but sure there no article => item like "End of Hertsena Street"; The water artery of Ukraine Dnieper (Q40855) has it's mouth is Dnieper-Bug Estuary (Q2618618), Black Sea (Q166) but it's source is unnotable Axeninskyi Mokh Swamp. How would you place you're terminii in these cases (which are not rare ones, actually). Also there is a practical moment - we have easily parsable end's and begin's coordinates in infoboxes to perform import but not terminii; also i'm not sure it's easy to put data from qualifier to infobox. --Base (talk) 13:25, 7 July 2013 (UTC)
•  Oppose per Rschen7754. Coordinates really shouldn't represent linear objects like this. We should either do something with terminus (P559) or try something with KML data. TCN7JM 23:12, 2 July 2013 (UTC)
•  Oppose Linear feature can be point out with a qualifier. --Fralambert (talk) 13:49, 7 July 2013 (UTC)

  With a qualifier of what? --Base (talk) 14:03, 7 July 2013 (UTC)

  A qualifier of the position of the point on coordinate location (P625). --Fralambert (talk) 16:45, 7 July 2013 (UTC)

  What reason is to use qualifiers in situation where data can be presented without qualifiers? Currently coordinate location (P625) is used for {{coord|...|display=title}}. Multiple coords will generate errors because only one coords can be shown in title. — Ivan A. Krestinin (talk) 18:05, 7 July 2013 (UTC)

•  Oppose We should have a special datatype for linear features (and for area features). Until we have that we can leave the coordinates out or use a point coordinate for the middle of the item. Filceolaire (talk) 16:06, 10 July 2013 (UTC)
  • Why river can not have three properties: "object shape", "springhead coordinates", "mouth coordinates"? Another question: have "special data type" ability to mark some points of the shape as mouth and springhead? — Ivan A. Krestinin (talk) 18:22, 11 July 2013 (UTC)
•  Support as End coordinates // Координаты конца. Is, and if is, why is, previous commenter sure that 1) such datatype will appear in the project in reasonable time and 2) we shall be able to use it conviniently for extracting beginning and ending coordinates? These properties are used in poscards and infoboxes now in RuWiki at least. But other opposing commenters who are talking about mergeing the sense to terminus (P559) are more notable. We can name the discussed property into sth more general like "end of linear object". But of course we can't use here Item-typed property, it must be Coord-typed per Krestinin. Ignatus (talk) 19:07, 11 July 2013 (UTC)
•  Oppose, at least with this datatype. It might make sense at some point to create this property with the linear geocoords datatype, though. --Yair rand (talk) 11:24, 17 July 2013 (UTC)

  Why linear? In infoboxes we use geocoordinates. See for example here.--Ahonc (talk) 23:27, 17 July 2013 (UTC)

  I agree that just pair of coordinates is required for some infoboxes i.e. for river (Q4022) with one for spring (Q124714) and the second for river mouth (Q1233637) as in example here. I put some comment about it in Property talk:P403 and was redirected here. Paweł Ziemian (talk) 19:54, 2 August 2013 (UTC)

•  Support Good idea, why we must use single point? Streets, rivers need two: start and finish. ShinePhantom (talk) 08:12, 26 August 2013 (UTC)

  @ShinePhantom: Because for the strange reason coordinates of the end was declined :'(. This decline of connected proposal is the weirdest thing i ever seen at WD.--Base (talk) 17:09, 24 October 2013 (UTC)

• support for streets, but please consider a fallback solution for circular roads. oppose beginning for rivers and other natural features. Too few reliable sources, too much guesswork and original research involved. Which definition of the Amazon should I use (with the Marañón, with the Ucayali, or from their confluence)? How can I pinpoint the beginning of a river on googlemaps? Even if the place is available in high-res (quite rarely), the stream is hidden under the trees. And if it's visible, is it this stream or that stream? Retired electrician (talk) 13:25, 26 August 2013 (UTC)
•  Support required for infobox. --  Docu  at 01:45, 7 September 2013 (UTC)
•  Comment To my knowledge I think it is hard to unambiguously define the start of a river i.e where streams become tributaries and where tributaries become rivers. Macadamia1472 (talk) 06:12, 14 October 2013 (UTC)
•  Undecided. I can see how this would be useful, but there are other ways to do this. For example, I use coordinate location (P625) --> coordinates of source with the qualifier instance of (P31) --> river source (Q7376362). --Jakob (Scream about the things I've broken) 16:26, 3 December 2013 (UTC)
• Base, the decline was because we can very well provide this information without a special property, see avenue des Champs-Élysées (Q550). Personnally, I have no clear opinion on that. Using coordinate location (P625) with qualifiers seems more scalable, as there can be many sorts of points of interests for various types of items (gravity center, administrative center, highest point), and keeping track of many properties, with sometimes overlapping meanings is not very convenient. On the other hand, it will be easier to make a query on a main statement value than on a qualifier. --Zolo (talk) 17:42, 3 December 2013 (UTC)
  • About avenue des Champs-Élysées (Q550): how {{coord|...|display=title}} will use it? What algorithm must be implemented in it? Looks like the algorithm must accept some qualifiers and reject another. Where we store accept/reject lists? If we store the lists in Wikipedias templates how to support its in actual state? — Ivan A. Krestinin (talk) 18:21, 3 December 2013 (UTC)
    • It is not yet handled by the template (I wanted to do it on fr.wikipedia, but it seems that the coordinates module needs some refactoring before it can satistifactorily interact with the Wikidata module). Actually, we will have some problem every time p625 has more than one value. It can be for a variety of reasons (because we do not use the same reference point, because different sources give different values, or simply because the object has moved so there are several values for different dates). As it seems a bit difficult to take all these possibilities into consideration in Wikipedia, I think the best solution will be to mark one version as "preferred" directly in Wikidata once ranks are available (I guess a bot should choose the point marked as "midpoint" with the most recent data qualifier). --Zolo (talk) 18:35, 3 December 2013 (UTC)
      • P625 is handled in ruwiki already. Currently we have {{Constrain:Single value}} for P625. Ranks is not good mechanism for this tasks because there is no answer to question: that is better street begin or midpoint? About qualifiers: many "midpoint"-like qualifiers are possible (from your comment: gravity center, administrative center, highest point and many another). Extending P625 to many various cases (for example to movable objects) will create situation then every data query need huge number of checks and unexpected situations. We need no collect all possible data. Creating easy to use and handle data structure is more important task. Too complex structures usually have less applications because heeds too complex data extraction algorithms. — Ivan A. Krestinin (talk) 19:21, 3 December 2013 (UTC)
        • • The "unique" constraint cannot always work, because objects can move (for instance fontaine du Château d'eau (Q3076267)). Ideally, the constraint should take date qualifiers into account.
          • I think your argument makes sense, but only if we decide that we should not use coordinate location (P625) at all for roads and rivers. If we use p625, there will always need to choose one point as the preferred one, either explicitly or implicitly. --Zolo (talk) 20:09, 3 December 2013 (UTC)
            • fontaine du Château d'eau (Q3076267) will be bad surprise for every application that will try to use P625. P625 can be used for streets and others, but for something like "middle point of the street" (that is needed for {{coord|...|display=title}}), not for beginning or end points. — Ivan A. Krestinin (talk) 20:29, 3 December 2013 (UTC)
              • Yes, complex cases can be annoying, but as they will come up anyhow, we need ways to deal with them. If we say "for streets, the coordinates property should only provide the midpoint, then it seems to make more sense to use a dedicated "midpoint coordinates" property. If we say that the property can use more points than just the midpoint, then I see nothing wrong with adding the start point and the end point there. And if we say "p625 is not restricted to the midpoint, but the midpoint should be preferred by default for external applications and template like Template:Coord, then I think it would be simpler to mark the midpoint as "preferred" using ranks. This way, we would at the same time solve potential issues about dates and other qualifiers. --Zolo (talk) 21:04, 3 December 2013 (UTC)
                • Every time then new complex case appears you will need rewrite all {{Coord}} templates in all projects. Every external data user will need to do this too. Ranking can solve only small group of cases because you can not say that rank of midpoint is higher then rank of endpoint. These two points are uncomparable. Only concrete application know that point is preferred for it. Approach based on separate properties will not break working of existing application (primary {{Coord}}). — Ivan A. Krestinin (talk) 09:11, 5 December 2013 (UTC)
•  Support Разделяй и властвуй. Мастер теней (master of shadows) 20:58, 27 December 2013 (UTC)

---

The above discussion is preserved as an archive. Please do not modify it. Subsequent comments should be made in a new section.

launch contractor

   Done: launch contractor (P1079) (Talk and documentation)

Description	Company that launched the rocket.
Data type	Item
Template parameter	Infobox space flight: launch_contractor
Domain	satellites
Allowed values	contractors
Example	Gaia (Q767805) = Arianespace (Q309867)
Format and edit filter validation	subclass of company?
Source	technical sources
Proposed by	--Tobias1984 (talk) 17:40, 19 December 2013 (UTC)

Discussion

•  Support --Paperoastro (talk) 16:57, 20 December 2013 (UTC)
•  Support Danrok (talk) 21:30, 20 January 2014 (UTC)

OKTMO identifier

   Not done

Description	code by Russian Classification on Territories of Municipal Division (similar to OKATO ID (P721))
Data type	String
Template parameter	ru:Шаблон:Сельское поселение ОКТМО, ru:Шаблон:Городское поселение ОКТМО
Domain	instances of administrative territorial entity of Russia (Q192287)
Allowed values	8 or 11 digits
Example	Plyos (Q179486) =>
Source	ruwiki infoboxes, open database by Federal State Statistics Service of Russian Federation [6]
Robot and gadget jobs	I'm planing to write a bot to fill this property
Proposed by	Alexander Sigachov (talk)

Discussion

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

Description	the name of the synthesis or the general synthesis process
Data type	Item
Template parameter	?
Domain	all chemicals
Allowed values	synthesis methods
Example	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	?
Source	scientific literature
Proposed by	--Tobias1984 (talk) 09:56, 24 December 2013 (UTC)

Discussion

Pinging relevant people:

Saehrimnir
Leyo
Snipre
Dcirovic
Walkerma
Egon Willighagen
Denise Slenter
Daniel Mietchen
Kopiersperre
Emily Temple-Wood
Pablo Busatto (Almondega)
Antony Williams (EPA)
TomT0m
Wostr
Devon Fyson
User:DePiep
User:DavRosen
Benjaminabel
99of9
Kubaello
Fractaler
Sebotic
Netha
Hugo
Samuel Clark
Tris T7
Leiem
Christianhauck
SCIdude
Binter
Photocyte
Robert Giessmann
Cord Wiljes
Adriano Rutz
Jonathan Bisson
GrndStt
Ameisenigel
Charles Tapley Hoyt
ChemHobby
Peter Murray-Rust
Erfurth
TiagoLubiana

Notified participants of WikiProject Chemistry,

Tobias1984
Doc James
Bluerasberry
Gambo7
Daniel Mietchen
Andrew Su
Andrux
Pavel Dušek
Mvolz
User:Jtuom
Chris Mungall
ChristianKl
Gstupp
Sintakso
علاء
Adert
CFCF
Jtuom
Drchriswilliams
Okkn
CAPTAIN RAJU
LeadSongDog
Ozzie10aaaa
Marsupium
Netha Hussain
Abhijeet Safai
Seppi333
Shani Evenstein
Csisc
Morgankevinj
TiagoLubiana
ZI Jony
Antoine2711
JustScienceJS
Scossin
Josegustavomartins
Zeromonk
The Anome
Kasyap
JMagalhães

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

Description	opposition to the passage of an electric current through
Data type	Number (not available yet)
Domain	all nonnegative numbers
Example	ohm (Q47083)
Proposed by	TeleComNasSprVen (talk)

Discussion

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)

therapy

   Not done

Description	A method that a particular disease may be treated with.
Data type	Item
Domain	disease (Q12136), (items related to wikipedia category Category:Diseases and disorders (Q7215431))
Allowed values	instances of chemical compound (Q11173)/drug (Q8386), surgical procedures, psychotherapy (Q183257)/physiotherapy (Q186005)/occupational therapy (Q380141) (or their types, to be more precise)
Example	Parkinson'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
Source	medical literature, wikipedia articles
Proposed by	Pavel Dušek (talk)

Discussion

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)

Description	Unique 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 type	String
Domain	instances of administrative territorial entity of Latvia (Q750277)
Allowed values	7 digits
Example	Bauska Municipality (Q2365998) => 0400200
Source	[7]
Robot and gadget jobs	Could be imported from the source.
Proposed by	Voll (talk)

Discussion

•  Support. It is an important geographical code that identifies every administrative unit in Latvia. --Voll (talk) 15:32, 12 January 2014 (UTC)
•  Support: Useful as many other national identifiers for administrative units. --Zuphilip (talk) 23:11, 12 January 2014 (UTC)

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

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

Kallikratis geographical code

   Done: ELSTAT geographical code (P1116) (Talk and documentation)

Description	Kalikratis 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 type	String
Domain	place
Example	Thessaloniki (Q17151) => 0701010001 , Kavala Municipality (Q12282294) => 0501, Kavala (Q187352) => 0501010101
Format and edit filter validation	2 to 10 numerical digits
Source	[8] [9] [10]
Proposed by	geraki talk

Discussion

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)

Description	number of votes candidate received in subject election
Data type	Number (not available yet)
Domain	elections for specific offices
Allowed values	positive integers
Example	w:en:United States presidential election, 2012 candidate w:en:Mitt Romney votes received 206
Robot and gadget jobs	allowed
Proposed by	Joshbaumgartner (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 --Jakob (talk) 20:56, 31 January 2014 (UTC)

pKb

   Done: pKa (P1117) (Talk and documentation)

Description	Химический показатель (ru) – (Please translate this into English.)
Data type	Number (not available yet)
Template parameter	en, fr and de infoboxes about chemicals
Domain	term
Example	see Wikidata:Chemistry_task_force/Properties.
Proposed by	GZWDer (talk) 03:07, 7 June 2013 (UTC)

Discussion

 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

   Done: number of speakers, writers, or signers (P1098) (Talk and documentation)

Description	number of speakers
Data type	Number (not available yet)
Template parameter	"speakers" in w:en:Template:Infobox language
Domain	languages, language families (?)
Example	Welsh (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))
Source	many estimates on enwiki come from Ethnologue, particularly for languages with few speakers
Robot and gadget jobs	similar to above: bots can do well but not perfect
Proposed by	KleptomaniacViolet (talk)

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

•  Support Pikolas (talk) 03:23, 4 September 2013 (UTC)
•  Support Macadamia1472 (talk) 08:07, 16 October 2013 (UTC)

•  Done now. --Jakob (talk) 12:57, 31 January 2014 (UTC)

Proportion

   Done: proportion (P1107) (Talk and documentation)

Description	used as a qualifier. (contry to other quantity properties, I did not see any proposal about that, maybe because it is so obvious)
Data type	Quantity
Allowed values	number between 0 and 1
Example	(company X is 40 % owned by Y, Earth atmosphere is composed of 80% dinitrogen and 20% dioxygen)
Proposed by	Zolo (talk) 15:22, 16 August 2013 (UTC)

Discussion

 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". -- Lavallen^talk(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)

Description	Pokedex number
Data type	Number (not available yet)
Domain	Any Pokémon
Allowed values	numbers
Example	<Bulbasaur> pokedex number <1> (qualifier National Pokédex)
Source	External reference, Wikipedia list article (either infobox or source)
Proposed by	Legoktm

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)

• Moved to pending by Sven Manguard Wha? -- 20:18, 15 June 2013 (UTC)

•  Done --Jakob (talk) 22:45, 31 January 2014 (UTC)

number of items in series

   Done: number of episodes (P1113) (Talk and documentation)

Description	the number of items in a series
Data type	Number (not available yet)
Domain	items that that are used as the object for Property part of the series (P179)
Allowed values	non-negative integers
Example	The Simpsons (Q886)
Source	Wikipedia episode lists
Robot and gadget jobs	none
Proposed by	Morten Haan (talk)

Discussion

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)

Attendance

   Done: attendance (P1110) (Talk and documentation)

Description	number of people who (passively) follow an event
Data type	Quantity
Template parameter	"attendance" in en:template:Infobox International Football Competition
Domain	all kinds of events
Example	1982 FIFA World Cup => "2109723 " ...
Proposed by	Kompakt (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)

•  Done --Jakob (talk) 17:57, 31 January 2014 (UTC)

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

   Not done

Description	highest ranking a tennis player has achieved during his career in the world singles ranking
Data type	Number (not available yet)
Template parameter	"highestsinglesranking" in en:Template:Infobox tennis biography
Domain	tennis players
Example	Rafael Nadal (Q10132) => "1"
Proposed by	Kompakt (talk)

Discussion

•  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)

Description	current ranking a tennis player has in the world singles ranking
Data type	Number (not available yet)
Template parameter	"currentsinglesranking" in en:Template:Infobox tennis biography
Domain	tennis players
Example	Rafael Nadal (Q10132) => "5"
Proposed by	Kompakt (talk)

Discussion

•  Support. --Stryn (talk) 12:30, 16 June 2013 (UTC)
•  Support. -- Edoderoo (talk) 07:52, 18 June 2013 (UTC)
•  Done --Tobias1984 (talk) 13:04, 2 February 2014 (UTC)

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

   Not done

Description	highest ranking a tennis player has achieved during his career in the world doubles ranking
Data type	Number (not available yet)
Template parameter	"highestdoublesranking" in en:Template:Infobox tennis biography
Domain	tennis players
Example	Rafael Nadal (Q10132) => "26"
Proposed by	Kompakt (talk)

Discussion

•  Support. --Stryn (talk) 12:30, 16 June 2013 (UTC)
•  Support. -- Edoderoo (talk) 07:39, 18 June 2013 (UTC)

 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)

Description	current ranking a tennis player has in the world doubles ranking
Data type	Number (not available yet)
Template parameter	"currentdoublesranking" in en:Template:Infobox tennis biography
Domain	tennis players
Example	Rafael Nadal (Q10132) => "404"
Proposed by	Kompakt (talk)

Discussion

•  Support. --Stryn (talk) 12:30, 16 June 2013 (UTC)
•  Support. -- Edoderoo (talk) 07:40, 18 June 2013 (UTC)

 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)

   Done: number of deaths (P1120) (Talk and documentation)

Description	The number of people who died in an event, as stated in reliable sources
Data type	Number (not available yet)
Template parameter	casualties in w:Infobox civilian attack and w:Infobox battle
Domain	Battles, wars, massacres, disasters, etc.
Example	Penn's Creek Massacre (Q14607541) --> 14 World War II (Q362) --> 73,000,000 Sugarloaf Massacre (Q14774038) --> 17
Source	Usually found in the infobox of the article.
Robot and gadget jobs	Bots would be helpful.
Proposed by	--Jakob (Scream about the things I've broken) 15:57, 1 September 2013 (UTC)

Discussion

•  Comment It would be nice if it were possible to discriminate which party lost how many combatants. Pikolas (talk) 18:27, 2 September 2013 (UTC)
•  Comment we should store such figures, but this needs to be looked at in some more detail. See this table which shows World War I casualties. Danrok (talk) 01:59, 3 September 2013 (UTC)
•  Support --Nightwish62 (talk) 18:12, 6 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

   Done: oxidation state (P1121) (Talk and documentation)

Description	The w:Oxidation states of an element
Data type	Number (not available yet)
Template parameter	'oxidation states' in w:Template:Infobox element
Domain	Chemical elements
Allowed values	-4 to +8
Example	hydrogen (Q556) --> -1,1 silicon (Q670) --> -4,-3,-2,-1,1,2,3,4 barium (Q1112) --> 2
Source	w:List of oxidation states of the elements
Robot and gadget jobs	Possible, but not needed as it would be used in < 110 items.
Proposed by	--Jakob (Scream about the things I've broken)

Discussion

•  Support But we will have to find a way to force the Number datatype to allow us to display +2 for Cu²⁺(not just 2) etc. Macadamia1472 (talk) 08:02, 16 October 2013 (UTC)

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

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

   Done: spin quantum number (P1122) (Talk and documentation)

Description	The spin quantum number of a subatomic particle.
Data type	Number (not available yet)
Domain	all subatomic particles
Proposed by	Paperoastro (talk) 12:02, 9 February 2013 (UTC)

• Isn't this uniquely determined by which type of elementary particle we are talking about - e.g. lepton? While the reverse does not hold true.Njardarlogar (talk) 18:14, 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)

•  Done --Tobias1984 (talk) 13:43, 2 February 2014 (UTC)

Parity / Parität /

   Done: parity quantum number (P1123) (Talk and documentation)

Description	Characteristic property of any elementary particle
Data type	Number (not available yet)
Template parameter	de:Vorlage:Infobox Teilchen
Domain	particles
Proposed by	Svebert (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 --Tobias1984 (talk) 13:54, 2 February 2014 (UTC)

TEU

   Done: no label (P1124) (Talk and documentation)

Description	Twenty-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 type	Number (not available yet)

•  Support Standard spec. for transport ships. Danrok (talk) 11:59, 14 May 2013 (UTC)
•  Support PMG (talk) 13:10, 19 August 2013 (UTC)
•  Support Pikolas (talk) 05:30, 12 November 2013 (UTC)
•  Done --Tobias1984 (talk) 13:58, 2 February 2014 (UTC)

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

   Done: Gini coefficient (P1125) (Talk and documentation)

Description	Measurement of income inequality of a country, region, etc. Number between 0 and 1
Data type	Number (not available yet)
Domain	country, region, etc., but not limited to those
Allowed values	number between 0 and 1
Example	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)
Source	e.g. CIA
Robot and gadget jobs	collect data
Proposed by	—★PοωερZtalk

Discussion

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οωερZ_talk 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)

•  Done --Tobias1984 (talk) 14:02, 2 February 2014 (UTC)

Isospin quantum number / Isospin Quantenzahl/

   Done: isospin quantum number (P1126) (Talk and documentation)

Description	Characteristic property of any elementary particle
Data type	Number (not available yet)
Template parameter	de:Vorlage:Infobox Teilchen
Domain	particles
Proposed by	Svebert (talk) 21:02, 15 March 2013 (UTC)

 Support clearly defined statistical value. Joshbaumgartner (talk) 06:51, 13 May 2013 (UTC)

•  Done --Tobias1984 (talk) 14:13, 2 February 2014 (UTC)

Isospin z-component / Isospin z-Komponente/

   Done: isospin z-component (P1127) (Talk and documentation)

Description	Characteristic property of any elementary particle
Data type	Number (not available yet)
Template parameter	de:Vorlage:Infobox Teilchen
Domain	particles
Proposed by	Svebert (talk) 21:02, 15 March 2013 (UTC)

 Support clearly defined statistical value. Joshbaumgartner (talk) 06:51, 13 May 2013 (UTC)

•  Done --Tobias1984 (talk) 14:16, 2 February 2014 (UTC)

Standings position (en)

   Not done

Description	The position to which season refers
Data type	Number (not available yet)
Template parameter	en:template:Infobox football club position
Domain	organization (football clubs)
Allowed values	1-50 (1st, 2nd, 3rd, 4th ...)
Example 1	MISSING
Example 2	MISSING
Example 3	MISSING
Source	External reference, Wikipedia list article
Robot and gadget jobs	they should be allowed
Proposed by	Xaris333 (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)