Wikidata:Property proposal/Archive/14

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

Official website / Offizielle Homepage / Site officiel / Sito ufficiale

Status:    Done

→ Property:P856

• Description: official website of a person
• Datatype: Item IRI
• Links:
• Infobox parameter example:
• Comments: --Nizil Shah (talk) 20:08, 4 February 2013 (UTC)

(See also Wikidata:Property_proposal/Archive/1#Official_website)

Should be datatype IRI.--Magnus Manske (talk) 16:31, 5 February 2013 (UTC)

 Oppose me suena a spam. --LadyInGrey (talk) 23:50, 5 February 2013 (UTC)

 Support when IRI datatype is available. But we need to choose which websites are acceptable (e.g. only personal website, not social media pages).--Stryn (talk) 07:50, 6 February 2013 (UTC)

 Support IRI for any entity's official web site. There is no spam problem as by definition if the subject has an Item on Wikidata, it is "notable".Espeso (talk) 18:43, 7 February 2013 (UTC)

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

•  Done: official website (P856). --Yair rand (talk) 22:49, 10 September 2013 (UTC)

URL/Website

   Done: reference URL (P854) (Talk and documentation)

Description	should be used for internet urls as references
Data type	IRI-invalid datatype (not in Module:i18n/datatype)
Domain	references
Example	Q1294046 to have the source http://www.newscientist.com/article/mg19726462.000-histories-the-male-military-surgeon-who-wasnt.html that the sex is unknown.
Proposed by	Sk!d (talk) 13:09, 21 March 2013 (UTC)

 Support Preferably sooner rather than later. However I believe the IRI datatype isn't deployed yet. Is it worth setting up the property with a string datatype in the meantime? --Avenue (talk) 01:19, 22 March 2013 (UTC)

 Support, too. I think there's consensus for doing this, so I'll move this section to the pending properties. --Ricordisamoa 08:41, 24 March 2013 (UTC)

 Support --DangSunM (talk) 22:30, 10 September 2013 (UTC)

 Done reference URL (P854) is created--DangSunM (talk) 22:30, 10 September 2013 (UTC)

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

Original discussion for Property:P370, but also applicable for Property:P855.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Ok here we go:

1. Sandbox-CommonsMediaFile (P368)
2. Sandbox-Item (P369)
3. 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 pending page:

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

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

CNKI / 中国知识基础设施工程

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

Description	China National Knowledge Infrastructure （CNKI）. Referencing may use the China Integrated Knowledge Resources Database, the main work of CNKI.
Data type	string or IRI-invalid datatype (not in Module:i18n/datatype)
Domain	mainly articles from newpapers, journals, magazines published within mainland China. Some magazines and newspapers can also be found in CNKI like People's Daily(Q54340)Qiushi(Q3429265)
Allowed values	I was thinking about the identification for items of CNKI. There is no formal identification method for CNKI.
Source	[1]
Proposed by	凡其Fanchy

It can be a replacement of DOI for items in CNKI. Although CNKI has been appointed as a registration agency in China, I didn't find the DOI for items in CNKI. [2] --凡其_Fanchy 16:34, 4 May 2013 (UTC)

Waiting for the IRI type is better. CNKI is quite a mess, although it is the most comprehensive academic full-text database in China--凡其_Fanchy 10:58, 13 May 2013 (UTC)

There's a en:Template:CNKI but I'm not sure how it is constructed. Liangent (talk) 18:53, 1 June 2013 (UTC)

Obviously it is designed for the English version CNKI. I guess only articles with English titles and abstracts will be shown on that English version--凡其_Fanchy 19:35, 1 June 2013 (UTC)

There is [3] corresponding to [4], and the www.cnki.com.cn site doesn't seem English-only. Liangent (talk) 16:01, 3 June 2013 (UTC)

Here is also a same paper [5] . That is why I say it is a mess. A paper is shown on three different place.--凡其_Fanchy 16:36, 3 June 2013 (UTC)

A fourth place [6]--凡其_Fanchy 16:43, 3 June 2013 (UTC)

e-archiv.li ID

   Done: e-archiv.li ID (P860) (Talk and documentation)

Description	identifier in directory of sources e-archiv.li of Landesarchiv (Q14563947)
Data type	String
Allowed values	\d+
Example	Gundakar, Prince of Liechtenstein (Q1554560) => 30758

• Added the template above. Someone might want to propose/create it --  Docu  at 19:49, 12 August 2013 (UTC)
•  Support--Micru (talk) 01:19, 17 August 2013 (UTC)
•  Support--Danrok (talk) 21:32, 6 September 2013 (UTC)

ESPN SCRUM ID (en)

   Done: ESPNscrum player ID (P858) (Talk and documentation)

Description	An identifier for any international rugby union player, from the site www.espnscrum.com
Data type	String
Domain	persons
Example	Jonny Wilkinson => 12757
Source	stats.espnscrum.com
Proposed by	Blackcat (talk) 12:01, 7 July 2013 (UTC)

Discussion

(English) The website www.espnscrum.com provides stats for any international rugby union player. It is provided in the form http://www.espnscrum.com/statsguru/rugby/player/12757.html (in this example, Jonny Wilkinson) where the number in bold is the parametre used in the template Scrum and in its correspondants in Italian and French language. The property should indicate for each international rugby union player this number.
(Français) paramètre qui correspond au code d'identification du joueur du rugby à XV affiché dans l'adresse web (example: http://www.espnscrum.com/statsguru/rugby/player/13317.html pour Sébastien Chabal)
(Italiano) la proprietà dovrebbe indicare il numero della pagina html corrispondente al rugbista a 15 le cui statistiche sono indicate nel sito www.espnscrum.com (per esempio http://www.espnscrum.com/statsguru/rugby/player/10657.html per Diego Domínguez. Tale proprietà va indicata come campo del template Scrum, che ha corrispondenti anche sui capitoli in francese e in inglese di Wikipedia. Blackcat (talk) 12:01, 7 July 2013 (UTC)

Sponsor (en) / Sponsor (fr)

   Done: sponsor (P859) (Talk and documentation)

Description	Enterprise that sponsorise this item
Data type	Item
Domain	person, organization, event
Allowed values	type of linked items,allowed values (if limited)
Example	Sample: Cristiano Ronaldo (Q11571) => Nike (Q483915)
Source	External reference, Wikipedia list article (either infobox or source)
Proposed by	Zil (talk) 21:18, 6 August 2013 (UTC)

Discussion

 Support should use time qualifiers. --Tobias1984 (talk) 21:44, 6 August 2013 (UTC)

 Question Should I copy it to the organisation and event section? Zil (talk) 23:48, 7 August 2013 (UTC)

 Comment support the idea, this needed. But is there another way to go about this? Many things are financed by other entities. Perhaps, one property for all financial backers, and a qualifier to indicate that they are a sponsor, provided a grant, or whatever. The applies to part (P518) could be the qualifier. Danrok (talk) 22:23, 27 August 2013 (UTC)

 Support but it needs to be renamed 'Sponsored by' if it is to be used as your example.

•  Support Its scope can be extended to cover w:patronage. Example: Horace (Q6197) <sponsored / patronage by> Gaius Maecenas (Q8833).--Micru (talk) 13:32, 28 August 2013 (UTC)

 Comment I think patronage should be a separate property. Danrok (talk) 12:37, 31 August 2013 (UTC)

• Already done, but I still will  Oppose. Sponsors are trivial information, and some people (eg. sportspeople) have so many sponsors, and it's not even possible to find reliable sources for all of them. And some can be sponsor just few days, some longer. How do we get this all by sourced? --Stryn (talk) 07:19, 12 September 2013 (UTC)

English Premiership ID

   Done: PremiershipRugby.com player ID (P861) (Talk and documentation)

Description	An unique identifier for each rugby union player who plays - or played - the English Premiership
Data type	String
Template parameter	Statistiche English Premiership on it.wiki, field #1
Domain	Persons
Example	Owen Farrell => http://www.premiershiprugby.com/matchcentre/fixtures/squads.php?player=79207&includeref=dynamic - The player number is 79207
Source	www.premiershiprugby.com/stats/player.php
Robot and gadget jobs	Collecting data from existent articles on it.wiki
Proposed by	Blackcat (talk)

Discussion

The goal of this property is to provide for each wiki the id number of each rugby union player who plays or has played in the English Premiership. Blackcat (talk) 11:46, 17 August 2013 (UTC)

•  Support similar idea to other properties created. Danrok (talk) 19:27, 29 August 2013 (UTC)

   Comment thanks Danrock, you mean that you have already proposed similar properties for identifying players by tournament? -- Blackcat (talk) 19:23, 30 August 2013 (UTC)

 Comment No, just saying that we have other properties for a variety of subjects which work along the same lines as this. That's one reason why I am supporting it. Danrok (talk) 12:59, 31 August 2013 (UTC)

 Comment the label may need to be premiershiprugby.com ID if this ID is that web site's own reference, and not an official ID for the player. Danrok (talk) 13:04, 31 August 2013 (UTC)

 Comment No problem for me to name it that way. Anyways that's the English Premiership's official website, and the player ID was the same even when it was known as guinnesspremiership.com. As a matter of fact the official Pro12's website shares the same IDs with the English Premiership's, see i.e. Brent Cockbain both in English Premiership and in the Pro12. I may suppose you agree also on this proposal? -- Blackcat (talk) 13:42, 31 August 2013 (UTC)

United States Navy aircraft designation

   Done: United States Navy aircraft designation (P847) (Talk and documentation)

Description	aircraft identifier as per United States Navy from 1922 to 1962
Data type	String
Domain	aircraft assigned designations by the United States Navy
Allowed values	alpha-numeric string
Example	Grumman S-2 Tracker => S2F
Source	w:en:1922 United States Navy aircraft designation system
Proposed by	Joshbaumgartner (talk) 12:49, 12 May 2013 (UTC)

 Info This is a distinct designation issued publicly by the US Navy. These designations were widely used and were the official designation/name for any aircraft in service with the US Navy from 1922 to 1962. Joshbaumgartner (talk) 12:49, 12 May 2013 (UTC)

 Support Danrok (talk) 15:41, 29 August 2013 (UTC)

 Support — Ivan A. Krestinin (talk) 18:02, 29 August 2013 (UTC)

United States Army aircraft designation

   Done: United States Army and Air Force aircraft designation (P897) (Talk and documentation)

Description	aircraft identifier as per United States Army and Air Force from 1924 to 1962
Data type	String
Domain	aircraft assigned designations by the United States Army and Air Force
Allowed values	alpha-numeric string
Example	Beechcraft Model 18 => C-45
Source	w:en:1924 United States Army Air Service aircraft designation system
Proposed by	Joshbaumgartner (talk) 12:49, 12 May 2013 (UTC)

 Info This is a distinct designation issued publicly by the US Army and Air Force. These designations were widely used and were the official designation/name for any aircraft in service with the US Army Air Service, Army Air Forces, and United States Air Force from 1924 to 1962. Joshbaumgartner (talk) 12:49, 12 May 2013 (UTC)

 Support Danrok (talk) 15:41, 29 August 2013 (UTC)

 Support — Ivan A. Krestinin (talk) 18:02, 29 August 2013 (UTC)

Japanese military aircraft designation

   Done: Japanese military aircraft designation (P849) (Talk and documentation)

Description	aircraft designation per the Japanese military
Data type	String
Domain	aircraft operated by Japan
Example	Douglas DC-3 => L2D
Source	w:en:Japanese military aircraft designation systems
Proposed by	Joshbaumgartner (talk) 12:49, 12 May 2013 (UTC)

 Info Japan has usually employed its own system of aircraft designations to identify aircraft, both of domestic and foreign origin. Joshbaumgartner (talk) 12:49, 12 May 2013 (UTC)

 Support Danrok (talk) 15:42, 29 August 2013 (UTC)

 Support — Ivan A. Krestinin (talk) 18:03, 29 August 2013 (UTC)

Operational Requirement

   Done: Operational Requirement of the UK Air Ministry (P862) (Talk and documentation)

Description	specification for future military aircraft by the UK Air Ministry
Data type	String
Domain	aircraft
Example	Supermarine Spitfire => OR.92
Source	w:en:Operational Requirement
Proposed by	Joshbaumgartner (talk) 12:49, 12 May 2013 (UTC)

 Info Development specifications for several British aircraft projects, officially issued by the Air Ministry. Joshbaumgartner (talk) 12:49, 12 May 2013 (UTC)

 Support Source: List of Air Ministry specifications. Danrok (talk) 14:43, 30 August 2013 (UTC)

Indiana Philosophy Ontology (InPhO) identifier (en)

   Done: InPhO ID (P863) (Talk and documentation)

Description	link to the Indiana Philosophy Ontology project
Data type	String
Domain	person, place, organization, event, creative work, term
Example	lambda calculus (Q242028) => https://inpho.cogs.indiana.edu/idea/5512.html
Format and edit filter validation	numeric identifier
Proposed by	—Ruud 11:45, 16 July 2013 (UTC)

Discussion

 Support Danrok (talk) 14:44, 30 August 2013 (UTC)

ACM Digital Library author identifier (en)

   Done: ACM Digital Library author ID (P864) (Talk and documentation)

Description	Association for Computing Machinery Digital Library (ACM DL) author identifier
Data type	String
Domain	person
Example	Edmund M. Clarke (Q92819) => http://dl.acm.org/author_page.cfm?id=81100393517
Format and edit filter validation	number
Source	ACM Digital Library
Proposed by	—Ruud 20:14, 16 July 2013 (UTC)

Discussion

 Support Danrok (talk) 14:45, 30 August 2013 (UTC)

BMLO

   Done: BMLO ID (P865) (Talk and documentation)

Description	Bayerisches Musiker-Lexikon Online (Q47191)
Data type	String
Template parameter	de:Vorlage:BMLO
Domain	person
Allowed values	[a-z][0-9]{4}
Example	Lorenz Hauslaib (Q11933906) => h1795
Robot and gadget jobs	available
Proposed by	Qk (talk) 14:53, 31 July 2013 (UTC)

• edited description above --  Docu  at 19:13, 8 August 2013 (UTC)

 Support Danrok (talk) 14:46, 30 August 2013 (UTC)

Perlentaucher (en) / Perlentaucher (de)/ Perlentaucher (fr)

   Done: Perlentaucher ID (P866) (Talk and documentation)

Description	identifier in Perlentaucher (Q2071388)
Data type	String
Template parameter	de:Vorlage:Perlentaucher
Domain	person, creative work
Example	James D. Watson (Q83333) => "12293" or "james-d-watson" => http://www.perlentaucher.de/autor/james-d-watson.html
Source	External reference
Proposed by	Pltcult (talk) 19:35, 3 August 2013 (UTC)

Discussion

•  Support --Kolja21 (talk) 12:23, 12 August 2013 (UTC)
•  Support Danrok (talk) 15:44, 29 August 2013 (UTC)

ROME Occupation Code (en) / ROME-Berufscode (de) / Code ROME du métier (fr)

   Done: ROME Occupation Code (v3) (P867) (Talk and documentation)

Description	ROME Code for a given occupation in France
Data type	String
Template parameter	Code ROME (France)
Domain	profession (Q28640),occupation (Q13516667),job
Allowed values	1 letter followed by a 4 digit number
Example	value for librarian (Q182436) is : K1601 (v3 code). You can add the full v3 description "Gestion de l'information et de la documentation". You can also add the v3 job titles. You can also add a couple of matching v2 codes along with their descriptions and their several associated job titles. V3 is simplified when compared to V2, but some articles on WP:FR use V2, and many French website still use V2.
Format and edit filter validation	check that it's 1 letter followed by a 4 digit number, and against this list.
Source	unofficial list with various names for each code, and v2/v3 code mappings, the WP-fr article explaining the system, and the official yet less detailed list
Robot and gadget jobs	robots can check the code exists by tweaking the codeRome parameter: http://recrutement.pole-emploi.fr/fichesrome/ficherome?codeRome=XXXXX&domaine=Candidat
Proposed by	2A01:E35:2EA8:950:AC1F:7C8:3AB9:BD5F 12:10, 13 August 2013 (UTC)

Discussion

1.  Support used by french administration. TomT0m (talk) 13:52, 25 August 2013 (UTC)
2.  Support Danrok (talk) 15:45, 29 August 2013 (UTC)

Foods traditionally associated / / / خوراک سنتی

   Done: foods traditionally associated (P868) (Talk and documentation)

Description	foods consumed during the ceremony
Data type	Item
Template parameter	Three foods (i.e. Samanu, Ajîl-e Moshkel-goshâ and Sabzi Polo) named in en:Template: Nowruz Traditions
Domain	subject domain is ceremonies, celebrations, festivals and holidays; object domain is cuisine, sweets and foods
Example	w:en:Chinese_new_year#Cuisine
Source	en:Template: Nowruz Traditions
Proposed by	دوستدار ایران بزرگ (talk)

Special festivals are observed during New Year holidays. During these days people usually consume special meals. In countries like Iran and China, these are traditionally cooked from old times during each New Year called "nowruz" and "Nián Jié", respectively. These are often specific sweets or foods symbolizing happiness. دوستدار ایران بزرگ (talk) 10:19, 19 April 2013 (UTC)

•  Comment the source provided doesn't appear to be a source for this information. Danrok (talk) 23:58, 26 June 2013 (UTC)
•  Support. I've rewritten the English name to better match the description. This property can also be used to link places to foods associated with them. Filceolaire (talk) 19:50, 15 August 2013 (UTC)
• I changed the Persian name Doostdar (talk) 17:00, 17 August 2013 (UTC)

 Comment Still no information on how this would be reliably sourced. Danrok (talk) 02:31, 27 August 2013 (UTC)

 Support Danrok (talk) 22:08, 29 August 2013 (UTC)

printed by

   Done: printed by (P872) (Talk and documentation)

Description	organization that printed the creative work (if different from "publisher")
Data type	Item
Example	Gutenberg Bible (Q158075) => Johannes Gutenberg (Q8958)
Proposed by	Micru (talk)

Discussion

Motivation: Sometimes publisher and printer differ. --Micru (talk) 15:37, 22 August 2013 (UTC)

•  Comment example? --Tobias1984 (talk) 18:13, 22 August 2013 (UTC)

• Updated.--Micru (talk) 18:27, 22 August 2013 (UTC)

•  Support Is there even a publisher in that case? --Tobias1984 (talk) 18:39, 22 August 2013 (UTC)
•  Support Danrok (talk) 17:00, 28 August 2013 (UTC)

Instrumentation

   Done: instrumentation (P870) (Talk and documentation)

Description	Combination of musical instruments employed in a composition,
Data type	Item
Domain	creative work/ musical compositions
Example	Cello Sonata (Q2747188) -> cello (Q8371), piano (Q5994)
Robot and gadget jobs	It can be imported from IMSLP
Proposed by	--Micru (talk) 17:13, 15 August 2013 (UTC)

Discussion

 Support--Micru (talk) 17:13, 15 August 2013 (UTC)

PORT identifier / PORT.hu-azonosító

   Done: PORT film ID (P905) (Talk and documentation)

Description	the PORT-network identifier of film or television program
Data type	String
Template parameter	"PORT.hu" and "porthu id" in hu:sablon:film infobox and hu:sablon:televíziós műsor infobox "PORT.ro" in ro:Format:Infocaseta Film
Domain	creative work
Example	Q980041 => 118830 hu, ro, cz, sk, hr, rs
Source	http://port.hu/, huwiki, etc.
Robot and gadget jobs	Could be imported from infoboxes (see above), hu:Sablon:PORT.hu-film, and en:Template:PORT.hu film
Proposed by	Matthew Beta (talk)

Discussion

PORT is a very popular (multilanguage) cultural website in the Carpathian region. It is widely used on huwiki. Matthew Beta (talk) 16:17, 3 May 2013 (UTC)

•  Support Danrok (talk) 13:54, 9 June 2013 (UTC)
•  Support Pikolas (talk) 02:11, 29 August 2013 (UTC)

Phase point

   Done: phase point (P873) (Talk and documentation)

Description	phase point to describe critical point and triple point, use of qualifier to describe the pressure, the temperature and the matter phase characterizing the point
Data type	Item
Domain	term
Allowed values	critical point (Q111059),triple point (Q106410)
Example	see Wikidata:Chemistry_task_force/Properties.
Proposed by	Snipre (talk) 19:23, 12 June 2013 (UTC)

Discussion

According to discussion below Snipre (talk) 19:23, 12 June 2013 (UTC)

Examples

water (Q283):

phase point (item):triple point (Q106410)

temperature (number): XXX K

pressure (number): XXX Pa

phase of matter (P515) (item):solid

phase of matter (P515) (item):vapor

phase of matter (P515) (item):liquid

water (Q283):

phase point (item):critical point (Q111059)

temperature (number): XXX K

pressure (number): XXX Pa

Votes

•  Support - This looks like a good solution to me, but there are still some things to work out. What should we do in this case:

phase of matter (P515) (item):solid

phase of matter (P515) (item):solid

phase of matter (P515) (item):solid

There might be more than one point described by this combination (see picture). A possible solution would be to use:

phase of matter (P515) (item):Ice I

phase of matter (P515) (item):Ice II

phase of matter (P515) (item):Ice III

Does anybody know how this would influence queries? --Tobias1984 (talk) 21:06, 12 June 2013 (UTC)

Right, for each solid form we need an item. And I dont see an issue with taht structure for query. Do you have an example ? Snipre (talk) 11:41, 15 June 2013 (UTC)

 Support Snipre (talk) 14:15, 28 June 2013 (UTC)

LIR

   Done: Lexicon istoric retic ID (P886) (Talk and documentation)

Description	identifier in the Lexicon istoric retic (LIR), Romansh variant of Historical Dictionary of Switzerland (Q642074)
Data type	String
Template parameter	"1=" in rm:Template:E-LIR, "rm=" in en:Template:HDS, possibly some others in Template:HDS (Q6235090)
Domain	all: e.g. persons, places, organizations, terms related to the Grisons
Example	Rom (Q688171) = 2639
Proposed by	- Vacallo (talk) 05:25, 3 June 2013 (UTC)

•  Support Appears to be similar to other library references already created as properties. Danrok (talk) 15:20, 29 August 2013 (UTC)

based on heuristic

   Done: based on heuristic (P887) (Talk and documentation)

Description	The property is determined based on some heuristic (Q201413). This would allow us to state that sex or gender (P21) is based on the heuristic full name (Q1071027), instead of "imported from Wikimedia project (P143)" it, indicating a lower level of confidence in its correctness.
Data type	Item
Robot and gadget jobs	Change current instances of "sex or gender (P21) imported from Wikimedia project (P143) full name (Q1071027)" to "sex or gender (P21) based on heuristic full name (Q1071027)".
Proposed by	—Ruud 12:30, 2 August 2013 (UTC)

Discussion

• I like it. It could also be extended to implied claims, e.g. assigning sex:male to an item is it is father or brother of another item, if such actions were to be undertaken by a bot. --Magnus Manske (talk) 12:55, 2 August 2013 (UTC)
•  Oppose Good idea but this will mix source and value. And like wikipedia wikidata is grounded on external references. This kind of analysis can be used only for data checking and search of unconsistent values. Snipre (talk) 13:26, 2 August 2013 (UTC)

  I'm not entirely sure I understand what you mean with "mix source and value". Also note, that we are already using heuristics to assign certain properties to items, this would merely make explicit the instances in we do (and have done) so. —Ruud 14:11, 2 August 2013 (UTC)

  You base your source on value and not on external sources. Your approach is definitevely out of th scope of the wikipedia spirit: you assume that it is possible to find the sex of a person from its name. First it is not always the case: they are some persons which have a name of the opposite gender and some names in some language can be used by both women and men. This approach is a "original research" based on an assumption that the sex is linked to the sex of the person. This is often the case but not always. Here we reach the limit of heuristics to "create" data and this is not the goal of wikidata which is a repository of data and not a place where data is generated. Snipre (talk) 15:26, 2 August 2013 (UTC)

I think you are misunderstanding the situation. "I" do not base my source on a value and "I" do not assume that it is possible to find the sex of a person from its name, but there are currently bots running which do (so). This is not the appropriate venue to discuss whether what they are doing is appropriate or not. I simply note that this is already happening and propose a sourcing property to make what is happening explicit. —Ruud 21:08, 2 August 2013 (UTC)

• Just noticing that SamoaBot's Task 33 has been regularly approved after a regular discussion; we selected suitable names with caution. The first run is now almost completed, but a new one is already planned.
  IMHO a "based on heuristic" property could be useful, but we should first have a large discussion on source properties; on the other hand, "imported from Wikimedia project (P143) full name (Q1071027)" doesn't mean that full name (Q1071027) is a clear and safe way at all to determine a person's gender. --Ricordisamoa 22:17, 2 August 2013 (UTC)

  There is a RfC on the sourcing requirement of bots and if there is a problem that's because bot owners are sourcing with unofficial properties. The property was a temporary property and an offical guideline was defined for the sourcing since that time. From now there are only two correct ways to sources: provide source according to help:sources or don't add any source. That is the clearest solution. Snipre (talk) 12:48, 15 August 2013 (UTC)

•  Support. --Yair rand (talk) 13:44, 25 August 2013 (UTC)
•  Support, will be a clear indication that the information should be double checked, but good heuristics can make really few mistakes so we take the better of both worlds. TomT0m (talk) 18:47, 25 August 2013 (UTC)
•  Support Filceolaire (talk) 13:30, 27 August 2013 (UTC)

JSTOR

   Done: JSTOR article ID (P888) (Talk and documentation)

Description	w:JSTOR provides full-text searches of almost 2,000 journals.
Data type	String
Domain	sources
Example	1736944.
Source	Template:Cite journal (Q5624899)
Proposed by	Micru (talk)

Discussion

Motivation: Needed to import Cite journal template.--Micru (talk) 20:37, 14 August 2013 (UTC)

 Oppose Use data of the original publication instead of an intermediary reference. Snipre (talk) 23:15, 14 August 2013 (UTC)

Sure, but this property can be used for verification purposes, to check that the original publication details are accurate.--Micru (talk) 00:10, 15 August 2013 (UTC)

And what happens if the pmc code is wrong ? Which is right ? Then we have the DOI which more general than the pmc. We have to be careful with crosschecking parameters because once you have 3 or more prameters which can defined 3 or more different objects that is a mess to see what is correct especially when you don't have the access to the documents. Snipre (talk) 12:42, 15 August 2013 (UTC)

Only those who do nothing make no mistakes. Mistakes are made to be corrected. TomT0m (talk) 18:51, 25 August 2013 (UTC)

 Support --Tobias1984 (talk) 08:06, 15 August 2013 (UTC)

 Support --Succu (talk) 08:41, 20 August 2013 (UTC)

 Support Filceolaire (talk) 13:32, 27 August 2013 (UTC)

 Comment can anyone explain exactly what is meant by "Needed to import Cite journal template"? Danrok (talk) 15:24, 29 August 2013 (UTC)

 Support I'll assume you are refering to cite templates on wikipedia, and the references contained there. Danrok (talk) 15:34, 29 August 2013 (UTC)

Mathematical Reviews identifier (MR)

   Done: Mathematical Reviews ID (P889) (Talk and documentation)

Description	w:Mathematical Reviews is a journal and online database published by the American Mathematical Society (AMS) that contains brief synopses (and occasionally evaluations) of many articles in mathematics, statistics and theoretical computer science.
Data type	String
Domain	sources
Example	1709679.
Source	Template:Cite journal (Q5624899)
Proposed by	Micru (talk)

Discussion

Motivation: Needed to import Cite journal template.--Micru (talk) 20:37, 14 August 2013 (UTC)

 Support --Tobias1984 (talk) 08:05, 15 August 2013 (UTC)

Request for Comments number (rfc)

   Done: RfC ID (P892) (Talk and documentation)

Description	A w:Request for Comments (RFC) is a publication of the Internet Engineering Task Force (IETF) and the Internet Society, the principal technical development and standards-setting bodies for the Internet.
Data type	String
Domain	sources
Example	5342.
Source	Template:Cite journal (Q5624899)
Proposed by	Micru (talk)

Discussion

Motivation: Needed to import Cite journal template.--Micru (talk) 20:37, 14 August 2013 (UTC)

 Comment --Tobias1984 (talk) 08:10, 15 August 2013 (UTC)

LOL --  Docu  at 08:13, 15 August 2013 (UTC)

 Support is what I meant :) --Tobias1984 (talk) 09:47, 15 August 2013 (UTC)

If I comment on this property, I suppose I should also write more than "LOL". Thus,  Support. To avoid ambiguity, IETF might need to be in the label. --  Docu  at 09:55, 15 August 2013 (UTC)

 Support Danrok (talk) 23:46, 29 August 2013 (UTC)

Social Science Research Network (SSRN)

   Done: SSRN article ID (P893) (Talk and documentation)

Description	The w:Social Science Research Network (SSRN) is a website devoted to the rapid dissemination of scholarly research in the social sciences and humanities.
Data type	String
Domain	sources
Example	900616.
Source	Template:Cite journal (Q5624899)
Proposed by	Micru (talk)

Discussion

Motivation: Needed to import Cite journal template.--Micru (talk) 20:37, 14 August 2013 (UTC)

 Support --Tobias1984 (talk) 09:49, 15 August 2013 (UTC)

Zentralblatt MATH (zbl and JFM codes)

   Done: zbMATH work ID (P894) (Talk and documentation)

Description	The service reviews more than 2,300 journals and serials worldwide, as well as books and conference proceedings. The Zentralblatt database also incorporates the 200,000 entries of the earlier similar publication Jahrbuch über die Fortschritte der Mathematik from 1868 to 1942, added in 2003.
Data type	String
Domain	sources
Example	Zbl: 05977305 JFM: 52.0141.06
Source	Template:Cite journal (Q5624899)
Proposed by	Micru (talk)

Discussion

Motivation: Needed to import Cite journal template. Before they were listed as sepparate entries, but since 2003 Zentralblatt incorporates the JFM codes, so it should be possible to merge them.--Micru (talk) 20:37, 14 August 2013 (UTC)

 Support --Tobias1984 (talk) 09:49, 15 August 2013 (UTC)

Avionics

   Done: avionics (P878) (Talk and documentation)

Description	notable sensors, electronics, and other avionics installed in the subject aircraft (avionics)
Data type	Item
Domain	aircraft
Allowed values	notable items
Example	<F-14 Tomcat> avionics <AN/AWG-9>
Proposed by	Joshbaumgartner (talk)

 Comment key piece of information, particularly for modern aircraft, for understanding capabilities of an aircraft. By being an 'item' property, it will limit statements to notable pieces of equipment. Joshbaumgartner (talk) 02:58, 30 May 2013 (UTC)

 Support --Tobias1984 (talk) 08:04, 30 May 2013 (UTC)

 Comment perhaps there is a more generic way to do this? Something like installed systems? So, the same property could be used for things like ships to indicate the radar installed, etc.? Danrok (talk) 21:12, 4 September 2013 (UTC)

That would be even better. I would support "carries instruments" which could also be used for scientific instruments of satellites. --Tobias1984 (talk) 09:37, 6 September 2013 (UTC)

 Support as generic. — Ivan A. Krestinin (talk) 03:41, 7 September 2013 (UTC)

pennant number / hull number

   Done: pennant number (P879) (Talk and documentation)

Description	The number or designation associated with individual warships, often painted on the hull.
Data type	String
Domain	term
Example	USS Iowa (Q562161) => BB-61 HMS Stockholm (Q10515155) => K11
Proposed by	Esquilo (talk)

•  Comment - What would be the primary source of this property? --Tobias1984 (talk) 13:53, 28 May 2013 (UTC)
•  Comment hull number of USS Iowa (Q562161) is 61 not BB-61. BB is the hull classification symbol. Danrok (talk) 18:29, 28 May 2013 (UTC)

 Support as a property for any and all types of codes/numbers combined in to a single string, as is usually painted on the hull. e.g. hull classification + hull number. Danrok (talk) 13:59, 31 August 2013 (UTC)

CPU aka "Central processing unit" (en) / CPU aka "Prozessor" (de)/ CPU aka "Processeur" (fr)/ CPU aka "unità di elaborazione centrale" (it)

   Done: CPU (P880) (Talk and documentation)

Description	Computer's CPU
Data type	Item
Template parameter	"cpu" in en:template:Infobox information appliance
Domain	term (computer)
Allowed values	for the future we could think to allow only items with Instance of equal to microprocessor (Q5297) (microprocessore)
Example	Commodore 64 (Q99775) --- ( cpu ) ---> MOS Technology 6510 (Q378246), Texas Instruments TI-99/4A (Q454390) --- ( cpu ) ---> Texas Instruments TMS9900 (Q767710)
Robot and gadget jobs	we could read "cpu" value in en:template:Infobox information appliance
Proposed by	LucaBiondi (talk) 11:45, 20 August 2013 (UTC)

Discussion

•  Support--Micru (talk) 13:15, 20 August 2013 (UTC)
•  Support Also, should not be limited to computers. Include devices and appliances. Danrok (talk) 20:49, 26 August 2013 (UTC)

NFPA Other

   Done: NFPA Special (P877) (Talk and documentation)

Description	NFPA Other
Data type	String
Template parameter	fr:infobox chimie, en:chembox, de:Chemikalien
Domain	chemistry
Allowed values	W or OX/OXY
Example	ethanol (Q153) = -
Source	NPFA704 2012
Proposed by	Snipre (talk) 22:10, 9 July 2013 (UTC)

Discussion

•  Support --Tobias1984 (talk) 08:45, 19 July 2013 (UTC)
•  Comment I think there should be three allowed values: W, OX/OXY and SA (Simple Asphyxiant). ∼Wostr (talk) 10:04, 6 August 2013 (UTC)

• There are more than 3 possibilities but only 2 are official. Snipre (talk) 11:24, 14 August 2013 (UTC)

• As far as I know SA symbol is one of the three official symbols. See Chapter 8, par. 8.2.4, NFPA 704 (2012 edition). ∼Wostr (talk) 21:23, 15 August 2013 (UTC)

UN packaging group

   Done: UN packaging group (P876) (Talk and documentation)

Description	packaging code
Data type	String
Template parameter	fr:infobox chimie, en:chembox, de:Chemikalien
Domain	chemistry
Allowed values	I, II, III, I/II, II/III
Example	sodium azide (Q407577) = II
Source	ADR 2011
Proposed by	Snipre (talk) 21:38, 9 July 2013 (UTC)

Discussion

•  Support --Tobias1984 (talk) 08:45, 19 July 2013 (UTC)
•  Support Danrok (talk) 10:32, 2 September 2013 (UTC)

UN class

   Done: UN class (P874) (Talk and documentation)

Description	UN hazard classification code
Data type	String
Template parameter	fr:infobox chimie, en:chembox, de:Chemikalien
Domain	chemistry
Allowed values	1.1, 1.2, 1.3, 1.4, 1.5, 1.6, 2.1, 2.2, 2.3, 3, 4.1, 4.2, 4.3, 5.1, 5.2, 6.1, 6.2, 7, 8, 9
Example	sodium azide (Q407577) = 6.1
Source	ADR 2011
Proposed by	141.6.11.21 12:00, 9 July 2013 (UTC)

Discussion

•  Support --Tobias1984 (talk) 08:45, 19 July 2013 (UTC)
•  Support Danrok (talk) 10:33, 2 September 2013 (UTC)

UN code classification

   Done: UN code classification (P875) (Talk and documentation)

Description	UN code classification
Data type	String
Template parameter	fr:infobox chimie, en:chembox, de:Chemikalien
Domain	chemistry
Example	sodium azide (Q407577) = T5
Source	ADR 2011
Proposed by	Snipre (talk) 21:38, 9 July 2013 (UTC)

Discussion

•  Support --Tobias1984 (talk) 08:45, 19 July 2013 (UTC)
•  Support Danrok (talk) 10:35, 2 September 2013 (UTC)

FIPS for countries/regions (FIPS 10-4)

   Done: FIPS 10-4 (countries and regions) (P901) (Talk and documentation)

Description	FIPS code for countries and (non US) regions per former FIPS 10-4 standard, see Federal Information Processing Standard (Q917824). See also: FIPS 55-3 (locations in the US) (P774)
Data type	String
Domain	places: countries/subnational entites (non US)
Allowed values	\D\D: countries, see en:List of FIPS country codes \D\D\d\d: subnational entities, see en:List of FIPS region codes

Added the template above. Someone might want to propose/create it. It seems preferable to split this out from FIPS 55-3 (locations in the US) (P774) --  Docu  at 08:25, 13 August 2013 (UTC)

How useful is this for objects outside US? Does this help our bots to identify correct items and fill them with information? -- Lavallen^talk(block) 07:31, 24 August 2013 (UTC)

It does make it easier to check the values in the other properties by clarifying the scope. Obviously, as all these FIPS codes are historic, current use is limited. Though, at least for US locations, they seem to have been used by the US government past their date. Maybe it's a way to help with the adoption of newer ones. --  Docu  at 07:39, 24 August 2013 (UTC)

Historic or future is not a big deal, as long at it helps us identify items compared with databases and statistical reports. -- Lavallen^talk(block) 07:44, 24 August 2013 (UTC)

The other two proposed at the same time are now available at FIPS 6-4 (P882) and P883 (P883). --  Docu  at 19:57, 11 September 2013 (UTC)

HDS

   Done: HDS ID (P902) (Talk and documentation)

Description	identifier in HDS/HLS/DHS/DSS: Historical Dictionary of Switzerland (Q642074), a national encyclopedia
Data type	String
Template parameter	Template:HDS (Q6235090)
Domain	all: e.g. persons, places, organizations, terms related to Switzerland
Allowed values	the part following "I" or "F" or "D"
Example	Vacallo (Q67470) = 2247 or 2247 or 2247, William Farel (Q435456) = 11113
Proposed by	- Vacallo (talk) 05:25, 3 June 2013 (UTC)

•  Support - Isn't the letter needed to make the string an unambiguous? --Tobias1984 (talk) 06:50, 3 June 2013 (UTC)
•  Oppose I = italian, D = german, F = french : use the property language to define the language. Snipre (talk) 12:03, 3 June 2013 (UTC)

• In that case it should probably be a multi-lingual string with all other languages linking to a default. --Tobias1984 (talk) 12:09, 3 June 2013 (UTC)
• In that case you just give the url, the title, the language and the date of access and no property is needed. Snipre (talk) 17:30, 3 June 2013 (UTC)

•  Comment Articles are available in all three languages under the same identifier. Users can select the language of an article by changing "i/I" in the URL to "f/F" or "d/D". - Vacallo (talk) 05:03, 10 June 2013 (UTC)

Libris

   Done: SELIBR ID (P906) (Talk and documentation)

Description	libris is a library-catalog provided by the National library of Sweden. A libris-id is often a nice tool to easily identify books who do not have an ISBN.
Data type	String
Template parameter	libris in sv:Mall:Bokref
Domain	books, sources
Allowed values	the identifier in uri's to for example: http://libris.kb.se/bib/7766806
Example	"7766806" for the book "Sveriges kommunindelning 1863-1993, Per Andersson". A widely used book
Robot and gadget jobs	not recommended en masse
Proposed by	Lavallentalk(block)

Discussion

Widly used in sources. Lavallen^talk(block) 17:06, 7 September 2013 (UTC)

 Support Sven Manguard Wha? 02:14, 13 September 2013 (UTC)

 Done as Property:P906 Sven Manguard Wha? 00:04, 14 September 2013 (UTC)

AMG Game ID (en)

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

Description	identification number used by allgame
Data type	String
Template parameter	N/A - this isn't used for infoboxes, it's used mainly for sources, but can also be a stand alone statement like Property:P436
Domain	creative work
Allowed values	string of five numbers
Example	In Q558753, this would be a statement, with the value 47753
Format and edit filter validation	Five digit number
Source	External reference
Robot and gadget jobs	When 47753 is entered, creates a link to http://allgame.com/game.php?id=47753 the same way a link is generated automatically in Property:P436
Proposed by	Sven Manguard Wha? 06:50, 12 September 2013 (UTC)

Discussion

No one raised any objections... Sven Manguard Wha? 00:08, 14 September 2013 (UTC)

Nova Scotia Register of Historic Places identifier (en) / identifiant Nova Scotia Register of Historic Places (fr)

   Done: Nova Scotia Register of Historic Places ID (P909) (Talk and documentation)

Description	The unique identifier of Nova Scotia Register of Historic Places
Data type	String
Domain	place
Example	Henry House (Q14816526) --> 23MNS0200 and 00PNS0261
Source	https://eapps.ednet.ns.ca/HPIPublic/propertysearch.aspx
Proposed by	Fralambert (talk)

Discussion

As the same of the other monuments registers in Canada--Fralambert (talk) 23:24, 5 September 2013 (UTC)

•  Support --Danrok (talk) 23:36, 9 September 2013 (UTC)
•  Comment Seems ready for creation. --  Docu  at 16:46, 14 September 2013 (UTC)
  •  Done --Fralambert (talk) 23:54, 15 September 2013 (UTC)

South African municipality code (en)

   Done: South African municipality code (P911) (Talk and documentation)

Description	ID for municipalities in South Africa
Data type	String
Template parameter	'muni_code' in Template:Infobox South African municipality
Domain	places: South African municipalities / metropolitan municipalities and districts
Example	City of Johannesburg Metropolitan Municipality (Q2346838) => JHB Capricorn District Municipality (Q692290) => DC35 eDumbe Local Municipality (Q311812) => KZN261
Source	en:List of municipalities in South Africa
Proposed by	Underlying lk (talk) 11:49, 1 September 2013 (UTC)

Discussion

•  Support --Ricordisamoa 15:06, 4 September 2013 (UTC)
• edited sample above. --  Docu  at 03:07, 5 September 2013 (UTC)
•  Support Danrok (talk) 14:39, 6 September 2013 (UTC)

Electrification

   Done: type of electrification (P930) (Talk and documentation)

Description	Electrification system (e.g. Third rail, Overhead catenary) and/or voltage)
Data type	Item
Template parameter	"electrification" or "el" in en:template:infobox rail line
Proposed by	Mange01 (talk) 21:45, 13 March 2013 (UTC)

 Comment switched proposal to new template. Danrok (talk) 10:16, 12 September 2013 (UTC)

 Support even if we have to create some new items. Filceolaire (talk) 12:43, 26 May 2013 (UTC)

 Support but should be renamed to "type of electrification" for semantics. --Tobias1984 (talk) 16:14, 1 August 2013 (UTC)

 Support --B.Zsolt (talk) 12:32, 23 August 2013 (UTC)

 Comment is there a reason why we can't just say instance of = overhead line (Q110701) (with relevant qualifiers when available)? Danrok (talk) 14:15, 29 August 2013 (UTC)

'instance of' links an item to a class which contains that item. '25kV overhead line electrification system' is more like a part of a railway line than a class it belongs to. I think 'has part' 'overhead lines' is better than 'instance of' but it still doesn't feel quite right. I think this new property is worth having. Filceolaire (talk) 18:08, 29 August 2013 (UTC)

Heritage Foundation of Newfoundland and Labrador identifier (en) / identifiant Heritage Foundation of Newfoundland and Labrador

   Done: Heritage NL ID (P933) (Talk and documentation)

Description	The unique identifier of Heritage Foundation of Newfoundland and Labrador
Data type	String
Domain	place
Allowed values	d/+
Example	Anderson House (Q4754101) --> 1558
Source	http://www.heritagefoundation.ca/property-search.aspx
Proposed by	Fralambert (talk)

Discussion

As the same of the other monuments registers in Canada. Fralambert (talk) 23:39, 5 September 2013 (UTC)

•  Support --Danrok (talk) 23:37, 9 September 2013 (UTC)

•  Comment Seems ready for creation. --  Docu  at 16:46, 14 September 2013 (UTC)

rada (Q7279926)

   Not done

Description	In Islam a rada is an important relation to a person
Data type	put datatype here (NEEDED: item, string, media, monolingual text, multilingual text, time)-invalid datatype (not in Module:i18n/datatype)
Template parameter	put Wikipedia infobox parameters here. If existing, sample: "population" in en:template:infobox settlement
Domain	family relations in an Islamic context
Allowed values	name of a person who is the rada of the person who is subject of the data item
Example	example item and/or example value (please add one or several sample uses of the property. Sample: Q1 => Q2
Source	External reference, Wikipedia list article (either infobox or source)
Robot and gadget jobs	not that I know
Proposed by	GerardM (talk)

• The English Wikipedia article on this property, Rada (fiqh), notes that 'rada' is a technical term with more specific meaning than simply a person that's important to another person. For example, it seems that this property would generally not be valid unless either the subject or object were female. And given the example of Muhammad al-Bukhari in that article, it seems like it might not be limited to persons. I think it would be worth establishing those kinds of basic parameters as part of this discussion.

I don't recall seeing any Arabic-speaking editors contributing to property proposal discussions. It'd be nice to get input from folks who are knowledgeable about rada. Would it be worth asking for input from users in Category:User_ar, and perhaps WikiProject Islam? Emw (talk) 03:48, 8 May 2013 (UTC)

•  Comment Wikidata_talk:Requests_for_comment/Kinship —★PοωερZ_talk 02:15, 11 May 2013 (UTC)
•  Oppose I believe rada is a type of relationship (roughly understood as milk-kinship), not a property of a person. For example, you would not give a person the property 'marriage', but instead 'spouse'. Similarly, you would not assign a person the property 'rada'. Granted, this is just my understanding and could be incorrect. Kaldari (talk) 07:28, 25 May 2013 (UTC)

Rada is the relation of one person towards another. You do not say is a rada ... you imply: rada of ****. Thanks, GerardM (talk) 13:47, 28 May 2013 (UTC)

 Oppose until a few examples are added to the template. --Tobias1984 (talk) 12:33, 4 August 2013 (UTC)

 Comment is this sourceable data? Danrok (talk) 00:33, 31 August 2013 (UTC)

facility

   Done: has facility (P912) (Talk and documentation)

Description	An installation, contrivance, or other things which facilitates something; a place for doing something.
Data type	Item
Domain	place, some terms
Allowed values	any item which describes a facility, e.g. escalator, toilet, car park, hangar, wheelchair ramp/lift, clinic, telephone, wi-fi, port crane, post office, letter box, lifeguard station, etc.
Example	HMS Montrose (Q5633432) => hangar (Q192375)
Source	wikipedia articles, various
Proposed by	Danrok (talk) 16:47, 29 August 2013 (UTC)

Discussion

 Comment this could be used on a wide range of items, and reduce the need for more specific properties. For example, we won't need a "number of elevators (lifts)" for buildings, just indicate that the building has facility = lift plus a quantity qualifier (when available) plus other qualifiers to indicate characteristics such as maximum load weight. Danrok (talk) 16:47, 29 August 2013 (UTC)

 Comment allowed values = any item which describes a facility, e.g. escalator, toilet, car park, hangar, wheelchair ramp/lift, clinic, telephone, wi-fi, port crane, post office, letter box, lifeguard station, etc. Danrok (talk) 16:50, 29 August 2013 (UTC)

 Support Filceolaire (talk) 20:26, 30 August 2013 (UTC)

Even though this is done, I'd like to comment that I believe this duplicates the "has part" relation, substantially if not completely (on a side note, this is exactly the use that 'has part' is best for). --Izno (talk) 20:35, 16 September 2013 (UTC)

Not sure that the two are exactly the same. The spirit of has facility (P912) is similar to what we'd see for a place on a map, e.g. a park which has car parking and camping facilities. In some cases, a facility provided might not be a physical part of the subject item. A hotel may offer tennis facilities to its guests, but the facility could be part of a neighboring sports complex, not a direct part of the hotel. Other facilities are not so tangible. e.g. wi-fi, and perhaps "has part" doesn't quite fit there. Also, this property was proposed twice. The other proposal related to a requirement for Wikivoyage, but I'm not familiar with what is needed there. Danrok (talk) 01:43, 24 September 2013 (UTC)

Topic main category

   Done: topic's main category (P910) (Talk and documentation)

Description	The main category of a topic. This is the inverse of category's main topic (P301)
Data type	Item
Template parameter	Will be used in templates like en:Template:Commons category and infoboxes that have a link to Commons.
Domain	All items about topics.
Allowed values	Category items, only one
Example	Haarlem (Q9920) => Category:Haarlem (Q7427769)
Format and edit filter validation	?
Robot and gadget jobs	This is the inverse of category's main topic (P301), so based on that claims can be added. Commons category (P373) contains information that can be used to add claims (for example Haarlem (Q9920) already contains a claim to "Category:Haarlem")
Proposed by	Multichill (talk)

Discussion

Linking categories and articles

Alternative use of interwikis. Working around the mainly inactive Gallery namespace at Commmons. Note the proposal below to link items for Commons Gallery pages (Q14916142) to items for articles (#Main_Commons_gallery_topic).

Some time ago I created Commons category (P373) to be able to store the links we have to Commons categories on Wikipedia's in a central location. This works, but is without the benefits of Wikidata. For example if a category gets deleted on Commons, this doesn't remove the claim. Now that Wikidata is going to be enabled for Commons, we can take the next step. We can start making links:

Commons:Haarlem -> Haarlem (Q9920) -> w:Haarlem

Commons:Category:Haarlem -> Category:Haarlem (Q7427769) -> w:Category:Haarlem

But we want to be able to link w:Haarlem to Commons:Category:Haarlem. With this property we can. This will replace Commons category (P373) over time. Multichill (talk) 18:21, 9 September 2013 (UTC)

Current stats:

• Commons: 110'000 galleries, 2'950'000 categories (excluding redirects)
• En wiki: 4'390'000 articles, 1'050'000 categories

Based on that, we would need to create about 2 million items for existing Commons categories. --  Docu  at 20:22, 9 September 2013 (UTC)

Why does Commons have such a large number of categories? Do you know? --Izno (talk) 22:09, 9 September 2013 (UTC)

Because Commons are file-based. There are 18'583'448 files on Commons and these are categorized in 2'950'000 categories. Galleries (that are also categorized) are only "additional bonus". --Jklamo (talk) 22:23, 9 September 2013 (UTC)

A large number of categories at Commons are intersected categories. For example "Churches in Haarlem". In the first run we should probably only create categories which are linked to, that would be a maximum of 800.000 items, but probably not even half of them. Multichill (talk) 07:31, 10 September 2013 (UTC)

• I would tend to agree that this property should exist, and it's odd that it doesn't currently.

  On a side note, we probably also need to figure out the whole namespacing situation that Commons deals with. --Izno (talk) 22:11, 9 September 2013 (UTC)

•  Oppose I say no unless the categorization of Commons will be maintained in Wikidata: w:Haarlem to Commons:Category:Haarlem, good thing but what happens is somebody changes the category in Commons without doing the update in Wikidata ? If Commons wants to use Wikidata, this means thaht every commons data will be mangaed in wikidata and not more in commons (no parallel system). Snipre (talk) 03:48, 10 September 2013 (UTC)
  • Snipre, I don't think you get it. This is not about metadata, this is only about the interwiki links. Multichill (talk) 07:31, 10 September 2013 (UTC)

•  Comment For pure symmetry, we should have this property, whatever the solution for Commons interwikis. --  Docu  at 17:51, 10 September 2013 (UTC)
  • True, and because this is a one on one mapping we don't have an exploding problem. Multichill (talk) 19:45, 10 September 2013 (UTC)
•  Support --  Docu  at 21:42, 11 September 2013 (UTC)

•  Support as an intermediate step to getting rid of categories  Oppose Categories are essentially queries on a set of pre-defined properties, and so should be obsolesced by Wikidata. The archived discussion Proposal for phase 4: unify and centralize categories contains detailed comments from several other contributors on this, but the gist is "get rid of categories". We should not be building infrastructure like specific 'category' properties to support a redundant, legacy categorization system on Wikidata.

I realize categories are fundamental to the current version of Wikimedia Commons. I have spent many hours curating categories and fastidiously categorizing my images there. I also realize there are currently also several very widely used properties that add some support for categories on client wikis. However, proposals for 'category' properties have been rejected before, see e.g. "category" and others. The fact that categories are currently so important on Wikimedia Commons does not negate the fact that queries and properties enable a vastly better solution to the problems that categories try to solve.

If someone could explain how this property would speed the transition away from categories and to a more property-and-query-based replacement, then I would likely support this property. Emw (talk) 02:38, 12 September 2013 (UTC)

I understand the property is not useful to you, but would the creation of this property adversely affect anything you try to do when using properties? --  Docu  at 04:51, 12 September 2013 (UTC)

I would like to have a system available that will let me browse images in an ad-hoc categorization scheme fulfilled by queries and properties. The creation of this property seems like it would forestall that goal, as explained in detail above. Furthermore, "would the creation of this property adversely affect anything you try to do when using properties" should not be a criterion of valid opposition. Otherwise, why have a property proposal? Emw (talk) 12:14, 12 September 2013 (UTC)

Emw, I want to get rid of categories of Commons in the long run. I've been saying that for over 2 years. So in the future File:Bavo haarlem south.jpg would just have a claim "depicts" linking it to Grote Kerk (Q1545193). I believe that we should go step by step. Commons category (P373) was the first step and this is the next one to achieve this goal. This way the whole chain between an article on Wikipedia and a category on Commons is all claims and items. Better links come available on Wikipedia and it will be a rich source of information to start adding claims to images in the future. Multichill (talk) 16:22, 12 September 2013 (UTC)

I've changed my vote to conditionally support this property as an intermediate step to eliminating categories. Thanks for the explanation, and your work in this domain. Emw (talk) 23:11, 12 September 2013 (UTC)

I wrote by thoughts down at Commons:User:Multichill/Commons Wikidata roadmap. Still work in progress, but I think it gives a good idea of the direction I think we should be heading in. Multichill (talk) 13:27, 14 September 2013 (UTC)

•  Support - Gareth (talk) 07:51, 13 September 2013 (UTC)
•  Support to take the place of Commons category (P373).--GZWDer (talk) 09:48, 13 September 2013 (UTC)
•  Oppose because it is not needed. Commons categories currently linked with pages in most cases (see commons:Category:Luna 9, commons:Category:Jimmy Wales as examples). This is good practice because there are many logical links between Wikipedia articles and Commons categories. Number of links between Wikipedia categories and Commons categories is less. Usually Commons category tree have +1 hierarchy level then Wikipedia category tree. This occurs because when we have notable object we create aritcle in Wikipedia and category on Commons for it. Wikipedia categories can obtain commons link using existing Commons category (P373) or category's main topic (P301). For gallery pages we can create separate property or do not use it at all because galleries exists for too low number of articles and often outdated. — Ivan A. Krestinin (talk) 18:47, 14 September 2013 (UTC)

Category items include links to Wikipedia and Wikivoyage too - so this isn't just about Commons. See Q5626403.

Wikivoyage`s hierarchy is more similar to Wikipedia as I see. Commons has different structure. — Ivan A. Krestinin (talk) 12:53, 15 September 2013 (UTC)

Yes, Commons has a different structure, but that doesn't preclude a link from a mainspace item to a corresponding category item from being useful, nor does it render this proposal invalid. Because Commons category (P373) goes directly to Commons it cannot provide this item to item link.

Created topic's main category (P910). Multichill (talk) 18:47, 16 September 2013 (UTC)

Spanish subject headings for public libraries (en) / Lista de Encabezamientos de Materia para Bibliotecas Públicas (es)

   Done: LEM ID (P920) (Talk and documentation)

Description	Subject Headings for public libraries mantained by the Spanish Ministry of Education, Culture and Sport. Terms are linked (in different numbers) to LCSH, GND, RAMEAU, LEMAC (Subject Headings in catalan).
Data type	String
Domain	term
Example	http://id.sgcb.mcu.es/lem/ver/Autoridades/LEM201010931/concept
Proposed by	Bibliowiki (talk) 16:13, 8 July 2013 (UTC)

Discussion

cleaned up description above. --  Docu  at 19:38, 8 August 2013 (UTC)

If there is no oposition I'm going to create this one.--Micru (talk) 15:59, 20 August 2013 (UTC)

 Support Danrok (talk) 14:47, 30 August 2013 (UTC)

Filming Location / Drehort / место съемок

   Done: filming location (P915) (Talk and documentation)

Description	where this film was filmed. can also be used as a quantifier for the proposed Story set in location property
Data type	Item
Domain	films
Allowed values	items that represent locations
Example	For a Few Dollars More (Q153677) <Filming Location> Spain (Q29) OR For a Few Dollars More (Q153677) <story set in location> New Mexico (Q1522) <Filming Location> Spain (Q29)
Proposed by	Shisma (talk)

Discussion

Motivation. Shisma (talk) 13:55, 1 September 2013 (UTC)

 Comment we need this, but perhaps this proposed property would cover it? Work location (en). Danrok (talk) 21:18, 1 September 2013 (UTC)

i think this goes more in detail which is I think required for the use as quantifier --Shisma (talk) 09:12, 4 September 2013 (UTC)

 Support Danrok (talk) 15:35, 5 September 2013 (UTC)

main topic of creative work

   Done: main subject (P921) (Talk and documentation)

Description	Subject of a creative work.
Data type	Item
Domain	published works
Example	The Sung Dynasty and its Precursors, 907–1279, Part 1 (Q13416074) <main topic of creative work> Five Dynasties and Ten Kingdoms period (Q242115)
Proposed by	--Micru (talk) 00:46, 25 June 2013 (UTC)

Discussion

•  Support There is depicts (P180) which is used for descriptive creative works (a picture <depicts> item), then there is category's main topic (P301), which is used for categories. It was perceived that none of this properties was precise enough to describe the subject/topic of a creative work.--Micru (talk) 00:46, 25 June 2013 (UTC)
•  Neutral Property category's main topic (P301) is somewhat similar. I would rather generalize the existing one. LaddΩ chat;) 21:26, 29 June 2013 (UTC)
  • There is a discussion now on category's main topic (P301), let's wait for the outcome.--Micru (talk) 14:08, 6 July 2013 (UTC)
    • Ok, so all the discussions are over, and this property should be differentiated from category's main topic (P301) because when doing searches it would bring up confusing results (category items). So if there is no opposition or no other comments I will create this property in a week from now.--Micru (talk) 20:47, 19 August 2013 (UTC)
•  Support Filceolaire (talk) 20:56, 20 August 2013 (UTC)
•  Wait I put this property on hold until the discussion about subject headings has finished (extremely related to this one).--Micru (talk) 14:23, 26 August 2013 (UTC)
•  Support --Shisma (talk) 14:43, 27 August 2013 (UTC)

so whats happening here? I don't see how subject headings is related to this property--Shisma (talk) 09:17, 9 September 2013 (UTC)

Variable type (en)

   Done: type of variable star (P881) (Talk and documentation)

Description	en:Variable star
Data type	Item
Template parameter	en:Template:Starbox observe Variable type
Domain	term
Example	Algol (Q13080)=>binary star (Q50053)
Proposed by	GZWDer (talk) 11:04, 8 July 2013 (UTC)

Discussion

• Maybe better use P60 (P60)? — Ivan A. Krestinin (talk) 16:19, 8 July 2013 (UTC)
•  Support I was going to propose this property after the discussion concerning hierarchy of the property P60 (P60). @Ivan: 1) my idea is to use P60 to classify astronomical objects to help Wikipedias to choose the right infobox. Furthermore, we can classify stars also for spectral type, luminosity class... 2) I prefer to not mix values of a property that can be used to choose an infobox or give a value for infobox parameters. --Paperoastro (talk) 20:12, 20 July 2013 (UTC) P.S.: I'd like to have your opinion about this. ;-)
  • Ok, I just ensure that you know about P60. — Ivan A. Krestinin (talk) 17:21, 30 July 2013 (UTC)
•  Support --Art-top (talk) 15:13, 30 July 2013 (UTC)
•  Support Danrok (talk) 15:51, 29 August 2013 (UTC)

Serves

   Not done

Description	Geographic entities served by an airport
Data type	Item
Domain	airport (other transportation ports/stations as well)
Example	<Seattle-Tacoma International Airport> serves <Seattle> AND <Tacoma>
Proposed by	Joshbaumgartner (talk)

 Comment: This is needed for situations where an airport served a notable destination, particular as its primary service area, but this is not reflected by its location. Many airports are located in smaller towns outside of the primary city they serve. Joshbaumgartner (talk)

•  Weak support - Shouldn't this link to US-counties instead of cities? Maybe name it "closest international airport for" and then list all the counties? --Tobias1984 (talk) 09:12, 1 May 2013 (UTC)

 Comment I'm not entirely sure how exactly to limit this one, so I see your point. I avoided including something like 'closest...' or 'primary...' because it could limit the utility of the property. Boeing Field (technically an international airport I believe) is closer than Sea-Tac to Seattle, but clearly Sea-Tac is a Seattle airport. Also, this property should be able to be used by non-international airports as well. I'm also not sure that an 'airport' property for use with cities/divisions/countries might not allow the same goal to be met from the other direction. Qualifiers could be used in that case to indicate role (some cities have different airports focused on different areas of flying). Joshbaumgartner (talk) 09:37, 1 May 2013 (UTC)

•  Support Note that the infobox label is city-served Infobox_airport. Danrok (talk) 00:01, 25 May 2013 (UTC)
•  Weak oppose in some countries major international airport can serve half of the country - shall all it's cities and towns be listed in it? --Base (talk) 13:10, 28 June 2013 (UTC)

  I don't think it has to be a city. There are articles for the recognized regions of most countries, so we could probably use those. TCN7JM 12:44, 6 August 2013 (UTC)

I agree. For a small country, e.g. Estonia, you would just specify that Tallinn airport serves Estonia, so just one item to list, not every city. Danrok (talk) 02:51, 27 August 2013 (UTC)

•  Support - Useful TCN7JM 12:48, 6 August 2013 (UTC)
•  Weak oppose This depends on both destination and what airline. Heathrow serves in some parts all of Europe, and maybe more than that. -- Lavallen (block) 05:45, 7 August 2013 (UTC)

If it can't be sourced, then there's no problem. It can be simply omitted for Heathrow (given that nothing is specified in the article). This should not prevent the creation of this property, which will be useful for many airports. Danrok (talk) 02:59, 27 August 2013 (UTC)

•  Support - Interesting! Quico (talk) 14:53, 9 August 2013 (UTC)
•  Comment not done, see place served by transport hub (P931) which is very similar. Danrok (talk) 10:54, 23 September 2013 (UTC)

city served (en)

   Done: place served by transport hub (P931) (Talk and documentation)

Description	If the airport is associated with a major city but actually located in a smaller town, list the major city here and the smaller town under location. This is not automatically linked, in order to allow multiple links if needed. (Source of this description: Airport summary.)
Data type	Item
Template parameter	"city-served" in en:template:infobox airport
Domain	place (airports)
Allowed values	cities
Example	London Luton Airport (Q8712) => London (Q84)
Source	wikipedia airport infoboxes
Robot and gadget jobs	bots can gather from infoboxes.
Proposed by	Danrok (talk) 18:13, 30 August 2013 (UTC)

Discussion

PubMed Center article number (pmc)

   Done: PMCID (P932) (Talk and documentation)

Description	w:PubMed Central is a free digital database of full-text scientific literature in biomedical and life sciences.
Data type	String
Domain	sources
Example	1480584.
Source	Template:Cite journal (Q5624899)
Proposed by	Micru (talk)

Discussion

Motivation: Needed to import Cite journal template. Not to be confused with PubMed ID (P698) or PubMed Health (P653).--Micru (talk) 20:37, 14 August 2013 (UTC)

•  Oppose Use data of the original publication instead of an intermediary reference. Snipre (talk) 23:16, 14 August 2013 (UTC)

  Sure, but this property can be used for verification purposes, to check that the original publication details are accurate.--Micru (talk) 00:10, 15 August 2013 (UTC)

  And what happens if the pmc code is wrong ? Which is right ? Then we have the DOI which more general than the pmc. We have to be careful with crosschecking parameters because once you have 3 or more prameters which can defined 3 or more different objects that is a mess to see what is correct especially when you don't have the access to the documents. Snipre (talk) 12:42, 15 August 2013 (UTC)

  According to good citation rules, you cite where you get the information from, regardless of whether that source is the actual original source of information. That's no less true for a website database such as PubMed then it is for an encyclopedia. --Izno (talk) 03:45, 17 September 2013 (UTC)

•  Support --Tobias1984 (talk) 08:06, 15 August 2013 (UTC)
• Support. --Izno (talk) 03:45, 17 September 2013 (UTC)
•  Support, though I think the the property's name should be changed from "PubMed Center article number (pmc)" to "PubMed Center reference number (PMCID)"; see http://publicaccess.nih.gov/citation_methods.htm. Emw (talk) 04:09, 17 September 2013 (UTC)

Notation / Обозначение

   Done: notation (P913) (Talk and documentation)

Description	mathematical notation or another symbol
Data type	Item
Template parameter	CAN BE MAPPED TO E.G. en:template:Infobox physical quantity: symbols.
Domain	Some categories of MAIN TYPE (physical or mathematical values)
Allowed values	Unicode symbol or sequence of symbols
Example	equality (Q842346) -> equals sign (Q214796)
Source	from some infoboxes or maybe lists in Wikipedia/or articles in Wiktionary
Robot and gadget jobs	no, manual (may be some table of symbols for convenient typing).
Proposed by	Infovarius (talk) 13:51, 16 March 2013 (UTC)

 CommentSeems reasonable, but I think that it should be "String" instead of "item".--Micru (talk) 14:37, 14 August 2013 (UTC)

 Support On a second view, item seems OK. I have updated the example.--Micru (talk) 20:26, 17 August 2013 (UTC)

Commons gallery

   Done: Commons gallery (P935) (Talk and documentation)

Description	name of the Wikimedia Commons gallery page(s) related to this item (is suitable to allow multiple link to more gallery pages)
Data type	String
Template parameter	"Commons" template and "Commons" parameters which link to non-category page
Domain	all items
Example	see cs:Karlovo náměstí (Praha), paralelly used Commons and Commonscat templates
Format and edit filter validation	the page of the name is existing on Commons
Source	templates Commons, Sisterlinks etc.
Robot and gadget jobs	should be treated similarly as P373 (Commons category)
Proposed by	--ŠJů (talk) 00:03, 7 July 2013 (UTC)

Discussion

•  Support sometimes there are pretty nice galleries pages on Commons. --Jklamo (talk) 18:31, 25 August 2013 (UTC)
•  Strong support - Great idea. --Jakob (Scream about the things I've broken) 21:46, 25 August 2013 (UTC)
•  Comment Commons category (P373) is an intermediate solution and I expect it not to stay around very long. With wikidata coming to Commons I don't think this is needed. Multichill (talk) 18:02, 9 September 2013 (UTC)

Facilities (en)

   Not done

Description	voy:Template:Listing
Data type	Item
Domain	items with Wikivoyage listings
Allowed values	items describing facilities in the subject item
Example 1	MISSING
Example 2	MISSING
Example 3	MISSING
Source	Wikivoyage listings
Proposed by	Filceolaire (talk) 00:11, 19 August 2013 (UTC)

Discussion

Can be represented by icons on listings.

•  Support Support as nom. See this RFC. Filceolaire (talk) 00:11, 19 August 2013 (UTC)Proposal withdrawn as per Danrok below.
•  Comment I created a similar proposal here before I saw this. Seems to be the same, except I am suggesting broader scope. Danrok (talk) 00:58, 30 August 2013 (UTC)
• Note this has effectively been crated as has facility (P912) --Danrok (talk) 23:31, 24 September 2013 (UTC)

Ideas for grouping items into principal groups

This is just to collect ideas, to brainstorm, not to evaluate if we should have such a property (no pros and cons). Such a property is not meant to replace other properties or interfere with the way they may work. Please avoid mentioning P31 (we already read all about that and people can look it up) and GND type (this has been discussed elsewhere).

Things it should be able to do:

• identify easily if an item is about a real person (or a legendary one that might have lived), possibly before we know gender, DOB, etc.
• identify items about organizations, companies
• identify geographic features on Earth, possibly before we know which country it is located in, the exact coordinates ..
• identify objects in space
• identify Wikipedia specific items (templates, Wikipedia namespace pages, categories, etc.)
• identify everything else

Please mention things it should do for you. --  Docu  at 05:33, 10 September 2013 (UTC)

Additions suggested below:

• Disease
• Organism (+ viruses)
• Biological sequence (e.g. gene, protein)

by Emw. --  Docu  at 11:05, 15 September 2013 (UTC)

P31/P279

instance of (P31) is your solution. 141.6.11.21 13:41, 10 September 2013 (UTC)

This is being discussed (at length) on Wikidata:Requests_for_comment/Migrating_away_from_GND_main_type. Please take all discussions there. Filceolaire (talk) 13:18, 11 September 2013 (UTC)

Yes, please respect my request above and discuss P31 there, not here. Thanks. --  Docu  at 21:42, 11 September 2013 (UTC)

Docu, have you seen the discussion at the Primary sorting property RFC? The questions above are precisely what was discussed there and I can't find your signature anywhere on that page, so it seems plausible that you might be unaware of that conversation. Emw (talk) 03:04, 12 September 2013 (UTC)

If you have suggestions for principal groups, please add these here. Thanks. --  Docu  at 04:36, 12 September 2013 (UTC)

You request that we "mention things (a list of main types) should do for you". I'm interested in biology and think it's generally relevant; a list of main types should help me find things related to biology. So in a hypothetical world in which we, for some reason, ignored detailed comments in one of Wikidata's most active RFCs and pursued the very suboptimal idea of having a "main type" property, here are some main types I would like to see:

• Disease
• Organism (+ viruses)
• Biological sequence (e.g. gene, protein)

The last might be a stretch, but it's still very high-level and something I would like to see in a list of main types. The other two seem clearly important enough to have among main types, certainly more than "objects in space". Emw (talk) 12:08, 12 September 2013 (UTC)

I added them. --  Docu  at 11:05, 15 September 2013 (UTC)

subclass of (P279) is the property to do this, creating a hierarchy of groups/classes from the very specific up to the very general. Then we need tools to let us define a class as all the instance of (P31) of an item plus all of the items that are subclasses of that item (sorry but you can't discuss subclass of (P279) without mentioning instance of (P31)). This is being used to do all the things you list above. Filceolaire (talk) 21:47, 12 September 2013 (UTC)

Brainstorming can be hard. Maybe I should start a separate thread for all the instance/class comments. --  Docu  at 23:57, 12 September 2013 (UTC)

This is the wrong place to be doing this. You might consider opening an RFC. --Izno (talk) 18:18, 14 September 2013 (UTC)

Stop: we have an RfC on the subject Wikidata:Requests_for_comment/Migrating_away_from_GND_main_type. I will delete these two proposals. Snipre (talk) 08:53, 16 September 2013 (UTC)

FishBase species identifier

   Done: FishBase species ID (P938) (Talk and documentation)

Description	w:FishBase is a database that provides an authoritative and comprehensive list of names of fishes
Data type	String
Template parameter	w:Template:FishBase
Domain	term / taxon
Example	5918
Robot and gadget jobs	Add 'http://www.fishbase.org/Summary/speciesSummary.php?id=$1' to Gadget-AuthorityControl.js
Proposed by	Liné1 (talk) 18:51, 6 September 2013 (UTC)

Discussion

 Support Liné1 (talk) 18:51, 6 September 2013 (UTC)

 Support --Tobias1984 (talk) 19:22, 6 September 2013 (UTC)

 Done --Tobias1984 (talk) 06:24, 25 September 2013 (UTC)

Current location (en) / Localisation actuelle (fr)

   Not done

Description	indicates the current location of an ancient geographical feature
Data type	Item
Domain	place
Example	numerous ancient athenian demes. For instance Athmonon (Q12872216) ==> Marousi (Q992348)
Proposed by	Alexander Doria (talk) 21:58, 9 June 2013 (UTC)

Discussion

 Comment - what does this have to do with space? --WDGraham (talk) 02:55, 10 June 2013 (UTC)

 Comment it just needs moving to geography. Secretlondon (talk) 19:31, 10 June 2013 (UTC)

 Move --Tobias1984 (talk) 08:59, 29 July 2013 (UTC)

 Weak support - If this tries to link e.g. Ephesus (Q47611) to Selçuk (Q876176) I support that. I think the English description might have to be reworded to be a little clearer. It might also be a thing we could query. Ephesus lies in the administrative region of Selcuk. So actually we are producing a slight redundancy in many of those statements. --Tobias1984 (talk) 16:02, 1 August 2013 (UTC)

Maybe these could also use P17, P131 and/or P30. BTW the proposed English name is already used by Property:P276 ("current location"). --  Docu  at 19:33, 8 August 2013 (UTC)

 Not done as far as I can see, based on the example given by the proposer, there is no need for this property. Also, no need for "current" type properties, just use date qualifiers. Danrok (talk) 10:03, 25 September 2013 (UTC)

historical period

   Not done

Description	The historical period to which the item belongs according to relevant sources
Data type	Item
Template parameter	"era" in en:template:infobox Former Subdivision
Domain	person, place, organization, event, creative work, term
Example	Roman Britain (Q185103) => classical antiquity (Q486761)
Source	wikipedia, books, etc.
Robot and gadget jobs	bots can source from infoboxes
Proposed by	Danrok (talk) 11:24, 2 September 2013 (UTC)

Discussion

•  Support Seems like a good idea to me. Ajraddatz (Talk) 17:18, 2 September 2013 (UTC)
• In addition to the regular date markers, all such time-based items could also state which historical period it was/is part of? No limitations? --Yair rand (talk) 18:03, 2 September 2013 (UTC)

No limitation as such. For some items there may not be any specific dates available, but the item may have been determined to originate in a given period, which is one good reason for this property. Danrok (talk) 18:02, 3 September 2013 (UTC)

Could 'part of' do this job? Filceolaire (talk) 21:37, 4 September 2013 (UTC)

Maybe part of could work, if so it would be the best way. Take a look at Roman Kingdom which is described as a period, but also described as part of the Iron Age (another period), and as part of modern Italy. I can't think of any issue with claiming that it is part of all of those things. I'll look at some more examples. Danrok (talk) 00:42, 5 September 2013 (UTC)

 Oppose Better give the dates of the start and the end as qualifier. For the example above, this can be described withe the property official name with dates as qualifier. Snipre (talk) 19:57, 5 September 2013 (UTC)

 Comment For many items there are no dates, which is part of my motivation for this. Also, not all historical eras have specific start/end dates. This is not necessarily about dates, it's about an expert stating that a given thing is of a certain era, based on scientific evidence and methods. For example, an item is found in the ground along with pottery from a certain period, so the item can be assumed to belong to the same period. Danrok (talk) 22:10, 5 September 2013 (UTC)

 Not done I'll abandon this for now, in favour of using part of. Danrok (talk) 02:20, 25 September 2013 (UTC)

Magnetic ordering (en) / magnetische ordnung (de)/ ordre magnétique (fr)/ ordenamiento magnético (es)

   Done: magnetic ordering (P922) (Talk and documentation)

Description	Magnetic ordering of a substance
Data type	Item
Template parameter	"magnetic ordering" in w:Template:Infobox element
Domain	term (substances)
Allowed values	See w:Magnetism#Topics
Example	iron (Q677) --> ferromagnetism (Q184207)
Source	w:Template:Infobox element
Proposed by	--Jakob (Scream about the things I've broken) 16:28, 19 August 2013 (UTC)

Discussion

•  Support With w:Curie temperature as qualifier.--Micru (talk) 13:29, 20 August 2013 (UTC)

GHS precautionary statements

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

Description	GHS precautionary statements
Data type	String
Template parameter	fr:infobox chimie, en:chembox, de:Chemikalien
Domain	chemistry
Example	ethanol (Q153) = P210
Proposed by	Snipre (talk) 22:10, 9 July 2013 (UTC)

Discussion

•  Support --Tobias1984 (talk) 08:45, 19 July 2013 (UTC)
•  Comment In contrast to H phrases, P phrases are not defined by the regulatory authorities. --Leyo 21:33, 28 July 2013 (UTC)

P phrases are derived from H phrases: there are some official rules to translate H phrases to P phrases. In some way we can do that automatically. Snipre (talk) 17:46, 20 August 2013 (UTC)

индекс ГРАУ (ru) / GRAU index (en)

   Done: GRAU index (P917) (Talk and documentation)

Description	GRAU index (Q527163), условное цифро-буквенное обозначение образца вооружения, присваиваемое одним из Заказывающих Управлений Министерства обороны СССР и России
Data type	String
Domain	образцы вооружения
Allowed values	цифро/буквенный код
Example	Vostok-K (Q3303767) => 8К72К
Format and edit filter validation	{{Constraint}}
Source	http://all-tanks.ru/content/indeksy-grau-mo-sssr-rf?page=show, http://www.designation-systems.net/non-us/soviet-mw.html
Proposed by	— Ivan A. Krestinin (talk)

 Support Danrok (talk) 14:37, 30 August 2013 (UTC)

CNP Occupation Code (en) / CNP-Berufscode (de) / Code de la Classification nationale des professions (CNP) (fr)

   Done: NOC Occupation Code (P918) (Talk and documentation)

Description	CNP Code for a given occupation in Canada and Québec
Data type	String
Template parameter	Code CNP in fr:template:Infobox Métier
Domain	profession (Q28640),occupation (Q13516667), job
Allowed values	number with 4 figures
Example	value for librarian (Q182436) is : 5111
Format and edit filter validation	Usage guidelines can be found at http://www5.hrsdc.gc.ca/NOC/English/NOC/2011/Introduction.aspx
Source	List at http://www5.rhdcc.gc.ca/cnp/francais/cnp/2011/RechercheRapide.aspx?val65=*
Robot and gadget jobs	Robots should check the gov website if the job exists e.g. for librarians: http://www5.hrsdc.gc.ca/NOC/English/NOC/2011/Profile.aspx?val=5&val1=5111
Proposed by	Teolemon (talk) 15:45, 29 August 2013 (UTC)

Discussion

 Support. Classification system used by administration. TomT0m (talk) 13:01, 22 September 2013 (UTC)

Standard Occupational Classification Code (en)

   Done: SOC Code (2010) (P919) (Talk and documentation)

Description	Standard Occupational Classification code for US jobs
Data type	String
Template parameter	None so far
Domain	profession (Q28640),occupation (Q13516667),jobs
Allowed values	XX-XXXX where X is a 0-9 digit
Example	value for librarian (Q182436) is 25-4021
Source	Structure of those codes: http://www.bls.gov/soc/soc_2010_class_and_coding_structure.pdf
Robot and gadget jobs	For the code XX-XXXX, check if this page exists: http://www.bls.gov/soc/2010/socXXXXXX.htm
Proposed by	Teolemon (talk) 16:00, 29 August 2013 (UTC)

Discussion

 Support same project, don't know about the matching.

Place of funeral (en) / Lieu des obsèques (fr)

   Not done

Description	Place of the funeral ceremony (church...)
Data type	Item
Domain	person
Example	Charles-Guillaume Étienne (Q2277482) => Saint-Roch (Q1436962) (with a qualifier : point in time (P585) => 15 March 1845)
Source	books, newspapers
Proposed by	Pyb (talk) 08:59, 27 August 2013 (UTC)

Discussion

 Oppose who needs this in infoboxes or lists? It is enough if you write it in the articles, though not necessary for an ecyclopedic view. It is also not needed in boxes to know where the wedding ceremony was or the baptism ceremony or the bar mitzwa or whatever ceremony one can experience in life (or death in that case).--Giftzwerg 88 (talk) 09:28, 27 August 2013 (UTC)

Not being useful for Wikipedia infoboxes or lists does not mean it shouldn't be included in Wikidata. That said, I'm not sure having a unique property would be the best way to handle this data. Each funeral having a separate item might work, but that seems rather cumbersome. --Yair rand (talk) 10:25, 27 August 2013 (UTC)

•  Support Ayack (talk) 10:45, 27 August 2013 (UTC)
• Useful at least for more spectacular burial places, like the Pharaos of Egypt... -- Lavallen^talk

(block) 12:31, 27 August 2013 (UTC)

• We have place of burial for this purpose which is clearly identified. We can speculate about the location of the funeral ceremony of the pharaohs a lot.--Giftzwerg 88 (talk) 19:29, 31 August 2013 (UTC)

•  Oppose significant event (P793)=>funeral (Q201676) with two qualifiers P766 (P766)=>Saint-Roch (Q1436962) and point in time (P585) => 15 March 1845

thx for the info. I'm ok to withdraw my demand. Pyb (talk) 14:42, 27 August 2013 (UTC)

 Comment The use of significant event (P793)=>funeral (Q201676) indeed seems to respond to the demand. But if we want to request people on funeral ceremony, we could have a confusion with burial (Q331055) which is a sub-class of funeral (Q201676) and have 2 different places and 2 different dates. Maybe it could be interresting to create an event funeral ceremony, sub-class of funeral (Q201676).--Shonagon (talk) 20:20, 27 August 2013 (UTC)

I think there's a long list of possible events regarding funerals around the world and throughout time. Same for births, as it is we don't have any properties relating to baptisms (and that is often the only date recorded, churches didn't record the birth date. The recording of dates of birth is a fairly new process). Danrok (talk) 19:47, 31 August 2013 (UTC)

 Not done opposition, and proposer agrees with an alternative solution. Danrok (talk) 00:15, 28 September 2013 (UTC)

appears in (en)

   Not done

Description	(person, place, ...) appears in work
Data type	Item
Template parameter	n/a
Domain	person, place, organization, event, creative work, term
Allowed values	n/a
Example	Frodo Baggins (Q177329) appears in The Fellowship of the Ring (Q208002)
Format and edit filter validation	n/a
Source	Often the work itself.
Robot and gadget jobs	Could be checked against the proposed property Wikidata:Property_proposal/Creative_work#characters / действующие лица.
Proposed by	—Ruud 23:23, 24 June 2013 (UTC)

Discussion

 Comment What about renaming it to "featured in"? "Appears in" seems too generic.--Micru (talk) 01:39, 8 July 2013 (UTC)

Sounds, okay. —Ruud 08:22, 17 July 2013 (UTC)

• Does this include nonfictional entities? If so, I think it would be better for this to be a property of the work, rather than of the subject featured. Also, some limitations would really need to be in place. ("France" appears in the work? "George Bush", "Microsoft", a "keyboard"? Etc.) --Yair rand (talk) 11:17, 17 July 2013 (UTC)
  • Yes, this could become problematic if not limited within reason. Restricting it to apply to only fictional entities would likely resolve most issues, and is its intended purpose. On the other hand, with some appropriate user interface support (limiting the number of items shown by default) it might be possible to also support this for some non-fictional entries like "France" and "George Bush", but also applying it to entities like "keyboard" would probably be overdoing it. —Ruud 12:14, 17 July 2013 (UTC)

 Comment This needs to be more clear. The meaning of "appears" in this context means that the actual person appeared. For example, Steve Jobs did not appear in Jobs (Q392825), he was portrayed in that movie. In any case, all of this is already handled in the movie's item using the cast member and role properties. So, this kind of information can already be determined. Danrok (talk) 15:52, 25 August 2013 (UTC)

 Oppose. Better have properties that work the other way round - you don't want 'London' to have a list attached to it of every film and book that it ever appeared in. Filceolaire (talk) 10:18, 31 August 2013 (UTC)

 Oppose too general. Snipre (talk) 11:19, 1 September 2013 (UTC)

 Not done due to opposition, and little support. Danrok (talk) 00:12, 28 September 2013 (UTC)

possible examinations / (fr) examen complémentaire

   Done: medical examination (P923) (Talk and documentation)

Description	examinations that might be used to diagnose the medical condition
Data type	Item
Template parameter	new infobox form French medicine project would be interested in this information
Domain	term
Allowed values	all types of medical examinations
Example	bone fracture (Q68833) = medical radiography (Q4115819)
Format and edit filter validation	target item has to be a subclass of medical examination
Source	medical literature
Robot and gadget jobs	?
Proposed by	--Tobias1984 (talk) 14:38, 25 July 2013 (UTC)

Discussion

unverifiable author

   Not done

Description	When the author identity cannot be properly established, use this property instead of P (P)
Data type	String
Domain	published works
Example	Authors with the same name that cannot be distinguished without error, authors signing with initials or incomplete name and whose identity cannot be determined now.
Proposed by	--Micru (talk) 17:53, 5 June 2013 (UTC)

Discussion

•  Support As proposer.--Micru (talk) 17:53, 5 June 2013 (UTC)
•  Support Further reading: http://www.nature.com/news/2008/080213/full/451766a.html --Tobias1984 (talk) 20:20, 5 June 2013 (UTC)
•  Support I think we also need a task force to help with identifying these authors. --Stevenliuyi (talk) 20:29, 5 June 2013 (UTC)
•  Support but change the name: this is the author property with another datatype. Insome cases even if the author can be identified as he published only one document there is no advantage to create an item for that guy. Then you have to propose a string format in order to handle that author in the same way as name from author item: example Li, Wang, or L. Wang or Hells, G. M. Snipre (talk) 00:51, 7 June 2013 (UTC)

  I think if it is identifiable we should create an item wether there is an interest or not. Identifying objects to items is the whole point of items, and if the author is identifiable we have some sourcable datas on him. Having an item on him will nethertheless help people to cite him as author if he write or has written on something else, and with the source the work will have to be done only once, and not potentially over and other again checking google to see if there is information on that name string on google, to see if there already have authors on the same name on wikidata ...

•  Support but only if we can obtain nothing on the author. We should always have some informations on the author on something, it is important to have a bird eye view on the quality of source. TomT0m (talk) 14:30, 8 June 2013 (UTC)
•  Oppose I think here should author be used instead with a qualifier that the author is unverifiable. --Pyfisch (talk) 19:18, 10 June 2013 (UTC)

  But with your solution 2 authors with the same name and without elment to differentiate them will share the same item. This proposal aims to solve the problem of author without wikipedia articles: in lot of documents like scientific or newspaper articles the authors are unknows even if you have their names. If the author name is special no problem but if the name is share by different authors you will have to 1) create in new item for each occurence or 2) use the same item even for different persons. Snipre (talk) 19:08, 12 June 2013 (UTC)

•  Neutral, not really against, but I think we could create items even for "unverifiable" authors, just like the GND "undifferentiated" type. It would avoid to have two properties to express the same relation. -Zolo (talk) 20:26, 12 June 2013 (UTC)
• As Zolo. --Ricordisamoa 21:07, 14 June 2013 (UTC)
•  Oppose - qualifier or rank will be better. Otherwise we create many properties twice (verified and unverified). --Nightwish62 (talk) 18:08, 6 July 2013 (UTC)
•  Oppose per Nightwish Filceolaire (talk) 04:20, 28 August 2013 (UTC)
•  Not done due to a number of oppositions with explanations. --Danrok (talk) 20:02, 29 September 2013 (UTC)

 Comment I think it would be best to use the creator (P170) for this, and create some suitable items which would be the unverifiable authors. Each item would be claimed as a name of an author, or several authors of the same name, who cannot be fully identified. Danrok (talk) 20:25, 29 September 2013 (UTC)

Inspired by

   Done: inspired by (P941) (Talk and documentation)

Description	this creative work is influenced by another creative work
Data type	Item
Domain	creative works
Allowed values	creative works
Example	The Matrix (Q83495) => Alice's Adventures in Wonderland (Q92640))
Proposed by	Shisma (talk)

Once upon the time there was a property labelled based on/Inspired by which now has been relablled to based on. maybe because these are two separate things. this ancient property can be found here: based on (P144). please feel free to add better examples --Shisma (talk) 15:39, 27 September 2013 (UTC)

Correction: based on (P144) has been "based on" since the beginning in Feb 2013, and only "based on/inspired by" between Aug 18th and Sep 26th. --AVRS (talk) 08:12, 28 September 2013 (UTC)

 Support needs to be separate from based on. Useful property for many items. --Danrok (talk) 20:11, 29 September 2013 (UTC)

KSH code (en) / code KSH (fr)/ KSH-kód (hu)

   Done: KSH code (P939) (Talk and documentation)

Description	Code attribué à chaque localité de Hongrie par l'Hungarian Central Statistical Office (Q1125966) à des fins statistiques. / Code of the Hungarian Central Statistical Office for every locality (town and commune) in Hungary / A KSH kódja minden magyarországi településre
Data type	String
Template parameter	Utilisés sur Wikipédia en français dans le modèle d'infobox des localités de Hongrie / Used in the French WP template for localities of Hungary / A francia wikin a magyar település infobox sablon használja : fr:Modèle:Infobox Commune de Hongrie/Code KSH
Domain	Localités de Hongrie : 3179 villes et communes. / 3179 towns and communes of Hungary / 3179 magyarországi település
Allowed values	Les codes sont des nombres. / Numbers / Számok
Example	Mohács (Q320798) : 23959
Format and edit filter validation	Exactement 5 chiffres de 0 à 9 / Exactly 5 figures between 0 and 9 / 5 db. 0 és 9 közötti számjegy
Source	Magyarország közigazgatási helynévkönyve, 2012. január 1.
Robot and gadget jobs	Les ajouts sont facilement automatisables. / Easily added by bot from source / Könnyű adatfeltöltés bottal a forrásból. Add 'http://www.ksh.hu/apps/!cp.hnt2.telep?nn=$1' to Gadget-AuthorityControl.js
Proposed by	Ljubinka (discuter) 14:07, 25 August 2013 (UTC)

Discussion

I added a request for Gadget-AuthorityControl.js to show the value with a link to the page of the locality on the KSH site (Hungarian Central Statistical Office), since this page will be the source of many other property values for the locality which are presently discussed here (in French, but feel free to use English or Hungarian, maybe in a new section). Oliv0 (talk) 09:23, 27 August 2013 (UTC)

 Support Danrok (talk) 15:54, 29 August 2013 (UTC)

 Comment Seems ready for creation. --  Docu  at 19:04, 6 September 2013 (UTC)

 Comment Thanks Danrok for the creation. The link on the value through Gadget-AuthorityControl.js is still absent, and I think also the control of allowed values and allowed items. Oliv0 (talk) 18:40, 26 September 2013 (UTC)

I can't edit Gadget-AuthorityControl.js because I am not an admin. But, you can ask someone to do that here MediaWiki_talk:Gadget-AuthorityControl.js. I believe the control of allowed values can be set-up/modified by anyone. --Danrok (talk) 12:19, 30 September 2013 (UTC)

Thank you, I found Template:Constraint. Oliv0 (talk) 17:05, 30 September 2013 (UTC)

Call sign / Позывной

   Not done

Description	позывной экипажа
Data type	Multilingual text (not available yet)
Template parameter	ru:Шаблон:Космическая экспедиция Позывной en:Template:Infobox space mission call sign
Domain	пилотируемые космические аппараты
Example	Союз ТМА-8, позывной: Карат
Source	Карточки в статьях
Proposed by	— Ivan A. Krestinin (talk) 19:20, 1 April 2013 (UTC)

 Comment -- I'm not clear on what this data is for. "Sign"" means exactly what? Once we figure it out, we might be able to name the field a bit more descriptively to help other English readers. Cheers. N2e (talk) 14:01, 27 April 2013 (UTC)

I think this is call sign - Soyuz TMA-8, callsign Karat. Secretlondon (talk) 14:43, 27 April 2013 (UTC)

Для аероліній існує Property:P432 — можливо просто розширити її сферу дії? --Base (talk) 16:22, 2 May 2013 (UTC)

I think airplane call sign are different? Secretlondon (talk) 20:22, 3 May 2013 (UTC)

How is it different? I would prefer to have one general callsign property to be used in space mission/ships/planes and what else may use callsigns. Byrial (talk) 08:30, 9 May 2013 (UTC)

We'll we'd need to rename P432 and take the restraints off. Secretlondon (talk) 11:26, 9 May 2013 (UTC)

The problem is if we use P432 for any call sign, it gets harder to do constraint checks on it. --  Docu  at 11:40, 12 May 2013 (UTC)

Do we have a military callsign field? That would be a closer match than an airline's callsign? --WDGraham (talk) 18:38, 22 May 2013 (UTC)

 Comment I think that callsign of airline (P432) should be renamed to call sign, based upon what I have read about call signs. See Call sign. Danrok (talk) 00:11, 30 August 2013 (UTC)

 Comment Also, constraint checks will be difficult given that any organization or person can potentially have a call sign (need to apply for it, have a licence for that radio, etc.). Danrok (talk) 00:15, 30 August 2013 (UTC)

 Comment See this guy's call sign is FK8GX. Danrok (talk) 00:19, 30 August 2013 (UTC)

•  Support given that spacecraft call signs are exceptional, but it looks like this will need to be multilingual-text, or a string in the original language only. Danrok (talk) 00:27, 30 August 2013 (UTC)
•  Comment Should be string. The whole thing about call signs is that they are unique identifiers, independent of language. If you want explanations or transcriptions these can be in multi-lingual qualifiers properties. Filceolaire (talk) 20:39, 30 August 2013 (UTC)
•  Oppose. Rename P432 and use that instead for airlines, spacecraft, ham radio etc. As call signs are arbitrary strings it will be tough to apply constraints. Where call signs for a particular domain have constraints which can be checked then we can check based on the Class that the subject of the property belongs to. Filceolaire (talk) 20:39, 30 August 2013 (UTC)

All non-space call signs will be unique (as far as I know). Space call signs might not be, because they're not regulated in the same way. I have no idea if there really are, or have been, 2 entities with the same call sign. But, perhaps this won't present an issue if all call signs share the same property, search results can always be further filtered to weed out spacecraft/astronauts, if needed. I'll mark this as not done, and change the description of callsign of airline (P432). Danrok (talk) 13:50, 2 September 2013 (UTC)

theme music

   Done: theme music (P942) (Talk and documentation)

Description	the theme music/song used under licence by the item (film, event, sport club/team, person, etc.)
Data type	Item
Template parameter	"theme" in en:template:Wrestling event
Domain	person, organization, event, creative work, term
Allowed values	song, music track
Example	2003 SummerSlam (Q59369) => St. Anger (Q1347942)
Source	infoboxes, wikipedia articles
Robot and gadget jobs	can source from infoboxes
Proposed by	Danrok (talk) 11:09, 8 September 2013 (UTC)

Discussion

•  Support --Micru (talk) 11:00, 22 September 2013 (UTC)

with

   Not done

Description	used to describe something that is with other (used mainly as a qualifier)
Data type	Item
Domain	person, possibly organization, creative work...
Example	Erwin Schrödinger (Q9130) award received (P166) Nobel Prize in Physics (Q38104) => Paul Dirac (Q47480)
Proposed by	Sarilho1 (talk) 12:40, 12 August 2013 (UTC)

Discussion

I didn't find any property that describe could be used in this way. I though that it could be used as qualifiers, but, like follows (P155) and followed by (P156) it could be used normally if needed. It maybe used in other proposes, but I just though in this. P.S.: I don't know what could be the name in English so I put this. I would appreciate if you find one better. - Sarilho1 (talk) 12:40, 12 August 2013 (UTC)

'with' is a good translation for 'juntamente'.

 Support Filceolaire (talk) 15:34, 12 August 2013 (UTC)

 Oppose* The example is implied by a query (award winners with qualifier date of), so I would oppose that usage. Is there another example that would make this property useful? --Izno (talk) 23:47, 22 August 2013 (UTC)

 Comment collaborator is one possible word for this, with on its own is very broad. Danrok (talk) 21:32, 30 August 2013 (UTC)

 Comment for use with awards only, it would be called the joint awardee. --Danrok (talk) 02:38, 25 September 2013 (UTC)

 Oppose "With" is too broad, it might be used instead of the best descriptive property. --DoSiDo (talk) 12:02, 4 October 2013 (UTC)

 Not done No consensus. John F. Lewis (talk) 18:50, 6 October 2013 (UTC)

Dedicated item for property

   Not done

Description	a property to identify with which property a given item is used. Can make it easier to do "one-of" constraint checks. Avoids cluttering other properties (e.g. P31)
Data type	Item
Domain	any
Allowed values	items for some of the properties with "one-of"-constraints
Example	female (Q6581072) → Q14830254

Added above template. --  Docu  at 17:33, 5 September 2013 (UTC)

Interesting idea. What tasks are needed this property? — Ivan A. Krestinin (talk) 12:45, 15 September 2013 (UTC)

It could make it easier to check one-of constraints. Instead of adding items to the list on the talk page, one would add this property to the items themselves and then using (Template:Constraint:Target required claim). --  Docu  at 12:51, 15 September 2013 (UTC)

Are {{Constraint:Type}} and {{Constraint:Value type}} better maybe? — Ivan A. Krestinin (talk) 13:01, 15 September 2013 (UTC)

I donno. Seems for larger fields. Have read a lot of advocacy about it, but I haven't seen it work yet. --  Docu  at 13:13, 15 September 2013 (UTC)

It works :-), please see Property talk:P375, Property talk:P403 as example. — Ivan A. Krestinin (talk) 14:41, 15 September 2013 (UTC)

As it works with instance of (P31) I don't see a need for this property.

but I would like to rename "Constraint:Type" to "Constraint:Domain" and "Constraint:Value Type" to "Constraint:Range". Filceolaire (talk) 20:33, 20 September 2013 (UTC)

But I  Support idea with "Dedicated item for property". Lets try this approach too. — Ivan A. Krestinin (talk) 18:12, 15 September 2013 (UTC)

I think we should avoid adding metadata to the database. My 2 cents. --Izno (talk) 18:19, 15 September 2013 (UTC)

I agree with Izno that using items and properties to define metamodel entities is inappropriate. However, unless developers suddenly realize that and propose new types of links for structuring concepts, better use such properties than doing nothing. - LaddΩ chat;) 16:37, 20 September 2013 (UTC)

As I said at #Constraint type, the devs have signaled positively that they would like to work out a better way for us to store metadata and metarelations. The better question is when, as the devs always seem to be busy with other things. :). Until such time, I think the current way to deal with metadata is fine. --Izno (talk) 20:18, 20 September 2013 (UTC)

 Not done Please see Wikidata:Project_chat#Property_Metadata. John F. Lewis (talk) 19:17, 6 October 2013 (UTC)

Property ID

   Not done

Description	The property ID, used with the proposal above.
Data type	String
Example	Q14830254=>P21
Proposed by	GZWDer (talk)

Discussion

GZWDer (talk) 10:00, 13 September 2013 (UTC)

 Support — Ivan A. Krestinin (talk) 18:12, 15 September 2013 (UTC)

 Comment seems like a hack because the dev team does not allow to use Properties entity in statements (and to put statements in properties). Really a good idea or should we talk to them ? TomT0m (talk)

 comment 2 May be useful in the Wikidata:Requests_for_comment/Constraint_violation_technical_bases discussion. TomT0m (talk) 18:25, 18 September 2013 (UTC)

 Oppose. Add Constraints to the properties instead (using templates on the talk page until we can do something else). Filceolaire (talk) 20:38, 20 September 2013 (UTC)

 Not done Please see Wikidata:Project_chat#Property_Metadata. John F. Lewis (talk) 19:15, 6 October 2013 (UTC)

domain of property

   Not done

Description	type of items that may have this property.
Data type	Item
Allowed values	person, place, organization, event, creative work, term
Example	Q14830254=>person (Q215627)
Proposed by	GZWDer (talk)

No, a solution for this kind of data is instance of (P31) with an adequate classification. See the RfC about this subject. And we don't delete the GND property to create a new one using these items. Snipre (talk) 11:19, 16 September 2013 (UTC)

Agre with Snipre. The Domain should be defined by the class (item) which the subject is an instance of. Not by these P107 items. Filceolaire (talk) 17:32, 21 September 2013 (UTC)

URL Formating string

   Not done

Description	such as http://www.wikidata.org/w/index.php?title=$1
Data type	String
Example 1	MISSING
Example 2	MISSING
Example 3	MISSING
Proposed by	GZWDer (talk)

This was already proposed. And rejected. Snipre (talk) 11:20, 16 September 2013 (UTC)

 Support. Filceolaire (talk) 20:28, 17 September 2013 (UTC)

 Comment How about some examples and a description? Danrok (talk) 02:18, 25 September 2013 (UTC)

 Oppose without a lot more clarity on what this is supposed to accomplish. Joshbaumgartner (talk) 05:25, 7 October 2013 (UTC)

Constraint type

   Not done

Description	{{Constraint}}
Data type	Item
Allowed values	Single value, Unique value, Format, One of, ...
Example 1	MISSING
Example 2	MISSING
Example 3	MISSING
Proposed by	GZWDer (talk)

The Wikidata devs have already discussed helping us with metadata management through other means and are amenable to other solutions than properties.

That aside, as I said elsewhere, we should not include metadata relevant only to Wikidata in the list of properties. --Izno (talk) 19:46, 16 September 2013 (UTC)

Property used for constraint

   Not done

Description	Used in {{Constraint:Item}} etc.
Data type	Item
Example 1	MISSING
Example 2	MISSING
Example 3	MISSING
Proposed by	GZWDer (talk)

Format used for constraint

   Not done

Description	Used in {{Constraint:Format}} etc.
Data type	String
Example 1	MISSING
Example 2	MISSING
Example 3	MISSING
Proposed by	GZWDer (talk)

Sample item: example-subject, example-property, example-object, qualifier, ...

   Not done

Description	used to migrate data in Wikidata:List_of_properties/Others and so on.
Data type	item (or string, coord, file, time, URL,...-invalid datatype (not in Module:i18n/datatype)
Allowed values	item for imported from Wikimedia project (P143)=>house cat (Q146), item for taxon rank (P105), subspecies (Q68947), English Wikipedia (Q328)
Example 1	MISSING
Example 2	MISSING
Example 3	MISSING
Proposed by	GZWDer (talk)

All marked as  Not done. Please see Wikidata:Project_chat#Property_Metadata. John F. Lewis (talk) 19:19, 6 October 2013 (UTC)

Wikivoyage banner

   Done: page banner (P948) (Talk and documentation)

Description	Wikivoyage banner
Data type	Commons media file
Domain	place
Example	New York City (Q60) => File:Loews Cineplex Times Square Banner.jpg
Source	Wikivoyage articles
Robot and gadget jobs	Bots could extract file names from Wikivoyage articles.
Proposed by	EugeneZelenko (talk)

Discussion

This will simplify articles translation and maintenance across different language versions. EugeneZelenko (talk) 14:50, 4 October 2013 (UTC)

 Support Why not, Wikidata should help the Wikimedia projects with these issues! --A.Bernhard (talk) 16:37, 4 October 2013 (UTC)

 Support--Shisma (talk) 13:16, 9 October 2013 (UTC)

 Support -- Lavallen (talk) 14:36, 9 October 2013 (UTC)

 Support --Paperoastro (talk) 14:53, 9 October 2013 (UTC)

 Support Fine, do not see any problems, the local community can always decide to overwrite the banner.--Ymblanter (talk) 18:00, 9 October 2013 (UTC)

 Support --Nicolas1981 (talk) 01:53, 11 October 2013 (UTC)

 Support This seems helpful. --Jakob (Scream about the things I've broken) 16:59, 12 October 2013 (UTC)