Wikidata

Wikidata:Property proposal/Archive/7

< Wikidata:Property proposal‎ | Archive
This page is an archive. Please do not modify it. Use the current page, even to continue an old discussion.

Local Name, Lokaler Name, نام محلی

  • Description: Local Name (The name of sth in its native country, Language)
  • Datatype: StringValue/MultilingualTextValue
  • Domain: Everything (can be a place, food, ....)
  • Infobox parameter: Local Name (In Persian wiki نام محلی)
  • Comments: this is used a lot. For Items that are foreign or have different name locally, than what is well-known. (I don't know if it is possible to query in another language, than wiki's own).

--Pouyana (talk) 22:31, 3 March 2013 (UTC)

  Support—Doostdar (talk) 20:48, 8 March 2013 (UTC)
I wasn't here for a long time, sorry to answer you a little bit late. it is diffrenet as in alias I think you use the same language not local language.--Pouyana (talk) 10:10, 21 March 2013 (UTC)
  •   Comment: I guess it could be in StringValue/MultilingualTextValue datatype. This is useful in Infobox country, as native name is usually shown at the top. It would be great if language code can also be added on StringValue datatype in the future. --Ericmetro (talk) 10:01, 9 March 2013 (UTC)
I guess you are right, I change the data type.--Pouyana (talk) 10:10, 21 March 2013 (UTC)
  •   Support as String, item makes no sense. -- MichaelSchoenitzer (talk) 14:26, 9 March 2013 (UTC)
  •   Comment It is used in many infoboxes, but it may not be better to use more technically accurate property names here. For instance the native name of a company should probably be the name under which it is registered, while the original title of the book is probably the title under which it was first published, and I am not convinced it makes logical sense to use the same property. --Zolo (talk) 06:59, 12 March 2013 (UTC)
Official Name is better for names companies were registered under, with time parameters if it changes. Local Name is still useful with language or geographic qualifiers where companies have local nicknames or operating names in different locations. Filceolaire (talk) 07:07, 5 April 2013 (UTC)
  •   Comment Arabesque is an art originated from our country. But no one has ever heard this word in our country.We call it "islimi" designing. "Islimi" is a word never heard by foreigners.Hence it wont be considered even as an alias for "arabesque". That's the difference between "alias" and "local name".
Does any one of you know the native name for "Mount Everest", the Erath's highest mountain? It is called "Sagarmatha" by Nepalis but its "local names" are "Deodungha" ("Holy Mountain") and "Chomolungma" ("Holy Mother") as mentioned in Chinese Wikipedia infoboxes Mount Everest Naming. So this property should be considered as a language-specific property. -- دوستدار ایران بزرگ (talk) 11:38, 14 March 2013 (UTC)
  •   Oppose: If you have a name of the item in all languages (the name of wikidata item on the top of page) then a local name is a duplicate. It would be better to have a property "native country" of the item, and to get the native name that way. Janjko (talk) 14:39, 19 March 2013 (UTC)
  •   Oppose: No automatic way of collecting this data from Wikipedia or an external source is provided. No concrete example is provided. Mange01 (talk) 08:28, 20 March 2013 (UTC)
We can have bot collecting the data from for example fawiki, and example it using is country info template in every wikipedia that use this template.--Pouyana (talk) 10:10, 21 March 2013 (UTC)
I don't think this would be a good property if it were tied to language, instead of place. We already have built-in capability to specify aliases in different languages. This property might provide value if it were qualified by place--so for example, the item for "elevator" could have the statement "local name: lift (country: UK)" which would carry more information than simply stating "lift" as an alias for "elevator". Silver hr (talk) 02:26, 31 March 2013 (UTC)
  •   Support as string. Multilingual text makes no sense for this property. If there are different names in different local languages then each should get it's own statement with its own language, location, pronunciation etc. qualifiers, as required. It could even have a translation qualifier which could be multi-lingual text as for the Mount Everest example above. Filceolaire (talk) 07:07, 5 April 2013 (UTC)
  Oppose not because this wouldn't be useful, but because the proposal doesn't make clear whether this would be tied to language or place, and also because there's a better way of doing it now that we have qualifiers: a generic name property with a place qualifier. Silver hr (talk) 13:47, 25 April 2013 (UTC)

Unicode astronomic symbol / / / simbolo astronomico Unicode

DescriptionUnicode symbols that identify planets and some asteroids of the solar system
Data typeString
Template parameternot known
Domainplanets of the solar system and some asteroids
Allowed valuessome unicode symbols
Example<Jupiter> unicode astronomic symbol <♃>
Proposed byRicordisamoa 11:29, 27 March 2013 (UTC)

  Support Very useful, even if this property is not associated to any infobox parameter. A small suggestion: perhaps it could be better use an integer datatype with the unicode number. --Paperoastro (talk) 15:31, 28 March 2013 (UTC)

If there is no opposition, I'll create it as a string. --Ricordisamoa 17:27, 3 April 2013 (UTC)

  Comment I think this is too special, what about a general property for unicode symbols? That would cover this property, currency signs, sybols like for airplanes and others... --Pyfisch (talk) 18:16, 7 April 2013 (UTC)
  Ok. --Ricordisamoa 11:44, 13 April 2013 (UTC)
I've filed a discussion here. --Ricordisamoa 16:10, 13 April 2013 (UTC)
Does Property:P487 work for this. Can we archive the proposal? --Tobias1984 (talk) 21:13, 4 May 2013 (UTC)
  Support for the use of P:P487. --Paperoastro (talk) 21:31, 4 May 2013 (UTC)


currency symbol

DescriptionSymbol of currency
Data typeString
Template parameteren:Template:Infobox currency symbol
DomainCurrency
Example<United States dollar> → $
Sourceinfobox
Robot and gadget jobsYes
Proposed byKwj2772 (talk)

Kwj2772 (talk) 08:15, 21 April 2013 (UTC)

  Oppose use proposed Property "Unicode character / Unicodezeichen" instead. --Pyfisch (talk) 15:23, 25 April 2013 (UTC)
  Comment use datatype wikibase-item and link the item of the currency symbol: Q4917→Q11110 and Q4916→Q18100. --Fomafix (talk) 09:37, 26 April 2013 (UTC)
  Support to Fomafix's idea. --Ricordisamoa 11:07, 26 April 2013 (UTC)

Provisional designation / / Désignation provisoire / / Designazione provvisoria

Descriptionthe provisional designation given to an astronomical body after its discovery and before the IAU approves the official name.
Data typeString
Template parameteren:Template:Infobox planet alt_names
Domainastronomical bodies as asteroids, natural satellites, comets...
Example<103 Hera> provisional designation <1927 CV>, <1950 CM>;
Sourcesee Provisional designation in astronomy
Proposed byPaperoastro (talk)

Motivation. Property certainly useful for a lot of astronomical items, but probably it could be useful also as "generic property". I chose the "not translated string" datatype because the nomenclature of this name is rigorously established by IAU and I verified for some satellites of Jupiter that no Wikipedias transliterate provisional names (even if I'm not totally sure for Persian language!). --Paperoastro (talk) 08:52, 18 April 2013 (UTC)

If there is no opposition, I will create the property. --Paperoastro (talk) 20:50, 4 May 2013 (UTC)
  Support - It looks like a useful property. --Tobias1984 (talk) 21:08, 4 May 2013 (UTC)

Orbit diagram

Descriptionthe image with the diagram of the orbit of an astronomic body.
Data typeCommons media file
Template parameteren:template:infobox planet orbit_diagram
Domainusually asteroids, natural satellites and comets, but it could be used also for extra-solar planets and multiple stars.
Allowed valuesimages in Commons category (and subcategories) commons:Category:Orbits.
Example<1105 Fragaria> orbit diagram File:1105orbit.gif
Proposed byPaperoastro (talk)

Motivation. It is a poorly used parameter of the English template "Infobox planet", but in Commons there are more than 300 images (and animated gif) of asteroid orbits. Wikidata can help other Wikipedias to manage them. --Paperoastro (talk) 09:47, 18 April 2013 (UTC)

  Support Sounds very useful. --Tobias1984 (talk) 09:49, 18 April 2013 (UTC)
  Fullt stöd -- Lavallen (block) 06:02, 4 May 2013 (UTC)

OMIM

   Done: OMIM ID (P492) (Talk and documentation)
DescriptionOnline Mendelian Inheritance in Man catalogue codes for diseases
Data typeString
Template parameteren:Template:Infobox disease field OMIM
Domainen:Mendelian Inheritance in Man
Allowed valuesen:Mendelian Inheritance in Man
ExampleHuntington's disease = 143100
Sourcehttp://www.omim.org/
Proposed byOldakQuill (talk) 04:10, 7 March 2013 (UTC)
  Support Emw (talk) 02:09, 27 March 2013 (UTC)
  Support Kaligula (talk) 11:09, 21 April 2013 (UTC)
  Support --Tobias1984 (talk) 08:43, 1 May 2013 (UTC)

ICD-9

   Done: ICD-9 ID (P493) (Talk and documentation)
DescriptionICD catalogue codes for diseases
Data typeString
Template parameteren:Template:Infobox disease fields ICD9 and ICD10
Domainen:International Statistical Classification of Diseases and Related Health Problems
Allowed valuesen:International Statistical Classification of Diseases and Related Health Problems
ExampleInfluenza = 487
Sourceen:International Statistical Classification of Diseases and Related Health Problems
Proposed byOldakQuill (talk) 04:10, 7 March 2013 (UTC)
  Support MichaelSchoenitzer (talk) 21:57, 13 March 2013 (UTC)
  Support Emw (talk) 02:09, 27 March 2013 (UTC)
  Oppose. I suggest to use only ICD and use qualifier for the version. --Nightwish62 (talk) 19:46, 30 March 2013 (UTC)
  Support I oppose the qualifier idea because ICD-9 & ICD-10 codes are very different and nobody will search for "code X in any ICD version" . Things would only be harder with a compulsory qualifier. By the way is ICD-9 still useful  ? Ske (talk) 09:18, 13 April 2013 (UTC)
  Comment Someday, we'll have ICD-11 --Chris.urs-o (talk) 17:31, 18 April 2013 (UTC)
  Support Kaligula (talk) 11:09, 21 April 2013 (UTC)
  Support separate properties for ICD 9, 10, 11. --Tobias1984 (talk) 13:15, 28 April 2013 (UTC)
  Support separate properties for ICD 9, 10, 11. --Chris.urs-o (talk) 17:57, 28 April 2013 (UTC)

ICD-10

   Done: ICD-10 (P494) (Talk and documentation)
DescriptionICD catalogue codes for diseases
Data typeString
Template parameteren:Template:Infobox disease fields ICD9 and ICD10
Domainen:International Statistical Classification of Diseases and Related Health Problems
Allowed valuesen:International Statistical Classification of Diseases and Related Health Problems
ExampleInfluenza = J10 & J11
Sourceen:International Statistical Classification of Diseases and Related Health Problems
Proposed byOldakQuill (talk) 04:10, 7 March 2013 (UTC)

For comments see ICD-9

Installed operating system

   Not done
Descriptionthe original operating system installed on this product
Data typeItem
Template parameteren:Template:Infobox Mobile phone | operatingsystem=
Domaindevices, computers, electronic products
Example 1MISSING
Example 2MISSING
Example 3MISSING
Proposed byDanrok (talk) 02:06, 4 March 2013 (UTC)
  Question Would this include the operating system that a piece of software runs on, as in en:Template:Infobox software? Or should that be a separate property? Reach Out to the Truth (talk) 16:34, 4 March 2013 (UTC)
I think these two are best kept separate, because the scenarios are quite different. For example, not all software is OS specific, some software runs in web browsers. Danrok (talk) 19:47, 5 March 2013 (UTC)
  Comment - If everybody is happy using Property:P306 I will archive this proposal in a couple of days. --Tobias1984 (talk) 14:41, 4 May 2013 (UTC)

Conflict / conflit

   Not done
DescriptionLarger conflict of which this military event is part of
Data typeItem
Template parameterEither conflict or partof in en:template:Infobox military conflict
Domainmilitary events (term)
ExampleFor Battle of the Somme, it would be WWII
For Battle of Gettysburg, it would be American Civil War, etc
Format and edit filter validation(sample: 7 digit number can be validated with edit filter Special:AbuseFilter/17)
Robot and gadget jobsShould or are bots or gadgets doing any task with this? (Check other properties for consistency, collect data, etc.)
Proposed byPikolas (talk)

We don't have properties to deal with wars and battles yet, and I think this one can connect smaller events (battles, attacks, offensives, sieges) into larger events (wars, revolutions, coups d'état, etc). Pikolas (talk) 11:23, 26 April 2013 (UTC)

Launch site

   Not done
DescriptionLaunch site
Data typeItem
Template parameteren:Template:Infobox spacecraft launch_site en:Template:Infobox_space_mission Launch pad
Domainsatellite or space launch
Allowed valuesLaunch site and pad
ExampleKosmos-419 launched from Baikonur 81/23.
SourceLaunchlog is probably the best source
Proposed bySecretlondon (talk)

In our articles about satellites we say where something launched from. We have been saying pad as well as area, but just linked to an article on the area. In the above example Baikonur 81/23 is pad 23, at Baikonur site 81. I think we need an object for each pad. Secretlondon (talk) 14:36, 27 April 2013 (UTC)

There already seems to be launch site actually. Can we document this stuff somewhere? Secretlondon (talk) 15:11, 27 April 2013 (UTC)
It's at Wikidata:List_of_properties#Spacecraft. Some of the more general ones may also apply to Space. --  Docu  at 15:26, 27 April 2013 (UTC)

Upper stage

   Not done
DescriptionUpper stage
Data typeItem
Template parameteren:Template:Infobox spacecraft launch_vehicle and carrier rocket
Domainlaunches, satellites
ExampleEutelsat 70B was launched by a Zenit-3SL with a Blok DM-SL upper stage.
SourceExternal reference, Wikipedia list article (either infobox or source)
Proposed bySecretlondon (talk)

We have launch vehicle but that seems just to be for things like Proton-K, not mentioning the upper stage which we always do when we write about a launch. In the infobox we will write something like Molniya-M/2BL with Molniya-M as the rocket and Blok 2BL as the upper stage. I think we need to capture the upper stages. Secretlondon (talk) 15:07, 27 April 2013 (UTC)

  Comment Implementing two separate parameters in infoboxes will be virtually impossible. --WDGraham (talk) 00:08, 28 April 2013 (UTC)
I've been playing with this on Kosmos 2485. I think we can get the barebones of a wiki satcat with this. I can have more than one entry for launch vehicle so I've added both the Soyuz and the Frigat as launch vehicle. We lose some specifics as we do not have an article for GLONASS-M (yet), only GLONASS. We have an article for Soyuz-2, not Soyuz-2-1b so the launch vehicle loses that detail. We have an article for Plesetsk Cosmodrome Site 43, not site 43 pad 4 so we lose the pad detail. However this looks really powerful. Secretlondon (talk) 14:31, 28 April 2013 (UTC)
I've now worked out how to make entries link to things without Wikipedia articles and as we can have two entries for launch vehicle I don't think we need upper stage anymore. Secretlondon (talk) 10:01, 6 May 2013 (UTC)

ISO 4217 code

DescriptionISO 4217 code of currency
Data typeString
Template parameteren:Template:Infobox currency iso_code
DomainCurrency
Example<United States dollar> → USD
Sourcehttp://www.currency-iso.org/en/home/tables/table-a1.html
Robot and gadget jobsYes
Proposed byKwj2772 (talk)

Kwj2772 (talk) 08:15, 21 April 2013 (UTC)

Website/ وبگاه

   Not done
DescriptionLink to city's web site.
Data typeURL
Template parameteren:template: Infobox_Italian_comune or en:template:Infobox_Israel_municipality website
Domaincities
Example 1MISSING
Example 2MISSING
Example 3MISSING
Proposed byدوستدار ایران بزرگ (talk) 17:42, 31 March 2013 (UTC)

  Comment could we use this? --Stryn (talk) 11:01, 10 April 2013 (UTC)

Maybe yes. دوستدار ایران بزرگ (talk) 07:39, 15 April 2013 (UTC)
If nobody opposes, I'll archive it in 24h, and assume we can use "Official website". --Ricordisamoa 19:56, 20 April 2013 (UTC)
I'd support that. Emw (talk) 20:05, 20 April 2013 (UTC)
nice idea دوستدار ایران بزرگ (talk) 07:59, 21 April 2013 (UTC)

First incumbent / Premier titulaire: Not done

Comments: - Ssolbergj (talk) 13:51, 13 March 2013 (UTC)


  Oppose Who is the first is seen from other data. If you give a person the property "held this position from 1980 to 1985" then you can find the first one with a query. So, this is duplicate data. The same for two properties beneath. Janjko (talk) 15:53, 19 March 2013 (UTC)
  Oppose per Janko: the data can be derived. --NaBUru38 (talk) 19:39, 27 March 2013 (UTC)
  Oppose per Janko too --Nightwish62 (talk) 20:02, 30 March 2013 (UTC)

Last incumbent / Dernier titulaire: Not done

  Oppose Property:P39 is doing the job with qualifiers Snipre (talk) 09:42, 2 April 2013 (UTC)
  Oppose per Snipre. --NaBUru38 (talk) 19:07, 18 April 2013 (UTC)

incumbent / titulaire: Not done

  Oppose Property:P39 is doing the job with qualifiers Snipre (talk) 09:42, 2 April 2013 (UTC)
  Oppose per Snipre. --NaBUru38 (talk) 19:07, 18 April 2013 (UTC)

Organization website (en)

   Not done
DescriptionThe URL of the club's official website
Data typeItem
Template parameteren:template:Infobox football club website
Domainorganization (football clubs)
Example 1MISSING
Example 2MISSING
Example 3MISSING
SourceExternal reference, Wikipedia list article
Robot and gadget jobsthey should be allowed
Proposed byXaris333 (talk) 15:54, 3 May 2013 (UTC)

Wikidata:Property proposal/Pending#Official website / Offizielle Homepage / Site officiel / Sito ufficiale --Jfhutson (talk) 18:46, 5 May 2013 (UTC)

Thx. I did't see it. Xaris333 (talk) 19:09, 5 May 2013 (UTC)
This proposal wil be deleted in few days. Snipre (talk) 01:03, 6 May 2013 (UTC)

Exclave of

  • Description: territory is legally or politically attached to a main territory with which it is not physically contiguous because of surrounding alien territory. It may also be an enclave.
  • Datatype: item
  Support this is a useful piece of data for such places. Joshbaumgartner (talk)
  Done as Property:P500 --  Docu  at 07:49, 9 May 2013 (UTC)

Enclave within

  • Description: territory is entirely surrounded by the other (enclaved)
  • Datatype: item
  Support as per 'exclave of', it is useful and straight-forward. Joshbaumgartner (talk)
  Done as Property:P501 --  Docu  at 07:49, 9 May 2013 (UTC)

HURDAT identifier

   Done: HURDAT ID (P502) (Talk and documentation)
DescriptionTropical cyclone identified in the NOAA AOML HRD's HURDAT database: Atlantic version is seen here, all storms are listed here
Data typeString
Domaintropical cyclone items within the Atlantic, eastern Pacific, and central Pacific tropical cyclone basins
Allowed valuesletters "AL," "EP," or "CP" followed, without a space, by a six-number string, the first two numbers indicating the storm number, and the last four indicating the year (e.g. CP021959, AL182012, EP061967). "WP" entries for the western Pacific exist as well, though only four, and those entries have been updated only for 2012. Regex: ^[AEC][LP]\d{6}$
Example<Hurricane Sandy> HURDAT identifier <AL182012>
SourceAtlantic source, full listing
Proposed byHurricanefan24 (talk) 18:37, 28 March 2013 (UTC)

I'm not sure if I fully understand the concept of authority control...if I've made a mistake in proposing it, just let me know.   Hurricanefan24 (talk) 18:54, 28 March 2013 (UTC)

It does not seem to be used in Wikipedias, and I do not understand anything about it, but a bit of googling suggests that it is a standard reference, and I do not see any harm in adding it. --Zolo (talk) 19:43, 6 May 2013 (UTC)
  Support standardized reference identifier published by an established authority Joshbaumgartner (talk) 07:42, 9 May 2013 (UTC)
  Done --FrigidNinja

Homeport

Descriptionhomeport as seen in Infobox ship career
Data typeItem
Domainterm: ships
Allowed valuesany item which is a port
ExampleExample: HMS Astute (S119)
Proposed byDanrok (talk) 19:18, 1 May 2013 (UTC)

General Manager / General Manager / Directeur général

DescriptionGeneral manager of a sports team
Data typeItem
Template parameterhockey club: en:Template:Infobox hockey team (GM parameter)
Domainsports teams
SourceWikipedia sports teams infoboxes
Robot and gadget jobsCan most likely be imported by bots
Proposed byCarport
  Support per above. With general manager (often abbreviated as GM in North America), we would now have the owner, president (those two non-specific to sports), GM and head coach hierarchy all in place. Shawn in Montreal (talk) 17:44, 8 March 2013 (UTC)
  Support an notable role in the organization. Maybe can also allow people with a different title, but the same job description to be claimed with a qualifier indicating official job title. Joshbaumgartner (talk) 10:35, 9 May 2013 (UTC)
  Done --FrigidNinja 12:11, 11 May 2013 (UTC)

ISO 15924 (code for writing systems) / (Code für Schriftsysteme) / (code pour des écritures)

Descriptionfour-letter and numeric code for writing systems
Data typeString
Template parameter'ISO15924='/'iso15924=' , see de:Vorlage:Infobox Schrift, en:Template:Infobox writing system or fr:Modèle:Infobox Système d'écriture
Example"Cyrl" and "220" for en:Cyrillic script (Q8209)
Proposed byMonsieurbecker (talk) 08:15, 30 March 2013 (UTC)

Both versions of the code (four-letter vs. numeric) should be distinguished by a qualifier. --Monsieurbecker (talk) 08:15, 30 March 2013 (UTC)

  Done (Property:P506) --Kolja21 (talk) 13:30, 11 May 2013 (UTC)

County code in Sweden

Description"länskod" (county-code)
Data typeString
Domainplace
Allowed valuesdd
Example14 -> Q103093 (county) etc.
Format and edit filter validationMaybe, but I have no experince with such tasks.
SourceI recomend Statistics Sweden as source
Robot and gadget jobsI intend to compare the values with the present on svwp and on Statistics Sweden, before I starts to use them.
Proposed byLavallen (block)

More properties will come from the original proposal on Wikidata:Property proposal/Place who had the original header: "Statistics Sweden-code / SCB-kod/". -- Lavallen (block) 16:18, 11 May 2013 (UTC)

Cause of Death

Descriptionan item describing the cause of a person or specific organism's (i.e Smokey) death. I.e Leukaemia, car crash
Data typeItem
Domainperson only (including named animals)
Allowed valuesdiseases, medical complications, traumatic events etc.
ExampleRichard Nixon => Stroke; Neil Armstrong --> surgical complications [qualifier:coronary artery bypass surgery]
Proposed byMacadamia1472 (talk)
Discussion

We already have killed by i.e. assassin so this seems logical as it has a larger scope and is of more statistical etc. relevance Macadamia1472 (talk) 01:50, 30 April 2013 (UTC)

Already rejected. Regards, FrigidNinja 01:53, 30 April 2013 (UTC)
Do we have any guidelines about re-proposing properties? That proposal underwent some substantial revision after it was originally proposed in response to early objections. I'm a bit biased, having been a supporter of the previous proposal, but this seems like a broader question. Emw (talk) 03:00, 30 April 2013 (UTC)
  Comment I would think that if the proposal was re-worked to address the concerns raised in the previous discussion, and those who opposed it before are notified where possible that it is back on the docket, then I think it is reasonable to bring something back to the floor. That is probably something for an RfC, and outside of the scope of this page I would presume. Joshbaumgartner (talk) 09:24, 9 May 2013 (UTC)
  Support cause of death seems to be a pretty basic and useful data point for a deceased person. Joshbaumgartner (talk) 09:24, 9 May 2013 (UTC)
  Support as it's a matter of general interest. --Nightwish62 (talk) 09:41, 11 May 2013 (UTC)

brother-in-law (sister's husband)

   Done: no label (P510) (Talk and documentation)
Descriptionw:Brother-in-law: limited to sister's husband. Terms may vary from one language to another.
Data typeItem
Domainpersons
ExampleQ461630 "Auguste de Beauharnais" => Q939 "Pedro I of Brazil"
Robot and gadget jobscould be derived from
Proposed by--  Docu  at 10:49, 25 April 2013 (UTC)
  Comment I suggest changing the name to "sibling's husband", in case of same-sex marriages. FrigidNinja 01:52, 26 April 2013 (UTC)

Honorific prefix

academic degree / /

DescriptionAcademic degree that the person holds
Data typeItem
Template parameterYou can use en:Template:Infobox person education as complementory factor.
DomainPerson
Allowed valuesAcademic degree such as Doctor of Philosophy, Master, Bachaelor etc.
Example<Paul Krugman>academic degree<Doctor of Philosophy> with qualifier "field of work" <Economics> and "alma mater" <MIT>
SourceExternal information about that person can be source of this property
Robot and gadget jobsNo.
Proposed byKwj2772 (talk)

This property may be helpful to describe academic career of specific person. Kwj2772 (talk) 13:50, 13 April 2013 (UTC)

  Support, but I think academic degree should be used as a qualifier to alma mater. The field of work is not necessarily related to the degree a person has, so I don't see why field of work is used as a qualifier for academic degree in the proposal. --Wylve (talk) 12:17, 20 April 2013 (UTC)
Because the field of work can express his/her major. Well we should determine which method to express their major: a) Use every item to express their major (e.g. Bachelor of Journalism) or b) add qualifier "field of work" that can express their major. I prefer b) to a) because all types of degree by major could not be listed as item. Usually types of degree by major are listed only in enwiki, and even in enwiki, some types of degree (e.g. w:en:Bachelor of Economics) redirect to just w:en:Bachelor's degree. Kwj2772 (talk) 07:55, 21 April 2013 (UTC)
  Comment, separating "education" from "alma mater" would create a rather confuse structure, espacially for people who have studied at various places. I think the "alma mater" property should be renamed to "education", with recommended format:
Paul Krugman:
education:
PhD
institution: MIT
date: 1974-1977
topic: eonomics
doctoral adivsor: Rudiger Dornbusch
PhD thesis: Essays on flexible exchange rates

Birth name

   Done: no label (P513) (Talk and documentation)
DescriptionName at birth, only if different from current name
Data typeString
Template parameter"birth name" from en:Template:Infobox person and various others (en:Template:Infobox sportsperson, en:Template:Infobox dancer)
DomainAny person
Example<Pope John Paul II> birth name <Karol Józef Wojtyła>
SourceInfobox on Wikipedia page
Robot and gadget jobsCould be easily imported from infoboxes by various bots
Proposed byFrigidNinja

I realize that many people may think that this is redundant with aliases, but I consider it necessary for inclusion in infoboxes. Remember also that aliases are not multilingual. FrigidNinja 23:00, 24 April 2013 (UTC)

Province / استان

   Not done
DescriptionThe name of a province of the country in which the city or village is situated equivalent to Prefecture (France & Japan)
Data typeItem
Template parameteren:template:Infobox Italian comune Province
Domaincities and villages
Exampleeg. the city of Milan is situated in Milan(MI) province, Lombardy
SourceGeographical references
Robot and gadget jobsbots are usefull
Proposed byدوستدار ایران بزرگ (talk) 11:29, 31 March 2013 (UTC)
  •   Comment I think that P131 is so general and at least we need a specific qualifier to narrow the concept. Province is a specific kind of administrative units. If you want to generalize P131 to all types of administrative units then there would be no need to properties like Property:P500 and Property:P17 supposing that in the same way these can be conveyed by a possible generalizing property like "inside continent". Having this assumption in mind we may say "Moscow is inside continent Asia" instead of saying "Moscow is in country Russia". دوستدار ایران بزرگ (talk) 19:46, 12 May 2013 (UTC)

interleaves with / verzahnt mit / FRENCH / RUSSIAN / OTHERS

Descriptionused for stratigraphic formations to indicate if the interleave with other formations
 
Interleaving can be observed between sedimentary units of any scale and composition.
Data typeItem
Template parametercurrently not in any infobox
Domainstratigraphic formations, groups and members
Allowed valuesother stratigraphic formations, groups and members
ExampleQ1009776 interleaves with Q2339647 and Q1557184
Sourcesources are stratigraphic tables that are published by geologic surveys
Robot and gadget jobsas of now the parameter is missing in the infobox so the data is probably not structured enough for a bot.
Proposed byTobias1984 (talk)

Improve the structure of stratigraphic information. Tobias1984 (talk) 15:53, 9 April 2013 (UTC)

  Support - lateral facies variations are really common. Mikenorton (talk) 14:03, 28 April 2013 (UTC)
  Support - --Chris.urs-o (talk) 15:38, 12 May 2013 (UTC)

variant of

   Not done
DescriptionOther aircraft or design which this aircraft is a variant, descendent, or version of
Data typeItem
Example<C-47 Skytrain> variant of <Douglas DC-3>
Proposed byJoshbaumgartner (talk)

State, phase

Descriptionindication of the state or phase of the matter at which the measure was made
Data typeItem
Template parameterused in chembox
Domainchemistry, physic
Allowed valuessolid, liquid, gas
Exampleheat capacity= xx kJ/kg °C at yy °C (gas)
Proposed bySnipre (talk) 12:41, 20 April 2013 (UTC)
  Support --Tobias1984 (talk) 19:53, 25 April 2013 (UTC)
  Support Emw (talk) 14:55, 27 April 2013 (UTC)

Location of scientific description

   Not done
Descriptionthe publication, where the first scientific description was published
Data typeString
Example 1MISSING
Example 2MISSING
Example 3MISSING
Proposed bySoulkeeper (talk) 16:01, 6 February 2013 (UTC) Nope, it wasn't me, I only commented on it. - Soulkeeper (talk) 14:32, 10 May 2013 (UTC)

The property name "Location of scientific description" could be misconstrued to refer to the geographic location where the type specimen was found.-Soulkeeper (talk) 16:01, 6 February 2013 (UTC)

  • @Soulkeeper. Sorry about putting you in the proposal. I assumed that you were the creator. I think this can be archived now anyway unless somebody still wants to add something. --Tobias1984 (talk) 15:12, 10 May 2013 (UTC)

Host country / Austragungsland

   Not done
Descriptioncountry in which the event takes/took place
Data typeItem
Template parameter"Country" in en:template:Infobox international football competition (and many others)
Domainevent
Allowed valuescountries
Exampleen:2010 FIFA World Cup: "South Africa"; en:Eurovision Song Contest 2009: "Russia", etc.
Proposed by--Kompakt (talk) 08:21, 26 April 2013 (UTC)
  Oppose redundant with country. Joshbaumgartner (talk) 04:49, 10 May 2013 (UTC)
I reconsidered my proposal and now agree with Joshbaumgartner. The already existing property P17 seems to be sufficient.--Kompakt (talk) 09:37, 12 May 2013 (UTC)
  Archived as withdrawn by proposer. Joshbaumgartner (talk) 00:10, 13 May 2013 (UTC)

Number of participating countries / Anzahl teilnehmender Länder / nombre de pays participants

   Not done
Descriptionnumber of participating countries of an international event.
Data typeQuantity
Template parameter"Nations participating" in en:template:Infobox Olympic games
Domaininternational events
Example2008 Summer Olympics => "204" (nations)
Proposed by--Kompakt (talk) 19:06, 29 April 2013 (UTC)

I'm not sure whether this property could also be expressed using "number of participants" along with some sort of qualifier. In this case the property would be obsolete of course.--Kompakt (talk) 19:08, 29 April 2013 (UTC)

  Oppose. As you're mentioned itself, a more generic property "number of participants" should be used, together with qualifiers. Or, at all: No such property because the number can be calculated by the sum of entries of "participants" easily. --Nightwish62 (talk) 10:20, 11 May 2013 (UTC)
Very well; so this property isn't needed. Anyway thanks for your clarification.--Kompakt (talk) 09:46, 12 May 2013 (UTC)
  Archived as withdrawn by proposer. Joshbaumgartner (talk) 00:23, 13 May 2013 (UTC)

armament for

   Not done
DescriptionSystem weapon is used on
Data typeItem
Example<AIM-120 AMRAAM> armament for <Boeing F/A-18E/F Super Hornet>
Proposed byJoshbaumgartner (talk)
  Oppose I think it is enough to have an "armament" property. The reverse logic can be querried. --Tobias1984 (talk) 07:50, 30 April 2013 (UTC)
  Comment I agree with you that the paired properties are probably not appropriate until and if support for automatic pairing is added. Joshbaumgartner (talk)
  Archived as withdrawn by proposer. Joshbaumgartner (talk) 07:12, 13 May 2013 (UTC)

powerplant for

   Not done
DescriptionAircraft on which engine is used
Data typeItem
Example<Pratt & Whitney JT8D> powerplant for <Boeing 737>
Proposed byJoshbaumgartner (talk)
  Oppose can be queried from property "powerplant". Might be implemented when bi-directional properties are created. --Tobias1984 (talk) 14:11, 30 April 2013 (UTC)
I agree, this is not needed. Joshbaumgartner (talk) 07:12, 13 May 2013 (UTC)
  Archived as withdrawn by proposer. Joshbaumgartner (talk) 07:12, 13 May 2013 (UTC)

powerplant

   Done: powered by (P516) (Talk and documentation)
DescriptionEngines used to power the aircraft
Data typeItem
Example<Boeing 737> powerplant <Pratt & Whitney JT8D>
Proposed byJoshbaumgartner (talk)
  •   Support but might need qualifiers for different years/makes/models/types of boeing 737. --Tobias1984 (talk) 14:10, 30 April 2013 (UTC)
    •   Comment I totally agree that qualifiers will be useful, and should be added. There are a lot of different scenarios that can play out for this so perhaps once the 'powerplant' property is being used, it will become more clear exactly what they should be. Joshbaumgartner (talk)
  Done as P:P516. Joshbaumgartner (talk) 07:43, 13 May 2013 (UTC)

Interaction / Wechselwirkung

   Done: interaction (P517) (Talk and documentation)
DescriptionThis particle is subject to the interaction
Data typeItem
Template parameterde:Vorlage:Infobox Teilchen
Domainparticles (electrons, neutrons, photons, ...)
Allowed values4 en:fundamental interactions: strong interaction, weak interaction, electromagnetic interaction, gravitational interaction
Examplephoton = electromagnetic interation; electron = weak + electromagnetic + gravitational interaction
Proposed bySvebert (talk) 15:02, 17 March 2013 (UTC)
  Support as long as each of the potential interactions are items in their own right. Joshbaumgartner (talk) 06:51, 13 May 2013 (UTC)

Part concerned

Descriptionpart of the item for which the claim is relevant
Data typeItem
Proposed byUser:Zolo

I think it has been proposed before but I cant find it. It would be useful in many contexts (for instance, a part of a building is protected, or is owned by a particular company). --Zolo (talk) 09:26, 4 May 2013 (UTC)

Yes, see Wikidata:Property proposal/Archive/Place#Parts_.2F_.2F. It's makes more sense as a generic property, so full   Support. -- Lavallen (block) 09:59, 4 May 2013 (UTC)
When discussing items and properties, could you please provide labels for items and properties? It's nice to be able to reason about a discussion without having to click on an item or enter http://www.wikidata.org/wiki/Property:P156 into a new tab to understand what's being discussed. Emw (talk) 11:37, 4 May 2013 (UTC)

Other examples would be:

Gare de l'Est:

  • Owner: SNCF (waiting hall) RFF (platforms)
  • Instance of monument historique (roofs, deooration)

Belly Amphora by the Andokides Painter:

  • Creator: Andokides painter (black figure ceramic) Lysippidès (red figure ceramic)

Actually, just having an item as the value is not extremely precise, but I do not see any other solution. --Zolo (talk) 11:14, 4 May 2013 (UTC)

If the concerned parts are items themselves, why not use properties directly on them, instead of on the item they are parts of. Like this:
  • Item: Waiting hall of Gare de l'Est
    • Property: part of. Value: Gare de l'Est
    • Property: owner. Value: SNCF
  • Item: Platforms of Gare de l'Est
    • Property: part of. Value: Gare de l'Est
    • Property: owner. Value: RFF
Etc. That way seems more simple to me. Byrial (talk) 11:28, 4 May 2013 (UTC)
That would have some good sides, but in some cases, in some cases I am weary that things would go complicated. For instance, French protected buildings like the Gare de l'Est are listed in a database, with a paramter stating which part are protected ([1]). That would be relatively easy to copy that here: "Gare de l'Est: instance of monument historique. Datbabase ID XX. Parts concerned Roof (using the generic roof item). But linking it to the database / official protection decree may become more redundant and intricated if we use separate items for the protected parts. Another example would be a painting with Painter X doing the characters and Painter Y doing the landscape (though arguable, a "role" qualifier may be more appropriate for this case). --Zolo (talk) 11:46, 4 May 2013 (UTC)
I see your point, and I didn't think of using generic items before. For the ownership, I suppose that you can also use generic items for the halls and platforms. That will probably be better than creating a new item for each concerned part. Byrial (talk) 12:14, 4 May 2013 (UTC)
What about values that don't have items, like 'black figure ceramic' and 'red figure ceramic' in the Belly Amphora example above? Emw (talk) 12:32, 4 May 2013 (UTC)
If there where no items, (and that is the case frequently), then I would have used "North", "Central" and "South" as items in my example. But that does not work in Byrials version. -- Lavallen (block) 13:06, 4 May 2013 (UTC)
Actually, for red-figure ceramic we have Q633683, but it is true that there are cases that seem more complicated (for listed buildings, there are plenty of things like: protected part: second window from the right). --Zolo (talk) 13:35, 4 May 2013 (UTC)

ORCID

   Done: ORCID iD (P496) (Talk and documentation)
DescriptionIdentifier for researchers and academic authors/contributors
Data typeString
Template parameter|ORCID=, in en:template:authority control
DomainPeople
Allowed valuesas per Property:P213 - four four-digit groups
ExampleMike Taylor (Q8134165) has ORCID 0000 0002 1003 5675
Sourcehttp://orcid.org
Robot and gadget jobsUser:VIAFbot will import this from enwiki, possibly other wikis, and potentially external DBs.
Proposed byAndrew Gray (talk)

The ORCID is an open identifier for researchers. It is linked to ISNI (P213) but the two identifiers currently exist in parallel and it is possible for individuals to have both, so we need a seperate identifier. Andrew Gray (talk) 12:33, 11 April 2013 (UTC)

  Support. Tpt (talk) 13:35, 11 April 2013 (UTC)

CBDB identifier

   Done: CBDB ID (P497) (Talk and documentation)
DescriptionChina Biographical Database Project (CBDB) identifier for ancient Chinese people
Data typeString
DomainPerson
Allowed values7-digit string
ExampleOuyang Xiu - 0001384 (link: Chinese English)
Proposed byStevenliuyi (talk)

CBDB is a respectable database of ancient Chinese people, developed by Peking University, Academia Sinica and Harvard University. --Stevenliuyi (talk) 19:00, 29 April 2013 (UTC)

  Support--凡其Fanchy 16:42, 4 May 2013 (UTC)

powerplant for

   Not done
DescriptionAircraft on which engine is used
Data typeItem
Example<Pratt & Whitney JT8D> powerplant for <Boeing 737>
Proposed byJoshbaumgartner (talk)
  Oppose can be queried from property "powerplant". Might be implemented when bi-directional properties are created. --Tobias1984 (talk) 14:11, 30 April 2013 (UTC)
  Archived I agree with tobias, so I am withdrawing and archiving this one. Joshbaumgartner (talk) 05:38, 16 May 2013 (UTC)

armament

   Done: armament (P520) (Talk and documentation)
DescriptionWeaponry aircraft is armed with
Data typeItem
Example<Boeing F/A-18E/F Super Hornet> weapon <AIM-120 AMRAAM>
Proposed byJoshbaumgartner (talk)
  •   Comment I don't know how that works with airplanes. Is the whole series fitted with these "AIM-120 AMRAAMs" or would qualifiers be needed to distinguish between different series/types/models/makes of "Boeing F/A-18E/F Super Hornets"? --Tobias1984 (talk) 07:54, 30 April 2013 (UTC)
  Comment Armament can be even more complicated than powerplants. They can run the gamut from simple fixed armament that is standard throughout a family or series, to highly configurable complex weapon systems (becoming more the norm these days). I figure best to start with a simple 'item' datatype so that any weapon system or element notable enough to warrant an item and which is used (standard or optionally) on an aircraft can be listed. Qualifiers would become very useful to further define how many can be carried, ammunition loads, optional load-outs, version compatibility, operator-specific systems, etc. Joshbaumgartner (talk)
  Done as P:P520. Joshbaumgartner (talk) 05:44, 16 May 2013 (UTC)

main engine

   Not done
Data typeMISSING
Example 1MISSING
Example 2MISSING
Example 3MISSING
  Archived I'm archiving it for now...if others agree it is a waste of archive space it can always be deleted. Joshbaumgartner (talk) 05:48, 16 May 2013 (UTC)

surface

   Not done
DescriptionRunway surface material (qualifier property for use with 'runway' property)
Data typeItem
Template parameter (runways section)
Domainairport, runway
Example<Portland International Airport> runway <10R/28L> surface <concrete>
SourceAirport infoboxes have runway data, including identifier, length, and surface
Proposed byJoshbaumgartner (talk) 09:21, 1 May 2013 (UTC)
  Comment: This is a qualifier property to support the 'runway' property proposal above. Joshbaumgartner (talk) 09:21, 1 May 2013 (UTC)
  Archived: Withdrawing this as it is apparent that 'material used' can cover this for now. Joshbaumgartner (talk) 06:10, 16 May 2013 (UTC)

scheduled service destination

DescriptionAirports/Stations served by regular/scheduled service from this Airport or station
Data typeItem
Domainairport (other transportation ports/stations as well)
Example<Seattle-Tacoma International Airport> scheduled service destination <Portland International Airport>
Robot and gadget jobsWikipedia airport articles have a destination table with this data
Proposed byJoshbaumgartner (talk) 09:21, 1 May 2013 (UTC)
  Comment: This brings the data maintained in destination tables on airport articles to wikidata. Qualifier 'operator' can indicate airlines operating to destinations. Other qualifiers can be developed to add details such as frequency, seasonal adjustments, cargo-only service, operated dates, etc. Joshbaumgartner (talk) 09:21, 1 May 2013 (UTC)
  Done Joshbaumgartner (talk) 06:18, 16 May 2013 (UTC)

Orbit type / Тип орбиты

Descriptionтип орбиты
Data typeItem
Template parameterru:Шаблон:Космический аппарат, ru:Шаблон:Космическая экспедиция Тип_орбиты
Domainкосмические аппараты не совершающие крупных манёвров
Allowed valuesгеостационарная орбита, солнечно-синхронная орбита, полярная орбита, высокая эллиптическая орбита и т. д.
ExampleЯмал-201, тип орбиты: геостационарная орбита
Sourceсайт NASA, launchlog, карточки в статьях, список запусков и т. д.
Proposed by— Ivan A. Krestinin (talk) 19:20, 1 April 2013 (UTC)
  Comment low earth orbit, medium earth orbit, molniya orbit are some othersSecretlondon (talk) 14:10, 27 April 2013 (UTC)
  Support sounds useful. --Tobias1984 (talk) 18:37, 30 April 2013 (UTC)
  Support Secretlondon (talk) 10:11, 6 May 2013 (UTC)

Temporal range start

DescriptionThe beginning of a fossil record, sedimentation, ice age (...) relative to the geologic time scale.
Data typeItem
Template parametertaxobox |fossil_range =
DomainAnimals, Plants, Fossils, Stratigraphic units,
Allowed valuesStages of the Geologic Time Scale
ExampleTyrannosaurus = Maastrichtian
Old Red Sandstone = Silurian
SourceScientific literature and databases
Robot and gadget jobsSome data could be collected for fossil and living animals.
Proposed byTobias1984 (talk)
Discussion
  Support (see #Temporal_range) Eran (talk) 15:12, 12 May 2013 (UTC)
  Support Joshbaumgartner (talk) 06:51, 13 May 2013 (UTC)
  Support - Soulkeeper (talk) 10:13, 13 May 2013 (UTC)

Temporal range end

DescriptionThe end of a fossil record, sedimentation, ice age (...) relative to the geologic time scale.
Data typeItem
Template parametertaxobox |fossil_range =
DomainAnimals, Plants, Fossils, Stratigraphic units,
Allowed valuesStages of the Geologic Time Scale
ExampleTyrannosaurus = Maastrichtian (because this is set it is extinct)
Old Red Sandstone = Carboniferous
SourceScientific literature and databases
Robot and gadget jobsSome data could be collected for fossil and living animals.
Proposed byTobias1984 (talk)
Discussion
  Support Joshbaumgartner (talk) 06:51, 13 May 2013 (UTC)
  Support. And for extant taxa, this property can be set to either "No value" or future (but that discussion can wait until the property has been made). - Soulkeeper (talk) 10:19, 13 May 2013 (UTC)

Temporal range (Single property)

   Not done
DescriptionFor extinct species, the period when it lived
Data typeItem
ExamplePrecambrian, Cambrian, Ordovician, Silurian, Devonian, Carboniferous, Permian, Triassic, Jurassic, Cretaceous, Paleogene, Neogene
Proposed byEran (talk) 20:41, 26 April 2013 (UTC)

It is displayed in infoboxs for extinct species (en:Tyrannosaurus). Sometimes more than 1 value should be added. Eran (talk) 20:41, 26 April 2013 (UTC)

Agreed. That could also solve the problem of differentiating extinct and extant species. - Soulkeeper (talk) 14:38, 10 May 2013 (UTC)

Subitem

   Not done
DescriptionThe subitem is an item which is part (subtheme, branch) of the current item. E. g. Lefthandedness is subitem of Handedness, Geometry is subtheme of Mathematics, Androphilia is subitem of Androphilia and gynephilia, Saint Cyril is subitem of Saints Cyril and Methodius, Rail transport is subitem of Track transport (Drážní doprava in Czech, including trolleybus and aerial cableway transport) etc. Complementary to "Upper item".
Data typeItem
Template parameter(en:Template:General geometry, branches)
Domainabstract terms, branches and discpilines of study, science, work or other activities etc., two-item and multi-item articles (in cases where formulation "part of" or "member of" is unsuitable), imperfectly synonymic terms etc.
Example 1MISSING
Example 2MISSING
Example 3MISSING
Proposed byŠJů (talk) 01:51, 13 March 2013 (UTC)
  • Comments: proposed to compensate (at least partially) disabled functionality of anchors (#) in interwikis and to capture this specific type of relation between items. --ŠJů (talk) 01:51, 13 March 2013 (UTC)
See #part of / teil von / fr / Часть on the page. Infovarius (talk) 20:18, 23 March 2013 (UTC)
  Oppose Already covered by instance of, subclass of, and part of. Silver hr (talk) 04:12, 31 March 2013 (UTC)
  Oppose +1 Infovarius (talk) 19:48, 2 April 2013 (UTC)

Upper item

   Not done
DescriptionThe upper item is an item (subtheme, branch) which covers (includes) the current item. E. g. Handedness is upper item to Lefthandedness, Mathematics is upper item to Geometry, Androphilia and gynephilia is upper item to Androphilia, Saints Cyril and Methodius is upper item to Saint Cyril. Complementary to "Subitem".
Data typeItem
Domainabstract terms, branches and discpilines of study, science, work or other activities etc., two-item articles (in cases where formulation "part of" or "member of" is unsuitable)
Example 1MISSING
Example 2MISSING
Example 3MISSING
Proposed byŠJů (talk) 01:51, 13 March 2013 (UTC)
  • Comments: proposed to compensate (at least partially) disabled functionality of anchors (#) in interwikis and to capture this specific type of relation between items. --ŠJů (talk) 01:51, 13 March 2013 (UTC)
  Oppose Already covered by instance of, subclass of, and part of. Silver hr (talk) 04:12, 31 March 2013 (UTC)
Proposed property is like inverse to those all. May be "consists of" would be appropriate name? Infovarius (talk) 19:48, 2 April 2013 (UTC)
Explicitly stating each member of a class seems it could get very problematic. For example, the list of "upper item" claims for "person" would have hundreds of thousands of entries. Emw (talk) 02:38, 3 April 2013 (UTC)

Municipality code in Sweden

Description"kommunkod": municipality code for Sweden
Data typeString
Template parameter"kommunkod" in sv:Template:Kommunfakta
Domainplace
Allowed valueskommunkod=dddd
ExampleQ515409 => 1083
Sourcesv:Template:Kommunfakta
Proposed byWikidata:Property_proposal/Place#Statistics_Sweden-code_.2F_SCB-kod.2F

More properties will come from the original proposal on Wikidata:Property proposal/Place who had the original header: "Statistics Sweden-code / SCB-kod/". -- Lavallen (block) 18:18, 16 May 2013 (UTC)

Parts / /

   Withdrawn
DescriptionA qualifier-property for P156 and maybe others.
Data typeItem
Domainplace/organisation/persons
Allowed valuesdepends of type of item
ExampleSee how I used the sandbox-property under P156 in Q10433566.
Robot and gadget jobscould be difficult in several cases
Proposed byLavallen (block)

Q10433566 (Boteå landskommun) was a municipality in Sweden 1952-1970. The nothern part became a part of Sollefteå Municipality and the sothern part became a part of Kramfors Municipality. I have no good name for this property (not even in my own language), but I see a need for something like this. -- Lavallen (block) 05:13, 22 April 2013 (UTC)

Maybe it also can be used for the succession of titles in for example Charles V, who was replaced by Ferdinand in Austria, and Filip in Spain. Another example is Elisabeth II who has already been replaced as chief of state in several nations. -- Lavallen (block) 06:44, 22 April 2013 (UTC)
I was also wondering about a qualifier in Q1878978 (property: creator), to mean Painter A made the red ceramic part and painter B the black ceramic part. Do you think it would be ok to use this property as well ? --Zolo (talk) 08:46, 24 April 2013 (UTC)
I think so, time to move this to /Generic instead? -- Lavallen (block) 13:18, 24 April 2013 (UTC)
  Comment If I understand correctly, you want to express for example that an administrative unit A with administrative subunits A1, A2, A3, A4 no longer exists and that A1, A2, and A3 are now parts of administrative unit B, and A4 is part of administrative unit C. If I'm correct, then this, although it's a slightly complex case, can be inferred if you record the relevant data: A1, A2, A3, A4 is in the administrative unit A (+temporal qualifier 1952-1970); A1, A2, A3 is in the administrative unit B; A4 is in the administrative unit C. Silver hr (talk) 20:26, 26 April 2013 (UTC)
No, it's not completly correct. A1, A2, A3 and A4 are not always administrative subunits, they are a geographic description. I could have used items like Q659 as A1/A2/A3/A4. And I cannot add Q659 as a part of anything like A. -- Lavallen (block) 16:14, 27 April 2013 (UTC)
In my example above, A1/A2/A3/A4 stoped to act as an administrative unit 1862 (if there ever where any, since local administration outside cities where introduced 1862), but they still exists as a geographic units. -- Lavallen (block) 16:20, 27 April 2013 (UTC)
I withdraw this proposal and support Wikidata:Property proposal/Archive/Generic#Part concerned instead. -- Lavallen (block) 10:12, 4 May 2013 (UTC)


Island

   Done: no label (P526) (Talk and documentation)
Descriptionisland the place is located on
Data typeItem
DomainGeographic features/places on islands
Allowed valuesislands
ExampleClifton => Union Island
Proposed by--  Docu  at 19:38, 9 May 2013 (UTC)
  Support -- MichaelSchoenitzer (talk) 21:21, 14 May 2013 (UTC)

Qualifier property: astronomic catalog

   Not done
Descriptionspecify the astronomic catalog of astronomic object names listed by the property catalog code
Data typeitem or text-invalid datatype (not in Module:i18n/datatype)
Template parameterused by property catalog code
Domainastronomical objects
Allowed valuesif datatype is item, only items with property instance of equal at astronomic catalog
Example<Andromeda Galaxy> catalog code <M31> qualifier: astronomic catalog <Messier objects>; catalog code <NGC 224> qualifier: astronomic catalog <New General Catalogue>
Sourcesee en:Astronomical catalog. Vizier database contains the data of more than 10 thousand different astronomic catalogs.
Proposed byPaperoastro (talk)
Discussion

Qualifier property to use with catalog code property to manage the huge number of catalog names of astronomical objects. The "ideal" datatype should be item, but this would limit the catalogs to those available in Wikidata. Paperoastro (talk) 14:31, 7 May 2013 (UTC)

You won't add each time the catalog name and the catalog code: if they are linked better add the code in the item of the catalog. Then can the catalog be the source of other informations ? If yesso you can use the catalog item to source data of the astronomic object and you don't need to specify the catalog as a property of the astronomic object. Again the catalog is not a real property of the astronomic object but only a place where you can get information so it is a data source. Snipre (talk) 22:50, 8 May 2013 (UTC)
Use catalogs as sources is a good idea: they can be used also for sourcing other informations. I'm sorry, but I don't understand the meaning of your sentence <<if they are linked better add the code in the item of the catalog.>> Could you explain me, please? After your explanation, I will close this proposal. --Paperoastro (talk) 09:28, 11 May 2013 (UTC)

Catalog code

   Done: catalog code (P528) (Talk and documentation)
Descriptionthe catalogue name of an astronomic object. This property need a qualifier to specify the catalog
Data typeString
Template parameterall name and other names parameters in en:Category:Astronomy infobox templates
Domainastronomical objects
Allowed valuesevery catalogue has a specific and rigorous syntax established by the compilers
Example<Andromeda Galaxy> catalog code <M31>, <NGC 224>
Sourcesee en:Astronomical catalog. Vizier database contains the data of more than 10 thousand different astronomic catalogs.
Proposed byPaperoastro (talk)
Discussion

This property, with a qualifier, can manage the huge number of catalog names of astronomical objects. Paperoastro (talk) 14:10, 7 May 2013 (UTC)


Year / Jahr / Année / год / jaar / سال

   Not done
Descriptionyear of the event and creation of the creative work
Data typeitem or string or even number-invalid datatype (not in Module:i18n/datatype)
Template parameteryear, "|date" in Infobox earthquake, next_year and previous_year can be easily calculated and used in Infobox election, "| This (single|song|album)" in infoboxes of musics (in chronology part). I didn't check other wikis' infoboxes
Domainevents and creative works
Allowed valuesyears
Example2010 for "category:2010 (singles|songs|films|albums|books)", 2009 for [[w:2009 Iranian election]]
Sourcecategories, infoboxes of events
Robot and gadget jobsthey can use categories and infoboxes
Proposed byAmir (talk)

I think it's a common data and can be updated and used very easily and rapidly in so many infoboxes and other contents. Amir (talk) 14:10, 24 April 2013 (UTC)

  Oppose The events and creative works should have some statements about their duration or creation, which should be of Time datatype (not yet available, though). For other uses, the name of the property leaves to much uncertainty about how it should be used.--83.240.94.18 18:11, 25 April 2013 (UTC)

death description / / / / descripción de muerte (es)

   Not done
DescriptionWikipedia article describing subject's death
Data typeItem
Domainperson
ExampleQ2831 (Michael Jackson) => Q761887 (death of Michael Jackson), Q352 (Adolf Hitler) => Q1993476 (death of Adolf Hitler), etc.
Proposed byThe Anonymouse (talk | contribs)
Discussion

This would be useful for people whose death is notable. Compare to something like Property:P163 (flag description) or Property:P418 (seal description). The Anonymouse (talk | contribs) 05:09, 3 May 2013 (UTC)

  Withdrawn by proposer Seems to be unnecessary because of WD:Property proposal/Generic#subject of. The Anonymouse (talk | contribs) 19:16, 14 May 2013 (UTC)


Chairperson / Vorsitzender / Président

   Done: chairperson (P488) (Talk and documentation)
Descriptionchairperson of a deliberative body presiding member of an organisation or body
Data typeItem
Domainpersons
Allowed valuesitems of persons which are chairs of a deliberative body an organisation or body
ExampleOn the item of the Bundestag: Norbert Lammert, president; On the item of the US House of Representatives: John Boehner, speaker; On the item of CDU: Angela Merkel, chairperson; etc.
Proposed byMF-W
Edited the proposal (with MF-W's agreement). SPQRobin (talk) 19:02, 4 May 2013 (UTC)

--MF-W 22:26, 8 April 2013 (UTC)

Created at Property:P488. SPQRobin (talk) 19:08, 4 May 2013 (UTC)


runway

   Done: runway (P529) (Talk and documentation)
DescriptionRunway name(s) at airport
Data typeString
Template parameter (runways section)
Domainairport
Example<Portland International Airport> runway <3/21> / <10L/28R> / <10R/28L>
SourceAirport infoboxes have runway data, including identifier, length, and surface
Proposed byJoshbaumgartner (talk) 09:21, 1 May 2013 (UTC)
  Comment: Runway identifiers and notes are key information about an airport. Qualifiers 'length', 'width', and 'surface' can be used (when available) to further enhance data. Joshbaumgartner (talk) 09:21, 1 May 2013 (UTC)

Diplomatic relation

Descriptiondiplomatic relations of the country
Data typeItem
Domaincountry
Example<United States of America> diplomatic relation <People's Republic of China>
Proposed by-Stevenliuyi (talk)

Several qualifiers can be used along with this property. A full example would be:

<United States of America> diplomatic relation <People's Republic of China>

--Stevenliuyi (talk) 00:48, 8 May 2013 (UTC)

  Support —★PοωερZtalk 11:34, 8 May 2013 (UTC)

Thesaurus

DescriptionA link to a national thesaurus (Q179797).
Data typeString
Template parameterauthority control
DomainGeneral knowledge (not a specific domain, but mainly general concepts).
Allowed values\d+
ExampleQ11660 is lemma 7235 in the Italian BNCF thesaurus
Sourcehttp://it.wikipedia.org/wiki/Progetto:Coordinamento/Bibliografia_e_fonti/Lista_lemmi_Thesaurus_del_Nuovo_Soggettario_BNCF (to be updated). The real source is http://thes.bncf.firenze.sbn.it/
Robot and gadget jobsSamoaBot is ready to import these codes --Ricordisamoa 05:58, 21 April 2013 (UTC)
Proposed byAubrey (talk)

We are organizing the insertion of few thousands links in Italian Wikipedia, in a collaboration with the National Library of Florence (BNCF). Thus we are proposing a property in Wikidata, because we think and hope that this would be useful also to other projects: there are of course other national thesauri out there, and they are likely to be matched with Wikipedia items as does the italian one. Aubrey (talk) 10:04, 17 April 2013 (UTC)

I also want to add that this could be a great opportunity to test Wikidata in the Italian Wikipedia, as this property would be added in around 11'000 pages. On it.wiki the template is almost ready, as the bot to add the template, so we are actually waiting for the wikidata property to be approved. --Aubrey (talk) 12:51, 17 April 2013 (UTC)
Just to make sure what you are trying to do: you'd use the string "7253" on item "Artificial intelligence" (Q11660) and you would want this to link to http://purl.org/bncf/tid/7253 ?
In that case, you might want to create a BNCF specific property. --  Docu  at 03:38, 20 April 2013 (UTC)
Well, the link should be to http://thes.bncf.firenze.sbn.it/termine.php?id=7253 --Ricordisamoa 05:55, 21 April 2013 (UTC)
And we can now use qualifiers to distinguish between different thesauri... --Ricordisamoa 05:56, 21 April 2013 (UTC)
Maybe the sample above should be adapted to illustrate this better, if this is what is proposed. BTW I'm not sure if links can be done based on qualifiers. --  Docu  at 15:34, 21 April 2013 (UTC)
Hi Docu. The aim is simply to be able to link a Wikipedia entry to the same entry in the BNCF Thesaurus. There are IDs available, so I figured out that it was a good idea to propose a property in Wikidata/Authoirity Control. Moreover, this could be useful for other wikipedias in the future... A thesaurus is a specific work, different from other authority control tools. That's the rationale. But I'm not sure it's the best idea. Aubrey (talk) 10:26, 24 April 2013 (UTC)
I think there could be 2 possibilities: one is to have a general property Thesaurus, in which we put the ID and generate the link. With the qualifier, we can state that this relation is from the item and the BNCF Italian thesaurus. So qualifiers will discriminate between different thesauri.
The other option would be having just a BNCF property, and non general thesaurus one. Aubrey (talk) 20:55, 29 April 2013 (UTC)
Any updates? --Ricordisamoa 23:08, 10 May 2013 (UTC)
  Done Property:P508. --Vituzzu (talk) 00:32, 12 May 2013 (UTC)


Port of registry

DescriptionPort of registry of the ship. This is painted on the ship's stern. For the "home port", see Property:P504.
Data typeItem
Template parameter"Ship registry" in w:Template:Infobox ship career, see "Ship registry" on usage guide
Domainterm: ships, watercraft
ExampleA => Hamilton
Proposed byimplicitly by Wikidata:Property_proposal/Archive/7#P504

As we already have "home port", we need this too. --  Docu  at 06:14, 12 May 2013 (UTC)

Target

   Done: target (P533) (Talk and documentation)
Descriptiontarget of a terrorist attack or military operation (generally a location; only a person if it is known to be a specifically targeted assassination)
Data typeItem
Template parametertarget in en:Template:Infobox civilian attack; also related to location parameter
Domainevents such as terrorist attacks or military operations/battles
Allowed valueslocations for attacks, individuals for assassinations (importantly, notable individuals killed in a general attack where they weren't the target are not included); intended target is given, whether or not the attack/operation was successful
ExampleFor September 11 attacks, it'd be World Trade Center, 7 World Trade Center, The Pentagon, and maybe The White House and The Capitol, as both are claimed by prominent individuals to have been the intended target (Shanksville, Pennsylvania/Stonycreek Township would not be included, nor would be any notable victims)
For Truman assassination attempt, it'd be Harry S. Truman, who wasn't hurt, and not Leslie Coffelt, who was killed protecting him
For Battle of Stalingrad it'd be Stalingrad/Volgograd
etc.
Proposed by — PinkAmpers&(Je vous invite à me parler)

I noticed that we didn't have any suitable property to link the 2013 Boston Marathon to the Boston Marathon bombings, and as an attack is largely defined by its target, I think that we should. — PinkAmpers&(Je vous invite à me parler) 02:44, 18 April 2013 (UTC)

Apparently historical events are considered terms. Moving this here from Wikidata:Property proposal/Archive/Event — PinkAmpers&(Je vous invite à me parler) 20:48, 19 April 2013 (UTC)
  Comment This property is clearly useful. However, I think the domain should be wider. This property really applies to both tokens (instances) and types (classes) of attacks and offensives. For example, the targets of a bombing are persons, buildings, structures, etc.; the target of an assassination is a person; the targets of a denial-of-service attack are websites and web services.
I would note that instances of other types of attacks, e.g. cyber attacks like DDoS attacks during the October 2011 South Korean by-election, seem to be applicable subjects for this property. (Wikidata likely won't have items about the particular websites or web services attacked, but specifying the targeted organization or person seems like a reasonable alternative in that case.) Emw (talk) 13:53, 21 April 2013 (UTC)

streak / Strichfarbe / trait

   Done: streak color (P534) (Talk and documentation)
Descriptioncolor of the powder of a mineral
Data typeItem
Template parameteren:template:infobox mineral streak
Domainminerals
Allowed valuescolors
Examplefluorite → white, pyrite → greenish-black to brownish-black, malachite→ light green
Proposed by23PowerZ (talk)

This is a standard characteristic used in mineralogy. See w:Streak (mineralogy) 23PowerZ (talk) 18:39, 18 April 2013 (UTC)

  Comment Please also look at the related request ofcolor (as an item). What should be done with color descriptions that don't have an item? Should "brownish white" and "yellowish white" be items? Would multilingual string be more appropriate? What should the qualifiers do? --Tobias1984 (talk) 20:35, 18 April 2013 (UTC)
I changed datatype to multilingual string as you are right about the silliness of having items like greenish-black.23PowerZ (talk) 10:11, 19 April 2013 (UTC)
 
Color circle by Johannes Itten.
 
HSL color solid.
I actually don't think that items are such a bad idea. User:Chris.urs-o send me the picture on the right. If we use this or a similar scheme there would be very few items that would describe a lot of colors. In this scheme we would have 12 items for colors. Betweenyellow and green we have an item that can be either yellowish green or greenish yellow. Between yellow and orangewe have an item that can be either yellowish orange or orangy yellow. The nice thing about these color wheels is that a search for "yellow" would return three colors, yellow itself and the two neighboring colors. I think done consistently this would be a very good way of doing colors as items. We just need to find a good scheme that everybody will agree to follow. We should have the same for greyscale, brown colors and pastel colors too. --Tobias1984 (talk) 13:01, 19 April 2013 (UTC)
Well, this particular scheme won't work, brightness is missing. When we generalize this much, precise information like dark cherry red for w:Pyrargyrite will be lost. 23PowerZ (talk) 18:28, 19 April 2013 (UTC)
True. We need some sort of a color expert :) --Tobias1984 (talk) 18:50, 19 April 2013 (UTC)
I think that it is good enough, dark is an adjective. Lustre, brightness, saturation and hue are different things. I like the hexadecimal code for colors (en:Web colors). The brightness isn't missing, color space: white → grey → yellow → green → cyan → blue → magenta → red → brown → black. --Chris.urs-o (talk) 06:50, 20 April 2013 (UTC)
BTW, I think that I'm a color expert as I'm an IMA mineral list expert ;) --Chris.urs-o (talk) 07:14, 20 April 2013 (UTC)
  • I would strongly oppose color as multilingual string. It would mean that the string had to be translated to all languages for each item using the property. If the value is an item, each color only has to be translated once. There is no sillyness about having items for "greenish-black". We can create items for every nuance of color, it would still avoid a lot of unnecessary translation work.Byrial (talk) 22:22, 26 April 2013 (UTC)
Granted. If no one has a problem with that, I'll change it back to item. —★PοωερZtalk 14:49, 28 April 2013 (UTC)
  Support suggestion by User:Byrial. --Tobias1984 (talk) 14:55, 28 April 2013 (UTC)
  • Only if we introduce a qualifier for "streak color". Mixing up these two sets of colors would be really confusing for mineral queries. I would also support the idea of this property being a qualifier. I am not sure what would be better in the long run.--Tobias1984 (talk) 15:16, 30 April 2013 (UTC)
I see the need to distingiush streak from the ordinary color. I guess that it will be more simple to have a separate property for streak color to avoid they are mixed up. Byrial (talk) 15:39, 30 April 2013 (UTC)
Hi, streak color and crystal color do not really correlate. A lot of minerals can differ in color eg. quartz from green to red, from yellow to violett. But the streak is always white, thats the trick. Up to now, I do not believe that it is possible to put it to RGB-Values to to Cie-Lab. Some minerals differ in brownish colors to black (Ilmenite or other iron containing minerals.) If I did not understood the discussion right, please ignore this part. BR --Krizu (talk) 09:30, 21 May 2013 (UTC)

Extinct

   Not done
DescriptionWhether the taxon is extinct
Data typeboolean-invalid datatype (not in Module:i18n/datatype)
Template parameterextinct in enwiki templates as en:Template:Taxonomy/Nedcolbertia (and other auto taxobox)
Example 1MISSING
Example 2MISSING
Example 3MISSING
Proposed byEran (talk) 20:41, 26 April 2013 (UTC)

Such data could be useful for creating taxobox of extinct species/genra etc (see also: en:Template talk:Taxobox#Taxobox 2013).Eran (talk) 20:41, 26 April 2013 (UTC)

  Support --Tobias1984 (talk) 09:51, 27 April 2013 (UTC)
  Oppose. It can be covered by IUC status=extinct. Infovarius (talk) 18:55, 28 April 2013 (UTC)
  Comment IUCN status extinct isn't the same: IUCN gives extinct status for species that became extinct in the modern times (-500 years), and not for dinusaurus for example. User:132.65.153.50
  Comment – Yes, it is the same. The problem is that species which became extinct in prehistoric time are not in the IUCN Red List, and thus doesn't have an IUCN conservation status. The same may also be true for some historic species. So a more general conversation status property could be needed, but I   Oppose just to have a boolean property. More than two categories may be useful as in the IUCN list. Byrial (talk) 11:06, 9 May 2013 (UTC)
  Comment Fossil species that have a temporal range that ends before the Holocene are automatically extinct. Same is true for Holocene species that have a temporal range beginning and ending in the Holocene. If the end of a temporal range is not set, then a species is not extinct. This property is probably useful, if one knows a species went extinct, but doesn't know when that happened.--Tobias1984 (talk) 05:51, 29 April 2013 (UTC)
  Oppose – If it is not present on the official IUCN Red List, then there aren't sources, and nobody could effectively prove that dinosaurs are extinct (we all know that they are extinct, but everything is subjective without official sources). --Ricordisamoa 11:24, 9 May 2013 (UTC)
  Comment – There are other sources for conservation status than the IUCN Red List. There may be scientific reports, and there arenational lists. Byrial (talk) 13:22, 9 May 2013 (UTC)
  Oppose I agree that IUC status should be up for the task but may need to be broadened a bit if their are taxons with a status that are not specifically IUC listed. Change name to 'conservation status' or some such and have IUC as a source? Probably that is a matter for P141's talk page, but I think a solution along those lines is better than adding extra properties.Joshbaumgartner (talk) 06:51, 13 May 2013 (UTC)

Code, Acronym or Abbrevation

Instead of creating a lot of different text properties, we may use this generic property whenever there is only one code standard that should be shown in most Wikipedias.

Later a multi-lingual version called "Acronyms" may be created:

Mange01 (talk) 16:35, 7 March 2013 (UTC)

  Support with the suggestion to extend this property to abbreviations of more than one letter: for example it would be very useful for the abbreviation field of the Infobox constellation (three letters) --Paperoastro (talk) 17:34, 7 March 2013 (UTC)

  Support Emw (talk) 03:16, 8 March 2013 (UTC)

  Oppose "code" (but updated, support "abbreviation", see below) -- I am generally for properties that are as generic as possible, but this is quite generic! Look at an infobox for an element or molecule and tell me that "code" is descriptive against other string values. I'm not sure I can support a property called "code" in any context -- I can't think of a case where the expected value would not be ambiguous. Espeso (talk) 15:16, 8 March 2013 (UTC)

  Oppose. Agree with Espeso, this is way too generic of a property.—Ëzhiki (Igels Hérissonovich Ïzhakoff-Amursky) • (yo?); March 8, 2013; 18:57 (UTC)

  Question: how is this different than an alias? Emw (talk) 03:44, 9 March 2013 (UTC)

Very different. This suggestion corresponds to a comon infobox name "symbol", or "code". It is useful if we in an infobox wants to link to the item, while an alias is not usefeul because we can not know that the alias shows a standard code.  – The preceding unsigned comment was added by Mange01 (talk • contribs) at 02:06, 10 March 2013‎ (UTC).

  Oppose: too generic unclear title. -- MichaelSchoenitzer (talk) 14:33, 9 March 2013 (UTC)

  Comment: Why not a property "abbreviation"? Would cover a lot without beeing to generic. -- MichaelSchoenitzer (talk) 14:43, 9 March 2013 (UTC)
Ok. "Acronym" seemes to be an even more common parameter name in infoboxes. "Code" is quite uncommon. "Symbol" is not a good name, because in some infoboxes that parameter name refers to an image, in others, it is a linked item, and in other a single character or a text, for example "chemical symbol". Mange01 (talk) 02:11, 10 March 2013 (UTC)
  • I   Support "abbreviation" as a more general variant of "acronym" and much more realizable than "code", which I opposed. The abbreviation property must reflect an accepted abbreviation of the topic name itself, in the relevant language. This implies that the property should not have a monolingual data type so can't be created yet. Such a property would, by definition, duplicate part of what aliases often contain, which is fine. Finally, contradicting the original proposal, there can be more than one abbreviation: on "United States of America" you could have "USA, U.S.A., US, U.S."! Espeso (talk) 17:52, 19 March 2013 (UTC)
  •   Oppose – This is not about the item, but about the names of the item. Even in the same language the item can have several synonymous names. Any abbreviation for a language is best decided in the Wikipedia of language. -- Byrial (talk) 17:37, 20 April 2013 (UTC)
  •   Oppose Abbrivations are not always the same in different languages. This should rather be ISO codes, or similar.--Snaevar (talk) 13:14, 22 May 2013 (UTC)

Dewey Decimal Classification / DDC / Classification décimale de Dewey

  • Description: proprietary library classification system created by Melvil Dewey in 1876
  • Infobox parameter: de:Vorlage:GNDlink
  • Datatype: StringValue
  • Domain:
  • Allowed values:
  • Source: en:List of Dewey Decimal classes; DNB
  • Examples: 025.48 de:Kategorie:Indexierung; 150 Psychology; 345 Criminal law; 543 Analytical chemistry
  • Use case:
  • Robot and gadget jobs:
  • Qualifier (future): Version (DDC 1, DDC 22ger etc.)
  Support I don't know if we can adopt DDC in full depth (due to copyright reasons) but we could use the ten classes, each divided into ten divisions. --Kolja21 (talk) 05:29, 9 March 2013 (UTC)
  Oppose until proceeding questions are answered   Questions: The Dewey Decimal Classification is not freely licensed, as you allude to. Given that, could Wikidata use even the 10 classes? If so, could it use the additional 100 derived divisions? If so, could it use the additional 1000 derived sections? Where is the line, if one exists? How does fair use apply to structured data like Dewey classifications? Would Wikidata allow fair use, since its structured data is in the public domain? Emw (talk) 14:19, 9 March 2013 (UTC)
These seem like relevant questions. Anyone up for answering them, or at least discussing them? Emw (talk) 17:09, 31 March 2013 (UTC)
Anyone? Bueller? Emw (talk) 01:35, 23 April 2013 (UTC)
  Support At least in my country, compiling a selection of entitities from a list or catalogue is to my understanding below the threshold of originality. Mange01 (talk) 22:02, 13 March 2013 (UTC)
  Neutral. A point that looks not clear in this proposal: is the property done to be used in all items (with, by example, <Art of computer programming> DDC <005>) or only in items that has an id in DDC (by example <Philosophy> DDC <100>). I prefer the second solution (with an other property like "topic" (<Art of computer programming> topic <Computer programming>)) because that will allow us to support easily all classification (DDC, Universal Decimal Classification...). Tpt (talk) 08:37, 16 March 2013 (UTC)
  Oppose – It seems problematic to use a nonfree system, both for legal and principal reasons. -- Byrial (talk) 17:55, 20 April 2013 (UTC)
  •   Oppose due to copyright. foundation:Resolution:Licensing policy states that projects without an fair use policy (more specifically an Exemption Doctrine Policy (EDP)) have to follow the Definition of Free Cultural Works (http://freedomdefined.org/Definition). If we are going to allow fair use material, then such an policy should be proposed and approved first, not the other way around. And even then, if Wikidata had an fair use policy, then it would be problematic to use the data on the wikipedias, as the use of the DDC would also need to comply with the EDP there.--Snaevar (talk) 15:17, 22 May 2013 (UTC)

IPA / ΜФА

   Not done
Descriptionpronunciation written in International Phonetic Alphabet
Data typestring multilingual text string-invalid datatype (not in Module:i18n/datatype)
Domainany
Examplelʲwiu̯
Proposed byDixonD (talk) 11:45, 2 April 2013 (UTC)
  •   Oppose For which items? By default items are interlanguage, so common pronunciation not exist. Infovarius (talk) 20:20, 2 April 2013 (UTC)
    I changed the datatype. --DixonD (talk) 06:54, 3 April 2013 (UTC)
  •   Oppose per Infovarius until either we won't deserve Wiktionary, or the property's target was specified more concrete, e.g. pronounsation local name of a place (from ex., seems to be supposed).
    Until this information is included in many Wikipedias, including English one, it is worth to be centralized in Wikidata. And IMO a part of information from Wiktionary should be moved to Wikidata anyway, but it is another story. --DixonD (talk) 05:24, 5 April 2013 (UTC)
  •   Support as qualifier for Local Name or for Official Name. I have changed the datatype back to string. Filceolaire (talk) 06:31, 5 April 2013 (UTC)
    For instance, the article en:Lviv has two pronunciations: Ukrainian and Polish. French Wikipedia (fr:Lviv) has French pronunciation. So the multilingual text datatype makes more sense than a qualifier to mentioned names as theoretically every language may have different pronunciation for some particular term. --DixonD (talk) 06:58, 5 April 2013 (UTC)
  •   Support but it must reflect the multiple pronunciations, even within a language. I don't know how. --NaBUru38 (talk) 16:45, 11 April 2013 (UTC)
  • Another "contra": Pronunciation is for words, but here we collect terms, whose names can be (almost arbitrarily) changed - thar's why they are numbers. Let's wait until we include interwiki-links for Wiktionary (Phase 4+?). Infovarius (talk) 19:43, 11 April 2013 (UTC)
  •   Oppose – This is dictionary stuff about words, not something related to items. Which words are used and how they are pronounced even within one language depends on time, age, status, location, dialect etc. It could be covered as support for wiktionary, but for now I think it is outside the scope of Wikidata. -- Byrial (talk) 19:23, 20 April 2013 (UTC)
  •   Support Items are words, and their pronunciation is an important piece of structured data. Different languages (and variants of languages) typically have their respective "received pronunciations" represented in dictionaries and used relatively consistently by reliable sources in their language variants (e.g. representative news organizations). These various pronunciations could use qualifiers to specify language codes like en-US, en-GB, en-AU, de-DE, etc. to indicate how some item is pronounced in various languages and variants within a language. Emw (talk) 02:26, 26 April 2013 (UTC)
  •   Oppose, per Byrial. --Yair rand (talk) 15:56, 28 April 2013 (UTC)
    • Well, "Abisko, Linköping" isn't pronunced in the same way as "Abisko, Kiruna", it is not because they are located 1000 km from each other, it's because they are two different localities (read items). -- Lavallen (block) 10:27, 8 May 2013 (UTC)

en:Main type of item (entity type)/ru:тип элемента (основной тип)/de:Entität (Typ)/fr:type principal (entité)

   Not done
Descriptionописание свойства (обязательный параметр)
Data typeItem
Template parameterprobably no
Domainall items. Should be endorsed in an official guideline.
Allowed valuesmay be some controlled but expandable vocabulary
Example 1MISSING
Example 2MISSING
Example 3MISSING
Sourcecommon sense, categories of Wikipedias
Robot and gadget jobsInitial values can be estimated and filled with ones from P:P107 and P:P31.

While GND main type has been controversially used as "main type", recently it was understood as not, we need a proper replacement. From the other hand, "is a" is a quite vague. Wikidata needs the main property to build its own ontology (its own category system). I propose number P1 for this property. Infovarius (talk) 19:18, 14 April 2013 (UTC)

First we need a clear onthology and once we have it we can create the property. An "empty" property (without a clear definition of its use) is dangerous and if a good onthology is accepted we can perhaps recycle the GND property. Snipre (talk) 17:17, 17 April 2013 (UTC)
Universal ontology is too complex thing to be built in advance. It can be refining (and even constructing) with the time. Infovarius (talk) 04:24, 22 April 2013 (UTC)
I agree with that point, Infovarius. I actually find it to be an argument in favor of using properties that support increasingly refined classification, which is a primary feature of P31/P279. (P31/P279 can be as high-level, or as low-level, as needed.) Emw (talk) 12:20, 22 April 2013 (UTC)
  •   Oppose "Main types" are a taxonomic kludge for systems that don't support multiple levels of hierarchical classification. In a project to structure all knowledge -- which Wikidata is -- restricting items into a small set of types will inevitably lead to classifications that are either A) too broad to be useful or B) simply incorrect. In other words, whether it is based on the GND or not, an ontology that classifies things with "main types" will inevitably end up with problems like the uselessly broad "term" main type in GND main type (P107), or simply incorrect classifications like families and literary figures as GND main type 'person'. Again, to emphasize: the fact that P107 is based on "main types" is a bigger problem than the fact that it is based on the GND. Let's not repeat that mistake.
There is a better solution: use "type" properties recommended for the Semantic Web by the W3C -- that is, use rdf:type and rdfs:subClassOf. These properties exist in Wikidata as instance of (P31) and subclass of (P279). These properties have been part of W3C recommendations for the Semantic Web for almost a decade. They are fundamental properties used in large controlled vocabularies to structure data into knowledge. They enable the important distinction between a type (class) and a token (instance). They facilitate classification at an arbitrary granularity; together 'instance of' and 'subclass of' can classify all subjects and be used to determine precisely where each subject exists in the hierarchy of knowledge. Not only do they solve those structural problems of P107 and other "main type" properties, but by being based on W3C recommendations, instance of (P31) and subclass of (P279) also make Wikidata more interoperable with the rest of the Semantic Web. Emw (talk) 00:19, 18 April 2013 (UTC)
What about Wikipedia templates, lists, categories? What type-property should we use for them? Infovarius (talk) 04:24, 22 April 2013 (UTC)
The answer to that question seems independent of whether a main type property or P31/P279 is used. I personally don't think it makes sense to have Wikipedia lists and categories on Wikidata in the long term (since Wikidata should be used to create those lists and categories), but in the near future whatever 'main type' applies to lists, categories etc. could be applied via P31/P279. Emw (talk) 12:17, 22 April 2013 (UTC)
  Oppose – Agree with Emw -- Byrial (talk) 19:37, 20 April 2013 (UTC)
  Oppose per Emw. Silver hr (talk) 19:19, 26 April 2013 (UTC)
  Comment The main type (GND) property is good to do a general classification. I would support a renaming to "main type/type principal/Haupttyp" to show the indepedendece of Wikidata and maybe customize it more for the needs of Wikidata as done with the extra type disamigulation. --Pyfisch (talk) 15:36, 8 May 2013 (UTC)
  Comment. I initially thought that a general "type" property could be good, but I see more and more problems, and less and less uses with that. For instance, I think we should have an easy way to identify people, but I think it should be simply done by setting P31 to person in each case, rather than "politician", "man" or "charming lady"). But still, if we want a high-level "type" property, I would favor devising a home-made system over assigning GND main types to things that do not have a GND entry. --Zolo (talk) 16:18, 8 May 2013 (UTC)
Yes, I thought about some high-level type (may be 2 or 3 levels of classification). While P31 is usually used as a lowest level ("politician of USA", "TV-actor" and so on), P1 can be used as a main type more useful for bots than GND. Infovarius (talk) 18:49, 8 May 2013 (UTC)

Twinning / Zwillingsbildung / Macle / Двойники / Geminato

   Done: twinning (P537) (Talk and documentation)
DescriptionDescribes the usual way that crystals show twinning.
Data typeItem
Template parameter
DomainMinerals, Variants of minerals
Allowed valuesSome are specific for certain minerals: Bavenoer, Karlsbader, Manebacher, Periklin, Dauphinée, ....
Exampleorthoklase = Bavenoer, Karlsbader, Manebacher (Qualifiers for frequency?)
Sourcemindat-, rruff-, mineral databases
Robot and gadget jobs?
Proposed byTobias1984 (talk)

Useful for infoboxes and for queries. --Tobias1984 (talk) 14:08, 30 April 2013 (UTC)

The Chemistry Task force already listed some properties for crystallography (seeWikidata:Chemistry_task_force/Properties#Crystallography. Perhaps can you see if this list is complete and then we can propose the whole list in once. Snipre (talk) 09:53, 12 May 2013 (UTC)
  Support used in fr:mineral infobox too Snipre (talk) 17:40, 21 May 2013 (UTC)
  Support --Chris.urs-o (talk) 12:10, 22 May 2013 (UTC)
  Support --Sbisolo (talk) 12:47, 22 May 2013 (UTC)

Fracture (mineralogy) / Bruch / Cassure / Излом / Frattura (mineralogia)

DescriptionDescribes the usual way that crystals fracture.
Data typeItem
Template parameter
DomainMinerals, Variants of minerals. Rocks, metals and other materials.
Allowed valuesen:Fracture_(mineralogy)
ExampleObsidian or Quartz = conchoidal
Sourcemindat-, rruff-, mineral databases
Robot and gadget jobs?
Proposed byTobias1984 (talk)

Useful for infoboxes and for queries. --Tobias1984 (talk) 18:22, 30 April 2013 (UTC)

  Support used in fr:mineral infobox too Snipre (talk) 17:41, 21 May 2013 (UTC)
  Support --Chris.urs-o (talk) 12:09, 22 May 2013 (UTC)
  Support--Sbisolo (talk) 12:49, 22 May 2013 (UTC)


Museofile

   Done: Museofile ID (P539) (Talk and documentation)
DescriptionID in a database by the French ministry of culture
Data typeString
Template parametercommons:Template:Authority control
DomainFrench museums
ExampleMusée Boucher-de-Perthes (Q3329099) -> M0811
Sourcehttp://www.culture.gouv.fr/documentation/museo/museo-musees.htm
Proposed byZolo (talk) 14:40, 20 May 2013 (UTC)

  Comment, one of the best online source of data for small French museums. --Zolo (talk) 14:40, 20 May 2013 (UTC)

  Support seems useful. --Ricordisamoa 12:23, 22 May 2013 (UTC)
  Support --Tobias1984 (talk) 12:30, 22 May 2013 (UTC)

Image

   Not done
Descriptiona relevant illustration
Data typeItem
Template parametermost infoboxes have this parameter as image or logo
Domainmost creative works, companies, etc.
Allowed valuesitems about files on specific Wikipedias. This property is the sibling of Property:P18, which only works for Commons files.
ExampleQ1371495 <image> File:Systemshock2box.jpg
Proposed by— ΛΧΣ21

Given that we now approved having items about files that are locally stored (e.g. are not on Commons), we need to create a sibling to P18 to allow linking those images with their respective subjects. — ΛΧΣ21 06:56, 19 April 2013 (UTC)

Couldn't you just add a qualifier to it for the Wikipedia's which have a local copy of the file? Multichill (talk) 18:17, 19 April 2013 (UTC)
I'm not talking about local copies, but NFCC files that are not on Commons because of copyright status. — ΛΧΣ21 18:34, 19 April 2013 (UTC)
I meant Q1371495 Image "Systemshock2box.jpg" <some sort of qualifier> English Wikipedia.
Ok I added the example. Multichill (talk) 19:18, 19 April 2013 (UTC)
It doesn't work. The issue is that when you click on the link, it takes you to Commons, and not to the item Q10862221. — ΛΧΣ21 19:26, 19 April 2013 (UTC)
So we should focus on fixing that instead of creating a completely redundant property to work around it. Multichill (talk) 19:42, 19 April 2013 (UTC)
And how will we fix that? Properties cannot have more than one datatype and point to items and Commons files at the same time. — ΛΧΣ21 20:00, 19 April 2013 (UTC)
It's just a string (look for P18) so you can use it like that on Wikipedia. Multichill (talk) 07:56, 20 April 2013 (UTC)

Latest release version

   Not done
Descriptionlatest release version of a software
Data typeString
Template parameteren:Template:Infobox Software | latest release version=
Domainterm
ExampleQ7593 => "Wheezy"
Proposed byNullzero (talk) 04:28, 6 May 2013 (UTC)
How should "latest development version" vs. "latest production version" be handled? - Soulkeeper (talk) 14:24, 10 May 2013 (UTC)
  Comment I am concerned about any property called 'latest foo', 'current foo', 'active foo', etc. I think it would be much better to have a property that was simply 'release version', 'development version', etc. and use qualifiers to attach a date to. So Super Cool Game release version 6.7.8B on date 12 May 2013. That way you would know how 'fresh' that information is, but we wouldn't be in the inevitable position of have something claimed as the 'latest' when it no longer is. Joshbaumgartner (talk) 06:51, 13 May 2013 (UTC)
  Oppose - The latest version can be queried from a property "Software version" that has many entries with qualifiers for "release date". --Tobias1984 (talk) 07:23, 13 May 2013 (UTC)
  Oppose per Tobias1984. Don't create time dependent property. Use qualifier to add additional data. Snipre (talk) 11:57, 18 May 2013 (UTC)
  Oppose, can be queried easily. --Nightwish62 (talk) 17:14, 22 May 2013 (UTC)

Subject

   Not done
Descriptionsubject of work, film, book, etc. For paintings, there is already the property "depicts".
Data typeItem
Domaincreative work
Example
Proposed by--  Docu  at 08:31, 21 April 2013 (UTC)
depicts is currently used for books and films too (example). I think it makes sense, as the idea is the same. --Zolo (talk) 15:52, 21 April 2013 (UTC)
Films are visual so it seems consistent, but books? --  Docu  at 08:35, 25 April 2013 (UTC)
The word may sound unfit, but the idea is the same so I think it is better to add one property, as it should be easier to manage, and avoid useless questions about fringe cases (say, comic books). Perhaps, we could rename it to "subject", but we can probably never find perfect labels that work in all languages. --Zolo (talk) 12:04, 25 April 2013 (UTC)
  Oppose Having a broader "depicts" property like this is a great idea, but I agree with Zolo that it would make more sense to relabel "depicts" to "subject" than to create a new property to accomplish that. Having multiple properties that describe the same thing in different domains is not a good idea. Emw (talk) 15:25, 27 April 2013 (UTC)
  Oppose per Emw. Joshbaumgartner (talk) 06:55, 9 May 2013 (UTC)

class/type / Klasse/Typ (P:P289)

   Not done
Descriptiongeneric property for statements like "ship class" or similar
Data typeItem
Template parameterthere might be many different
Domainseveral
Allowed valuesnot limited directly
ExampleUSS Enterprise => Constitution class
Proposed by#Reaper (talk)
Discussion

The Property:P289 has been created without discussion. Instead of deleting it, it might should be renamed. --#Reaper (talk) 14:04, 27 April 2013 (UTC)

See also Property:P288 (watercraft type).
  •   Oppose, redundant with instance of (P31) and subclass of (P279). Emw (talk) 15:18, 27 April 2013 (UTC)
    • Here your classification reaches its limits: if you have different classifications using "subclass of", how do you want to differentiate them in the infobox ? Just an example. A ship is define according to its purpose, "subclass of": military ship and by its propulsion type, "subclass of": nuclear propulsed ship, how do you do the extraction in the infobox with only "subclass of" ? Snipre (talk) 14:53, 29 April 2013 (UTC)
  • Snipre, how does your comment relate to my statement that this proposed 'class' property is redundant with P31 and P279? It seems like your comment is more of a general question about 'subclass of', and thus better suited for Property_talk:P279. It's a reasonable question that's worth discussing, but it seems independent of this particular proposal. Emw (talk) 02:51, 30 April 2013 (UTC)
Perhaps we can move this discussion but this proposal with its generalization concept gives me elements about limitations of general properties for classification so I just wrote here. Snipre (talk) 08:08, 30 April 2013 (UTC)
  •   Oppose, current definition of property matches infobox use. --  Docu  at 05:13, 29 April 2013 (UTC)
  •   Oppose I agree that with "instance-of" and "subclass-of", we already have properties to express this. Plus, it doesn't provide a solution to the problem of differentiating between values in infoboxes, for an item can belong to several classes as well. The underlying problem remains the same, and eventually, we would need further properties like "sub-class" and "sub-sub-class", or "class 1", "class 2", "class 3", and so on. Instead, differentiating should be implemented with qualifiers (perhaps "of-item", as proposed below), which makes it a lot more flexible.--Kompakt (talk) 10:59, 17 May 2013 (UTC)

Venue / Veranstaltungsstätte

   Done: no label (P540) (Talk and documentation)
Descriptionexact venue where the event takes/took place
Data typeItem
Template parameter"Venue" in en:template:Infobox GrandSlamTournaments (and many others)
Domainevent
Allowed valuesgeographic locations such as stadiums, convention centers, ....
Exampleen:Indian Wells Masters: "Indian Wells Tennis Garden"; en:Super Bowl XLII: "University of Phoenix Stadium"; en:Eurovision Song Contest 2009: "Olympic Indoor Arena", en:2004 Democratic National Convention: "FleetCenter"
Proposed by--Kompakt (talk) 08:21, 26 April 2013 (UTC)
  Support seems specific enough. Joshbaumgartner (talk) 05:00, 10 May 2013 (UTC)

office contested / zur Wahl stehendes Amt /

Descriptiontitle of office which election will determine the next holder of
Data typeItem
Domainelections for specific offices
Allowed valuesname of office
Examplew:en:United States presidential election, 2012 => w:en:President of the United States
Format and edit filter validationmust be a valid item
Robot and gadget jobsallowed
Proposed byJoshbaumgartner (talk) 05:10, 13 May 2013 (UTC)
  Info This property is for use on specific individual elections (e.g. w:en:United States presidential election, 2012, not for election events which cover several different individual elections (e.g. w:en:United States elections, 2012. Joshbaumgartner (talk) 05:10, 13 May 2013 (UTC)

  Support Clearly a necessary property to describe an election.--Kompakt (talk) 08:28, 14 May 2013 (UTC)

Officially opened by / Offiziell eröffnet von / Ouverture officielle par

Descriptionperson that officially opened the Olympic Games
Data typeItem
Template parameter"Officially opened by" in en:template:Infobox Olympic games
DomainOlympic Games
Allowed valuespeople
Example2008 Summer Olympics => Hu Jintao
Proposed by--Kompakt (talk) 19:29, 29 April 2013 (UTC)
  Support This is specific and useful. Joshbaumgartner (talk) 00:37, 13 May 2013 (UTC)

Olympic Oath made by / Olympischer Eid abgeleistet von / Serment olympique prononcé par

   Done: oath made by (P543) (Talk and documentation)
Descriptionperson(s) that made the Olympic Oath
Data typeItem
Template parameter"Athlete's Oath", "Judge's Oath" in en:template:Infobox Olympic games
DomainOlympic Games
Allowed valuespeople
Example2008 Summer Olympics => Zhang Yining, Huang Liping
Proposed by--Kompakt (talk) 19:29, 29 April 2013 (UTC)
  Support This is specific and useful. Joshbaumgartner (talk) 00:37, 13 May 2013 (UTC)

Olympic Torch lit by / Olympischer Flamme entzündet von / Flamme olympique allumée par

   Done: torch lit by (P545) (Talk and documentation)
Descriptionperson that lit the Olympic Torch
Data typeItem
Template parameter"Olympic Torch" in en:template:Infobox Olympic games
DomainOlympic Games
Allowed valuespeople
Example2008 Summer Olympics => Li Ning
Proposed by--Kompakt (talk) 19:29, 29 April 2013 (UTC)
  Support --Nightwish62 (talk) 10:24, 11 May 2013 (UTC)
  Support This is specific and useful. Joshbaumgartner (talk) 00:37, 13 May 2013 (UTC)
  Support --Stryn (talk) 12:44, 22 May 2013 (UTC)

Docking port / Стыковочный узел

   Done: docking port (P546) (Talk and documentation)
Descriptionстыковочный узел при первой стыковке, стыковочный узел при второй стыковке и т. д./docking port for the first dock, docking port for the second dock etc
Data typeItem
Template parameterru:Шаблон:Космическая экспедиция Стыковка 1, Стыковка 2, и т. д. en:Template:Infobox_space_mission Docking port en:Template:Infobox_spaceflight docking_port
Domainкосмические аппараты осуществлявшие стыковку/spacecraft that docked
Allowed valuesимена стыковочных узлов (для них нужно будет создать элементы), либо имена модулей ОС/names of the docking stations or modules
ExampleСоюз ТМА-9, стыковочный узел при первой стыковке: кормовой узел модуля "Звезда"/Soyuz TMA-9 docking port for first docking: the aft port of Zvedza
Sourcespace.kursknet.ru, карточки в статьях и т. д.
Proposed by— Ivan A. Krestinin (talk) 19:20, 1 April 2013 (UTC)
Added en Secretlondon (talk) 13:39, 27 April 2013 (UTC)
  Support Secretlondon (talk) 10:09, 6 May 2013 (UTC)
  Support --Tobias1984 (talk) 10:32, 7 May 2013 (UTC)
  Support --Paperoastro (talk) 13:21, 18 May 2013 (UTC)

commemorates

   Done: commemorates (P547) (Talk and documentation)
Descriptionwhat the place, monument, memorial commemorates
Data typeItem
Domainplace, creative work
Example
Proposed by--  Docu  at 09:49, 21 April 2013 (UTC)

Versiontype

   Done: version type (P548) (Talk and documentation)
DescriptionType of version (Qualifier for P348)
Data typeItem
Allowed valuesalpha, beta, stable version, …
Robot and gadget jobssee above
Proposed byMichaelSchoenitzer (talk) 22:22, 14 May 2013 (UTC)
  Comment - What about version number? Is that a separate description of "version"? --Tobias1984 (talk) 15:23, 15 May 2013 (UTC)
  Strong support for both. Qualifiers are avaible, so we can use them to distinguish which version type we have. But please define an exact set of allowed parameters for Versiontype property. --Pyfisch (talk) 08:44, 18 May 2013 (UTC)
  Strong support, as Pyfisch. --Ricordisamoa 13:54, 18 May 2013 (UTC)
  Comment - If the name is so generic people are going to use it for different stuff. If it should be only for software then it should be called "software version". --Tobias1984 (talk) 17:08, 19 May 2013 (UTC)

MGP ID

Descriptionid for mathematicians at the Mathematics Genealogy Project (Q829984)
Data typeString
Domainperson
Example<Leonhard Euler (Q7604)> MGP ID <38586>
Sourceen:Template:MathGenealogy, http://genealogy.math.ndsu.nodak.edu/index.php
Proposed byStevenliuyi (talk) 18:32, 20 May 2013 (UTC)

Chivalric order

DescriptionThe chivalric order in which a person is in, if any
Data typeItem
Template parameterNot known.
Domainitems about persons
Allowed valuese.g. Order of Saint George, Knights of the Band or Order of the Garter
ExampleCharles à Court Repington → Order of St Michael and St George
SourceChivalric_order
Robot and gadget jobsNot now.
Proposed by— ΛΧΣ21 04:27, 26 March 2013 (UTC)
  Support Useful. Joshbaumgartner (talk) 08:24, 9 May 2013 (UTC)

Residence

   Done: residence (P551) (Talk and documentation)
DescriptionThe place where the person is, or has been, resident. As seen in infoboxes on Wikipedia (Infobox person). Not to be confused with the Official Residence property.
Data typeItem
Template parameteren:template:Infobox person residence
Domainperson
Allowed valuesplaces (items)
ExampleKim Dotcom residence = New Zealand
SourceSource from infoboxes in wikipedia articles
Robot and gadget jobsCould be imported by robots.
Proposed byDanrok (talk) 13:14, 1 April 2013 (UTC)
what is the difference with Official Residence property ? Old official residence can be described with Property:P263 with qualifiers and what are the definition of residence if it isn't the official one ? To live 3, 6, 12 or month ? To have a house or to rent a flat is suffisant ? For me that is not relevant. Snipre (talk) 09:28, 2 April 2013 (UTC)
As said in the description "Not to be confused with the Official Residence property". These are not the same. The Official Residence property is used with office articles, not person articles, and is used to specify buildings which are official residences. This information already exists in infoboxes on wikipedia, as shown in the proposal. Danrok (talk) 16:18, 7 April 2013 (UTC)
  Oppose, it's not relevant to mention where a person lives. --NaBUru38 (talk) 16:52, 11 April 2013 (UTC)
  Support If it is allegedly not relevant as to the location of a living residence why is this information currently hosted in wikipedia? As this information is currently viewed as revelant on the wikipedias it should be assumed to be relevant for wikidata as well.
  Support This property is clearly relevant; Wikipedia is full of residence information. Of course, that doesn't mean it needs to specify a person's street address. Emw (talk) 20:50, 20 April 2013 (UTC)
  Strong support, widely used parameter. --Stryn (talk) 11:22, 21 April 2013 (UTC)
  Support --Viscontino (talk) 21:00, 7 May 2013 (UTC)
  Support very relevant and widely used on Wikipedia. Joshbaumgartner (talk) 08:34, 9 May 2013 (UTC)
  Support - maybe it's not that relevant, it's a field in many infoboxes, and therefor a logical property. Edoderoo (talk) 11:16, 21 May 2013 (UTC)
  Comment seems very relevant to me, good to know the list of places where a person has taken residency. Many towns and cities put up memorials to say this person lived here, so it must be significant. Not to be confused with citizenship, not everyone becomes a citizen of the country where they're living and working. Danrok (talk) 11:22, 21 May 2013 (UTC)
Significance: Victor Hugo (French) resided in Guernsey (British), 1855 until 1870, where he wrote his most famous works. Danrok (talk) 11:46, 21 May 2013 (UTC)

Handedness

   Done: handedness (P552) (Talk and documentation)
Descriptionhandedness of the person
Data typeItem
Template parameteren:template:infobox tennis player plays
Domainperson
Allowed valuesright-handed, left-handed
Example<Novak Djokovic> – <right--handedness>
SourceWTA, ATP, ITF profiles
Proposed byStryn (talk)
  Comment merge with P:P423? --Stevenliuyi (talk) 15:47, 14 April 2013 (UTC)
Maybe, but in ice hockey, if he shoots from right, he is often left-handed. In tennis most of players who are right-handed players also play with right hand, except some like Rafael Nadal. --Stryn (talk) 15:54, 14 April 2013 (UTC)
  Support the merger, it applies to baseball pitchers, golfists, surfers and stakeboarders (stance). --NaBUru38 (talk) 19:05, 18 April 2013 (UTC)
Maybe one property (e.g. "laterality") with different items for various aspects and different sports could work. --  Docu  at 08:29, 25 April 2013 (UTC)
  Support the merger --Tobias1984 (talk) 14:39, 6 May 2013 (UTC)
  Support. Sounds like interesting data. ("List of all current left-handed heads of government", hmmm...) --Yair rand (talk) 16:18, 25 April 2013 (UTC)
  Comment should "ambidextrous" (Q1365348, for example) or "cross-dominance" be part of the allowed values? Or should the property list both "right-handed" and "left-handed" as values, combined with qualifiers? Gabbe (talk) 09:32, 27 April 2013 (UTC)

  Support some way for this to also be applied to baseball players. AutomaticStrikeout 17:37, 6 May 2013 (UTC)

  Comment - I think we should make a qualifier "type of activity" that links to items. handedness could then be for example "right handed" & activity = "writing" & "left handed" & activity = "throwing" etc... --Tobias1984 (talk) 17:43, 6 May 2013 (UTC)

  Support -- This could be used for many things, including, of course, baseball. TCN7JM 20:29, 6 May 2013 (UTC)   Comment - I'm still trying to find out how such a change of meaning is handled at Wikidata_talk:Property_creators. I was thinking that we could just move this discussion to the properties talk page and then change the description of the property. --Tobias1984 (talk) 12:37, 12 May 2013 (UTC)

has social media account on

DescriptionA social network that the person has an account on, to be supplemented by a qualifier property "social media address" (Property:P554) indicating the account name on that social network.
Data typeItem
Domainperson, organization
ExampleEric Schmidt Q92747 => Twitter Q918, qualifier "social media address" => "ericschmidt" (string data type)
Proposed byYair rand (talk)
Discussion

I'm not completely sure this is a good idea, but it's probably better than creating separate properties for individual social networks, as was proposed earlier. There probably is lots of interesting data one could get from this (as I mentioned under the Twitter account proposal, one could use this to analyze Twitter text output of all people elected to X position who also have attributes X). If this is done, I think this property's use should be limited to those individuals who are already public figures, and not those who are only on Wikidata because of their association to someone else. --Yair rand (talk) 16:32, 28 April 2013 (UTC)

  Support interesting idea. --Stryn (talk) 10:46, 30 April 2013 (UTC)
  Support this would help in knowing about public figures. --Napoleon.tan (talk) 12:58, 30 April 2013 (UTC)
  SupportNice hack to use one property for multiple websites. Note that you need to propose the creation of the "social media address" property as well to complete this. Filceolaire (talk) 21:06, 14 May 2013 (UTC)
I figured the creation of that was implied. Do I need to create a separate proposal? --Yair rand (talk) 00:11, 20 May 2013 (UTC)
  Support as long as the qualifier mentioned by Filceolaire is also created. TCN7JM 01:18, 20 May 2013 (UTC)

Doublesrecord

Descriptionwin/loose balance for a player in doubles tournaments
Data typeString
Template parameter"doublesrecord" in en:template:infobox tennis biography
Domainperson
Example215 – 138
SourceExternal reference, Wikipedia list article (either infobox or source)
Robot and gadget jobscould be updated from ATP website
Proposed byEdoderoo (talk)
Discussion

This properties value can change in time, and needs to be updated on many language articles for active tennis players. Doing this on a centralised place on WikiData makes the most sense. Edoderoo (talk) 20:09, 29 April 2013 (UTC)

  Support. --Stryn (talk) 09:36, 2 May 2013 (UTC)
  Support Vinkje83 (talk) 10:02, 7 May 2013 (UTC)

DiseasesDB

   Done: DiseasesDB (P557) (Talk and documentation)
Descriptionw:Diseases Database
Data typeString
Template parameteren:Template:Infobox disease field DiseasesDB
Domainterm: diseases
Exampleheart attack = "8664",
Sourcehttp://www.diseasesdatabase.com/
Proposed byKizar --Kizar (talk) 00:46, 18 May 2013 (UTC)

Crystal system

DescriptionType of crystal for crystal coumpounds
Data typeItem
Template parameter"Système cristallin" in fr:modèle:Infobox chimie
Domainterm
Allowed valuescubic, hexagonal, trigonal, tetragonal, orthorhombic, monoclinic, triclinic
Examplesodium chloride => cubic
Proposed bySnipre (talk) 12:21, 18 May 2013 (UTC)
Property proposed by the Wikidata:Chemistry task force and the Wikidata:Mineralogy task force. Snipre (talk) 12:21, 18 May 2013 (UTC)

unit symbol / Einheitenzeichen

   Done: no label (P558) (Talk and documentation)
DescriptionSymbol of a unit (Q1307710)
Data typeString
Template parameterCan be mapped to de:Vorlage:Infobox Einheit: Symbol.
Domainunits (Q47574) and prefixes (Q131299)
Allowed valuesUnicode symbol or sequence of symbols
Example“km” for kilometre
SourceISO/IEC 80000 or http://www.ewh.ieee.org/soc/ias/pub-dept/abbreviation.pdf
Proposed byFomafix (talk) 15:21, 19 March 2013 (UTC)
Are these symbols actually universal between languages? --Yair rand (talk) 17:50, 19 March 2013 (UTC)
No. At least they are Cyrillic in Russian and Belarusian. --EugeneZelenko (talk) 04:05, 20 March 2013 (UTC)
ru:Вольт (Q25250) uses Latin „V“ in addition to Cyrillic „В“. --Fomafix (talk) 09:01, 20 March 2013 (UTC)

largest city / größte Stadt

   Not done
Descriptionthe largest city of this country
Data typeItem
Template parametercountrylargestcity
Domaincountries
Allowed valuesonly cities
ExampleGermany: Berlin
SourceInfobox
Proposed byBene* talk 21:00, 26 March 2013 (UTC)
  Oppose the "largest" city should be obtained with a query instead --Ricordisamoa 11:12, 27 March 2013 (UTC)
  Oppose per Ricordisamoa Emw (talk) 00:21, 28 March 2013 (UTC)
I don't quite understand the opposes but another concern is that there should be a way to get this for any administrative entity, such as a state, province or territory. Shawn in Montreal (talk) 23:59, 30 March 2013 (UTC)
It's because this property represents a very plausible use case for Wikidata queries. If information like "largest city" can be obtained with a query, it would be best to not create a property for it. Emw (talk) 00:12, 31 March 2013 (UTC)
  Oppose as it's right, this is a job for a query --Nightwish62 (talk) 15:43, 31 March 2013 (UTC)
  Comment Usually a country's "largest city" means its "most populous city", and query surely can do the job. But it's not that simple. For instance, there was a prolonged discussion in Chinese Wikipedia of whether or not Shanghai is the largest city of China. It's not the largest city based on population. But finally the community accepted that Shanghai is the largest city of China even though we don't know the criteria, because it's a widely accepted statement, which is stated in enormous sources, including sources from Chinese government and many mainstream media all around the world. --Stevenliuyi (talk) 16:33, 31 March 2013 (UTC)
  Comment In Upplands Väsby Municipality, Stockholm is the most populated "City", but not a single person in the City of Stockholm lives in Upplands Väsby. The city has 2 ha of land, and 0 population in that municipality, the rest of the city is located in 11 other municipalities. How is such an anomaly handled by queries? -- Lavallen (block) 15:23, 16 April 2013 (UTC)
  Oppose See en:World's largest cities for some discussion on how ill-defined the simple term 'largest city' is--essentially both 'largest' and 'city' require clear definition first before it can have any meaning. The preferred method is for cities to have 'population' and 'is in..' properties and a query can determine which is 'largest' per the parameters selected by the query's author. Joshbaumgartner (talk)
  Not done --Rschen7754 21:39, 25 May 2013 (UTC)

Terminus

   Done: terminus (P559) (Talk and documentation)
DescriptionThe feature (intersecting road, train station, etc.) at the terminus of a linear feature.
Data typeItem
Template parameter"terminus_a", "terminus_b" in en:Template:Infobox road
DomainLinear features, especially man-made, like roads and rail lines
ExampleOklahoma State Highway 74 <terminus> Interstate 35 in Oklahoma
SourceData available in en:Template:Infobox road for roads
Proposed by—Scott5114↗ [EXACT CHANGE ONLY]
Discussion

This will allow the addition for information about terminus information to linear features like roads and rail lines. It will use the property "is in the administrative feature" as a qualifier to denote the geographic location of the terminus, and "terminus direction" (proposed below) as a qualifier to denote which end of the feature this is (northern, southern, etc.) —Scott5114↗ [EXACT CHANGE ONLY] 06:44, 18 May 2013 (UTC)

  Support --Rschen7754 07:54, 18 May 2013 (UTC)
  Support -- Will be useful for many, many items. TCN7JM 17:53, 18 May 2013 (UTC)
  Support – This property is not used in the German template de:Vorlage:Infobox hochrangige Straße, but in the Template --Labant (talk) 05:37, 20 May 2013 (UTC)

Terminus direction

   Done: direction (P560) (Talk and documentation)
DescriptionThe direction of a terminus
Data typeItem
Template parameter"direction_a", "direction_b" in en:Template:Infobox road
DomainLinear features, especially man-made, like roads and rail lines
ExampleOklahoma State Highway 74 <terminus> Interstate 35 in Oklahoma <terminus direction> north
SourceData available in en:Template:Infobox road for roads
Proposed by—Scott5114↗ [EXACT CHANGE ONLY]
Discussion

To be used as a qualifier for the proposed "terminus" property (see above). —Scott5114↗ [EXACT CHANGE ONLY] 06:44, 18 May 2013 (UTC)

  Support --Rschen7754 07:54, 18 May 2013 (UTC)
  Support -- Makes sense as a qualifier. TCN7JM 17:56, 18 May 2013 (UTC)
  Support – This property is not used in the German template de:Vorlage:Infobox hochrangige Straße, but in the Template --Labant (talk) 05:30, 20 May 2013 (UTC)
  Comment I think up and down could be valid values as well. Vertical train: Dubai City Tower. Danrok (talk) 07:16, 20 May 2013 (UTC)
Indeed, while cardinal directions will be the usual (and thus "suggested") values, there would be no reason things like "up" or "down" couldn't be used. We need the flexibility to use other ways to describe termini, so I don't support outright restricting it to cardinal directions. There are some complicated examples of roads in the US having three or four ends (as an example, Oklahoma State Highway 63A, which is Y-shaped, having three ends). —Scott5114↗ [EXACT CHANGE ONLY] 22:09, 20 May 2013 (UTC)
  Comment Could this be renamed to just 'direction'? That way it could be used as a qualifier for 'adjacent station' on circular routes which have no termini, such as the Glasgow Subway. Gareth (talk) 08:13, 25 May 2013 (UTC)
I personally don't see why not. --Rschen7754 08:21, 25 May 2013 (UTC)
Agreed. —Scott5114↗ [EXACT CHANGE ONLY] 23:27, 25 May 2013 (UTC)

NATO reporting name

Descriptionmilitary equipment name assigned by NATO/ASCC
Data typeString
Domainaircraft, missiles, submarines, other military equipment assigned NATO code names
ExampleMikoyan-Gurevich MiG-21 => Fishbed
Sourcew:en:NATO reporting name
Proposed byJoshbaumgartner (talk) 12:49, 12 May 2013 (UTC)
  Info NATO reporting names are officially assigned by NATO and the Air Standardization Coordinating Committee to provide references to Soviet, Warsaw Pact, and Chinese aircraft, missiles, submarines, and military equipment. Joshbaumgartner (talk) 12:49, 12 May 2013 (UTC)

ORCID

   Done
DescriptionID for researchers, other contributors to published works (including Wikimedians!), etc. Already used in en:Template:Authority Control. See en:ORCID.
Data typeString
Domainperson
Allowed valuesSee ORCID documentation for checksum etc
Example0000-0001-5882-6823
Proposed byAndy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 10:46, 25 May 2013 (UTC)
Already created: Property:P496. Tpt (talk) 13:50, 25 May 2013 (UTC)

Find a Grave

Descriptioncode for the online "Find a Grave" database
Data typeString
Template parameterTemplate:Find a Grave
Domaindead people
Allowed valuesnumbers
ExampleSon House → 7951199
Format and edit filter validationsupposed to be a 7-digit number
SourceWikipedia, see above
Robot and gadget jobsSamoaBot is ready to import this
Proposed byRicordisamoa 23:29, 10 May 2013 (UTC)
Discussion
Probably belongs in the "authority control" category, but   Support the proposal. Regards, FrigidNinja 23:42, 10 May 2013 (UTC)
  Support and agree that this is authority control. Joshbaumgartner (talk) 13:12, 12 May 2013 (UTC)
OK, should I do the move? --Ricordisamoa 13:48, 12 May 2013 (UTC)
  Property:P535 --Ricordisamoa 17:56, 21 May 2013 (UTC)

central bank

DescriptionCentral bank that issuing the currency
Data typeItem
DomainCurrency
Example<Euro> → <European Central Bank>
Robot and gadget jobsYes
Proposed byKwj2772 (talk)

Kwj2772 (talk) 08:15, 21 April 2013 (UTC)

  Support - --Tobias1984 (talk) 11:17, 8 May 2013 (UTC)
  Comment I think "issuing authority" is a better name, since some currencies are not issued by "central bank". --Stevenliuyi (talk) 15:36, 9 May 2013 (UTC)
  Comment What would be the value for bitcoin? --Pyfisch (talk) 08:01, 10 May 2013 (UTC)
Maybe an item for "Bitcoin Project"? --Ricordisamoa 11:18, 10 May 2013 (UTC)

powerplant quantity

   Not done
DescriptionNumber of engines aircraft is equipped with
Data typeNumber (not available yet)
Example<Boeing 737> powerplant quantity <2>
Proposed byJoshbaumgartner (talk)
  Support - This should be a qualifier for the powerplant property. --Tobias1984 (talk) 13:06, 2 May 2013 (UTC)
  Comment on further reflection, I am thinking just a generic 'quantity' property would be fine as such a qualifier. But since we don't have numbers yet anyway, I'll leave it for now. Joshbaumgartner (talk) 05:41, 16 May 2013 (UTC)
  Comment I agree, a generic quantity property could be best. Danrok (talk) 16:01, 22 May 2013 (UTC)

ICDO

   Done: ICD-O (P563) (Talk and documentation)
Descriptionw:International Classification of Diseases for Oncology
Data typeString
Template parameteren:Template:Infobox disease field ICDO
ExampleQ2300699 = "8561/0"
Proposed byKaligula (talk) 11:09, 21 April 2013 (UTC)

Singlesrecord / Enkelrecord / EinzelBilanz

Descriptionwin/loose balance for a player in singles tournaments
Data typeString
Template parametersinglesrecord" in en:template:Infobox tennis biography
Domainperson
Allowed valuespositive values
Example151 – 218
Proposed byEdoderoo (talk)
Discussion

This property can change in time, and needs to be updated on many language articles for active tennis players. Edoderoo (talk) 20:26, 27 April 2013 (UTC)

*   Comment I've asked clarification for this proposal. --Stryn (talk) 21:37, 28 April 2013 (UTC)

  •   Comment how to handle with differents values? Will every wiki use the same "design" (of course if they want to use this property)? Some examples: en-wiki: 579–110 (84.03%) de-wiki: 577:110, it-wiki: 577 - 110 (83,99%) --Stryn (talk) 15:48, 1 May 2013 (UTC)
    • In theory, the numbers should be the same. We could add the percentage as a separate property, then every language can decide to show it or not. The main reason that the numbers are not the same today, is that it is far too much work to keep all tennisplayers up to date on all languages. Edoderoo (talk) 07:17, 2 May 2013 (UTC)

ATP tennis male player id / Identifiant ATP d'un joueur de tennis

Descriptioneach ATP player have a specific identifiant on ATP website.
Data typeString
Domainperson
Allowed values4 characters (letters or numbers)
Example<Rafael Nadal (Q10132)> N409
SourceATP website, French Wikipedia article with {{Profil ATP}} inclusion
Robot and gadget jobscould be updated by my bot fr:User:Hawk-Eye-Bot
Proposed byHawk-Eye (talk)
Discussion

Each player have a specific id. For "N409", add "http://www.atpworldtour.com/Tennis/Players/" before and ".aspx" after (example : http://www.atpworldtour.com/Tennis/Players/N409.aspx) and you obtain link to player profile (of Rafael Nadal]. It could by useful to update some proprieties as Weight, Height, Prize money, Singlesrecord, Doublesrecord (and other future proposal properties). I'm ever using this identifiant to update infoboxes in french Wikipedia with my bot fr:User:Hawk-Eye-Bot. See this example of contribution. Hawk-Eye (talk) 07:11, 14 May 2013 (UTC)
Sorry for my poor English — Hawk-Eye (talk) 07:27, 14 May 2013 (UTC)

  Support useful --Ricordisamoa 07:23, 14 May 2013 (UTC)
  Support --Stryn (talk) 07:32, 14 May 2013 (UTC)
  Support -- logic property, altough it's static data Edoderoo (talk) 10:52, 14 May 2013 (UTC)
  created, see the link above. --Ricordisamoa 11:56, 22 May 2013 (UTC)
PS: also added a link in AuthorityControl.js --Ricordisamoa 12:08, 22 May 2013 (UTC)
Retrieved from "https://www.wikidata.org/w/index.php?title=Wikidata:Property_proposal/Archive/7&oldid=1380148074"