View source for Testwiki:Property proposal/Archive/9

{{archive|category=Property proposal archive}}
__TOC__
==== [[P:P625|coordinate location / Standort / Position]] ====
<span id="P625"></span>{{status|done}} → [[Property:P625]]
* '''Description''': Coordinates of the place
* '''Datatype''': [[m:Wikidata/Data_model#Geographic locations|GeoCoordinateValue]]
* '''Links''': 
* '''Infobox parameter example:'''
* '''Comments:''' 
:{{support}} must needed property. --[[User:Nizil Shah|Nizil Shah]] ([[User talk:Nizil Shah|talk]]) 20:39, 8 February 2013 (UTC)
:: {{support}}. --[[User:NaBUru38|NaBUru38]] ([[User talk:NaBUru38|talk]]) 21:39, 8 February 2013 (UTC)
:Proposal to change the label from "Location" to "location coordinate" to be more explicit and to avoid conflict with the other proposed property. (see: http://www.wikidata.org/wiki/Wikidata:Property_proposal#Is_in_.2F_Ist_in_.2F_Est_a) --[[User:Napoleon.tan|Napoleon.tan]] ([[User talk:Napoleon.tan|talk]]) 02:50  February 16, 2013 (UTC)
:: {{support}}: location coordinate --[[User:ThorstenX1|ThorstenX1]] ([[User talk:ThorstenX1|talk]]) 19:47, 16 February 2013 (UTC)
:: {{support}} Important, but should be renamed as proposed above. -- [[User:Faux|Faux]] ([[User talk:Faux|talk]]) 21:52, 17 February 2013 (UTC)
:::Changed. [[User:Sven Manguard|<span style="color:#207004">'''<span style="font-size:115%">S</span>ven <span style="font-size:115%">M</span>anguard'''</span>]] [[User talk:Sven Manguard|<small><span style="color:#F0A804">'''Wha?'''</span></small>]] 05:37, 18 February 2013 (UTC)

==== [[P:P626|Sandbox-GeoCoordinateValue / Spielwiese-GeoCoordinateValue / Bac à sable-GeoCoordinateValue / Pagina delle prove-GeoCoordinateValue]] ====
<span id="P626"></span>{{status|done}}
{{comment}}  → [[Property:P626]] created now that coordinates datatype is available.''' —&nbsp;[[User:PinkAmpersand|<u><font color="000">PinkAmpers</font></u>]]'''[[User talk:PinkAmpersand|'''<u><font color="FF1493">&#38;</font></u>'''<font color="000"><sup>(<u>''Je vous invite à me parler''</u>)</sup></font>]] 18:47, 10 June 2013 (UTC)
----
* '''Description:''' any kind of values
* '''Datatype:''' [[m:Wikidata/Data_model#Geographic locations|GeoCoordinateValue]] (1 Sandbox type per available data type)
* '''Domain:''' any kind of values
* '''Infobox parameter:''' any/generic (but more for testing than productive)
* '''Comments:'''
----
''Original discussion below copied from [[Wikidata:Property proposal/Archive/4#P370]].''

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 --[[User:DrTrigon|DrTrigon]] ([[User talk: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)? [[User:Snipre|Snipre]] ([[User talk: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 --[[User:DrTrigon|DrTrigon]] ([[User talk: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. [[User:Snipre|Snipre]] ([[User talk: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. --[[User:DrTrigon|DrTrigon]] ([[User talk:DrTrigon|talk]]) 22:36, 22 March 2013 (UTC)
:::::I think testing bots should not be done on the productive Wikidata, except in the [[Q4115189|sandbox]].--[[User:Faux|Faux]] ([[User talk: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 --[[User:DrTrigon|DrTrigon]] ([[User talk: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... --[[User:DrTrigon|DrTrigon]] ([[User talk: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. --[[User:Zolo|Zolo]] ([[User talk:Zolo|talk]]) 21:29, 23 March 2013 (UTC)
::::::::Sounds good! (+1) Thanks for the idea! Greetings --[[User:DrTrigon|DrTrigon]] ([[User talk: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? --[[User:Faux|Faux]] ([[User talk: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. --[[User:Zolo|Zolo]] ([[User talk: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 --[[User:DrTrigon|DrTrigon]] ([[User talk:DrTrigon|talk]]) 10:52, 29 March 2013 (UTC)
::Ok here we go:
::# [[Property:P368|Sandbox-CommonsMediaFile (P368)]]
::# [[Property:P369|Sandbox-Item (P369)]]
::# [[Property:P370|Sandbox-String (P370)]]
::so these can be considered '''done''' but I think it makes sence to propose the future ones too and set them to the [[Wikidata:Property_proposal/Pending|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 --[[User:DrTrigon|DrTrigon]] ([[User talk:DrTrigon|talk]]) 01:09, 30 March 2013 (UTC)

==== Reference property: Minor planet circular  ====
{{Property proposal
|status                 = not done
|description            = to be used as a source-property, to reference such thing as P138
|infobox parameter      = 
|datatype               = string
|domain                 = Minor Planets and Comets
|allowed values         = 
|suggested values       = "Name Ref." in [http://www.minorplanetcenter.net/iau/lists/NumberedMPs005001.html this] can be used.
|source                 = 
|example                = "MPC 21134" or only "21134" in [[Q155190|5261 Eureka]]
|filter                 = ?
|robot and gadget jobs  = Possible, but be carefull! Examples where it can be wrong is in "216 Kleopatra". MPC 73983 only tells the origin of the name of "Cleoselene" and "Alexhelios", not the main object itself. 
|proposed by            = [[User:Lavallen|Lavallen]] ([[Special:Block/Lavallen|block]])
}}
;Discussion
Today I see [[q328]] used as "source" everywhere and my insticts tells me it's wrong, but I understand why it's necessary. This gives us a better alternative. [[User:Lavallen|Lavallen]] ([[Special:Block/Lavallen|block]]) 18:24, 10 May 2013 (UTC)
* {{support}} This is a good idea! A script could automatically show the link to the web page, as for GND or VIAF properties. --[[User:Paperoastro|Paperoastro]] ([[User talk:Paperoastro|talk]]) 11:25, 12 May 2013 (UTC)
::A good idea, if it's possible. I have tried to copy those uri, but there is something strange with them. Does it demand a POST? -- [[User:Lavallen|Lavallen]] ([[Special:Block/Lavallen|block]]) 13:37, 12 May 2013 (UTC)
:::[http://www.minorplanetcenter.net/iau/ECS/MPCArchive/2013/MPC_20130425.pdf This] is one of the last MPC. The link is made with the date of publication. Perhaps my idea is not so simple! --[[User:Paperoastro|Paperoastro]] ([[User talk:Paperoastro|talk]]) 18:59, 12 May 2013 (UTC)
:Please do not create a particular reference system. For website we have a set of "mandatory" parameters see in order to have a general concept as explained in [[Help:Sources]]. And if you want to use URL data please wait on the appropriate datatype because it would be a mess later. [[User:Snipre|Snipre]] ([[User talk:Snipre|talk]]) 17:22, 18 May 2013 (UTC)
::@[[User:Paperoastro|Paperoastro]] Your proposition (pdf) can be defined as a report in the [[Help:Sources]] page. [[User:Snipre|Snipre]] ([[User talk:Snipre|talk]]) 17:26, 18 May 2013 (UTC)
:::I did not proposed it as a webb-property. I do not simply find a way to create a url based on this "number". I rather propose this as a "serial number" for this publication. The matrix in the webb-page above simply connects each "serial number" with some claim in some items. I know there is a RFC about references in progress, and this proposal should not be closed as succesfull until we know the result of that RFC. 
:::Regarding the RFC: I find it very difficult to understand what they talk about there. But I often fail to understand the technical parts of references even when they are discussed on Wikipedia. To often are Wikipedians speaking about references as if they are going to publish a hand-written dissertation. My teacher told me to not bother about such things, as long as I use the same system in all of the paper. LaTeX simply solved that for me. -- [[User:Lavallen|Lavallen]] ([[Special:Block/Lavallen|block]]) 17:52, 18 May 2013 (UTC)
::::RFC concerns mainling books and the problem of different editions of the same but having different bibliographic data. Do not focus on that if you are not using books for referencing. [[User:Snipre|Snipre]] ([[User talk:Snipre|talk]]) 04:24, 19 May 2013 (UTC)
I'm sorry to generate confusion with my idea of automatic link! MPC circulars are identified only by a progressive number (and, optional, by the date of pubblication), as specified by Lavallen in this proposal. My idea of creating automatically a link to the web page (as for GND or VIAF) is not feasible because the circulars are grouped by the day of pubblication.

@[[User:Snipre|Snipre]] thank you very much for the link, I read it very carefully. Imho the idea to have few properties to manage sources is intriguing and "MPC circulars" could be identified in the group of report.

@[[User:Lavallen|Lavallen]] your professor (and you) has right: is importat to use the same system, and in [[Help:Sources]] people try to do this for Wikidata ;-) Do not be discouraged! If I understand correctly, MPC circulars can be identified as "Report" in this manner:
* Title: ''MPC circulars'' number;
* Author: the list of authors;
* Publisher: ''Minor Planet Center'';
and, if we want, we can use also the Date of publication and the language. Do you agree?

If all of you are agree, we can change this proposal to create the missing property ''title'' for Reports. --[[User:Paperoastro|Paperoastro]] ([[User talk:Paperoastro|talk]]) 00:31, 19 May 2013 (UTC) <small>P.S.: I hope not to be too bold!</small>
: That's it. This property is already proposed in [[Wikidata:Property_proposal/References#Article title]]. We can extend the application field to report and media without any problem. [[User:Snipre|Snipre]] ([[User talk:Snipre|talk]]) 04:24, 19 May 2013 (UTC)
: Please support the Article title proposal with your comment for extension to report in order to show the consensus for the property creation. [[User:Snipre|Snipre]] ([[User talk:Snipre|talk]]) 17:53, 26 May 2013 (UTC)

I support such property, but it should have also link to circular.--[[User:Ahonc|Ahonc]] ([[User talk:Ahonc|talk]]) 20:45, 26 May 2013 (UTC)

@[[User:Lavallen|Lavallen]]: they actually use some sort of silly [[:en:HTTP referer|referer]] check, the message is "This script can only be called by the MPES or from the list of discovery circumstances of numbered minor planets." --<span style="font-variant:small-caps">[[User:Ricordisamoa|<span style="color:#004B70">Ricordi</span>]][[User talk:Ricordisamoa|<span style="color:#00703E">samoa</span>]]</span> 22:44, 26 May 2013 (UTC)
:{{done|resolved}}, http://scully.cfa.harvard.edu/cgi-bin/showcitation.cgi?num=005002 can now be shortened and hotlinked with http://ricordisamoa.tk/mpc/005002! --<span style="font-variant:small-caps">[[User:Ricordisamoa|<span style="color:#004B70">Ricordi</span>]][[User talk:Ricordisamoa|<span style="color:#00703E">samoa</span>]]</span> 23:25, 26 May 2013 (UTC)
::Very interesting! Thanks! :) Can be used automatically without URL datatype? --[[User:Paperoastro|Paperoastro]] ([[User talk:Paperoastro|talk]]) 10:45, 8 June 2013 (UTC)
:Can we close the proposal ? [[User:Snipre|Snipre]] ([[User talk:Snipre|talk]]) 13:31, 10 June 2013 (UTC)
:: I think yes. --[[User:Paperoastro|Paperoastro]] ([[User talk:Paperoastro|talk]]) 14:05, 10 June 2013 (UTC)

=== edition of ===
{{Property proposal
|status                 = 629
|description            = this item is used to link the edition item with its main work item.
|infobox parameter      = 
|datatype               = item
|domain                 = mainly books, can be used for other domains
|allowed values         = 
|suggested values       =
|source                 =
|example                = ''Edwards, Phillip, ed. 1985'' <edition of> ''Hamlet''
|filter                 = 
|proposed by            = --[[User:Micru|Micru]] ([[User talk:Micru|talk]]) 01:02, 5 June 2013 (UTC)
}}
;Discussion
*{{support}} Needed to complete the logical structure of book sources. See [[Wikidata:Books_task_force#Edition_properties]]--[[User:Micru|Micru]] ([[User talk:Micru|talk]]) 01:02, 5 June 2013 (UTC)
*{{support}} --[[User:Stevenliuyi|Stevenliuyi]] ([[User talk:Stevenliuyi|talk]]) 20:32, 5 June 2013 (UTC)
*<s>{{oppose}}</s> We can use instance of or subclass of. [[User:Snipre|Snipre]] ([[User talk:Snipre|talk]]) 18:14, 8 June 2013 (UTC) I am not convinced by this proposal but I prefer to have this property and a solution for sourcing statement than spending still weeks in discussion. We can always change the property later. [[User:Snipre|Snipre]] ([[User talk:Snipre|talk]]) 19:26, 14 June 2013 (UTC)
**Probably "subclass of" would confuse users. "Edition of" is more clear in that regard.--[[User:Micru|Micru]] ([[User talk:Micru|talk]]) 20:07, 12 June 2013 (UTC)
*{{S}} [[User:Filceolaire|Filceolaire]] ([[User talk:Filceolaire|talk]]) 18:00, 10 June 2013 (UTC)
==> continued in [[Wikidata:Property_proposal/Archive/9#edition (2)|#edition (2)]], below.

=== Paris electronic code / code information de la ville de Paris ===
{{Property proposal
|status                 = 630
|description            = electronic code used by the city of Paris for street identification
|infobox parameter      = [[:fr:Template:Infobox Voie parisienne]]
|datatype               = string
|domain                 = streets in Paris
|allowed values         = 
|suggested values       =
|source                 = I think they have already all been imported to fr.wikipedia
|example                = {{Q|550}} -> [http://www.v2asp.paris.fr/commun/v2asp/v2/nomenclature_voies/Voieactu/1736.nom.htm 1736]
|filter                 = 
|robot and gadget jobs  = 
|proposed by            = [[User:Zolo|Zolo]] ([[User talk:Zolo|talk]]) 14:40, 20 May 2013 (UTC)
}}
:*{{support}} - We need this. --[[User:Tobias1984|Tobias1984]] ([[User talk:Tobias1984|talk]]) 19:36, 1 June 2013 (UTC)


=== Structural engineer ===
{{Property proposal
|status                 = 631
|description            = The senior structural engineer for this building project, usually a person or organization (similar to architect property)
|infobox parameter      = [[:en:template:infobox building]] structural_engineer
|datatype               = item
|domain                 = work or geographical feature
|allowed values         = 
|suggested values       =
|source                 = 
|example                = World Trade Center [[Q11235]] => [[Q6530777]] Leslie E. Robertson
|filter                 = 
|robot and gadget jobs  = 
|proposed by            = [[User:Danrok|Danrok]] ([[User talk:Danrok|talk]]) 14:50, 16 May 2013 (UTC)
}}
;Discussion
:{{support}} --[[User:Чаховіч Уладзіслаў|Чаховіч Уладзіслаў]] ([[User talk:Чаховіч Уладзіслаў|talk]]) 08:56, 3 June 2013 (UTC)

=== Cultural properties of Belarus reference number / Шыфр гісторыка-культурнай каштоўнасці Рэспублікі Беларусь ===
{{Property proposal
|status                 = 632
|description            = reference number of Belarusian сultural property
|infobox parameter      = 
|datatype               = string
|domain                 = creative work
|allowed values         = instance of [[Q2079150|Cultural property]]
|suggested values       =
|source                 = [http://icomos.by/images/Spis-HKK-2012.pdf State Register of Historical and Cultural Values of the Republic of Belarus (2012)]
|example                = [[Q1532456|Corpus Christi Church in Nesvizh]] → 610Г000465
|filter                 = 
|robot and gadget jobs  =  Could be imported from Belarusian Wikipedia ([[w:be:Шаблон:Гісторыка-культурная каштоўнасць Рэспублікі Беларусь|template]])
|proposed by            = [[User:Чаховіч Уладзіслаў|Чаховіч Уладзіслаў]] ([[User talk:Чаховіч Уладзіслаў|talk]])
}}
;Discussion
:{{support}}--[[User:Хомелка|Хомелка]] ([[User talk:Хомелка|talk]]) 05:30, 3 June 2013 (UTC)


=== Répertoire du patrimoine culturel du Québec identifier / identifiant Répertoire du patrimoine culturel du Québec  ===
{{Property proposal
|status                 = 633
|description            = The (unique) identifier of a {{Q|3456276}}
|infobox parameter      = 
|datatype               = string
|domain                 = instance of {{Q|3370013}}
|allowed values         = number only 
|suggested values       = 
|source                 = http://www.patrimoine-culturel.gouv.qc.ca/
|example                = {{Q|1032248}} ==> [http://www.patrimoine-culturel.gouv.qc.ca/rpcq/detail.do?methode=consulter&id=98890&type=bien 98890]
|filter                 = 
|robot and gadget jobs  = 
|proposed by            = [[User:Fralambert|Fralambert]] ([[User talk:Fralambert|talk]])
}}
;Discussion
Useful as not all the properties inscribed in the {{Q|3456276}} are present in {{P|477}}. --[[User:Fralambert|Fralambert]] ([[User talk:Fralambert|talk]]) 03:19, 26 May 2013 (UTC)
:{{Support}}.  This should probably be at [[Wikidata:Property proposal/Authority control]], though. [[User:Superm401|Superm401]] - [[User_talk:Superm401|Talk]] 03:03, 27 May 2013 (UTC)
:: Should I move the proposal? I put this here because {{P|477}} and {{P|380}} was in creative work. --[[User:Fralambert|Fralambert]] ([[User talk:Fralambert|talk]]) 13:08, 28 May 2013 (UTC)
*{{support}} [[User:Danrok|Danrok]] ([[User talk:Danrok|talk]]) 13:57, 9 June 2013 (UTC)
{{anchor|P634}}

=== Captain / Kapitän / Capitaine ===
<span id="P634"></span>{{status|done}} → [[Property:P634]]
* '''Description''': Captain of a sports team
* '''Datatype''': Item
* '''Links''': 
* '''Domain''': sports teams
* '''Infobox parameter example:''' hockey club: [[:en:Template:Infobox hockey team]] (captain parameter)
* '''Comments:'''  --[[User:Carport|Carport]] ([[User talk:Carport|talk]]) 17:36, 8 March 2013 (UTC)
{{support}} [[User:Shawn in Montreal|Shawn in Montreal]] ([[User talk:Shawn in Montreal|talk]]) 17:45, 8 March 2013 (UTC)
:{{Comment}} only current captain or every captains in the team history? --[[User:Stryn|Stryn]] ([[User talk:Stryn|talk]]) 09:04, 16 March 2013 (UTC)
::All. Qualifiers will tell when each player was captain. --[[User:NaBUru38|NaBUru38]] ([[User talk:NaBUru38|talk]]) 19:39, 27 March 2013 (UTC)
:{{Support}} --[[User:Stryn|Stryn]] ([[User talk:Stryn|talk]]) 12:08, 28 May 2013 (UTC)
:{{Done}} - Created at {{P|634}}. [[User:Superm401|Superm401]] - [[User_talk:Superm401|Talk]] 19:10, 16 June 2013 (UTC)
=== <s>Station Class / 车站等级</s> ===
{{Property proposal
|status                 = not done
|description            = [[:en:Top_Class_station]]，Station Class used in China (both PRC and ROC have station classes, though different)
for Taiwan's station class, see [[:zh:特等站 (台鐵)]]
|infobox parameter      = sample: "TraLevel" in [[:zh:Template:Infobox_Station]], "车站等级" in [[:zh:Template:Infobox China railway station]]
|datatype               = item
|domain                 = Train station in China
|allowed values         = Several station class items
|suggested values       = 
|source                 = [http://www.people.com.cn/item/flfgk/gwyfg/1980/226009198001.html 铁路车站等级核定办法（草案）] for PRC. 
|example                = [[Q523887]]-> [[Q3183365]], [[Q700588]]->[[Q12820822]]
|filter                 =
|robot and gadget jobs  =
|proposed by            = [[User:Li3939108|<span style="font-family:sans-serif;">凡其</span>]][[User talk:Li3939108|<span style="font-family:sans-serif;"><sub>Fanchy</sub></span>]]
}}
{{support}}, but I think it would be better if the property is named "station classification". --[[User:Wylve|Wylve]] ([[User talk:Wylve|talk]]) 15:50, 26 May 2013 (UTC)
:I don't know if there is an official translation or not. "station class" can only be found on English Wikipedia. --[[User:Li3939108|<span style="font-family:sans-serif;">凡其</span>]][[User talk:Li3939108|<span style="font-family:sans-serif;"><sub>Fanchy</sub></span>]] 19:57, 1 June 2013 (UTC)
::On second thought, This can be done with {{P|31}}.--[[User:Li3939108|<span style="font-family:sans-serif;">凡其</span>]][[User talk:Li3939108|<span style="font-family:sans-serif;"><sub>Fanchy</sub></span>]] 19:17, 2 June 2013 (UTC)
'''This proposal will be deleted''': proposal withdrawn [[User:Snipre|Snipre]] ([[User talk:Snipre|talk]]) 08:27, 15 June 2013 (UTC)
=== Article title ===

{{Property proposal
|status            = not done
|description       = Title of a scientific article, newspaper article in reference purpose
|infobox parameter = 
|datatype          = string
|source            = 
|example           = 
|robot and gadget jobs = 
|proposed by      = [[User:Snipre|Snipre]] ([[User talk:Snipre|talk]]) 09:31, 13 April 2013 (UTC)
}}
It is not possible to have an item for every article so for reference purpose so we need an additional property allowing to enter this information in reference data. A constraint to use this propery will be to use it in parallel of the property "stated in": the "Article title" property concern only subpart of another work (a journal for example) and the whole work in which the article is published has to be cited too. [[User:Snipre|Snipre]] ([[User talk:Snipre|talk]]) 09:31, 13 April 2013 (UTC)

:I think we need a "title" property for all sorts of  works. It should be a monolingual string, a be the full title, by contrast to the label that is multilingual, will often be missing in many languages, and can clip the real title for convenience).
:I would support simply renaming [[P:P357]] to title. Having two properties is confusing, as we do not know which one to choose when the work does not have any translation. Major libraries simply use "title" for the original title, and that makes even more sense in a multilingual database. Note that I had initially created [[P:P357]] under the name title and documented it with [[Q12418]], where "original title" does not make any sense. --[[User:Zolo|Zolo]] ([[User talk:Zolo|talk]]) 07:29, 25 April 2013 (UTC)
::"monolingual string", what is the difference between "monolingual string" and "string"? -- [[User:Lavallen|Lavallen]] ([[Special:Block/Lavallen|block]]) 16:13, 26 May 2013 (UTC)

:: <del>A general title property for articles, report, books and so on will be very useful. Initially I was agree with Zolo to use [[P:P357]], but I prefer as datatype ''monolingual string'' instead of ''string'', so I {{support}} the creation of this property with ''monolingual string'' datatype. To avoid confusion, P357 should be deleted.</del> @[[User:Lavallen|Lavallen]]: ''monolingual string'' is a string with in addition the specification of the language of the text. --[[User:Paperoastro|Paperoastro]] ([[User talk:Paperoastro|talk]]) 18:36, 26 May 2013 (UTC)
::: We have a property to specify the language of the work see [[Property:P407]], so we don't need to wait on a monolingual datatype. Using a property to screen language of sources is more simpler than using a subinformation of a datatype. And if you assume that you will have item as sources like for books, the language property will be the best solution to screen and compare languages of all sources and in a independent way from the datatype. [[User:Snipre|Snipre]] ([[User talk:Snipre|talk]]) 07:38, 27 May 2013 (UTC)
:::: Your idea sounds good, and surely it could avoid confusion. (I "delete" my comment above, after your explanation) ;) Before to support this proposal, I have a question: what is the difference between this new property and [[P:P357]]? There are any reasons to have a different property? --[[User:Paperoastro|Paperoastro]] ([[User talk:Paperoastro|talk]]) 11:47, 27 May 2013 (UTC)
::::: I did a proposition to extend the application field of the original title property [[Property_talk:P357#Extension_of_this_property|there]]. [[User:Snipre|Snipre]] ([[User talk:Snipre|talk]]) 18:57, 27 May 2013 (UTC)
:'''This proposal will be deleted''': an existing properties is used in an extending concept. [[User:Snipre|Snipre]] ([[User talk:Snipre|talk]]) 13:49, 13 June 2013 (UTC)
=== Original name /// Название на языке страны  ===
{{Property proposal
|status                 = not done
|description            = name of place on the official language of country where the place located
|infobox parameter      = original name
|datatype               = string (multilingual)
|domain                 = Place
|allowed values         = any
|suggested values       =
|source                 = official documents, classifiers, other sources
|example                = [[Q1726]] => München, [[Q1899]] => Київ, [[Q162548]] => Усть-Каменогорск (ru), Өскемен (kk) (2 values with qualifiers because of two state languages)
|filter                 = 
|robot and gadget jobs  = 
|proposed by            = [[User:Ahonc|Ahonc]] ([[User talk:Ahonc|talk]])
}}
;Discussion
:'''<big>This proposal will be deleted:</big>''' it is redundant with [[Wikidata:Property_proposal/Pending#Official_name_.2F_Name_.2F_Nom_.2F]]. [[User:Snipre|Snipre]] ([[User talk:Snipre|talk]]) 19:18, 10 June 2013 (UTC)

=== Critical pressure (en) ===
{{Property proposal
|status                 = not done
|description            = 
|infobox parameter      = 
|datatype               = value
|domain                 = term
|allowed values         = 
|suggested values       = 
|source                 = 
|example                = see [[Wikidata:Chemistry_task_force/Properties]].
|filter                 = 
|robot and gadget jobs  = 
|proposed by            = [[User:GZWDer|GZWDer]] ([[User talk:GZWDer|talk]]) 03:07, 7 June 2013 (UTC)
}}
;Discussion
:{{support}} [[User:Snipre|Snipre]] ([[User talk:Snipre|talk]]) 12:09, 7 June 2013 (UTC)
:'''This proposal will be deleted''': this proposal is merged. [[User:Snipre|Snipre]] ([[User talk:Snipre|talk]]) 19:27, 12 June 2013 (UTC)

=== Critical temperature (en) ===
{{Property proposal
|status                 = not done
|description            = 
|infobox parameter      = 
|datatype               = value
|domain                 = term
|allowed values         = 
|suggested values       = 
|source                 = 
|example                = see [[Wikidata:Chemistry_task_force/Properties]].
|filter                 = 
|robot and gadget jobs  = 
|proposed by            = [[User:GZWDer|GZWDer]] ([[User talk:GZWDer|talk]]) 03:07, 7 June 2013 (UTC)
}}
;Discussion
:{{support}} [[User:Snipre|Snipre]] ([[User talk:Snipre|talk]]) 12:09, 7 June 2013 (UTC)
:'''This proposal will be deleted''': this proposal is merged. [[User:Snipre|Snipre]] ([[User talk:Snipre|talk]]) 19:29, 12 June 2013 (UTC)

=== Triple point pressure (en) ===
{{Property proposal
|status                 = not done
|description            = 
|infobox parameter      = 
|datatype               = value
|domain                 = term
|allowed values         = 
|suggested values       = 
|source                 = 
|example                = see [[Wikidata:Chemistry_task_force/Properties]].
|filter                 = 
|robot and gadget jobs  = 
|proposed by            = [[User:GZWDer|GZWDer]] ([[User talk:GZWDer|talk]]) 03:07, 7 June 2013 (UTC)
}}
;Discussion
:{{support}} [[User:Snipre|Snipre]] ([[User talk:Snipre|talk]]) 12:09, 7 June 2013 (UTC)
:{{comment}} Isn't it enough to create the property "triple point temperature" and use a qualifier for the pressure? As an alternative we could also make a property called "triple point" that links to an item which describes which triple point were talking about. Both temperature and pressure would be existing qualifiers for that property and we would be able to create items for all the phase changes not only the triple point for solid-liquid-gas. --[[User:Tobias1984|Tobias1984]] ([[User talk:Tobias1984|talk]]) 15:25, 10 June 2013 (UTC)
:'''This proposal will be deleted''': this proposal is merged. [[User:Snipre|Snipre]] ([[User talk:Snipre|talk]]) 19:29, 12 June 2013 (UTC)

=== Triple point temperature (en) ===
{{Property proposal
|status                 = not done
|description            = 
|infobox parameter      = 
|datatype               = value
|domain                 = term
|allowed values         = 
|suggested values       = 
|source                 = 
|example                = see [[Wikidata:Chemistry_task_force/Properties]]. {{Q|283}} = 273.16 K & "at pressure" = 611.73 Pa
|filter                 = 
|robot and gadget jobs  = 
|proposed by            = [[User:GZWDer|GZWDer]] ([[User talk:GZWDer|talk]]) 03:07, 7 June 2013 (UTC)
}}
;Discussion
:{{support}} [[User:Snipre|Snipre]] ([[User talk:Snipre|talk]]) 12:09, 7 June 2013 (UTC)
:{{Comment}} I think ''key point'' (item) with qualifiers ''temperature'' (number) and ''pressure'' (number) would be a better solution than having these 4 properties. This way all the information belonging together would be in the same claim. —[[User:23PowerZ|<font color="red">★</font>P''οωερ''<font color="black"><b>Z</b></font>]]<sub><sub>[[User talk:23PowerZ|talk]]</sub></sub> 14:56, 8 June 2013 (UTC)
::*I can't really be done like that, because all of those measurements need qualifiers themselves if they weren't carried out by STP-conditions. I think we would need a new multi-dimensional data type to fully describe a chemical system with all its physical characteristics. --[[User:Tobias1984|Tobias1984]] ([[User talk:Tobias1984|talk]]) 16:03, 8 June 2013 (UTC)
::::STP is only temperature and pressure, the things being measured here. —[[User:23PowerZ|<font color="red">★</font>P''οωερ''<font color="black"><b>Z</b></font>]]<sub><sub>[[User talk:23PowerZ|talk]]</sub></sub> 16:47, 8 June 2013 (UTC)
*{{support}} - As all of thermodynamics everything should be strictly in Kelvin and Pascal. No Bars, Fahrenheit, mmHG, etc. --[[User:Tobias1984|Tobias1984]] ([[User talk:Tobias1984|talk]]) 16:03, 8 June 2013 (UTC)
*: No, unit as to be put in the original ãnd unit will be converted in the template in the client. the reason for that is to ensure a correct conversion of the unit. [[User:Snipre|Snipre]] ([[User talk:Snipre|talk]]) 17:53, 8 June 2013 (UTC)
::*To my knowledge all thermodynamic literature is metric so if somebody enters a non-metric number, that number has already been converted. So there is no way to tell if it has been converted correctly the first time around. --[[User:Tobias1984|Tobias1984]] ([[User talk:Tobias1984|talk]]) 20:35, 8 June 2013 (UTC)
*::: In organic chemistry they used a lot the calorie unit and depending the publication especially the old ones you can find formation enthalpy in kcal. [[User:Snipre|Snipre]] ([[User talk:Snipre|talk]]) 21:53, 10 June 2013 (UTC)
::::::Units are a core problem of ''number'' datatype. We should wait for the devs to create the datatype before discussing possible problems with it. —[[User:23PowerZ|<font color="red">★</font>P''οωερ''<font color="black"><b>Z</b></font>]]<sub><sub>[[User talk:23PowerZ|talk]]</sub></sub> 22:01, 10 June 2013 (UTC)
[[File:Phasendiagramm_Eis.svg|thumb|right|phase diagram of water for different ice phases (German)]]

* {{comment}} Water has eleven known triple points, so you '''have to''' group them together in one way or another (and also two critical points). —[[User:23PowerZ|<font color="red">★</font>P''οωερ''<font color="black"><b>Z</b></font>]]<sub><sub>[[User talk:23PowerZ|talk]]</sub></sub> 04:20, 10 June 2013 (UTC)
::*You're right. We could rename this property "triple-point solid-liquid-gas"? What can we do with the other triple points? --[[User:Tobias1984|Tobias1984]] ([[User talk:Tobias1984|talk]]) 15:11, 10 June 2013 (UTC)
:::*When we create a property for one of the triple points, all of them should have one, but I think that's the wrong approach since we could end up creating a property with only one use. We have items for the different phases, e.g. {{Q|1051773}} (at least for water, I don't know about other materials' phases, so we might have to create them), so something like this structure could be better:

{{Q|283}}
:''triple point <small>(item)</small>:'' [liquid, gas, solid]
::''temperature <small>(number)</small>:'' XXX K
::''pressure <small>(number)</small>:'' XXX Pa
:''triple point:'' [liquid, Ice Ih, Ice III]
::''temperature:'' XXX K
::''pressure:'' XXX Pa

We might be able to replace ''Ice Ih'', etc. by ''hexagonal'', etc. to avoid creating items, as ''Ice Ih'' is just the name of the water phase with a hexagonal crystal system. —[[User:23PowerZ|<font color="red">★</font>P''οωερ''<font color="black"><b>Z</b></font>]]<sub><sub>[[User talk:23PowerZ|talk]]</sub></sub> 18:29, 10 June 2013 (UTC)
:Not in favor of a string datatype for triple point: I agree for the idea of T and P as qualifier, but I would propose to use 3 times the property phase as qualifier each time to describe one phase of the triple point. Ex.:
:{{Q|283}}
:''phase point <small>(item)</small>:''triple point
::''temperature <small>(number)</small>:'' XXX K
::''pressure <small>(number)</small>:'' XXX Pa
::''{{P|515}} <small>(item)</small>:''solid
::''{{P|515}}  <small>(item)</small>:''vapor
::''{{P|515}}  <small>(item)</small>:''liquid   [[User:Snipre|Snipre]] ([[User talk:Snipre|talk]]) 22:07, 10 June 2013 (UTC)
;Discussion
*{{support}} - I think this is the way to go for all the other cases of triple points. The solid-liquid-gas triple point might be special enough to warrant a separate item. Also, we should create separate items for all the phases of ice. We do the same for all the minerals and there are a lot of physical statements that can go into those items. --[[User:Tobias1984|Tobias1984]] ([[User talk:Tobias1984|talk]]) 18:39, 10 June 2013 (UTC)

The way qualifiers work, Snipre's system is better. —[[User:23PowerZ|<font color="red">★</font>P''οωερ''<font color="black"><b>Z</b></font>]]<sub><sub>[[User talk:23PowerZ|talk]]</sub></sub> 22:16, 10 June 2013 (UTC)
:'''This proposal will be deleted''': this proposal is merged. [[User:Snipre|Snipre]] ([[User talk:Snipre|talk]]) 19:29, 12 June 2013 (UTC)

=== edition (2) ===
{{Property proposal
|status                 = not done
|description            = this item is used to list the editions of a book.
|infobox parameter      = 
|datatype               = string
|domain                 = mainly books, can be used for other domains
|allowed values         = 
|suggested values       =
|source                 =
|example                = ''Hamlet'' <edition> ''Edwards, Phillip, ed. 1985''
|filter                 = 
|proposed by            = [[User:Filceolaire|Filceolaire]] ([[User talk:Filceolaire|talk]])
}}
;Discussion<BR>
Alternative to 'edition' with datatype 'string' instead of 'item'. <BR>
Property is used to list editions of a book whether or not the edition has it's own item. If an edition does not have an item the qualifiers such as 'date of publication', 'place', 'language', 'title', 'subtitle' etc. can add info. <BR>
If an edition does have it's own page then qualifier 'dedicated page' can link to that page or 'edition of' can provide a reverse link. 
*<strike>{{S}}</strike> [[User:Filceolaire|Filceolaire]] ([[User talk:Filceolaire|talk]]) 20:38, 11 June 2013 (UTC)
*{{o}} If done this way it won't be possible to point to a specific edition of an item, besides there are many other fields associated with the edition that should be "packed" together (isbn, publisher, date, etc.).--[[User:Micru|Micru]] ([[User talk:Micru|talk]]) 18:14, 12 June 2013 (UTC)
I'm going to withdraw this proposal, as Micru's comment. Also we have property {{P|393}} which has string datatype and can do this. [[User:Filceolaire|Filceolaire]] ([[User talk:Filceolaire|talk]]) 08:03, 13 June 2013 (UTC)

'''This proposal will be deleted''': proposal withdrawn [[User:Snipre|Snipre]] ([[User talk:Snipre|talk]]) 08:34, 15 June 2013 (UTC)

=== edition of ===
Done as [[Property:P629]], archived. This message can be deleted in a few days once people have seen it :). --[[User:Zolo|Zolo]] ([[User talk:Zolo|talk]]) 07:49, 15 June 2013 (UTC)
=== Motto ===
{{Property proposal
|status                 = not done
|description            = phrase meant to formally summarize the general motivation or intention of a social group or organization
|infobox parameter      = "mottoeng" in [[:en:template:infobox university]]
|datatype               = monolingual text
|domain                 = organization
|allowed values         = 
|suggested values       =
|source                 = wikipedia infoboxes
|example                = {{Q|16955}} => Self-discipline and Social Commitment
|filter                 = 
|robot and gadget jobs  = 
|proposed by            = [[User:Danrok|Danrok]] ([[User talk:Danrok|talk]])
}}
:{{question}} - (1) Does a university in Bejing really have an English motto? (2) How will translations be available in monolingual-texts? --[[User:Tobias1984|Tobias1984]] ([[User talk:Tobias1984|talk]]) 16:11, 8 June 2013 (UTC)
::(1) Yes it really does, see [http://news.tsinghua.edu.cn/publish/newsen/6051/2011/20110105155557829651737/20110105155557829651737_.html University Introduction]. (2) No idea. [[User:Danrok|Danrok]] ([[User talk:Danrok|talk]]) 19:50, 8 June 2013 (UTC)

:{{comment}} there is also a similar proposal at [[Wikidata:Property_proposal/Place#Motto_.2F_Wahlspruch_.2F_Devise]]. -- [[User talk:Docu|<span style="font-size:90%;border:#000 solid 1px;padding:0;margin:0">&nbsp;<font color="#990000">D</font><font color="#339966">o</font><font color="#006699">c</font><font color="#339966">u</font>&nbsp;</span>]] <small>at</small> 20:16, 9 June 2013 (UTC)
:'''<big>This proposal will be deleted</big>''': redundant with [[Wikidata:Property_proposal/Place#Motto_.2F_Wahlspruch_.2F_Devise]]. [[User:Snipre|Snipre]] ([[User talk:Snipre|talk]]) 19:00, 10 June 2013 (UTC)
=== Years active ===
{{Property proposal
|status                 = not done
|description            = years when player was active
|infobox parameter      = "turnedpro" and "retired" in [[:en:template:Infobox tennis biography]]
|datatype               = number
|domain                 = person
|allowed values         = n/a
|suggested values       = 
|source                 = ATP/WTA/ITF websites
|example                = <Björn Becker> ''Active'' <1984–1999>
|filter                 = 
|robot and gadget jobs  = 
|proposed by            = --[[User:Stryn|Stryn]] ([[User talk:Stryn|talk]]) 16:23, 1 May 2013 (UTC)
}}
;Discussion
*{{comment}} Some Wikipedias use both, ''turnedpro'' and ''retired'' parameters (including en-wiki), and some only active parameter (e.g. 2000–2010). So I'm not sure what we should do with that, and if this is duplicate with [[Wikidata:Property_proposal/Generic#from_time_.28since.29|from time (since)]] and [[Wikidata:Property_proposal/Generic#to_time_.28until.29|to time (until)]]. --[[User:Stryn|Stryn]] ([[User talk:Stryn|talk]]) 16:23, 1 May 2013 (UTC)
* {{support}} If both years are stored in wikidata, specific infoboxes may choose to display them on the same line or not. [[User:Vinkje83|Vinkje83]] ([[User talk:Vinkje83|talk]]) 10:02, 7 May 2013 (UTC)
*{{wait}} This is better accomplished with a date datatype, and 'from/start' and 'to/end' properties will be amongst the first date properties available. [[User:Joshbaumgartner|Joshbaumgartner]] ([[User talk:Joshbaumgartner|talk]]) 10:09, 9 May 2013 (UTC)
*{{Oppose}} as "number" datatype. We should have qualifiers of "datetime" type (not available yet), or maybe a "date-interval" datatype. --<span style="font-variant:small-caps">[[User:Ricordisamoa|<span style="color:#004B70">Ricordi</span>]][[User talk:Ricordisamoa|<span style="color:#00703E">samoa</span>]]</span> 07:26, 14 May 2013 (UTC)

*{{Comment}} I think we can express this with default date-range-qualifiers (from time ... to time) on {{Property|106}} = {{Q|10833314}}.--[[User:Kompakt|Kompakt]] ([[User talk:Kompakt|talk]]) 14:24, 28 May 2013 (UTC)
:*Sounds good IMO. --[[User:Stryn|Stryn]] ([[User talk:Stryn|talk]]) 08:18, 30 May 2013 (UTC)
:'''Without any new comment this proposal will be deleted''': the trend is to use qualifers {{p|580}} and {{p|582}} and we need to use an unique system to indicate time interval for data extraction reason. [[User:Snipre|Snipre]] ([[User talk:Snipre|talk]]) 02:14, 7 June 2013 (UTC)
=== Twitter account ===
* '''Description''': Personal Twitter account 
* '''Datatype''': Monolingual text
* '''Domain''': Person, Organisation
* '''Source''': External links section in biography articles in Wikipedia
* '''Example item and value''': <Toomas Hendrik Ilves> Twitter account <IlvesToomas>
* '''Comments''': Should be verified somehow. Link in personal webpage is good, Twitter account verification is better. --[[User:Papuass|Papuass]] ([[User talk:Papuass|talk]]) 13:36, 12 March 2013 (UTC)
:{{comment}} with or without starting '@'? -- [[User:MichaelSchoenitzer|MichaelSchoenitzer]] ([[User talk:MichaelSchoenitzer|talk]]) 22:38, 13 March 2013 (UTC)
::I propose '''without''' the '@' (helps saving storage, can be automatically formatted+linked later) --<span style="font-variant:small-caps">[[User:Ricordisamoa|<span style="color:#004B70">Ricordi</span>]][[User talk:Ricordisamoa|<span style="color:#00703E">samoa</span>]]</span> 22:49, 13 March 2013 (UTC)
: {{support}} --[[User:Goldzahn|Goldzahn]] ([[User talk:Goldzahn|talk]]) 10:44, 14 March 2013 (UTC)
::{{oppose}}. This would open the door to facebook-page, google-plus-page, tumblr, myspace, and many many more. Also I dont think that such property has any relevance in say 20 years.--[[User:Svebert|Svebert]] ([[User talk:Svebert|talk]]) 15:28, 14 March 2013 (UTC)
:::What's wrong with those? It's relevant data. It doesn't matter whether our data will be relevant in 20 years, or 100000 years. [[User:Legoktm|Legoktm]] ([[User talk:Legoktm|talk]]) 15:40, 14 March 2013 (UTC)
::::If find it awkward to say Person xy has the property twitter-account=xyz. Also I do not understand why twitter and not -say- myspace. Why twitter and not any email-address--[[User:Svebert|Svebert]] ([[User talk:Svebert|talk]]) 15:50, 14 March 2013 (UTC)
:::::Propose a myspace property then. I would support that too. Email address is also a valid property, but might be harder, since people tend to keep their email address private compared to say, a twitter account. It's no less valid though. [[User:Legoktm|Legoktm]] ([[User talk:Legoktm|talk]]) 15:54, 14 March 2013 (UTC)
::::::how about ''postal address''? Or ''GPS-coordinates of the bedroom used in the month of may''?
::::::how about ''color of bed sheets'' or ''favourite car manufacturer''?
::::::how about ''length of distance to workplace in winter when streets are icy''?
::::::Why are these proposals obviously ridiculous but not “twitter account“?
::::::My hint: Nobody on earth would describe somebody with the property “twitter account“. If you are talking about a person with a friend who doesn't know this person, do you say: “This person has the twitter-account xyz”? You propably stick to the more objective properties like “This persons sex is female“, “She works at ...“, ”She is at age 36” etc.--[[User:Svebert|Svebert]] ([[User talk:Svebert|talk]]) 16:32, 14 March 2013 (UTC) 
:::::::All the stuff you said is non-notable. Twitter accounts are added to biographies in the External links section. [[User:Emijrp|Emijrp]] ([[User talk:Emijrp|talk]]) 12:31, 16 March 2013 (UTC)

:{{support}} without the "@". [[User:Legoktm|Legoktm]] ([[User talk:Legoktm|talk]]) 15:40, 14 March 2013 (UTC)

:I don't know how much this property will be relevant in 20 years, but at the moment, I feel that this information could be useful; however, including all names and codes for personal accounts will lead to '''edit wars''' (due to poor references) and '''overclaimization'''. --<span style="font-variant:small-caps">[[User:Ricordisamoa|<span style="color:#004B70">Ricordi</span>]][[User talk:Ricordisamoa|<span style="color:#00703E">samoa</span>]]</span> 16:44, 14 March 2013 (UTC)
:{{oppose}} - I do not believe Wikidata should be a repository for external links, only personal information. The problem with linking any third-party service is that these services change and some go obsolete. In addition, I fear that some living people might see this as a privacy violation (even if it technically isn't).--[[User:Jasper Deng|Jasper Deng]] ([[User talk:Jasper Deng|talk]]) 00:48, 15 March 2013 (UTC)
::This isn't a URL property, it's text. [[User:Legoktm|Legoktm]] ([[User talk:Legoktm|talk]]) 03:25, 15 March 2013 (UTC)
:{{comment}} Svebert, the intention of nominating only Twitter property was to check general response. If this is considered OK property, then "personal website", "facebook page", "cyclingarchives.com profile ID" (for professional cyclists), "national-football-teams.com profile ID" (for professional football players), "nhl.com profile ID" and lots of other useful resources could be added. Notability guidelines can be established (I think they exist for external links section). These properties are not useful for infoboxes (maybe website link is used), but they are used in most Wikipedias in external links section. These links could be gathered from Wikidata and displayed in every Wikipedia, just like the Phase 2 for infoboxes. Anyway, if property is found to be outdated (Twitter decides to shut down the service), technically it is very easy to remove all references to it. --[[User:Papuass|Papuass]] ([[User talk:Papuass|talk]]) 09:42, 15 March 2013 (UTC)
:{{oppose}} Wikidata is not a directory of personal information. This kind of information doesn't help to describe or to inform about the person. [[User:Snipre|Snipre]] ([[User talk:Snipre|talk]]) 12:21, 15 March 2013 (UTC)
*{{comment}} official website is already accepted? Why not to rename it something like "official sites" where to put every notable links, including Twitter? --[[User:Stryn|Stryn]] ([[User talk:Stryn|talk]]) 08:57, 16 March 2013 (UTC)
:{{oppose}}. Official website is accepted, due to the fact that it does not run on another platform (like Twitter or Facebook) and provides relatively formal information, whereas Twitter pages display more personal information about the entity. --[[User:Wylve|Wylve]] ([[User talk:Wylve|talk]]) 09:56, 16 March 2013 (UTC)
::{{comment}} many people/band don't have official websites, but official twitter/facebook/google+/myspace account. --[[User:Stryn|Stryn]] ([[User talk:Stryn|talk]]) 10:25, 16 March 2013 (UTC)
:::I propose not to create this property, but to use the entity's twitter profile URL as the value of the official website property only when the entity does not have an official website. Same goes to Facebook, myspace, linkedin, etc. --[[User:Wylve|Wylve]] ([[User talk:Wylve|talk]]) 06:33, 17 March 2013 (UTC)

:{{support}} [https://en.wikipedia.org/w/index.php?title=Special:WhatLinksHere/Template:Twitter&limit=500 see]. [[User:Emijrp|Emijrp]] ([[User talk:Emijrp|talk]]) 12:33, 16 March 2013 (UTC)
*I'd {{support}} an "official media" property, which could include official website and social network accounts, but also magazines, television shows, etc. But I {{oppose}} having a property for each social network. --[[User:NaBUru38|NaBUru38]] ([[User talk:NaBUru38|talk]]) 19:17, 19 March 2013 (UTC)
:{{Oppose}} per NaBUru38's reason for opposing. But something like "social media" property would be good. --[[User:Stryn|Stryn]] ([[User talk:Stryn|talk]]) 21:40, 19 March 2013 (UTC)
::It doesn't have to be a social media, it can be an old-school media like an official website, radio / television show or magazine. --[[User:NaBUru38|NaBUru38]] ([[User talk:NaBUru38|talk]]) 18:51, 20 March 2013 (UTC)
*If a person or organization has a relevant public account on a social network related to whatever it is they're notable for, I could see it making sense to have that data on Wikidata. (I'm picturing someone using Wikidata to analyze Twitter text output of all people elected to X position who also have attributes X...) However, we should specify that the account has to be relevant, though I'm not sure what criteria we would need for this. We probably wouldn't, for instance, want to list the account of someone who has a Wikidata item on account of being related to someone. This needs further consideration. --[[User:Yair rand|Yair rand]] ([[User talk:Yair rand|talk]]) 00:29, 20 March 2013 (UTC)
* {{Oppose}} Per Snipre. --[[User:Sannita|Sannita]] - <small>''[[User talk:Sannita|not just another it.wiki sysop]]''</small> 14:05, 23 March 2013 (UTC)
* {{Oppose}} Wikipedia has achieved a consensus that articles about Twitter accounts of persons/organizations are not notable for inclusion. So, how do we'd link to them from here if they don't exist and an item about those Twitter accounts cannot be created? Also, they can change of account name when they wish, so we would have to be be updating the info each and then, which will make this more trouble than benefit. And additionally, I agree with what someone said above that this would open the door to facebook-page, google-plus-page, tumblr, myspace, and many many more. — [[User:Hahc21|<font color="#333333">'''ΛΧΣ'''</font>]][[User_talk:Hahc21|<font color="#336699">'''<sup>21</sup>'''</font>]] 04:40, 26 March 2013 (UTC)
* {{comment}} Bear in mind that Wikidata is not Wikipedia. It may be that other users of Wikidata would want this information to be available. [[User:Danrok|Danrok]] ([[User talk:Danrok|talk]]) 13:06, 1 April 2013 (UTC)
* {{comment}} ΛΧΣ: there is no propositon to create items about Twitter acounts, but use them as properties instead. And I do not see much difference between this proposal and already confirmed property [[Property:P345]]. --[[User:Papuass|Papuass]] ([[User talk:Papuass|talk]]) 09:14, 2 April 2013 (UTC)
* {{Oppose}} There are many websites, many hosting websites, and many social networking websites and networks of them. IMDB is an old database (23 years); OpenStreetMap is a free database (and integrated in Wikipedia). Twitter is a microblog hosting and a social networking service that appeared in 2006 (7 years ago). It is popular, but is neither old, nor free or integrated with Wikipedia; how is it different from StatusNet, Diaspora etc., except that it always has the same domain name (which means the specific service can be inferred from the address)? Maybe create an item for blogs and social networks, and use with qualifiers: [[Wikidata:Project_chat#Property_qualifier_release_on_Wednesday]]. But what if people start adding e-mail addresses? --[[User:AVRS|AVRS]] ([[User talk:AVRS|talk]]) 18:18, 17 April 2013 (UTC)
* {{Oppose}} Many other social media and other website should be consolidated in a common attribute like member of "Twitter" then qualifier for media id.
e.g.  Eric Schmidt Q92747 => Twitter Q918, qualifier "social media address" => "ericschmidt" (string data type)
--[[User:Napoleon.tan|Napoleon.tan]] ([[User talk:Napoleon.tan|talk]]) 13:27, 30 April 2013 (UTC)
* {{support}}, as it is a widely used and very influential website. I have nothing against creating properties for social media but would oppose a general "social media" property, as it would make things substantially more complicated for no clear benefit. --[[User:Zolo|Zolo]] ([[User talk:Zolo|talk]]) 08:58, 2 May 2013 (UTC)
* {{support}} as comments above. [[User:Filceolaire|Filceolaire]] ([[User talk:Filceolaire|talk]]) 19:42, 14 May 2013 (UTC)
* {{comment}} How do we ascertain that added account is the original one and not spoof? because there are a ton of spoof accounts.--[[User:Vyom25|Vyom25]] ([[User talk:Vyom25|talk]]) 14:17, 23 May 2013 (UTC)
::Perhaps it could be verified accounts only? [[User:Danrok|Danrok]] ([[User talk:Danrok|talk]]) 21:37, 23 May 2013 (UTC)
* {{support}} Let's say, hypothetically, that I've created my own AI running off of Wikidata, and am giving it away for free as an app. (This is, of course, what we hope will eventually become one of the primary purposes of this database.) So, what is the average person talking into their smartphone more likely to ask my AI: "What's so-and-so's VIAF identifier?" or "What's so-and-so's Twitter handle?" It's all well and good that we're turning this project into a useful resource for librarians, statisticians, and what-not, but don't forget the Everyman!''' —&nbsp;[[User:PinkAmpersand|<u><font color="000">PinkAmpers</font></u>]]'''[[User talk:PinkAmpersand|'''<u><font color="FF1493">&#38;</font></u>'''<font color="000"><sup>(<u>''Je vous invite à me parler''</u>)</sup></font>]] 11:19, 30 May 2013 (UTC)
**<small>Huh. Turns out we ''had'', in fact, [//www.wikidata.org/w/index.php?title=Q13407143&action=history forgotten the Everyman]. Lol.''' —&nbsp;[[User:PinkAmpersand|<u><font color="000">PinkAmpers</font></u>]]'''[[User talk:PinkAmpersand|'''<u><font color="FF1493">&#38;</font></u>'''<font color="000"><sup>(<u>''Je vous invite à me parler''</u>)</sup></font>]] 11:24, 30 May 2013 (UTC)</small>
*{{Oppose}}, redundant to {{P|553}}. --[[User:Yair rand|Yair rand]] ([[User talk:Yair rand|talk]]) 12:28, 30 May 2013 (UTC)
----
There're already {{P|553}}. This request is archived.--[[User:GZWDer|GZWDer]] ([[User talk:GZWDer|talk]]) 03:07, 19 June 2013 (UTC)
=== together with / gemeinsam mit ===

{{Property proposal
|status=not done
|description=        Qualifier indicating that the property is shared with someone/something else
|infobox parameter=  ?
|datatype=           item
|domain=             Properties, especially people or other acteurs
|allowed values=     persons (usually)
|suggested values=
|source=             
|example=            Leonard Huxley has child Aldous Huxley ''together with'' Julia Arnold; Robert Anton Wilson authored Illuminatus ''together with'' Robert Shea; Serge Haroche got the Nobel Prize in Physics (in 2012) ''together with'' David J. Wineland.
|filter=             
|robot and gadget jobs=     
|proposed by= [[User:Duesentrieb|Duesentrieb]] ([[User talk:Duesentrieb|talk]])
}}
The ''together with'' qualifier allows an easy way to indicate that some property or relationship is shared with someone else. This is especially useful if the meaning of the relationship is influenced by it's shared nature, e.g. in the case of parentship. Note that this qualifier is not necessarily limited to people, but seems especially useful in that context. [[User:Duesentrieb|Duesentrieb]] ([[User talk:Duesentrieb|talk]]) 10:46, 25 April 2013 (UTC)
: {{question}} Is it useful to have properties/qualifiers inferable from neighbouring items? If there are exceptions, could you show an example? Thanks. --[[User:AVRS|AVRS]] ([[User talk:AVRS|talk]]) 10:56, 25 April 2013 (UTC)
:: In theory yes, but we'll not have automatic inferred parameters on Wikidata soon, and even when we do, we still need a qualifier property to represent them. I could imagine such qualifiers being added by bot, though.
:: I'm not sure what kind of example you mean... maybe, if Serge Haroche has Nobel Prize (in Physics) (in 2012), and David J. Wineland also has Nobel Prize (in Physics) (in 2012), we could infer the "together with" qualifier for that... but it already needs a bit of special knowledge to decide which qualifiers need to be taken into account for this match. 
:: Anyway, no matter whether this is going to be maintained manually, by bot, or fully automated based on rules, we need to define the property to be able to use it as a qualifier. -- [[User:Duesentrieb|Duesentrieb]] ([[User talk:Duesentrieb|talk]]) 12:30, 25 April 2013 (UTC)
: {{comment}} This should be listed as a generic property because it applies to more than just people, but also organizations or even other items: Bell ''manufactures'' the V-22 Osprey ''together with'' Boeing; Idaho ''borders'' Oregon ''together with'' Washington; B-17 Flying Fortress ''maiden flight'' was in 1935 ''together with'' Douglas DC-3; etc. [[User:Joshbaumgartner|Joshbaumgartner]] ([[User talk:Joshbaumgartner|talk]]) 09:04, 9 May 2013 (UTC)
::As far as manufacturing goes, we can already claim this kind of thing. Just list the manufacturers involved, add the qualifier {{P|518}} to indicate which parts they made. [[User:Danrok|Danrok]] ([[User talk:Danrok|talk]]) 23:29, 8 June 2013 (UTC)
:: done -- [[User:Duesentrieb|Duesentrieb]] ([[User talk:Duesentrieb|talk]]) 13:37, 21 May 2013 (UTC)
::{{o}} I'm not sure this is needed for any of your examples.
::Aldous Huxley has {{P|22}}  Leonard Huxley
::Aldous Huxley has {{P|25}} Julia Arnold.
::Illluminatus has author Robert Anton Wilson.
::Illuminatus has author Robert Shea.
::Nobel prize:
:::year: 2012
:::subject: Physics
:::winner: Serge Haroche
:::winner: David J Wineland.
::Putting one of the property items into a qualifier is relegating it to second place where it may well be missed in a search. We should just list both parties as above, giving each equal billing. [[User:Filceolaire|Filceolaire]] ([[User talk:Filceolaire|talk]]) 20:29, 6 June 2013 (UTC)
:::{{oppose}} per [[User:Filceolaire|Filceolaire]] [[User:Snipre|Snipre]] ([[User talk:Snipre|talk]]) 15:59, 8 June 2013 (UTC)
*{{oppose}} I can't see what this property would achieve which cannot already be achieved using existing properties, qualifiers, etc. [[User:Danrok|Danrok]] ([[User talk:Danrok|talk]]) 23:23, 8 June 2013 (UTC)
*{{comment}} I would like to point out that while this property can easily be derived from existing properties, for it to be derived visibly and usably within wikidata, ''it must exist''! It's redundant in the sense that the brother/sister relationships are redundant, since they are implied by a shared parent: they are redundant and can be derived, but they are non the less useful to ''have'', no matter wither they are entered explicitly, maintained by bot or derived by the system itself. I think that it is useful to be able to express the notion that some property is shared in cases where the "shared-ness" is relevant (like when having children, or sharing a prize). -- [[User:Duesentrieb|Duesentrieb]] ([[User talk:Duesentrieb|talk]]) 20:02, 10 June 2013 (UTC)
----
Consensus against. Request is archived.--[[User:GZWDer|GZWDer]] ([[User talk:GZWDer|talk]]) 03:11, 19 June 2013 (UTC)
=== together with / gemeinsam mit ===
''moved to [[Wikidata:Property_proposal/Generic#together with / gemeinsam mit]] as per [[User:Joshbaumgartner|Joshbaumgartner]]'s suggestion'' -- [[User:Duesentrieb|Duesentrieb]] ([[User talk:Duesentrieb|talk]]) 13:36, 21 May 2013 (UTC)

=== brother-in-law (spouse's brother) ===
{{Property proposal
|status=not done
|description=        [[w:Brother-in-law]]: limited to brother of spouse. Terms may vary from one language to another.
|infobox parameter=  "relatives" in [[w:Template:Infobox_person]]
|datatype=           item
|domain=             person
|allowed values=     
|suggested values=
|source=             
|example= [[Q129837]] "Amélie of Leuchtenberg" => [[Q310790]] "Miguel I of Portugal"
|filter=             
|robot and gadget jobs= Sample [[Q129837]] "Amélie of Leuchtenberg" => [[Q310790]] "Miguel I of Portugal" could be derived from 
**[[Q129837]] "Amélie of Leuchtenberg" ([[Property:P26]] "spouse" with value [[q939]] "Pedro I of Brazil")
** and  [[q939]] "Pedro I of Brazil" ([[Property:P7]] "brother" with value [[Q310790]] "Miguel I of Portugal")
|proposed by= -- [[User talk:Docu|<span style="font-size:90%;border:#000 solid 1px;padding:0;margin:0">&nbsp;<font color="#990000">D</font><font color="#339966">o</font><font color="#006699">c</font><font color="#339966">u</font>&nbsp;</span>]] <small>at</small> 10:49, 25 April 2013 (UTC), edited 10:54, 25 April 2013 (UTC)
}}
Isn't this redundant since this data is already stored with [[Property:P7]] in the spouse's item? —[[User:23PowerZ|<font color="red">★</font>P''οωερ''<font color="black"><b>Z</b></font>]]<sub><sub>[[User talk:23PowerZ|talk]]</sub></sub> 13:11, 25 April 2013 (UTC)
:No, usually there is no separate item for the spouse, but there may still be a brother-in-law with an item. -- [[User talk:Docu|<span style="font-size:90%;border:#000 solid 1px;padding:0;margin:0">&nbsp;<font color="#990000">D</font><font color="#339966">o</font><font color="#006699">c</font><font color="#339966">u</font>&nbsp;</span>]] <small>at</small> 14:54, 25 April 2013 (UTC)
::[[Wikidata:Notability]]: "An item is acceptable [...] if it fulfils at least one of these two goals: [...] 3. It fulfils some structural need, i.e. it is needed to make statements made in other items more useful." If there is a relevant brother-in-law, wife becomes relevant. —[[User:23PowerZ|<font color="red">★</font>P''οωερ''<font color="black"><b>Z</b></font>]]<sub><sub>[[User talk:23PowerZ|talk]]</sub></sub> 14:59, 25 April 2013 (UTC)
:{{Oppose}}, per 23PowerZ. --[[User:Yair rand|Yair rand]] ([[User talk:Yair rand|talk]]) 16:14, 25 April 2013 (UTC)
:{{comment}} What if sources only say "X is Y's brother-in-law" and nothing more? In this case we even don't know what "brother-in-law" means, should we use "brother-in-law (sister's husband)" or "brother-in-law (spouse's brother)"? --[[User:Stevenliuyi|Stevenliuyi]] ([[User talk:Stevenliuyi|talk]]) 17:37, 25 April 2013 (UTC)
{{Comment}} I proposed merging [[P:P7]] (brother) and [[P:P9]] (sister) at [[Wikidata:Project_chat#Merging_Property:P7_and_Property:P9|Wikidata:Project chat]]. [[User:Izno]] pointed out to me quite well the current family relationship system is a mess. So I created [[User:23PowerZ/Stuff]] for a more general discussion. —[[User:23PowerZ|<font color="red">★</font>P''οωερ''<font color="black"><b>Z</b></font>]]<sub><sub>[[User talk:23PowerZ|talk]]</sub></sub> 02:59, 26 April 2013 (UTC)
:{{Oppose}} [[User:Snipre|Snipre]] ([[User talk:Snipre|talk]]) 17:24, 21 May 2013 (UTC)
----
Consensus against. Request is archived.--[[User:GZWDer|GZWDer]] ([[User talk:GZWDer|talk]]) 03:14, 19 June 2013 (UTC)

=== Nephew (en) / Neffe (de)/ Neveu (fr)===
{{Property proposal
|status                 = not done
|description            = a nephew is the son of an uncle's brother or sister
|infobox parameter      = 
|datatype               = item
|domain                 = person
|allowed values         = [[Property:P29]] and [[Property:P139]]
|suggested values       = 
|source                 = 
|example                = Sample: [[Q2572655]] => [[Q211411]]
|filter                 = 
|robot and gadget jobs  = 
|proposed by            = [[User:Alexander Doria|Alexander Doria]] ([[User talk:Alexander Doria|talk]]) 22:11, 30 May 2013 (UTC)
}}
;Discussion
Apparently this has never been proposed. If the property is already on its way, please revert… Btw, ''niece'' would be helpful as well. [[User:Alexander Doria|Alexander Doria]] ([[User talk:Alexander Doria|talk]]) 22:11, 30 May 2013 (UTC)
*{{oppose}} per [[Wikidata:Requests for comment/Kinship]]. —[[User:23PowerZ|<font color="red">★</font>P''οωερ''<font color="black"><b>Z</b></font>]]<sub><sub>[[User talk:23PowerZ|talk]]</sub></sub> 22:47, 30 May 2013 (UTC)
*{{oppose}}, redundant. See also: [[Wikidata:Properties for deletion#Property:P29 + Property:P139]]. [[User:Mushroom|Mushroom]] ([[User talk:Mushroom|talk]]) 12:32, 4 June 2013 (UTC)
*{{Oppose}}, per above. --<span style="font-variant:small-caps">[[User:Ricordisamoa|<span style="color:#004B70">Ricordi</span>]][[User talk:Ricordisamoa|<span style="color:#00703E">samoa</span>]]</span> 13:32, 4 June 2013 (UTC)
*{{Oppose}}. --[[User:Yair rand|Yair rand]] ([[User talk:Yair rand|talk]]) 19:18, 10 June 2013 (UTC)

----
Consensus against. Request is archived.--[[User:GZWDer|GZWDer]] ([[User talk:GZWDer|talk]]) 03:14, 19 June 2013 (UTC)

=== BPN (en) ===
{{Property proposal
|status                 = 651
|description            = Person number from Dutch Biography Portal "Biografisch Portaal" database
|infobox parameter      = Sample: "BPN" in [[:en:template:Authority control]]
|datatype               = string
|domain                 = person
|allowed values         = 
|suggested values       = 99999999
|source                 = http://www.biografischportaal.nl
|example                = example item and/or example value (please add one or several sample uses of the property. Sample: [[Q2929721]] => [[Q1868372]]  [http://www.biografischportaal.nl/persoon/55199730 BPN:55199730]
|filter                 = 
|robot and gadget jobs  = This property can be filled by bot from the English Wikipedia or Wikimedia Commons. The data is stored in the Authority Control template
|proposed by            = [[User:Jane023|Jane023]] ([[User talk:Jane023|talk]]) 19:01, 3 June 2013 (UTC)
}}
;Discussion
:{{Support}} --<span style="font-variant:small-caps">[[User:Ricordisamoa|<span style="color:#004B70">Ricordi</span>]][[User talk:Ricordisamoa|<span style="color:#00703E">samoa</span>]]</span> 02:35, 17 June 2013 (UTC)

=== RKD artists (en) ===
{{Property proposal
|status                 = 650
|description            = ID of a person in the RKDartists database
|infobox parameter      = 
|datatype               = string
|domain                 = artists, mostly Dutch
|allowed values         = 
|suggested values       = 
|source                 = 
|example                = {{Q|5598}} -> [http://www.rkd.nl/rkddb/dispatcher.aspx?action=search&database=ChoiceArtists&search=priref=66219 66219]
|filter                 = 
|robot and gadget jobs  = 
|proposed by            = [[User:Zolo|Zolo]] ([[User talk:Zolo|talk]]) 06:34, 5 June 2013 (UTC)
}}
;Discussion
We already have {{P|350}}, also by {{Q|758610}}, for objects but there is a different database for people, and I do not think it is possible to use the same property to generate external links. --[[User:Zolo|Zolo]] ([[User talk:Zolo|talk]]) 06:34, 5 June 2013 (UTC)

{{support}} [[User:Jane023|Jane023]] ([[User talk:Jane023|talk]]) 08:08, 19 June 2013 (UTC)



=== NRHP reference number (en) ===
{{Property proposal
|status                 = 649
|description            = National Register of Historic Places reference number assigned by the National Park Service of the USA.
|infobox parameter      = "refnum" in [[:en:template:Infobox NRHP]]
|datatype               = string
|domain                 = items about places that are on the {{Q|3719}}. At the moment that is 87.450 items.
|allowed values         = A string of 8 decimals.
|suggested values       = 81000382
|source                 = [[:en:NRHP]]
|example                = {{Q|172822}} -> 81000382. {{Q|9188}} -> 82001192
|filter                 = 8 digit number
|robot and gadget jobs  = The value is unique. Probably more in the future. This property is very similar to {{P|359}}
|proposed by            = [[User:Multichill|Multichill]] ([[User talk:Multichill|talk]]) 15:47, 15 June 2013 (UTC)
}}
;Discussion
:{{Support}} --<span style="font-variant:small-caps">[[User:Ricordisamoa|<span style="color:#004B70">Ricordi</span>]][[User talk:Ricordisamoa|<span style="color:#00703E">samoa</span>]]</span> 02:33, 17 June 2013 (UTC)
:{{support}}--[[User:Zolo|Zolo]] ([[User talk:Zolo|talk]]) 08:44, 17 June 2013 (UTC)
:{{support}} [[User:Jane023|Jane023]] ([[User talk:Jane023|talk]]) 08:07, 19 June 2013 (UTC)

=== UNII ===
{{Property proposal
|status                 = 652
|description            = {{q|6593799}}:  UNique Ingredient Identifier (UNII) is a non-proprietary, free, unique, unambiguous, non-semantic, alphanumeric identifier linked to a substance's molecular structure and/or descriptive information by the Substance Registration System of the Food and Drug Administration (FDA)
|infobox parameter      = {{q|6033882}} UNII, {{Q|52426}} UNII
|datatype               = string
|domain                 = term
|allowed values         = 
|suggested values       = 
|source                 =
|example                = {{q|132621}} = "YKH834O4BH ", {{q|1318776}} = "3XMK78S47O", {{q|43656}} = "97C5T2UQ7J"
|filter                 = 
|robot and gadget jobs  = Gather data from infoboxes and website.
|proposed by            = --[[User:Tobias1984|Tobias1984]] ([[User talk:Tobias1984|talk]]) 06:49, 4 June 2013 (UTC)
}}
{{support}} identifier of FDA. [[User:Snipre|Snipre]] ([[User talk:Snipre|talk]]) 23:44, 4 June 2013 (UTC)
:{{support}} --[[User:Kaligula|Kaligula]] ([[User talk:Kaligula|talk]]) 07:06, 19 June 2013 (UTC)

=== PubMed Health ===
{{Property proposal
|status                 = 653
|description            = PubMed Health provides information for consumers and clinicians on prevention and treatment of diseases and conditions. PubMed Health is a service provided by the National Center for Biotechnology Information (NCBI) at the U.S. National Library of Medicine (NLM).
|infobox parameter      = Not yet, but would be included in the diseases infobox
|datatype               = string
|domain                 = term
|allowed values         = 
|suggested values       = 
|source                 = http://www.ncbi.nlm.nih.gov/pubmedhealth/
|example                = {{Q|12152}} = "0001246", {{q|2840}} = "0001144"
|filter                 = Constraint number of digits
|robot and gadget jobs  = Gather data from infobox
|proposed by            = --[[User:Tobias1984|Tobias1984]] ([[User talk:Tobias1984|talk]]) 12:16, 6 June 2013 (UTC)
}}
;Discussion
:{{support}} [[User:Peter.C|Peter.C]] ([[User talk:Peter.C|talk]]) 20:53, 15 June 2013 (UTC)
:: {{support}} --[[User:Gambo7|Gambo7]] ([[User talk:Gambo7|talk]]) 20:43, 16 June 2013 (UTC)
:{{support}} --[[User:Kaligula|Kaligula]] ([[User talk:Kaligula|talk]]) 06:59, 19 June 2013 (UTC)

=== Coordination / coordinación / Koordination /coordinazione ===
* '''Description''': coordination parameters which can be used in infoboxs or [[:en:template:coord|coord template]] or [[:en:Template:Location map|Location map Template]]
* '''Datatype''':Geographical coordinate
* '''Links''': [[:en:template:Infobox settlement]]
* '''sources''': we can extract these variables by bots or manually form wikipedia infoboxs or websites like google map or coordination datacenters like openstreet maps and etc.
* '''Infobox parameter example:'''[[:en:Atlanta]] or [[:en:berlin]]
* '''Comments:''' I suggest to make separate property for these variables. I tried to collect the vaital variabel and we can descusss for others like (map_alt ,map_caption ,pushpin_map ,pushpin_label_position,pushpin_map_alt,pushpin_map_caption,coor_pinpoint,coordinates_type,coordinates_display,coordinates_footnotes,coordinates_region) in another requests 
; Essential parameters for degree base coordination
*'''latd''' :latitude degree (Datatype:Number)
*'''latm''' :latitude minute (Datatype:Number)
*'''lats''' :latitude second (Datatype:Number)
*'''longd''' :longitude degree (Datatype:Number)
*'''longm''' :longitud minute (Datatype:Number)
*'''longs''' :longitud second (Datatype:Number)

*'''latNS''' :latitude direction (North or South) (Datatype:String)
*'''longEW''' :longitud  direction (East or West) (Datatype:String)

; Essential parameters for radian base coordination
*'''latitude''': latitude in radian
*'''longitude''':longitude in radian

-[[User:Yamaha5|Yamaha5]] ([[User talk:Yamaha5|talk]]) 17:43, 28 March 2013 (UTC)
::We should use the "{{int:datatypes-type-geo-coordinate}}" datatype instead. --<span style="font-variant:small-caps">[[User:Ricordisamoa|<span style="color:#004B70">Ricordi</span>]][[User talk:Ricordisamoa|<span style="color:#00703E">samoa</span>]]</span> 18:58, 28 March 2013 (UTC)

::{{done}}[[User:Yamaha5|Yamaha5]] ([[User talk:Yamaha5|talk]]) 08:55, 29 March 2013 (UTC)

:{{comment}} Data entry with UTM would be a lot easier in my opinion. Two numbers instead of a lot of special characters (",',°) or multiple fields. The other values can be easily calculated from UTM. --[[User:Tobias1984|Tobias1984]] ([[User talk:Tobias1984|talk]]) 10:41, 17 April 2013 (UTC)
::"easily calculated". Well, the more technical solutions you add to this system, the fewer users will be able to use it. The threshold will be higher and higher. In some project, there is maybe only a few users with such technical skills, and they become fatigued by all requests from other users. This ''is'' simple to calculate, for those who know. More people think they know, but don't. There will be problems if a project only has the latter kind of "technically skilled" users. -- [[User:Lavallen|Lavallen]] ([[Special:Block/Lavallen|block]]) 14:22, 18 April 2013 (UTC)
:::I think data entry will be possible in any format. But for storage a UTM number like ''23423432'' is a lot simpler than ''34:234'34"32'' in my opinion. I also can't do the calculations in my head :) but there are a lot of converters on the internet and programs like google earth allow you to switch from one format to the other. I guess my comment was more about that UTM was still missing from the list ;). --[[User:Tobias1984|Tobias1984]] ([[User talk:Tobias1984|talk]]) 14:32, 18 April 2013 (UTC)
::::I'm full agree with Tobias1984, there is no need storing six entries instead of two. I really think that these entries will mostly be imported from Wikipedia using Bots (like [[User:Geobot]]) and so there is no problems about having homogeneity in the database. I really think that is better to have one standard in a database (simplify the reuses). Beside if we multiply the entries we increase the number of typos. [[User:Otourly|Otourly]] ([[User talk:Otourly|talk]]) 16:26, 22 April 2013 (UTC)
::::::~{{comment}} There is no need to to discuss the format here. That's up to the developers. --[[User:Zolo|Zolo]] ([[User talk:Zolo|talk]]) 16:35, 22 April 2013 (UTC)
----
Coordination datatype is supported. move to archive.--[[User:GZWDer|GZWDer]] ([[User talk:GZWDer|talk]]) 10:10, 20 June 2013 (UTC)

=== date retrieved (proposal #2) (en) ===
{{Property proposal
|status                 = not done
|description            = date that a website or online database which is used as a reference for a claim is accessed
|infobox parameter      = None. '''Template parameter:''' "accessdate" in citation templates (the "Cite xxx" series) at the English Wikipedia.
|datatype               = time
|domain                 = Part of statement references. Not to be used in claims or qualifiers.
|allowed values         = dates
|suggested values       = 
|source                 = na
|example                = Source for some statement: {{P|248}}: some database; ''date retreived'': June 9, 2013.
|filter                 = 
|robot and gadget jobs  = 
|proposed by            = [[User:Byrial|Byrial]] ([[User talk:Byrial|talk]]) 07:48, 9 June 2013 (UTC)
}}
;Discussion
'''Relation to other properties:'''
* {{P|577}}: Use P577 if the accessed webpage states a date of publication (either instead of this property or together with it).
* {{P|585}}: "date retrieved" is redundant as P585 could easily serve this way for references. But some Wikidatans have expressed that they want a separate property for use in references to avoid any possible confusion even though that qualifiers and references are distinct things in a statement. [[User:Byrial|Byrial]] ([[User talk:Byrial|talk]]) 07:48, 9 June 2013 (UTC)

*{{Neutral}} – I see no need for another redundant property, but if the community prefers that, I can live with it without problems. However they should know what they do, and the property should have a description that makes sense. What's why I made this alternative proposal for a "date retrieved" property. [[User:Byrial|Byrial]] ([[User talk:Byrial|talk]]) 07:48, 9 June 2013 (UTC)

*{{support}}, I think it is what was meant by the previous proposal, but I can only support a more precise terminology. --[[User:Zolo|Zolo]] ([[User talk:Zolo|talk]]) 21:30, 9 June 2013 (UTC)
*{{comment}} previous proposal amended as this wording. [[User:Filceolaire|Filceolaire]] ([[User talk:Filceolaire|talk]]) 22:22, 9 June 2013 (UTC)
:: The previous proposal is better now than before, but it still uses the word qualifier which is misleading and contrary to Wikidata's datamodel. And the motivation talks about a need. There is no need. It would be better to motivate a wish for a redundant property than to deny the redundancy. So I will keep this alternative proposal for now. [[User:Byrial|Byrial]] ([[User talk:Byrial|talk]]) 06:21, 10 June 2013 (UTC)
:::AH. I missed your wording for the infobox parameter section. Your wording is better and I would like to merge into the proposal above. [[User:Filceolaire|Filceolaire]] ([[User talk:Filceolaire|talk]]) 18:15, 10 June 2013 (UTC)
:::: Please do! Also under "Robot and gadget jobs" and in the motivation you call it a qualifier. [[User:Byrial|Byrial]] ([[User talk:Byrial|talk]]) 18:51, 10 June 2013 (UTC)
* '''This proposal is hereby withdrawn by the proposer''' – The proposal above for the same property have been changed so the two proposals are now nearly identical, and there is no reason to keep this proposal anymore. [[User:Byrial|Byrial]] ([[User talk:Byrial|talk]]) 08:35, 12 June 2013 (UTC)

=== <s>year (en)</s> ===
{{Property proposal
|status                 = not done
|description            = Some magazines distinguish a specific issue by "issue x of the YEAR xxxx" rather than "volume xx issue x". ( Very common for Chinese journals and general magazines)
|infobox parameter      = 
|datatype               = String
|domain                 = 
|allowed values         = 
|suggested values       = 
|source                 = 
|example                = 
|filter                 = 4 digits
|robot and gadget jobs  = 
|proposed by            = [[User:Li3939108|<span style="font-family:sans-serif;">凡其</span>]][[User talk:Li3939108|<span style="font-family:sans-serif;"><sub>Fanchy</sub></span>]] 15:14, 6 June 2013 (UTC)
}}
;Discussion
"year" and "volume" shouldn't coexist. If there are "year" and "volume" for a specific "issue" of a magazine, use the "volume" and record the "year" ( and possible more detailed month, day) on "date of publication". --[[User:Li3939108|<span style="font-family:sans-serif;">凡其</span>]][[User talk:Li3939108|<span style="font-family:sans-serif;"><sub>Fanchy</sub></span>]] 15:14, 6 June 2013 (UTC)

Or the meaning of "volume" need to be extended to "volume number". These magazines in fact regard the "year" as "volume number" to distinguish "issues". In this way the "volume" could be 1999, 2000, 2001 ... rather than 1, 2, 3, ... --[[User:Li3939108|<span style="font-family:sans-serif;">凡其</span>]][[User talk:Li3939108|<span style="font-family:sans-serif;"><sub>Fanchy</sub></span>]] 15:55, 6 June 2013 (UTC)
:{{oppose}} extend the concept of volume and use this property with the year as value. [[User:Snipre|Snipre]] ([[User talk:Snipre|talk]]) 02:00, 7 June 2013 (UTC)
::OK, don't create this property  and  it is better to add a claim <volume> "no value" for magazines not using volume and a claim <volume> "unknown value" when you don't know the volume. --[[User:Li3939108|<span style="font-family:sans-serif;">凡其</span>]][[User talk:Li3939108|<span style="font-family:sans-serif;"><sub>Fanchy</sub></span>]] 09:07, 7 June 2013 (UTC)

=== Subdivisions /  /  ===
* '''Description''': Number of subdivisions of varios types (neigborhoods for municipalities)
* '''Datatype''': value, item
* '''Links''':
* '''Infobox parameter example:'''
* '''Comments:'''  In Czech republic every municipality have in infobox numbers of three types of subdivisions (villages, cadastral areas and statistical parts (often are all similar)), might be with links too.
**{{oppose}}, this can be derived from [[P:P131]] and [[P:P150]]. --[[User:NaBUru38|NaBUru38]] ([[User talk:NaBUru38|talk]]) 20:01, 27 March 2013 (UTC)
**{{oppose}} per [[User:NaBUru38|NaBUru38]] [[User:Snipre|Snipre]] ([[User talk:Snipre|talk]]) 19:09, 10 June 2013 (UTC)

----
Consensus against. Request is archived.--[[User:GZWDer|GZWDer]] ([[User talk:GZWDer|talk]]) 12:29, 21 June 2013 (UTC)

=== Historical land /  /  ===
* '''Description''': Historical subdivision of state
* '''Datatype''': item
* '''Links''': [[Q45551]]
* '''Infobox parameter example:'''
* '''Comments:'''
::Shouldn't this just be the standard (Administrative division) item with (From date) and (To date) properties. [[User:Filceolaire|Filceolaire]] ([[User talk:Filceolaire|talk]]) 00:40, 25 February 2013 (UTC)
:::Agree with Filceolaire. --[[User:NaBUru38|NaBUru38]] ([[User talk:NaBUru38|talk]]) 20:02, 27 March 2013 (UTC)
:{{Oppose}} This is covered by [[P:P150]] though appropriate qualification properties may need to be developed. [[User:Joshbaumgartner|Joshbaumgartner]] ([[User talk:Joshbaumgartner|talk]])
----
Consensus against. Request is archived.--[[User:GZWDer|GZWDer]] ([[User talk:GZWDer|talk]]) 12:29, 21 June 2013 (UTC)

====Administrative center====
*'''Description''': Administrative center
*'''Datatype''': StringValue
*'''Links''': 
*'''Infobox parameter example:'''
* '''Comments:''' useful for the divisions which have a seat which is specifically ''not'' referred to as "capital" (e.g., in Russia). Alternatively, we might combine the [[Property:P36|capital]] property with this into a generic "seat" and create another property called "seat type".—[[User:Ezhiki|Ëzhiki (Igels Hérissonovich Ïzhakoff-Amursky)]]&nbsp;•&nbsp;([[User talk:Ezhiki|yo?]]); March&nbsp;8, 2013; 19:56 (UTC)
: Could you give an example of this kind of seat? --[[User:Stevenliuyi|Stevenliuyi]] ([[User talk:Stevenliuyi|talk]]) 20:11, 8 March 2013 (UTC)
::The city of [[:en:Ufa|Ufa]] is the capital of the [[:en:Republic of Bashkortostan|Republic of Bashkortostan]] and the administrative center of [[:en:Ufimsky District|Ufimsky District]]. In general, only the [[:en:republics of Russia|republics of Russia]] have capitals; all other entities only have administrative centers: [[:en:Vladivostok|Vladivostok]], for example, is the administrative center of [[:en:Primorsky Krai|Primorsky Krai]]; it is incorrect to call it its "capital".—[[User:Ezhiki|Ëzhiki (Igels Hérissonovich Ïzhakoff-Amursky)]]&nbsp;•&nbsp;([[User talk:Ezhiki|yo?]]); March&nbsp;8, 2013; 20:28 (UTC)
::: Thanks for the example. I prefer a generic property, because otherwise we may also need properties like "county seat" for US, "county town" for UK, "chef-lieu" for various countries, and many more properties for many different kinds of seats of government in different countries. --[[User:Stevenliuyi|Stevenliuyi]] ([[User talk:Stevenliuyi|talk]]) 21:20, 8 March 2013 (UTC)
::::Well, the intent of my example was more to illustrate that there are cases where one generic moniker is not going to work because multiple terms are used within the context of the same infobox (as opposed to within the context of different countries). I feel that the best solution is to have both a "seat type" and a "seat" property; this way one can be easily customize for any country. But while that's unavailable, creating a generic property (be it called "seat" or "administrative center", but definitely not "capital") and allowing it to hold multiple values is probably the best solution.—[[User:Ezhiki|Ëzhiki (Igels Hérissonovich Ïzhakoff-Amursky)]]&nbsp;•&nbsp;([[User talk:Ezhiki|yo?]]); March&nbsp;8, 2013; 21:30 (UTC)
:::::I agree that we need to specify the "seat type" if we use a generic "seat" property (I have no idea how we should call it), but I think it's better to let the "seat type" be a qualifier (when it's available) of the "seat" property, instead of creating two separate properties. --[[User:Stevenliuyi|Stevenliuyi]] ([[User talk:Stevenliuyi|talk]]) 22:02, 8 March 2013 (UTC)
::::::I, too, agree that it'd better be a qualifier... it's just that we don't know when those are going to be implemented! By the looks of it Phase II might very well go live before that happens... Cheers,—[[User:Ezhiki|Ëzhiki (Igels Hérissonovich Ïzhakoff-Amursky)]]&nbsp;•&nbsp;([[User talk:Ezhiki|yo?]]); March&nbsp;8, 2013; 22:21 (UTC)
:::::::Sure. I have no problem with creating a temporary "seat type" property, since it's easy for bots to transfer the data when qualifiers are available. --[[User:Stevenliuyi|Stevenliuyi]] ([[User talk:Stevenliuyi|talk]]) 22:35, 8 March 2013 (UTC)
: {{oppose}} I would prefer that the existing [[P:P36|capital]] cover this.  While the exact name 'capital' may not be fully accurate itself in all situations, the description provides coverage for administrative seats.  If the label is the problem, then it should be altered to broaden its coverage.  If we have a different property for every different local way of considering its seat, it will be messy and hard to use for clients.  The label we use won't matter to the template querying it, as client-side, an appropriate title can be provided. If it is really notable, a qualifier can be used to give the official 'title' of the seat. [[User:Joshbaumgartner|Joshbaumgartner]] ([[User talk:Joshbaumgartner|talk]]) 06:06, 16 May 2013 (UTC)
:: I would support relabelling P36 to "administrative seat". I think {{P|31}} can be used for "type of seat". --[[User:Zolo|Zolo]] ([[User talk:Zolo|talk]]) 07:39, 16 May 2013 (UTC)
:{{Oppose}} We have [[Property:P36|capital]] property, which description says that it can be seat of government of state or ''administrative division''.--[[User:Ahonc|Ahonc]] ([[User talk:Ahonc|talk]]) 11:31, 17 May 2013 (UTC)

----
Consensus against. Request is archived.--[[User:GZWDer|GZWDer]] ([[User talk:GZWDer|talk]]) 12:30, 21 June 2013 (UTC)


==== [[Q333634|Translator / Übersetzer  / Traducteur]] ====
{{Property proposal
|status                 = 655
|description            = Translator of the book
|infobox parameter      = 
|datatype               = Item
|domain                 = 
|allowed values         = 
|source                 = 
|example                = 
|robot and gadget jobs  = 
|proposed by            = [[User:Tpt|Tpt]] ([[User talk:Tpt|talk]]) 20:20, 31 January 2013 (UTC)
}}
===== Discussion about the property "Translator" ===== 
*{{support}} I think the role of translator is usually quite clear in any work and having a property "Translator" will convey useful information. Another option could be "secondary author", but in a work with several "secondary authors", then it would be unclear which one took the role of translator.--[[User:Micru|Micru]] ([[User talk:Micru|talk]]) 19:46, 2 June 2013 (UTC)
:*{{support}}, if we do not have this property, we can use qualifiers. I think {{P|170}} XX <small>{{P|518}}: {{Q|7553}}</small> would be technically correct, though perhaps a bit odd. But I "translator" is such a customary role, that I think it deserves it own property, just like author, illustrator, etc. --[[User:Zolo|Zolo]] ([[User talk:Zolo|talk]]) 20:06, 2 June 2013 (UTC)
*{{support}} --[[User:Stevenliuyi|Stevenliuyi]] ([[User talk:Stevenliuyi|talk]]) 20:34, 5 June 2013 (UTC)
*I don't quite understand how this property would be used. Could someone give an example? --[[User:Yair rand|Yair rand]] ([[User talk:Yair rand|talk]]) 10:40, 6 June 2013 (UTC)
:* According to [[Wikidata:Books task force]], "translator" is an "edition item property" instead of "work item property", so I think this property would only be used for specific editions. --[[User:Stevenliuyi|Stevenliuyi]] ([[User talk:Stevenliuyi|talk]]) 11:46, 6 June 2013 (UTC)
:* Stevenliuyi is right, for instance let's take this item: {{Q|3793400}}. It represents a work written by Jonas Jonasson in Swedish language. This book has different editions, some of them are in Swedish, some of them in other languages, including English. Usually there is a person called "translator" that takes the responsibility of translating from one language into another. So for that general item there will be linked items for each edition, the item representing the Chinese edition will have as translator "Zhaoyan Fan", the item representing the English edition will have as translator "Rod Bradbury", for the Italian edition the translator is "Margherita Podestà Heir". Later on, each language Wikipedia will use in their book infobox the main work item (containing the author, title, etc), and the edition item (containing the details regarding the translated edition, like ISBN, publisher, and the translator) so the readers have all the information that it is relevant in their language. Hopefully now it is more clear how important this property is.--[[User:Micru|Micru]] ([[User talk:Micru|talk]]) 15:57, 6 June 2013 (UTC)

===== Discussion on translations ===== 
The following discussion has been archived for the following reasons: translations will be stored as a separate item (see: [[Wikidata:Requests_for_comment/References_and_sources#Simple_guidelines_for_sources|guidelines for sources]]). In the light of this new circumstances I will ask the participants to share their opinion again on this property.--[[User:Micru|Micru]] ([[User talk:Micru|talk]]) 19:46, 2 June 2013 (UTC)
*{{S}} this property is needed however the details of the translated edition are stored. [[User:Filceolaire|Filceolaire]] ([[User talk:Filceolaire|talk]]) 08:21, 13 June 2013 (UTC)



{{ctop|Archived discussion (relative to the separation of items)|width=100%}}
:The can be done two ways. For instance, either as a property of the original work:
:* QXX Hamlet, a play by Shakespeare. Property: French translator, François Victor Hugo (1865), Yves Bonnefoy (1958)
:or in a separate item:
:* QXY Hamlet, translation of Shakespeare's play by François-Victor Hugo.
:The latter sounds better to me, as it will be easier to add properies about the translation itself (date, publisher, isbn, etc.) --[[User:Zolo|Zolo]] ([[User talk:Zolo|talk]]) 07:57, 3 February 2013 (UTC)
:: +1. I favor a separate item for the edition. --[[User:Kolja21|Kolja21]] ([[User talk:Kolja21|talk]]) 22:18, 3 February 2013 (UTC)
::This is important (see my '''Comments III''' above), because as I understand it we are confusing different levels. If we are willing to have a wikidata page per ''work'' (eg. Hamlet), we need to set all the properties minding all the manifestations and expressions of that work (plays, books, translations movies). We we prefer to have different Wikidata pages (Hamlet the play, Hamlet the movie(s), etc.) we'll have other properties (or, at least, same properties with different syntaxes, I suppose). Furthermore, if we set the Translator property like this we should be coherent for all the other properties. 
::We could actually have [[:w:FRBR]] properties ''isWork, isManifestation, isExpression''... --[[User:Aubrey|Aubrey]] ([[User talk:Aubrey|talk]]) 09:45, 19 February 2013 (UTC)
::Anyway, {{support}} for the latter form also for me, it's easier and more wiki-like to have different items/pages. We just need a way (ie properties) to link these pages together. --[[User:Aubrey|Aubrey]] ([[User talk:Aubrey|talk]]) 09:45, 19 February 2013 (UTC)
:::Am I blind ? I see a "Translator" for a book, but where is the "Author" property ? --[[User:Hsarrazin|Hsarrazin]] ([[User talk:Hsarrazin|talk]]) 21:10, 7 March 2013 (UTC)
::::{{p|50}}--[[User:Micru|Micru]] ([[User talk:Micru|talk]]) 19:46, 2 June 2013 (UTC)
:Creating a separate item for each translation will, I believe, put Wikidata out of synch with WikiPedia for no good reason since we can deal with this by having a statement for each translation, just as we have for each edition. Translator would be a qualifier for the statement describing the translation. [[User:Filceolaire|Filceolaire]] ([[User talk:Filceolaire|talk]]) 11:56, 6 April 2013 (UTC)
::Separate items for translations raises some issues, but I think it is a better long-term solution. An important usecase would be [[:en:Template:Cite book]]. If we have an item for each edition, we would just need the item's ID to cite it. By contrast, if several editions are listed in the same property of the same items, choosing the right one would be much more complicated and brittle. I think a similar case could be made for other uses, both by Wikipedias or external clients. --[[User:Zolo|Zolo]] ([[User talk:Zolo|talk]]) 12:24, 6 April 2013 (UTC)
{{cbot}}

=== RefSeq ===
{{Property proposal
|status                 = 656
|description            = Specify Refernce Sequence identifier for the Protein and RNA. This will used as a '''qualifier''' to {{p|637}} &{{p|639}}
|infobox parameter      = [[:en:Template:GNF_Protein_box]] ---->  RefSeq(mRNA) & RefSeq(Protein)
|datatype               = string
|domain                 = term
|allowed values         = 
|suggested values       = 
|source                 = http://www.ncbi.nlm.nih.gov/
|example                = [[Q414043|Reelin]] --> RefSeq(mRNA) = NM_005045  &  RefSeq(Protein) = NM_011261
|filter                 = 
|robot and gadget jobs  = Fill gene wiki items with correct Reference Sequence 
|proposed by            = [[User:Chinmay26|Chinmay26]] ([[User talk:Chinmay26|talk]])
}}
:{{support}} part of protein infobox and important for a GSoC project. --[[User:Tobias1984|Tobias1984]] ([[User talk:Tobias1984|talk]]) 15:13, 18 June 2013 (UTC)
:{{support}} [[User:Andrew Su|Andrew Su]] ([[User talk:Andrew Su|talk]]) 17:48, 21 June 2013 (UTC)
{{done}} --[[User:Tobias1984|Tobias1984]] ([[User talk:Tobias1984|talk]]) 09:54, 22 June 2013 (UTC)

=== GenLoc_chr ===
{{Property proposal
|status                 = 643
|description            = Specifies the database chapter of the gene in UCSC Genome Informatics website.
|infobox parameter      = [[:en:Template:GNF_Protein_box]] = GenLoc_chr
|datatype               = Number
|domain                 = term
|allowed values         = 
|suggested values       = 
|source                 = http://genome.ucsc.edu/
|example                = [[Q414043|Reelin]] = 7
|filter                 = Only Numbers. Number of digits may be constrained within specific range
|robot and gadget jobs  = Fill gene wikidata items with correct Database chapter
|proposed by            = [[User:Chinmay26|Chinmay26]] ([[User talk:Chinmay26|talk]]) 20:30, 10 June 2013 (UTC)
}}
;Discussion
:*{{support}} -- though we also need to allow "X" and "Y" chromosomes. [[User:Andrew Su|Andrew Su]] ([[User talk:Andrew Su|talk]]) 21:47, 10 June 2013 (UTC)
:*{{support}} - Can we handle the x and y chromosome as a qualifier? Best to propose them together. --[[User:Tobias1984|Tobias1984]] ([[User talk:Tobias1984|talk]]) 19:46, 13 June 2013 (UTC)
::*And is also needs the {{p|89}} qualifier. --[[User:Tobias1984|Tobias1984]] ([[User talk:Tobias1984|talk]]) 19:57, 13 June 2013 (UTC)
:*{{comment}} apparently, the datatype should be string, as X and Y are not compatible with a number datatype. --[[User:Zolo|Zolo]] ([[User talk:Zolo|talk]]) 18:07, 18 June 2013 (UTC).
:*{{Comment}} 'Number' is a problematic datatype for the reasons cited above.  However, 'string' isn't ideal either.  Chromosomes are distinct objects that have properties like 'accession', 'length', etc. and should thus be represented as 'items'.  I suggest changing the 'datatype' to 'item' and having claims of the form {{Q|414043}} ''GenLoc_chr'' {{Q|657319}}. [[User:Emw|Emw]] ([[User talk:Emw|talk]]) 01:31, 27 June 2013 (UTC)

=== GenLoc_start ===
{{Property proposal
|status                 = 644
|description            = Specifies the database starting location of the gene in UCSC Genome Informatics website.
|infobox parameter      = [[:en:Template:GNF_Protein_box]] = GenLoc_start
|datatype               = Number
|domain                 = term
|allowed values         = 
|suggested values       = 
|source                 = http://genome.ucsc.edu/
|example                = [[Q414043|Reelin]] = 103112231
|filter                 = Numbers only. Number of digits may be constrained within specific range
|robot and gadget jobs  = Fill gene wikidata items with correct Database starting point
|proposed by            = [[User:Chinmay26|Chinmay26]] ([[User talk:Chinmay26|talk]]) 20:37, 10 June 2013 (UTC)
}}
;Discussion
:*{{support}} [[User:Andrew Su|Andrew Su]] ([[User talk:Andrew Su|talk]]) 21:47, 10 June 2013 (UTC)
:*{{support}} - needs {{p|89}} qualifier. --[[User:Tobias1984|Tobias1984]] ([[User talk:Tobias1984|talk]]) 19:58, 13 June 2013 (UTC)
:*{{Comment}} In addition to a species qualifier, when defining a gene's location I think we also need to include qualifiers for: 
::* Which [[:en:Genome_assembly|genome assembly]] the coordinates are derived from (e.g. GRCh37/hg19, NCBI36/hg18, etc).
::* The [[:en:Accession_number_(bioinformatics)|accession]] of the sequence (including a version, if applicable).  This would make it unambiguous which gene variant or alternative placement is being used. 
:: The same information would be needed in GenLoc_chr and GenLoc_end, since all three properties would be needed to define a chromosome coordinate. [[User:Emw|Emw]] ([[User talk:Emw|talk]]) 04:37, 19 June 2013 (UTC)

=== GenLoc_end ===
{{Property proposal
|status                 = 645
|description            = Specifies the database ending location of the gene in UCSC Genome Informatics website.
|infobox parameter      = [[:en:Template:GNF_Protein_box]] = GenLoc_end
|datatype               = Number
|domain                 = term
|allowed values         = 
|suggested values       = 
|source                 = http://genome.ucsc.edu/
|example                = [[Q414043|Reelin]] = 103629963
|filter                 = Numbers only. Number of digits may be constrained within specific range
|robot and gadget jobs  = Fill gene wikidata items with correct Database ending point
|proposed by            = [[User:Chinmay26|Chinmay26]] ([[User talk:Chinmay26|talk]]) 20:42, 10 June 2013 (UTC)
}}
;Discussion - Using the above three properties we can specify "genomic coordinates" in UCSC. Ex: [[Q414043|Reelin]] = http://genome.ucsc.edu/cgi-bin/hgTracks?org=Human&db=hg19&position=chr7:103112231-103629963
:*{{support}} [[User:Andrew Su|Andrew Su]] ([[User talk:Andrew Su|talk]]) 21:47, 10 June 2013 (UTC)
:*{{support}} - needs {{p|89}} qualifier. --[[User:Tobias1984|Tobias1984]] ([[User talk:Tobias1984|talk]]) 19:59, 13 June 2013 (UTC)

*{{P|643}}, {{P|644}}, {{P|645}} --[[User:Tobias1984|Tobias1984]] ([[User talk:Tobias1984|talk]]) 21:32, 18 June 2013 (UTC)

=== RTECS number (en) ===
{{Property proposal
|status                 = 657
|description            = RTECS number ({{Q|754938}})
|infobox parameter      = {{Q|52426}} en: RTECS
|datatype               = string
|domain                 = term
|allowed values         = 
|suggested values       = 
|source                 = 
|example                = see [[Wikidata:Chemistry_task_force/Properties]]. {{Q|2351742}} = "TZ8616000"
|filter                 = 
|robot and gadget jobs  = 
|proposed by            = [[User:GZWDer|GZWDer]] ([[User talk:GZWDer|talk]]) 09:30, 6 June 2013 (UTC)
}}
;Discussion
*{{support}} --[[User:Tobias1984|Tobias1984]] ([[User talk:Tobias1984|talk]]) 09:36, 6 June 2013 (UTC)
*{{support}} [[User:Snipre|Snipre]] ([[User talk:Snipre|talk]]) 22:27, 6 June 2013 (UTC)
* {{strong support}}.  --[[User:Beetstra|Beetstra]] ([[User talk:Beetstra|talk]]) 13:05, 24 June 2013 (UTC)
* {{support}}--[[User:Saehrimnir|Saehrimnir]] ([[User talk:Saehrimnir|talk]]) 15:46, 24 June 2013 (UTC)

=== Tracklist ===
{{Property proposal
|status = 658
|description = Tracklist of the album. Every track must have: title, music composer(s), lyric composer(s), featuring (if needed), duration, ...
|infobox parameter =
|datatype = Item
|domain =
|allowed values =
|source = [[w:it:Template:Tracce]]
|example =
|robot and gadget jobs =
|proposed by = <small style="background:#f00;">'''★&nbsp;[[User:Airon90|<span style="color:#000;">→ A</span>]][[Special:Contributions/Airon90|<span style="color:#f00;background:#000;">ir</span>]][[User talk:Airon90|<span style="color:#000;">on&#32;90</span>]]'''</small> 13:04, 21 February 2013 (UTC)
}}
<!-- {{ctop|See discussion|width=100%}} --><!-- Unhide when approved/declined and add {{cbot}} at the end. -->
;Discussion
* It's very useful, but should we create sub-properties for doing this? At the time it's not possible (I think) --'''<span style="font-family:BankGothic Md BT">[[Utente:Viscontino|<span style="color:green">Viscontino</span>]]&nbsp;[[Discussioni utente:Viscontino|<span style="font-size:small;color:#348017"><sup>talk</sup></span>]]</span>''' 10:07, 2 March 2013 (UTC)
*{{support}} Needed. — [[User:Hahc21|<font color="#333333">'''ΛΧΣ'''</font>]][[User_talk:Hahc21|<font color="#336699">'''<sup>21</sup>'''</font>]] 20:48, 18 April 2013 (UTC)
*{{Comment}} 1. Since it's an item, we should create an article for each song. 2. We should add qualifiers such as the order number. --[[User:Viscontino|Viscontino]] ([[User talk:Viscontino|talk]]) 11:20, 19 April 2013 (UTC)
**{{comment}} 1 & 2 sounds good for me. I would do it that way, yeah. --[[User:Nightwish62|Nightwish62]] ([[User talk:Nightwish62|talk]]) 15:58, 19 April 2013 (UTC)
* {{support}}. [[User:Conny|Conny]] ([[User talk:Conny|talk]]) 14:28, 28 April 2013 (UTC).
* {{support}}. I'm new to wikidata, but I would sure like this. It would be nice if it could be made in such a way that we have (or could later add) a link to the "canonical" version of the song. For example, there are many versions of Dream A Little Dream. And one artist might have several versions of a songs (e.g. live album and studio album). Somewhat related, it would also be nice with a way to say if a song samples a different song (i.e uses a clip of a song to make a new song). —[[User:Bajsejohannes|Bajsejohannes]] ([[User talk:Bajsejohannes|talk]]) 05:40, 30 April 2013 (UTC)
*{{support}} --[[User:Napoleon.tan|Napoleon.tan]] ([[User talk:Napoleon.tan|talk]]) 12:28, 30 April 2013 (UTC)
:Don't understand to what this property should link? To an item linked to Wikipedia pages containing a tracklist? Not useful. To all Tracks? Maybe useful but an item has to be created for every song. Don't know what you mean by "Every track must have…" that wouldn't be part of the properties value. -- [[User:MichaelSchoenitzer|MichaelSchoenitzer]] ([[User talk:MichaelSchoenitzer|talk]]) 23:59, 10 May 2013 (UTC)
*{{oppose}} - Oppose the datatype. Track names don't have to be translated. A property called "tracks" could hold a string for each song with a qualifier for the number on the album. --[[User:Tobias1984|Tobias1984]] ([[User talk:Tobias1984|talk]]) 12:39, 24 May 2013 (UTC)
**{{comment}} It's not about the point to translate a track name, it's about the point to have the possibility to enter more information to a track. --[[User:Nightwish62|Nightwish62]] ([[User talk:Nightwish62|talk]]) 15:53, 30 June 2013 (UTC)

=== group ===
{{Property proposal
|status                 = not done
|description            = the item is part of a group of the same kind of items as itself.
|infobox parameter      = many, see examples below
|datatype               = item
|domain                 = all
|allowed values         = the value must be an item which the subject is a part of, and which only consists of items of that kind.
|suggested values       = 
|source                 = 
|example                = <br/ >
**Islands: {{Q|8828}} group {{Q|5765}} (infobox parameter: archipelago in [[:en:template:Infobox islands]]; will obsolete {{P|614}})
**Mountains: {{Q|513}} group {{Q|924257}}, {{Q|5451}} (infobox parameter: range in [[:en:template:Infobox mountain]]; will obsolete {{P|295}})
**Persons: {{Q|2186}} group {{Q|2197}}
**Roads: {{Q|19191}} group {{Q|400256}} (infobox parameter: system in [[:en:template:Infobox road]]; will obsolete {{P|16}})
**Lakes: {{Q|1383}} group {{Q|7347}} (infobox parameter: group in [[:en:Template:Infobox lake]], will obsolete {{P|265}}
|filter                 = 
|robot and gadget jobs  = It can be checked with help of tables with allowed values if object is of a type which is a group of the same kind as the subject
|proposed by            = [[User:Byrial|Byrial]] ([[User talk:Byrial|talk]]) 09:32, 10 June 2013 (UTC)
}}
;Discussion
This property was briefly discussed at [[Wikidata:Properties for deletion#Property:P265]]. If it is created it will obsolete several other properties which should be deleted. (4 properties which can be replaced are mentioned in the examples section above, and there may be more). "Group" is clearly redundant with {{P|361}}, but it will be easier to use in infoboxes than P361 because of the constraint on the value type. [[User:Byrial|Byrial]] ([[User talk:Byrial|talk]]) 09:32, 10 June 2013 (UTC)
:{{oppose}} Redundant with {{p|361}} [[User:Snipre|Snipre]] ([[User talk:Snipre|talk]]) 12:08, 10 June 2013 (UTC)
:{{oppose}} as Snipre --[[User:Paperoastro|Paperoastro]] ([[User talk:Paperoastro|talk]]) 12:20, 18 June 2013 (UTC)

=== instances of (en) ===
{{Property proposal
|status                 = not done
|description            = the item is about several individual instances of a class.
|infobox parameter      = 
|datatype               = item
|domain                 = Group of instances
|allowed values         = Classes
|suggested values       = 
|source                 = 
|example                = {{Q|219937}} instances of {{Q|215627}}
|filter                 = 
|robot and gadget jobs  = 
|proposed by            = [[User:Byrial|Byrial]] ([[User talk:Byrial|talk]]) 10:00, 18 June 2013 (UTC)
}}
;Discussion
This property is similar to {{P|31}}, but is used when the item is not one, but several instances of a class. The subject should not be a list of instances selected by some criteria (use {{P|360}} for that), but should be about a few instances described in detail. If there also is separate items for the contained instances these can be indicated with {{P|527}}. [[User:Byrial|Byrial]] ([[User talk:Byrial|talk]]) 10:00, 18 June 2013 (UTC)
* {{Oppose}} This seems redundant with {{P|279}}.  A class is a type, which is a set of instances and the properties that those instances share.  {{Q|219937}} is fundamentally a set of (two) instances and the properties that those instances share.  It's clearly an unusual example of a class, but in terms of [[:en:Ontology components|ontology components]], 'Bonnie and Clyde' is a class nonetheless.
: To those who might not agree: how is {{Q|219937}} fundamentally different than other, more conventional classes, like {{Q|215627}}?  More to the point, how would 'instances of' be fundamentally different than 'subclass of'? [[User:Emw|Emw]] ([[User talk:Emw|talk]]) 11:45, 18 June 2013 (UTC)
:: An instance of any class is also a subset with one member of the class, and thus a subclass by that argumentation. So can we expect a deletion proposal for {{P|31}}? The problem with this is that {{Q|219937}} do not share any properties that other persons do not have, except for being Bonnie and Clyde. And the same is valid for each of them. [[User:Byrial|Byrial]] ([[User talk:Byrial|talk]]) 12:10, 18 June 2013 (UTC)
::: Insofar as set theory applies to ontology components like instances and classes, {{P|31}} (rdf:type) corresponds to <math>\in</math> ([[:en:Element_(mathematics)|element of]]) and {{P|279}} (rdfs:subClassOf) corresponds to <math>\subseteq</math> ([[:en:Subset|subset of]]).  So I don't see how it's valid to say that all instances of a class are sets.  Is that supported by the description logics that underlay OWL DL, or the basis of some other W3C recommendation for structured data?  
::: I also still don't see how 'instances of' would be fundamentally different than 'subclass of'.  P31 and P279 are based on W3C recommendations, are implemented throughout the Semantic Web, have support in ontology toolsets, and have a substantial body of literature about them.  To my knowledge, 'instances of' does not.  If it does, which would presumably mean it's not redundant with {{P|279}}, then please point me to where I can read more about that. [[User:Emw|Emw]] ([[User talk:Emw|talk]]) 04:07, 19 June 2013 (UTC)

A class A is a subclass of class B if all instances of A is also instances of B. So if you define a class as "the class of items which are either {{Q|2319886}} or {{Q|3320282}}" it is a subclass of {{Q|215627}} with 2 instances. And if you define a class as "the class of items which are {{Q|2319886}}" it is a subclass of {{Q|215627}} with one instance. But if you define a class as "the class of items which are {{Q|219937}}" it is not a subclass of {{Q|215627}} as {{Q|219937}} is not an instance of {{Q|215627}}. Instead {{Q|219937}} is an instance of the class "two persons described together", but we have not created an item for that class (as far as I know). We could do that, but I think it is better to create the property "instances of". "X is 'instances of' class Y" really means "X is an instance of the class of 'instances of class Y described together'", so I do not agree that it is redundant to {{P|279}}. I cannot point you to any literature on this, and I doubt that W3C or others who made recommendations for semantic webs considered the situation where we have the both the two items {{Q|2319886}} and {{Q|3320282}}, and a separate item {{Q|219937}}. [[User:Byrial|Byrial]] ([[User talk:Byrial|talk]]) 06:25, 19 June 2013 (UTC)

{{O}} We don't need to tie ourselves in knots trying to write statements about {{Q|219937}}. The detailed statements are in the items about each individual and we already have {{P|527}} which works to link {{Q|219937}} to {{Q|2319886}} and {{Q|3320282}}. For me that is the only statement we need to make about any page which refers to two or more items. [[User:Filceolaire|Filceolaire]] ([[User talk:Filceolaire|talk]]) 20:00, 19 June 2013 (UTC)

=== in language / in der Sprache ===
{{Property proposal
|status            = not done
|description       = list of languages, for which a language dependent statement is applicable
|infobox parameter = 
|datatype          = item
|domain            = language dependent properties of any item
|allowed values    = items of languages
|source            = 
|example           = [[Q925]] would have a property [[Property:P138|named after]] set to [[Q1150|Mercury]] with this qualifier set to [[Q1860|English]] and the same property set to [[Q1090|Silver]] with this qualifier set to [[Q188|German]]
|robot and gadget jobs = 
|proposed by      = [[User:Šlomo|Šlomo]] ([[User talk:Šlomo|talk]])
}}
Not sure where's the right place to propose qualifiers, so I try it here. The need of this qualifier was mentioned at [[Property_talk:P138#Dépendance aux langues / Language dependency]] [[User:Šlomo|Šlomo]] ([[User talk:Šlomo|talk]]) 10:44, 19 April 2013 (UTC)
:{{comment}} "named after" is applicable to a word or a name, not to a language. Actually "mercury" was also called "quicksilver" in English. --[[User:Zolo|Zolo]] ([[User talk:Zolo|talk]]) 12:12, 19 April 2013 (UTC)
:{{comment}} The program name "[[Q58427|Jitsi]]" comes from a Bulgarian word for wires, but the name "Jitsi" itself probably cannot be called Bulgarian-specific. So one side of the "named after" statement is language-specific, but the other is not… --[[User:AVRS|AVRS]] ([[User talk:AVRS|talk]]) 12:23, 19 April 2013 (UTC)
:{{Comment}} – There is still the problem that it not refers to the item, but to names for it. If a language have different names of different origin for an item, which of the names does the statement apply to? Examples where Danish have synonyms are some elements (like [[Q629|oxygen]]), plants (like [[Q161360|Chamaecyparis lawsoniana]]), animals (like [[Q216815|Common eland]]) and more. [[User:Byrial|Byrial]] ([[User talk:Byrial|talk]]) 13:58, 19 April 2013 (UTC)
::This raises a question about the property itself, or about it's use. I can imagine multiple "named after" statement for one item even with the same language qualifier, especially when distinguished through other qualifiers (time etc.). I would understand a statement like this like: "There is some name for item A which is derived from some name of item B." Also, we can remove the "named after" property from the list. But if we'll have it, we'll definitely need a language qualifier for it.--[[Special:Contributions/83.240.94.18|83.240.94.18]] <small>=[[User:Šlomo|Šlomo]] ([[User talk:Šlomo|talk]])</small> 18:26, 25 April 2013 (UTC)
:::That's the beauty of qualifiers. They apply to one statement. Each 'named after' statement has it's own language qualifier that applies to that statement. [[User:Filceolaire|Filceolaire]] ([[User talk:Filceolaire|talk]]) 21:11, 6 June 2013 (UTC)
:{{comment}} Is there a particular reason why we couldn't use regular properties as qualifiers where appropriate? This seems like it would be covered by [[Property:P407]]. [[User:Silver hr|Silver hr]] ([[User talk:Silver hr|talk]]) 19:33, 26 April 2013 (UTC)
::{{o}} per Silver. Redundant to {{P|407}} [[User:Filceolaire|Filceolaire]] ([[User talk:Filceolaire|talk]]) 21:11, 6 June 2013 (UTC)
:{{oppose}} Translation won't be a property: use the label with the appropriate language code. [[User:Snipre|Snipre]] ([[User talk:Snipre|talk]]) 18:45, 10 June 2013 (UTC)

=== Fought in conflict(s) / Gekämpft in Konflikt(en) / Combattu dans les conflits / Сражались в конфликтe(ах) / 攻防戦で戦った ===
{{Property proposal
|status            = not done
|description       = This property indicates the wars and/or battles to which the subject has participated.
|infobox parameter = [[:en:template:Infobox Governor]] '''battles''' [[:en:template:Infobox officeholder]] '''battles''' etc.
|datatype          = wikibase-item
|domain            = [[Q215627|person]]
|allowed values    = event
|source            = Source from infoboxes in wikipedia articles
|example           = [[Q742978|Harold Guy Hunt]]
|robot and gadget jobs = This could easily be imported through the use of automation services.
|proposed by      = [[User:Presentime|Presentime]] ([[User talk:Presentime|talk]])
}}
This property would give specific clarity as to the conficts that the subject has fought in. The property for the branch of their military service exists already [[Property:P241|military branch]]. This property would serve the purpose of denoting which specific events the subject has participated in while a member of their military force. [[User:Presentime|Presentime]] ([[User talk:Presentime|talk]]) 20:14, 20 April 2013 (UTC)
: {{Comment}} This property seems useful!  But I would tweak its title to simply 'fought in', and change the 'allowed values' field to be 'conflicts'.  Conflicts are a [[P:P279|subclass of]] event, and it's best for the 'allowed values' field to be as precise as possible. [[User:Emw|Emw]] ([[User talk:Emw|talk]]) 20:23, 20 April 2013 (UTC)
:: That is a good point. Perhaps this should be a qualifier of 'fought in' to specify which battles the subject was involved in. For example: '''fought in''' [[Q362|World War II]] with a qualifier of '''Fought in conflict''' [[Q1970141|Battle of Gondar]]. --[[User:Presentime|Presentime]] ([[User talk:Presentime|talk]]) 22:11, 20 April 2013 (UTC)
:::{{Comment}} - If somebody fought in the Battle of Gondar and that battle is a "subclass of = World War 2" then the qualifier would be redundant? --[[User:Tobias1984|Tobias1984]] ([[User talk:Tobias1984|talk]]) 10:26, 8 May 2013 (UTC)
::::Yes, I think the battle would be enough, and battles are "part of" war, rather than "subclass of". See [[Q83224]] Battle of Hastings. [[User:Danrok|Danrok]] ([[User talk:Danrok|talk]]) 02:44, 18 May 2013 (UTC)
*{{Support}} --[[User:Odejea|Odejea]] ([[User talk:Odejea|talk]]) 13:14, 5 June 2013 (UTC)
*The property has been created already, see {{P|607}}. This discussion can be archived.--[[User:Kompakt|Kompakt]] ([[User talk:Kompakt|talk]]) 05:35, 14 June 2013 (UTC)
<br/>
{{not done}}, since {{P|607}} already exist. --[[User:Nightwish62|Nightwish62]] ([[User talk:Nightwish62|talk]]) 21:36, 30 June 2013 (UTC)

== drafted by ==
{{Property proposal
|status            = 647
|description= which team the player was drafted by
|infobox parameter= put infobox parameter here if existing, e.g. [[:en:Template:Infobox ice hockey player]] '''drafted_team''' 
|datatype= wikibase-item
|domain= sportsperson
|allowed values= any sports team
|source= Infobox I guess
|example= [[Q434899|Joe Thornton]] <drafted by> [[Q194121|Boston Bruins]]
|robot and gadget jobs= My bot is ready to import this data for all hockey players.
|proposed by= [[User:Legoktm|Legoktm]] ([[User talk:Legoktm|talk]]) 02:57, 30 March 2013 (UTC)
}}
:{{oppose}} We already have [[Property:P54]] [[User:Snipre|Snipre]] ([[User talk:Snipre|talk]]) 09:23, 2 April 2013 (UTC)
::No that's totally different. You can be drafted by a team and never play for them. [[User:Legoktm|Legoktm]] ([[User talk:Legoktm|talk]]) 10:37, 2 April 2013 (UTC)
::: Sorry but property [[Property:P54|member of sports team]] doesn't imply that the sportman has to play. I don't know if my English is too poor but draft is for me integration in a team, after if you play or not is something else. By being drafted you can play as member of the team. [[User:Snipre|Snipre]] ([[User talk:Snipre|talk]]) 17:36, 9 April 2013 (UTC)
:::: {{comment}} Very often a player will be drafted by a Major League Baseball team and never get close to even being on that team's roster.  They may be traded or fail to develop long before reaching that point, or even refuse to sign with the organization at all.  This is still relevant information to know though, so a separate property for the drafting organization is valid and distinct from a property for teams a player was a member of. [[User:Joshbaumgartner|Joshbaumgartner]] ([[User talk:Joshbaumgartner|talk]]) 08:32, 9 May 2013 (UTC)
:{{Support}}, though it looks like the infobox parameter is draft_team.  The date of the draft could be added as a qualifier when available. [[User:Superm401|Superm401]] - [[User_talk:Superm401|Talk]] 01:00, 6 April 2013 (UTC)
::You're right, fixed. Thanks, [[User:Legoktm|Legoktm]] ([[User talk:Legoktm|talk]]) 06:44, 6 April 2013 (UTC)
:{{oppose}}, not relevant. Being a member of a team is. --[[User:NaBUru38|NaBUru38]] ([[User talk:NaBUru38|talk]]) 16:47, 11 April 2013 (UTC)
::Relevant to what?  It seems like a well-defined concept that can be easily sourced.  I see no reason to exclude it.  Further, this is the kind of thing a biography would mention whether or not they actually played for the team. [[User:Superm401|Superm401]] - [[User_talk:Superm401|Talk]] 04:24, 17 April 2013 (UTC)
: {{Support}} This property is relevant in its domain. [[User:Emw|Emw]] ([[User talk:Emw|talk]]) 20:52, 20 April 2013 (UTC)
: {{Support}} per Emw and Superm401. <font face="Vani" color="black">'''''[[User:FrigidNinja|Frigid]][[User Talk:FrigidNinja|Ninja]]'''''</font> 11:55, 27 April 2013 (UTC)
:I think this should have a less ambiguous label. "Drafted by" could mean many other things. --[[User:Yair rand|Yair rand]] ([[User talk:Yair rand|talk]]) 16:12, 28 April 2013 (UTC)
:{{Support}} --[[User:Stryn|Stryn]] ([[User talk:Stryn|talk]]) 16:19, 28 April 2013 (UTC)
:{{support}} this is a very useful piece of information when learning more about a player's career path, as well as studying a team's player development and scouting history. [[User:Joshbaumgartner|Joshbaumgartner]] ([[User talk:Joshbaumgartner|talk]]) 08:32, 9 May 2013 (UTC)
<br/>
{{done}} Regards, — [[User:Moe Epsilon|<span style="color:royalblue; font-family: Segoe Script">Moe</span>]] [[User talk:Moe Epsilon|<span style="color:royalblue; font-family: Segoe Script">Epsilon</span>]] 21:48, 18 June 2013 (UTC)

== GenLoc_assembly ==
{{Property proposal
|status                 = 659
|description            = Specify the genome assembly of the gene in UCSC Genome Informatics website. This wil be used as a '''qualifier''' to GenLoc_start, GenLoc_end & GenLoc_chr.
|infobox parameter      = [[:en:Template:GNF_Protein_box]] = GenLoc_db
|datatype               = item
|domain                 = term
|allowed values         = 
|suggested values       =
|source                 = http://genome.ucsc.edu/
|example                = [[Q414043|Reelin]] = hg19
|filter                 = 
|robot and gadget jobs  = Fill gene wiki items with correct gene assembly
|proposed by            = [[User:Chinmay26|Chinmay26]] ([[User talk:Chinmay26|talk]])
}}
:{{support}} part of protein infobox and important for a GSoC project. --[[User:Tobias1984|Tobias1984]] ([[User talk:Tobias1984|talk]]) 15:15, 18 June 2013 (UTC)
:{{Support}}<s>{{Comment}}</s> hg19 (i.e. GRCh37) is a genome assembly, not a 'database assembly' or 'gene assembly'.  I would suggest calling this qualifier "GenLoc_assembly" and updating the documentation 'description' field. [[User:Emw|Emw]] ([[User talk:Emw|talk]]) 03:28, 21 June 2013 (UTC)
::Updated. --[[User:Chinmay26|Chinmay26]] ([[User talk:Chinmay26|talk]]) 17:42, 21 June 2013 (UTC)
::: Thanks!  Another suggestion: to help avoid confusion over aliases for the genome assembly (GRCh37 vs. hg19 vs. ...), it seems like it'd be a good idea to change the "datatype" of this property from "string" to "item".  Wikidata items for the genome assemblies could be created as needed.  The set of relevant genome assemblies is small, so this doesn't seem like it would be a problem.  Another benefit of using an "item" datatype is the assembly could also be linked to an accession. [[User:Emw|Emw]] ([[User talk:Emw|talk]]) 02:05, 22 June 2013 (UTC)
::::Handling aliases may not be a problem.I am not aware about whether there would be a need to represent assemblies as wikidata items. I will run this through the task force for some more clarification. --[[User:Chinmay26|Chinmay26]] ([[User talk:Chinmay26|talk]]) 10:43, 22 June 2013 (UTC)
::::: A more compelling reason to use 'item' instead of 'string' is that it would enable properties about those assemblies to be easily organized.  For example, assemblies have accessions.  Having this property point to an item representing an assembly rather than just a string would allow sequences to be queried by the accession of the assembly they're associated with.  Assemblies also have other relevant properties, like length (i.e. the length of an organism's genome), associated chromosomes, etc. [[User:Emw|Emw]] ([[User talk:Emw|talk]]) 01:22, 27 June 2013 (UTC)
:::::: I think in the long term, assemblies as items make a lot of sense.  However, I hesitate here because of the practicalities of [[User:Chinmay26|Chinmay26]]'s GSoC project.  His goal of course is to model genes in sufficient detail so that the Wikipedia templates can draw most (if not all) of their content from Wikipedia.  I don't want Chinmay to get too caught up in modeling all of biology correctly and never get to coding.  Emw, what do you think?  Can we leave this one as a string for now in the name of simplicity, and move toward assemblies as items later?  Cheers, [[User:Andrew Su|Andrew Su]] ([[User talk:Andrew Su|talk]]) 20:09, 27 June 2013 (UTC)
::::::: Will any of the ported PBB template parameters use properties with an item datatype?  If not, then it seems that many of the properties put forward for the GSoC work will need to be remapped to item-based properties in the long term.  (And how will the kind of EC class discussed [[Property_talk:P591#Distinguishing_enzymes_and_gene_products|here]] be handled?) With this particular property, it seems claims would involve only two items: either the item for the human assembly or the item for the mouse assembly.
::::::: If handling item-based properties would be a big impediment to the progress of the GSoC project, then I agree it's better to have string-based claims than no claims at all.  If that's the case, I agree it'd make sense to use strings now and update these claims to use item-based properties later. [[User:Emw|Emw]] ([[User talk:Emw|talk]]) 01:21, 28 June 2013 (UTC)
:::::::: Good questions, as usual.  I think the majority of the PBB parameters are modeled as strings (current first-pass list: HGNCid , Symbol , AltSymbols, Homologene, EntrezGene , Ensembl, RefseqmRNA(qualifier to protein ID) , GenLoc_db /start/chr , GeneAtlas_image, species , Uniprot ID). But on second thought, it probably doesn't matter from Chinmay's point of view if hg19 is an item rather than a string.  I think as long as we let him create that as a bare-bones item and leave populating statements on that item to others (accessions, length, etc.), then that won't hold him up at all.  I was getting worried that Chinmay would have to do that, but of course that's not strictly necessary just for changing the data type here.  Bottom line, I'm happy with changing the data type to item.  Anyone else (especially Chinmay) have any objection?  Cheers, [[User:Andrew Su|Andrew Su]] ([[User talk:Andrew Su|talk]]) 07:11, 28 June 2013 (UTC)
:::::::::As Andrew pointed it out, I dont have any issues regarding this. I have updated it to item datatype. [[User:Chinmay26|Chinmay26]] ([[User talk:Chinmay26|talk]]) 17:36, 28 June 2013 (UTC)
:{{support}} [[User:Andrew Su|Andrew Su]] ([[User talk:Andrew Su|talk]]) 21:32, 21 June 2013 (UTC)
{{done}} --[[User:Tobias1984|Tobias1984]] ([[User talk:Tobias1984|talk]]) 12:18, 2 July 2013 (UTC)

== EC classification ==
{{Property proposal
|status                 = 660
|description            = the Enzyme Commission (EC)-based accepted name of any enzyme classifications of the protein or RNA molecule.  May be the same as the name of an item about a protein or RNA molecule, but should only link from protein or RNA items to items that are a subclass of {{Q|8047}} and have an {{P|591}} value.  Should not be used for claims in enzyme items.
|infobox parameter      = [[Q6453709|Template:Infobox_enzyme]] = name
|datatype               = item
|domain                 = {{Q|8054}}, {{Q|11053}} (not {{Q|8047}})
|allowed values         = Names of [[Q8047|enzymes]] that have an {{P|591}} value
|suggested values       = 
|source                 = [http://www.chem.qmul.ac.uk/iubmb/enzyme/ Enzyme Nomenclature Committee of the International Union of Biochemistry and Molecular Biology] for the EC accepted names, {{Q|905695}} for protein → enzyme mappings
|example                = for the [[WD:MBTF]] model protein: {{Q|13561329}} = {{Q|420032}} (should be "serine endopeptidases" which is the EC accepted name for this enzyme); for a protein that has an alias matching the name in the EC classification {{Q|1476411}} (alias: pappalysin 1) = {{Q|13107614}} 
|filter                 = 
|robot and gadget jobs  = 
|proposed by            = [[User:Emw|Emw]] ([[User talk:Emw|talk]])
}}
: {{Support}} This property is the outcome of the discussion at [[Property_talk:P591#Distinguishing enzymes and gene products]]. Open questions:
::* How should statements using this property be sourced? 
::* How should enzyme classes that have no "full" name be labeled?  For example, according to http://www.chem.qmul.ac.uk/iubmb/enzyme/EC2/1/, EC 2.1 has the name "Transferring one-carbon groups".  Should such enzyme classes be labeled by taking the next-highest EC classes name (e.g. [http://www.chem.qmul.ac.uk/iubmb/enzyme/EC2/ EC 2], "transferase") and prepending it to the "incomplete" name to give labels like "transferases transferring one-carbon groups"?  The official EC name could be an alias of the item in these cases.
: RNA molecules with EC classifications, like {{Q|1012651}} ([http://www.chem.qmul.ac.uk/iubmb/enzyme/EC3/1/26/5.html EC 3.1.26.5]), also need to be considered. [[User:Emw|Emw]] ([[User talk:Emw|talk]]) 17:40, 29 June 2013 (UTC)
: {{Support}} I agree that the edge cases mentioned above need some thought and discussion, but I'd suggest not holding up the property proposal before those are resolved.  One way or another, we're going to need this property...  Cheers, [[User:Andrew Su|Andrew Su]] ([[User talk:Andrew Su|talk]]) 17:47, 29 June 2013 (UTC)
: {{Support}} – I took the liberty of adding EC-IUBMB as the source.  In addition, the "name" parameter of the enzyme infobox should be set to the EC accepted name, hence this parameter should be appropriate for this property.  [[User:Boghog|Boghog]] ([[User talk:Boghog|talk]]) 00:02, 30 June 2013 (UTC)
:: I agree that the names themselves should come from EC-IUBMB (and occasionally adjusted per the second question above?), but what source should be used to support the assignments of those EC names to gene products?  For example, what source supports the claim that [[:en:Reelin|reelin]] is a serine endopeptidase ([http://www.chem.qmul.ac.uk/iubmb/enzyme/EC3/4/21/ EC 3.4.21])?  And when the EC name differs from the Wikipedia article name -- e.g. with the EC name serine endopeptidase corresponding to the Wikidata item [[Q420032]] (currently labeled 'serine protease') -- should the Wikidata item label change, or should the EC name be added as an alias, or what? [[User:Emw|Emw]] ([[User talk:Emw|talk]]) 03:21, 30 June 2013 (UTC)
::: I think UniProt should the ultimate source of the annotation (e.g., [http://www.uniprot.org/uniprot/P78509]).  For the latter question, I think the Wikipedia article should stay at "Serine protease" (because that's how most scientists would probably refer to it), and the Wikidata label should be "serine endopeptidase" (because that's the official label).  And then we can use redirects and aliases to make sure either search resolves correctly on both ends.  (The Wikipedia redirect is already in place.)  My two cents...  Cheers, [[User:Andrew Su|Andrew Su]] ([[User talk:Andrew Su|talk]]) 04:09, 30 June 2013 (UTC)
:::: Great, having UniProt as the source for these claims seems good to me.  If the EC classification for a gene product can be supported by simply referring to a URL of the form<nowiki>http://www.uniprot.org/uniprot/</nowiki><[[Property:P352|UniProt ID]]>, then that seems fairly automatable, since virtually all protein items will have a UniProt ID added as part of the GSoC project.  I don't think such sourcing should be necessary for the GSoC project, but is there some place to add this task to a backlog so it doesn't get forgotten? 
:::: Regarding labels, I think it would be reasonable to change the enzyme Wikidata item's label to the EC accepted name when the Wikipedia article name differs.  In these cases, I imagine we agree that the Wikipedia article name should be kept as an alias on the Wikidata item.  I've mocked up {{Q|420032}} as an example. [[User:Emw|Emw]] ([[User talk:Emw|talk]]) 04:38, 30 June 2013 (UTC)
::::: I agree that UniProt would be a good source for the protein → enzyme mappings. In addition, UniProt can supply a list of all proteins with a given EC number/accepted name (see for example[http://www.uniprot.org/uniprot/?query=ec%3A3.4.21.-+reviewed%3Ayes+AND+organism%3A%22Human+%5B9606%5D%22&sort=score human serine endopeptidases]) if that is needed. [[User:Boghog|Boghog]] ([[User talk:Boghog|talk]]) 09:43, 30 June 2013 (UTC)
::::: Regarding task tracking, we don't have a running list anywhere.  You're welcome to start one on [[Wikidata:Molecular Biology task force]] if you like, but I'm pretty sure we'll catch this one when we systematically do our uploading and sourcing...  (and {{Q|420032}} looks great to me!)  Cheers, [[User:Andrew Su|Andrew Su]] ([[User talk:Andrew Su|talk]]) 15:40, 30 June 2013 (UTC)
{{done}} --[[User:Tobias1984|Tobias1984]] ([[User talk:Tobias1984|talk]]) 12:28, 2 July 2013 (UTC)

== ChemSpider ==
{{Property proposal
|status                 = 661
|description            = {{q|2311683}}: ChemSpider is a free chemical database, owned by the Royal Society of Chemistry.
|infobox parameter      = {{q|6033882}} ChemSpiderID, {{Q|52426}} ChemSpiderID
|datatype               = string
|domain                 = term
|allowed values         = 
|suggested values       = 
|source                 = http://www.chemspider.com/
|example                = {{q|179996}} = "3953", {{q|199678}} = "10189562", {{q|4118}} = "1086"
|filter                 = Only digits
|robot and gadget jobs  = Gather data from infoboxes and website.
|proposed by            = --[[User:Tobias1984|Tobias1984]] ([[User talk:Tobias1984|talk]]) 21:01, 3 June 2013 (UTC)
}}
:{{oppose}} but weak: it's a open database so not an authority.[[User:Snipre|Snipre]] ([[User talk:Snipre|talk]]) 23:38, 4 June 2013 (UTC)
:{{strong support}}: The ChemSpider (UK) database is similarly important as the PubChem (USA) database. --[[User:Leyo|Leyo]] 11:17, 24 June 2013 (UTC)
* {{strong support}}.  --[[User:Beetstra|Beetstra]] ([[User talk:Beetstra|talk]]) 13:05, 24 June 2013 (UTC)
* {{strong support}}. If the connection is wrong this will get fixed very soon. --[[User:Saehrimnir|Saehrimnir]] ([[User talk:Saehrimnir|talk]]) 14:57, 24 June 2013 (UTC)
* {{support}} useful  --[[User:Holmium|Holmium]] ([[User talk:Holmium|talk]]) 16:15, 24 June 2013 (UTC)
{{done}} --[[User:Tobias1984|Tobias1984]] ([[User talk:Tobias1984|talk]]) 12:37, 2 July 2013 (UTC)

== PubChem ==
{{Property proposal
|status                 = 662
|description            = {{q|278487}}: PubChem is a database of chemical molecules and their activities in biological assays. Each compound in Pubchem is identified by a unique Compound Identifier (CID) accession number.
|infobox parameter      = {{q|6033882}} PubChem, {{Q|52426}} PubChem
|datatype               = string
|domain                 = term
|allowed values         = only digits
|suggested values       = 
|source                 = [http://pubchem.ncbi.nlm.nih.gov PubChem, U.S. National Library of Medicine]
|example                = {{q|203174}} = "[http://pubchem.ncbi.nlm.nih.gov/summary/summary.cgi?cid=5426 5426]", {{q|407535}} = "[http://pubchem.ncbi.nlm.nih.gov/summary/summary.cgi?cid=5284603 5284603]",{{q|410174}} = "[http://pubchem.ncbi.nlm.nih.gov/summary/summary.cgi?cid=11125 11125]"
|filter                 =
|robot and gadget jobs  = Gather data from infoboxes and website.
|proposed by            = --[[User:Tobias1984|Tobias1984]] ([[User talk:Tobias1984|talk]]) 21:14, 3 June 2013 (UTC)
}}
{{Constraint:Format|pattern=<nowiki>\d+</nowiki>}}
* {{support}} - Authoritative and stable. [[User:Boghog|Boghog]] ([[User talk:Boghog|talk]]) 19:25, 17 June 2013 (UTC)
* {{support}} --[[User:Kaligula|Kaligula]] ([[User talk:Kaligula|talk]]) 07:06, 19 June 2013 (UTC)
* {{support}} [[User:Danrok|Danrok]] ([[User talk:Danrok|talk]]) 14:51, 22 June 2013 (UTC)
* {{support}} A must have. --[[User:Leyo|Leyo]] 11:19, 24 June 2013 (UTC)
* {{support}} --[[User:Cvf-ps|Cvf-ps]] ([[User talk:Cvf-ps|talk]]) 12:03, 24 June 2013 (UTC)
* {{strong support}}.  --[[User:Beetstra|Beetstra]] ([[User talk:Beetstra|talk]]) 13:05, 24 June 2013 (UTC)
* {{support}} --[[User:Saehrimnir|Saehrimnir]] ([[User talk:Saehrimnir|talk]]) 15:46, 24 June 2013 (UTC)
* {{support}} --[[User:Holmium|Holmium]] ([[User talk:Holmium|talk]]) 16:16, 24 June 2013 (UTC)
{{done}} --[[User:Tobias1984|Tobias1984]] ([[User talk:Tobias1984|talk]]) 14:53, 2 July 2013 (UTC)

== DSM IV ==
{{Property proposal
|status                 = 663
|description            = classification found in the Diagnostic and Statistical Manual of Mental Disorders
|infobox parameter      = [[Q6436840]] es: DSM-IV
|datatype               = string
|domain                 = term
|allowed values         = [[:en:DSM-IV_codes]]
|suggested values       = [[:en:DSM-IV_codes]]
|source                 = 
|example                = [[Q742672|dycalculia]] = "315.1", [[Q177190|sleep disorder]] = "291.89"
|filter                 = only numbers separated by a dot.
|robot and gadget jobs  = gather data from infobox and the [[:en:DSM-IV_codes]]
|proposed by            =--[[User:Tobias1984|Tobias1984]] ([[User talk:Tobias1984|talk]]) 16:16, 1 June 2013 (UTC)
}}
;Discussion
:{{support}} --[[User:Wouterstomp|Wouterstomp]] ([[User talk:Wouterstomp|talk]]) 10:04, 6 June 2013 (UTC)
::{{support}} --[[User:Gambo7|Gambo7]] ([[User talk:Gambo7|talk]]) 20:43, 16 June 2013 (UTC)
:{{support}} --[[User:Kaligula|Kaligula]] ([[User talk:Kaligula|talk]]) 06:59, 19 June 2013 (UTC)
{{done}} - --[[User:Tobias1984|Tobias1984]] ([[User talk:Tobias1984|talk]]) 19:14, 2 July 2013 (UTC)

==Organizer / Veranstalter / organisateur ==
{{Property proposal
|status                 = 664
|description            = person, committee, company, etc., who organizes the event
|infobox parameter      = 
|datatype               = item
|domain                 = events
|allowed values         = people or organizations
|suggested values       =
|source                 =
|example                = [[Q300008|ATP World Tour]] => [[Q744089|Association of Tennis Professionals]]; [[Q101751|{{label|Q101751}}]] => [[Q253414|{{label|Q253414}}]]; [[Q276|{{label|Q276}}]] => [[Q166400|{{label|Q166400}}]]
|filter                 = 
|robot and gadget jobs  = 
|proposed by            = [[User:Kompakt|Kompakt]] ([[User talk:Kompakt|talk]])
}}
;Discussion
I haven't found this property in an infobox as yet, still I think it's a necessary property to describe an event, and can be useful for queries and generating lists (as soon as this functionality is available). The property would have several values in many cases; like in [[Q10162|Eurovision Song Contest 2013]], e.g., this would be not only the EBU, but also [[Q215363|{{label|Q215363}}]]. It's the same with international sports events that are not only organized by the international body, but (usually for the most part) by local organizations or committees.--[[User:Kompakt|Kompakt]] ([[User talk:Kompakt|talk]]) 07:37, 20 May 2013 (UTC)
::I agree with the general idea. But how would it work exactly? Events, especially large events, are often organised by more than one entity, with each taking control of different aspects of the event. [[User:Danrok|Danrok]] ([[User talk:Danrok|talk]]) 22:54, 8 June 2013 (UTC)
:::You're right, I think we can simply add all organizers to the property. For Eurovision 2013, e.g., we'd add both the EBU and Sveriges Television.--[[User:Kompakt|Kompakt]] ([[User talk:Kompakt|talk]]) 16:00, 11 June 2013 (UTC)
* {{support}} [[User:Danrok|Danrok]] ([[User talk:Danrok|talk]]) 19:19, 23 June 2013 (UTC)

== KEGG ==
{{Property proposal
|status                 = 665
|description            = {{q|909442}}:  collection of online databases dealing with genomes, enzymatic pathways, and biological chemicals. The PATHWAY database records networks of molecular interactions in the cells, and variants of them specific to particular organisms. Since July 2011, KEGG switched to a subscription model, and access via FTP is no longer free.
|infobox parameter      = {{q|6033882}} KEGG, {{Q|52426}} KEGG
|datatype               = string
|domain                 = term
|allowed values         = 
|suggested values       = 
|source                 =
|example                = {{q|193598}} = "D00018 ", {{q|243547}} = "D08098 ", {{q|410846}} = "D02601" Leave "D" away?
|filter                 = 
|robot and gadget jobs  = Gather data from infoboxes and website.
|proposed by            = --[[User:Tobias1984|Tobias1984]] ([[User talk:Tobias1984|talk]]) 06:57, 4 June 2013 (UTC)
}}
{{comment}} Better move this proposal under the biochemistry section. [[User:Snipre|Snipre]] ([[User talk:Snipre|talk]]) 23:49, 4 June 2013 (UTC)
:{{support}} --[[User:Kaligula|Kaligula]] ([[User talk:Kaligula|talk]]) 07:06, 19 June 2013 (UTC)
* {{strong support}}.  --[[User:Beetstra|Beetstra]] ([[User talk:Beetstra|talk]]) 13:05, 24 June 2013 (UTC)
* {{support}}--[[User:Saehrimnir|Saehrimnir]] ([[User talk:Saehrimnir|talk]]) 15:46, 24 June 2013 (UTC)
{{done}} --[[User:Tobias1984|Tobias1984]] ([[User talk:Tobias1984|talk]]) 12:43, 3 July 2013 (UTC)

== ICPC 2 ==
{{Property proposal
|status                 = 667
|description            = is a classification method for primary care encounters. It allows for the classification of the patient’s reason for encounter (RFE), the problems/diagnosis managed, primary or general health care interventions, and the ordering of the data of the primary care session in an episode of care structure. It was developed by the WONCA International Classification Committee (WICC), and was first published in 1987 by Oxford University Press (OUP) (from: [[:en:International_Classification_of_Primary_Care]]) See also: [[:en:ICPC-2_PLUS]]
|infobox parameter      = [[Q6436840]] es: CIAP-2
|datatype               = string
|domain                 = term
|allowed values         =
|suggested values       =
|source                 = http://www.who.int/classifications/icd/adaptations/icpc2/en/
|example                = [[Q42982|allergy]] = "A92", [[Q164655|abscess]] = "S10"
|filter                 = 17 beginning letters, followed by a number
|robot and gadget jobs  = gather data from infobox
|proposed by            =--[[User:Tobias1984|Tobias1984]] ([[User talk:Tobias1984|talk]]) 16:16, 1 June 2013 (UTC)
}}
;Discussion
:{{support}} --[[User:Wouterstomp|Wouterstomp]] ([[User talk:Wouterstomp|talk]]) 10:04, 6 June 2013 (UTC)
:: {{support}} --[[User:Gambo7|Gambo7]] ([[User talk:Gambo7|talk]]) 20:43, 16 June 2013 (UTC)
:{{support}} --[[User:Kaligula|Kaligula]] ([[User talk:Kaligula|talk]]) 06:59, 19 June 2013 (UTC)
{{done}} --[[User:Tobias1984|Tobias1984]] ([[User talk:Tobias1984|talk]]) 13:00, 3 July 2013 (UTC)

== GeneReviews  ==
{{Property proposal
|status                 = 668
|description            = online collection of peer-reviewed articles that describe specific gene-releated diseases (See: [[:en:GeneReviews]]
|infobox parameter      = [[Q6436840]] en: GeneReviewsNBK (GeneReviewsName is an additional field of the infobox that describes the entry in the database)
|datatype               = string
|domain                 = term
|allowed values         = 
|suggested values       = 
|source                 = http://www.ncbi.nlm.nih.gov/sites/GeneTests/review
|example                = [[Q8277|multiple sclerosis]] = "NBK1316", [[Q906492|dystonia]] = "NBK1155" (dystonia overview) & "NBK1492" (Early-Onset Primary Dystonia)
|filter                 = NBK followed by number
|robot and gadget jobs  = gather from infobox
|proposed by            = --[[User:Tobias1984|Tobias1984]] ([[User talk:Tobias1984|talk]]) 16:50, 1 June 2013 (UTC)
}}
;Discussion
:{{comment}} - not sure what we should do with the second field that describes the entry. It could be a separate string or multilingual string? --[[User:Tobias1984|Tobias1984]] ([[User talk:Tobias1984|talk]]) 16:50, 1 June 2013 (UTC)
:{{support}} --[[User:Wouterstomp|Wouterstomp]] ([[User talk:Wouterstomp|talk]]) 10:04, 6 June 2013 (UTC)
:: {{support}} --[[User:Gambo7|Gambo7]] ([[User talk:Gambo7|talk]]) 20:43, 16 June 2013 (UTC)
:{{support}} --[[User:Kaligula|Kaligula]] ([[User talk:Kaligula|talk]]) 06:59, 19 June 2013 (UTC)
{{done}} --[[User:Tobias1984|Tobias1984]] ([[User talk:Tobias1984|talk]]) 13:16, 3 July 2013 (UTC)

== MeSH Code ==
{{Property proposal
|status                 = 672
|description            = Medical Subject Headings (MeSH) codes are an index and thesaurus for the life sciences. See: [[:en:List of MeSH codes]]
|infobox parameter      = Not included in any infobox.
|datatype               = String
|domain                 = Main type = term. Life science subjects.
|allowed values         = See: [[:en:List of MeSH codes]]
|suggested values       = See: [[:en:List of MeSH codes]]
|source                 = http://www.ncbi.nlm.nih.gov/pubmed/13982385?dopt=Abstract
|example                = [[Q3999|Anatomy]] = "A", [[Q11068|Cardiovascular system]] = "A07", [[Q101004|Aorta]] = "A07.231.114.056"
|filter                 = 
|robot and gadget jobs  = Can be acquired when Phase 3 gathers information from lists.
|proposed by            = [[User:Tobias1984|Tobias1984]] ([[User talk:Tobias1984|talk]])
}}
;Discussion
:Is it different from [[Property:P486]] (MeSH ID) ? [[User:Snipre|Snipre]] ([[User talk:Snipre|talk]]) 22:15, 8 May 2013 (UTC)
::The MeSH code is the structure of the classification. MeSH ID is the ID that each MeSH Code has in the database. The diseases infobox included the ID rather than the code. I think it would be better to store the code and put the database ID into the source information (so this is actually more of a proposal to change [[Property:P486]]. --[[User:Tobias1984|Tobias1984]] ([[User talk:Tobias1984|talk]]) 10:17, 9 May 2013 (UTC)
::: I suggest to use only one parameter from MeSH DB: the code or the ID but not both. Put the suggestion in the talk page of the property and try to contact the contributors who supported the initial property to see what is the best solution [[User:Snipre|Snipre]] ([[User talk:Snipre|talk]]) 09:47, 12 May 2013 (UTC)
:{{weak support}} Because I have no background knowlenge about this only weak support. This property can be used in [[w:en:List of MeSH codes]] and subpages. But we also need the MeSH ID to link to a special medicine term because diseases can appear in different regions of the hierarchy. --[[User:Pyfisch|Pyfisch]] ([[User talk:Pyfisch|talk]]) 16:37, 12 May 2013 (UTC)
:{{support}} --[[User:Wouterstomp|Wouterstomp]] ([[User talk:Wouterstomp|talk]]) 10:04, 6 June 2013 (UTC)
::{{support}} --[[User:Gambo7|Gambo7]] ([[User talk:Gambo7|talk]]) 20:43, 16 June 2013 (UTC)
:{{support}} --[[User:Kaligula|Kaligula]] ([[User talk:Kaligula|talk]]) 06:59, 19 June 2013 (UTC)
{{done}} --[[User:Tobias1984|Tobias1984]] ([[User talk:Tobias1984|talk]]) 09:34, 4 July 2013 (UTC)

== eMedicine ==
{{Property proposal
|status                 = 673
|description            =  online clinical medical knowledge base (See: [[:en:EMedicine]]
|infobox parameter      = [[Q6436840]] en: EMedicine
|datatype               = string
|domain                 = term
|allowed values         = 
|suggested values       =
|source                 = http://emedicine.medscape.com/
|example                = [[Q41571|epilepsy]] = "1184846" (new page name), "neuro/415" (old formatting (redirect)), [[Q41112|schizophrenia]]= "288259" and "805988" (new), "med/2072" and "emerg/520" (old)
|filter                 = 
|robot and gadget jobs  = 
|proposed by            = --[[User:Tobias1984|Tobias1984]] ([[User talk:Tobias1984|talk]]) 16:50, 1 June 2013 (UTC)
}}
;Discussion
:{{comment}} - I don't know if we should use the old or the new formatting. --[[User:Tobias1984|Tobias1984]] ([[User talk:Tobias1984|talk]]) 16:50, 1 June 2013 (UTC)
:: Definitely the new, the old one only exist anymore as redirects. Also, for many diseases multiple emedicine pages exist, how is this dealt with? --[[User:Wouterstomp|Wouterstomp]] ([[User talk:Wouterstomp|talk]]) 19:00, 1 June 2013 (UTC)
:::We have that problem with many pages on Wikipedia and items on Wikidata that they can have multiple entries in other databases. Currently the "infobox disease" just represents them as a list without any qualifiers. If you can think of a way on how we could improve this we could start a discussion at [[Wikidata:Medicine_task_force]]. --[[User:Tobias1984|Tobias1984]] ([[User talk:Tobias1984|talk]]) 19:17, 1 June 2013 (UTC)
:{{support}} --[[User:Wouterstomp|Wouterstomp]] ([[User talk:Wouterstomp|talk]]) 10:04, 6 June 2013 (UTC)
:{{support}} --[[User:Kaligula|Kaligula]] ([[User talk:Kaligula|talk]]) 06:59, 19 June 2013 (UTC)
{{done}} --[[User:Tobias1984|Tobias1984]] ([[User talk:Tobias1984|talk]]) 22:39, 5 July 2013 (UTC)

== ÚSOP ID (en) / kód ÚSOP (cs)==
{{Property proposal
|status                 = 677
|description            = A link to national database of protected areas and trees
|infobox parameter      = ''úsop'' in [[:cs:Template:Infobox chráněné území v Česku]]; ''číslo'' in [[:cs:Template:Infobox stromy]]
|datatype               = string
|domain                 = geographic feature; protected area, tree in Czech republic
|allowed values         = 
|suggested values       = 
|source                 = http://drusop.nature.cz/index.php
|example                = [[:cs:Blana]] - http://drusop.nature.cz/ost/chrobjekty/chrob_find/index.php?frame=1&h_kod=5649
|filter                 = number
|robot and gadget jobs  = Should be added by [[User:JAnDbot]]
|proposed by            = [[User:JAn Dudík|JAn Dudík]] ([[User talk:JAn Dudík|talk]]) 21:18, 28 June 2013 (UTC)
}}
;Discussion
:{{support}}--[[User:Shlomo|Shlomo]] ([[User talk:Shlomo|talk]]) 17:50, 30 June 2013 (UTC)
::{{done}} [[User:JAn Dudík|JAn Dudík]] ([[User talk:JAn Dudík|talk]]) 21:11, 6 July 2013 (UTC)

== Qualifier ''incertae sedis'' (en) ==
{{Property proposal
|status                 = 678
|description            = Qualifier for {{P|171}} to mark which intermediate ranks are incertae sedis
|infobox parameter      = every rank in [[:en:Template:Taxobox]] which has the unknown status incertae sedis for the corresponding taxon
|datatype               = item
|domain                 = taxa above genus level (terms)
|allowed values         = one or more items which are an instance of {{P|105}}, see the [[Property talk:P105|list of all feasible values]]
|suggested values       = ranks between the rank of the item and the rank of the object of P171
|source                 = External reference, Wikipedia list article (either infobox or source)
|example                = the subfamily of the genus {{Q|3008467}} (see [[:en:Cyclocorus]]) is incertae sedis (unknown) according to{{Q|13416674}}. However, it is clear that this snake belongs to the family {{Q|182751}}. Thus,  {{Q|3008467}} has {{P|171}}: {{Q|182751}}, but this needs the qualifier that the subfamily is unkown: [[incertae sedis (P???)]]: {{Q|2455704}}<br/>
:Some taxa have more than one rank incertae sedis, see [[:en:Phialophora asteris]]
|filter                 = only items in the [[Property talk:P105|list of all feasible values]], if possible
|robot and gadget jobs  = source for taxoboxes
|proposed by            = &nbsp;—&nbsp;[[User:FelixReimann|Felix&nbsp;Reimann]] ([[User talk:FelixReimann|talk]]) 15:33, 24 June 2013 (UTC)
}}
;Discussion

* It took me a while to understand your proposal. :) {{support}} --[[User:Succu|Succu]] ([[User talk:Succu|talk]]) 16:25, 25 June 2013 (UTC)
*{{support}} --[[User:Tobias1984|Tobias1984]] ([[User talk:Tobias1984|talk]]) 09:23, 4 July 2013 (UTC)
{{done}} --[[User:Tobias1984|Tobias1984]] ([[User talk:Tobias1984|talk]]) 19:14, 7 July 2013 (UTC)

== ZVG number (en) ==

{{Property proposal
|status                 = 679
|description            = ID in the [[Q52424|GESTIS database]] of the [[:en:Institute for Occupational Safety and Health|Institute for Occupational Safety and Health]]
|infobox parameter      = 
|datatype               = value
|domain                 = term
|allowed values         = 
|suggested values       = 
|source                 = 
|example                = {{Q|2270}} = “10060”; see [[Wikidata:Chemistry task force/Properties]]
|filter                 = 
|robot and gadget jobs  = 
|proposed by            = [[User:GZWDer|GZWDer]] ([[User talk:GZWDer|talk]]) 03:07, 7 June 2013 (UTC)
}}
;Discussion
* {{s}}: Well maintained database with reviewed properties. --[[User:Leyo|Leyo]] 14:50, 24 June 2013 (UTC)
* {{strong support}} crucial for references to safety data. --[[User:Saehrimnir|Saehrimnir]] ([[User talk:Saehrimnir|talk]]) 15:46, 24 June 2013 (UTC)
* {{s}}: Required for German Wikipedia's crusade to have reputable secondary sources on every chemical safety information provided. Also useful for other Wikipedias that show EU warning labels in their chemboxes. [[User:Matthias M.|Matthias M.]] ([[User talk:Matthias M.|talk]]) 20:52, 24 June 2013 (UTC)
* {{s}} very useful source for safety data. --[[User:Cvf-ps|Cvf-ps]] ([[User talk:Cvf-ps|talk]]) 10:56, 26 June 2013 (UTC)

== has_molecular_function ==
{{Property proposal
|status                 = 680
|description            = Used to represent gene ontology function annotations
|infobox parameter      = [[:en:Template:GNF_Protein_box]] = Function
|datatype               = item
|domain                 = term
|allowed values         = 
|suggested values       = 
|source                 = http://amigo.geneontology.org
|example                = [[Q414043|Reelin]] = Molecular function metal ion binding
|filter                 = 
|robot and gadget jobs  = Fill gene wikidata items with appropriate link to gene atlas image
|proposed by            = [[User:Chinmay26|Chinmay26]] ([[User talk:Chinmay26|talk]]) 17:17, 2 July 2013 (UTC)
}}
:{{comment}} - Can this be an item datatype? We can create items for e.g. "lipoprotein particle receptor binding". This will reduce the amount of translation and I'm sure that these processes can hold plenty of statements of their own. Some of them might already have Wiki articles. --[[User:Tobias1984|Tobias1984]] ([[User talk:Tobias1984|talk]]) 18:51, 2 July 2013 (UTC)
:{{support}} - agree with [[User:Tobias1984|Tobias1984]]; made the change to item-datatype and supporting.  Cheers, [[User:Andrew Su|Andrew Su]] ([[User talk:Andrew Su|talk]]) 22:46, 3 July 2013 (UTC)
:{{support}} --[[User:Tobias1984|Tobias1984]] ([[User talk:Tobias1984|talk]]) 07:49, 4 July 2013 (UTC)
:{{Comment}} A few suggestions:
::* Change label from 'has_molecular_function' to 'molecular function', which matches the GO term on which this property is based.
::* A link to guidelines for this property's use -- http://www.geneontology.org/GO.function.guidelines.shtml -- would help to have in the documentation. Having it in the 'Description' field seems to make the most sense.
::* In the 'Source' field, specify the more source more precisely: http://amigo.geneontology.org/cgi-bin/amigo/term_details?term=GO:0003674
::* Exactly how will claims involving this property be sourced?  I don't think it's critical to provide sources in the GSoC project (though it would be very nice), but I think we should establish how GO claims will eventually be sourced while everyone's thinking about GO properties.
:: I have similar suggestions for the other GO properties. [[User:Emw|Emw]] ([[User talk:Emw|talk]]) 21:26, 5 July 2013 (UTC)
{{done}} --[[User:Tobias1984|Tobias1984]] ([[User talk:Tobias1984|talk]]) 08:40, 9 July 2013 (UTC)

== occurs in cell component ==
{{Property proposal
|status                 = 681
|description            = Used to represent gene ontology location annotations
|infobox parameter      = [[:en:Template:GNF_Protein_box]] = Function
|datatype               = item
|domain                 = term
|allowed values         = 
|suggested values       = 
|source                 = http://amigo.geneontology.org
|example                = [[Q414043|Reelin]] = Reelin occurs in cytoplasm
|filter                 = 
|robot and gadget jobs  = Fill gene wikidata items with appropriate link to gene atlas image
|proposed by            = [[User:Chinmay26|Chinmay26]] ([[User talk:Chinmay26|talk]]) 17:17, 2 July 2013 (UTC)
}}
:{{comment}} - we have an item for {{Q|79899}}. Can we use item-datatype instead of string? --[[User:Tobias1984|Tobias1984]] ([[User talk:Tobias1984|talk]]) 18:42, 2 July 2013 (UTC)
:{{support}} - agree with [[User:Tobias1984|Tobias1984]]; made the change to item-datatype and supporting.  Cheers, [[User:Andrew Su|Andrew Su]] ([[User talk:Andrew Su|talk]]) 22:46, 3 July 2013 (UTC)
:{{support}} --[[User:Tobias1984|Tobias1984]] ([[User talk:Tobias1984|talk]]) 07:49, 4 July 2013 (UTC)
:{{Comment}} A few suggestions:
::* Change label from 'occurs in cell component' to 'cell component', which matches the GO term on which this property is based.
::* In the 'Source' field, specify the more source more precisely: http://amigo.geneontology.org/cgi-bin/amigo/term_details?term=GO:0005575.  
::* A link to guidelines for this property's use -- http://www.geneontology.org/GO.component.guidelines.shtml -- would help to have in the documentation.  Having it in the 'Description' field seems to make the most sense.
::* Exactly how will claims involving this property be sourced?  I don't think it's critical to provide sources in the GSoC project (though it would be very nice), but I think we should establish how GO claims will eventually be sourced while everyone's thinking about GO properties.
:: I have similar suggestions for the other GO properties. [[User:Emw|Emw]] ([[User talk:Emw|talk]]) 21:31, 5 July 2013 (UTC)
{{done}} --[[User:Tobias1984|Tobias1984]] ([[User talk:Tobias1984|talk]]) 08:55, 9 July 2013 (UTC)

== participates in biological process ==
{{Property proposal
|status                 = 682
|description            = Used to represent gene ontology process annotations
|infobox parameter      = [[:en:Template:GNF_Protein_box]] = Function
|datatype               = item
|domain                 = term
|allowed values         = 
|suggested values       = 
|source                 = http://amigo.geneontology.org
|example                = [[Q414043|Reelin]] = Reelin involved in process migration
|filter                 = 
|robot and gadget jobs  = Fill gene wikidata items with appropriate link to gene atlas image
|proposed by            = [[User:Chinmay26|Chinmay26]] ([[User talk:Chinmay26|talk]]) 17:17, 2 July 2013 (UTC)
}}
:{{comment}} - We have items for many of those processes: e.g. {{Q|33123}}. I think this should be an item property. --[[User:Tobias1984|Tobias1984]] ([[User talk:Tobias1984|talk]]) 18:56, 2 July 2013 (UTC)
:{{support}} - agree with [[User:Tobias1984|Tobias1984]]; made the change to item-datatype and supporting.  Cheers, [[User:Andrew Su|Andrew Su]] ([[User talk:Andrew Su|talk]]) 22:46, 3 July 2013 (UTC)
:{{support}} --[[User:Tobias1984|Tobias1984]] ([[User talk:Tobias1984|talk]]) 07:49, 4 July 2013 (UTC)
:{{Comment}} A few suggestions:
::* Change label from 'participates in biological process' to 'biological process', which matches the GO term on which this property is based.
::* In the 'Source' field, specify the more source more precisely: http://amigo.geneontology.org/cgi-bin/amigo/term_details?term=GO:0008150.  
::* A link to guidelines for this property's use -- http://www.geneontology.org/GO.process.guidelines.shtml -- would help to have in the documentation.  Having it in the 'Description' field seems to make the most sense.
::* Exactly how will claims involving this property be sourced?  I don't think it's critical to provide sources in the GSoC project (though it would be very nice), but I think we should establish how GO claims will eventually be sourced while everyone's thinking about GO properties.
:: I have similar suggestions for the other GO properties. [[User:Emw|Emw]] ([[User talk:Emw|talk]]) 21:33, 5 July 2013 (UTC)
{{done}} --[[User:Tobias1984|Tobias1984]] ([[User talk:Tobias1984|talk]]) 09:01, 9 July 2013 (UTC)

== ChEBI ==
{{Property proposal
|status                 = 683
|description            = {{q|902623}}:  Chemical Entities of Biological Interest, also known as ChEBI, is a database and ontology of molecular entities focused on 'small' chemical compounds, that is part of the Open Biomedical Ontologies effort.
|infobox parameter      = {{q|6033882}} ChEBI , {{Q|52426}} ChEBI 
|datatype               = string
|domain                 = term
|allowed values         = 
|suggested values       = 
|source                 =http://www.ebi.ac.uk/chebi/
|example                = {{q|407217}} = "28969", {{q|133145}} = "133145", {{q|151313}} = "18153" I didn't include the prefix "CHEBI:"
|filter                 = only digits
|robot and gadget jobs  = Gather data from infoboxes and website.
|proposed by            = --[[User:Tobias1984|Tobias1984]] ([[User talk:Tobias1984|talk]]) 07:05, 4 June 2013 (UTC)
}}
* {{strong support}}.  --[[User:Beetstra|Beetstra]] ([[User talk:Beetstra|talk]]) 13:05, 24 June 2013 (UTC)
* {{support}}--[[User:Saehrimnir|Saehrimnir]] ([[User talk:Saehrimnir|talk]]) 15:46, 24 June 2013 (UTC)
{{done}} --[[User:Tobias1984|Tobias1984]] ([[User talk:Tobias1984|talk]]) 09:36, 9 July 2013 (UTC)

== ortholog ==
{{Property proposal
|status                 = 684
|description            = orthologous genes
|infobox parameter      =
|datatype               = item
|domain                 = genes
|allowed values         = (should be a gene too, how to identify items about genes remains to be determined)
|suggested values       = 
|source                 = [http://www.ncbi.nlm.nih.gov/homologene HomoloGene @ U.S. National Center for Biotechnology Information]
|example                = {{Q|414043}} <-> {{Q|13567973}}
|filter                 = 
|robot and gadget jobs  = 
|proposed by            = See [[wikidata talk:Molecular biology task force]]
}}
:{{support}} --[[User:Tobias1984|Tobias1984]] ([[User talk:Tobias1984|talk]]) 07:49, 4 July 2013 (UTC)
:{{support}} [[User:Andrew Su|Andrew Su]] ([[User talk:Andrew Su|talk]]) 01:10, 9 July 2013 (UTC)
:{{support}} [[User: Salvatore Loguercio|Salvatore Loguercio]] ([[User talk:Salvatore Loguercio|talk]]) 17:50, 9 July 2013 (UTC)
:{{Support}} [[User:Chinmay26|Chinmay26]] ([[User talk:Chinmay26|talk]]) 18:13, 9 July 2013 (UTC)
:{{Support}}.  We should probably encourage (and maybe require) this property to be used with a {{P|89}} qualifier, to enable easier unambiguous statements when orthologs for multiple species are made with this property. [[User:Emw|Emw]] ([[User talk:Emw|talk]]) 05:23, 10 July 2013 (UTC)
{{done}} --[[User:Tobias1984|Tobias1984]] ([[User talk:Tobias1984|talk]]) 09:27, 10 July 2013 (UTC)

== NCBI Taxonomy ID ==
{{Property proposal
|status                 = 685
|description            = ID of a taxon in the Taxonomy Database by the NCBI
|infobox parameter      =
|datatype               = string
|domain                 = taxa
|allowed values         = integer
|suggested values       = 
|source                 = [http://www.ncbi.nlm.nih.gov/taxonomy Taxonomy Database @ U.S. National Center for Biotechnology Information]
|example                = {{Q|5}} -> [http://www.ncbi.nlm.nih.gov/taxonomy/9606 9606]
|filter                 =
|robot and gadget jobs  = 
|proposed by            = See [[wikidata talk:Molecular biology task force]]
}}
{{Constraint:Format|pattern=<nowiki>\d+</nowiki>}}
:{{support}} --[[User:Tobias1984|Tobias1984]] ([[User talk:Tobias1984|talk]]) 07:49, 4 July 2013 (UTC)
::Minor comment: Would you mind renaming it to "NCBI Taxon ID" or similar? Each taxonomy database defines its own "Taxonomy ID". See for example [http://img.jgi.doe.gov/cgi-bin/w/main.cgi?section=TaxonDetail&page=taxonDetail&taxon_oid=648028003]. &nbsp;—&nbsp;[[User:FelixReimann|Felix&nbsp;Reimann]] ([[User talk:FelixReimann|talk]]) 14:03, 4 July 2013 (UTC)
:::Question, I wonder if we should leave the name as "Taxonomy ID" and use {{Q|82494}} as the source.  Also relates to the discussion at[[Wikidata_talk:Molecular_biology_task_force#gene.2C_RNA.2C_and_protein_identifiers]].  Cheers, [[User:Andrew Su|Andrew Su]] ([[User talk:Andrew Su|talk]]) 18:42, 9 July 2013 (UTC)
:::: I may be missing something, but isn't there already is a property called {{Q|7432}} to which the name of a species can be assigned? As Andrew suggested in the MCB task force discussion, we could then have a property for {{Q|5}}: "Taxon ID" → "9606"  (Source: {{Q|82494}}) and "Taxon ID" → "180092" (Source: {{Q|82575}}) (note that the {{Q|3183039}} linked above uses the NCBI Taxon ID). [[User:Boghog|Boghog]]([[User talk:Boghog|talk]]) 19:54, 9 July 2013 (UTC)
:{{support}} – and per Felix&nbsp;Reimann, I also suggest renaming to "NCBI Taxonomy ID". [[User:Boghog|Boghog]] ([[User talk:Boghog|talk]]) 19:06, 4 July 2013 (UTC)
:{{support}} --[[User:Andrew Su|Andrew Su]] ([[User talk:Andrew Su|talk]]) 01:13, 9 July 2013 (UTC)
:{{Support}} [[User:Chinmay26|Chinmay26]] ([[User talk:Chinmay26|talk]]) 18:13, 9 July 2013 (UTC)
:{{support}} [[User: Salvatore Loguercio|Salvatore Loguercio]] ([[User talk:Salvatore Loguercio|talk]]) 18:39, 9 July 2013 (UTC)
{{done}} --[[User:Tobias1984|Tobias1984]] ([[User talk:Tobias1984|talk]]) 09:47, 10 July 2013 (UTC)

== Gene Ontology ID ==
{{Property proposal
|status                 =686 
|description            = ID in the Gene Ontology
|infobox parameter      =
|datatype               = string
|domain                 = molecular function, biological process, or cellular component (objects of {{P|680}} {{p|681}} {{p|682}})
|allowed values         = string
|suggested values       = 
|source                 =  [http://amigo.geneontology.org/ AmiGO] (e.g., [http://amigo.geneontology.org/cgi-bin/amigo/term_details?term=GO:0046872])
|example                = {{Q|13667380}} -> [http://amigo.geneontology.org/cgi-bin/amigo/term_details?term=GO:0046872 GO:0046872]
|filter                 =
|robot and gadget jobs  = 
|proposed by            = [[User:Andrew Su|Andrew Su]] ([[User talk:Andrew Su|talk]])
}}
{{Constraint:Format|pattern=<nowiki>^GO:\d+</nowiki>}}
: {{support}} --[[User:Andrew Su|Andrew Su]] ([[User talk:Andrew Su|talk]]) 16:41, 9 July 2013 (UTC)
:{{Support}} [[User:Chinmay26|Chinmay26]] ([[User talk:Chinmay26|talk]]) 18:13, 9 July 2013 (UTC)
:{{support}} [[User: Salvatore Loguercio|Salvatore Loguercio]] ([[User talk:Salvatore Loguercio|talk]]) 18:39, 9 July 2013 (UTC)
: {{Support}} [[User:Emw|Emw]] ([[User talk:Emw|talk]]) 05:25, 10 July 2013 (UTC)
{{done}} --[[User:Tobias1984|Tobias1984]] ([[User talk:Tobias1984|talk]]) 14:11, 11 July 2013 (UTC)

== BHL Page Id ==
{{Property proposal
|status                 = 687
|description            = Id of a page at the {{Q|172266}}
|infobox parameter      = 
|datatype               = String
|domain                 = Sourcing statements
|allowed values         = 
|suggested values       =
|source                 = 
|example                = Page ID for the publication of the scientific name {{Q|163559}} is [http://biodiversitylibrary.org/page/358022 358022]
|filter                 = 
|robot and gadget jobs  = Add <code><nowiki>'http://biodiversitylibrary.org/page/$1'</nowiki></code> to [[MediaWiki:Gadget-AuthorityControl.js|Gadget-AuthorityControl.js]]
|proposed by            = [[user:Succu|Succu]]
}}
;Discussion
{{Q|172266}} hosts a lage amount of biological works. Each page has an unique identifier. The proposed property allows a direct link to a scientific discription of a taxon. [[User:Succu|Succu]] ([[User talk:Succu|talk]]) 14:27, 26 June 2013 (UTC)
:{{support}} --[[User:Tobias1984|Tobias1984]] ([[User talk:Tobias1984|talk]]) 09:42, 9 July 2013 (UTC)
: {{support}} &nbsp;—&nbsp;[[User:FelixReimann|Felix&nbsp;Reimann]] ([[User talk:FelixReimann|talk]]) 19:55, 10 July 2013 (UTC)
: {{support}} - Hard to see how this could hurt. In some cases this will be extremely useful. - [[User:Brya|Brya]] ([[User talk:Brya|talk]]) 11:12, 11 July 2013 (UTC)
{{done}} --[[User:Tobias1984|Tobias1984]] ([[User talk:Tobias1984|talk]]) 10:20, 12 July 2013 (UTC)

== Encodes ==
{{Property proposal
|status                 = 688
|description            = the product of a gene (usually a protein or RNA)
|infobox parameter      =
|datatype               = item
|domain                 = gene
|allowed values         = protein, RNA
|suggested values       = 
|source                 = 
|example                =  {{Q|414043}} --> {{Q|13569356}}
|filter                 = 
|robot and gadget jobs  = 
|proposed by            = See [[wikidata talk:Molecular biology task force]]
}}
:{{support}} but I don't know if we should have both properties (encodes, encoded by) or just one. --[[User:Tobias1984|Tobias1984]] ([[User talk:Tobias1984|talk]]) 07:49, 4 July 2013 (UTC)
:{{support}} --[[User:Andrew Su|Andrew Su]] ([[User talk:Andrew Su|talk]]) 01:12, 9 July 2013 (UTC)
:{{Support}} [[User:Chinmay26|Chinmay26]] ([[User talk:Chinmay26|talk]]) 18:13, 9 July 2013 (UTC)
: {{Support}} <s>{{Wait}}</s> I think this property description should be modified to allow it to be used on the ''gene product'' encoded by the gene, which can be either a protein or an RNA molecule.  Consider for example [[:en:HOTAIR|HOTAIR]], which encodes an [[:en:ncRNA|ncRNA]] molecule. [[User:Emw|Emw]] ([[User talk:Emw|talk]]) 05:16, 10 July 2013 (UTC)
:: Agreed!  Great point, changed...  Cheers, [[User:Andrew Su|Andrew Su]] ([[User talk:Andrew Su|talk]]) 17:09, 11 July 2013 (UTC)
::: Thanks, this looks good to go from my perspective. [[User:Emw|Emw]] ([[User talk:Emw|talk]]) 22:52, 11 July 2013 (UTC)
{{done}} --[[User:Tobias1984|Tobias1984]] ([[User talk:Tobias1984|talk]]) 10:41, 12 July 2013 (UTC)

== afflicts ==
{{Property proposal
|status                 = 689
|description            = a type of organism which a condition or disease afflicts. 
|infobox parameter      = 
|datatype               = item
|domain                 = taxon
|allowed values         = any disease or medical condition
|suggested values       = human
|source                 = External reference, Wikipedia list article (either infobox or source)
|example                = [[Q5788570|Infectious Coryza]] => [[Q21659|Galliformes]]; [[Q133087|gout]] => [[Q5|humans]];[[Q147778|cirrhosis]] => [[Q9368|liver]]
|filter                 = 
|robot and gadget jobs  = 
|proposed by            = [[User:ColinFine|ColinFine]] ([[User talk:ColinFine|talk]])
}}
;Discussion
I was editing [[Q5788570]], and wanted to enter that it is a disease of birds, in fact of galliformes. There does not seem to be a property for this (or indeed an infobox in enwiki). I haven't found a really good name for the property, though [[User:ColinFine|ColinFine]] ([[User talk:ColinFine|talk]]) 21:35, 16 June 2013 (UTC)
: {{Support}} This property seems useful.  A few things could be adjusted in the documentation template:
::* Domain: just 'taxon'; 'term' is too imprecise
::* Allowed values: any {{Q|12136}}
: I would also change the label to simply 'afflicts'. "Gout afflicts humans" is much more natural than "Gout disease afflicts humans".  The 'disease afflicts' label is putting the range constraint in the label, when it's enough to have it in the range field of documentation template (i.e. "allowed values"). [[User:Emw|Emw]] ([[User talk:Emw|talk]]) 00:18, 17 June 2013 (UTC)
::Reply from proposer: thanks for the comments. 
::*I didn't realise that the name was supposed to be read directly as part of an English sentence: in that case, "Afflicts" is probably the best we'll get. 
::*I'd change the description to "type of organism which this medical condition afflicts" ("disease" is too narrow, I think). 
::*I put "term" in because the comment in the template I copied says "type of items that may have this property. Mention main types (person, place, organization, event, creative work, term)". I think you're saying that this instruction is wrong. 
::* I don't see where in the template there is a place so specify that the Q1 should be a disease or medical condition. Am I missing something? --[[User:ColinFine|ColinFine]] ([[User talk:ColinFine|talk]]) 15:49, 17 June 2013 (UTC)
:{{support}} --[[User:Kaligula|Kaligula]] ([[User talk:Kaligula|talk]]) 06:59, 19 June 2013 (UTC)
:{{question}} - Can this also be used to say that a certain organ is targeted by the disease? --[[User:Tobias1984|Tobias1984]] ([[User talk:Tobias1984|talk]]) 18:05, 20 June 2013 (UTC)

:{{comment}} I have updated the proposal according to the comments above: changed the name and description, and added the organ as a possible target. --[[User:ColinFine|ColinFine]] ([[User talk:ColinFine|talk]]) 16:34, 9 July 2013 (UTC)
::{{comment}} I added the organ according to Tobias' suggestion, but I see that he has proposed a separate property for this, so I have removed it from "afflicts" again. --[[User:ColinFine|ColinFine]] ([[User talk:ColinFine|talk]]) 01:00, 12 July 2013 (UTC)
{{done}} --[[User:Tobias1984|Tobias1984]] ([[User talk:Tobias1984|talk]]) 07:44, 13 July 2013 (UTC)

== Species ==
{{Property proposal
|status            = not done
|description       = species used for a toxicological measurement
|infobox parameter = used in chembox
|datatype          = item
|domain            = chemistry, biology
|allowed values    = -
|suggested values  = rat, guinea pig, mouse, human, golden fish,...
|source            = -
|example           = rat for median lethal dose (DL50)
|robot and gadget jobs = -
|proposed by      = [[User:Snipre|Snipre]] ([[User talk:Snipre|talk]]) 13:00, 18 May 2013 (UTC)
}}
:*{{comment}} - Can we just use [[Property:P89]] as a qualifier or will that mess up that property? --[[User:Tobias1984|Tobias1984]] ([[User talk:Tobias1984|talk]]) 20:43, 18 May 2013 (UTC)
:* Right, I will delete the proposal.[[User:Snipre|Snipre]] ([[User talk:Snipre|talk]]) 19:07, 10 June 2013 (UTC)
::Wait till [[Wikidata:Requests_for_comment/Inheritance_of_taxon_ranks|this RfC]] is closed, maybe ''species'' will be deleted.—[[User:23PowerZ|<font color="red">★</font>P''οωερ''<font color="black"><b>Z</b></font>]]<sub><sub>[[User talk:23PowerZ|talk]]</sub></sub>19:11, 10 June 2013 (UTC)
{{done}} --[[User:Tobias1984|Tobias1984]] ([[User talk:Tobias1984|talk]]) 07:54, 13 July 2013 (UTC)

== Space group ==
{{Property proposal
|status                 = 690
|description            = Every crystal can be assigned to one of the 230 space groups.
|infobox parameter      = [[:de:Vorlage:Infobox_Mineral]] = Raumgruppe=
|datatype               = item
|domain                 = term
|allowed values         = 230 space groups [[:en:Space_group#Table_of_space_groups_in_3_dimensions]]
|suggested values       = 230 space groups
|source                 = Scientific literature
|example                = [[Q2314|sodium chloride]] => "Space group 225" (Fm3m)  (230 space groups have to be created first), Aspirine => "space group 14" (P12<sub>1</sub>/c1), [[Q182264|albite]] =[[Q13365008|space group 2]]
|filter                 = 230 space groups
|robot and gadget jobs  = Add space group to every crystal from scientific databases
|proposed by            = --[[User:Tobias1984|Tobias1984]] ([[User talk: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 also propose to create the 230 space groups as "Space group 1" through "Space group 230". The other notations could be put into the aliases because they require special letters to be non-ambiguous which are not available for the name (horizontal bars above letters and subscript). --[[User:Tobias1984|Tobias1984]] ([[User talk:Tobias1984|talk]]) 08:25, 20 May 2013 (UTC)
:*{{comment}} - In theory we could say that "Albite" is "space group 2" and because space group 2 has the crystal class "pinacoidal" and the crystal system "triclinic", those two things could be queried. So each mineral would just get one statement, if we don't want any redundancies. --[[User:Tobias1984|Tobias1984]] ([[User talk:Tobias1984|talk]]) 16:31, 20 May 2013 (UTC)
<s>:{{oppose}}</s> to the current solution of "space group #" items. The best datatype is string with value numbers between 1 and 230. Later when complex formulas will be possible we can change numbers by the formulas. [[User:Snipre|Snipre]] ([[User talk:Snipre|talk]]) 18:34, 23 May 2013 (UTC)
::{{comment}} - I have thought about this for some time and I think we need those 230 space group items. (1) We need them to make the symmetrical classification complete. (2) Space groups have many different string designations (one string would be insufficient) (3) They have different physical properties that can't be stored with other items (e.g. phyisical, chemical, spectroscopy, deformation, magnetic, (super)conductor). (4) some already have their own commons category (5) they can link to each other by common symmetry elements. --[[User:Tobias1984|Tobias1984]] ([[User talk:Tobias1984|talk]]) 18:34, 24 May 2013 (UTC)
::: Is it possible to have other label than "space group #" ? Something a little more explicit. Just a question. [[User:Snipre|Snipre]] ([[User talk:Snipre|talk]]) 23:52, 4 June 2013 (UTC)
::::The problem is that the other names of the space groups are full of symbols that we can't use in the labels (yet). --[[User:Tobias1984|Tobias1984]] ([[User talk:Tobias1984|talk]]) 06:07, 5 June 2013 (UTC)
::::: I know about the symbols but it is just to be sure that we can't use a term even scientific and difficult to understand but which is a little more descriptive than space group 1.[[User:Snipre|Snipre]] ([[User talk:Snipre|talk]]) 11:16, 5 June 2013 (UTC)
::::::I really can't think of any other way to name the space groups. Apart from the 7 crystal systems I don't find any of the symmetry terms particular descriptive. Everybody knows what cubic symmetry is about, but when I read about a point group like "ditrigonal-scalahedral" I always have to look at a picture or the Hermann-Mauguin notation to know what it looks like. The space groups to my knowledge don't have any names, but those would be very long and equally non-descriptive. I did take a look at how WolframAlpha handles this. A search for [http://www.wolframalpha.com/input/?i=space+group+210 space group 210] returns the correct space group. But searching for the other notations which can't be inputted unambiguously returns weird results. --[[User:Tobias1984|Tobias1984]] ([[User talk:Tobias1984|talk]]) 11:37, 5 June 2013 (UTC)
:{{support}} [[User:Snipre|Snipre]] ([[User talk:Snipre|talk]]) 12:09, 7 June 2013 (UTC)
:{{Question}}: what to do with those who are in multiple spacegroups?  There are two forms of Tin, e.g., water can be crystallised in several groups, other compounds crystallise depending on the solvents or circumstances in different ways.  Can a record link to multiple 'data'?  --[[User:Beetstra|Beetstra]] ([[User talk:Beetstra|talk]]) 13:05, 24 June 2013 (UTC)
::Single items having properties that can have multiple values is a general problem of Wikidata and propably any database. We just have to find a good solution for items we don't want to split or find out which items we should split into multiple items. Probably we need a qualifier for the symmetry properties that says "valid for = cubic phase" or "valid for = iron rich phase". A similar question would be, if chirals should have separate items. --[[User:Tobias1984|Tobias1984]] ([[User talk:Tobias1984|talk]]) 15:21, 2 July 2013 (UTC)
:{{comment}} I see that the German [[:de:Vorlage:Infobox_Mineral]] has a target for this, however most of the English chemistry pages use [[:en:Template:Chembox]] <strike>which doesn't currently have a dedicated option for space group.</strike> actually strike that, it does but it's rarely used [[:en:Template:Chembox_SpaceGroup]]. The strucutre is noramlly described in the text - is that likely to be a problem? Also does this mean that we'll need to make 230 new pages on each space group?[[User:Project Osprey|Project Osprey]] ([[User talk:Project Osprey|talk]]) 13:35, 24 June 2013 (UTC)
::230 items are not very much and they will ensure that we keep translation to a minimum. Also the 230 symmetry groups have many properties themselves. So we need to create the items anyway. I don't know if a bot can gather this information from a text. Otherwise we just have to try to import this information from a crystallographic database. --[[User:Tobias1984|Tobias1984]] ([[User talk:Tobias1984|talk]]) 15:21, 2 July 2013 (UTC)
:{{support}}--[[User:Sbisolo|Sbisolo]] ([[User talk:Sbisolo|talk]]) 10:08, 15 July 2013 (UTC)
{{done}} --[[User:Tobias1984|Tobias1984]] ([[User talk:Tobias1984|talk]]) 10:49, 15 July 2013 (UTC)

== Gene Atlas Image ==
{{Property proposal
|status                 = 692
|description            = This image shows GeneAtlas expression pattern, showing where the gene is expressed across diverse anatomic tissues.
|infobox parameter      = [[:en:Template:GNF_Protein_box]] = GeneAtlas_image
|datatype               = media
|domain                 = term
|allowed values         = 
|suggested values       = 
|source                 = Wikimedia Commons
|example                = [[Q414043|Reelin]] = PBB_GE_RELN_205923_at_tn.png
|filter                 = 
|robot and gadget jobs  = Fill gene wikidata items with appropriate link to gene atlas image
|proposed by            = [[User:Chinmay26|Chinmay26]] ([[User talk:Chinmay26|talk]]) 20:11, 10 June 2013 (UTC)
}}
;Discussion
:*{{support}} [[User:Andrew Su|Andrew Su]] ([[User talk:Andrew Su|talk]]) 21:47, 10 June 2013 (UTC)
:*{{support}} --[[User:Tobias1984|Tobias1984]] ([[User talk:Tobias1984|talk]]) 10:17, 11 June 2013 (UTC)
:* {{Support}} [[User:Emw|Emw]] ([[User talk:Emw|talk]]) 13:16, 6 July 2013 (UTC)
:* {{support}} [[User: Salvatore Loguercio|Salvatore Loguercio]] ([[User talk:Salvatore Loguercio|talk]]) 18:30, 9 July 2013 (UTC)
:*{{wait}} - We should wait for this RfC first: [[Wikidata:Requests_for_comment/Image_properties:_many_properties_or_many_qualifiers]]. --[[User:Tobias1984|Tobias1984]] ([[User talk:Tobias1984|talk]]) 12:14, 10 July 2013 (UTC)
::: This property is needed for the GSoC project to put Gene Wiki infobox data onto Wikidata.  The schedule [[User:Chinmay26|here]] notes that deployment of Wikidata work onto Gene Wiki articles is intended to begin on July 20 -- three days from now.  Given that RFCs can take several months to close and Chinmay's project depends on being able to put Gene Atlas image data into Wikidata properties, I propose that we not wait for the linked RFC to resolve itself and, absent a specific alternative for how this property should behave, work with this property as it's proposed above.  Determining how image annotation should work on Wikidata is important, but that wider discussion should not block the GSoC project. [[User:Emw|Emw]] ([[User talk:Emw|talk]]) 02:43, 17 July 2013 (UTC)
{{done}} --[[User:Tobias1984|Tobias1984]] ([[User talk:Tobias1984|talk]]) 08:40, 17 July 2013 (UTC)

==Monotypic taxon==
{{Property proposal
|status=not done
|description=Whether the taxon is monotypic. (see also [//www.wikidata.org/w/index.php?title=Wikidata:Project_chat&oldid=31395103#Genus_vs_species])
|infobox parameter=
|datatype=boolean (once it will be available...)
|domain=
|allowed values=
|suggested values=
|source=
|example=
|filter=
|robot and gadget jobs=
|proposed by=[[User:ערן|Eran]] ([[User talk:ערן|talk]]) 20:41, 26 April 2013 (UTC)
}}
Sometimes there is only 1 genus in family (for example). In such cases Wikipedia have 1 article for both of them, and the taxonbox infobox shows both the family and the genus in '''bold''' + taxonom author. I think that in Wikidata should handle such cases by creating seperate entity for the family, and declaring with some property that it is monotypic. Currently boolean data type isn't[[Special:ListDatatypes|supported]], but once it would... [[User:ערן|Eran]] ([[User talk:ערן|talk]]) 20:41, 26 April 2013 (UTC)
* {{Oppose}} – No need, we can use [[P:P31|instance of]]: [[Q310890|monotypic taxon]]. And we still need items for the all ranks to indicate taxon name etc. [[User:Byrial|Byrial]] ([[User talk:Byrial|talk]]) 10:41, 9 May 2013 (UTC)
**I agree, so I'm dropping my proposal for "Monotypic taxon" property. [[User:ערן|Eran]] ([[User talk:ערן|talk]]) 14:28, 10 May 2013 (UTC)
:::As long as the different ranks are in fact one and the same taxon, I am not thrilled about the prospect of creating separate entities for it. That would be like having one item for Germany and a different item for Deutschland. I think it would be better to list all ranks, all taxon names, and all authors in one item, and separate them with qualifiers. But first we'd have to agree on a standard for that. -[[User:Soulkeeper|Soulkeeper]] ([[User talk:Soulkeeper|talk]]) 14:35, 10 May 2013 (UTC)
::::"list all ranks, all taxon names, and all authors in one item" - but all the taxon ranks properties expect entity - so for a monotypic species, do you expect to define itself as both genus and species? (e.g: in [[Q30847]] set genus and species to be [[Q30847]] (and not a seperate entity for the genus?)
{{done}} --[[User:Tobias1984|Tobias1984]] ([[User talk:Tobias1984|talk]]) 17:53, 17 July 2013 (UTC)

== Order of magnitude / Größenordnung / Ordre de grandeur ==
{{Property proposal
|status=not done
|description=Order of magnitude
|infobox parameter=
|datatype=QuantityValue
|domain=Units of measure, e.g. "_Nanosecond_ is an order of magnitude of _second_"
|allowed values=
|suggested values=
|source=
|example=
|filter=
|robot and gadget jobs=
|proposed by=[[User:OldakQuill|OldakQuill]] ([[User talk:OldakQuill|talk]]) 15:20, 2 March 2013 (UTC)
}}
*'''Comments:''' Alternative might be to have a more general property "scale". --[[User:OldakQuill|OldakQuill]] ([[User talk:OldakQuill|talk]]) 15:20, 2 March 2013 (UTC)
: {{comment}} I would suggest naming this to something like "times bigger than" and then have the datatype as an Item that defines how much does the subject have to be multiplied to get the object in it's qualifier. So a centimeter would have meter with a qualifier 100. And meter could have centimeter with a qualifier 0.01. [[User:Janjko|Janjko]] ([[User talk:Janjko|talk]]) 16:48, 19 March 2013 (UTC)
:I think a more simple solution would be "SI equivalent" (or whatever label also applieas to nanosedond). "nanosecond. SI equivalent: 10^-9 s", "mile. SI equivalent: 1609 m".--[[User:Zolo|Zolo]] ([[User talk:Zolo|talk]]) 16:58, 19 March 2013 (UTC)
:: I agree, that's better. [[User:Janjko|Janjko]] ([[User talk:Janjko|talk]]) 21:20, 20 March 2013 (UTC)
:{{oppose}} Treat 'nanosecond' like a physical constant with value>0.0001 and SI units>seconds or better yet wait to see if we can have a datatype with both value and units. [[User:Filceolaire|Filceolaire]] ([[User talk:Filceolaire|talk]]) 19:16, 16 May 2013 (UTC)
{{done}}--[[User:Tobias1984|Tobias1984]] ([[User talk:Tobias1984|talk]]) 17:55, 17 July 2013 (UTC)

== [[Q2400750|Linguasphere]] ==
{{Property proposal
|status=not done
|description=Code given to language
|infobox parameter=
|datatype=[[m:Wikidata/Data_model#Multilingual_string|Multilingual string]]
|domain=
|allowed values=
|suggested values=
|source=
|example=
|filter=
|robot and gadget jobs=
|proposed by=[[User:Monsieurbecker|Monsieurbecker]] ([[User talk:Monsieurbecker|talk]]) 08:15, 30 March 2013 (UTC)
}}
:{{Comment}} - Needs a lot more explanation. --[[User:Tobias1984|Tobias1984]] ([[User talk:Tobias1984|talk]]) 12:58, 16 May 2013 (UTC)
:{{comment}} should be monolingual string. What is a "Linguasphere". "language code" is clearer. [[User:Filceolaire|Filceolaire]] ([[User talk:Filceolaire|talk]]) 17:37, 17 May 2013 (UTC)
{{done}} --[[User:Tobias1984|Tobias1984]] ([[User talk:Tobias1984|talk]]) 17:59, 17 July 2013 (UTC)

== Cleavage (crystal) / Spaltbarkeit/ Clivage/ Спайность / Sfaldatura ==
{{Property proposal
|status            = 693
|description       = Describes the usual way that crystals cleave.
|infobox parameter = * [[:de:Vorlage:Infobox_Mineral]] |Spaltbarkeit
|datatype          = Item
|domain            = Minerals, Variants of minerals. Some rocks (schists). Other material?
|allowed values    = [[:en:Cleavage_(crystal)]]
|source            = mindat-, rruff-, mineral databases
|example           = halite = {001} + Qualifier = good '''OR:''' halite = good cleaveability + Qualifier = {001}; {001} meaning any miller indices of cubic planes (100, 010, 001)
|robot and gadget jobs = ?
|proposed by      = [[User:Tobias1984|Tobias1984]] ([[User talk:Tobias1984|talk]])
}}
Useful for infoboxes and for queries. --[[User:Tobias1984|Tobias1984]] ([[User talk:Tobias1984|talk]]) 18:31, 30 April 2013 (UTC)
:{{support}} used in fr:mineral infobox too [[User:Snipre|Snipre]] ([[User talk:Snipre|talk]]) 17:46, 21 May 2013 (UTC)
:{{support}} --[[User:Chris.urs-o|Chris.urs-o]] ([[User talk:Chris.urs-o|talk]]) 12:08, 22 May 2013 (UTC)
:{{support}} - using "halite = {001} + Qualifier = good" --[[User:Sbisolo|Sbisolo]] ([[User talk:Sbisolo|talk]]) 12:51, 22 May 2013 (UTC)
::Would "string" be the more appropriate datatype then. I don't know if items for Miller indices would be a good idea. --[[User:Tobias1984|Tobias1984]] ([[User talk:Tobias1984|talk]]) 07:03, 25 May 2013 (UTC)
::On the other hand some of these miller indices also have names. So it might be a good idea after all. --[[User:Tobias1984|Tobias1984]]([[User talk:Tobias1984|talk]]) 13:52, 26 May 2013 (UTC)
{{done}} --[[User:Tobias1984|Tobias1984]] ([[User talk:Tobias1984|talk]]) 18:15, 17 July 2013 (UTC)

== Replaced synonym (nom. nov.) ==
{{Property proposal
|status                 = 694
|description            = „The legitimate or illegitimate, previously published name on which a replacement name (avowed substitute, nomen novum) is based.“ (see ICN-[http://www.iapt-taxon.org/nomen/main.php?page=glo Glossary] and ICN-Art. [http://www.iapt-taxon.org/nomen/main.php?page=art6#6.11 6.11])
|infobox parameter      = 
|datatype               = Item
|domain                 = Scope of [[Q693148|{{label|Q693148}}]] (ICN)
|allowed values         = 
|suggested values       =
|source                 = 
|example                = ''[[Q391711|{{label|Q391711}}]]'' Replaced synonym is ''Bravoa geminiflora'' 
|filter                 = Single value
|robot and gadget jobs  = 
|proposed by            = [[User:Succu|Succu]] ([[User talk:Succu|talk]])
}}
;Discussion
Helps to bring together otherwise not linked taxon names. Similar to {{P|566}} but author and epithet are replaced. [[User:Succu|Succu]]([[User talk:Succu|talk]]) 12:30, 21 May 2013 (UTC)
:{{support}} &nbsp;—&nbsp;[[User:FelixReimann|Felix&nbsp;Reimann]] ([[User talk:FelixReimann|talk]]) 19:55, 10 July 2013 (UTC)
{{done}} --[[User:Tobias1984|Tobias1984]] ([[User talk:Tobias1984|talk]]) 19:07, 17 July 2013 (UTC)

== UN number ==
{{Property proposal
|status                 = 695
|description            = four-digit numbers that identify hazardous substances, and articles (such as explosives, flammable liquids, toxic substances, etc.) in the framework of international transport
|infobox parameter      = fr:infobox chimie, en:chembox, de:Chemikalien
|datatype               = string
|domain                 = chemistry
|allowed values         = number
|suggested values       =
|source                 = [http://www.unece.org/fileadmin/DAM/trans/danger/publi/adr/adr2011/English/VolumeI.pdf ADR 2011]
|example                = {{Q|407577}} = 1687
|filter                 = -
|robot and gadget jobs  = -
|proposed by            = [[User:Snipre|Snipre]] ([[User talk:Snipre|talk]]) 12:12, 8 July 2013 (UTC)
}}
:Discussion:
{{support}} --[[User:Tobias1984|Tobias1984]] ([[User talk:Tobias1984|talk]]) 18:43, 8 July 2013 (UTC)
{{done}} --[[User:Tobias1984|Tobias1984]] ([[User talk:Tobias1984|talk]]) 19:15, 17 July 2013 (UTC)

== Neurolex ID ==
{{Property proposal
|status                 = 696
|description            = ID in the neurolex database.
|infobox parameter      = {{Q|10977159}}
|datatype               = string
|domain                 = term
|allowed values         = http://neurolex.org/wiki/Main_Page
|suggested values       = 
|source                 = http://neurolex.org/wiki/Main_Page
|example                = {{Q|147298}} = http://neurolex.org/wiki/Sao1103104164 or "Sao1103104164"
|filter                 = 
|robot and gadget jobs  = 
|proposed by            = --[[User:Tobias1984|Tobias1984]] ([[User talk:Tobias1984|talk]]) 13:38, 10 July 2013 (UTC)
}}
;Discussion
: {{support}} -- [[User:Andrew Su|Andrew Su]] ([[User talk:Andrew Su|talk]]) 21:19, 11 July 2013 (UTC)
{{done}} --[[User:Tobias1984|Tobias1984]] ([[User talk:Tobias1984|talk]]) 20:19, 17 July 2013 (UTC)

== Ex taxon author(s) ==
{{Property proposal
|status                 = 697
|description            = Person(s) to whom the {{P|405}} wish to ascribe a taxon name, denoted by ''ex''. See eg. ICN-Art. [http://www.iapt-taxon.org/nomen/main.php?page=art46#46.10 46.10])
|infobox parameter      = 
|datatype               = Item
|domain                 = Scope of [[Q693148|{{label|Q693148}}]] (ICN)
|allowed values         = 
|suggested values       =
|source                 = 
|example                =  
|filter                 = Single value
|robot and gadget jobs  = 
|proposed by            = [[User:Succu|Succu]] ([[User talk:Succu|talk]])
}}
;Discussion
Missing property which allows to construct author citations like [[Q27187|Magnoliales]] [[Q223963|Juss.]] ex [[Q940150|Bercht.]] & [[Q379593|J.Presl]]. [[User:Succu|Succu]] ([[User talk:Succu|talk]]) 12:30, 21 May 2013 (UTC)
:{{support}} required for many plant taxons. &nbsp;—&nbsp;[[User:FelixReimann|Felix&nbsp;Reimann]] ([[User talk:FelixReimann|talk]]) 13:39, 9 July 2013 (UTC)
:Clearly, something needs to be done about author citations. Most likely the best thing would be a text field, as in the "description", as there are many permutations ([//www.wikidata.org/w/index.php?title=Property_talk:P405&oldid=54321611#Author_citations see here]). However if an itemized data structure is desired the following will go a long way:
<hr>
:basionym ex-author1
:basionym ex-author2
:basionym ex-author3
:etc

:basionym author1
:basionym author2
:basionym author3
:etc

:basionym year 

:valid ex-author1
:valid ex-author2
:valid ex-author3
:etc

:valid author1
:valid author2
:valid author3
:etc

:valid year

: {{comment}} With {{P|405}} you can add an infinite number of authors and qualify {{P|225}} with {{P|574}}. You can do this with {{P|566}} too. --[[User:Succu|Succu]] ([[User talk:Succu|talk]]) 19:26, 9 July 2013 (UTC)

<hr>

:''Andinobates'' Twomey, Brown, Amézquita & Mejía-Vargas, 2011
::[ animal ]

:valid author1 = Twomey
:valid author2 = Brown
:valid author3 = Amézquita
:valid author4 = Mejía-Vargas

:valid year = 2011

<hr>

:''Kniphofia uvaria'' (L.) Oken (1841)
::[ plant ]

:basionym author1 = L.

:valid author1 = Oken 

:valid year = (1841)

<hr>

:''Andinobates daleswansoni'' (Rueda-Almonacid, Rada, Sánchez-Pacheco, Velásquez-Álvarez, and Quevedo-Gil, 2006)
::[ animal ]

:basionym author1 = Rueda-Almonacid
:basionym author2 = Rada
:basionym author3 = Sánchez-Pacheco
:basionym author4 = Velásquez-Álvarez
:basionym author5 = Quevedo-Gil

:basionym year  = 2006

:[ Note no "valid author" as the zoological Code omits the author(s) of the combination ]

<hr>

:''Lithocarpus polystachyus'' (Wall. ex A. DC.) Rehder (1919)
::[plant]

:basionym ex-author1 = Wall.

:basionym author1 = A.DC.

:valid author = Rehder 

:valid year = (1919)

<hr>

:''Gentianales'' Juss. ex Bercht. & J.Presl (1820)
::[plant]

:valid ex-author1 = Juss.

:valid author1 = Bercht.
:valid author2 = J.Presl

:valid year = (1820)

<hr>

:''Bacillus subtilis'' (Ehrenberg 1835) Cohn 1872
::[ prokaryote ]

:basionym author1 = Ehrenberg 

:basionym year = 1835

:valid author1 = Cohn 

:valid year = 1872

<hr>

:But most likely, very many users will think this is too hard to understand, and will get tangled in it. Safest is a normal text field. - [[User:Brya|Brya]] ([[User talk:Brya|talk]]) 16:53, 9 July 2013 (UTC)

{{done}} --[[User:Tobias1984|Tobias1984]] ([[User talk:Tobias1984|talk]]) 08:49, 18 July 2013 (UTC)

== Pubmed ID (PMID) ==
{{Property proposal
|status                 = 698
|description            = ID for journal articles/abstracts in pubmed, useful as a source for claims
|infobox parameter      = ?
|datatype               = string
|domain                 = term
|allowed values         =
|suggested values       =
|source                 = http://www.ncbi.nlm.nih.gov/pubmed
|example                = http://www.ncbi.nlm.nih.gov/pubmed/6888443 = "6888443"
|filter                 = 
|robot and gadget jobs  = ?
|proposed by            = [[User:Tobias1984|Tobias1984]] ([[User talk:Tobias1984|talk]])
}}
;Discussion
: {{strong support}} Will be used extensively in our efforts to import Gene Ontology annotations...  Cheers, [[User:Andrew Su|Andrew Su]] ([[User talk:Andrew Su|talk]]) 21:12, 11 July 2013 (UTC)
: {{Support}} [[User:Emw|Emw]] ([[User talk:Emw|talk]]) 03:30, 18 July 2013 (UTC)
{{done}} --[[User:Tobias1984|Tobias1984]] ([[User talk:Tobias1984|talk]]) 08:56, 18 July 2013 (UTC)

== Disease Ontology ID ==
{{Property proposal
|status                 = 699
|description            = ID in the Disease Ontology
|infobox parameter      = None yet, but being prototyped in [[:w:Template:Infobox_disease/sandbox2]] 
|datatype               = string
|domain                 = disease
|allowed values         = 
|suggested values       = 
|source                 = http://disease-ontology.org/
|example                = {{Q|938205}} -->  [http://disease-ontology.org/term/DOID%3A769/ DOID:769]
|filter                 = 
|robot and gadget jobs  = 
|proposed by            = --[[User:Andrew Su|Andrew Su]] ([[User talk:Andrew Su|talk]])
}}
;Discussion
: {{support}} -- [[User:Andrew Su|Andrew Su]] ([[User talk:Andrew Su|talk]]) 21:19, 11 July 2013 (UTC)
: {{support}} [[User:Emw|Emw]] ([[User talk:Emw|talk]]) 03:32, 18 July 2013 (UTC)
{{done}} --[[User:Tobias1984|Tobias1984]] ([[User talk:Tobias1984|talk]]) 09:05, 18 July 2013 (UTC)

== Hazard Identification Number or Kemler code ==
{{Property proposal
|status                 = 700
|description            = code describing the hazards of a chemical in tranport
|infobox parameter      = fr:infobox chimie, en:chembox, de:Chemikalien
|datatype               = string
|domain                 = chemistry
|allowed values         = number or alphanumeric code
|suggested values       =
|source                 = [http://www.unece.org/fileadmin/DAM/trans/danger/publi/adr/adr2011/English/VolumeI.pdf ADR 2011]
|example                = {{Q|407577}} = 60
|filter                 = -
|robot and gadget jobs  = -
|proposed by            = [[User:Snipre|Snipre]] ([[User talk:Snipre|talk]]) 12:12, 8 July 2013 (UTC)
}}
:Discussion:
:{{support}} --[[User:Tobias1984|Tobias1984]] ([[User talk:Tobias1984|talk]]) 18:56, 8 July 2013 (UTC)
{{done}} --[[User:Tobias1984|Tobias1984]] ([[User talk:Tobias1984|talk]]) 13:23, 18 July 2013 (UTC)