Wikidata:Property proposal/Archive/8

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

Crystal habit / Kristallhabitus / Habitus / Габитус кристаллов / -

Done: crystal habit (P565) (Talk and documentation)

Description	Describes the usual shape of a crystal.
Data type	Item
Template parameter	de:Vorlage:Infobox_Mineral
Domain	Minerals, Variants of minerals
Allowed values	tabular, prismatic, cubic, aggregate, needle-shaped, ...
Example	phlogopite = "tabular", "platy", "prismatic", "flaky" and "massiv". Qualifiers could give information about the frequency of certain habits.
Source	mindat-, rruff-, mineral databases
Robot and gadget jobs	?
Proposed by	Tobias1984 (talk)

Useful for infoboxes and for queries. --Tobias1984 (talk) 08:30, 20 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:52, 12 May 2013 (UTC)

en.wikipedia:Template:Chembox hasn't crystal habit

Support --Chris.urs-o (talk) 12:07, 22 May 2013 (UTC)

Support --Sbisolo (talk) 12:45, 22 May 2013 (UTC)

Support Can we have a complete list of possible values ? Just to be sure that this property won't be used as crystal system property.Snipre (talk) 10:06, 26 May 2013 (UTC)

I will create a list of items from these lists: en:Crystal habit, de:Kristallhabitus, nl:Habitus_(kristal) and add those items to the constraints of the property. Having the "habits" as items will also ease the translation. Also once we have all those items we can generate "habit-lists" for every Wikipedia language. E.g. fr:Habitus_(minéralogie) is missing a nice list with images. --Tobias1984 (talk) 10:21, 26 May 2013 (UTC)

Basionym

Done: has basionym (P566) (Talk and documentation)

Description	„The legitimate, previously published name on which a new combination or name at new rank is based.“ (see ICN-Glossary and ICN-Art. 6.10)
Data type	Item
Domain	Scope of International Code of Nomenclature for algae, fungi, and plants (ICN)
Example	Opuntia ficus-indica basionym is Cactus ficus-indica
Format and edit filter validation	Single value
Proposed by	Succu (talk)

Discussion

Helps to bring together otherwise not linked taxon names. Makes it possible to generate the correct author citation: Opuntia ficus-indica (L.) Mill. Succu (talk) 12:30, 21 May 2013 (UTC)

Support - Especially because it is needed for citations. --Tobias1984 (talk) 13:37, 21 May 2013 (UTC)

Support - Resonable, other databases also contain this property, see http://www.tropicos.org/Name/5100164 --Cactus26(talk) 07:07, 24 May 2013 (UTC)

Support - Necessary for the names of plants according to the definition of ICN FelixReimann (talk) 16:54, 27 May 2013 (UTC)

hangingwall / Hangend

Done: underlies (P567) (Talk and documentation)

Description	stratigraphic relation: younger units lie on top of older units
Data type	Item
Template parameter	en:Template:Infobox_rockunit overlies, underlies
Domain	stratigraphic formations, members and groups
Allowed values	other articles of stratigraphic formations, members and groups
Example	en:Marcellus Formation, hangingwall=Mahantango Formation
Source	External reference, Wikipedia list article (either infobox or source NEEDED)
Robot and gadget jobs	?
Proposed by	Tobias1984 (talk)

I would like to sort stratigraphic data entries similar to http://www.bgr.de/app/litholex/gesamt_ausgabe_neu.php?id=2008131.Tobias1984 (talk) 10:43, 7 April 2013 (UTC)

Support as two separate properties, overlies and underlies, at least until there are bidirectional properties.Superm401 - Talk 16:30, 8 April 2013 (UTC)

Comment of course we could also use the properties preceded by and followed by for these relations. I'm not really sure how that would influence possible querries in the future. --Tobias1984 (talk) 15:42, 9 April 2013 (UTC)

Well, preceded and followed imply a temporal relation, and there are certain processes which can move older layers on top of newer ones, so overlays =/= follows. Chris857 (talk) 19:29, 25 April 2013 (UTC)

The terms overlies and underlies are being used here in their normal stratigraphic sense, I don't think that we should be including tectonic layering here. Mikenorton (talk) 13:57, 28 April 2013 (UTC)

The default should be stratigraphic succession. We could introduce qualifiers for things like unconformities and tectonic contacts. --Tobias1984 (talk) 14:17, 28 April 2013 (UTC)

Support - makes sense. Mikenorton (talk) 13:57, 28 April 2013 (UTC)

Support - --Chris.urs-o (talk) 15:37, 12 May 2013 (UTC)

footwall / Liegend

Done: overlies (P568) (Talk and documentation)

Description	stratigraphic relation: younger units lie on top of older units
Data type	Item
Template parameter	en:Template:Infobox_rockunit overlies, underlies
Domain	stratigraphic formations, members and groups
Allowed values	other articles of stratigraphic formations, members and groups
Example	en:Marcellus Formation, , footwall=Onondaga Formation
Source	External reference, Wikipedia list article (either infobox or source NEEDED)
Robot and gadget jobs	?
Proposed by	Tobias1984 (talk)

Date of birth / Geburtsdatum / Date de naissance / Data di nascita

Status: Done

→ Property:P569

Description: Birth date of a person
Datatype: TimeValue
Links: schema.org FOAF...
Infobox parameter example:
Comments: Basic property used by all biographical infobox. Tpt (talk) 20:31, 30 January 2013 (UTC)

That may not sound very important -nor the right page to talk about that- but what about fictional worlds with fictional dates (see this infobox). Any way to escape the TimeValue datatype ? --Zolo (talk) 08:54, 3 February 2013 (UTC)

It is not a real person so it will be simpler to crate a new typ of item for fictional figures. Snipre (talk) 10:21, 3 February 2013 (UTC)

+1 it is very important --Viscontino (talk) 17:22, 5 February 2013 (UTC)

Support absolutely necessary. There will be a solution for the fictional World someday.

Support --LadyInGrey (talk) 23:47, 5 February 2013 (UTC)

Support It existed a few hours ago (probably Property:P67 but was deleted !! --Eric-92 (talk) 02:44, 6 February 2013 (UTC)

Support once possible. @Eric: P67 was deleted because it used the "item" datatype, when it should've used "TimeValue". For that reason, of course, this property can't be created until TimeValue is enabled as a possible datatype. — PinkAmpers&^{(Je vous invite à me parler)} 07:47, 6 February 2013 (UTC)

I think there's consensus for hacking this; I am putting this in a hidden block so it doesn't distract from others that are on-going conversations, whilst we wait for the datatype to be created. James F. (talk) 18:12, 6 February 2013 (UTC)

Property:P95 was created (not by me), maybe should be removed. --Eric-92 (talk) 22:24, 6 February 2013 (UTC)

Removed by someone. Ajraddatz (Talk) 12:46, 9 February 2013 (UTC)

Date of death / Sterbedatum / Date de décès / Data di morte

Status: Done

→ Property:P570

Description: Death date of a person
Datatype: TimeValue
Links:
Infobox parameter example:
Comments: Basic property used by all biographical infobox. Tpt (talk) 12:32, 2 February 2013 (UTC)

Support --LadyInGrey (talk) 23:48, 5 February 2013 (UTC)

I think there's consensus for this; am hiding from the list of on-going discussions to avoid distractions. James F. (talk) 18:13, 6 February 2013 (UTC)

Foundation or Creation Date / Gründungsdatum / Date de fondation

Status: Done

→ Property:P571

Description: When the Organization was founded
Datatype: TimeValue
Links:
Infobox parameter example: en:Template:Infobox company (Founded)
Comments:
- Agree. --NaBUru38 (talk) 21:28, 8 February 2013 (UTC)
  - Support Used in info box. --ThorstenX1 (talk) 06:18, 10 February 2013 (UTC)
Wait for TimeValue datatype. --Eric-92 (talk) 03:08, 11 February 2013 (UTC)

Rotation period / Rotationsperiode / Période de rotation / Periodo di rotazione

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

Description	the time that astronomic objects takes to complete one revolution around its en:axis of rotation.
Data type	Point in time
Template parameter	en:template:Infobox planet sidereal_day
Domain	asteroids, satellites, dwarf planets, planets, stars
Proposed by	Paperoastro (talk)

Support Better. MER-C (talk) 12:55, 9 February 2013 (UTC)

Orbital period / Siderische Periode / Période orbitale

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

Description	the time taken for a given astronomic object to make one complete about another object. A qualifier can distinguish different definitions of orbital period (i.e. sidereal period, or synodic period).
Data type	Point in time
Template parameter	en:template:Infobox planet period, synodic_period
Domain	asteroids, satellites, dwarf planets, planets, stars
Proposed by	Paperoastro (talk)

Biology: Date of scientific description

Status: Done

→ Property:P574

Description: publication date of the first scientific description
Datatype: Date (year)
Links:
Infobox parameter example:
Comments:

Support. - Soulkeeper (talk) 17:48, 8 February 2013 (UTC)

Support. Same as for "Taxon author". Amphicoelias (talk) 12:17, 7 March 2013 (UTC)

Support. Same as for "Taxon author". Liné1 (talk) 08:05, 8 March 2013 (UTC)

Support. Same as for "Taxon author". Mirgolth (talk) 08:25, 8 March 2013 (UTC)

Support.Same as for "Taxon author". Hexasoft (talk) 08:51, 8 March 2013 (UTC)

Support. MichaelSchoenitzer (talk) 15:34, 9 March 2013 (UTC)

Support. --Salixen (talk) 15:10, 13 March 2013 (UTC)

Discovery date / Entdeckungs Datum / Data di scoperta

Done: time of discovery or invention (P575) (Talk and documentation)

Description	when the item was discovered
Data type	Point in time
Template parameter	e.g. Infobox planet discovered, Infobox particle discovered, Infobox element discovery date, Infobox diamond found, Infobox fossil date discovered
Domain	all item that was discovered (e.g. astronomic objects, inventions, archaeological sites, animal/plant species...)
Example	<Uranus> discovery date <13 March 1781>
Proposed by	Paperoastro (talk)

Comments: general property useful for lots of items --Paperoastro (talk) 23:36, 6 March 2013 (UTC)

Support ~~Comment~~ Why not have a more succinct label like "discovery date"? Label wording aside, this property seems useful. Emw (talk) 03:40, 9 March 2013 (UTC)

Good idea! I have changed the name of the property. --Paperoastro (talk) 10:01, 9 March 2013 (UTC)

Support -- MichaelSchoenitzer (talk) 14:31, 9 March 2013 (UTC)

Support But it should be made clear that America wasn't "discovered" in 1492. Maybe add something like "discovered by mankind" in the description. --FA2010 (talk) 21:48, 15 March 2013 (UTC)

It is not so simple: in some cases two or more people discover something independently, and all of them are recognized as "discoverer". In these cases the discovery date will result to be not unique! --Paperoastro (talk) 16:06, 20 March 2013 (UTC)

Support Please provide more infobox examples. We should follow the infobox definitions. Mange01 (talk) 08:30, 20 March 2013 (UTC)

I add some other infobox examples. --Paperoastro (talk) 16:06, 20 March 2013 (UTC)

Support --Faux (talk) 07:45, 22 March 2013 (UTC)

Dissolved (en)

Done: dissolved, abolished or demolished date (P576) (Talk and documentation)

Description	The date (or year) the club was dissolved. Should not be wikilinked.
Data type	Point in time
Template parameter	en:template:Infobox football club dissolved
Domain	organization (football clubs)
Example	Q4384416
Source	External reference, Wikipedia list article
Robot and gadget jobs	they should be allowed
Proposed by	Xaris333 (talk) 15:54, 3 May 2013 (UTC)

I don't believe we have a date dissolved property pending, but we will need to wait for the timevalue datatype. I think this should be broadened to any organization. --Jfhutson (talk) 18:48, 5 May 2013 (UTC)

I agree. Thats why i named it Organization dissolved. Xaris333 (talk) 19:09, 5 May 2013 (UTC)

OK, sorry bout that. I guess the domain field and the section heading made me think these were intended just for football clubs. --Jfhutson (talk) 19:17, 5 May 2013 (UTC)

Comment It can just be named 'dissolved' with a date datatype. Joshbaumgartner (talk) 03:36, 10 May 2013 (UTC)

Done as Property:P576. Generic to all organisations, not just football clubs. Del_♉sion23 (talk) 21:18, 29 May 2013 (UTC)

Date of publication / Erscheinungsjahr / Date de publication

Done: publication date (P577) (Talk and documentation)

Description	Date of the publication of the book
Data type	Point in time
Proposed by	Tpt (talk) 20:20, 31 January 2013 (UTC)

Discussion

We should distinguish between the year a work was first published (Kafka: Der Process, 1925) and the date of a specific edition (El proceso, Madrid 2009). --Kolja21 (talk) 22:05, 31 January 2013 (UTC)
- I think that there will be an item for each version of the book in order to allow people to easily quote them in the reference part ofstatements. In that case I'm not sure (but I may have wrong) that the two properties are needed. Tpt (talk) 17:44, 1 February 2013 (UTC)
  - +1. This is the way Open Library solves the problem: Der Prozeß as a work (.../works/OL498751W) and one page for every edition (.../books/OL9051126M). --Kolja21 (talk) 18:31, 1 February 2013 (UTC)
    - Do we have different items for each edition? --NaBUru38 (talk) 21:38, 8 February 2013 (UTC)
      - No, but we will have qualifiers. Sven Manguard Wha? 06:11, 18 February 2013 (UTC)
Support. --NaBUru38 (talk) 21:38, 8 February 2013 (UTC)
- I'm not a proper librarian, but I know there are a lot of cases for "dates". Data of publication, date of the edition, date of reprint... Maybe we want a general "date" property with several qualifiers? As I said in Comment III up here, it really depends by the purpose of the metadata. We'll probably have a Wikipedia page for the "work" (FRBR-like) Der Prozeß, but we'll have also different scanned books on Commons, (ie translations, different editions, reprints, etc.). I think that Wikidata would be absolutely usefule especially for Commons and Wikisources, so I wonder how should we design the list of properties for books in Wikidata. --Aubrey (talk) 10:37, 18 February 2013 (UTC)
  - Support --Aubrey (talk) 09:32, 19 February 2013 (UTC)
Support and we'll need similar functions for all creative works, I should think. Shawn in Montreal (talk) 04:24, 27 February 2013 (UTC)
Support per Shawn --Wikijunkie (talk) 00:29, 11 March 2013 (UTC)

See publication date (P577) Snipre (talk) 21:44, 29 May 2013 (UTC)

Sandbox-TimeValue / Spielwiese-TimeValue / Bac à sable-TimeValue / Pagina delle prove-TimeValue

Status: Done

→ Property:P578

Description: any kind of values
Datatype: Time value (1 Sandbox type per available data type)
Domain: any kind of values
Infobox parameter: any/generic (but more for testing than productive)
Comments:

To be honest I am badly informed about wikidata, just to make that clear. I do think that I need a property to be created in order to store values, please confer Wikidata:Requests for permissions/Bot/DrTrigonBot and Wikidata talk:Infoboxes task force#Feasibility of DrTrigonBot/Subster to update Wikidata. Thanks for all your help and patience. Greetings --DrTrigon (talk) 20:54, 22 March 2013 (UTC)

Sorry. What do you need ? An property with a numeric datatype ? Or a property representing a numeric concept with a string as datatype ? If I take your example with swiss franc you want something like "currency division" to give the nominal value of each coin/note ( 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10, 20, 50, 100, 200, 1000)? Snipre (talk) 21:03, 22 March 2013 (UTC)

In fact I think a good thing would be a generic property (e.g. "DrTrigonBot Value" or even more generic "Bot Value") for the bot in cases when it has data to write for which no property was created yet - as it is the situation right now for a property "Currency Exchange Rate" (or similar) that is needed for swiss franc. This would allow the bot to already be tested or used without having the need to create always the suitable/correct property before being able to check if the bot works at all (in that specific situation), e.g. That would be a really good and useful/helpful thing! Thanks a lot for considering this and Greetings --DrTrigon (talk) 21:41, 22 March 2013 (UTC)

Just for a test you can see if there is a property in request for deletion using string as datatype or a property which not used in a lot of item or finally try on the demo version of wikidata. Snipre (talk) 22:05, 22 March 2013 (UTC)

Thats clear, currently I am using something else. Also the demo was already used to adopt the bot code. What I need is something permanent. In future and daily (usual) operation there will always be a case where you have to test, since the bot is freely configurable from here - by any user. --DrTrigon (talk) 22:36, 22 March 2013 (UTC)

I think testing bots should not be done on the productive Wikidata, except in the sandbox.--Faux (talk) 17:04, 23 March 2013 (UTC)

It is not testing bots, but testing setups - as on wikipedia itself you will always have situations were you have to change something, modify setup of data, configuration and so on... at least that is what holds for me. Then I have to disagree because testing of bots is needed, e.g. in order to fullfill the bot flag request a given number (e.g. 250) of test edits have to be done. And there will in future clearly be other situations - as soon wikidata will be used frequently... Greetings --DrTrigon (talk) 20:55, 23 March 2013 (UTC)

I mean ... it does not need to be something bot specific, what about general maintenance (for human users)? I would even more support such a property, that can be used if it is e.g. not clear yet what property to use, one has to be renamed, other name conflicts or anything else... --DrTrigon (talk) 20:59, 23 March 2013 (UTC)

Why not simply a sandbox property per datatype ? I do not see what harm can be done with that, as long as it is clear that it is a sandbox. --Zolo (talk) 21:29, 23 March 2013 (UTC)

Sounds good! (+1) Thanks for the idea! Greetings --DrTrigon (talk) 22:41, 23 March 2013 (UTC)

Do you plan using that sandbox property only on sandbox/test items, or also on production items? --Faux (talk) 12:12, 24 March 2013 (UTC)

I do not see anything wrong in using it other items. It will not look very good, and if we can avoid using it too massively, that is better, but raw Wikidata items do not look very good anyhow. The important thing is that it does not unintendedly get transcluded to Wikipedias and other clients. And as long as they do not query sandbox statements, I see no reason for that to happen. --Zolo (talk) 12:22, 24 March 2013 (UTC)

So... are we done here, or for what are we waiting? ;) If you agree I would step forwards and create following 3 properties:

Label: Sandbox-CommonsMediaFile / Description: Sandbox property for value of type "Commons Media File" / Data type: Commons Media File
Label: Sandbox-Item / Description: Sandbox property for value of type "Item" / Data type: Item
Label: Sandbox-String / Description: Sandbox property for value of type "String" / Data type: String

any comments or thoughts on this? Thanks and Greetings --DrTrigon (talk) 10:52, 29 March 2013 (UTC)

Ok here we go:

so these can be considered done but I think it makes sence to propose the future ones too and set them to the pending page:

Label: Sandbox-Quantity / Description: Sandbox property for value of type "Quantity" / Data type: Quantity
(and all other data types to be introduced in future...)

Thanks for all your help! Greetings --DrTrigon (talk) 01:09, 30 March 2013 (UTC)

IMA status / IMA Status

Done: IMA status and/or rank (P579) (Talk and documentation)

Description	Descripes the official IMA status of a mineral
Data type	Item
Template parameter	not yet part of any infobox
Domain	minerals (items)
Allowed values	9 possible inputs per language (approved, grandfathered, redefined, renamed, questionable + approved, questionable + grandfathered, questionable + discredited, published without approval, discredited)
Example	e.g. Abelsonite = approved, Abernathyite = grandfathered
Source	http://pubsites.uws.edu.au/ima-cnmnc/IMA_Master_List_(02-2013).pdf (3rd column)
Robot and gadget jobs	Bot could collect data from 3rd column and add it to minerals found in 1st column.
Proposed by	Tobias1984 (talk)

Would be nice for mineral queries to exclude for example all questionable minerals. Tobias1984 (talk) 07:06, 20 April 2013 (UTC)

Support --Sbisolo (talk) 08:06, 22 April 2013 (UTC)

Support --Chris.urs-o (talk) 12:02, 22 May 2013 (UTC)

Oppose the datatype. With only few possible values, item would be much better, because then you only have to translate the values to all languages once pr. value instead of once pr. mineral. Byrial (talk) 22:32, 26 April 2013 (UTC)

datatype changed to item. --Tobias1984 (talk) 14:58, 28 April 2013 (UTC)

I'd like 9 possible outputs. We have already spodiosite (discredited 2003) (Q3966942) and pimelite (Q3905061). Maybe, the IMA status should be parted in two. --Chris.urs-o (talk) 17:39, 28 April 2013 (UTC)

from time (since)

Done: start time (P580) (Talk and documentation)

Description	The time the claim began being valid
Data type	Point in time
Domain	Any claim that is valid within a certain range of time
Allowed values	Any time before the end time of the claim (if the claim has an end time)
Example	examples include: Mexico head of government Felipe Calderón from time December 1, 2006 India instance of sovereign state since 26 January 1950
Proposed by	Emw (talk) 13:36, 20 April 2013 (UTC)

Note that in cases like population, where change in the real-world value is effectively continuous but is only measured in discrete intervals, this qualifier would indicate the range of time the value was valid according to a given source. Here, that would be the official census of India. Emw (talk) 13:48, 20 April 2013 (UTC)

A good point was made in the proposal for the 'to time' qualifier that because census results typically represent a snapshot (i.e. an instantaneous measurement), it's incorrect to assert that the sources say claims about population counts are valid for a range of time. So I've added an 'as of' alias to this qualifier, and adjusted the 'domain' of this property to reflect that. Emw (talk) 15:32, 20 April 2013 (UTC)

Support This is a really common qualifier for a lot of property, any idea when the time datatype would be created? --Napoleon.tan (talk) 13:51, 20 April 2013 (UTC)
Support --Paperoastro (talk) 13:58, 20 April 2013 (UTC)
Comment. Maybe an other property for "as of": "from time" is for the beginning of a time range and "as of" for a specific date time. Tpt (talk)

Are you suggesting that the 'from time' qualifier would only be valid if the 'end time' qualifier were also applied to the claim? (And the converse, that 'end time' would only be valid if 'from time' were applied?)

In that case, claims that have begun but not ended, e.g. 'India instance of sovereign state since 26 January 1950', 'Universe instance of physical body since 13.8 billion years ago' would presumably also only be valid for 'as of' and not this 'from time' qualifier. Emw (talk) 16:30, 20 April 2013 (UTC)

See as of. Emw (talk) 21:20, 20 April 2013 (UTC)

Yes, I'm suggesting that the 'from time' qualifier would only be valid if there is an 'end time' qualifier. That will allow us to move easily to a time range (value of the 'as of' qualifier) if the range feature is added in the future. So Support now. Tpt (talk) 16:46, 28 April 2013 (UTC)

Support – Now that it is separated from "as of", it is clear and unambiguous. And it is also very much needed. -- Byrial (talk) 05:51, 21 April 2013 (UTC)
Support. Conny (talk) 13:58, 28 April 2013 (UTC).
Support--Saehrimnir (talk) 10:39, 8 May 2013 (UTC)
Support --NaBUru38 (talk) 13:06, 14 May 2013 (UTC)
Support Note that we require such a "start date"-property for all kinds of events, too. I think there's no need to create another property, but instead we can use this one. So the domain should include events as well.--Kompakt (talk) 09:05, 23 May 2013 (UTC)
Created as start time (P580), as "start date" considering the above comments that it need not always be a qualifier.

Overlapping Proposals

start date and time

Not done

Description	The date and time an item began
Data type	Point in time
Template parameter	Many
Domain	Any item which has a time range and a start date and time. Does not apply to items that are considered instantaneous events.
Allowed values	Any time before the end time
Example	2012–2013 Central African Republic conflict: December 10, 2012; 89th United States Congress: January 3, 1965; Aztec Empire: March 13, 1428; Cretaceous Period: 145 million years ago; Universe: 13.8 billion years ago
Proposed by	Emw (talk) 04:00, 27 March 2013 (UTC)

The example values would be formatted per TimeValue. This property would go into Wikidata:Property_proposal/Pending until that datatype is available. Emw (talk) 04:01, 27 March 2013 (UTC)

Dates held

Description: I think that office held should be augmented with the dates during which the subject held that office. In that way, we could specify that e.g. George W. Bush was Governor of Texas from 17 Jan 1995 until 21 December 2000, and then President from 20 Jan 2001 to 20 Jan 2009 (dates taken from enwiki). Inputting the dates that way could also end disputes over how to format them (DMY, MDY, etc.): they could be automatically displayed in the format that users chose, without you having to change anything in edit mode in Wikipedia itself.
Infobox parameter: Can be mapped to e.g. en:Template:Infobox Officeholder: term_startn, term_endn.
Datatype: Date
Domain: Person
Allowed values: Dates
Source: WP infoboxes
Example item and value: Barack Obama. Office held: President of the United States. Dates held: 20 Jan 2009–present.
Robot and gadget jobs: Perhaps mining these from WP infoboxes. Could check for inconsistencies between different language versions of Wikipedia.

It Is Me Here ^{t / c} 12:25, 14 March 2013 (UTC)

Comment. I'd like to see how "qualifiers" work before this type of property is made. This property can't be entered as its own statement as it would have no meaning without reference to some other statement. Espeso (talk) 06:06, 15 March 2013 (UTC)

to time (until)

Done: end time (P582) (Talk and documentation)

Description	The time the claim ended being valid
Data type	Point in time
Domain	Any claim that is valid within a certain range of time
Allowed values	Any time after the beginning time of the claim (if the claim has a beginning time)
Example	Mexico head of government Felipe Calderón to time November 30, 2012
Proposed by	Emw (talk) 13:40, 20 April 2013 (UTC)

(See comment from Lavallen below.) Note that in cases like population, where change in the real-world value is effectively continuous but is only measured in discrete intervals, this qualifier would indicate the range of time the value was valid according to a given source. Here, that would be the official census of India. Emw (talk) 13:48, 20 April 2013 (UTC)
Support --Napoleon.tan (talk) 13:52, 20 April 2013 (UTC)
Support --Paperoastro (talk) 13:59, 20 April 2013 (UTC)
I understand the Mexico and US-example, but not the India-example. A census is normally made a certain day, or a at least a certain year. Such numbers are very seldom in a very long range of time. Would it not be better to search for the latest census-date (2001) if you want to know the numbers for 2010? -- Lavallen (block) 14:29, 20 April 2013 (UTC)

Great point! You're right at least about the United States census; the census makes a point of noting that it represents things as they were on precisely April 1. So at least the US census is a snapshot, i.e. an instantaneous measurement. I'm not familiar with the details of the Indian census, but I assume it's the same in that regard.

The broader clarification seems to be this: if a statement represents a fact tied to a specific date, then it should have a "from time" qualifier but not an "to time" qualifier. Population counts and estimates are a good example of this: the sources are only asserting that their claim is valid for one specific date, not a range of time. Emw (talk) 15:22, 20 April 2013 (UTC)

Question – How would you distinguish between a statement for a specific date, and a statement for a state that has not yet ended, and thus is still valid? -- Byrial (talk) 20:31, 20 April 2013 (UTC)

With as of! Emw (talk) 21:19, 20 April 2013 (UTC)

'to time' not needed for population time stamps. 145.53.76.181 15:12, 20 April 2013 (UTC)
Support – needed together with "from time" -- Byrial (talk) 05:52, 21 April 2013 (UTC)
Support. But how to handle two not crossing timelines for an object? From 1992-1999 and 2001-2005 -> will this work? Conny (talk) 14:00, 28 April 2013 (UTC).
- It will most likely work, even if it will look like: From: 1992, 2001; To: 1999, 2005; But it will be a challenge to make templates who can make it look nice. -- Lavallen (block) 14:19, 28 April 2013 (UTC)
  - Wouldn't it be better to just set it as two separate statements, each with their own from-time/to-time qualifiers? --Yair rand (talk) 15:51, 28 April 2013 (UTC)
Should we decide in advance whether the values of this are inclusive or exclusive (ie does September 1-September 20 include the 20th?) ? --Yair rand (talk) 15:51, 28 April 2013 (UTC)

Good question. I think we should decide that before this qualifier (and from time) is created. In George W. Bush, the subject's presidency is shown as January 20, 2001 – January 20, 2009. According to First inauguration of George W. Bush, he was in office as of 12:01 p.m. January 20, 2001. So those 'from date' and 'to date' values are inclusive. I'm not sure if this is standard for that field's use for all politicians, though.

For what it's worth, popular SQL implementations of "BETWEEN" make that operator inclusive, see e.g. BETWEEN in MySQL. Perhaps that indicates that this qualifier should be inclusive.

Are there any prominent counterexamples, where 'from date' or 'to date' are used in the exclusive sense in a certain domain?

Should this be limited to use as a qualifier? Some main items could use this, too. For example, Q1719918. --Yair rand (talk) 15:51, 28 April 2013 (UTC)

There have been property proposals for 'date', 'start time' and 'end time' awaiting feedback for over a month (over three months for 'date') at Wikidata:Property_proposal/Event, which would apply to things like Presidency of George W. Bush (Q1719918). The labels 'start time', 'end time' and 'date' seem more idiomatic to apply to events than 'from time', 'to time' and 'as of', with 'date' and 'as of' seeming especially awkward to interchange. (Saying 'Tenerife airport disaster <as of> March 27, 1977' is clearly worse than saying 'Tenerife airport disaster <date> March 27, 1977'.) Emw (talk) 18:38, 28 April 2013 (UTC)

Support--Saehrimnir (talk) 10:39, 8 May 2013 (UTC)
Support --NaBUru38 (talk) 13:07, 14 May 2013 (UTC)
Support As mentioned above, the domain should include events, too (where this wouldn't be used as a qualifier but a "top-level"-property).--Kompakt (talk) 09:07, 23 May 2013 (UTC)
Created as end time (P582), "end date" considering the above comments that it need not always be a qualifier.

end date and time

Not done

Description	The date and time an item ended
Data type	Point in time
Template parameter	Many
Domain	Any item which has a time range and an end date and time. Does not apply to items that are considered instantaneous events.
Allowed values	Any time after the start time
Example	89th United States Congress: January 3, 1967; Aztec Empire: August 13, 1521; Cretaceous Period: 66 million years ago
Proposed by	Emw (talk) 04:00, 27 March 2013 (UTC)

The example values would be formatted per TimeValue. This property would go into Wikidata:Property_proposal/Pending until that datatype is available. Emw (talk) 04:01, 27 March 2013 (UTC)

as of

Done: point in time (P585) (Talk and documentation)

Description	The point in time for which the source supports the claim
Data type	Point in time
Domain	Any claim that is supported by a source for a specific point in time, but not a range of time
Allowed values	Any time
Example	United States of America population 308,745,538 as of April 1, 2010
Proposed by	Emw (talk) 21:15, 20 April 2013 (UTC), originally suggested by Tpt

Support – It seems clear to me that we need a separate qualifier for point of time. (Compare to the discussions for "from time" and "to time" -- Byrial (talk) 06:00, 21 April 2013 (UTC)
Support - Complete the set of qualifier properties for "time". --Paperoastro (talk) 16:08, 21 April 2013 (UTC)
Support - So how can qualifier be created? --Napoleon.tan (talk) 06:09, 22 April 2013 (UTC)
SupportThey are not. Qualifiers are just properties of properties so every property can be used as Qualifer. That means if the property proposals for 'date', 'start time' and 'end time' are succesful this is not needed anymore.--Saehrimnir (talk) 10:39, 8 May 2013 (UTC)
Support --Viscontino (talk) 14:04, 8 May 2013 (UTC)
Support --NaBUru38 (talk) 13:07, 14 May 2013 (UTC)
I would prefer a more general "date" property, as it would be applicable both as an "as of" qualifier and as a stand-alone statement for punctual events. --Zolo (talk) 12:24, 30 May 2013 (UTC)
Created as point in time (P585) per Zolo --Saehrimnir (talk) 12:47, 30 May 2013 (UTC)

Date / Datum /

Description: date when the event occured
Datatype: Date
Links:
Domain: historical events like catastrophic
Infobox parameter example: aircraft occurrence: en:Template:Infobox_aircraft_occurrence (date parameter)
Comments: --Faux (talk) 13:41, 18 February 2013 (UTC)
Some events span periods of time, days, weeks, etc. So, this would need to be start and end date/time. Probably applies to almost all events. Danrok (talk) 20:11, 21 February 2013 (UTC)

Support Doostdar (talk) 14:46, 7 March 2013 (UTC)

Obviously

Support. I can't believe that we have over 300 properties, but none to say that the 2004 elections were held in 2004. --NaBUru38 (talk) 19:26, 19 March 2013 (UTC)

- - Well, Wikidata doesn't actually support the Date data type yet...
  - Should this be split into start date/end date, or does the data type handle that by itself? --Yair rand (talk) 00:11, 20 March 2013 (UTC)

Support: Essential property for events. Emw (talk) 02:40, 27 March 2013 (UTC)

IpniAuthorId

Done: IPNI author ID (P586) (Talk and documentation)

Description	Author-Id of a taxon author (P405) maintained by International Plant Names Index
Data type	String
Domain	Source of botanist author abbreviation (P428)
Example	IpniAuthorId of L. (Carl von Linné) is 12653-1
Format and edit filter validation	Single value, Unique value
Robot and gadget jobs	Add `'http://www.ipni.org/ipni/idAuthorSearch.do?id=$1'` to Gadget-AuthorityControl.js
Proposed by	Succu (talk)

Discussion

Provides a direct link to the International Plant Names Index whichs maintains the botanist author abbreviation (P428). Should be used as source. --Succu (talk) 13:20, 26 May 2013 (UTC)

Support - sinnvoll. --Tobias1984 (talk) 07:24, 29 May 2013 (UTC)

Maritime Mobile Service Identity (MMSI)

Done: MMSI (P587) (Talk and documentation)

Description	MMSI is described here: MMSI. A unique ID for ships. Could link to: http://www.marinetraffic.com/ (forms part of the URL).
Data type	String
Domain	term
Example	Sample: Ebba Mærsk (Q4037895) => 220497000
Source	various sources, exists in some infoboxes for ships, otherwise easily found
Proposed by	Danrok (talk) 17:25, 25 May 2013 (UTC)

Discussion

Support --Tobias1984 (talk) 21:01, 26 May 2013 (UTC)

ISO

Done: ISO standard (P503) (Talk and documentation)

Description	the ISO (International Standardization Organization) reference
Data type	String
Template parameter	authority control
Domain	entities standardized by ISO
Allowed values	valid ISO numbers; e.g. 1:400, 9001, 27001
Example	<Office Open XML> standardized by ISO <29500>
Source	http://www.iso.org/iso/search/extendedsearchstandards.htm?formKeyword=&displayForm=true&published=true
Proposed by	Faux (talk)

Support Hurricanefan24 (talk) 18:51, 28 March 2013 (UTC)

Comment I don't think this is an infobox parameter. Do you have a link? --Kolja21 (talk) 17:44, 29 March 2013 (UTC)

Support --Viscontino (talk) 20:53, 7 May 2013 (UTC)

Support Standardized, useful - Joshbaumgartner (talk) 07:38, 9 May 2013 (UTC)

Done: P503 -- MichaelSchoenitzer (talk) 23:17, 10 May 2013 (UTC)

Team years (en)

Not done

Description	The years of appearances of player for every team he played with.
Data type	Number (not available yet)
Template parameter	en:template:Infobox football biography years
Domain	person
Allowed values	1850-2050
Example 1	MISSING
Example 2	MISSING
Example 3	MISSING
Source	External reference, Wikipedia list article
Robot and gadget jobs	they should be allowed
Proposed by	Xaris333 (talk) 01:26, 3 May 2013 (UTC)

Oppose Once the date datatype is available, it seems clear we will quickly have generic 'from/start' and 'to/end' properties which should cover this when used as qualifiers for 'member of team' claims. Joshbaumgartner(talk) 09:33, 9 May 2013 (UTC)

Ok. But when will be available? Xaris333 (talk) 17:07, 9 May 2013 (UTC)

Comment They are working right now on this data type (see Wikidata:Status_updates). However, no idea how long it would still take. --Nightwish62 (talk) 09:51, 11 May 2013 (UTC)

Oppose as user Joshbaumgartner. --Nightwish62 (talk) 09:51, 11 May 2013 (UTC)

Oppose per Joshbaumgartner and Nightwish62. --Ricordi samoa 12:14, 22 May 2013 (UTC)

Currentclub (en)

Not done

Description	The current club of a player
Data type	Item
Template parameter	en:template:Infobox football biography currentclub
Domain	person
Allowed values	1
Example 1	MISSING
Example 2	MISSING
Example 3	MISSING
Source	External reference, Wikipedia list article
Robot and gadget jobs	they should be allowed
Proposed by	Xaris333 (talk) 01:26, 3 May 2013 (UTC)

~~Support~~ --Tobias1984 (talk) 14:34, 6 May 2013 (UTC)
Comment - We should probably rename this to "club" and then add time qualifiers. Queries can return the current club. --Tobias1984 (talk) 13:54, 7 May 2013 (UTC)

Perhaps this cam be done in member of sports team. Xaris333(talk) 14:28, 7 May 2013 (UTC)

Property:P54 is redundant enough already to Property:P463, which is arguably redundant to Property:P361. --Jfhutson (talk) 17:04, 7 May 2013 (UTC)

Oppose Redundant, can be done with time qualifiers. —★PοωερZ_{_talk} 20:27, 7 May 2013 (UTC)

Oppose Time sensitive sister-property to Member of sports team. Qualifiers will allow 'current' team to be derived. Joshbaumgartner (talk) 09:38, 9 May 2013 (UTC)

Assocciation Football Player Position (en)

Not done

Description	The player's most common position or positions. If a player is known for playing in multiple roles then explain the point more fully within the article.
Data type	Item
Template parameter	en:template:Infobox football biography position
Domain	person
Allowed values	I suggest the use only of the general positions Goalkeeper, Defenter, Midfielder, Stiker
Example 1	MISSING
Example 2	MISSING
Example 3	MISSING
Source	External reference, Wikipedia list article
Robot and gadget jobs	they should be allowed
Proposed by	Xaris333 (talk) 01:26, 3 May 2013 (UTC)

Oppose --Tobias1984 (talk) 08:26, 4 May 2013 (UTC) changed to oppose. --Tobias1984 (talk) 21:24, 20 May 2013 (UTC)

Oppose redundant with Position (on team) which is perfectly suitable for association football positions as well as any other sport. Joshbaumgartner (talk) 09:49, 9 May 2013 (UTC)

Oppose as Joshbaumgartner. --Nightwish62 (talk) 09:45, 11 May 2013 (UTC)

Assocciation Football Player Height (en)

Not done

Description	The player's height in the units most common within the country he or she plays.
Data type	Number (not available yet)
Template parameter	en:template:Infobox football biography height
Domain	person
Allowed values	0-10
Example 1	MISSING
Example 2	MISSING
Example 3	MISSING
Source	External reference, Wikipedia list article
Robot and gadget jobs	they should be allowed
Proposed by	Xaris333 (talk) 01:26, 3 May 2013 (UTC)

Oppose I am sure we are going to have a "height" property and I don't see that this property could have a different value. --Tobias1984 (talk) 08:24, 4 May 2013 (UTC)

I don't think "height" is use out of sports templates. But, we can change the title as height. Xaris333 (talk) 12:52, 4 May 2013 (UTC)

Ok. I cancel this proposal and lets discuss the other which came first and its general. Xaris333 (talk) 13:44, 4 May 2013 (UTC)

Student of (en)

Not done

Description	have been the student of someone
Data type	Item
Domain	person
Example	there is already Property:P185, but that does not apply to older times. In greek philosophy the relationship between a student and teacher is most important. For instance, Q859 => Q913 or Q1287486 => Q317947. In fact Student of could even replace P185 as it covers a broader set of situations.
Proposed by	Alexander Doria (talk) 22:11, 31 May 2013 (UTC)

Discussion

Alexander Doria (talk) 22:11, 31 May 2013 (UTC)

see above: Wikidata:Property_proposal/Person#student--Kompakt (talk) 07:01, 1 June 2013 (UTC)

Sorry for the duplicate. This proposal can be closed. Alexander Doria (talk) 13:15, 1 June 2013 (UTC)

Largest city/ größte Stadt / Plus grande ville/ Крупнейший город

Not done

Description	Largest city in an administrative division
Data type	Item
Template parameter	w:Template:Infobox U.S. County largest city
Domain	Conties, states, countries
Allowed values	Boroughs, cities, towns
Example	Q488693 (Q1133544), Q1400 (Q1345), Q30 (Q60)
Source	English Wikipedia
Proposed by	...Jakob ^{Megaphone,Telescope}

Comment: Redundant of proposal Wikidata:Property_proposal/Place#largest_city_.2F_gr.C3.B6.C3.9Fte_Stadt. --Nightwish62 (talk) 10:04, 11 May 2013 (UTC)

Oppose Subjective property: which criterion is used to determine the largest parameter ? This can be deduced by multiple parameters query like "city of XX with the biggest population" or "city of XX with the biggest GNP". Snipre(talk) 09:17, 12 May 2013 (UTC)

Oppose, per Snipre. --Yair rand (talk) 21:33, 12 May 2013 (UTC)

Continental confederation affiliation (en)

Not done

Description	The year the association joined the region (AFC, CAF, CONCACAF, CONMEBOL, OFC, UEFA))
Data type	Number (not available yet)
Template parameter	en:template:Infobox football association Region affiliation
Domain	organization (football clubs)
Allowed values	Number (1916- ) (The oldest region association create on 1916)
Example 1	MISSING
Example 2	MISSING
Example 3	MISSING
Source	External reference, Wikipedia list article
Robot and gadget jobs	they should be allowed
Proposed by	Xaris333 (talk) 02:52, 9 May 2013 (UTC)

Oppose This is not necessary. Simply use continental confederation with a qualifier from/start (e.g. My Favorite Team - continental confederation - CONCACAF - from - 9 May 2013). Obviously this has to wait on new datatypes, but so does this proposal. Joshbaumgartner (talk) 04:14, 10 May 2013 (UTC)

Oppose as above Snipre (talk) 09:06, 12 May 2013 (UTC)

Host city / Austragungsstadt

Not done

Description	city in which the event takes/took place
Data type	Item
Template parameter	"City" in en:template:Infobox GrandSlamTournaments (and many others)
Domain	event
Allowed values	cities
Example	en:US Open (tennis): "New York City"; en:2000 Republican National Convention: "Philadelphia"; en:Super Bowl XLII: "Glendale, Arizona", en:Eurovision Song Contest 2009: "Moscow"
Proposed by	--Kompakt (talk) 08:21, 26 April 2013 (UTC)

Oppose covered by P:P131, and this broadens it to be able to cover events hosted in counties, provinces, etc, not just cities. Joshbaumgartner (talk) 04:47, 10 May 2013 (UTC)

type (of school, university, ...)

Not done

Description	the type of school (all schools, universities, colleges)
Data type	Item
Template parameter	type (en:Infobox university)
Domain	universities/colleges etc.
Example 1	MISSING
Example 2	MISSING
Example 3	MISSING

Comments: Values would include public, business school, music school and many others. Danrok (talk) 15:58, 24 February 2013 (UTC)
- I'm a bit worried about the range of types. Public vs priavate is binary. Arts vs business vs technical is an axis. University vs universitary institute vs God knows what depends on legislation. --NaBUru38 (talk) 23:15, 25 February 2013 (UTC)

Perhaps it could be limited to public, private and national? Are there any other main types? Danrok (talk) 15:28, 26 February 2013 (UTC)

If it's truly "all schools," then primary, secondary, and post-secondary would seem necessary. Shawn in Montreal (talk) 22:40, 3 March 2013 (UTC)

Oppose Start by using Is a(n). There is only one "type" field in that infobox, so there is no risk of conflict. The allowed item objects is not a limited list, so the bots don't need another type property. Mange01(talk) 02:27, 7 March 2013 (UTC)

Oppose: redundant with instance of (P31) and subclass of (P279). (talk) 02:36, 27 March 2013 (UTC)

Looks a little to country-specific to be usefull in a global perspective. It is always difficult for me as a Sweede to describe what kind of education I have, since we normally starts in University later than other in other nations and our time in school is normally shorter. Also post-graduate students have another kind of relation to the school than in other countries, even if the exam is the same. Lavallen (block) 09:05, 20 April 2013 (UTC)

Oppose per Emw's redundancy comment. Joshbaumgartner (talk) 10:31, 9 May 2013 (UTC)

Song engaged to /

Not done

Description	song(s) name(s) granted to the traditional custom
Data type	Item
Template parameter	it can be easily excluded from other certain ceremony templates or categories eg. ,and
Domain	subject domain is ceremonies, celebrations, festivals and holiday; object domain is song(s) or pieces of songs or poem(s) name(s) recently or traditionally sung or written
Example 1	MISSING
Example 2	MISSING
Example 3	MISSING

Comments: Some cultural events are traditionally accompanied by several old songs eg. you cannot consider Persian Nowruz ceremony separable from Doa-ye-Tahvil song in Iran. Sometimes there are songs improvised on a ceremony eg. Nowrouz Album, by Iranian singer, Shahram Nazeri, is dedicated exclusively to Nowrouz festival. Another example of this type is Happy Holiday, a popular Christmas song composed by Irving Berlin. As well as, "The Christmas Song" written in 1944 by M. torme & B. Wells and "stay cool by thinking cool", the most-performed Christmas song, together are some other samples for the proposed wikidata property. Doostdar (talk) 20:34, 8 March 2013 (UTC)
- Oppose, the relation between the two subjects is too weak it me. --NaBUru38 (talk) 19:27, 19 March 2013 (UTC)
- Oppose, I think this should be replaced with 'theme' as this would allow a less niche property whilst also helping ensure a better world view (they have different Christmas songs in Spain vs. U.K.). Basically I think this should be a property attached to the song etc. not the event.

Championship seasons

Not done

Description	seasons in which team won a championship
Data type	Item
Domain	organization (sports teams)
Allowed values	type of linked items,allowed values (if limited)
Example	The Florida Marlins item could use 1997 Florida Marlins season and2003 Florida Marlins season as objects that fit in this property.
Proposed by	AutomaticStrikeout

Discussion

This property would allow us to list championship seasons in items about sports teams. AutomaticStrikeout 15:35, 11 May 2013 (UTC)

Oppose Use the title of the competition or the name of the cup with the year as qualifier. Wikidata is not Wikipedia linking article between them. Or the best is to used the below proposal Wikidata:Property_proposal/Organization#Standings positionwith the first position in order to determine the years when the team won the competition. Or use the propertyaward received Snipre (talk) 09:43, 12 May 2013 (UTC)

FIFA affiliation (en)

Not done

Description	The year the association joined FIFA
Data type	Number (not available yet)
Template parameter	en:template:Infobox football association FIFA affiliation
Domain	organization (football clubs)
Allowed values	1904- (FIFA founded on 1904) or Not member
Example 1	MISSING
Example 2	MISSING
Example 3	MISSING
Source	External reference, Wikipedia list article
Robot and gadget jobs	they should be allowed
Proposed by	Xaris333 (talk) 02:52, 9 May 2013 (UTC)

Oppose This is not necessary. Simply use member of with a qualifier from/start (e.g. My Favorite Team - member of - FIFA - from - 9 May 2013). Obviously this has to wait on new datatypes, but so does this proposal. Joshbaumgartner (talk) 04:05, 10 May 2013 (UTC)

Oppose as above Snipre (talk) 09:07, 12 May 2013 (UTC)

Book (title) / Buch (Titel) / Livre (titre)

Not done

Description	The title of the book.
Data type	Item
Example 1	MISSING
Example 2	MISSING
Example 3	MISSING

Discussion

Comment: Example: Source The World Factbook. --Kolja21 (talk) 18:06, 19 February 2013 (UTC)
- Oppose, the item description exists for that. --NaBUru38 (talk) 19:31, 19 March 2013 (UTC)

The item description is multilingual. Only one of those languages is the book title. Filceolaire(talk) 11:43, 6 April 2013 (UTC)

Oppose: if you mean original title, there is Property:P357. I think the item label is for that.--CENNOXX (talk) 14:21, 6 April 2013 (UTC)

{{Not done}} per consensus against its creation and existence of Property:P357. — ΛΧΣ²¹ 00:32, 14 April 2013 (UTC)

Actually I had created P:P357 as "title", par another discussion (about journal articles, I think). It was renamed to "original title" afterwards, so that we stil need a "title" property. We can really not assume that the label will always be the same as the title. For instance, old books may have very long titles, that do not fit into a label, or a book may have two titles (for instance translations), or an article in non-latin script may have a transliterated label (which would follow a rather common practice) that would obscure the real title. I think the simplest solution would be to rename P:P357 back to "title", as using a qualifer for "original" would be more flexible, and much clearer books that were never translated, and where title and original title are the same. In any case, a "title" property is needed. I don't see any use to restricting to books though, as the property is even more needed for journal articles cites in sources, and for some artworks. --Zolo(talk) 21:36, 14 April 2013 (UTC)

Sub continental confederation affiliation (en)

Not done

Description	The year the association joined the subregion (i.e. CECAFA, CEMAC, COSAFA, UNAF, WAFU))
Data type	Number (not available yet)
Template parameter	en:template:Infobox football association Region affiliation
Domain	organization (football clubs)
Allowed values	Number (1916- ) (The oldest region association create on 1916)
Example 1	MISSING
Example 2	MISSING
Example 3	MISSING
Source	External reference, Wikipedia list article
Robot and gadget jobs	they should be allowed
Proposed by	Xaris333 (talk) 02:52, 9 May 2013 (UTC)

Oppose This is not necessary. Simply use subcontinental confederation with a qualifier from/start (e.g. My Favorite Team - subcontinental confederation - UNAF - from - 9 May 2013). Obviously this has to wait on new datatypes, but so does this proposal. Joshbaumgartner (talk) 04:14, 10 May 2013 (UTC)

Oppose as above Snipre (talk) 09:07, 12 May 2013 (UTC)

Subsidiary

Not done

Description	An organisation which is a subsidiary of another organisation
Data type	Item
Template parameter	Can be mapped to en:template:infobox company, with its field called subsid. Alsoen:template:infobox airline, though its field is called subsidiaries.
Domain	Organisation
Allowed values	linked objects
Example	en:British Airways would be listed as a subsidiary on en:International Airlines Group. Then, en:BA CityFlyer, en:OpenSkies and en:British Airways Limited would be listed as subsidiaries on the British Airways page.
Source	several infoboxes use this, like the ones given above, and probably others
Robot and gadget jobs	Should presumably be reciprocal with parent company, proposed above.

have left the German/French names blank because the interwiki links for subsidiary both link to articles called "filiale" which translate as "branch", and I'm not 100% if that's exactly the same meaning. (After all, branch can also mean two branches of the same bank, for example.) Buttons to Push Buttons (talk) 09:59, 10 March 2013 (UTC)

Comment I don´t know, but Property:P127 (owner of the subject) seems to be rather similar. "The owner of British Airways is International Airlines Group". --Goldzahn (talk) 23:36, 11 March 2013 (UTC)

You're right, for some reason I was under the impression that property was for people only. Would it be an issue to use a field called owner for infoboxes which use parameter subsid? Not something I'm qualified to answer. And is there a need for distinction between ownership by people and ownership by organisations? Not sure on this one, but perhaps not. Buttons to Push Buttons (talk) 23:43, 11 March 2013 (UTC)

I think, that at the moment only the developers are qualified to answer. In my view,this shows that the property name is used only in the infoboxes, but will not be displayed. --Goldzahn (talk) 00:16, 12 March 2013 (UTC)

Actually, P127 should be on the above property, "subsidiary" is the opposite :). I dont know if there is any benefit in having a different property for people and for companies, but the current trend is toward rather general property, so it would sound more consistent to have just one. And the current property is already used for companies. --Zolo (talk) 18:38, 12 March 2013 (UTC)

Oppose: One property is enough. With checking for a second property e.g. gnd-type or something else one can conclude if the property means subsidiary or something else. I added this name as alias

And Zolo is right, subsidaries is the opposite of P:P127. This confused me for some minutes. I really hope we get the “bidirectional” properties Wikidata:Project_chat#bidirectional_properties--Svebert (talk) 10:44, 16 March 2013 (UTC)

Move from unsorted to organizations. Joshbaumgartner (talk) 05:17, 17 May 2013 (UTC)

Oppose no need for this as it can be queried. Joshbaumgartner (talk) 05:17, 17 May 2013 (UTC)

Already created: see Property:P355 Snipre (talk) 18:18, 26 May 2013 (UTC)

Country of origin / Produktionsland / …

Done: country of origin (P495) (Talk and documentation)

Description	The country of origin from the creative work.
Data type	Item
Template parameter	en:Template:Infobox television & en:Template:Infobox film: country, de:Vorlage:Infobox Fernsehsendung & de:Vorlage:Infobox Film: Produktionsland/PL
Domain	films, television series, maybe other creative works
Allowed values	countries
Example	United States for Breaking Bad
Source	infobox
Robot and gadget jobs	possible
Proposed by	CENNOXX (talk)

I don't know if other creative works besides film and television series use this property. It would also be possible to reuse theProperty:P17, if the description is slightly adjusted, but I would prefer to seperate the "country of origin" from a the location of an item (Property:P17). Please comment what your opinion is!--CENNOXX (talk) 16:33, 11 April 2013 (UTC)

Done Created the Property:P495 – Country of origin. nearly a month without any objections.--CENNOXX (talk) 17:29, 6 May 2013 (UTC)

Subtitle / Untertitel / Sous-titre

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

Description	The subtitle of the book.
Data type	String

Discussion

Helpful for the info boxes. Especially scientific work tend to have pretty long subtitles, that are not always suitable to print in full length.--Kolja21 (talk) 01:29, 4 February 2013 (UTC)
- Support, although I'm not familiar with works with subtitles. --NaBUru38 (talk) 19:31, 19 March 2013 (UTC)
- Support, should also be used for movies and other creative works --Nightwish62 (talk) 17:59, 26 March 2013 (UTC)
  - Indeed, documentary films in particular often have use a subtitles, after the main title. Shawn in Montreal (talk) 23:08, 9 April 2013 (UTC)
- Support. I would recommend original subtitle, like original title. Superm401 -Talk 06:26, 12 April 2013 (UTC)
  - Comment Maybe, when qualifiers will be available, we could use them to add more subtitles adding a "qualifier" like "language edition". --Viscontino (talk) 10:09, 18 April 2013 (UTC)
- Support --Napoleon.tan (talk) 12:48, 30 April 2013 (UTC)
Already done as Property:P392. — ΛΧΣ²¹ 06:13, 9 May 2013 (UTC)

Era

Not done

Description	the era in which the writer, the poet or the author of a literature book has lived
Data type	Item
Example	Period indicated in w:en:Template:Infobox writer/doc
Proposed by	دوستدار ایران بزرگ (talk)

Discussion

As it is indicated in the infobox writer, the era will be calculated according to time from first publication to last. For a sample refer to English wikipedia article w:en:Ferdowsi -- دوستدار ایران بزرگ (talk) 19:30, 12 March 2013 (UTC)

Oppose You probably mean "period", but this should be clear by the list of publications. Description: "Dates from first publication to last publication." (w:en:Ferdowsi use this field in a special way.) --Kolja21 (talk) 15:29, 17 March 2013 (UTC)
Comment Ferdowsi's 40 year life had coincided with a change in governing regime i.e. the substitution of two dynasties of Samanids and Ghaznavids in Iran but for most of poets, writers, etc. it's not difficult to conceive the period in which he or she has lived. There won't be even any necessity for searching the date of his or her publications. دوستدار ایران بزرگ (talk) 11:22, 18 March 2013 (UTC)
Oppose This is a property of the author, not a property of the work. Filceolaire (talk) 16:09, 15 May 2013 (UTC)

translated into

Not done

Description	Languages the work has been translated into
Data type	Item
Domain	creative work
Allowed values	any language
Example	<Lolita> translated into <Russian language>
Source	External reference, Wikipedia article
Proposed by	Legoktm

Discussion

Inspired by a discussion in #wikimedia-office :) Legoktm (talk) 17:50, 25 April 2013 (UTC)

Oppose Sorry, but this property would be the same as P:P407 (language). P407 is btw itself more or less a duplicate (the other way around) of P:P364 (original language). Qualifiers could be used here if necessary I think. --#Reaper (talk) 20:52, 25 April 2013 (UTC)

Oppose If each edition (including translations) gets a statement on the wikidata page for the book then P:P407 (language) will work as as a qualifier. We don't need this. The seem applies if each edition and translation is a seperate item.Filceolaire (talk) 17:14, 15 May 2013 (UTC)

Number of singles/albums/live CDs/EPs/DVDs

Not done

Description	All property used in en:Template:Infobox artist discography should be transformed in properties
Data type	Number (not available yet)
Template parameter	en:Template:Infobox artist discography
Domain	Discography items
Example 1	MISSING
Example 2	MISSING
Example 3	MISSING
Source	Discography pages
Robot and gadget jobs	Yes
Proposed by	★ → A ir on 90 00:14, 4 April 2013 (UTC)

Discussion

Oppose, can be easily queried. --Nightwish62 (talk) 09:38, 6 April 2013 (UTC)

I don't understand what "can be easily queried" means. Could you explain that? --★ → A ir on 9018:46, 6 April 2013 (UTC)

Basically, it means we will be able to automatically get the number of items that are e.g. instances of live album (Q209939) and have a particular performer (P175). So, there is no need to hand-calculate it and add it ourselves. That would only be redundant and get out of date. I presume at some point such queries will be available for infoboxes, but I don't know the details. Superm401 - Talk 21:55, 6 April 2013 (UTC)

Strong oppose per Nightwish62 and Superm401. --Ricordi samoa 22:22, 6 April 2013 (UTC)

Isn't possible to make it by hand now and then by bot or by database queries? --★ → A ir on 9010:59, 7 April 2013 (UTC)

I don't think that's really in the spirit of Wikidata. We don't to put in a lot of info we know we'll have to take out when queries arrive. For now, the Wikipedias can keep doing what they're doing. Superm401 -Talk 19:31, 7 April 2013 (UTC)

Planned road length / Straßenlänge in der Planung / longueur de la route planifié

Not done

Description	length of the planned part of the road / Länge des geplanten Teils der Straße
Data type	Number (not available yet)
Template parameter	w:de:Vorlage:Infobox hochrangige Straße (Planlänge)
Example 1	MISSING
Example 2	MISSING
Example 3	MISSING
Proposed by	unit in kilometer per default --Daniel749 talk 09:21, 23 February 2013 (UTC)

- Can this be accurately sourced? --Rs chen 7754 07:13, 25 February 2013 (UTC)
- : Oppose Projects change often. Snipre (talk) 18:29, 18 April 2013 (UTC)

Oppose as this is not manageable for most situations. In those cases where it is feasible to have this data, it can be done under 'length' (see above proposals) with a qualifier 'status' or some such. Joshbaumgartner (talk)

Recorded (at)

Done: recorded at studio or venue (P483) (Talk and documentation)

Description	the studio where a song/album was recorded
Data type	Item
Template parameter	en:template:Infobox single / en:template:Infobox song / en:template:Infobox albumrecorded
Domain	items about recordings (mostly songs and albums)
Allowed values	the name of the studio, regardless if the studio has, or not, a WP article (most studios are not notable)
Example	On the Floor <recorded at> Cove Studios
Source	The list of studios can be found on the recording's booklet, or the artist's website. This information usually appears on the infobox of WP articles about the recording
Proposed by	— ΛΧΣ²¹

This is needed. — ΛΧΣ²¹ 21:01, 18 April 2013 (UTC)

Support --Nightwish62 (talk) 10:19, 19 April 2013 (UTC)

Support, but it would be nice if we could set "item" DataType in case there's a WP article (not only for this case). --Viscontino (talk) 11:25, 19 April 2013 (UTC)

Comment agree. Item is better. --Nightwish62 (talk) 16:01, 19 April 2013 (UTC)

I'd like to create items to all studios and change the type to item. Let me see if this can be done :) — ΛΧΣ²¹ 17:59, 19 April 2013 (UTC)

Done with datatype "Item' at Property:P483. — ΛΧΣ²¹ 16:46, 3 May 2013 (UTC)

input device / Eingabegerät

Done: input device (P479) (Talk and documentation)

Description	input method/device for video games (not software I would say), maybe video game consoles (and maybe also possible for other devices)
Data type	Item
Template parameter	de:Vorlage:Infobox Computer- und Videospiel Bedienung
Domain	video games, video game consoles
Allowed values	items which are subclass of input device
Example	<Counter-Strike 1.6> input method <mouse>, <keyboard>
Source	Infobox
Robot and gadget jobs	could and maybe should be done by bots
Proposed by	#Reaper (talk)

Discussion

Everything should be clear I think. #Reaper (talk) 14:24, 21 April 2013 (UTC)

Support Mostly because many games have additional specific input devices, like the Dance Dance Revolution or Kinect games.— ΛΧΣ²¹ 16:41, 22 April 2013 (UTC)
Support --Toru10 (talk) 13:05, 30 April 2013 (UTC)
Done as Property:P479. — ΛΧΣ²¹ 06:59, 2 May 2013 (UTC)

Show's creator / Idee / ...

Not done

Description	The show's creator or creators.
Data type	Item
Template parameter	en:Template:Infobox television
Domain	Person
Example	Buffy the Vampire Slayer: Joss Whedon

Support I don't know exactly how to call the English label (TV = Show's creator; film = ?), but there should be a distinction between an artist like Leonardo da Vinci and the creator of a show's. (Right now both have the same property.) --Kolja21 (talk) 07:46, 16 March 2013 (UTC)

Comment Please also have a look at en:Princess Zelda, "created by Shigeru Miyamoto". Should cases like this be included or is designer (Property:P287) suitable? --Kolja21 (talk) 07:52, 16 March 2013 (UTC)

Oppose There already is Property:P170, creator. Creator is a tv-thing, or do you mean the author of Property:P144, or something like that?--CENNOXX (talk) 00:34, 26 March 2013 (UTC)

Support "An original idea by" is a common phrase in many works, not just television programs. I prefer the "idea by". --NaBUru38 (talk) 19:45, 27 March 2013 (UTC)

But it's not a showrunner, isn't it?--CENNOXX (talk) 13:27, 28 March 2013 (UTC)

Exactly, that's a different role. --NaBUru38 (talk) 18:51, 18 April 2013 (UTC)

Oppose Duplication. Already exists as Property:P170, which expressly includes creators of creative works. Shawn in Montreal (talk) 18:47, 5 April 2013 (UTC)

Oppose, clearly a duplicate of "creator (P170)"; this proposal should be archived soon. --Ricordi samoa 00:17, 11 May 2013 (UTC)

ID in database / Primärschlüssel in Datenbank

Not done

Description	For referencing of items that have entries in databases.
Data type	String
Template parameter	None
Domain	Terms
Allowed values	No restrictions
Example	Currently Lupus has the MeSH ID instead of the MeSH code. So MeSH ID = D008180. I propose to move this meaning ID into the source and rename MeSH ID to MeSH code which would be C17.300.480 and C20.111.590 for Lupus and ID = D008180.
Format and edit filter validation	If it is used for a lot of different databases we can't apply any filters.
Source	Databases
Robot and gadget jobs	Data collection from databases would be possible
Proposed by	Tobias1984 (talk)

Discussion

Strong oppose since we have already many properties for the ids in different databases this is not necessary. As you say we can't use filters here which makes it much more difficult and complicated to find wrong values. Also it will be more difficult to add ids for users because they have to set the database in the qualifier section (you should not use sources for that). --Pyfisch (talk) 15:21, 12 May 2013 (UTC)

Thanks for the review Pyfisch. I am still a little confused on how to best handle this kind of things. Could you maybe review this proposal Wikidata:Property_proposal/Term#MeSH_Code. I would like to know your opinion on 1) the creation of a second property 2) if one of the two properties should be a qualifier for the other one. --Tobias1984 (talk) 15:33, 12 May 2013 (UTC)

member of musical group

Not done

Description	Musical group they are a member of
Data type	Item
Template parameter	enwiki Infobox musical artist#associated_actsthough this proposal is a little more precise than the infobox
Domain	Person
Allowed values	Instances of musical group or musical group's subclasses.
Example	Paul McCartney => The Beatles
Source	en:Template:Infobox_musical_artist#associated_acts

Discussion

We have member of political party and member of sports team, but not this as far as I can tell. This should also be bidirectional if/when that is supported. Superm401 - Talk 06:05, 4 April 2013 (UTC)

WITHDRAWN. Superm401 - Talk 03:38, 27 May 2013 (UTC)

Support Indeed. We have so many artists that are members of musical groups, and this will be useful. — ΛΧΣ²¹ 06:08, 4 April 2013 (UTC)
Support, rename to "member of artistic group" to include other forms of art. --NaBUru38 (talk) 16:53, 11 April 2013 (UTC)

That seems like a good idea. Then we could use it for ballet, theatre troupes, etc. Superm401 -Talk 06:29, 12 April 2013 (UTC)

Oppose, redundant with part of (P361). Emw (talk) 13:49, 13 April 2013 (UTC)
Oppose per Emw. Also, if there were a "member of" property, then it should be used instead of creating "member of X" for every X, which is redundant and pointless. Silver hr (talk) 00:46, 19 April 2013 (UTC)
Comment I don't see a redundancy with Property:P361 (from it's discussion page I gather the proposed use in cases where no more specific property for a part-whole-relationship is applicable). However "Member of a (musical) group" should be considered a special case of the "affiliation" relation between persons and organizations and as such is qualified by a period of time and roles. The domain of useful roles is influenced by the kind of organization. Affiliation itself would allow statements like "Sam Cutler was Tour manager for The Grateful Death in 197[?])" (or think of other roles like "legal representative", agent, ...) and there probably would still be the need to determine a narrower set of roles expressing bandmembership proper (what about "supporting musicians" anyway: "Tim Bonhomme is (employed as) keyboarder for the Beach Boys since 1993" vs. "David Marks ws guitarrist and vocalist of the Beach Boys from 1962-1963 and in 1997"). So maybe it would be best to keep the musical roles and the membership roles ("bandleader", "lead guitarist", does one really need them) completely separated, but all of them as datatypes strongle need a qualifier for the interval(s) of time this connection was valid. -- Gymel (talk) 07:24, 19 April 2013 (UTC)

The problem with this property and properties like it is that it's essentially creating a domain-specific property where a generic one suffices. It sets a precedent for an explosion of "member of X", "type of X", etc. properties. The expressivity of the statements given above is fully achievable by using generic properties like 'part of' instead of domain-specific versions of those generic properties. Emw (talk) 20:40, 20 April 2013 (UTC)

However this generic one shouldn't be Property:P361 for membership and roles (more general: relations between persons and organizations). My left thumb by transitivity is part of the matter in the universe but David Marks' thumb IMHO shouldn't be considered a member of the Beach Boys. -- Gymel (talk) 22:49, 23 April 2013 (UTC)

The relation seems even broader than just a "part of" relation between persons and organizations. For example, Germany is a member of the EU, but Berlin is not a member of the EU. I think what your use case is searching for is a way to get thehighest-level parts of some item. I think this use case would be better to support with one simple query technique involving part of, rather than a proliferation of "member of" properties that users would need to look up individually. Emw (talk) 04:31, 24 April 2013 (UTC)

Comment Now that we have member of, this property would be really redundant. Silver hr(talk) 18:38, 26 April 2013 (UTC)
Oppose per Silver hr. --Viscontino (talk) 21:00, 7 May 2013 (UTC)
Oppose redundant to member of. Joshbaumgartner (talk) 08:41, 9 May 2013 (UTC)

coolant

Done: coolant (P588) (Talk and documentation)

Description	substance used by the subject to dissipate excess thermal energy
Data type	Item
Domain	engines, electronics, other items which require a cooling substance
Example	Hispano-Suiza 8 coolant water
Proposed by	Joshbaumgartner (talk) 08:00, 19 May 2013 (UTC)

Basic piece of information for several engines, electronics, weapons, and other items which produce heat as a by-product.Joshbaumgartner (talk) 08:00, 19 May 2013 (UTC)

Support - Can also be used for en:Liquid_metal_cooled_reactor, en:Molten_salt_reactor,en:Thermoelectric_cooling. For MRI it would be, I think liquid helium. --Tobias1984 (talk) 08:26, 19 May 2013 (UTC)
Support --Viscontino (talk) 08:57, 26 May 2013 (UTC)

Point group

Done: point group (P589) (Talk and documentation)

Description	There are 32 point groups that subdivide the crystal systems. They are derived from crystallographic symmetry operations. Every macroscopic crystal and mineral belongs to one of these point groups. The point group is equivalent to "crystal class".
Data type	Item
Template parameter	de:Vorlage:Infobox_Mineral = Kristallklasse=
Domain	term
Allowed values	32 point groups (have to be created)
Example	sodium chloride => cubic-hexoctahedral, albite =triclinic-pinacoidal
Format and edit filter validation	32 point groups
Source	Scientific literature
Robot and gadget jobs	Add point group to every crystal from scientific databases
Proposed by	--Tobias1984 (talk) 08:07, 20 May 2013 (UTC)

Comment - The table of all the point groups can be seen here:link --Tobias1984 (talk) 08:07, 20 May 2013 (UTC)
Comment - Property proposed by the Wikidata:Chemistry task force and the Wikidata:Mineralogy task force.
Comment - I created Q13359926, Q13359928, Q13359929, Q13359930 and Q13359931 so one can look at an example. --Tobias1984 (talk) 10:53, 20 May 2013 (UTC)
Support --Sbisolo (talk) 14:44, 23 May 2013 (UTC)
Comment - We need more than 32 point groups: we need 'crystal system xy, undefined point group' as well. --Chris.urs-o (talk) 09:25, 24 May 2013 (UTC)
Nõ, if it is unknown, we let empty. Snipre (talk) 19:08, 27 May 2013 (UTC)
Support Snipre (talk) 19:08, 27 May 2013 (UTC)

Maximum speed / Höchstgeschwindigkeit / Vitesse maximale

Not done

Description	Maximum authorised speed (VNe)
Data type	Number - default m/s.-invalid datatype (not in Module:i18n/datatype)
Example 1	MISSING
Example 2	MISSING
Example 3	MISSING

Comment: Default unit should be changed to km/h since this property will most often be used for powered aircraft which do not us m/s as a normal unit for speed. Joshbaumgartner (talk) 02:41, 30 April 2013 (UTC)

Oppose - speed is too generic. Things like "maximum" should be solved with qualifiers. --Tobias1984(talk) 14:01, 16 May 2013 (UTC)

Generic: Speed. --Tobias1984 (talk) 14:14, 22 May 2013 (UTC)

Stall speed / Mindestgeschwindigkeit / Vitesse de décrochage

Not done

Description	The speed (VS) at which the plane will stall with normal load.
Data type	Number - default m/s.-invalid datatype (not in Module:i18n/datatype)
Example 1	MISSING
Example 2	MISSING
Example 3	MISSING

Oppose - speed is too generic. Things like "stall speed" should be solved with qualifiers. --Tobias1984(talk) 14:01, 16 May 2013 (UTC)

Generic: Speed. --Tobias1984 (talk) 14:16, 22 May 2013 (UTC)

GNIS

Done: GNIS Feature ID (P590) (Talk and documentation)

Description	Official identification Code for geographic objects in the US, see: Geographic Names Information System
Data type	String
Template parameter	en:template:geobox/type/settlement: blank1_info.
Domain	all kinds of geographic objects in the US
Example	Lebanon (Q993523) = "0867976"
Source	http://www.census.gov/geo/maps-data/data/gazetteer2010.html

Support -- Phoebe (talk) 20:00, 25 February 2013 (UTC)
Support but there are some difficulties. 1) Incorporated places do have two different GNIS codes, one for the populated place and another for the incorporated subject, the GNIS does have different codes for e.g. Hibbing, Minnesota and the City of Hibbing, Minnesota. The issue is that neither in the EN nor in the DE Wikipedia (refer to de:Vorlage:Infobox Ort in den Vereinigten Staaten) one can be sure that in every case the "right" code was used; I even am not aware that this issue has been discussed before in the EN:WP. 2) GNIS also exists for the US Minor Outlying Areas and Puerto Rico. 3) There exist also GNIS codes in another databas for antarctic objects. At the moment I do not know wether only for those objects which have been named by the BGN or for any antarctic feature. --Matthiasb (talk) 13:24, 7 March 2013 (UTC)
Comment Datatype should be String. Source should be http://geonames.usgs.gov/domestic/index.html SupportMrwojo (talk) 16:40, 26 March 2013 (UTC)
Support --aconcagua (talk) 07:46, 26 April 2013 (UTC)
Support But as Matthiasb said above, there's also a separate GNIS database for antarctic features with its own IDs. We probably need a separate property for those. --Kam Solusar (talk)

EC Number

Done: EC enzyme number (P591) (Talk and documentation)

Description	Enzyme Commission number (EC number) is a numerical classification scheme for enzymes, based on the chemical reactions they catalyze. As a system of enzyme nomenclature, every EC number is associated with a recommended name for the respective enzyme. (See: en:Enzyme Commission number
Data type	String
Template parameter	en:Template:GNF_Protein_box = ECnumber
Domain	item
Example	gastric lipase = "3.1.1.3", alcohol dehydrogenase = "1.1.1.1",creatine kinase = "2.7.3.2"
Format and edit filter validation	constrain formatting of EC codes d.d.d.d
Source	http://www.chem.qmul.ac.uk/iubmb/enzyme/
Robot and gadget jobs	collect data from infoboxes and online databases
Proposed by	--Tobias1984 (talk) 08:57, 27 May 2013 (UTC)

Discussion

Support Emw (talk) 18:24, 2 June 2013 (UTC)

ChEMBL

Done: ChEMBL ID (P592) (Talk and documentation)

Description	chemical database of bioactive molecules with drug-like properties (See: en:ChEMBL
Data type	String
Template parameter	en:Template:GNF_Protein_box = ChEMBL
Domain	item
Example	aspirin = "CHEMBL25", caffeine = "CHEMBL113", lactose = "CHEMBL417016"
Format and edit filter validation	constrain formatting
Robot and gadget jobs	collect data from infoboxes and online databases
Proposed by	--Tobias1984 (talk) 09:09, 27 May 2013 (UTC)

Discussion

Support Emw (talk) 18:25, 2 June 2013 (UTC)

IUPHAR ID

Done: Guide to Pharmacology Ligand ID (P595) (Talk and documentation)

Description	ID in the IUPHAR database
Data type	String
Template parameter	en:Template:GNF_Protein_box = IUPHAR
Domain	item
Example	cocaine = "2286", morphine = "1627", serotonin = "5"
Format and edit filter validation	constrain formatting
Source	http://www.iuphar-db.org
Robot and gadget jobs	collect data from infoboxes and online databases
Proposed by	--Tobias1984 (talk) 10:19, 27 May 2013 (UTC)

Discussion

Support Emw (talk) 18:27, 2 June 2013 (UTC)

Homologene ID

Done: HomoloGene ID (P593) (Talk and documentation)

Description	ID in the Homologene database
Data type	String
Template parameter	en:Template:GNF_Protein_box = Homologene
Domain	item
Example	rhodopsin = "68068", leptin = "193", prolactin = "732"
Format and edit filter validation	constrain formatting
Source	http://www.ncbi.nlm.nih.gov/homologene
Robot and gadget jobs	collect data from infoboxes and online databases
Proposed by	--Tobias1984 (talk) 10:24, 27 May 2013 (UTC)

Discussion

Support Emw (talk) 18:33, 2 June 2013 (UTC)

Ensembl ID

Done: Ensembl gene ID (P594) (Talk and documentation)

Description	ID in the Ensembl database (See: en:Ensembl)
Data type	String
Template parameter	en:Template:GNF_Protein_box = Hs_Ensembl (humans) Mm_Ensembl (mouse)
Domain	item
Allowed values	string plus item-qualifier that denotes the species
Example	myoglobin = "ENSG00000198125" & species = "human" + "ENSMUSG00000018893" & species = "mouse" fibronectin = "ENSG00000115414" & species = "human" + "ENSMUSG00000026193" & species = "mouse"
Format and edit filter validation	constrain formatting
Source	http://www.ensembl.org/index.html
Robot and gadget jobs	collect data from infoboxes and online databases
Proposed by	--Tobias1984 (talk) 10:35, 27 May 2013 (UTC)

Discussion

Support Emw (talk) 18:34, 2 June 2013 (UTC)

cardinal direction / Himmelsrichtung / point cardinal / сторона света

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

Description	qualifier: for which cardinal direction the statement applies.
Data type	Item
Domain	useful for shares border with (P47), maybe more.
Allowed values	0-360 (Azimuth values)
Example	United States of America <shares border with> Canada with qualifiers 0, 90
Proposed by	Šlomo (talk)

Can be usefull for creating navbox for articles about geographical areas. Šlomo (talk) 19:40, 25 April 2013 (UTC)

Seems useful, but unsure about the values. Why not allow further subdivisions (NNE, ENE, ESE etc.) for cases where further precision may be needed. Or even just use degrees to measure the direction? --Byrial (talk) 21:56, 25 April 2013 (UTC)
Well, I chose the 8 directions that have their items to make the extraction of data in various languages easier. Also, having in mind Property:P47, the neighbouring countries, states, regions, counties a.s.o. won't usually be in an exact direction from each other. But I agree that a numeric value can be comparably useful and it has potencial of another use in situations where more precise values would be possible and needed.--Šlomo (talk) 01:08, 26 April 2013 (UTC)
Support. Conny (talk) 14:01, 28 April 2013 (UTC).
Comment It seems there's consensus that this property should not be restricted to the cardinal directions -- i.e. north, east, south and west. So I think this property should renamed to something like "direction". Also, the documentation should clarify whether the values for this qualifier are based on true north or magnetic north, and which coordinate reference system is used. Emw (talk) 16:49, 28 April 2013 (UTC)
Comment Having looked at the example (in the future, please give the actual labels so it's possible to read without going to each individual page), it's unclear to me why this property would use degrees 0-360 as values. Stating that "United States of America shares <0, 90 degrees> border with Canada" seems odd compared to "United States of America shares <north> border with Canada". So I think the original choice to use cardinal directions (and maybe intercardinal directions like NE, NNE) would be better than allowing degrees 0-360. Emw (talk) 17:03, 28 April 2013 (UTC)
Translating <0, 90 degrees> to <north and east> can be easily done by the software. I found the idea of azimuth values more useful, because it doesn't limit as for the future to use it more precise. If we use Item datatype, we are at this moment limited to cardinal and intercardinal directions - at least I didn't find items for NNE, NbE etc.--Šlomo (talk) 10:54, 1 May 2013 (UTC)

Ah, OK, thanks for the clarification. I think that should be made clear in the proposal. It should also be made clear that this qualifier handles exclaves of its subject. For example the United States shares a significant border on the east with Canada only in Alaska, which is not contiguous with the rest of the United States. Would this qualifier handleenclaves like Lesotho, which is an enclave of South Africa? If so, how? The list of enclaves and exclaves provide more edge cases that might be worth considering. Emw (talk) 00:12, 2 May 2013 (UTC)
Support the 8 item idea. Everything else with more detail has to be done with geopolygons in my opinion. --Tobias1984 (talk) 21:04, 20 May 2013 (UTC)

Support But with cardinial directions, per Emw and Tobias1984. I would allow 16 items (north, north-east, north-north-east), but that's enough. The full 360 degrees really aren't needed here. On the contrary, it would only pretend to have a precision that the claim in most cases can't have; e.g. is the US-Canadian Border at 89, 90 or 91 degrees from the US?--Kompakt (talk) 09:32, 23 May 2013 (UTC)

16 would be OK too. If anybody want to know the azimuth angle between New York and Rome then that anyway can be calculated from the GPS coordinates of both cities. Everything more complex than a GPS-point will have to wait until geo-lines and geo-polygons can be implemented. --Tobias1984 (talk) 09:46, 23 May 2013 (UTC)

Is everybody Ok with me creating this property with "item"-datatype and 16 possible inputs? The reference system would be geographic and not magnetic. --Tobias1984 (talk) 16:52, 2 June 2013 (UTC)

I'm OK with the property being created, but I think its label should be changed. Cardinal direction refers to only north, south, east and west. If this properties allows more values than those, its label should not indicate it only allows those four values. Emw (talk) 21:26, 2 June 2013 (UTC)

Taxon publication year (withdrawn)

Description: The year of the publication.
Datatype: Date (Precision: Year)
Allowed values: 1753 - present year
Infobox parameter example: "1755" for Prunus avium
Proposed by: Soulkeeper (talk) 11:44, 30 May 2013 (UTC)
Comments:

There is already a property covering that kind of data: publication date (P577). Just see if this can't be used. Snipre(talk) 12:34, 30 May 2013 (UTC)

I'm not sure. It seems too generic. The property description is "date when this work was published" (or "Date of the publication of the book"), but strictly speaking the taxon description (a work) is not the same as the taxon (which is what the item is about). But maybe it's close enough, I don't know. - Soulkeeper (talk) 14:14, 30 May 2013 (UTC)

I just found year of publication of scientific name for taxon (P574), so I'm retracting this proposal. - Soulkeeper (talk) 14:19, 30 May 2013 (UTC)

WTA id / WTA-Kennung / identifiant WTA

Done: WTA player ID (P597) (Talk and documentation)

Description	identifier to access the player's page on the WTA website
Data type	String
Domain	women tennis players
Example	Serena Williams (Q11459) => "9044"
Source	en:Template:WTA
Robot and gadget jobs	yes
Proposed by	Kompakt (talk)

Discussion

The reason to create it is the same as for ATP player ID (P536) (see old discussion here). The id is appended to the urlhttp://www.wtatennis.com/players/player/. It will make it possible for bots to update data automatically from the WTA website.--Kompakt (talk) 09:44, 30 May 2013 (UTC)

Support --Stryn (talk) 10:18, 30 May 2013 (UTC)

Support and identifiant can be transfered to Wikidata by my bot if you want. — Hawk-Eye (talk) 13:49, 30 May 2013 (UTC)

This would be really great!--Kompakt (talk) 07:15, 31 May 2013 (UTC)

Support Edoderoo (talk) 07:34, 31 May 2013 (UTC)

Support --Tobias1984 (talk) 19:48, 1 June 2013 (UTC)

commands / / commandement

Done: commander of (DEPRECATED) (P598) (Talk and documentation)

Description	for persons who are notable as commanding officers, the units they commanded
Data type	Item
Template parameter	"commands" in en:Template:Infobox military person
Domain	person
Example	First Army (France) (Q161715), French Far East Expeditionary Corps (Q2997796)
Proposed by	Ayack (talk)

Discussion

ITF id / ITF-Kennung / identifiant ITF

Done: ITF player ID before 2020 (archived) (P599) (Talk and documentation)

Description	identifier to access the player's page on the ITF website
Data type	String
Domain	tennis players
Example	Serena Williams (Q11459) => "20007765"; Novak Djokovic (Q5812) => "100004087"
Source	en:Template:ITF female profile, en:Template:ITF male profile
Robot and gadget jobs	yes
Proposed by	Kompakt (talk)

Discussion

Another id for tennis players, from the ITF, again to facilitate bot updates. The id is appended to the url http://www.itftennis.com/procircuit/players/player/profile.aspx?playerid= .--Kompakt(talk) 09:44, 30 May 2013 (UTC)

Support --Stryn (talk) 10:18, 30 May 2013 (UTC)

Support and identifiant can be transfered to Wikidata by my bot if you want. — Hawk-Eye (talk) 13:49, 30 May 2013 (UTC)

This would be really great!--Kompakt (talk) 07:15, 31 May 2013 (UTC)

Support - analog to the ATP_id parameter we recently introduced. This IFT parameter leads to more player statistics, and is pretty essential. Edoderoo (talk) 07:32, 31 May 2013 (UTC)

Support --Tobias1984 (talk) 19:50, 1 June 2013 (UTC)

MedlinePlus

Done: MedlinePlus ID (P604) (Talk and documentation)

Description	w:MedlinePlus
Data type	String
Template parameter	en:Template:Infobox disease field MedlinePlus
Domain	term: diseases
Example	w:Chagas disease, heart attack = "155919"
Source	http://reference.medscape.com/
Proposed by	Kizar --Kizar (talk) 00:46, 18 May 2013 (UTC)

Comment - Why does en:Heart attack give 3 values in the field eMedicine that redirect to 2 different pages? What is the meaning of that formatting, e.g. "emerg/327"? --Tobias1984 (talk) 07:38, 18 May 2013 (UTC)

Until maybe one or two years ago, all articles were categorized by specialty and urls were formatted in that way. The old urls will still redirect to the new articles, however some have been merged on emedicine and some articles now have several links to the same emedicine page. Maybe they can be updated with the help of a bot one day.--Wouterstomp (talk) 19:20, 26 May 2013 (UTC)

I am not sure I understand what your meaning, but we can create items that have no Wikipedia page. --Tobias1984(talk) 20:06, 26 May 2013 (UTC)

It may be a good idea to look at switching to pubmed health from medline plus. There are slightly better IMO even though both are similar.Doc James (talk · contribs ·email) (if I write on your page reply on mine) 21:20, 1 June 2013 (UTC)

I think we could do both. Do you want to open a request for pubmed? --Tobias1984 (talk) 22:24, 1 June 2013 (UTC)

Support --Wouterstomp (talk) 10:04, 6 June 2013 (UTC)

battles/wars / / conflits

Done: conflict (P607) (Talk and documentation)

Description	notable battles or wars in which the person participated
Data type	Item
Template parameter	"battles" in en:Template:Infobox military person
Domain	person
Example	World War I (Q361), World War II (Q362), First Indochina War (Q748780)
Proposed by	Ayack (talk)

Discussion

Exhibition history

Done: exhibition history (P608) (Talk and documentation)

Description	exhibition history
Data type	Item
Template parameter	commons:Template:Artwork
Domain	museum objects
Example	The Virgin and Child with Saint Anne (Q563727) -> La Sainte Anne, l'ultime chef-d'œuvre de Léonard de Vinci
Source	provided in several good museum databases. --Zolo (talk) 12:55, 31 May 2013 (UTC)
Robot and gadget jobs	Could be imported from Wikimedia commons ARTWORK template (for some)
Proposed by	Zolo (talk) 12:55, 31 May 2013 (UTC)

Notable enough for Wikidata ? --Zolo

if it is there, it's always notable, because the artwork is notable, so for example the artwork probably influenced another younger artist somewhere who saw it in an exhibition, etc. Though the Mona Lisa was "seen" in print by many artists before travel became easier to do, recording its whereabouts is definitely notable for other reasons (security issues, influences on modern artists or public opinion, art history publications, etc.) --Jane023 (copied from Wikidata:Artworks task force/Properties)

Comment could possibly use a more general property but I cannot think of any (it is distinct from location)--Zolo (talk) 12:55, 31 May 2013 (UTC)

NUTS (without version) / NUTS (with version)

Status: Done

→ Property:P605

without version

Description: Country subdivision code of the European Union
Datatype: ~~value~~ Monolingual string
Domain: Places (Countries. Administrative and non-administrative subdivisions of countries)
Source:
Infobox parameter: en:Infobox German state (nuts) and many other templates
Example value: SE071
Comments: see w:en:Nomenclature of Territorial Units for Statistics

Code for different levels of territorial units. --Monsieurbecker (talk) 14:50, 12 March 2013 (UTC)

Support This would be useful. - Ssolbergj (talk) 00:10, 13 March 2013 (UTC)
Support Documentation above okay. (I changed datatype.) Mange01 (talk) 19:30, 13 March 2013 (UTC)
Question We probably should distinguish different versions of NUTS: NUTS 1995, NUTS 1999, NUTS 2003, NUTS 2006 and the current NUTS 2010 in order to facilitate the later automatic integration of statistic data. What do you think? --Monsieurbecker (talk) 07:14, 22 March 2013 (UTC)
Oppose We should name every property as accurate as possible to prevent confusion. If there are really diffrent NUTS versions, we should a.) create multiple properties for every version b.) name it with the version. --Nightwish62 (talk) 21:26, 23 March 2013 (UTC)
Support, but please let us wait one or two weeks till qualifiers are available. Ok? What we also need is a new generic property 'version' (Data value: String). At moment there is only a property 'stable version' for software. However, I even think this property should be deleted/renamed to 'version' and use qualifiers for 'stable/unstable' status also. --Nightwish62 (talk) 15:19, 30 March 2013 (UTC)
- Question What about the three properties for the ISO 3166-1 country code (Property:P297, Property:P298, Property:P299)? Will they be merged to one property as soon as qualifiers are available? --Monsieurbecker (talk) 06:40, 31 March 2013 (UTC)
  - In my opinion they should, yeah. It's the same situation. --Nightwish62 (talk) 08:43, 31 March 2013 (UTC)
Support once qualifiers are available. James F. (talk) 11:15, 13 April 2013 (UTC)

with version (example 'NUTS 2010')

Support, perhaps as a temporary solution until qualifiers can be used to differentiate sources, dates and versions of Nuts data from each other.Mange01 (talk) 13:44, 30 March 2013 (UTC)

Comment, qualifier will released within the next two weeks already. --Nightwish62 (talk) 15:13, 30 March 2013 (UTC)

Done: Property:P519 Without version, we'll use qualifieres for that. -- MichaelSchoenitzer (talk) 21:35, 14 May 2013 (UTC)

Sorry, wrong datatype. Will be corrected soon. -- MichaelSchoenitzer (talk) 21:41, 14 May 2013 (UTC)

Done now at Property:P605. --Stryn (talk) 21:01, 6 June 2013 (UTC)

Airplanes

Status: Done

→ Property:P606

Aircraft / Flugzeug / Avion

See: en:Template:Infobox aircraft

Comment The proposal discussion below was restored from this change of Wikidata:Property_proposal/Term.

Glider (sailplane) / Segelflugzeug / Planeur

All gliders could meaningful be caracterized by (most of) the propertis listed below. It would be nice, if after stating, that a LS4 (Q544661) 'is a' Glider (sailplane) (Q180173) the property-list below pops up for filling in.

Construction and production

Title	ID	Data type	Description	Example	Inverse
role	?	Item	the role(s) the sailplane fills, eg. trainer, acrobatic, touring motor glider, motorglider	<Glaser-Dirks DG-400> role <Motorglider>	–
class	?	Item	the classes the glider type usually competes in, eg. club class, standard class, 15 m class, 18 m class, open class	<Glaser-Dirks DG-400> class <Club class>	–
national origin	?	Item	the country, where the type was constructed or first made	<Glaser-Dirks DG-400> national origin <Germany>	–
manufacturer	176	Item	organisation(s) procucing the type	<Glaser-Dirks DG-400> manufacturer <DG Flugzeugbau>	–
designer	287	Item	person(s) in charge of designing the type	<Schleicher ASK 21> designer <Q90204>	–
maiden flight	606	Invalid type: time	time for first (test-) flight, see maiden flight	<Schleicher ASK 21> maiden flight <1979-12>	–
number built	?	Invalid type: integer	number of airframes built	<Schleicher ASK 21> number built <750>	–
production period	?	Invalid type: time	the period in which the plane was produced	<Schleicher ASK 21> production period <1979-->	–
variants	?	Item	the different variants of the type	<Schleicher ASK 21> variants <ASK 21, ASK 21 Mi>	–

Support --Goldzahn (talk) 23:57, 11 March 2013 (UTC)

Comment Maybe "type of aircraft" would be better than "role"? At least touring motor glider and motorglider should be "type of aircraft", but "trainer, acrobatic" is something else. I think, it is more what this aircraft is used for. --Goldzahn (talk) 12:49, 14 March 2013 (UTC)

Support 'role': 'Role' and 'type' can definitely be distinct properties. 'Role' generally indicates a purpose for the aircraft (i.e. what it does) while 'type' is often more a description of its design (i.e. what it is). These obviously can be hazy lines and overlap, but having the property named 'role' seems to give more indication of usage. Joshbaumgartner (talk) 02:41, 30 April 2013 (UTC)

Oppose new 'class' property, since it's redundant with Property:P31 and Property:P279. Emw (talk) 23:28, 17 March 2013 (UTC)
- Why an opposition ? Here we have different targets for class. Instead of using the same property which will mix different types of association better use an accurate name for the property like plane class Snipre (talk) 20:26, 22 March 2013 (UTC)

In my view this class is a class in an competition. Similar to "Flyweight" in boxing. --Goldzahn (talk) 10:32, 23 March 2013 (UTC)

Comment Perhaps change 'class' to 'competition class' to better indicate such intent? Joshbaumgartner (talk) 01:10, 30 April 2013 (UTC)

Oppose 'national origin' and 'produced period' as proposed. 'National origin' should be changed to 'country of origin', as aircraft are categorized by country, not nation () and 'produced period' should be changed to 'production period' for better English readability. Joshbaumgartner (talk) 02:41, 30 April 2013 (UTC)

Support 'role', 'first flight', 'number built', and 'variants' as proposed. Joshbaumgartner (talk) 02:41, 30 April 2013 (UTC)

Support 'maiden flight' and 'production period' 87.54.11.4 12:10, 31 May 2013 (UTC)

Comment Property:P606 was subsequently created for 'maiden flight'. -- LaddΩ chat ;) 14:24, 16 January 2016 (UTC)

Highest point (en) / 地理最高點 (zh)

Done: highest point (P610) (Talk and documentation)

Description	see example
Data type	Item
Domain	place
Example	Q148 => Q513
Proposed by	GZWDer (talk) 13:23, 29 May 2013 (UTC)

religious order / / ordre religieux

Done: religious order (P611) (Talk and documentation)

Description	The order of monks or nuns which the monastery housed (also true for persons or organizations)
Data type	Item
Template parameter	"order" in en:Template:Infobox monastery
Domain	person, place, organization
Example	Benedictines (Q131132)
Proposed by	Ayack (talk)

mother house / / abbaye mère

Done: mother house (P612) (Talk and documentation)

Description	Name of the mother house
Data type	Item
Template parameter	"mother" in en:Template:Infobox monastery
Domain	place
Example	Solesmes Abbey (Q306131)
Proposed by	Ayack (talk)

Terminus location (en) / Ubicación del término (es)

Done: terminus location (P609) (Talk and documentation)

Description	Location of the terminus
Data type	Item
Template parameter	terminus_a, terminus_b of en:Template:Infobox road
Domain	Any item that uses terminus
Example	<Oklahoma State Highway 325> terminus location <Boise City> direction <east>
Source	Infoboxes on enwp and other projects, maps, station directories, etc.
Proposed by	—Scott5114 ↗ [EXACT CHANGE ONLY] 09:28, 30 May 2013 (UTC)

Discussion

This property would be used with the terminus property (which notes the feature at which the item terminates at, like a railway station or intersecting road) to indicate the location of the termini. Initially, this was thought to be able to be handled by a qualifier to the terminus property. Unfortunately, road termini often have several different roads at the terminus intersection; see Oklahoma State Highway 325 as an example, which ends at a traffic circle that five other highways pass through. As a result, the qualifier is in the administrative unit <Boise City> has to be duplicated five times. This property would eliminate the duplication, resulting in a cleaner, more maintainable database. —Scott5114 ↗ [EXACT CHANGE ONLY] 09:28, 30 May 2013 (UTC)

Support to fix the problem. --Rs chen 7754 09:38, 30 May 2013 (UTC)

Support per Rschen7754. T C N7JM 02:49, 6 June 2013 (UTC)

Done Property:P609 Legoktm (talk) 20:52, 8 June 2013 (UTC)

OS grid reference

Done: OS grid reference (P613) (Talk and documentation)

Description	A grid location reference from the Ordnance Survey National Grid reference system used in Great Britain, explained here Ordnance Survey National Grid.
Data type	String
Template parameter	Is used in some infoboxes, for example: Bodiam Castle.
Domain	places
Allowed values	places in Great Britain
Example	Q639208 => TQ7855025649
Source	Ordnance Survey maps are the original sources
Proposed by	Danrok (talk) 13:05, 22 May 2013 (UTC)

Discussion

Comment - Can this be calculated from the GPS-coordinates? --Tobias1984 (talk) 19:55, 1 June 2013 (UTC)

archipelago / / archipel

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

Description	the name of the group of islands the island belongs to
Data type	Item
Template parameter	"archipelago" in en:Template:Infobox islands
Domain	place
Example	Java (Q3757) --> Greater Sunda Islands (Q165481)
Proposed by	Ayack (talk)

DiseasesDB

Not done

Description	The Diseases Database is a database that underlies a free website that provides information about the relationships between medical conditions, symptoms, and medications. (From en:Diseases_Database
Data type	String
Template parameter	many languages: DiseasesDB
Domain	term
Example	lung cancer = "7616"
Format and edit filter validation	edit filter only numbers and number of digits
Source	http://www.diseasesdatabase.com
Robot and gadget jobs	collect data from infoboxes
Proposed by	--Tobias1984 (talk) 21:10, 31 May 2013 (UTC)

Discussion: Support --Wouterstomp (talk) 10:04, 6 June 2013 (UTC)

Duplicate of DiseasesDB (P557) --Tobias1984 (talk) 19:49, 9 June 2013 (UTC)

Cultural heritage registration code (CHRC) / / /شمارۀ ثبت

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

Description	Code for Ancient buildings and monuments, Ancient traditions, Astonishing human made creations in Iran enumerated by Iran Cultural Heritage, Handcrafts and Tourism Organization
Data type	String
Template parameter	w:fa:الگو:جعبه_اطلاعات_جای‌های_تاریخی_ایران
Domain	Ancient buildings and monuments, Ancient traditions, Astonishing human made creations in Iran
Allowed values	Codes assigned by Iran Cultural Heritage, Handcrafts and Tourism Organization
Example	e.g CHR code dedicated to Cave of Karaftu is 330.
Source	w:fa:الگو:جعبه_اطلاعات_جای‌های_تاریخی_ایران
Proposed by	دوستدار ایران بزرگ (talk)

Code for Iranian Ancient Monuments, castles, caves, bridges, etc. دوستدار ایران بزرگ (talk) 19:10, 16 April 2013 (UTC)

source of energy / Energiequelle / source d'énergie / fuente de energía

Done: source of energy (P618) (Talk and documentation)

Description	describes the source of energy an animated object (machine or animal) uses
Data type	Item
Template parameter	couldn't find an infobox that included this
Domain	GND:term, machines, aircraft, vehicles, ships, animals, ...
Allowed values	type of linked items,allowed values (if limited)
Example	Nuclear submarine = nuclear energy, nuclear reactor = nuclear energy, car = fuel (or diesel, ...), airplane = kerosine, satellite = solar energy, animals = food (or chemical energy?), hybrid car = batteries + fuel, sun = fusion energy, cellphone = Li-battery, power tools = electricity, windmill = wind, ...
Source	relevant literature
Proposed by	Tobias1984 (talk)

Discussion

Interesting queries would be possible with this property. Needs a lot of feedback from different branches of science so it we can get the most out of it. For animals there should probably be a separate food chain property. Tobias1984 (talk) 12:36, 10 May 2013 (UTC)

I think it would be most practical to treat machines and biological organisms separately. Biology is generally much more complex than mechanics. - Soulkeeper (talk) 14:22, 10 May 2013 (UTC)

Support

Question There are several applications for this as a generic energy source data point. Many more specific ones have been proposed, such as 'powerplant' for aircraft or similar ones for ships, etc. Is this intended to cover these, or is it only designed to be the more general basic source, and not the engine for the energy to be made available to the subject? i.e. shouldSupermarine Spitfire source of energy aviation fuel, or should it be more specific and beSupermarine Spitfire source of energy Rolls-Royce Merlin? I think this is good property and support it, but I do think that it will take some refining in practice to get the best out of it. Joshbaumgartner(talk) 06:51, 13 May 2013 (UTC)

I was thinking that this property should only be for the fuel and not for the engine, taking your example. It would allow for such queries as "What are all the things that have wind as a source of energy" and return "Windmills, ...". A query for "aviation fuel" would return "Airplanes". For the individual airplanes we should probably be more specific as the Boeing Dreamliner for example also uses batteries as a source of power. --Tobias1984 (talk) 07:19, 13 May 2013 (UTC)

I am liking this property, and it makes sense to me to think of it as the form of energy that enters a system, vs. how that energy is translated into motive or other force. I am not sure about batteries however, as wouldn't that simply be a way of storing energy that has already entered the system or been created by the system, and be kind of like putting 'fat cells' as a source of energy for 'human'?Joshbaumgartner (talk) 05:33, 16 May 2013 (UTC)

Support I like this is a generic term which would include solar panels for satellites, nuclear reactors for submarines etc. The misnamed "powerplant" is intended for types of engines? Secretlondon (talk) 14:09, 18 May 2013 (UTC)

Power sources / Источники питания

Done: source of energy (P618) (Talk and documentation)

Description	источники питания
Data type	Item
Template parameter	ru:Шаблон:Космический аппарат Источники питания en:Template:Infobox spacecraft power batteries
Domain	Космические аппараты
Allowed values	солнечная батарея, NiCd-аккумулятор и т. д.
Example	Космос-367, источники питания: ядерный реактор
Source	Карточки в статьях и т. д.
Proposed by	— Ivan A. Krestinin (talk) 19:20, 1 April 2013 (UTC)

Oppose - Too qualitative, better handled locally. --WDGraham (talk) 00:06, 28 April 2013 (UTC)

Support - I think queries for satellites powered by RTGs or nuclear reactors would be interesting. --Tobias1984 (talk) 18:39, 30 April 2013 (UTC)

Comment - Having thought about it, this property could be used for submarines (diesel or nuclear power), cars (as in what kind of fuel, hybrids = Li-battery+fuel), airplanes (kerosine, boeing-dreamliner=Li-batteries and fuel), different toys (AA-battery, AAA-battery), cell phones (Li-battery). --Tobias1984 (talk) 07:08, 6 May 2013 (UTC)

Comment - I proposed a more general version of this property atWikidata:Property_proposal/Term#source_of_energy_.2F_Energiequelle_.2F_source_d.27.C3.A9nergie_.2F_fuente_de_energ.C3.ADa. --Tobias1984 (talk) 12:39, 10 May 2013 (UTC)

yard number

Done: yard number (P617) (Talk and documentation)

Description	number of the ship assigned by its builder (shipyard)
Data type	Number (not available yet)

Support Found in infoboxes. Danrok (talk) 00:24, 28 May 2013 (UTC)
Done as string. Might not be strictly numeric. -- Docu at 20:05, 9 June 2013 (UTC)

supporting actor/actress

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

Description	Supporting actor/actress played in film.
Data type	Item
Domain	Persons
Proposed by	EugeneZelenko (talk)

Will be useful to create list of notable people played in film but not fitting in Property:P161. Could be used for creating list of actors/actresses in text of article. --EugeneZelenko (talk) 14:16, 24 March 2013 (UTC)

- Comment Supporting actors range from bit parts to secondary leads, it's not as clear as on Property:P161 which of them should be named, only walk-on-roles, only "Over-Five"s, ...--CENNOXX (talk) 14:47, 27 March 2013 (UTC)
- Support, with the definition by EugeneZelenko: actors not starring the film. --NaBUru38 (talk) 19:53, 27 March 2013 (UTC)
- Support--Romero (talk) 23:53, 12 April 2013 (UTC)
- Support, in look of thinkings EugeneZelenko. Conny (talk) 14:41, 28 April 2013 (UTC).
Done as Property:P482. — ΛΧΣ²¹ 16:34, 3 May 2013 (UTC)

as

Done: character role (P453) (Talk and documentation)

Description	qualifier for Property:P161 to specify role played by actor/actress in film
Data type	Item
Domain	film
Example	Sherlock Holmes and Dr. Watson starring Vasily Livanov as Sherlock Holmes
Proposed by	EugeneZelenko (talk) 13:40, 16 April 2013 (UTC)

Sure, better name for property is possible. --EugeneZelenko (talk) 13:40, 16 April 2013 (UTC)

I suggest "role" as the name of the qualifier. --Wylve (talk) 16:55, 16 April 2013 (UTC)

I could suggest "character"? — ΛΧΣ²¹ 00:55, 19 April 2013 (UTC)

Support such a property, but unsure which name it should have. 'as' could be used outside move/characters also, but I don't know if this is an advantage or disadvantage. --Nightwish62 (talk) 10:22, 19 April 2013 (UTC)

Support, but with another name (character/role). What if there's not a WP article for that character anyways? --Viscontino (talk) 11:29, 19 April 2013 (UTC)

Support -- MichaelSchoenitzer (talk) 21:11, 21 April 2013 (UTC)

Support --Romero (talk) 12:48, 22 April 2013 (UTC)

Done P453, continue discussion about names for different languages there. -- MichaelSchoenitzer (talk) 16:19, 22 April 2013 (UTC)

Filmaffinity

Done: FilmAffinity film ID (P480) (Talk and documentation)

Description	The id of filmaffinity page.
Data type	String
Template parameter	es:Plantilla:Ficha de película filmaffinity
Domain	Films, actors, directors...
Allowed values	In eswiki it's numeric
Example	799532 for the film Q161678. Filmaffinity
Source	infobox
Robot and gadget jobs	My bot can import this property from eswiki.
Proposed by	Kizar (talk)

In eswiki is more common to use this page instead of IMDB. Filmaffinity is in english and spanish. Most articles in eswiki already have the id and only needs to be imported. Kizar (talk) 14:40, 17 April 2013 (UTC)

The datatype can be numeric but as no operations or formats are to be applied can be a string.--Kizar (talk) 20:50, 17 April 2013 (UTC)

Support -- MichaelSchoenitzer (talk) 16:42, 18 April 2013 (UTC)
Support — ΛΧΣ²¹ 16:37, 22 April 2013 (UTC)
Support --Napoleon.tan (talk) 12:19, 30 April 2013 (UTC)
Done as Property:P480. — ΛΧΣ²¹ 07:08, 2 May 2013 (UTC)

Wine AppDB-ID / Wine AppDB-Identifikationsnummer

Done: Wine AppDB ID (P600) (Talk and documentation)

Description	Application-ID in the the AppDB of WineHQ
Data type	String
Domain	Software (running on Windows)
Allowed values	Application-Ids
Example	IrfanView -> 163
Source	appdb.winehq.org
Robot and gadget jobs	Import by bots or gadgets could be done;
Proposed by	MichaelSchoenitzer (talk)

Discussion

Since Property 306 (Operatingsystem) only lists the operating systems the software runs native, but not if the program can be used with Wine and including this information directly to Wikidata wouldn't be a good idea for several reasons (depending on versions and setting, fast changing, good database existing, no need for competition), I would suggest to make it possible to connect Wikidata to this existing Database. MichaelSchoenitzer (talk) 16:09, 18 April 2013 (UTC)

Support I think we could add Wine as value for the platform property, I think this would be work and be ok. --#Reaper (talk) 14:03, 21 April 2013 (UTC)

Support main proposal (Wine AppDB-ID). Superm401 - Talk 03:07, 27 May 2013 (UTC)

Done Property:P600 -- MichaelSchoenitzer (talk) 19:21, 5 June 2013 (UTC)

Landing date / Дата посадки

Done: UTC date of spacecraft landing (P620) (Talk and documentation)

Description	дата посадки, landing date
Data type	Point in time
Template parameter	ru:Шаблон:Космический аппарат, ru:Шаблон:Космическая экспедиция Дата посадки en:Template:Infobox spacecraft return
Domain	космические аппараты
Allowed values	любая дата, можно ограничить снизу 1957 годом
Example	Союз ТМА-9 совершил посадку 21.04.2007 12:31:30 UTC
Source	сайт NASA, карточки в статьях и т. д.
Proposed by	— Ivan A. Krestinin (talk) 19:20, 1 April 2013 (UTC)

Comment added return which is landing date and time. Secretlondon (talk) 12:30, 27 April 2013 (UTC)

Support Secretlondon (talk) 10:10, 6 May 2013 (UTC)

Support --Paperoastro (talk) 13:23, 18 May 2013 (UTC)

Support Danrok (talk) 13:58, 9 June 2013 (UTC)

Launch date / Дата запуска

Done: UTC date of spacecraft launch (P619) (Talk and documentation)

Description	дата запуска/launch date
Data type	Point in time
Template parameter	ru:Шаблон:Космический аппарат, ru:Шаблон:Космическая экспедиция Запуск en:Template:Infobox_spacecraft, en:Template:Infobox space mission en:Template:Infobox spaceflight en:Template:Infobox cargo spacecraft "launch date"
Domain	космические аппараты/ space craft
Allowed values	любая дата, можно ограничить снизу 1957 годом/ any date from 1957 onwards
Example	Кассини-Гюйгенс запущен 15 октября 1997 года, 16:01:00 UTC/ Cassini−Huygens launched 15 October 1997, 16:01:00 UTC
Source	сайт NASA, launchlog, карточки в статьях, список запусков и т. д./ NASA's website, launchlog, articles etc
Robot and gadget jobs	Могу настроить бота на проверку значения свойства по какому-либо источнику, например, launchlog-у./I can set up a bot to get the value from any source eg launchlog
Proposed by	— Ivan A. Krestinin (talk) 19:20, 1 April 2013 (UTC)

Support --Tobias1984 (talk) 08:36, 25 April 2013 (UTC)

Comment I added the en-infobox fields above. -- Docu at 09:58, 27 April 2013 (UTC)

Comment I changed "spacecrafts" to "spacecraft", the English plural (and singular) form of the word is "spacecraft". Cheers. N2e (talk) 12:45, 27 April 2013 (UTC)

Comment - How will this support entries where the exact day or time is not known - for example listing something that happened in October 1997 but on an unknown day, something which happened at an unknown time on 15 October 1997, or something that is listed as happening at 16:01 on that date, but the exact second is not known? --WDGraham (talk) 00:05, 28 April 2013 (UTC)

Support I presume when time is implemented it will handle lack of precision. Secretlondon (talk) 10:08, 6 May 2013 (UTC)

Support --Paperoastro (talk) 13:13, 18 May 2013 (UTC)

Comment Added English translation of the template Secretlondon (talk) 13:26, 18 May 2013 (UTC)

Decay date / Дата схода с орбиты

Done: time of object orbit decay (P621) (Talk and documentation)

Description	ru: Дата схода с орбиты, en: orbital decay
Data type	Point in time
Template parameter	ru:Шаблон:Космический аппарат, ru:Шаблон:Космическая экспедиция Сход_с_орбиты en:Template:Infobox_spacecraft decay
Domain	ru: космические аппараты, en: spacecraft
Allowed values	любая дата, можно ограничить снизу 1957 годом
Example	Союз ТМА-9 сошёл с орбиты 21.04.2007 11:42 UTC
Source	сайт NASA, launchlog, карточки в статьях, список запусков и т. д.
Robot and gadget jobs	Могу настроить бота на проверку значения свойства по какому-либо источнику, например, launchlog-у.
Proposed by	— Ivan A. Krestinin (talk) 19:20, 1 April 2013 (UTC)

CommentAdded decay date which use on en: for when a craft re-enters. We need to be careful with sources. Launchlog from Jonathan's space page is a good source, but is it usable? NASA's NSDDC we generally don't think is accurate enough. Secretlondon (talk) 12:27, 27 April 2013 (UTC)

Support Secretlondon (talk) 10:10, 6 May 2013 (UTC)

Support --Paperoastro (talk) 13:22, 18 May 2013 (UTC)

Docking/Undocking dates / Даты стыковки/расстыковки

Done: spacecraft docking/undocking date (P622) (Talk and documentation)

Description	дата первой стыковки, дата первой расстыковки, дата второй стыковки, дата второй расстыковки и т. д., dates of first and second docking and undocking etc.
Data type	Point in time
Template parameter	ru:Шаблон:Космическая экспедиция Стыковка 1, Расстыковка 1, и т. д. en:Template:Infobox_space_mission Docking date Undocking date en:Template:Infobox_spaceflight docking_date undocking_date
Domain	космические аппараты осуществлявшие стыковку/spacecraft that docked
Allowed values	любая дата, можно ограничить снизу 1957 годом/any date not before 1957
Example	Союз ТМА-9, дата первой стыковки 20 сентября 2006 5:08:42 UTC/ Soyuz TMA-9 date of first docking 20 September 2006 5:08:42 UTC
Source	space.kursknet.ru, карточки в статьях и т. д.
Proposed by	— Ivan A. Krestinin (talk) 19:20, 1 April 2013 (UTC)

CommentAdded in en. Secretlondon (talk) 13:38, 27 April 2013 (UTC)

Support Secretlondon (talk) 10:09, 6 May 2013 (UTC)

Support --Paperoastro (talk) 13:20, 18 May 2013 (UTC)

Crew photo / Фотография членов экипажа

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

Description	фотография членов экипажа
Data type	Commons media file
Template parameter	ru:Шаблон:Космическая экспедиция Фотография en:Template:Infobox_space_mission "crew_photo"
Domain	пилотируемые космические аппараты
Example	Союз ТМА-8, фотография экипажа File:Soyuz TMA-8 crew.jpg
Source	Карточки в статьях
Proposed by	— Ivan A. Krestinin (talk) 19:20, 1 April 2013 (UTC)

Comment I added the en-infobox field above. -- Docu at 10:03, 27 April 2013 (UTC)

Guidance system

Done: guidance system (P624) (Talk and documentation)

Description	Guidance system of a missile
Data type	Item
Domain	term
Example	AIM-9 Sidewinder (Q235396) => infrared homing (Q1366032)
Proposed by	Esquilo (talk)

Discussion: Support - looks like we need this. --Tobias1984 (talk) 12:56, 22 May 2013 (UTC)

Express-3 code / / / Код Экспресс-3

Done: station code (P296) (Talk and documentation)

Description	station code used in post-USSR countries for passenger transportation
Data type	String
Domain	train stations
Example	Kiev Passenger Railway Station has the Express-3 code 2200001
Format and edit filter validation	7 digits
Source	External reference, Wikipedia list article (either infobox or source)
Proposed by	Ahonc (talk)

Discussion

Railway stations in post-USSR countries usually have two codes: UNL code (Russian код ЕСР) which used for cargo transportation and Express-3 code which used in pessenger transportation, e.g. in the tickets. For the UNL code we can use property P296, but for second code we need separate property.Ahonc (talk) 10:51, 2 May 2013 (UTC)

Support Joshbaumgartner (talk) 04:36, 9 May 2013 (UTC)

Comment: I expect it's the same data than the UIC station code I suggested above. The 3 Express-3 code I have found, Kiev(2200001) Tashkent (2900001) and Ulan Bator (3100022), share the same pattern : 7 digits beginning with the 2-digit UIC country code. Ske (talk) 12:12, 22 May 2013 (UTC)

OK, we may merge it with UIC code.--Ahonc (talk) 13:22, 22 May 2013 (UTC)

No, it's NOT the same. UIC code : Kiev 2232030 ; Tashkent 2972661 and Ulan Bator 3105819. 90.63.14.233 21:09, 23 September 2013 (UTC)

IUCN-ID

Done: IUCN taxon ID (P627) (Talk and documentation)

Description	Id of a taxon listed by IUCN Red List
Data type	String
Domain	Source of IUCN conservation status (P141)
Example	Id of Acharagma aguirreanum is 40966
Robot and gadget jobs	Add `'http://www.iucnredlist.org/details/$1/0'` to Gadget-AuthorityControl.js
Proposed by	Succu (talk)

Discussion

Provides a direct link to IUCN Red List whichs maintains the IUCN conservation status (P141). Should be used as source. --Succu(talk) 18:25, 1 June 2013 (UTC)

Strong support --Tobias1984 (talk) 20:23, 1 June 2013 (UTC)

Support Eran (talk) 20:09, 11 June 2013 (UTC)

E number (en)

Done: E number (P628) (Talk and documentation)

Description	E numbers are codes for chemicals which can be used as food additives for use within the European Union (See:E number (Q207810))
Data type	String
Domain	term
Allowed values	See: E number (Q207810)
Example	see Wikidata:Chemistry_task_force/Properties. curcumin (Q312266) = "E100"
Source	http://eur-lex.europa.eu/LexUriServ/LexUriServ.do?uri=OJ:L:2011:295:0001:0177:DE:PDF
Proposed by	GZWDer (talk) 03:07, 7 June 2013 (UTC)

Discussion

Support --Tobias1984 (talk) 07:47, 7 June 2013 (UTC)
Support it's an official identifier in food industry. Snipre (talk) 12:01, 7 June 2013 (UTC)

ISTAT code / codice ISTAT

Done: ISTAT ID (P635) (Talk and documentation)

Description	number sequence for the identification of municipalities in Italy
Data type	String
Template parameter	"Codice statistico" in it:template:Divisione amministrativa
Domain	place
Example	Roma: 058091, Milano: 015146
Format and edit filter validation	(\d){6}
Source	http://www.istat.it/it/archivio/6789
Proposed by	β₁₆ - (talk)

Discussion

Official unique code for municipalities in Italy, assigned by national statistic institute. Same as INSEE (Property:P374) for France. β₁₆ - (talk) 21:02, 2 May 2013 (UTC)

Support Could we use a generic "statistic code" for INSEE, ISTAT, etc.? --Ricordi samoa 11:55, 4 May 2013 (UTC)

Support Ricordisamoa's proposal, adding a qualifier like "statistic institute" to specify the one that set the code. --Viscontino (talk) 13:22, 5 May 2013 (UTC)

Also Property:P382 (for Netherlands) and Property:P442 (for China) are been created. --β₁₆- (talk) 22:57, 5 May 2013 (UTC)

Support Danrok (talk) 22:53, 19 May 2013 (UTC)

Support -- Yiyi .... (talk!) 09:47, 27 May 2013 (UTC)

Support -- CristianCantoro (talk) 12:54, 27 May 2013 (UTC)

Support I'm agree to create a general "statistic code" property (with a qualifier property to distinguish between institutions), but until its discussion and approval, it is better to create this property to import the ISTAT code of municipality. --Paperoastro (talk) 13:08, 27 May 2013 (UTC)

Done --Tobias1984 (talk) 09:19, 17 June 2013 (UTC)

Route of administration

Done: route of administration (P636) (Talk and documentation)

Description	route of administration (Q621636) A route of administration in pharmacology and toxicology is the path by which a drug, fluid, poison, or other substance is taken into the body.
Data type	Item
Template parameter	Template:Infobox medical condition (old) (Q6436840) routes_of_administration
Domain	term
Example	aspirin (Q18216) = "oral", diazepam (Q210402) = "oral" & "intramuscular injection (Q432083)" & "intravenous infusion and defusion (Q640448)" & suppository (Q180799)
Format and edit filter validation	Constraint one of a list of items.
Source	Scientific literature
Robot and gadget jobs	Gather data from infobox
Proposed by	--Tobias1984 (talk) 10:17, 4 June 2013 (UTC)

Discussion: Support --Gambo7 (talk) 20:43, 16 June 2013 (UTC); Support Peter.C (talk) 01:21, 17 June 2013 (UTC); Support The chemicals can used this property too for the definition of the letal dose Snipre (talk) 13:26, 17 June 2013 (UTC)

Done --Tobias1984 (talk) 14:01, 17 June 2013 (UTC)

Protein ID

Done: RefSeq protein ID (P637) (Talk and documentation)

Description	Specifies the Protein ID
Data type	String
Template parameter	en:Template:GNF_Protein_box = Hs_RefseqProtein
Domain	term
Example	Reelin = NP_005036 (RefSeq value)
Format and edit filter validation	Digits + Characters + underscore
Source	http://www.ncbi.nlm.nih.gov/
Robot and gadget jobs	Fill gene wikidata items with appropriate value
Proposed by	Chinmay26 (talk) 20:57, 10 June 2013 (UTC)

Discussion - Using "RefSeq" as qualifier, we can map to Hs_RefseqProtein

Support Andrew Su (talk) 21:47, 10 June 2013 (UTC)
Support Use P89 (P89) as a qualifier similar to Ensembl ID: Q192642 --Tobias1984 (talk) 18:57, 13 June 2013 (UTC)

Done - needed for GSoC. --Tobias1984 (talk) 09:18, 18 June 2013 (UTC)

PDB ID

Done: PDB structure ID (P638) (Talk and documentation)

Description	Protein Data Bank (PDB) contains 3D structures of proteins and nucleic acids. This property will provide access to such structures and associated images for the corresponding biological molecule.
Data type	String
Template parameter	en:Template:GNF_Protein_box = PDB ID
Domain	term
Example	Reelin = "2ddu" & "2e26"
Source	http://www.rcsb.org/pdb/home/home.do , http://www.ebi.ac.uk/pdbsum/ , http://www.pdbe.org/
Robot and gadget jobs	Collect data from MyGene.info and fill gene wiki items with this data
Proposed by	Chinmay26 (talk) 15:38, 10 June 2013 (UTC)

Format: value must be formatted using this pattern (PCRE syntax).
[0-9][a-zA-Z0-9]{3}

Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/Property proposal/Archive/8#Format

Discussion

Support - important part of the protein infobox. --Tobias1984 (talk) 15:46, 10 June 2013 (UTC)
Support - though in cases where multiple PDB IDs exist, I think they should be two instances of the same property (rather than concatenating them into a single field.) Andrew Su (talk) 21:47, 10 June 2013 (UTC)
Comment I changed the proposal so that the two strings are separate. --Tobias1984 (talk) 10:19, 11 June 2013 (UTC)
Support – The filter however should be made more specific (a four letter code composed of a digit followed by three characters that can be either digits or letters, regex: "[0-9][a-zA-Z0-9]{3}"). Boghog (talk) 16:48, 15 June 2013 (UTC)

Done Needed for GSoC. --Tobias1984 (talk) 09:28, 18 June 2013 (UTC)

RNA ID

Done: RefSeq RNA ID (P639) (Talk and documentation)

Description	Specifies the RNA ID
Data type	String
Template parameter	en:Template:GNF_Protein_box = Hs_RefseqmRNA
Domain	term
Example	Reelin = NM_005045 (RefSeq value)
Format and edit filter validation	Digits + Characters + underscore
Source	http://www.ncbi.nlm.nih.gov/
Robot and gadget jobs	Fill gene wikidata items with appropriate value
Proposed by	Chinmay26 (talk) 20:57, 10 June 2013 (UTC)

Discussion - Using "RefSeq" as quaifier, we can map it to Hs_RefseqmRNA.

Support Andrew Su (talk) 21:47, 10 June 2013 (UTC)
Support Use P89 (P89) as a qualifier similar to Ensembl ID: Q192642 for Human and Mouse. --Tobias1984 (talk) 19:04, 13 June 2013 (UTC)

Done needed for GSoC. --Tobias1984 (talk) 09:46, 18 June 2013 (UTC)

Léonore ID (en) / cote base Léonore (fr)

Done: Léonore ID (P640) (Talk and documentation)

Description	ID of a person in the Léonore database (Q2886420) (members of the French Legion of Honour)
Data type	String
Template parameter	fr:template:Base Léonore
Domain	person
Example	Gérard de Cathelineau (Q3124401) => 19800035/435/58145 (link)
Source	http://www.culture.gouv.fr/documentation/leonore/recherche.htm
Proposed by	Ayack (talk) 16:42, 13 June 2013 (UTC)

Discussion

Support It's a useful database with a lot of information (date of birth, date of death, date of Legion of Honour, the resume of a person...) Pyb (talk) 11:37, 14 June 2013 (UTC)

Support --Ricordi samoa 02:33, 17 June 2013 (UTC)

Sport

Done: sport (P641) (Talk and documentation)

Description	sport in which the entity participates or belongs to
Data type	Item
Template parameter	en:template:Infobox sports league sport
Domain	person, organization
Allowed values	sports
Example	National Basketball Association Q155223 => Q5372 Basketball
Proposed by	Danrok (talk) 17:23, 18 May 2013 (UTC)

Discussion

I think this can be done by more general property, like field of this occupation (P425). Infovarius (talk) 19:34, 18 May 2013 (UTC)

How does that fit with organizations such as the National Basketball Association? Danrok (talk) 19:58, 18 May 2013 (UTC)

National Basketball Association field of this occupation (P425) basketball. Infovarius (talk) 10:43, 19 May 2013 (UTC)

P425 is meant to work with terms, not people or organizations. -- Docu at 05:56, 26 May 2013 (UTC)

For sportspeople, we have occupation (P106). For organizations, I would recommend to extend 425 as well, to, say, "field of activity" or something. We will need such a property not only in sports, but for all kinds of different organizations, e.g. companies.--Kompakt (talk) 10:10, 26 May 2013 (UTC)

Support I think "field of activity" is too broad and would prefer a separate property for sport to make it easier for editors to find the appropriate item. A property for "field of business" or similar can be created for businesses.

If the devs decide that a single property covering both of these would make search queries better then they can create a "subproperty" in phase 3 and define "sport" and "business activity" as subproperties of "field of activity". Filceolaire (talk) 21:35, 6 June 2013 (UTC)

It would be used also to indicate the discipline practiced for an athlete? For example, Pietro Mennea --> 200 metres. If yes, I'm

Support. If not, it's the same ;-) (but something for Pietro Mennea --> 200 metres would be useful). -- Yiyi .... (talk!) 17:26, 16 June 2013 (UTC)

I'd suggest that sport = 200 metres (Q211155) would work just fine. I've claimed it as a subclass of sprinting, which is a subclass of athletics, and so on. So, the wider sport category can be found. Danrok (talk) 00:32, 17 June 2013 (UTC)

Done Regards, — Moe Epsilon 21:24, 18 June 2013 (UTC)

of item

Done: of (P642) (Talk and documentation)

Description	qualifiers stating that a statement applies within the scope of a particular item
Data type	Item
Example	<Jean-Baptiste Le Moyne de Martigny> office held mayor of Rochefourchat
Proposed by	Zolo

We need a way to say that X is mayor of village Y for any village. As discussed in Wikidata:Project_chat/Archive/2013/05#Political_offices, putting that in the item about the village iteself does not seem a practical solution. Creating a "mayor of village Y" item for every village does not seem really seem a sensible solution either (unless there is anything specific about the mayor of the village compared to mayors of similar villages). --Zolo (talk) 10:43, 11 May 2013 (UTC)

Maybe can also be used for captials: (if we are supposed to use "instance of" for that)

Stockholm: "instance of" "capital" <"of" "Sweden"><"of" "Stockholm County"><"of" "Stockholm Municipality">.

Since different kinds of capitals use different names (huvudstad, residensstad, centralort), something who tells what kind of capital is needed. -- Lavallen (block) 10:53, 11 May 2013 (UTC)

I thought the head of government property is used inverse: Rochefourchat head of local government <Jean-Baptiste Le Moyne de Martigny> – so instead I think the example should be: <Jean-Baptiste Le Moyne de Martigny> office held mayor of Rochefourchat. Otherwise the proposal looks reasonable. Byrial (talk) 22:46, 12 May 2013 (UTC)

Yes, I should have made that explicit in the example. As discussed in Wikidata:Project_chat/Archive/2013/05#Political_offices, Rochefourchat head of government <Jean-Baptiste Le Moyne de Martigny> is actually a bit problematic (because we need USA: Head of State: President of the United States, not just Head of State: Barack Obama) --Zolo (talk) 17:02, 13 May 2013 (UTC)

Support The qualifier seems useful, but meanwhile I see the potential for abuse, perhaps someone would add statements like "<X> occupation <politician> of <United States of America>". I suggest that the qualifier should only be used when the information cannot be stated using other properties. --Stevenliuyi (talk) 18:59, 14 May 2013 (UTC)

I agree, any idea to make that clear in the label ? --Zolo (talk) 19:43, 14 May 2013 (UTC)

Okay, adopting this idea would have some serious consequences, so this should be discussed thoroughly before being implemented. Having "of" as a qualifier means that the qualifier property itself isn't really adding any data, so it's basically a way to have a top-level property accept two arguments. If Lavallen's idea about "instance of" "capital" "of" X is used, that would mean that either it or P:P36 is redundant. Re use for mayor, the fact that there are some items like Q785304 complicates it somewhat. There are hundreds of potential uses for this qualifier, but we should examine whether these are generally better than using an alternative solution. Also, we might want to ask the devs whether there are any plans to deploy a proper multi-item/argument property type at any point. --Yair rand (talk) 02:26, 20 May 2013 (UTC)

Could you elaborate on the "serious consequences". I can sort of see that it seems to stretch the intended use of qualifiers, but still I think it would not really break anything. If X is the mayor Y, he is really an instance of mayor, so that it do not really make statements false.
There does not seem to be any plan for anything like that by the developers in the initial development plan, so if something gets developed, it is unlikely to be this year. --Zolo (talk) 15:44, 18 June 2013 (UTC)

Comment why not use applies to part, aspect, or form (P518)? Note that I've suggested renaming it to applies to. Danrok (talk) 13:40, 24 May 2013 (UTC)

Support if applies to part, aspect, or form (P518) cannot be used for this. Danrok (talk) 13:46, 24 May 2013 (UTC)

Support Needed as a qualifier not only for mayors, but for many other functions (<dean> of a <faculty>, <bishop> of a <diocese>, <coach> of a <sports club> etc., as well as for some other properties (e.g. award received (P166) <honorary citizenship> of a <city/country>). On the other hand, I'm quite afraid about using a general <of item> qualifier together with a general <instance of> statement to make a statement of anything. We could help it if we make clear guidance how to use it. Stevenliuyi's idea (see above) of using it only as "ultima ratio" can be a good start, I would propose creating a list of properties which can take <of item> property as a qualifier - in a similar way as we have a list of acceptable values for some properties.--Shlomo (talk) 10:57, 11 June 2013 (UTC)

It is hard to make a full list. But I think it would mostly apply to instance of (P31) and related properties. And also to properties like depicts (P180) (Tectonic map and overall architecture of the Alpine orogen (Q13416617) depicts the orogenesis of the Alps). --Zolo (talk) 15:44, 18 June 2013 (UTC)

Done Regards, — Moe Epsilon 21:25, 18 June 2013 (UTC)

Freebase identifier

(moved from Wikidata:Property proposal/all)

Done: Freebase ID (P646) (Talk and documentation)

Description	An ID specifying an equivalent page in the Freebase open knowledge graph.
Data type	String
Template parameter	put Wikipedia infobox parameters here. If existing, sample: "population" in en:template:infobox settlement
Domain	All named entities (eg. person, place, organization, event, creative work)
Allowed values	alpha-numeric string (eg. /m/0j9kvph)
Example	Wikidata => /m/0j9kvph
Format and edit filter validation	All Freebase identifiers should start with "/m/" followed by more than one of the following "0123456789bcdfghjklmnpqrstvwxyz_".
Source	Freebase, Documentation
Robot and gadget jobs	This property can be populated by a bot using interwiki links in Freebase.
Proposed by	Narphorium (talk) 22:57, 10 June 2013 (UTC)

Discussion

Comment As a large contributor to many other external identifiers like Slovakia (Q214), having these connections between the two can make a great bridge to draw other data across. So this could potentially be a boon to our other properties, and means that Wikipedias could include freebase properties. The reason I don't support is because I have to better understand Google's motivations before we start linking with them. Maximilianklein (talk) 19:14, 14 June 2013 (UTC)

Comment Freebase, and by extension the Knowledge Graph, makes use of WP infobox data and it would be great to close the loop so that fixes in either dataset get propagated in both directions. This would make it easier Google and Freebase to use WikiData as well as making it easier for WikiData to pull data from Freebase. This will improve the quality of both datasets over time. --2620:0:1000:147D:1610:9FFF:FEDF:EC57

There should certainly be no loop. Just imagine Wikidata using Freebase as reference and Freebase using Wikidata. We cannot use data from from Freebase. Byrial (talk) 17:29, 17 June 2013 (UTC)

Comment IMHO we should discuss it widely with the community, before even accepting to link a similar database. --Ricordi samoa 08:57, 17 June 2013 (UTC)

Actually, I can imagine that there would be some benefits for Google, as it would probably outsource some of the curation work needed for Freebase. I am not so sure about the benefits for Wikidata as we have stricter requirements in terms of sources, and of license, that may make it hard to use Freebase content. That said, I cannot see what harm there can be in having this link. --Zolo (talk) 15:18, 17 June 2013 (UTC)

Comment, I have left a message at the Village Pump. --Zolo (talk) 15:18, 17 June 2013 (UTC)

Support - In my opinion there is no harm to link to Freebase, but nothing really to gain as freebase is of poor quality for most scientific topics (The other items probably not meeting the notability standards). I oppose importing data and properties. That would just increase the "imported from Wikipedia" source problem. Lastly one has to admit that any structured information added to Wikipedia and Wikidata (or the internet for that matter) will benefit the business models of internet search engine providers. A point we might as well ignore, the Wikimedia foundation should charge for, or we have to be thankful for the donations (e.g. Google, Yandex). --Tobias1984 (talk) 16:08, 17 June 2013 (UTC)

Comment – I cannot see any gain from having this property, but I would like to see a motivation for the proposal before definitive saying no. Byrial (talk) 17:29, 17 June 2013 (UTC)

Support linking to Freebase, just like we link to all sorts of other databases, as well as using it as a source in the "imported from" field, seeing as we've historically allowed using user-generated sources for the importing of statements. — PinkAmpers&^{(Je vous invite à me parler)} 00:50, 18 June 2013 (UTC)

Support Useful --FischX (talk) 11:56, 18 June 2013 (UTC)

Done Regards, — Moe Epsilon 21:32, 18 June 2013 (UTC)

Open Library identifier

Done: Open Library ID (P648) (Talk and documentation)

Description	Numeric book identifier, similar to ISBN but without date restriction. It has two versions: at work and at edition level
Data type	String
Domain	Mainly published materials.
Allowed values	OLXXXXXW for works, OLXXXXXXM for editions, where X is a number.
Example	Twenty years after <Open Library identifier> OL6985207M
Proposed by	--Micru (talk) 01:02, 5 June 2013 (UTC)

Discussion

Support See Wikidata:Books_task_force#Edition_properties--Micru (talk) 01:02, 5 June 2013 (UTC)
Support Caution, identifiers are non-unique. There can be several OLXXXXXW work numbers for one work, several OLXXXXXXM edition numbers for one edition, and several OLXXXXXA numbers for one author. There is a redirect mechanism on OpenLibrary, but it does not work cleanly at this time. LeadSongDog (talk) 21:10, 5 June 2013 (UTC)
Support The label is disambiguate. Do we need two identifiers? If this one should be for books (works and editions) what is the label for the "Open Library identifier"s for authors. --Kolja21 (talk) 15:26, 15 June 2013 (UTC)
Done Regards, — Moe Epsilon 22:05, 18 June 2013 (UTC)

Direction relative to location (en)

Done: direction relative to location (P654) (Talk and documentation)

Description	To be used as a qualifier for geographical locations to express relative direction (e.g. "west of Goldsby").
Data type	Item
Template parameter	n/a
Domain	To be used in any situation where it is appropriate to state a relative location
Allowed values	any
Example	See description
Proposed by	—Scott5114 ↗ [EXACT CHANGE ONLY] 02:17, 6 June 2013 (UTC)

Discussion

If a less clunky label can be come up with, please suggest it. —Scott5114 ↗ [EXACT CHANGE ONLY] 02:17, 6 June 2013 (UTC)

Support - Could definitely be useful as a qualifier for properties like terminus (P559). T C N7JM 02:47, 6 June 2013 (UTC)
Support --Rs chen 7754 06:24, 6 June 2013 (UTC)
Isn't that P596 (P596) ? --Zolo (talk) 07:24, 6 June 2013 (UTC)
- No, but P596 (P596) appears to be redundant to direction (P560), so I will be headed off to properties for deletion after this. The difference here is that 560/596 are used to tag the direction of something (e.g. distinguishing between the north and south ends of something). This property would be to establish location relative to something else (e.g. establishing that something is north of something else). The reason both are needed is because of things like the terminus location parameter proposed directly above this; a location may need to be qualified as referring to the north end of the item, but being west of some city. —Scott5114↗ [EXACT CHANGE ONLY] 08:02, 6 June 2013 (UTC)
  - I am not sure I understand, could you provide a full example ? As I see it, P596 is used to state relative positions, like North America borders South America to the North. --Zolo (talk) 08:18, 6 June 2013 (UTC)
    - Sure. Oklahoma State Highway 132 (Q2174277) has its south end at a point west of the town of Hennessey (Q2305381). So with this property and the terminus location property proposed above, that would be expressed Oklahoma State Highway 132 (Q2174277) <terminus location> Hennessey (Q2305381) <direction (P560)> south (Q667), <direction relative to location> west (Q679).

- - - If P596 (P596) is meant to fulfill the purpose of this proposal, then its documentation needs to be improved to make this evident, as direction of something versus direction relative to something is a subtle point, and the way the documentation is worded now makes it look wholly redundant to direction (P560). —Scott5114 ↗ [EXACT CHANGE ONLY] 09:14, 6 June 2013 (UTC)

┌────────────────────────────────────────────────────────────────────────────────────────────────────┘ Yes, P596 (P596) should be relabelled and better documented, but looking at how it is used, it seems to be different from direction (P560).

I think that this proposal is similar to how P596 is used, except that the syntax is inverted:

Asia: shares borders with: Europe: to the West
Oklahoma State Highway 132 (Q2174277): end point: Hennessey (Q2305381)West of

In the second case, "West" means West of the property value, while in the first one, it means West of the item, so East of the property value. That seems potentially confusing, and I think we should have just one format, but I really do not know which one. --Zolo (talk) 07:24, 7 June 2013 (UTC)

See, to me that looks a lot like what direction (P560) is doing. Asia has multiple borders. One is with Europe. Which one? The west border. (By analogy to SH-132—the highway has multiple end points. One of them is at SH-51. Which one? The south end point.) I think that P596 (P596) is probably a lot closer to direction (P560) than to this proposal. I agree, it's a somewhat confusing distinction to make, but I think it is one that should be made. —Scott5114 ↗ [EXACT CHANGE ONLY] 10:05, 7 June 2013 (UTC)

Ok, I think you are right, so

Support--Zolo (talk) 14:08, 7 June 2013 (UTC)