Wikidata:Property proposal/Archive/29

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

secrétaire adjoint (fr) – (Please translate this into English.)

   Not done

Description	position held in a french voluntary association (association loi de 1901)
Data type	Item
Domain	organization (Q43229) (organisation)
Example 1	MISSING
Example 2	MISSING
Example 3	MISSING
Proposed by	Hopala!

Discussion

Motivation Hopala! (talk) 13:48, 21 October 2014 (UTC)

 Comment: This is an incomplete proposal. The only unique content is the description, and the French version seems to mean something slightly different than the English version. Both seem to have something to do with association under the French law of 1901 (Q11513034) but I don't know what, and my native language is English. The rest of the proposal is just template messages: no examples, and no discussion of motivation. --Closeapple (talk) 07:07, 25 October 2014 (UTC)

 Comment cleaned it up a bit. --- Jura 12:15, 18 November 2014 (UTC)

 Not done. Please feel free to resubmit a more complete proposal. Ask if you need help. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 22:02, 6 March 2015 (UTC)

Journalisted ID

   Done: Journalisted ID (P1714) (Talk and documentation)

Description	Identifier on http://journalisted.com/ (Journalisted (Q18575556)) an independent, not-for-profit website (by Media Standards Trust (Q6805545)) listing the published writing of journalists and politicians
Represents	Journalisted ID (Q18575559)
Data type	String
Template parameter	|journalisted= in en:Template:UK MP links and en:Template:UK Peer links; and in its recently-created en:Template:Journalisted.
Domain	Persons
Allowed values	URL stems from Journalisted profile URLs
Example	Tom Watson (Q263802) => tom-watson (resolves to http://journalisted.com/tom-watson )
Source	Wikipedia, Journalsited
Robot and gadget jobs	Possible
Proposed by	Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits

Discussion

-- Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 21:28, 26 November 2014 (UTC)

 Support --Pasleim (talk) 18:47, 21 January 2015 (UTC)

Fach (Q1748957)

   Done: Fach vocal classification (P1731) (Talk and documentation)

Description	Fach (Q1748957), describes the special ablilites of an operatic singers voice
Represents	Fach (Q1748957)
Data type	Item
Domain	persons: operatic singers, singers of classical music. Not intended to use for singers in other music styles.
Allowed values	items that are an instance of Fach (Q1748957) like dramatic mezzo-soprano (Q6012297), Soubrette (Q836983), tenorino (Q6141663), boy soprano (Q1376492), haute-contre (Q1873389), light soprano (Q3822738) ....
Example	Fritz Wunderlich (Q57809) => lyric tenor (Q359282)
Format and edit filter validation	items with this property need to have voice type (P412), several values are common.
Proposed by	Giftzwerg 88 (talk)

Discussion

Needed to describe operatic singers and singers of classical music, may be used in infoboxes or lists. Also can be used as a qualifier to voice type (P412). Giftzwerg 88 (talk) 11:50, 24 January 2015 (UTC)

 Support --Pasleim (talk) 18:56, 30 January 2015 (UTC)

@Giftzwerg 88: @Pasleim:  Done Fach vocal classification (P1731) It seems that @GZWDer: did this a while ago. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 22:11, 6 March 2015 (UTC)

Sport number

   Not done

Description	number worn on a sports player's uniform
Represents	uniform number (Q599003)
Data type	Number (not available yet)
Domain	human (Q5)
Allowed values	number
Example	Zinedine Zidane (Q1835) member of sports team (P54) France national association football team (Q47774) => 10
Proposed by	Harmonia Amanda (talk)

Discussion

Could be used, probably mostly as a qualifier in many sports. Teams sports use numbers but many individual races do too… --Harmonia Amanda (talk) 13:18, 26 December 2014 (UTC)

•  Support Useful for sports. -Ash Crow (talk) 13:21, 26 December 2014 (UTC)
• There's already sport number (P1618) which seems to be the same. --Stryn (talk) 15:57, 26 December 2014 (UTC)
•  Not done, duplicate.--GZWDer (talk) 05:06, 31 December 2014 (UTC)

Biography at the Bundestag of Germany

   Done: biography at the Bundestag of Germany URL (P1713) (Talk and documentation)

Description	link to the biography pages of the German parliament
Data type	URL
Domain	Persons
Allowed values	URLs like http://www.bundestag.de/bundestag/abgeordnete*/biografien/*
Example	Angela Merkel (Q567) => http://www.bundestag.de/bundestag/abgeordnete18/biografien/M/merkel_angela.html
Proposed by	Hoo man (talk)

Discussion

Basically meant to replace Q14396312 which is a giant, hard to maintain key value table used to store this data now. Hoo man (talk) 23:39, 26 December 2014 (UTC)

support DerHexer (talk) 23:42, 26 December 2014 (UTC)

 Support--Oursana (talk) 11:17, 8 January 2015 (UTC)

•  Support --- Jura 20:28, 3 February 2015 (UTC)

education, studies

   Not done

Description	claim of education, studies of the item
Data type	Item
Domain	studies, professions
Allowed values	science (Q336)
Example	Beispiel: Urban VIII (Q131579) Q131579 => Q4932206 jurisprudence (Q4932206)
Format and edit filter validation	(Beispiel: eine siebenstellige Zahl kann mit dem Missbrauchsfilter 17 überprüft werden)
Robot and gadget jobs	Führen Bots oder Helferlein irgendwelche Tätigkeiten mit dieser Eigenschaft aus oder sollten sie solche Tätigkeiten ausführen? (etwa in dem sie andere Eigenschaften auf Konsistenz überprüfen, Daten sammeln etc.)
Proposed by	Oursana (talk)

Discussion

Motivation Oursana (talk) 13:19, 8 January 2015 (UTC)

Duplicate of academic major (P812) and academic minor (P811)? --Pasleim (talk) 18:45, 21 January 2015 (UTC)

Thx, I think this will do--Oursana (talk) 14:27, 24 January 2015 (UTC)

together with

   Done: together with (P1706) (Talk and documentation)

Description	persons to whom awards , or positions (rulers, kings) are only granted together with somebody else, kind of inverse property (P1696) of applies to part (P518)
Data type	Item
Template parameter	Hier den Infobox-Parameter einfügen, falls es einen gibt. Beispiel: "Bevölkerung" (population) in en:template:infobox settlement
Domain	Persons
Allowed values	human (Q5)
Example	Helene Dubreuil, Q3144755 award received (P166) Q19020Academy Awards (Q19020) => Anne Seibel Q964305 Fritz Bergius Friedrich Bergius (Q76614) award received (P166) Q44585Nobel Prize in Chemistry (Q44585) => Carl Bosch Carl Bosch (Q76606) Q61277Frederick III (Q77233) position held (P39) Prince-Elector (Q22722) of (P642) Electorate of Saxony (Q156199) =>John, Elector of Saxony (Q61277)
Proposed by	Oursana (talk)

Discussion

Motivation necessary to express a commonly granted award, or common ruling Oursana (talk) 02:14, 11 January 2015 (UTC)

•  Support--GZWDer (talk) 10:02, 21 January 2015 (UTC)

see together with (P1706), which I just noticed. Perhaps we could change this for a more general property including this proposal.--Oursana (talk) 15:53, 21 January 2015 (UTC)

•  Comment For the record, I am in favour of changing together with (P1706) to become more generic, and therefore also include this proposal. The discussion for this is currently in Wikidata:Property proposal/Generic (search for "award shared with"). Jon Harald Søby (talk) 18:21, 18 February 2015 (UTC)

 Changed together with (P1706) to encompass this as well, since there were no objections in a long time. Jon Harald Søby (talk) 00:43, 28 February 2015 (UTC)

date of oath of office

   Done: oath of office date (P1734) (Talk and documentation)

Description	date when a , use as qualifier
Represents	oath of office (Q774482)
Data type	Point in time
Template parameter	"Giuramento" in it:Giudici_della_Corte_costituzionale_della_Repubblica_Italiana#Elenco_cronologico
Domain	offices held
Allowed values	>DOB, <=DOD
Example	Sergio Mattarella (Q3956186) - position held (P39) : judge of the Constitutional Court of Italy (Q1714174) with qualifier "oath of office" : "11 October 2011"

. Discussion --- Jura 18:54, 31 January 2015 (UTC)

@Jura1:  Done oath of office date (P1734). Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 21:35, 6 March 2015 (UTC)

position held by

   Not done

Description	subject currently or formerly holds the object position or public office
Data type	Item
Template parameter	Various
Domain	Persons
Allowed values	Persons
Example	Prime Minister of Italy (Q796897) => Matteo Renzi (Q47563) (as Matteo Renzi (Q47563) => Prime Minister of Italy (Q796897) is done by position held (P39))
Source	Various
Proposed by	★ → Airon 90

Discussion

This proposal seems to be a duplicate of the "position or title held by" proposal at Wikidata:Property proposal/Person. --Yair rand (talk) 23:45, 15 September 2014 (UTC)

•  Support --- Jura 03:48, 9 December 2014 (UTC)
•  Oppose No need of inverse property: the whole list can be got through a query. Snipre (talk) 11:59, 23 December 2014 (UTC)
•  Oppose as Snipre indicated, this is an inverse property. Duplication of properties is never good. Apohllo (talk) 22:22, 15 January 2015 (UTC)

 Not done No consensus. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 23:36, 6 March 2015 (UTC)

election period in years

   Done

Description	period between elections for a parliament, council
Data type	Number (not available yet)
Template parameter	Hier den Infobox-Parameter einfügen, falls es einen gibt. Beispiel: "Bevölkerung" (population) in en:template:infobox settlement
Domain	Beispiel: General council (Q1398920), parliament (Q35749)
Allowed values	Art der verlinkten Objekte (Q-Vorlage oder Text), eine Liste der möglichen Werte oder ein Wertebereich, Muster für Strings etc.
Example	Beispiel: Q1398920 general council of a French department => election period in years => 6
Source	Externe Referenzen, Listenartikel in der Wikipedia (entweder Infobox oder Quelle)
Robot and gadget jobs	Führen Bots oder Helferlein irgendwelche Tätigkeiten mit dieser Eigenschaft aus oder sollten sie solche Tätigkeiten ausführen? (etwa in dem sie andere Eigenschaften auf Konsistenz überprüfen, Daten sammeln etc.)
Proposed by	Oursana (talk)

Discussion

Motivation: We need this property to express the election periodOursana (talk) 11:21, 15 October 2014 (UTC)

Do we need a way to clarify cases like the U.S. House of Representatives in the U.S., where there are elections every 2 years, but the term of office is 6 years, because only 1/3 of seats are up for re-election each time? Or en:Cambridge City Council where "Elections for a third of the seats take place 3 out of every 4 years" ? -- Jheald (talk) 16:22, 15 October 2014 (UTC)

strong yes, but first we have to install the general property for hundreds or thousands of parliaments in the world and their different election periods, because also in your example we need this property, and then use qualifier with applies to part (P518) 1/3 or 33 %--Oursana (talk) 22:03, 24 October 2014 (UTC)

•  Support the only question I have is the basic time unit - aren't there any elections happening every n months? Apohllo (talk) 23:27, 15 January 2015 (UTC)

yes, there are elections every "n" years therefore my property proposal "election period in years" to tell us. Thanks for your support--Oursana (talk) 15:59, 17 January 2015 (UTC)

 Weak support but I would use number datatype --Pasleim (talk) 21:45, 21 January 2015 (UTC)

 Done thx --Oursana (talk) 01:55, 27 January 2015 (UTC)

founding organization

   Not done

Description	organization that founded another organization
Data type	Item
Domain	organization (Q43229)
Allowed values	organization (Q43229)
Example	Xavier University (Q1849843) => Society of Jesus (Q36380); White Violet Center for Eco-Justice (Q7995505) => Sisters of Providence of Saint Mary-of-the-Woods (Q3977434)
Source	external reference, Wikipedia list article (either infobox or source)
Proposed by	Sweet kate (talk)

Discussion

With founded by (P112) being limited to the domain of person (Q215627), there's no current way I see to indicate when something was founded by an organization. Lots of schools are founded by religious organizations, new non-profits are organized by other non-profits, foundations are chartered by social groups, etc. Unless someone has a better idea? Sweet kate (talk) 22:30, 24 November 2014 (UTC)

 Support Very useful also for hospitals: Haydom Lutheran Hospital (Q15838483) => Norwegian Lutheran Mission (Q1770870). It might be good to at least discuss a domain change for founded by (P112). --Tobias1984 (talk) 09:14, 25 November 2014 (UTC)

 Oppose Use founded by (P112). Snipre (talk) 13:53, 25 November 2014 (UTC)

 Oppose Same as Snipre. --Casper Tinan (talk) 14:08, 25 November 2014 (UTC)

Then as Tobias1984 says, we need a domain change for founded by (P112). How do we make that happen? (I was using founded by (P112) and it was telling me it was a constraint violation, which is why I requested this property.) Sweet kate (talk) 14:58, 25 November 2014 (UTC)

@Sweet kate: I just checked, and the constraint template can't handle or-relationships at the moment Template:Constraint:Value_type. I think we will just have to ignore the constraint violations until the template can handle this. Maybe User:Ivan A. Krestinin has a better idea? --Tobias1984 (talk) 15:17, 25 November 2014 (UTC)

There are technical ways to resolve this. But I am not sure that relations person -> organization and organization -> organization are the same type of relations. founded by (P112) is used already in 4 templates in ruwiki and in unknown number of templates in other wikies. Are you sure that these infoboxes are ready to display organizations too? Labels and another context of these infoboxes can conflict with organizations. It is more simple to split two properties in infobox than filter single property. Also difficult cases can present with organization was founded by some person, but some organization is legal and financial founder. So I think more accurate way is creating new property, so  Support. — Ivan A. Krestinin (talk) 19:41, 25 November 2014 (UTC)

@Snipre:, @Casper Tinan:, given Ivan A. Krestinin's feedback, any additional thoughts? Sweet kate (talk) 21:57, 8 January 2015 (UTC)

No, we have to change the constraints. For me they are no problems because we can filter and differentiate person from organizations using P31. From concept point of view there is no reasons to differentiate persons and organizations in term of fondation. Snipre (talk) 10:06, 16 January 2015 (UTC)

I cannot see in what way the Founder-foundation relation could differ depending on the nature of the founder. As the concept is the same, there is no reason for creating a duplicate property.Casper Tinan (talk) 10:32, 16 January 2015 (UTC)

 Oppose the constraint on founded by (P112) should be changed to juridical person (Q155076) and that would allow both people and organizations to be founders of other organizations Apohllo (talk) 00:34, 16 January 2015 (UTC)

 Oppose Good faith proposal, but use founded by (P112), modified per Apohllo. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 18:00, 16 January 2015 (UTC)

 Not done Consensus is clearly against (even discounting my own !vote). Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 23:39, 6 March 2015 (UTC)

church

   Not done

Description	church that belongs to this religion
Represents	Christianity (Q5043)
Data type	wikidata (example : Q9592)-invalid datatype (not in Module:i18n/datatype)
Domain	Q templates
Allowed values	text
Example	Vytautas (Q218186) : church → Catholic Church (as a subproperty of religion = Q5043) / (as a subproperty of P1636 = 1386) — church → Orthodox Church (as a subproperty of P1636 = 1384)
Source	référence externe, article de liste de Wikipédia (soit infobox, soit source)
Proposed by	genium ⟨✉⟩

Discussion

Catholicism is not a new religion, it's an instance of Catholic Church, please see http://it.cathopedia.org/wiki/Cattolicesimo This rule also applies to Orthodox Church, etc… but also in Islam (chiisme, sunnisme, etc.), I don't know for Jusdaism. genium ⟨✉⟩ 03:05, 22 February 2015 (UTC)

•  Oppose, "Catholic Church" is perfectly fine for use as a listed religion of a person. This property would complicate things. Keep it simple. --AmaryllisGardener ^talk 03:33, 22 February 2015 (UTC)
•  Oppose dupplicate of religion or worldview (P140). --Fralambert (talk) 03:42, 22 February 2015 (UTC)
•  Strong oppose Per this. The user has modified several main items to prove his point without providing valid references or making sense at all. Andreasm ^{háblame / just talk to me} 16:23, 22 February 2015 (UTC)

 Not done Strong consensus against. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 23:35, 6 March 2015 (UTC)

Naturbase ID

   Done: Naturbase ID (P1732) (Talk and documentation)

Description	ID in the Naturbase database by the Norwegian Environment Agency
Represents	Naturbase (Q11990971)
Data type	String
Template parameter	no:Mal:Naturbase
Domain	places (and possibly species)
Allowed values	string pattern [A-Z][A-Z]\d{8,8}
Example	Skipsfjord conservation area (Q19323599) => VV00000090
Format and edit filter validation	(sample: 7 digit number can be validated with edit filter Special:AbuseFilter/17)
Source	no:Mal:Naturbase
Robot and gadget jobs	My bot can import values from nowiki and nnwiki
Proposed by	Jon Harald Søby (talk)

Discussion

This would be useful for parks and other protected areas of Norway. Quite an extensive database. Jon Harald Søby (talk) 03:03, 20 February 2015 (UTC)

 Created as there were no objections in one week. Jon Harald Søby (talk) 18:21, 27 February 2015 (UTC)

Category for films shot at this location

   Done: category for films shot at this location (P1740) (Talk and documentation)

Description	see WikiProject Filming Locations for more information.
Data type	Item
Domain	categories
Allowed values	items with instance of (P31)=Wikimedia category (Q4167836) and category combines topics (P971)=filming location (Q1045481) and category combines topics (P971)=location
Example	Amsterdam (Q727): Category:Films shot in Amsterdam (Q10217113)
Source	these categories
Robot and gadget jobs	can be added with quickstate

Similar to P:P1464. Not terribly useful in itself, but with quickstate, it makes it easy to map these categories to locations and in a second step, the content of these categories to filming location (P915). --- Jura 17:12, 2 March 2015 (UTC)

 Created as category for films shot at this location (P1740). Jon Harald Søby (talk) 17:29, 9 March 2015 (UTC)

Central government debt as a percent of GDP

   Done: central government debt as a percent of GDP (P1689) (Talk and documentation)

Description	Amount of central government debt divided by the GDP of the country
Data type	number (percent)-invalid datatype (not in Module:i18n/datatype)
Domain	Countries, regions and cities
Allowed values	A positive percentage
Example	87%
Source	http://data.worldbank.org/indicator/GC.DOD.TOTL.GD.ZS
Robot and gadget jobs	Global Economic Map Bot can do this
Proposed by	Mcnabber091 (talk) 19:01, 14 April 2014 (UTC)

 SupportMcnabber091 (talk) 10:14, 16 May 2014 (UTC)

 Support Amir (talk) 21:32, 23 May 2014 (UTC)

Unsure. I think we need items for central govt of X (but that may be a bit tricky). If we have that + a "debt" property, we do not need a property for the ratio. --Zolo (talk) 19:52, 10 June 2014 (UTC)

 Support Eurodyne (talk) 05:12, 25 October 2014 (UTC)

• @Mcnabber091, Ladsgroup, Zolo, Eurodyne:  Done --Jakob (talk) 01:28, 1 January 2015 (UTC)

Flora of North America

   Done: Flora of North America taxon ID (P1727) (Talk and documentation)

Description	TaxonId in Flora of North America (Q1429295)
Represents	plant (Q756)
Data type	String
Domain	plant (Q756)
Example	Orchidaceae (Q25308) => 10638
Source	Flora of North America (Q1429295) ([FNA])
Robot and gadget jobs	Add 'http://www.efloras.org/florataxon.aspx?flora_id=1&taxon_id=$1' to Gadget-AuthorityControl.js
Proposed by	Succu (talk)

Discussion

As suggested by Brya it would be good to have some eFloras on board. So let's start us with the Flora of North America. --Succu (talk) 15:52, 16 February 2015 (UTC)

 Support. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 17:42, 16 February 2015 (UTC)

 Support Obviously, I am in favour. This would have been one of the first things I would have added. As all the e-flora's use the same number, perhaps they can be handled all together? Not sure how many of them are really interesting (North America, China, Pakistan, Taiwan, any others?). - Brya (talk) 18:19, 16 February 2015 (UTC)

Unfortunately we have to create a separate property for each flora, because we want to provide a direct link to the correct entry. BTW: With the FNA we can link to more than 10,000 entries. I didn't checked the others yet. --Succu (talk) 12:35, 24 February 2015 (UTC)

 Support It was not already done? --Fralambert (talk) 22:29, 16 February 2015 (UTC)

@Succu, Brya, Pigsonthewing:  Done --Fralambert (talk) 01:01, 27 February 2015 (UTC)

General formula (wikt:general formula)

   Done: general formula (P1673) (Talk and documentation)

Description	molecular formula of a class of compounds
Data type	string + string for n= + up to n items for R1 to Rn-invalid datatype (not in Module:i18n/datatype)
Domain	maybe group of isomeric entities (Q15711994)
Example	Q41581 => CnH2n+2, (n = 1, 2, 3, 4, ...) Q2602701 => R¹R²C=N−R³ with R³ IS NOT hydrogen (Q556)
Source	Externe Referenzen, Listenartikel in der Wikipedia (entweder Infobox oder Quelle)
Proposed by	Kopiersperre (talk)

Discussion

@Kopiersperre: There is a relevant discussion and bug report here: Wikidata_talk:Development_plan#Formula_datatype -Tobias1984 (talk) 21:32, 20 October 2014 (UTC)

 Support. If a 'Formula' datatype which allows xml text is created eventually then this can be replaced. In the meantime this property will be useful. Filceolaire (talk) 23:03, 2 November 2014 (UTC)

Merck Index monograph ID

   Done: Merck Index monograph (P1738) (Talk and documentation)

Description	Identifier of a chemical, in The Merck index Online.
Represents	The Merck Index (Q663360)
Data type	String
Template parameter	n/a
Domain	chemical elements or compounds
Allowed values	URL stems from The Merck Index Online
Example	D-ribofuranose (Q179271) => mono1500008328 => https://www.rsc.org/Merck-Index/monograph/mono1500008328
Source	The Merck Index Online
Formatter URL	https://www.rsc.org/Merck-Index/monograph/$1
Robot and gadget jobs	Possible
Proposed by	Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits

Discussion

Useful identifier and disambiguator. Widely cited in Wikipedia. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 16:59, 9 February 2015 (UTC)

 Support Snipre (talk) 11:39, 3 March 2015 (UTC)

 Support --Succu (talk) 11:46, 3 March 2015 (UTC)

• @Snipre: @Succu:  Done. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 12:37, 9 March 2015 (UTC)

number confirmed

   Done: number confirmed (P1674) (Talk and documentation)

Description	qualifier; number of occurrences classified as confirmed for reporting purposes
Data type	Number (not available yet)
Template parameter	None yet.
Domain	disease outbreak (Q3241045)
Allowed values	Non-negative integers
Example	2014 Ebola virus epidemic in Liberia (Q18208679) number of cases 6,253, number confirmed 2,515
Source	Health institutes, e.g. World Health Organization, US Centers for Disease Control and Prevention
Proposed by	Emw (talk)

Case definitions for infectious conditions under public health surveillance (US CDC, 1997) provides definitions for various case definitions used in epidemiology. In the scope of Wikidata, number confirmed, number probable and number suspected seem relevant. These would be used as qualifiers on number of cases claims.

The WHO and CDC provide case definitions for outbreaks and uses these for reporting, e.g. http://www.who.int/csr/resources/publications/ebola/ebola-case-definition-contact-en.pdf, http://www.who.int/csr/disease/swineflu/WHO_case_definition_swine_flu_2009_04_29.pdf. The coarser number of cases (proposed above) is typically used by mass media, but more granular figures are also of interest in comprehensive coverage. Emw (talk) 03:55, 31 October 2014 (UTC)

 Support. Filceolaire (talk) 23:25, 2 November 2014 (UTC)

 Support Wikidata should store information from reliable sources about particular disease outbreaks. This data is especially useful when particular Wikipedia articles cover those diseases. The paper "Case definitions for infectious conditions under public health surveillance" is a good idea for defining what characteristics of disease outbreaks should be measured and quantified, and what the numbers presented mean. When this kind of information is available it seems reasonable to put it in Wikidata because this is the sort of information which could be called in multiple Wikimedia projects. Blue Rasberry (talk) 15:33, 14 November 2014 (UTC)

number probable

   Done: number probable (P1675) (Talk and documentation)

Description	qualifier for number of cases; number of occurrences classified as probable for reporting purposes
Data type	Number (not available yet)
Template parameter	None yet.
Domain	disease outbreak (Q3241045)
Allowed values	Non-negative integers
Example	2014 Ebola virus epidemic in Liberia (Q18208679) number of cases 6,253, number probable 1,540
Source	Health institutes, e.g. World Health Organization, US Centers for Disease Control and Prevention
Proposed by	Emw (talk)

See motivation for number confirmed proposal above. Emw (talk) 04:01, 31 October 2014 (UTC)

 Support. Filceolaire (talk) 23:25, 2 November 2014 (UTC)

 Support on the same rationale as I made for "number confirmed" property. Blue Rasberry (talk) 15:33, 14 November 2014 (UTC)

number suspected

   Done: number suspected (P1676) (Talk and documentation)

Description	qualifier for number of cases; number of occurrences classified as suspected for reporting purposes
Data type	Number (not available yet)
Template parameter	None yet.
Domain	disease outbreak (Q3241045)
Allowed values	Non-negative integers
Example	2014 Ebola virus epidemic in Liberia (Q18208679) number of cases 6,253, number suspected 2,480
Source	Health institutes, e.g. World Health Organization, US Centers for Disease Control and Prevention
Proposed by	Emw (talk)

See motivation for number confirmed proposal above. Emw (talk) 04:01, 31 October 2014 (UTC)

 Support. Filceolaire (talk) 23:25, 2 November 2014 (UTC)

 Support on the same rationale as I made for "number confirmed" property. Blue Rasberry (talk) 15:33, 14 November 2014 (UTC)

index case of

   Done: index case of (P1677) (Talk and documentation)

Description	primary case, patient zero: initial patient in the population of an epidemiological investigation
Data type	Item
Template parameter	None yet.
Domain	disease outbreak (Q3241045)
Allowed values	human (Q5)
Example	Thomas Eric Duncan (Q18249266) index case of Ebola virus disease in the United States (Q17486597)
Source	Health institutes, e.g. World Health Organization, US Centers for Disease Control and Prevention
Proposed by	Emw (talk)

 Support. Filceolaire (talk) 23:25, 2 November 2014 (UTC)

 Support on the same rationale as I made for "number confirmed" property. Blue Rasberry (talk) 15:33, 14 November 2014 (UTC)

has vertex figure

   Done: has vertex figure (P1678) (Talk and documentation)

Description	the figure exposed when a corner of a polytope is sliced off.
Data type	Item
Template parameter	"vertex figure" in en:template:Infobox_polyhedron and en:template:Infobox_polychoron
Domain	vertex figure (Q598843)
Allowed values	polytope (Q747980)
Example	cuboctahedron (Q847941) => rectangle (Q209), 600-cell (Q2610844) => icosahedron (Q188758), pentagon (Q127840) => line segment (Q166154) ,
Source	infoboxes
Robot and gadget jobs	leeching infoboxes.
Proposed by	opensofias (talk)

Discussion

it's basically the opposite of has facet polytope (P1312) --opensofias (talk) 18:32, 6 October 2014 (UTC)

Opensofias
Tobias1984
Arthur Rubin
Cuvwb
TomT0m
Physikerwelt
Lymantria
Bigbossfarin
Infovarius
Helder
PhilMINT
Malore
Lore.mazza51
Wikisaurus
The Anome
The-erinaceous-one
Daniel Mietchen
Haansn08
Xenmorpha
John Samuel
Jeremy Dover
Toni 001
Bocardodarapti
Duckmather
HTinC23
fgnievinski

Notified participants of WikiProject Mathematics

 Support -Tobias1984 (talk) 18:11, 8 October 2014 (UTC)

second image

   Not done

Description	вторая важная иллюстрация к теме
Data type	Commons media file
Template parameter	en:Template:Taxobox: image2
Example	Green-tailed Sunbird (Q3238764) => Green tailed Sunbird.jpg
Proposed by	Termininja (talk)

Discussion

Property similar to image (P18). They both together can be used in pages like en:Green-tailed sunbird. Termininja (talk) 10:21, 23 February 2015 (UTC)

•  Oppose Multiple images can be displayed using Lua.--GZWDer (talk) 12:52, 23 February 2015 (UTC)

 Not done - no support, apparently not necessary. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 12:43, 9 March 2015 (UTC)

inverse of

   Done: inverse property (P1696) (Talk and documentation)

Description	links a property to its inverse property. Implements owl:inverseOf.
Represents	inverse element (Q338057)
Data type	Property
Domain	Wikidata property (Q18616576)
Allowed values	any Wikidata property (Q18616576)
Example	part of (P361) => has part(s) (P527); shares border with (P47) => shares border with (P47)
Proposed by	Filceolaire (talk)

Discussion

This is so that we can identify where one property is the inverse of another property. For Symmetric properties the object can be the same as the subject as the second example above. This is different from the Constraint as in most cases we will not be requiring that there is always a statement using the reverse property wherever the property is used. Filceolaire (talk) 17:36, 13 November 2014 (UTC)

•  Support -- LaddΩ chat ;) 18:12, 13 November 2014 (UTC)
  • Example of symmetric property changed from P7 (P7) to shares border with (P47). Brother is not symmetricbecause of Sister. Filceolaire (talk) 13:30, 14 November 2014 (UTC)
•  Support --Paperoastro (talk) 21:50, 15 November 2014 (UTC)
•  Support. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 12:30, 26 November 2014 (UTC)
•  Support. http://www.w3.org/TR/owl-ref/#InverseFunctionalProperty-def owl:inverseOf should be the definitive semantics here. Emw (talk) 03:17, 4 December 2014 (UTC)
•  Oppose We should avoid inverse properties: this just creates a set of redundant data and lead to heavy items (like Germany) which can't be loaded easily. Query has to be used instead of inverse property. Snipre (talk) 07:44, 13 December 2014 (UTC)
  • This is for use on properties, not items. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 19:39, 14 December 2014 (UTC)
•  Support.--Oursana (talk) 11:56, 17 December 2014 (UTC)
•  Comment: Filceolaire, Laddo, Paperoastro, Snipre, Andy, Oursana, I have updated the proposed description to note that this property maps specifically to owl:InverseFunctionalProperty. This should help clarify things for downstream users and align us with Semantic Web standards. Emw (talk) 05:51, 19 December 2014 (UTC)
  • Good work. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 12:45, 20 December 2014 (UTC)
  • I'm agree. --Paperoastro (talk) 12:25, 21 December 2014 (UTC)

I've updated the property to note it implements owl:inverseOf, not owl:InverseFunctionalProperty, per Vladimir's comment below.

•  Oppose Oppose Have to agree with @Snipre: owl:inverseOf just creates redundant triples.
  • Since you can query a relation in any direction (in WDQ, in a SPARQL triple pattern, even in a SPARQL property path), inverses are never necessary
  • An entity with many incoming relations (eg Germany) will also get a lot of outgoing relations, and its RDF file (to be served out of the entity URL when one of the RDF mime types is requested) may become too large. That's why in the Getty vocabularies LOD we decided to eliminate downward properties.
  • Read the judicious reasons why the PROV ontology has no inverses. And even more: reserves the names of potential inverse properties. Wikidata might adopt such practice, but DO NOT create pairs of inverse properties!
  • @Emw: owl:inverseOf has nothing to do with owl:InverseFunctionalProperty. IFP is used for stuff like "if two people have the same SSN then they are the same person". --Vladimir Alexiev (talk) 02:45, 23 December 2014 (UTC)

Vladimir, thanks for the correction regarding owl:inverseOf and owl:InverseFunctionalProperty, and for the pointers to PROV-O and the Getty Vocabularies. Given that other major vocabularies like the Relation Ontology (RO) use inverse properties and owl:inverseOf is a widely used feature per http://arxiv.org/pdf/1202.0984, it's not immediately clear to me that inverse of would be a bad idea. I'll need to read around more, but those resources you are good to have on hand. Emw (talk) 08:14, 23 December 2014 (UTC)

User:Emw, I work for a semantic repository vendor, so I can only say "the more triples the better" ;-). But you should consider the consequences. If you create Q an inverse property of P, then both props will get used. Then the RDF export either has to materialize all pairs xPy and yQx, or leave it to a reasoner or repo to do the inverse inferencing, or burden the user with seeking both patterns ?x P ?y and ?y Q ?x in queries. Which is exactly what PROV wants to avoid.

The right approach is not to omit an inverse declaration, but NOT to create Q in the first place: you don't need redundant properties. --Vladimir Alexiev (talk) 09:01, 23 December 2014 (UTC)

@Vladimir Alexiev, Snipre: This proposal is about creating the "inverseOf" property, not choosing if we should have properties that are inverse of others. It's a point that is more important than the creation of this property and should maybe be the topic of a WD:RFC. As there are currently some properties that are inverse of an other, do you agree to the creation of an "inverseOf" property in order to manage them (property that may be removed when we will get free of properties that are "inverseOf" others if there is a community consensus about it)? Tpt (talk) 10:30, 23 December 2014 (UTC)

 Support @Tpt: if inverseOf will be clearly described as a book-keeping property, used to "seek and destroy" actual inverses; with a reference to the PROV considerations given above. What I oppose is to make automatic inferencing for inverse and symmetric properties, which I've seen elsewhere in a request

•  Support Tpt (talk) 10:30, 23 December 2014 (UTC)

instance of/property type/characteristics

   Not done

Description	Specifies if a property is transitive, non-transitive, symmettric
Data type	item,-invalid datatype (not in Module:i18n/datatype)
Domain	Item
Allowed values	Transitive, non-transitive, symmetric.
Example	father (P22) => non-transitive. located in the administrative territorial entity (P131) => transitive. shares border with (P47) => symmetric
Format and edit filter validation	allowed values only
Robot and gadget jobs	no
Proposed by	Filceolaire (talk)

Discussion

Some properties are transitive i.e. if A => B and B => C then A => C. Others are not. This allows us to specify for each property which case applies. This property can also be used for any other boolean properties/characteristics. Knowing whether or not a property is transitive will mean will mean we know whether or not we can follow a property up the chain. Filceolaire (talk) 17:53, 13 November 2014 (UTC)

Amended to change example of symmetric property from P7 (P7) to shares border with (P47). Filceolaire (talk) 13:32, 14 November 2014 (UTC)

•  Support. Also companion of (P399) is a symmetric property. --Paperoastro (talk) 21:55, 15 November 2014 (UTC)
• Should instance of (P31) be used?--GZWDer (talk) 10:06, 29 November 2014 (UTC)

   Oppose After the structure proposed by Emw, I change my support if favor to P31. --Paperoastro (talk) 12:32, 21 December 2014 (UTC)

•  Comment: this needs input from people knowledgeable about OWL or intending to use Wikidata's RDF / OWL exports. OWL 2 allows properties to be declared symmetric, transitive, reflexive, irreflexive, and asymmetric. See Section 2.2.3 in the OWL 2 New Features and Rationale recommendation for details and examples. We need to be able to say the same about our properties in a way that maintains clear, straightforward compatibility with OWL 2 DL, the reference ontology language of the Semantic Web. I'll ask for input from the wikidata-l mailing list. Emw (talk) 03:26, 19 December 2014 (UTC)
•  Oppose As in OWL I think we should use instance of (P31) for that. See this email. Tpt (talk) 08:28, 19 December 2014 (UTC)
•  Oppose per Denny's comment in this email. instance of (P31) is rdf:type; thus we should use P31 and not a new property to declare that a property is transitive, etc.

I have created several special items to fulfill this structural need:

• transitive Wikidata property (Q18647515)
• symmetric property (Q18647518)
• asymmetric Wikidata property (Q18647519)
• Q18647520 (may need to be merged with asymmetric Wikidata property (Q18647519), see note below)
• reflexive property (Q18647521)
• Q18647522

For example, the OWL spec notes that "in mereology, the partOf relation is defined to be transitive, reflexive, and antisymmetric". We should model this like so:

part of (P361)

• instance of (P31) transitive Wikidata property (Q18647515)
• instance of (P31) reflexive property (Q18647521)
• instance of (P31) asymmetric Wikidata property (Q18647519)

Emw (talk) 14:52, 19 December 2014 (UTC)

Note: apparently OWL considers asymmetric and antisymmetric properties to be the same. http://math.stackexchange.com/questions/778164/is-an-anti-symmetric-and-asymmetric-relation-the-same-are-irreflexive-and-anti seems to contradict that. I'm rusty on my logic and don't have time at the moment to investigate that further. In any case, we should not be going outside OWL in these kinds of statements, so I've updated the 'part of' example above to use 'asymmetric' rather than 'antisymmetric'. We should merge Q18647520 into asymmetric Wikidata property (Q18647519) if 'antisymmetric' is conflated with 'asymmetric' in OWL. Emw (talk) 15:01, 19 December 2014 (UTC)

• "Comply with semantic web standards" sounds right and mighty, but the fact is that there's modest RDFS inferencing on the real semantic web, and very little OWL inferencing. In general, we should not introduce property characteristics before the Wikidata community fully understands the implications of RDFS & OWL inferencing. The horrible class hierarchy shows that the community does not understand even the implications of rdfs:subClassOf. --Vladimir Alexiev (talk) 03:14, 23 December 2014 (UTC)
  •  Oppose owl:ReflexiveProperty P means xPx for every item x. You don't want that, believe me!
  •  Oppose owl:TransitiveProperty P means xPy & yPz => xPz. However, it's always better to know which is the step property Q (eg "part of" has step property "member of"), then declare xPy & yQz => xPz. The step property is useful on its own, and declaring it allows more efficient inferencing. See this Ontotext GraphDB performance hint
  •  Comment owl:AsymmetricProperty P means you can never have xPy & yPx (whereas antisymmetric allows that for x=y)
  • ({Comment}} How about owl:FunctionalProperty P? Meaning: xPy & xPz => y=z
  • ({Comment}} How about owl:InverseFunctionalProperty P? Meaning: xPy & zPy => x=z
  • ({Comment}} How about P owl:propertyChainAxiom (Q,R)? Meaning: xQy & yRz => xPz

Vladimir Alexiev, thanks for those summaries. I agree that Wikidatans should be made aware of the definition and implications of these property characteristics. At the same time, I think we should support these Semantic Web standards from OWL 2 DL in Wikidata, even if certain technologies like Ontotext's GraphDB may not.

User:Emw, I never said GraphDB does not support them (in fact it supports them more efficiently than many competing products). I'm only making wikipedians aware of what these mean in terms of inference. (Please don't talk of "OWL DL": OWL2 has 3 more profiles: EL, RL and QL, that are just as important as DL. Talk of "OWL2".)

Vladimir, referring to "OWL 2 DL" is entirely reasonable and done in many reliable sources. Including the "2" makes sense because OWL 1 DL doesn't include several major features of OWL 2 DL, e.g. punning. Including the "DL" makes sense because it distinguishes the referrent from OWL Full. As noted in Section 10 of the OWL 2 Primer, all OWL 2 EL, RL and QL reasoners are also OWL 2 DL reasoners, but OWL 2 DL is tuned for a more general set of cases. So if we want to talk about the current decidable subset of OWL without getting into the weeds of the various more specific profiles -- as I think we often do when discussing modeling issues on Wikidata -- the way to do so is by referring to "OWL 2 DL". And if we're being persnickety, then it should be "OWL 2" not "OWL2", as most reliable sources use the spaced styling. Emw (talk) 16:13, 24 December 2014 (UTC)

@Emw: "Decidable" is not the same as "decidable in a reasonable amount of time". RL, QL, EL have many benefits compared to DL, which itself has benefits compared to Full, that's why W3C bothered to define RL, QL, EL in OWL2. It's not the time and place to decide on any sort of commitment that Wikidata may have towards DL, RL, QL, EL, that's why I suggest you don't refer to DL specifically, refer just to "OWL 2". Vladimir Alexiev (talk) 14:08, 25 December 2014 (UTC), corrected on 7 Jan 2015.

Major ontologies use owl:ReflexiveProperty and owl:TransitiveProperty. The OWL 2 recommendation outlines stories for these features in Use Case #5, Use Case #6 and Use Case #8. See Simple part-whole relations in OWL Ontologies by Rector et al. and Relations in Biomedical Ontologies (RO) by Smith et al. for descriptions of how part of (P361) is transitive, reflexive and asymmetric. RO is a foundation in many natural science ontologies. So we do indeed want a way to represent owl:ReflexiveProperty, for example.

Transitivity is no doubt needed. But consider again what I wrote about owl:ReflexiveProperty above (local reflexivity = self-restriction is another story, see below). I think we need stronger practical (actual) examples of what it's useful for. RDFS and OWL also define a bunch of properties to be reflexive, including rdfs:subClassOf and rdfs:subPropertyOf. But I cannot think of any practical use for this reflexivity: can you?

You said: "owl:ReflexiveProperty P means xPx for every item x. You don't want that, believe me!"? The description is helpful but neither that in itself nor the vague warning is a compelling argument against encoding reflexivity in property statements. Regarding their usefulness, see the use cases linked in the comment you're replying to, and the discussions of part of in the linked papers. Emw (talk) 16:13, 24 December 2014 (UTC)

This is not a vague warning, but a very real consequence of using reflexive properties. If you declare such owl:ReflexiveProperty for some props and export the ontology to RDF & OWL, complying repositories have to to make these inferences. For example, "x rdfs:subClassOf x" and "p rdfs:subPropertyOf p" for every class and property. And speaking from experience, these are always useless. If you want to declare part of as reflexive, then for each item you must make the reflexive claim (at least for items falling in its domain), else the property is violated. In other words, interpreting part of as proper part of is more sensible and useful. Vladimir Alexiev (talk) 14:08, 25 December 2014 (UTC)

I am wary of tying Wikidata's vocabulary to seemingly custom, proprietary features like step properties used in only one particular software product.

Likewise I think we should avoid defining "real" Semantic Web inferencing in a way that excludes significant RDFS and OWL inferencing engines like, say, ELK, Pellet, Racer and FaCT and ontologies that use owl:TransitiveProperty like those in the OBO Foundry.

I never said to exclude TransitiveProperty (just gave a better construct that ties step & transitive). I don't understand how you concluded that "step properties" is a feature of our product. It's a very basic concept: many transitive properties feed off (are declared as superproperties of) a step property. Example from wikidata: "member of" is the step property of "part of". Example from SKOS: skos:broader is the step property of skos:broaderTransitive. RDFS is amiss not to declare such, so both of the most popular RDF APIs do it: Sesame (sesame:directSubClassOf, sesame:directSubPropertyOf and sesame:directType) and Jena.

I concluded that step properties were a feature of your software because the link in your previous comment ("See this Ontotext GraphDB performance hint") links to a section titled "TransitiveProperty Through Step Property". The fact that that's a subsection of "Consider Specialized Property Constructs" (emphasis mine) and https://www.google.com/search?q=%22step+property%22+ontology returns no clearly applicable results suggests that "step property" is a non-standard term with no (or little) use beyond your Ontotext product. It's discussed in the context of a "transitiveOver" property construct, which is also non-standard. The optimization technique may well be useful, but in my opinion the proper place to discuss supporting it is a W3C mailing list, e.g. http://lists.w3.org/Archives/Public/www-rdf-interest/ or http://lists.w3.org/Archives/Public/public-owl-dev/ rather than a project that strives for compatibility with current Semantic Web standards.

You concluded wrong. These are suggestions and ideas how to implement a transitive property more efficiently by declaring which is its step property. They are not "ontologies" nor features of GraphDB. They are not limited to GraphDB: the same considerations apply to any reasoner.

The basic idea of Semantic Web is openness: anyone is free to create new constructs (and it's no coincidence that all RDFS and OWL constructs are expressed in RDF, i.e. the schema and data are expressed using the same data model). If Wikidata adopts a construct like "p transitiveOver q", that will allow more efficient reasoning with transitive properties, and at the same time can be exported using the standard construct Vladimir Alexiev (talk) 14:08, 25 December 2014 (UTC)

 p ptop:transitiveOver q.
 q rdfs:subProperty of p.
 p owl:TransitiveProperty.

That said, if you could convince Markus Krötzsch that Wikidata should support step properties as you suggest, then I would probably support your proposal. Otherwise, I think we can use standard techniques to achieve something like step properties. For example, part of (P361) would have the statement "instance of (P31) transitive Wikidata property (Q18647515)" and member of (P463) could be made a "step property" by the claim "member of subproperty of (P1647) part of". Property transitivity is not inherited via subproperty of to my understanding, so member of would thus be a non-transitive step property of part of by those straightfoward, standards-compliant techniques. Emw (talk) 16:13, 24 December 2014 (UTC)

In my page above I also write that "subPropertyOf" could be used to declare the step property, HOWEVER that's not fully robust. The reasoner also needs a "promise" that the transitive property won't be asserted explicitly (ad-hoc). If not, transitiveOver will miss to make some part of the closure, since it seeks to extend the path only using the step prop, not the transitive prop (that's what makes the reasoning faster). I think this matches best-practice usage: editors will only claim member of whereas some reasoning mechanism will infer part of as the closure of member. Vladimir Alexiev (talk) 14:08, 25 December 2014 (UTC)

I agree that Wikidata's class hierarchy is messy, particularly towards the top. I would say that derives at least as much from differences in philosophical perspective as misunderstanding of the implications of rdfs:subClassOf (subclass of (P279)). We could clean up our class hierarachy by importing a well-known upper ontology like, say, BFO, but I think that's a separate discussion. For now I think educating the Wikidata community on basic things like "what is a reflexive property?", etc. in an easy-to-understand way would greatly help.

I hope we won't have to go the BFO or DOLCE way, IMHO it's too abstract for most people.

The main reasons are: 1. there's no editorial control over "subclass of" (which is just as important as property definition), 2. No editorial control over "instance of" (which is non-transitive and a critical point: no classes below this point admitted). 3. No clarity what's "design" vs what's a "physical item", something that FRBR addressed 10-15 years ago for Works. @Emw: Could you please help me start a RFD on this important topic?

BFO, DOLCE, SUMO etc. are easy to crudely simplify to everyday terms (s/continuant/object, s/occurrent/event, etc.) and they provide a robust ontological framework for representing knowledge. They are also used in many of the world's major scientific ontologies, e.g. Gene Ontology and other OBO Foundry ontologies.

BFO at least has a clear way to discuss "design" vs. "physical item"; see the Information Artifact Ontology and its constituent Document Act Ontology (more). These are both considerably more comprehensive than FRBR as they take into account a broad range of knowledge describable via documentality. They also have the advantage of being coherently tied back to an upper ontology, and seeing use in many domain ontologies.

I don't see how your points 1 and 2 are arguments against importing an upper ontology like BFO. The fact that there is little active curation of the top of the hierarchy is as much an argument against having a hierarchy as it is an argument against having an imported upper hierarchy -- both would be subject to uninformed editors adding mistaken claims and making the hierarchy a mess. Same with your comment on instance of; how it is specifically an argument against importing an upper ontology like BFO is unclear. And your "no classes below this point admitted" comment warrants refinement: Wikidata is replete with metamodeling, where classes are classified with instance of and have many classes below them via asserted subclass of claims.

I'm not arguing against BFO, I said I hope we won't have to go to such levels since they're complex. I very much doubt your claim "they're easy to simplify". I think it'll take real ontologists to figure out how to apply it to Wikidata, and then a genius to cast it to practical terms that the wide editorial community can understand. Wikidata, IMHO, needs first and foremost practical solutions!). I've worked with data models for 20 years and ontologies for 4 years, but I'll admit without shame that I'm a little scared. I've read about BFO (in the context of VIVO), I'll read about IAO, DAO, documentality.

 Comment If you want a great way to waste your Christmas holidays, read about ISO 15926. It's used in the process industries (eg oil & gas) to describe very complex dynamic systems, with data coming from many parties. Eg see http://15926.org/publications/templates/introduction/index.htm#Lifted_Templates. See here for a "self-study" program: http://levenchuk.com/2012/10/01/iso-15926-self-education-sequence/. Vladimir Alexiev (talk) 14:08, 25 December 2014 (UTC)

If you would like to start a Request for Comment (RFC) on FRBR, IAO, DAO, documentality, etc., the place to do so is Wikidata:Requests_for_comment. I would be happy to participate, or even give feedback on a draft. Emw (talk) 16:13, 24 December 2014 (UTC)

I'll start it and very much would like if we draft it together. I feel the class hierarchy mess is an urgent and important problem. But I don't have ready solutions. And I think you write very clearly (and take the time to make it clear), which is needed for this RFC. Vladimir Alexiev (talk) 14:08, 25 December 2014 (UTC)

You ask about how we can represent owl:FunctionalProperty, owl:InverseFunctionalProperty and owl:propertyChainAxiom. Good question! We may be able to capture such knowledge in Wikidata property statements, but like universal and existential quantifier knowledge from owl:allValuesFrom and owl:someValuesFrom, I think Wikidata would need user interface enhancements to make those features understandable to non-specialists. Emw (talk) 07:41, 23 December 2014 (UTC)

Agree. Manchester Notation was discussed several times (eg Wikidata:Project chat/Archive/2013/07#Turtle vs. Manchester_syntax and Wikidata:Requests for comment/Typing : class ⇄ instance relationship in Wikidata. It is indeed the most readable notation for expressing OWL axiom, while Turtle is the most readable for expressing RDF data, and the two are equal for RDFS axioms. The Quick Reference gives examples for all OWL constructs (though not all examples correlate to each other). Eg here are some examples of self-irreflexivity and self-reflexivity I made up following that quick ref:

 Class: Person
   SubClassOf: not hates Self
 Class: Narcissist
   SubClassOf: Person
   SubClassOf: loves Self
 ObjectProperty: loves
   DisjointWith: hates

 Comment However, it's not just about readability of syntax and making nice editing widgets. Wikidatians should also understand the possible inferencing (Open World) vs constraint/validation (Closed World) vs documentation interpretation of the selected constructs, pick an interpretation that's appropriate to the purpose (Wikidata being "LOD in the wild"), document it, and design appropriate editorial policies. The RDF Shapes working group was recently formed precisely because OWL2 semantics cannot be used for validation. Eg see this poll, User:Kcoyle is aware of it.

• Nevertheless, OWL2 constructs can be used for validation, given appropriate interpretation (eg Pellet ICV)
•  Support Overall I support using standard vocabs to document properties and classes in Wikipedia, if we are not tempted to blindly stick to OWL semantics without considering the consequences
• BTW, the OWL vocabulary for classes is quite richer than the vocabulary for properties. We should use that too

Cheers! --Vladimir Alexiev (talk) 08:52, 23 December 2014 (UTC)

•  Not done, Use instance of (P31) instead.--GZWDer (talk) 10:15, 30 December 2014 (UTC)

family

   Done: part of the series (P179) (Talk and documentation)

Description	family of OS, e.g. Windows NT (Q486487) for Windows 7 (Q11215)
Represents	Windows 7 (Q11215)
Data type	Item
Template parameter	en:Template:Infobox OS family
Domain	Windows 7 (Q11215), Linux (Q388), OS X Mountain Lion (Q63734), Mac OS 9 (Q904519), Windows 98 (Q483132), Windows Server 2012 (Q11222)
Allowed values	Windows NT (Q486487), Unix-like operating system (Q14656), macOS (Q14116), Macintosh operating systems (Q43627), Windows 9x (Q609733), Windows Server (Q11219)
Example	Windows NT (Q486487) → Windows 7 (Q11215)
Format and edit filter validation	(образец: проверка на правильность 7-разрядного числа может быть осуществлена фильтром правок Special:AbuseFilter/17)
Source	ru:Ш:Карточка ОС
Proposed by	— Dimon4ezzz (обс.)

Discussion

Мотивация — Dimon4ezzz ^(обс.) 19:31, 8 January 2015 (UTC)

WikiProject Informatics has more than 50 participants and couldn't be pinged. Please post on the WikiProject's talk page instead.

I guess that your proposal should be rewritten. With the rule of en:Template:Infobox OS, it would be:

   Not done

Description	OS family
Data type	Item
Template parameter	family in en:Template:Infobox OS, Stammbaum in de:Template:Infobox Betriebssystem, семейство in ru:Template:Карточка ОС
Domain	operating system (Q9135)
Allowed values	Unix-like operating system (Q14656), Classic Mac OS (Q1882478), Microsoft Windows (Q1406)
Example	Windows NT (Q486487) => Microsoft Windows (Q1406), Windows 7 (Q11215) => Microsoft Windows (Q1406), Linux (Q388) => Unix-like operating system (Q14656), OS X Mountain Lion (Q63734) => Unix-like operating system (Q14656), Mac OS 9 (Q904519) => Classic Mac OS (Q1882478)

Visite fortuitement prolongée (talk) 21:11, 9 January 2015 (UTC)

Classic Mac OS (Q1882478) isn't family of OSs. It's just OS, I think. — Dimon4ezzz ^(обс.) 12:49, 11 January 2015 (UTC)

brand

   Done: brand (P1716) (Talk and documentation)

Description	brand of a product
Represents	brand (Q431289)
Data type	Item
Domain	product (Q2424752)
Allowed values	instances of brand (Q431289)
Example	Levi's 501 (Q3237209) => Levi's (Q13085298), Mercedes-Benz W205 (Q15312688) => Mercedes-Benz (Q36008)
Proposed by	Pasleim (talk)

Discussion

Currently, manufacturer (P176) is often used to indicate the brand of a product but manufacturer and brand is not the same and we should distinguish them on Wikidata. Pasleim (talk) 10:01, 10 January 2015 (UTC)

 Support. Conny (talk) 15:07, 20 January 2015 (UTC).

Entry in force date

   Not done

Description	Date a statute or another document enters in force
Data type	Point in time
Example	Belgian Anti-Racism Law (Q2465867) : 1981-08-18
Proposed by	Dereckson (talk)

Discussion

To be able to describe the life of a law. Dereckson (talk) 00:04, 12 December 2013 (UTC)

 Comment Couldn't we use 'significant event (P793)' for this? Filceolaire (talk) 16:37, 26 December 2013 (UTC)

 Not done - use significant event (P793). Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 16:18, 6 March 2015 (UTC)

Enactement date

   Not done

Description	Official date of a statute or another document, in most country the date the chief of state sigs the text
Data type	Point in time
Example	Belgian Anti-Racism Law (Q2465867) : 1981-07-30
Proposed by	Dereckson (talk)

Discussion

To be able to describe the life of a law. Dereckson (talk) 00:04, 12 December 2013 (UTC)

 Comment Couldn't we use 'significant event (P793)' for this? Filceolaire (talk) 16:38, 26 December 2013 (UTC)

 Not done - use significant event (P793). Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 16:18, 6 March 2015 (UTC)

Terms in office

   Not done

Description	how long someone has been in office; how many times someone has been elected to office
Data type	Number (not available yet)
Domain	all positive rational integers
Example	Congressman, President
Source	external reference, Wikipedia list article (either infobox or source)
Proposed by	TeleComNasSprVen (talk)

Discussion

Motivation. TeleComNasSprVen (talk) 13:08, 27 December 2013 (UTC)

 Oppose. better to use start date/end date Filceolaire (talk) 05:51, 25 February 2014 (UTC)

@Filceolaire: Are there existing or pending property proposals for start/end dates for these yet? We can just change the datatype for this property to suit your preferences if you would like. The property itself is what's important, not the datatype that it has. TeleComNasSprVen (talk) 17:54, 27 February 2014 (UTC)

The Domain is the type of item that uses this property. From your description this is items about politicians. For these items we have position held (P39) for each office the politician is elected to. If they are elected 4 times to the same position then position held (P39) has 4 values, each with qualifiers of (P642) to indicate the city/state and start time (P580), end time (P582) for the dates. I don't think this property would add anything.

Well, if that person holds that position (continuously) for several consecutive terms, there might be only one value with start and end date spanning the whole period (i.e. POTUS for 8 years). The proposed property could serve as an additional qualifier explaining that these 8 years span 2 terms. -- Gymel (talk) 21:03, 24 February 2015 (UTC)

 Not done - use start/end dates for these (use multiple sets with consecutive dates for Gymel's scenario). Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 16:17, 6 March 2015 (UTC)

Length of office

   Not done

Description	how long someone is in office for a single term
Data type	Point in time
Example	Congressman, President (10 days, 4 years)
Source	external reference, Wikipedia list article (either infobox or source)
Proposed by	TeleComNasSprVen (talk)

Discussion

Motivation. TeleComNasSprVen (talk) 13:13, 27 December 2013 (UTC)

 Oppose better to use start date/end date. Filceolaire (talk) 05:52, 25 February 2014 (UTC)

 Comment we don't have a data type to save a value like "4 years" --Pasleim (talk) 19:38, 21 January 2015 (UTC)

 Not done Use start date/end date. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 16:14, 6 March 2015 (UTC)

Closing date

   Not done

Description	The date of the official public closing
Data type	Point in time
Domain	Museums, other public buildings, Roller coasters, attractions
Allowed values	dates
Example	Gamla bergbanan (Q10502454) => 20 September 1987)
Source	Template:Infobox attraction (Q13478527)
Proposed by	abbedabbtalk

Discussion

Useful in infoboxes. I use it roller coaster templates abbedabb^talk 20:13, 25 February 2014 (UTC)

@Abbedabb: Finns det något som gör att dissolved, abolished or demolished date (P576) är olämplig?-- Lavallen (talk) 17:49, 15 March 2014 (UTC)

 Oppose duplicate of dissolved, abolished or demolished date (P576) --Pasleim (talk) 19:40, 21 January 2015 (UTC)

 Oppose - dissolved, abolished or demolished date (P576) fits the bill. Josh Baumgartner (talk) 16:52, 27 February 2015 (UTC)

 Not done - use dissolved, abolished or demolished date (P576). Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 16:40, 6 March 2015 (UTC)

organist

   Not done

Description	person employed to play a church's (or other building's, or occasionally event's) organ
Data type	Item
Template parameter	"organist" in en:template:infobox church
Domain	geographic location (Q2221906) (place), organization (Q43229) (organization), event (Q1656682) (event)
Allowed values	people
Example	St James' Church (Q16908818) => Theodore Stephen Tearne (Q7782056)
Source	Wikipedia infoboxes
Robot and gadget jobs	A bot could import these, with date qualifiers where available.
Proposed by	Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits

Discussion

Events could include coronations and notable funerals. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 11:30, 13 June 2014 (UTC)

•  Support--Kippelboy (talk) 09:14, 15 June 2014 (UTC)
•  Oppose: There is also cantor (Q330679). While en:Cantor (church) only mentions his responsibility for vocal music, de:Kantor emphasises that playing the organ is one of his usual duties as well as "Kantor" being the designation for the person in charge of all musical activities in the church. Anyway it would be a bit funny to denote the Thomaskantor (Q641457) Johann Sebastian Bach (Q1339) with this property as the employed organist (Q765778) of St. Thomas Church (Q170402). I think supplying the inverse property, i.e. noting employer (P108) at the person with the specific kind or denomination of tasks as a qualifier would be more exact. Questions like "who played the organ there" perhaps should be more appropriately answered by a (not yet existing) property for the indiviual organ items. -- Gymel (talk) 10:23, 15 June 2014 (UTC)
  • Cantor would not be appropriate for organists at secular venues. In the UK, churches may have a musical director "in charge of all musical activities", senior (or at least different) to the organist. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 08:40, 5 July 2014 (UTC)
    • I have to admit that I have no clue what your proposal is aiming at: Is the emphasis on "person employed to play the organ" (which then we deem more important than the musician in charge of everything)? Or is it rather "who played the organ?" (which I consider an appropriate property for the organ, not the church). The :en:infobox you mention has provisions for "organist/director of music", "organist", "organ scholar" and "director of music" (but not "cantor" - bias at work?) and seems to list all lay personell at the given church at the price of selectivity: Not a good supposition for transfering the parameters to wikidata, I think. Singling out the parameter "organist" necessitates a more stringent definition than implicit from the infobox context, therefore my question. -- Gymel (talk) 23:37, 14 July 2014 (UTC)
• No consensus. Closing as  unsuccessful. --George (Talk · Contribs · CentralAuth · Log) 11:20, 17 February 2015 (UTC)

breed

   Not done

Description	breed of animal
Data type	Item
Template parameter	"breed" in en:template:infobox animal
Domain	individual animals
Allowed values	animal breeds
Example	Bo (Q1273495) => Portuguese water dog (Q38559)
Source	Wikipedia
Proposed by	AmaryllisGardener talk

Discussion

Used in infoboxes. Useful info. AmaryllisGardener ^talk 22:38, 30 August 2014 (UTC)

Template:AmaryllisGardener For human individuals we say instance of (P31) = human. Maybe this would be a case for p31 = Portuguese water dog (Q38559)? -Tobias1984 (talk) 19:07, 19 October 2014 (UTC)

Didn't think of that. Sounds good. --AmaryllisGardener ^talk 20:29, 19 October 2014 (UTC)

 Oppose. I think it makes more sense to say Bo (Q1273495):instance of (P31):Portuguese water dog (Q38559) and Portuguese water dog (Q38559):instance of (P31)breed (Q38829). Filceolaire (talk) 13:47, 2 November 2014 (UTC)

 Not done - use instance of (P31). Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 16:29, 6 March 2015 (UTC)

Pokémon

Pokémon browser number

   Done: Pokémon index (P1685) (Talk and documentation)

Description	a Pokémon identification number
Data type	String
Domain	Any Pokémon
Allowed values	"Numbers" (R-xxx, N-xxx, S-xxx and X-xxx for now, maybe more format later)
Example	<Bulbasaur> Pokémon browser number <R-001> (qualifier Fiore Pokémon browser), <R-014> (qualifier Oblivia Pokémon browser), <N-004> (qualifier Oblivia past Pokémon browser)
Source	in-game informations from the Pokémon Ranger games
Proposed by	Ju gatsu mikka

Discussion

With property P1112 (P1112), only number can be used: "national" and "regional" pokédex from the main games series and maybe some others like Pokémon gallery from Pokémon Conquest can have a statement. I would like to make Pokémon items as complete as possible with as many data as needed to. Ju gatsu mikka (talk) 08:57, 25 September 2014 (UTC)

 Support Seems useful. --AmaryllisGardener ^talk 16:02, 29 September 2014 (UTC)

•  Support --- Jura 15:09, 19 November 2014 (UTC)

Pokémon egg group

   Not done

Description	Pokémon breeding in-game mechanism
Data type	Item
Domain	Any Pokémon
Allowed values	Monster group, water 1 group, water 2 group, water 3 group, bug group, flying group, field group, fairy group, grass group, human-like group, mineral group, amorphous group, dragon group, ditto group, undiscovered group. Each entries will be create if the property is approved.
Example	<Bulbasaur> Pokémon egg group <monster group>, <grass group>
Source	in-game informations from the Pokémon games
Proposed by	Ju gatsu mikka

Discussion

I would like to make Pokémon items as complete as possible with as many data as needed to. Ju gatsu mikka (talk) 08:57, 25 September 2014 (UTC)

 Strong support ALL 3 ABOVE, HAHA!!! --Liuxinyu970226 (talk) 15:03, 29 September 2014 (UTC)

 Oppose I think part of (P361) is sufficient for this. -Tobias1984 (talk) 15:30, 29 September 2014 (UTC)

 Oppose per Tobias. --AmaryllisGardener ^talk 16:02, 29 September 2014 (UTC)

• Closing as  unsuccessful --George (Talk · Contribs · CentralAuth · Log) 11:20, 17 February 2015 (UTC)

deaths

   Not done

Description	people which died because of this in a certain timescale
Data type	Number (not available yet)
Domain	(Taxons)
Example	alcoholism (Q15326), cancer (Q12078), Ebola hemorrhagic fever (Q51993)
Proposed by	Impériale (talk)

Discussion

This property could help to create graphics and infoboxes. There is a similar property (Property:P1590) but it only shows one point in time. Maybe it's a also a solution to change this property (In my opinion it should behave like Property:P1082). Impériale (talk) 23:12, 7 January 2015 (UTC)

 Oppose - number of deaths (P1120) should work for this. You can have multiple values listed, each with their own time-related qualifiers. Josh Baumgartner (talk) 17:01, 27 February 2015 (UTC)

 Not done - use number of deaths (P1120). Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 16:39, 6 March 2015 (UTC)

SAAM person/institution

   Done: Smithsonian American Art Museum person/institution ID (P1795) (Talk and documentation)

Description	Smithsonian American Art Museum: person/institution thesaurus id
Represents	Smithsonian American Art Museum person/institution ID (Q19186351)
Data type	String
Template parameter	none.
Domain	persons, institutions
Allowed values	digits
Example	Allan D'Arcangelo (Q4730556) -> 1121 (web, RDF)
Source	http://americanart.si.edu/collections/search/lod/about/browse_artists.cfm
Formatter URL	http://edan.si.edu/saam/id/person-institution/$1
Robot and gadget jobs	Wikipedia/dbpedia coreference: https://github.com/usc-isi-i2/saam-lod/tree/master/n3/n3-seeAlso. Download: maybe https://github.com/usc-isi-i2/saam-lod/blob/master/datasets/complete-data-from-database/cbev2.WebArtistBio.csv but gotta check with authors
Proposed by	Vladimir Alexiev (talk)

Discussion

Used in the SAAM LOD (40k works of art), eg http://edan.si.edu/saam/id/object/1966.29.18 Vladimir Alexiev (talk) 10:44, 12 February 2015 (UTC)

•  Support Already added ~8K entries to mix'n'match. --Magnus Manske (talk) 19:15, 19 March 2015 (UTC)

@Vladimir Alexiev, Magnus Manske:  Done Smithsonian American Art Museum person/institution ID (P1795) Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 15:40, 22 March 2015 (UTC)

Parlement & Politiek ID

   Done: Parlement.com ID (P1749) (Talk and documentation)

Description	entry of described object on Parlement & Politiek, website describing Dutch politic
Represents	Parlement.com (Q14042250)
Data type	String
Domain	person, organisations, terms
Allowed values	12 symbols
Example	Mark Rutte (Q57792): vg9fgoprkxw3 People's Party for Freedom and Democracy (Q239333): vh8lnhrouwxy Second Rutte cabinet (Q1638648): vj47glycfix9
Source	http://www.parlement.com/
Formatter URL	http://www.parlement.com/id/$1
Proposed by	Sjoerd de Bruin (talk)

Discussion

 Support - Husky (talk) 10:57, 1 March 2015 (UTC)

 Support Filceolaire (talk) 16:53, 2 March 2015 (UTC)

@Sjoerddebruin, Husky, Filceolaire:  Created as Parlement.com ID (P1749). Jon Harald Søby (talk) 00:22, 10 March 2015 (UTC)

Cool, thanks! Husky (talk) 08:32, 10 March 2015 (UTC)

bureau du patrimoine de Seine-Saint-Denis ID

   Done: bureau du patrimoine de Seine-Saint-Denis ID (P1794) (Talk and documentation)

Description	atlas-patrimoine93 ID
Data type	String
Domain	architectural structures, places
Example	Basilica of Saint-Denis (Q184407) -> 066s021
Formatter URL	http://www.atlas-patrimoine93.fr/pg-html/bases_doc/inventaire/fiche.php?idfic=$1

Discussion

Code enabling links to the atlas-patrimoine93.fr website. Entries about buildings are usually linked to the national Mérimée database, making for easy link harvesting. The area served is relatively small, but the descriptions provided in the Atlas are often detailed (much more so than Mérimée's). --Zolo (talk) 15:46, 27 February 2015 (UTC)

@Zolo:  Done bureau du patrimoine de Seine-Saint-Denis ID (P1794) Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 15:34, 22 March 2015 (UTC)

Aviation Safety Network accident description ID

   Done: Aviation Safety Network accident ID (P1755) (Talk and documentation)

Description	Accident description ID per the Aviation Safety Network's database
Represents	Aviation Safety Network accident description (Q19356096)
Data type	String
Domain	aviation accident (Q744913)
Example	TransAsia Airways Flight 235 (Q18951344) => Aviation Safety Network accident description ID => 20150204-0
Format and edit filter validation	8 digit number followed by '-' and a final digit can be validated with edit filter
Source	ASN Aviation Safety Database
Formatter URL	http://aviation-safety.net/database/record.php?id=$1
Robot and gadget jobs	possible
Proposed by	Josh Baumgartner (talk)

Discussion

ASN's databases are a comprehensive reference aviation accidents and other incidents. The accident descriptions generally cover the larger airline incidents. Josh Baumgartner (talk) 16:31, 27 February 2015 (UTC)

@Joshbaumgartner:  Done Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 22:32, 13 March 2015 (UTC)

Aviation Safety Network Wikibase Occurrence

   Done: Aviation Safety Network Wikibase Occurrence (P1760) (Talk and documentation)

Description	Wikibase occurrence number per the Aviation Safety Network's database
Represents	Aviation Safety Network Wikibase Occurrence (Q19359000)
Data type	String
Domain	aviation accident (Q744913)
Example	Yverdon-les-Bains Air Club crash (Q19360289) => Aviation Safety Network Wikibase Occurrence => 174061
Format and edit filter validation	6 digit number can be validated with edit filter
Source	ASN Aviation Safety WikiBase
Formatter URL	http://aviation-safety.net/wikibase/wiki.php?id=$1
Robot and gadget jobs	possible
Proposed by	Josh Baumgartner (talk)

Discussion

ASN's databases are a comprehensive reference aviation accidents and other incidents. The WikiBase Occurrences generally cover the notable non-airline accidents. Josh Baumgartner (talk) 16:42, 27 February 2015 (UTC)

@Joshbaumgartner: Please give resolvable URLs as examples --Vladimir Alexiev (talk) 12:43, 4 March 2015 (UTC)

@Joshbaumgartner:@Vladimir Alexiev: Aviation Safety Network Wikibase Occurrence (P1760) Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 22:44, 13 March 2015 (UTC)

GTAA - Common Thesaurus Audiovisual Archives

   Done: GTAA ID (P1741) (Talk and documentation)

Description	Thesaurus numbers, used for (mainly) Dutch audiovisual archives, specifically the Netherlands Institute for Sound and Vision and EYE Film Institute.
Data type	String
Domain	Subjects, Persons, Names, Locations, Genres and Makers
Allowed values	a number of unspecified length
Example	André van Duin (Q523644) => 95024
Format and edit filter validation	\d+
Source	Official site (Dutch), Overview (English)
Proposed by	Husky (talk)

Discussion

This comparable to something like Virtual International Authority File (Q54919) or BNCF Thesaurus ID (P508). It's a little broader than just persons, because places, locations and concepts can also be identified. When this is added, i could start linking Dutch television and radio makers to Wikidata using the GTAA, allowing a broad spectrum of data to be added to Wikidata on those subjects. Husky (talk) 11:23, 1 March 2015 (UTC)

•  Support 85jesse (talk) 09:09, 2 March 2015 (UTC)
•  Support @Husky: suggest to rename to "GTAA id", and move the long name to description. Suggest to move the details (NISV and EYE) to the description of Common Thesaurus of Audiovisual Archives (Q19366588) --Vladimir Alexiev (talk) 12:49, 4 March 2015 (UTC)
  • Thanks. To be completely correct, i think we should probably call it "GTAA concept identifier', because that's what it is officially called. Moving the details and long name is fine with me. Husky (talk) 13:00, 4 March 2015 (UTC)

• @Husky:, @85jesse:, @Vladimir Alexiev:  Done Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 19:58, 9 March 2015 (UTC)
  • Awesome, thanks! Husky (talk) 20:03, 9 March 2015 (UTC)

Hi @Husky: you made a mistake: Common Thesaurus of Audiovisual Archives (Q19366588) should stay as "GTAA": the item is the thesaurus; "GTAA concept identifier" is the property GTAA ID (P1741). Take a look eg at "ULAN" thesaurus (item) and "ULAN id" (property). --Vladimir Alexiev (talk) 14:38, 12 March 2015 (UTC)

• I'm getting a bit confused. Could you fix the items? :) Husky (talk) 08:58, 13 March 2015 (UTC)
  • @Husky: see now

denkXweb id

   Done: denkXweb object ID (P1769) (Talk and documentation)

Description	denkXweb is the online database for cultural heritage monuments in the german state of Hesse, see [1]. We use the ID that each cultural heritage monument has in this database as an identifier both on de-wiki and on Commons. There is no nationwide identifier.
Represents	denkXweb (Q19411765)
Data type	Number (not available yet)
Template parameter	"Nummer" in de:Vorlage:Denkmalliste Hessen Tabellenzeile, first field in commons:Template:Kulturdenkmal Hessen
Domain	cultural heritage monuments located in Hesse
Allowed values	integer up to 999999 (max. 6 digits, range might change)
Example	Limburg Cathedral (Q564957) => 53076
Formatter URL	http://denkxweb.denkmalpflege-hessen.de/cgi-bin/mapwalk.pl?event=Query.Details&obj=$1
Robot and gadget jobs	Bots can pull data from denkXweb, which is a reliable source, and it will be very useful for maintenance of lists, to communicate with the ministry department (cross-checking data, right now done manually), and last but not least for Wiki Loves Monuments
Proposed by	Cirdan (talk)

Discussion

Useful property to bring cultural heritage monuments to Wikidata and make the lists on de-wiki available in database format. As this is my first request of this kind, I'm also happy with another property name. Cirdan (talk) 17:37, 3 March 2015 (UTC)

 Support. @Cirdan: Please make an item "denkXweb" (see eg Union List of Artist Names (Q2494649) for applicable fields) and put the Q number in "subject item" above. Also, provide the resolvable URL of '53076' as example. --Vladimir Alexiev (talk) 12:53, 4 March 2015 (UTC)

Added.--Cirdan (talk) 15:07, 4 March 2015 (UTC)

 Support Could be added to https://tools.wmflabs.org/wlmuk/index_wd.html Regards, Christoph Braun (talk) 08:16, 20 March 2015 (UTC)

• @Cirdan: @Vladimir Alexiev: @Christoph Braun:  Done as denkXweb object ID (P1769). Datatype is "string", as is usual for such identifiers. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 10:33, 20 March 2015 (UTC)

LMI code

   Done: Romania LMI code (P1770) (Talk and documentation)

Description	identifier for Romanian heritage sites
Data type	String
Domain	only instances of historic monument (Q916620) ?
Example	Grand Hôtel du Boulevard (Q3113619) -> B-II-m-A-18678
Source	Commons:Template:Monument istoric, ro:Category:Liste de monumente istorice din România

Discussion

Zolo (talk) 06:46, 11 March 2015 (UTC)

• @Zolo: Is there a URL that refers to or represents B-II-m-A-18678 ? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 07:48, 11 March 2015 (UTC)

• @Pigsonthewing: apparently not, but ro.wikipedia has devised a system of internal links instead. To see this, click on the LMI code of Commons:Category:Banffy Castle in Bonţida. --Zolo (talk) 08:16, 11 March 2015 (UTC)

@Zolo:  Done Romania LMI code (P1770). Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 10:42, 20 March 2015 (UTC)

Renamed to "**Romania** LMI code". Both https://ro.wikipedia.org/wiki/Cod:LMI:CJ-II-a-A-07534 and https://en.wikipedia.org/wiki/ro:Cod:LMI:CJ-II-a-A-07534, but I agree the first one is better as it emphasizes the Romanian nature of the id. --Vladimir Alexiev (talk) 10:19, 24 March 2015 (UTC)

IPEDS ID

   Done: Integrated Postsecondary Education Data System ID (P1771) (Talk and documentation)

Description	Unique identification number assigned to United States postsecondary institutions surveyed through the US Department of Education's Integrated Postsecondary Education Data System (IPEDS). Also known as Unit ID.
Data type	Number (not available yet)
Domain	Colleges and universities in the United States. As of 2015-03-10, this is about 7500 institutions.
Allowed values	positive integers of length 6
Example	Valparaiso University (Q186047) => 152600
Source	IPEDS ID definition

Discussion

Proposed by: Runner1928 (talk)

Motivation: I have worked with US Department of Education data for several years. It is useful and high quality, though the trade-off is that it is often about a year old by the time it's published. IPEDS, the Integrated Postsecondary Education Data System, is a large dataset that, because it is created and published solely by the US federal government, is in the public domain. There are many, many properties for colleges in this data, but some that we might prioritize are:

• number of students: undergraduate, graduate, ...
• latitude/longitude location
• graduation rate
• faith affiliation
• official website

But in order to map US colleges in Wikidata to Department of Education data, we must have IPEDS ID values in Wikidata. Then a bot can do the data transfer work. Runner1928 (talk) 21:27, 10 March 2015 (UTC)

@Runner1928:  Done as Integrated Postsecondary Education Data System ID (P1771). DAta type is "string", as is usual for such identifiers. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 10:57, 20 March 2015 (UTC)

DVN identifier

   Done: DVN ID (P1788) (Talk and documentation)

Description	Identifier in the Dutch Digitaal Vrouwenlexicon van Nederland (Online Dictionary of Dutch Women), a biography portal of prominent women in Dutch history.
Represents	Online Dictionary of Dutch Women (Q13135279)
Data type	String
Domain	person
Allowed values	a string of text characters, often the person's (last) name
Example	Judith Leyster (Q232423) => Leyster (http://resources.huygens.knaw.nl/vrouwenlexicon/lemmata/data/Leyster)
Source	http://resources.huygens.knaw.nl/vrouwenlexicon
Formatter URL	http://resources.huygens.knaw.nl/vrouwenlexicon/lemmata/data/$1

Discussion

Motivation: Trustworthy source of women's biographies by a Dutch research institute, often used as a reference on Wikipedia. The database is planned to be extended with biographies of notable 20th-Century women in the upcoming years. Counterpart of Biografisch Portaal (Q1868372).

Proposed by: Spinster (talk) 17:53, 13 March 2015 (UTC)

 Support, useful for referencing statements. Sjoerd de Bruin (talk) 18:15, 13 March 2015 (UTC)

 Support, let's do this. Let's git it to 100% coverage here. Multichill (talk) 18:43, 13 March 2015 (UTC)

 Support. Husky (talk) 19:51, 13 March 2015 (UTC)

 Support, per Sjoerd de Bruin. --Jan.Kamenicek (talk) 00:18, 16 March 2015 (UTC)

 Support. --Magnus Manske (talk) 19:32, 17 March 2015 (UTC)

@Spinster, Sjoerddebruin, Multichill, Husky, Jan.Kamenicek, Magnus Manske:  Done DVN ID (P1788) Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 21:52, 21 March 2015 (UTC)

Awesome! Husky (talk) 21:54, 21 March 2015 (UTC)

Muséofile ID

   Not done

Description	identifier in the Muséofile database about 1315 French museums
Data type	String
Domain	museum (Q33506)
Allowed values	M\d{1,4}
Example	Louvre Museum (Q19675) => M5031
Source	http://www.culture.gouv.fr/documentation/museo/index.htm
Formatter URL	http://www.culture.gouv.fr/public/mistral/museo_fr?ACTION=CHERCHER&FIELD_98=REF&VALUE_98=$1
Proposed by	— Ayack (talk) at 17:34, 18 March 2015‎

Discussion

@Ayack: it already exists: Museofile ID (P539). --Zolo (talk) 13:54, 24 March 2015 (UTC)

non-free file URL

   Not done

Description	Like image (P18), but for non-free files.
Data type	URL
Domain	all
Allowed values	.jpg, png, ...
Example	24 Hours of a Woman's Life (Q4631883)=>http://www.movieposterdb.com/posters/06_05/1952/0044330/l_116399_0044330_b015da00.jpg (probably have better examples)
Proposed by	GZWDer (talk)

Discussion

• So... how to use those links? Is those URLs are allowed to be embedded? Do they have privacy policy? Does site that uses Wikidata need to inform users that some of queries are sent to unknown website? Will this website be happy for direct-linking of images? At least, do you understand, this property will be unusable on wikimedia project without complex bot-support system on local wikis? -- Vlsergey (talk) 14:33, 15 August 2014 (UTC)
•  Support I've been thinking about something like this for many months. --Jakob (talk) 00:14, 16 August 2014 (UTC)
•  Oppose: Non-free images cannot be used, so I see no the point in linking to them. Regards, Dipsacus fullonum (talk) 14:03, 21 August 2014 (UTC)
•  Support --Eurodyne (talk) 03:49, 24 September 2014 (UTC)
•  Oppose --Micru (talk) 08:55, 18 October 2014 (UTC)
•  Oppose--Oursana (talk) 18:23, 18 October 2014 (UTC)

 Comment it is not possible to use this files on wikidata, however you can link to any page on the internet, no matter what kind of copyright or user conditions apply.

@‎Giftzwerg 88: Not exactly, it is a complex issue with many nuances and with different laws depending on the country. See: w:Copyright aspects of hyperlinking and framing.--Micru (talk) 17:34, 20 October 2014 (UTC)

Laws are a different issue and usefullness or appropriateness of the links another.--Giftzwerg 88 (talk) 07:24, 21 October 2014 (UTC)

 Support. The claim that "non-free images cannot be used" is false, in many situations, both on Wikipedias and elsewhere. For example: https://en.wikipedia.org/wiki/File:PicassoGuernica.jpg Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 13:07, 20 December 2014 (UTC)

• Oppose creation — This doesn't seem to have a particularly good use case for our external stakeholders and not a particularly good use case that Google doesn't already handle for our internal stakeholders. --Izno (talk) 17:32, 9 March 2015 (UTC)

 Not done No consensus. Jon Harald Søby (talk) 23:58, 9 March 2015 (UTC)

orderable

   Not done

Description	For use in a statement on a property, whose values are an ordering key
Represents	collation (Q10513350)
Data type	Boolean-invalid datatype (not in Module:i18n/datatype)
Domain	Properties
Allowed values	true, false
Example	point in time (P585) → true
Robot and gadget jobs	Automatic ordering of orderable claims and claims with orderable qualifiers upon insertion
Proposed by	Petr Matas

Discussion

See WD:PC#UI - order of events in significant events. Petr Matas 11:31, 22 December 2014 (UTC)

•  Comment: Would "point in time (P585) is of type orderable Wikidata property (Q18668171)" be a better alternative? Petr Matas 17:04, 22 December 2014 (UTC)
•  Comment: I don't understand what the use of this property is.--Giftzwerg 88 (talk) 12:07, 21 January 2015 (UTC)
•  Oppose use instance of (P31)=orderable Wikidata property (Q18668171) --Pasleim (talk) 16:32, 2 March 2015 (UTC)

 Not done No consensus. Jon Harald Søby (talk) 00:02, 10 March 2015 (UTC)

ordering key

   Not done

Description	Indicates, which qualifier should be used as a preferred ordering key for multiple statements with this property
Represents	collation (Q10513350)
Data type	Property
Domain	All properties
Allowed values	All properties
Example	significant event (P793) → point in time (P585)
Robot and gadget jobs	Automatic ordering of claims with orderable qualifiers upon insertion
Proposed by	Petr Matas

Discussion

See WD:PC#UI - order of events in significant events. Petr Matas 09:33, 23 December 2014 (UTC)

I don't really get what it is supposed to do. If we just want to sort them by chronological order, that seems to be the same for all properties: that is point in time (P585) / start time (P580) with fallback to end time (P582)). --Zolo (talk) 09:00, 21 January 2015 (UTC)

 Oppose per Zolo. Filceolaire (talk) 22:51, 18 February 2015 (UTC)

 Oppose All claims with qualifier point in time (P585) should be ordered chronologically. --Pasleim (talk) 16:38, 2 March 2015 (UTC)

 Not done Jon Harald Søby (talk) 00:03, 10 March 2015 (UTC)

candidate of

   Not done

Description	Reverse of candidate (P726).
Data type	Item
Domain	person, party
Allowed values	election
Example	Rajmohan Gandhi (Q734521)=>2014 Indian general election (Q3587169)
Robot and gadget jobs	Yes
Proposed by	GZWDer (talk)

Discussion

As candidate (P726) is currently abused we must spilt the usage to another property. So I will create it in 10 days if there are no oppose. GZWDer (talk) 09:46, 8 January 2015 (UTC)

•  Oppose. candidate (P726) should have its usage cleaned up, preferably by bot. There is no need to duplicate candidate data. --Yair rand (talk) 17:00, 22 February 2015 (UTC)
•  Oppose.Per Yair rand. Casper Tinan (talk) 20:40, 2 March 2015 (UTC)

 Not done Jon Harald Søby (talk) 00:03, 10 March 2015 (UTC)

format (regex)

   Done: format as a regular expression (P1793) (Talk and documentation)

Description	Format for this specific property or item, defined by a regex
Data type	String
Template parameter	Template:Constraint:Format, even Template:Property documentation
Domain	properties, possibly other items
Allowed values	regular expressions
Example	Property:P1293: "\d{1,4}" Market Identifier Code (Q6770697) = "\p{4}"

Discussion

Could be used to hold regex currently defined in one of the above templates.

Similar to "pattern" included in the list by @Ivan A. Krestinin: at Property proposal/Property metadata#Originally proposed_3. --- Jura 12:56, 30 January 2015 (UTC)

 Support but I believe this property should be proposed in this section: Wikidata:Property proposal/Property metadata. Tpt (talk) 09:09, 31 January 2015 (UTC)

Single property has a little sense. We need to discuss all required properties in complex. Please move your efforts to complex discussion. — Ivan A. Krestinin (talk) 10:01, 31 January 2015 (UTC)

 Comment I think this property can be helpful on items as well properties themselves. This is why I proposed it here. As it has merits of its own, I'd rather not drown it in a complex discussion in an even more complex proposal page. --- Jura 10:28, 31 January 2015 (UTC)

{@Jura1: give an example how can be used for item --Vladimir Alexiev (talk) 15:27, 23 February 2015 (UTC)

Sure, I added one above. --- Jura 18:26, 23 February 2015 (UTC)

 Support --Pasleim (talk) 16:26, 2 March 2015 (UTC)

@Tpt, Ivan A. Krestinin, Jura1, Pasleim:  Done format as a regular expression (P1793). Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 15:14, 22 March 2015 (UTC)

property used by this WikiProject

   Not done

Description	list properties used by a given WikiProject
Data type	Property
Domain	WikiProjects
Allowed values	any property
Example	WikiProject France (Q10816832): INSEE municipality code (P374), etc.
Source	lists on WikiProjects

• To illustrate usage of properties. --- Jura 11:48, 16 February 2015 (UTC)
• I would prefer a "property used by this template" if such does not yet exist. This would allow us to move the notices on the talk pages to properties. Would need to be qualified by the wiki. Frankly, who cares what the WikiProjects are doing with a property if most of the uses of a property are probably going to be in templates? --Izno (talk) 17:17, 9 March 2015 (UTC)
  • And I see above that my idea was proposed. Given that fact, I see no reason for this property and so oppose its creation. --Izno (talk) 17:22, 9 March 2015 (UTC)
    • It seems to me that your argument isnogood: a template is not a WikiProject. And yes, we care about WikiProjects. --- Jura 18:38, 9 March 2015 (UTC)

      • Explain to me what value this property adds. --Izno (talk) 23:15, 10 March 2015 (UTC)

      • @Jura1: Do you wish to respond? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 15:08, 22 March 2015 (UTC)
        • Not really. If he is not interested in WikiProjects .. I don't see the point. Everybody else probably knows that these are subject area collaborations, key to the development of Wikimedia. --- Jura 06:08, 23 March 2015 (UTC)

 Not done Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 08:07, 23 March 2015 (UTC)

scale

   Done: scale (P1752) (Talk and documentation)

Description	Proportional ratio of a linear dimension of a model to the same feature of the original
Represents	scale (Q10858537)
Data type	number?-invalid datatype (not in Module:i18n/datatype)
Template parameter	"ratio" in w:en:Infobox model rail scale, possibly others
Domain	model railway scales, scale models, statues/sculptures, toys, prototypes, relplicas, anything else produced to a scale ratio. Map scales could either be included or as a separate property, I don't know which is preferable.
Allowed values	1:n (for smaller than lifesize), 1:1 (for lifesize), n:1 (for larger than lifesize). n is a decimal number
Example	Scalextric (Q1683328) 1:32, HO scale (Q911411) 1:87.1
Format and edit filter validation	?
Source	external reference, Wikipedia list article (either infobox or source)
Robot and gadget jobs	Not aware of any, but bots could collect data from infoboxes
Proposed by	Thryduulf (talk: local

Discussion

This is a key property for model railway scales, but I actually came across it trying to improve Scalextric (Q1683328). Not sure whether this should just be for 3 dimensional objects or whether map scales should included. If map scales aren't included that should be a separate new property. Thryduulf (talk: local | en.wp | en.wikt) 12:55, 21 February 2015 (UTC)

•  Support in principle. This should either be a string ("1:32"), or a number n, where in the first example n=32. For larger-than-lifesize, the number n would be < 1. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 13:33, 21 February 2015 (UTC)
•  Support with number datatype for "1:n". --- Jura 14:53, 21 February 2015 (UTC)
•  Support of course. Same property for maps and other models, no dimentional number, no need to make thing more complex without a concrete usecase. TomT0m ^(talk) 10:39, 5 March 2015 (UTC)

@Thryduulf: @TomT0m:  Done scale (P1752) Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 22:15, 13 March 2015 (UTC)

List related to category

   Done: list related to category (P1753) (Talk and documentation)

Description	A list article corresponding to the membership of this category.
Represents	Wikimedia list article (Q13406463)
Data type	Item
Domain	Wikimedia category (Q4167836)
Allowed values	an instance of a subclass of Wikimedia list article (Q13406463)
Example	Category:Geographers (Q7233691) => list of geographers (Q3243996)
Format and edit filter validation	The category item and the list item should normally have the same inclusion criteria as specified by the property is a list of (P360), unless the difference is intentional and flagged by a qualifier
Source	Wikimedia categories
Robot and gadget jobs	Some auto-population may be possible using is a list of (P360) -> topic's main category (P910) -> (category), and then checking for inclusion of the list in the corresponding wiki category in any language. Also by identifying what lists actually are included in particular categories.
Proposed by	Jheald (talk)

Discussion

When harvesting information from categories it is important to be able to identify "auxiliary" items intentionally included in the category, that in general will not conform normal category inclusion criteria specified by is a list of (P360).

Such "auxiliary" items should also be white-listed, when identifying category-member items that appear to be in constraint violation of the category's is a list of (P360) criteria, that should either have necessary missing properties added, or their category membership reviewed.

The most common type of such "auxiliary" items in categories are survey articles on the topic of the category as a whole, identified by category's main topic (P301). The second most common type of "auxiliary" item is a list paralleling the membership of the category. That is what this proposed property would identify. Jheald (talk) 18:12, 27 February 2015 (UTC)

•  Support --- Jura 18:02, 5 March 2015 (UTC)

@Jheald: @Jura1:  Done list related to category (P1753) Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 22:21, 13 March 2015 (UTC)

Category related to list

   Done: category related to list (P1754) (Talk and documentation)

Description	A list article corresponding to the membership of this category.
Represents	Wikimedia category (Q4167836)
Data type	Item
Domain	Wikimedia list article (Q13406463)
Allowed values	an instance of a subclass of Wikimedia category (Q4167836)
Example	list of geographers (Q3243996) => Category:Geographers (Q7233691)
Format and edit filter validation	The list item and the category item should normally have the same inclusion criteria as specified by the property is a list of (P360), unless the difference is intentional and flagged by a qualifier
Source	Wikimedia lists
Robot and gadget jobs	Some auto-population may be possible using is a list of (P360) -> topic's main category (P910) and then checking for inclusion of the list in the corresponding wiki category in any language)
Proposed by	Jheald (talk)

Discussion

Inverse of the above.

Currently people are sometimes using topic's main category (P910) on list articles; but that property might be better reserved as a strict inverse of category's main topic (P301).

Jheald (talk) 18:20, 27 February 2015 (UTC)

•  Support --- Jura 18:02, 5 March 2015 (UTC)

@Jheald: @Jura1:  Done category related to list (P1754) Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 22:27, 13 March 2015 (UTC)

related concept

   Not done

Description	links two entities that represent related concepts
Data type	Item
Domain	items (concepts)
Allowed values	items (concepts)
Example	happiness (Q8) ↔ joy (Q935526) peering (Q772532) ↔ Q19400005 distance-vector routing protocol (Q1229441) ↔ distance vectors (Q19400159)
Proposed by	ProgVal (talk)

Discussion

This property could be useful for editors to not confuse concepts that are close to each other. For instance, one may see peering (Q772532) and think of it as a “political concept” instead of the actual meaning (the technical action of connecting networks). Having Q19400005 mentioned in the page would help distinguish these two concepts.

Moreover, this property could be used in infoboxes to show related (or “going further”) articles.

ProgVal (talk) 10:50, 3 March 2015 (UTC)

 Oppose too vague. Wikidata has more precise properties, related concept whould be deducable because they are linked by some properties. @ProgVal: Plus there is probably existing model like Simple Knowledge Organization System (Q2288360) who are suitable and standards for this kind of relationships. TomT0m ^(talk) 10:44, 5 March 2015 (UTC)

 Not done Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 15:06, 22 March 2015 (UTC)

Slogan

   Not done

Description	Motto or slogan of organisation
Data type	monolingual-invalid datatype (not in Module:i18n/datatype)
Template parameter	motto in en:Template:Infobox organization
Domain	geographic location (Q2221906) (place), organization (Q43229) (organization), event (Q1656682) (event)
Allowed values	type of linked items (Q template or text), list or range of allowed values, string pattern...
Example	Thurmont (Q755596) → "...Gateway to the Mountains"; McDonald’s (Q38076) → "i’m lovin’ it"; Eurovision Song Contest 2014 (Q5354210) → "#JoinUs"
Source	external reference, Wikipedia list article (either infobox or source)
Proposed by	Zellfaze (talk)

Discussion

There are a number of towns that have slogans or mottos; almost every business and organisation has a motto or slogan; most events also have one. It would be useful to be able to both keep track of those and to list how they have changed over time. Zellfaze (talk) 00:26, 10 June 2014 (UTC)

Mono or multilingual datatype. Snipre (talk) 11:34, 10 June 2014 (UTC)

Multilingual seems like it would be better suited. Sorry for only putting string. I'm still getting used to Wikidata. Zellfaze (talk) 13:02, 10 June 2014 (UTC)

Aren't most slogans in a particular language? --Yair rand (talk) 19:18, 10 June 2014 (UTC)

There are some slogans that are in multiple languages. To take McDonalds for example, they have different slogans in different regions and languages. "Amo muito tudo isso" is their slogan in Brazil. "Me encanta" in Spanish, "C’est tout ce que j’aime" in French, "Ich liebe es" in Deutsch, "Ninaipenda" in Swahili, "вот что я люблю" in Russian, and "işte bunu seviyorum" in Turkish to name a few. I think multilingual is appropriate. (Source) Zellfaze (talk) 20:02, 10 June 2014 (UTC)

I misunderstood what multilinugal meant. I've now read over a bit of mediawiki:Wikibase/DataModel and understand that monolingual is in fact what I wanted. My apologies. Zellfaze (talk) 11:59, 13 June 2014 (UTC)

There are two properties in the en:Template:Infobox organization, slogan and motto. So, would need to be one or the other. Also, this can get fairly complex. Apart from different languages, some organizations may have many slogans which are used for different purposes, for different products, and situations. Danrok (talk) 22:57, 25 June 2014 (UTC)

Zellfaze, Danrok, we already have a pending approval for motto, and I think it is good to have another property for "commercial slogan" (this one?). We can decide later on which qualifiers are needed for other uses. For now, I  Support.--Micru (talk) 08:24, 26 June 2014 (UTC)

 Support Very necessary. Eurovision Song Contest since 2002, uses slogans. I was looking for this!  – The preceding unsigned comment was added by Miloszk22 (talk • contribs).

 Weak oppose Now we have both motto (P1546) and motto text (P1451). Would it not be a duplicate? I don't see so much difference between "motto" and "slogan" (the purpose is different). Secondly I think that many "not informed" users could mix up the two properties and in short time they would become interchangeable. --Nastoshka (talk) 00:03, 17 February 2015 (UTC)

 Oppose With motto (P1546) and motto text (P1451), you can use qualifiers such as has use (P366) for those cases where multiple sayings are attributed or info boxes require more definition. Josh Baumgartner (talk) 18:22, 27 February 2015 (UTC)

 Oppose use motto (P1546) and motto text (P1451) Snipre (talk) 13:22, 13 March 2015 (UTC)

 Not done - we have exiting properties for this. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 12:19, 20 March 2015 (UTC)

military element

   Not done

Description	describes a military/paramilitary/police element like squad, platoon, unit, unit collection or any other administrative division
Data type	Item
Template parameter	nicht bekannt
Domain	barracks (Q131263), military base (Q245016), warship (Q3114762), air base (Q695850), real property (Q684740), Terrorist training camp (Q2405521)
Allowed values	Beispiele: 1. Panzerdivision, Bundeswehrzentralkrankenhaus Koblenz, Qassam-Brigaden, Eighth Air Force, Provincial Reconstruction Team
Example	Gereon barracks (Q15121187) => Federal Office of Personnel Management of the Bundeswehr (Q1005474), Gereon barracks (Q15121187) => Personalamt der Bundeswehr (Q575684)
Format and edit filter validation	nicht bekannt
Source	Externe Referenzen, Listenartikel in der Wikipedia (entweder Infobox oder Quelle)
Robot and gadget jobs	nicht bekannt
Proposed by	Jotpe (talk)

Discussion

Momentan kann man als Eigenschaft nur "Militärischer Verband" eintragen. Das ist zu speziell.

Dieser Vorschlag soll über alle regulären Armeen, Polizeien, Paramilitärs und sonstigen bewaffneten Organisationen die Möglichkeit schaffen, entsprechenden Einrichtungen wie Kasernen, Schiffe, Fluplätze oder gar Terrorcamps mit den militärischen Datenobjekten zu verbinden. Es sind bewusst keine, der Armee zugehörigen strukturellen Elemente, ausgeklammert, sodass auch unbewaffnete, nur mit Verwaltungsaufgaben betraute, Dienststellen mit dieser Eigenschaft getaggt werden können. --Jotpe (talk) 19:29, 28 July 2014 (UTC)

@Jotpe: Ich verstehe das Problem, aber ich denke dass eine allgemeine Eigenschaft besser ist. Siehe: Wikidata:Property_proposal/Generic#used_by. Reicht es?--Micru (talk) 11:08, 17 August 2014 (UTC)

 Comment I can't make any sense out of this proposal. Danrok (talk) 14:14, 10 January 2015 (UTC)

•  Oppose A property needs a clear definition - the one proposed is not. The domain is also too vague. Can you please write a narrative explaining what data/phenomenon you wish to capture? Apohllo (talk) 23:24, 15 January 2015 (UTC)

 Oppose die allgemeine Eigenschaft used by (P1535) ist besser --Pasleim (talk) 21:43, 21 January 2015 (UTC)

 Not done Jon Harald Søby (talk) 00:39, 10 March 2015 (UTC)

chief operating officer

   Done: chief operating officer (P1789) (Talk and documentation)

Description	The chief operating officer of an organization.
Represents	chief operating officer (Q623279)
Data type	Item
Domain	organization (Q43229)
Allowed values	People
Example	Facebook (Q355) => Sheryl Sandberg (Q234653), Duck Commander (Q15631659) => Jase Robertson (Q14755553), Heaven Sent Gaming (Q17275459) => Isabel Ruiz Lucero (Q17275427),
Source	Official website or reliable third party sources
Proposed by	DunDunDunt (talk)

Discussion

Much in the same vein as chief executive officer (P169), information related to chief operating officers provides a slightly more insight into a corporate structure. Some COO wield as much power as the CEO, as shown in Fortune magazine which listed the COO of Facebook Sheryl Sandberg as one of 2014's Top Ten Most Powerful Women in Business. DunDunDunt (talk) 15:51, 19 January 2015 (UTC)

 Support Sweet kate (talk) 18:17, 19 March 2015 (UTC)

@DunDunDunt, Sweet kate:  Done chief operating officer (P1789) Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 23:03, 21 March 2015 (UTC)

Total imports as a percent of GDP

   Not done

Description	Amount of goods and services bought from other countries in a year divided by theGDP of that country in that year
Data type	Number (not available yet)
Domain	Countries
Allowed values	Positive percentage numbers
Example	17%
Robot and gadget jobs	Global Economic Map Bot can do this
Proposed by	Mcnabber091 (talk) 19:06, 14 April 2014 (UTC)

 SupportMcnabber091 (talk) 10:14, 16 May 2014 (UTC)

 Oppose. Support total import in nominal value and GDP properties. Ratio can be computed by the user. --Zolo (talk) 19:48, 10 June 2014 (UTC)

 Not done No support. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 08:37, 23 March 2015 (UTC)

ISIC code

   Done: International Standard Industrial Classification code Rev.4 (P1796) (Talk and documentation)

Description	code of industry by ISIC (International Standard Industrial Classification of All Economic Activities)
Data type	String
Domain	industrial sector (Q8148) (industry)
Allowed values	Sectional level: [A-U], divisional level: two digits, class level: four digits
Example	aerospace manufacturer (Q3477363) => 3030
Source	http://unstats.un.org/unsd/cr/registry/isic-4.asp
Proposed by	Bezik (talk)

Discussion

ISIC is a standard classification of industries, governed by United Nations and used worldwide to classify economic entities and activities. In ruwiki we used ru:Template:ISIC based on this classification to automatically categorize companies by industry and country. Prospectively, Property:P452 could be restricted to values, that have such property. Probably, this property could be directly assigned to domain of organization (Q43229) (primarily for company (Q783794)) and used as standardized alternative of industry (P452). Bezik (talk) 15:58, 19 August 2014 (UTC)

@Bezik:  Done International Standard Industrial Classification code Rev.4 (P1796) Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 08:48, 23 March 2015 (UTC)

YourPaintings venue/collection identifier

   Done: Art UK collection ID (P1751) (Talk and documentation)

Description	A gallery or art collection, in the YourPaintings database
Data type	String
Domain	Art galleries, museums, organisations, collections, etc.
Example	Hereford Museum and Art Gallery (Q5738000) => hereford-museum-and-art-gallery-637 (see http://www.bbc.co.uk/arts/yourpaintings/galleries/collections/hereford-museum-and-art-gallery-637 )
Source	http://www.bbc.co.uk/arts/yourpaintings/galleries/
Robot and gadget jobs	formatterURL: http://www.bbc.co.uk/arts/yourpaintings/galleries/collections/$1
Proposed by	Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits

Discussion

Provides lists and images of oil paintings in the specified collection. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 20:27, 14 July 2014 (UTC)

-  Support. Move to section "Authority control". --Vladimir Alexiev (talk) 10:54, 7 January 2015 (UTC)

@Vladimir Alexiev:  Done Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 22:26, 9 March 2015 (UTC)

National Pipe Organ Register identifier

   Done: National Pipe Organ Register ID (P1763) (Talk and documentation)

Description	Identifier in National Pipe Organ Register (Q19294701), operated by British Institute of Organ Studies (Q4970119).
Data type	String
Template parameter	Used in en:Template:National Pipe Organ Register (recently created)
Domain	Churches, theatres, civic halls, etc.
Allowed values	Numbers prefixed by letters
Example	Church of St George (Q19239882) => N06500
Source	National Pipe Organ Register
Robot and gadget jobs	possible
Proposed by	Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits

Discussion

Website includes "details of 35,000 organs including 10,000 pictures", plus audio recordings. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 09:03, 13 February 2015 (UTC)

 Support - although we have only about 100 organ items at the moment and most of those are located East Frisia (Q165269)... -- Gymel (talk) 21:27, 24 February 2015 (UTC)

Thank you. This will be for places that have organs (churches, community buildings, concert halls), not necessarily organs themselves - though it could be used for those too. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 08:53, 4 March 2015 (UTC)

@Gymel:  Done National Pipe Organ Register ID (P1763) Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 23:18, 13 March 2015 (UTC)

Flemish organization for Immovable Heritage ID

   Done: Flemish Heritage Object ID (P1764) (Talk and documentation)

Description	identification code in the database of the Flemish organization for Immovable Heritage
Represents	Flanders Heritage Agency (Q3262326)
Data type	Number (not available yet)
Domain	cultural heritage (Q210272)
Allowed values	0-9999999
Example	Saint Peter's Abbey (Q1170767) => 21199 resolves to https://inventaris.onroerenderfgoed.be/dibe/relict/21199
Formatter URL	https://inventaris.onroerenderfgoed.be/dibe/relict/$1
Robot and gadget jobs	bots could check whether the object exists at https://inventaris.onroerenderfgoed.be/dibe/relict/$1
Proposed by	FranklyMyDear... (talk)

Discussion

It would be nice to have a way to link to the database of the Flemish organization for Immovable Heritage. Their database usually has a description and (brief) history of the object. FranklyMyDear... (talk) 16:58, 24 February 2015 (UTC)

@FranklyMyDear...:  Done Flemish Heritage Object ID (P1764), data type is 'string' as is usual for such things. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 23:22, 13 March 2015 (UTC)

Hornbostel-Sachs classification

   Done: Hornbostel-Sachs classification (P1762) (Talk and documentation)

Description	the Hornbostel-Sachs classification of this instrument
Represents	Hornbostel–Sachs (Q496327)
Data type	String
Template parameter	hornbostel_sachs in en:Template:Infobox_instrument (and in the equivalent templates on the as, id, ilo, lt, ml, ms, nn, no, pa, sco, simple, uk, uz and vi Wikipedias), "Hornbostel-Sachsi number" in et:Mall:Muusikainstrument, classe in pt:Predefinição:Info/Instrumento
Domain	musical instrument (Q34379)
Allowed values	string containing 0-9.-+
Example	aerophone (Q659216) => 4, reed aerophone (Q3152896) => 422, trumpet (Q8338) => 423.233, ocarina (Q187780) => 421.221.42, castanets (Q183932) => 111.141
Source	infoboxes, en:Category:Lists_of_musical_instruments_by_Hornbostel-Sachs_number
Robot and gadget jobs	bots could migrate values from infoboxes
Proposed by	Nikki (talk)

Discussion

@Nikki:  Done Hornbostel-Sachs classification (P1762) Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 23:13, 13 March 2015 (UTC)

Thanks! - Nikki (talk) 10:59, 14 March 2015 (UTC)

category of people buried here

   Done: category for people buried here (P1791) (Talk and documentation)

Description	Wikipedia category for people with a burial site within this area
Represents	location of burial (Q18857007)
Data type	Item
Template parameter	burial place (categorization)
Domain	geographical feature (Q618123)
Allowed values	Wikimedia category (Q4167836)
Example	Minsk (Q2280) → Category:Burials in Minsk (Q7976974)
Source	Wikipedia categorization

Discussion

by analogy with category for people born here (P1464) and category for people who died here (P1465)Чаховіч Уладзіслаў (talk) 12:14, 23 January 2015 (UTC)

•  Support - added English label/desc. Josh Baumgartner (talk) 20:25, 2 March 2015 (UTC)
•  Support. makes mappings easier --- Jura 21:07, 2 March 2015 (UTC)

@Чаховіч Уладзіслаў, Joshbaumgartner, Jura1:  Done category for people buried here (P1791). Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 14:34, 22 March 2015 (UTC)

Category of associated people

   Done: category of associated people (P1792) (Talk and documentation)

Description	Wikipedia category for people associated with this area
Data type	Item
Domain	geographical feature (Q618123)
Allowed values	Wikimedia category (Q4167836)
Example	Minsk (Q2280) → Category:People from Minsk (Q8808730)
Source	Wikipedia categorization

Discussion

by analogy with category for people born here (P1464) and category for people who died here (P1465)Чаховіч Уладзіслаў (talk) 12:14, 23 January 2015 (UTC)

 Support - Added English label/desc. Josh Baumgartner (talk) 20:25, 2 March 2015 (UTC)

•  Support --- Jura 21:07, 2 March 2015 (UTC)

@Чаховіч Уладзіслаў, Joshbaumgartner, Jura1:  Done category of associated people (P1792) Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 14:40, 22 March 2015 (UTC)

Point of interest

   Not done

Description	Spatial location related to another location (e.g. a city) that might be of interest (e.g. a tourist attraction)
Represents	point of interest (Q960648)
Data type	Item
Domain	place of interest, typically for its inherent or exhibited natural or cultural value
Allowed values	items located in the given item, for example museums, monuments, natural attractions like parks and beaches
Example	Amsterdam (Q727) => Rijksmuseum (Q190804), Vondelpark (Q1419691), Grachtengordel (Q478707)
Proposed by	Husky (talk)

Discussion

When Googling for certain places, in the 'knowledge graph' box a list of 'points of interest' appears (see example), this sounds like a very valuable addition to Wikidata as well. A case could be made that this could be a combination of several different properties (e.g. monuments, parks, squares, etc.), but given that the types of POI's might be endless, and is very difficult to create ranking and filter such a list, i think a single property would be better. I thought about calling this 'touristic attraction', but 'point of interest' sounds a little bit more neutral. I could imagine this would be very useful for Wikivoyage as well. Husky (talk) 23:50, 20 December 2014 (UTC)

If there were just three POIs for Amsterdam, this might work. Otherwise, shouldn't this work the other way round: determine what are POI for your interest => select the ones that are located in Amsterdam. --- Jura 13:13, 21 December 2014 (UTC)

• This seems to me to be inherently subjective. Each wikipedia could have a different opinion on which are the points of interest and each wikivoyage could have an opinion too. We have geolocation so we can find items that are near. We know stuff about each of those items so we can filter to just show museums or monuments or public transport infrastructure or whatever. I  Oppose for now but am open to something like this in the future - probably based on wikivoyage developments. Filceolaire (talk) 20:25, 19 March 2015 (UTC)
•  Oppose subjective selection of touristic attractions --Чаховіч Уладзіслаў (talk) 13:17, 22 March 2015 (UTC)

 Not done Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 15:01, 22 March 2015 (UTC)

Location map data

   Not done

Description	The Lua table containing the data about the location maps for the area
Data type	Item
Template parameter	(could replace some map-related parameters in some infoboxes)
Domain	places
Allowed values	instances of map data module (Q18711811)
Example	United States of America (Q30) -> Module:Location map/data/United States (Q16853427)
Proposed by	Zolo (talk)

Discussion

Note that it is sometimes a bit messy, because in Lua. For instance, because Lua redirects are not recognized as redirects by the software. Both en:Module:Location map/data/United States and en:Module:Location map/data/United States of America have an item though they are really the same module. This property could help make things a bit clearer, and should help with the maintenance of maps in Wikipedias.

I think the module should be limited to Lua data. In most Wikipedias, the same data are still stored in a Wikistyle template like Template:Location map USA2 (Q2885082). If we also need a property for this, I think it shold be a different one, as templates do not work the same way as modules, and are much harder to reuse. Zolo (talk) 13:16, 5 January 2015 (UTC)

•  Strong oppose. @Zolo:I think this should be stored in Wikidata so that we no longer need any local location map modules. We can use it in any wikis without copying it. See my propose below.--GZWDer (talk) 13:19, 6 January 2015 (UTC)

That sounds like a good idea, but it can only works once arbitrary access is ensabled. There are also some ticky points. For example en:Module:Location map/data/USA only includes mainland USA while fr:Module:Carte/données/états-unis also includes Alaska and Hawai. Beside, the French module also contains some language-related data that do not seem really fit for Wikidata. Anoher case is Québec that two modules using different map projection techniques (fr:Module:Carte/données/québec and fr:Module:Carte/données/québec (conique).

There issues are solvable of course,but they suggest that things will not be very totally straightforward, and will require some work from the Wikipedia side. @GZWDer:, I support the poperty you propose below, but given the bleak track-record of most Wikipedias in terms of Wikidata incorporation, I still think of "location map data" property could be useful, at least the very least as a transitory measure, and I do not see any major issue with having that. --Zolo (talk) 14:24, 6 January 2015 (UTC)

@Zolo: If we use "location map data" property we should copy the module to other wikis, otherwise this is phab:T41610. arbitrary access is coming (maybe in February).--GZWDer (talk) 04:46, 7 January 2015 (UTC)

Quite many languages have a module Module:Location map (Q15934920). Apparently, most of them are directly copied from enwiki, but rather few languages have the submodules that would be necessary to make it work. I guess it is up to individual Wikipedias to choose if they want to use data-modules or want to wait until they can somehow pull Lua functions directly from Wikidata items. --Zolo (talk) 17:09, 7 January 2015 (UTC)

 Oppose Lets do this once and do it right even if it takes a little longer. Store the data as statements on wikidata. The example you linked to does bother me as the coordinates quoted ignore Alaska, Hawaii and Puerto Rico. If these map parameters get added on wikidata it will be to an item labelled 'contiguous states of the USA' not to the USA item. Just saying. Filceolaire (talk) 19:56, 19 March 2015 (UTC)

 Not done Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 15:02, 22 March 2015 (UTC)

place name sign

   Done: place name sign (P1766) (Talk and documentation)

Description	image of road sign with place name on it
Represents	town sign (Q266488)
Data type	Commons media file
Domain	geographic locations
Allowed values	images
Example	Old Appleton (Q963346) = File:Old Appleton, Missouri, Road sign.jpg
Robot and gadget jobs	Could be added with http://tools.wmflabs.org/fist/wdfist/

Discussion

• P:P14 ("highway marker") seems too specific. --- Jura
•  Support. This is a classic example of a specific type of image that needs it's own wikidata property. Filceolaire (talk) 20:08, 19 March 2015 (UTC)

 Created as place name sign (P1766). @Jura1, Filceolaire: Jon Harald Søby (talk) 08:01, 20 March 2015 (UTC)

ISO 639-5

   Done: ISO 639-5 code (P1798) (Talk and documentation)

Description	ISO 639-5 code for a language family
Represents	ISO 639 Set 5 (Q2455758)
Data type	String
Template parameter	iso5 in w:en:Template:Infobox language family, iso5 in w:fr:Template:Infobox Langue
Domain	language family (Q25295)
Allowed values	3 lowercase letters
Example	Greek (Q9129) => grk, Algic languages (Q721612) => aql
Source	w:en:List of ISO 639-5 codes
Proposed by	Visite fortuitement prolongée (talk)

Discussion

See also ISO 639-1 code (P218), ISO 639-2 code (P219), ISO 639-3 code (P220), ISO 639-6 code (P221), Wikidata talk:WikiProject Languages#ISO 639-5. Visite fortuitement prolongée (talk) 22:31, 29 December 2014 (UTC)

1.  Support Pamputt (talk) 10:43, 30 December 2014 (UTC)
2.  Support Snipre (talk) 13:01, 9 January 2015 (UTC)

@Visite fortuitement prolongée, Pamputt, Snipre:  Done ISO 639-5 code (P1798) Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 09:09, 23 March 2015 (UTC)

Thanks Visite fortuitement prolongée (talk) 20:47, 23 March 2015 (UTC)

name day

   Done: name day (P1750) (Talk and documentation)

Description	day of the year associated with a first/given name. Useful for Wikidata:WikiProject Names. A qualifier can be used to identify the calendar that is being used. Distinguish from "feast day" (P:P841).
Represents	name day (Q216584)
Data type	Item
Template parameter	"name day" in en:Template:Infobox given name, "fête" in fr:Modèle:Infobox Prénom,
Domain	items for given names, first names
Allowed values	items for specific days of the year
Example	Lucy (Q17379191) = December 13 (Q2379)
Source	infobox

Ash Crow
Dereckson
Harmonia Amanda
Hsarrazin
Jura
Чаховіч Уладзіслаў
Joxemai
Place Clichy
Branthecan
Azertus
Jon Harald Søby
PKM
Pmt
Sight Contamination
MaksOttoVonStirlitz
BeatrixBelibaste
Moebeus
Dcflyer
Looniverse
Aya Reyad
Infovarius
Tris T7
Klaas 'Z4us' van B. V
Deborahjay
Bruno Biondi
ZI Jony
Laddo
Da Dapper Don
Data Gamer
Luca favorido
The Sir of Data Analytics
Skim
E4024
Joeykentin
Envlh
Susanna Giaccai
Epìdosis
Aluxosm
Dnshitobu
Ruky Wunpini
Balû
★Trekker

Notified participants of WikiProject Names

Discussion

Allows to import elements from the above infobox. --- Jura 13:02, 7 February 2015 (UTC)

•  Support per proposal --- Jura 13:02, 7 February 2015 (UTC)
•  Comment don't forget that this strongly depends on country (and thus, indirectly, language), culture and may be religion. It may be difficult to reflect all necessary conditions. --Infovarius (talk) 10:24, 25 February 2015 (UTC)
  • I agree. Qualifiers should probably be mandatory or highly recommended. --- Jura 11:17, 25 February 2015 (UTC)
•  Support if all necessary stuff around this is found (e.g. what qualifiers?). I even imagine country depending calendars created by Wikidata. Matěj Suchánek (talk) 17:20, 1 March 2015 (UTC)

@Jura1, Infovarius, Matěj Suchánek:  Created as name day (P1750) (see also the constraints I added). Jon Harald Søby (talk) 01:06, 10 March 2015 (UTC)

Political Donation

   Not done

Description	The amount donated to a political party
Data type	Number (not available yet)
Template parameter	n/a
Domain	Persons
Allowed values	integers
Example	sample items that would use that property, with proposed values; example: Simon Robertson (Q16105756) => 25000
Format and edit filter validation	(sample: 7 digit number can be validated with edit filter Special:AbuseFilter/17)
Source	e.g Electoral Commission http://www.electoralcommission.org.uk/
Robot and gadget jobs	Yes, can be a job.
Proposed by	Battleofalma (talk)

Discussion

Would be useful for building a record of political donations. Thanks Battleofalma (talk) 12:02, 11 October 2014 (UTC)

• Support - would need qualifiers of currency, political party, and date (or year). Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 12:54, 11 October 2014 (UTC)
•  Comment We need some more datatypes for this. This is datatype currency which is one of the most difficult as it is necessary to express the value in many different currencies. On the other hand I wonder if it is possible to use a more general property instead.--Giftzwerg 88 (talk) 08:02, 26 October 2014 (UTC)
• Suggest this be changed to record who the donation was made to. This can be created now and a qualifier giving the amount can follow when a suitable datatype is created. In the meantime the reference can link to a source with the amount. Filceolaire (talk) 22:44, 31 October 2014 (UTC)
•  Comment Why limit to political donations? Donations are also part of the system of NGO´s and in many other areas like school funding etc. I wonder if this property is usefull at all. I just imagine someone replacing the figures every five minutes during a fund raising party.--Giftzwerg 88 (talk) 11:57, 18 November 2014 (UTC)
•  Oppose This seems outside the scope of Wikidata. As Giftzwerg 88 points out above, there's really no reason this should be limited to political donations, and if we include all donations, it just becomes a giant mass of (probably unmaintainable) data. A person making a donation is a common and mundane activity, not something that stands out as an important event in their life. Kaldari (talk) 01:54, 23 December 2014 (UTC)
•  Oppose per Kaldari --Nastoshka (talk) 23:54, 16 February 2015 (UTC)

 Not done No consensus, out of scope. Jon Harald Søby (talk) 00:33, 10 March 2015 (UTC)

BioStor author identifier

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

Description	Author identifier, in the BioStor database and archive of journal articles
Data type	String
Template parameter	Tends to be in external links or references on Wikipedia
Domain	People, possibly groups, companies etc.
Allowed values	Stems of BioStor author URLs
Example	John Eleuthère du Pont (Q3655973) => 69822
Source	Wikipedia; BioStor
Formatter URL	http://biostor.org/author/$1
Robot and gadget jobs	Possible
Proposed by	Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits

Discussion

Useful disambiguator; and source of reliable sources for Wikipedia articles. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 12:00, 30 November 2014 (UTC)

Please give more information about this identifier.--Giftzwerg 88 (talk) 12:02, 4 December 2014 (UTC)

What information would you like? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 17:33, 9 December 2014 (UTC)

•  Support. Filceolaire (talk) 13:27, 13 March 2015 (UTC)

@Giftzwerg 88, Filceolaire:  Done P1790 (P1790). Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 10:08, 22 March 2015 (UTC)

related to

   Not done

Description	This property, as particular case of related property (P1659) might be useful in the case of a person, who is often quoted or related with another. At present we have only particular and precise property such as (contributor to the creative work or subject (P767) or employer (P108) oreducated at (P69)). What instead I think we need is a property that allows to connect two people (especially when one is mentioned often in relation to another). related property (P1659) is IMO too generic, since I can link not only person but also his company, group, other abstract-concept related to the subject etc...
Data type	Item
Domain	person (Q215627)
Allowed values	any element in the domain person (Q215627)
Example	example could be various; all items, for example, of writers which published, especially in Renaissance, with an unique editor. Here contributor to the creative work or subject (P767) doesn't fit very well. Or official biographer of a famous person, or also mentor/disciple: so Arnold Schoenberg (Q154770) --> related to Alban Berg (Q78475) as the first was the master/teacher of the second.
Source	A good source could be Wikipedia or the VIAF database. If you see, for instance, Nelson Mandela on VIAF, you have a section with related items (some of them are cities, organizations but there are few names could be imported in this new property)
Robot and gadget jobs	validation (only other item should be accepted)
Proposed by	Nastoshka (talk)

Discussion

•  Support--Daniele.Brundu (talk) 23:36, 7 March 2015 (UTC)
•  Oppose. Extremely vague, no clear potential uses, and thoroughly unsourcable. --Yair rand (talk) 23:31, 12 March 2015 (UTC)
•  Oppose. Too generic, and the examples are already covered by student (P802), student of (P1066), or influenced by (P737). Mushroom (talk) 00:20, 13 March 2015 (UTC)

 Not done Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 21:32, 20 March 2015 (UTC)

original airdate

   Not done

Description	date on which the item was first broadcast (whether on TV, the Internet, radio before being released, or otherwise presented in live form before being properly "published")
Data type	Point in time
Template parameter	"Airdate" in en:template:infobox television episode
Domain	episode (Q1983062), television film (Q506240), but certainly not restricted to those
Allowed values	as precise as possible, but allowed to vary by region of airing
Example	Smoked (Q7545917) => 2011-05-18
Source	en:template:infobox television episode
Proposed by	Mahir256 (talk)

Discussion

There's enough of a difference between publication date (P577) and this to warrant the latter's inclusion: a video (this may be an episode, a movie, or something on YouTube even) may have both an airdate, when it is first shown to the public, and a release date when one may acquire it in either a physical or digital form. Furthermore, many videos are often repackaged in compilations or anthologies, whose release dates may be contenders for the 'true' release date. This property would help in disambiguating between what is streamed live and what is released at once. Mahir256 (talk) 04:00, 5 March 2015 (UTC)

 Oppose Better enlarge the field of date of first performance (P1191) Snipre (talk) 13:26, 13 March 2015 (UTC)

Isn't publication date (P577) used for this? --- Jura 05:56, 23 March 2015 (UTC)

 Not done Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 08:12, 23 March 2015 (UTC)

Original title

   Not done

Description	Original title of a work
Data type	Monolingual text
Template parameter	"title_orig" in en:template:infobox book
Domain	filmmaking, television production, novel, video game, or music album
Allowed values	all
Example	Czterej pancerni i pies (Q990) => Czterej pancerni i pies (when English id Four tank-men and a dog)
Proposed by	Rezonansowy (talk)

Discussion

--Rezonansowy (talk) 23:08, 27 October 2014 (UTC)

Rezonansowy; Can you change the text "working title for this" where I added it above to whatever was the working title for 'Animal Farm. Also do the same for the proposal above for original title as the example is incomplete. Filceolaire (talk) 20:32, 3 November 2014 (UTC)

@Filceolaire: Fixed. --Rezonansowy (talk) 09:27, 4 November 2014 (UTC)

Rezonansowy Again I can see this could be a useful property so I will  Support if the datatype is changed to monoliingual text. I think, however, that the example here is a bad example. The proposed native language property would be better for Czterej pancerni i pies. I think Star Wars VI and Animal Farm are better examples of Original name since they were first released under different names. Filceolaire (talk) 15:13, 15 November 2014 (UTC)

Changed. --Rezonansowy (talk) 18:34, 18 November 2014 (UTC)

There is already P357 (P357). --Harmonia Amanda (talk) 16:26, 17 November 2014 (UTC)

@Harmonia Amanda: P357 (P357) is now obsolete in favor of title (P1476). Should the second have the same description – "original title"? Is title (P1476) the property for the original title of a given work? --Rezonansowy (talk) 10:33, 15 December 2014 (UTC)

 Oppose No need of this property: title (P1476) is sufficient for most of the works. And for works where the title changed, use title (P1476) with start and end date like for official name property. Snipre (talk) 12:05, 23 December 2014 (UTC)

What about video games? The consensus so far I've seen in most Wikipedias is: "Title of video game in that Wikipedia language (original lang.: Tytuł oryginalny)". This is presented also in infoboxes (e.g. pl:Amnesia: Mroczny obłęd) as a separate row in the header. I understand that it's not so easy to implement in terms of how Wikidata allows you to translate all property values. For most games it would be sufficient to use English as an original title. However, there's a great number of games coming from Japan, and then some... Not sure if this would be something that Wikidata could fix, or we should fix on each Wikipedia separately. Holek (talk) 13:25, 26 December 2014 (UTC)

 Oppose per Snipre --Pasleim (talk) 19:28, 21 January 2015 (UTC)

 Oppose per Snipre --Casper Tinan (talk) 21:38, 21 January 2015 (UTC)

 Oppose per Snipre. To solve the infobox problem, the client can refer to the original language of film or TV show (P364) and/or country of origin (P495) of the game to determine which language the original title uses. —Wylve (talk) 04:57, 8 March 2015 (UTC)

 Not done No consensus. Jon Harald Søby (talk) 00:48, 10 March 2015 (UTC)

CiNii book identifer

   Done: NACSIS-CAT bibliography ID (P1739) (Talk and documentation)

Description	Identifier for books, in the Japanese CiNii (Q10726338) bibliography. AKA NCID
Data type	String
Template parameter	n/a
Domain	Books
Example	The Catcher in the Rye (Q183883) => BA89854848 (resolves to http://ci.nii.ac.jp/ncid/BA89854848 - English version at http://ci.nii.ac.jp/ncid/BA89854848?l=en)
Source	CiNii (Q10726338)
Formatter URL	http://ci.nii.ac.jp/ncid/$1
Robot and gadget jobs	Possible
Proposed by	Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits

Discussion

Also acts as a form of Authority Control. Also usable in COinS (Q1024186) metadata [2]. Note that we already offer NACSIS-CAT author ID (P271) from the same source. The title is not "work identifier", as there is a separate ID for journal articles. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 13:04, 7 February 2015 (UTC)

OK,  Done. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 19:53, 9 March 2015 (UTC)

Bradley and Fletcher checklist number

   Done: Bradley and Fletcher checklist number (P1743) (Talk and documentation)

Description	Reference for a species in the Bradley and Fletcher checklist of over 2,700 species British lepidoptera ("A Recorder's Log Book or Label List of British Butterflies and Moths" by J.D. Bradley and D.S. Fletcher.)
Data type	String
Template parameter	n/a
Domain	Lepidoptera (Q28319) species of the United Kingdom
Allowed values	Integers below 2500; or the same suffixed with a lower-case letter.
Example	Incurvaria praelatella (Q1355083) -> 132; Saturnia pyri (Q265918) -> 1643a
Source	Op. Cit.; also [3]
Robot and gadget jobs	Possible
Proposed by	Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits

Discussion

Widely used by the UK biological recording community. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 16:46, 6 February 2015 (UTC)

@Pigsonthewing:  Created as Bradley and Fletcher checklist number (P1743). Jon Harald Søby (talk) 23:09, 9 March 2015 (UTC)

Agassiz et al checklist number

   Done: Agassiz checklist number (P1744) (Talk and documentation)

Description	Reference for a species in the 2013 checklist of over 2,700 species British lepidoptera ("A checklist of the Lepidoptera of the British Isles" by Agassiz, D.J.L., Beavan, S.D. & Heckford R.J. 2013)
Data type	String
Template parameter	n/a
Domain	Lepidoptera (Q28319) species of the United Kingdom
Allowed values	Two integers separated by a decimal point; the first integer being maximum two digits; the second four digits
Example	Incurvaria praelatella (Q1355083) -> 8.004; Saturnia pyri (Q265918) -> 68.0011
Source	Op. Cit.; also [4]
Robot and gadget jobs	Possible
Proposed by	Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits

Discussion

Widely used by the UK biological recording community. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 16:46, 6 February 2015 (UTC)

@Pigsonthewing:  Created as Agassiz checklist number (P1744). Jon Harald Søby (talk) 23:19, 9 March 2015 (UTC)

VASCAN ID

   Done: VASCAN ID (P1745) (Talk and documentation)

Description	identifiant of the Database of Vascular Plants of Canada (Canada, Greenland dans Saint-Pierre-et-Miquelon)
Represents	Tracheophyta (Q27133)
Data type	String
Domain	Taxons
Allowed values	number
Example	Picea mariana (Q218425) --> 7174
Source	http://data.canadensys.net/vascan/search
Proposed by	Fralambert (talk)

Discussion

WikiProject Taxonomy has more than 50 participants and couldn't be pinged. Please post on the WikiProject's talk page instead. Identifiant of all species of Tracheophyta (Q27133) present in Canada, Greenland and Saint-Pierre-et-Miquelon. Give the official name in french and english for the plants in the territory. --Fralambert (talk) 02:40, 16 February 2015 (UTC)

In many ways, this is similar to the Dyntaxa ID proposed above. There is little or no original information, just a presentation of highlights as seen from a particular country. If we start this we will end up with a lot of these national databases (something like Bellis perennis may end up with dozens of these ID's as statements). In this particular case I am not impressed with the maps (not the actual distribution, but the states in which it occurs). - Brya (talk) 05:02, 16 February 2015 (UTC)

The paper Database of Vascular Plants of Canada (VASCAN): a community contributed taxonomic checklist of all vascular plants of Canada, Saint Pierre and Miquelon, and Greenland (2013) gives some background information. The data are released as CC0. --Succu (talk) 10:21, 16 February 2015 (UTC)

 Support I think it meets the quality requirements for out "identifier + link"-data. @Brya: I think dozens of statements is not even the beginning of what some items will likely have. In my opinion more a problem on the view and filter side of the database than on the data-side of the database. The interface will need to become smarter once we have hundreds or thousands of statements on single items. --Tobias1984 (talk) 10:31, 16 February 2015 (UTC)

The fact that I have mixed feelings does not mean I don't see some benefits as well. This would be a real database, easily managed. Having a lot of such databases entered into items (and there are quite a few of them!) would make it easy for the user to see what are the "good taxa" that are widely accepted. The fictitious taxa would stay bare of them. But still this means adding a lot of statements for very little real gain in information, a massive redundancy. Also, there would be a skewed effect: taxa in developed countries can be found in lots of databases, while taxa in undeveloped countries have no databases to be listed in. - Brya (talk) 11:44, 16 February 2015 (UTC)

I would rather have something with real information: we still do not have the e-flora's. - Brya (talk) 11:59, 16 February 2015 (UTC)

@Brya: That is exactly how I see it. The extra statements are a tradeoff between redundancy and some sort of measure of how established a name is in the literature (The latter with a lot of question marks, if the databases copy data between each other without any checks). The comment about developed countries is a lot more difficult and probably can't be solved intrinsically by Wikidata. It is kind of similar situation to the gender-bias (if it can even be called a bias) on Wikipedia and Wikidata. We can't write more about women, if none of our sources write more about women. So it is a bias of the worlds body of literature and not one of Wikipedia/Wikidata. At least in biology we know that the coverage-situation is improving (on a long time scale). --Tobias1984 (talk) 15:20, 17 February 2015 (UTC)

In the case of these official national databases, I am not worried about errors: these are to a high standard (the errors can be found in the ambitious world-wide aggregators, like the Catalogue of Life, The Plant List: in these the error rate is pretty much off the scale). But redundancy is an issue: if we adopt VASCAN ID we will also have to adopt the USDA Plants, and VASCAN ID will have little that is not in USDA Plants as well. This is a lot more pronounced in Europe, very likely there will be a French database, a Belgian database, a Dutch database, a British database, a German database, an Austrian database, etc). And, yes, coverage is increasing, even on a short time scale, it is just that garbage seems to be increasing at least as fast. . . - Brya (talk) 18:03, 17 February 2015 (UTC)

@Brya: Wikidata is all about "somebody says this", it's not up to us to decide whether or not it is an error. It's up to somebody who want to cross datas to decide whether or not it's a good information. Known errors are to be marked "deprecated", that's all. TomT0m ^(talk)

Ah, the phylosophy of "let's connect everything to everything else, making the biggest, most impenetrable, most error-riddled tangle imaginable". The purpose of Wikidata is to hold structured data based on reliable sources. It is the duty of users to decide what should and what should not be included; Wikidata is here to fight the connect-everything-to-everything-else-phylosophy and to keep out the junk. Marking known errors as "deprecated" proves to be very damaging and is quite insufficient. - Brya (talk) 17:34, 23 February 2015 (UTC)

Ah, your beautiful comments, formated god knows how (seems it's just done that way to annoy), and unproved claim ... Marking deprecated is the standard way to do in Wikidata. Can't you automatically track the differences beetween the databases ? Is'nt it just an ID property by the way ? There can be no mistake (there could be, but it won't be because the databases have errors). TomT0m ^(talk) 20:41, 23 February 2015 (UTC)

Having a salespitch ready to explain why you are doing it wrong does not make it less wrong. - Brya (talk) 06:07, 24 February 2015 (UTC)

 Support. Known database, traceable information. Could even be use to track known errors in those databases. TomT0m ^(talk) 14:51, 23 February 2015 (UTC)

 Support I think this dataset could be usful in the future. It contains vernacular names in en and fr and distributions at ISO 3166-2 (Q133153) level. Around 10,000 of our taxa would have a match. --Succu (talk) 12:57, 24 February 2015 (UTC)

@Fralambert, Tobias1984, TomT0m, Brya, Succu:  Created as VASCAN ID (P1745). Jon Harald Søby (talk) 23:27, 9 March 2015 (UTC)

GRIN Taxonomy ID (en) / identifiant GRIN (fr)

   Not done

Description	ID of the National Plant Germplasm System - GRIN Taxonomy for Plants
Data type	String
Domain	plant taxons
Example	Sairocarpus nuttallianus => 456783
Source	http://www.ars-grin.gov
Proposed by	Minerv (talk) 20:41, 20 February 2015 (UTC)

Discussion

Motivation Property:P685 ; Property:P961 ; Property:P1070...
(Could someone delete the page Q19328829..., thanks!)

Minerv, we have GRIN URL (P1421). --Succu (talk) 22:23, 20 February 2015 (UTC)

With some late, thank you Succu. I've seen it, after, in Taxonomy properties - Databases on each discussion page. Minerv (talk) 17:17, 26 February 2015 (UTC)

@Minerv, Succu:  Not done, already exists as GRIN URL (P1421) (please correct me if I misunderstood). Jon Harald Søby (talk) 23:28, 9 March 2015 (UTC)

@Minerv, Succu, Jon Harald Søby: Why are we storing this as a URL, not an identifier, as we do for similar properties? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 16:17, 21 March 2015 (UTC)

Andy Mabbett, this would require three IDs (see: Wikidata:Property_proposal/Archive/24#GRIN-URL). --Succu (talk) 16:24, 21 March 2015 (UTC)

┌────────────────────────────────────────────────────────────────────────────────────────────────────┘

Thank you. And I also see the IDs are not unique:

• http://www.ars-grin.gov/cgi-bin/npgs/html/genus.pl?10404
• http://www.ars-grin.gov/cgi-bin/npgs/html/taxon.pl?10404

-( Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 16:31, 21 March 2015 (UTC)

Still, I feel that the whole string is cumbersome and that having three ID's ("taxon.pl?10404", "genus.pl?10404" and "family.pl?10404") would be preferable, as being a lot more readable. - Brya (talk) 16:40, 21 March 2015 (UTC)

ZooBank nomenclatural act

   Done: ZooBank ID for name or act (P1746) (Talk and documentation)

Description	identifier for nomenclatural act at ZooBank
Represents	scientific name (Q15730631)
Data type	String
Domain	zoology (Q431), ZooBank (Q8074026)
Example	Amargastegos (Q19377675) => FB0A73A0-E464-4919-8307-80DCCB14FB16
Format and edit filter validation	^[A-Za-z0-9]{8}-[A-Za-z0-9]{4}-[A-Za-z0-9]{4}-[A-Za-z0-9]{4}-[A-Za-z0-9]{12}$
Source	http://zoobank.org/
Formatter URL	http://zoobank.org/NomenclaturalActs/$1
Proposed by	Succu (talk)

Discussion

ZooBank is a central, authoritative resource for scientific names in zoology and the official registry of Zoological Nomenclature. (see About ZooBank). Succu (talk) 14:58, 2 March 2015 (UTC) WikiProject Taxonomy has more than 50 participants and couldn't be pinged. Please post on the WikiProject's talk page instead.

 Support --Tobias1984 (talk) 16:56, 2 March 2015 (UTC)

 Support - have never really used it, but obviously an important database (and will be more important in the future). - Brya (talk) 17:19, 2 March 2015 (UTC)

 Support – needed to handle zoological nomenclature properly. --Daniel Mietchen (talk) 00:50, 4 March 2015 (UTC)

@Succu, Tobias1984, Brya, Daniel Mietchen:  Created as ZooBank ID for name or act (P1746). Jon Harald Søby (talk) 23:34, 9 March 2015 (UTC)

Flora of China

   Done: Flora of China ID (P1747) (Talk and documentation)

Description	TaxonId in Flora of China (Q5460442)
Represents	plant (Q756)
Data type	String
Domain	plant (Q756)
Example	Orchidaceae (Q25308) => 10638
Format and edit filter validation	[1-9]\d{4,9}
Source	Flora of China (Q5460442) (FOC)
Formatter URL	http://www.efloras.org/florataxon.aspx?flora_id=2&taxon_id=$1
Proposed by	Succu (talk)

Discussion

After Flora of North America taxon ID (P1727) (used around 10,000 times) we should add the next eFlora. --Succu (talk) 11:13, 3 March 2015 (UTC) WikiProject Taxonomy has more than 50 participants and couldn't be pinged. Please post on the WikiProject's talk page instead.

•  Support Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 11:21, 3 March 2015 (UTC)
•  Support --Tobias1984 (talk) 11:23, 3 March 2015 (UTC)
•  Support -- sure. - Brya (talk) 11:48, 3 March 2015 (UTC)
•  Support Looks good to me. --Daniel Mietchen (talk) 00:55, 4 March 2015 (UTC)

@Succu, Pigsonthewing, Tobias1984, Brya, Daniel Mietchen:  Created as Flora of China ID (P1747). Jon Harald Søby (talk) 23:40, 9 March 2015 (UTC)

Watson & Dallwitz

   Done: Watson & Dallwitz family ID (P1761) (Talk and documentation)

Description	familyID in Watson & Dallwitz: The families of flowering plants
Data type	String
Domain	plant families
Example	Caryophyllaceae (Q25995) => caryophy
Source	L. Watson and M.J. Dallwitz (1992 onwards). The families of flowering plants: descriptions, illustrations, identification, and information retrieval. http://delta-intkey.com
Formatter URL	http://delta-intkey.com/angio/www/$1.htm
Proposed by	Brya

Discussion

This concerns only a small number of pages (ca 600 families?), but very heavily used on Wikipedia's as it is very convenient, so we really should have it. WikiProject Taxonomy has more than 50 participants and couldn't be pinged. Please post on the WikiProject's talk page instead.. - Brya (talk) 18:08, 6 March 2015 (UTC)

 Support --Succu (talk) 07:45, 9 March 2015 (UTC)

@Brya: @Succu:  Done Watson & Dallwitz family ID (P1761) Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 22:59, 13 March 2015 (UTC)

USDA Plants ID

   Done: USDA PLANTS ID (P1772) (Talk and documentation)

Description	ID in USDA Plants
Data type	String
Domain	plants
Example	Pseudotsuga menziesii (Q156687) => PSME
Source	USDA Plants Database
Formatter URL	http://plants.usda.gov/core/profile?symbol=$1
Proposed by	Brya

Discussion

As we already have VASCAN, it would make sense to also have its big brother. - Brya (talk) 06:39, 12 March 2015 (UTC) WikiProject Taxonomy has more than 50 participants and couldn't be pinged. Please post on the WikiProject's talk page instead.

•  Support - My bot can add them. --Succu (talk) 16:25, 12 March 2015 (UTC)
•  Support Useful. --Daniel Mietchen (talk) 00:29, 15 March 2015 (UTC)

@Brya: @Succu: @Daniel Mietchen:  Done USDA PLANTS ID (P1772) Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 13:52, 20 March 2015 (UTC)

NCI Thesaurus ID

   Done: NCI Thesaurus ID (P1748) (Talk and documentation)

Description	NCI Thesaurus (NCIt) provides reference terminology for many NCI and other systems. It covers vocabulary for clinical care, translational and basic research, and public information and administrative activities.
Represents	NCI Thesaurus (Q19404626)
Data type	String
Domain	Diseases
Allowed values	alphanumeric
Example	Cornelia de Lange syndrome (Q1133289)=>C75016
Source	http://ncit.nci.nih.gov/ncitbrowser/ConceptReport.jsp?dictionary=NCI_Thesaurus&version=14.10d&code=C75016
Robot and gadget jobs	Should or are bots or gadgets doing any task with this? (Checking other properties for consistency, collecting data, etc.)
Proposed by	Andrawaag (talk)

Discussion

In our efforts of enriching Wikidata with Disease ontology terms and related identifiers, we have erroneously added NCIthesaurus terms with property P1395 (National Cancer Institute ID) This has been reverted, but we very much like to add these NCIthesaurus identifiers to disease terms in Wikidata. Would it be possible to add the NCIthesaurus property? Andrawaag (talk) 21:55, 3 March 2015 (UTC)

•  Support Andrew Su (talk) 00:21, 4 March 2015 (UTC)
• I agree that would be useful to have. Not sure how best to fill in the "allowed values" field – is it always a capital C followed by a series of digits? How many?
  Tobias1984
  Doc James
  Bluerasberry
  Gambo7
  Daniel Mietchen
  Andrew Su
  Andrux
  Pavel Dušek
  Mvolz
  User:Jtuom
  Chris Mungall
  ChristianKl
  Gstupp
  Sintakso
  علاء
  Adert
  CFCF
  Jtuom
  Drchriswilliams
  Okkn
  CAPTAIN RAJU
  LeadSongDog
  Ozzie10aaaa
  Marsupium
  Netha Hussain
  Abhijeet Safai
  Seppi333
  Shani Evenstein
  Csisc
  Morgankevinj
  TiagoLubiana
  ZI Jony
  Antoine2711
  JustScienceJS
  Scossin
  Josegustavomartins
  Zeromonk
  The Anome
  Kasyap
  JMagalhães
  
  Notified participants of WikiProject Medicine --Daniel Mietchen (talk) 02:08, 4 March 2015 (UTC)
•  Support It is a capital C, while the number of digits varies from 3 to 6 (for now). Emitraka (talk) 14:16, 4 March 2015 (UTC)
•  Support --Succu (talk) 14:28, 4 March 2015 (UTC)

@Andrawaag, Andrew Su, Daniel Mietchen, Emitraka, Succu:  Created as NCI Thesaurus ID (P1748), but can someone please write a good description for it? Jon Harald Søby (talk) 23:48, 9 March 2015 (UTC)

 Done Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 10:34, 16 March 2015 (UTC)

PSGC code

   Not done

Description	PSGC (Philippines Standard Geographic Code) for location – region code + province code + city / municipality code + barangay code
Data type	String
Template parameter	Nothing preset, but usually uses |blank1_name_sec1= and |blank1_info_sec1= in en:template:infobox settlement e.g. see en:Bogo, Cebu
Allowed values	99 = region code + 99 = province code + 99 = city / municipality code + 999 = barangay code. Zeros are permitted, hierarchically, i.e. 999999000 means city / municipality, 999900000 means province , 990000000 means region
Example	en:Bogo, Cebu => PSGC 072211000 = region 07 (Central Visayas), province 22 (Cebu), mun/city 11, barangay = 000; en:Bongbong, Ubay => PSGC 071246007 = region 07, province 12 (Bohol), mun 46 (Ubay), barangay 007
Source	external reference, Wikipedia list article, etc.

Discussion

Motivation:

Proposed by: Unbuttered Parsnip (talk)

Many Philippine administrative properties are not catered for. This is necessary to automate many data entry methods. Potential usage is many thousands. Unbuttered Parsnip (talk) 23:48, 26 March 2015 (UTC)

• I found this under its abbreviated name psgc = p988. So withdraw this request of course. Sorry -- Unbuttered Parsnip (talk) 02:07, 29 March 2015 (UTC)

  That is Philippine Standard Geographic Code (P988). Visite fortuitement prolongée (talk) 17:44, 29 March 2015 (UTC)

property used in this template

   Withdrawn

Description	list properties used in a given template
Data type	Property
Domain	templates
Allowed values	any property
Example	Template:Infobox person (Q6249834): date of birth (P569), date of death (P570), etc.
Source	templates at Wikipedia

Discussion

Illustrate usage of properties --- Jura 05:45, 19 December 2014 (UTC)

•  Support, though I would recommend moving this proposal to Wikidata:Property_proposal/Property_metadata. Emw (talk) 05:54, 19 December 2014 (UTC)

  I placed it here as this meant for templates, not for properties. --- Jura 06:28, 19 December 2014 (UTC)

Jura, thanks for the clarification. I now see this proposal makes sense to have here. Emw (talk) 15:39, 27 December 2014 (UTC)

•  Comment Template:Infobox person (Q6249834) has 120 sitelinks to 120 different templates. Some templates use date of birth (P569), another do not use. So claim Template:Infobox person (Q6249834) <property used in this template> date of birth (P569) is not true in general. — Ivan A. Krestinin (talk) 22:32, 17 February 2015 (UTC)
  • "applies to part" could be used. --- Jura 03:43, 18 February 2015 (UTC)
•  Comment We have {{ExternalUse}} and developers are working on tracking entity usage. Matěj Suchánek (talk) 17:08, 1 March 2015 (UTC)
  • Well, you could actually use this property to build the fields retrieved by the template. Of course, one can always use a template instead, but isn't this where we came from? --- Jura 17:28, 2 March 2015 (UTC)
•  Comment how would this be used? How do I know what field in the template corresponds to what property? I doubt this will work and scale. How do you deal with properties being used in language a, but not language b? This should be part of a bigger plan/design. Multichill (talk) 19:30, 8 March 2015 (UTC)
• Oppose creation — this should be handled in the core software, not via property. --Izno (talk) 17:30, 9 March 2015 (UTC)
•  Oppose per Izno. Jon Harald Søby (talk) 00:01, 10 March 2015 (UTC)
•  Oppose see also Wikidata:Property_proposal/Unsorted#Infobox_property --Pasleim (talk) 21:06, 24 March 2015 (UTC)
• Withdrawn --- Jura 05:32, 11 April 2015 (UTC)

corresponding numerical code

   Not done

Description	qualifier for alpabetical codes containing the corresponding numerical value
Data type	String
Allowed values	\d+
Example	Euro (Q4916): ISO 4217 code (P498) => EUR (qualifier => 978) English (Q1860): GOST 7.75–97 code (P278) => анг (qualifier => 45)

Discussion

Many of the code systems have both alpha and numeric value for the same entity. There is the problem of entering these codes. In most cases, the code property includes only alphabetical code. And even if there is a separate property for a numeric code, is impossible to establish a correspondence between them. Sometimes code is entered as a string containing both alpha and numeric values, but it reduces the usability of such a value, it must be pre-processed every time before use. The proposed qualifier solves some of these problems. It's must be string, not numeric, because some codes have leading zeroes. —putnik 20:55, 20 March 2015 (UTC)

•  Oppose I'd rather see a separate property. --- Jura 14:04, 24 March 2015 (UTC)
  • @Jura1: Even if we are going to create separate properties, we need to be able establish a connection between them, in cases where there is more than one value. E. g. Russian ruble (Q41044): ISO 4217 code (P498) => RUB (643), RUR (810). —putnik 20:23, 24 March 2015 (UTC)
    • Here is one for ISO 3166: click "Show". --- Jura 20:34, 24 March 2015 (UTC)
•  Oppose Agree with Jura: there should be two props "ISO 4217 alphabetic code" and "ISO 4217 numeric code". Two reasons:
  • The chance that people would accurately enter the numberic code as proposed above, approximates zero
  • What matters is that RUR and 810 are obsolete (end time 1998), not so much that they correspond to each other

--Vladimir Alexiev (talk) 09:55, 25 March 2015 (UTC)

 Not done, no support. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 16:46, 29 March 2015 (UTC)

KulturNav ID

   Not done

Description	The ids as used by KulturNav, a common site for ontologies used within the cultural sector in Norway and Sweden.
Data type	string (really an ID but we don't have anything like that)-invalid datatype (not in Module:i18n/datatype)
Domain	Thing (Item)
Allowed values	string (ref to dataset)
Example 1	MISSING
Example 2	MISSING
Example 3	MISSING
Format and edit filter validation	UUID
Source	http://kulturnav.org/2b94216b-f2fc-46a3-b2ce-eeb93aa19185?format=application/rdf%2Bxml (several other formats exists)
Formatter URL	http://kulturnav.org/$1
Robot and gadget jobs	Manuel verification, but could use automatic updates.

Discussion

Motivation: KulturNav is a common site for all kinds of ontologies used to describe the content in Norwegian and Swedish museums. Often this will map nicely to encyclopedic content in Wikipedia and then further onto Wikidata. Even if almost everything can be mapped to similar descriptions here, one type of mapping seems to me especially interesting and that is persons. A lot of persons that otherwise lacks good IDs given by an autority will be defined in this registry. Over time there will be a separate registry in Norway, the so called Historical person registry, but it will take time to make that an viable option. As most of the historical persons will be cultural persons already described in KulturNav we can speed up things and start building the connections with IDs from KulturNav.

There is a slight problem with how the entity and the dataset is separated. We can always use the UUID from the URL as the identifier, but this is strictly speaking for the dataset and not for the entity. Most datasets seems to have a fragment id #entity.alternativeId-0 and this as the full URL (http://kulturnav.org/2b94216b-f2fc-46a3-b2ce-eeb93aa19185#entity.alternativeId-0) could be a valid URI for the entity. It doesn't seem to be available information about this, so it is perhaps better to say we have a seeAlso-like relation with the dataset until they can provide some documentation. Using the UUID is a bit fishy anyhow, so the philosophical problem isn't that important.

Proposed by: Jeblad (talk)

•  Comment same as KulturNav-ID (P1248) ? --- Jura 15:33, 7 April 2015 (UTC)

Yes… :D Jeblad (talk) 15:38, 7 April 2015 (UTC)

Drainage basin

   Not done

Description	basin drained by a river and its tributaries which this item is within
Represents	drainage basin (Q166620)
Data type	Item
Domain	river (Q4022)
Allowed values	instances under drainage basin (Q166620)
Example	Amazon (Q3783) => drainage basin => Amazon basin (Q244451) Xingu River (Q49544) => drainage basin => Amazon basin (Q244451)
Robot and gadget jobs	possible
Proposed by	Josh Baumgartner (talk)

Discussion

Link to the item of the drainage basin a stream or river are a part of. Josh Baumgartner (talk) 21:07, 2 March 2015 (UTC)

• Would this be better reversed, i.e. Amazon basin (Q244451) -> drained by -> Amazon (Q3783) ? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 15:04, 22 March 2015 (UTC)
  • @Pigsonthewing: With the example of Amazon (Q3783), I suppose it could go either way, but doing it as proposed allows tributaries to also be linked to the basin they are part of (I have added an example of this above). Doing it in reverse could be done with an inverse property and a bot to automate the linking, but the list could get pretty long for a big basin like the Amazon with hundreds of tributaries. Josh Baumgartner (talk) 16:23, 23 March 2015 (UTC)
    • @Joshbaumgartner, Pigsonthewing: See Wikidata:Property_proposal/Archive/23 for previous request. Micru said located in/on physical feature (P706) shoyld be used instead.--GZWDer (talk) 12:37, 18 April 2015 (UTC)

 Not done @GZWDer, Pigsonthewing: Missed that one in my search. Proposal withdrawn and archived. Thanks! Josh Baumgartner (talk) 17:01, 20 April 2015 (UTC)

sensu stricto / in the narrow sense

   Not done

Description	meaning in the narrow sense
Data type	qualifier-invalid datatype (not in Module:i18n/datatype)
Domain	organism (Q7239), fossil (Q40614), but also other things
Allowed values	organism (Q7239), fossil (Q40614), but also other things
Example	Sensu stricto meaning of Alum is Potassium alum (Q190527 -> Q411309), In a restrictive sense bryophyte means moss (Q29993 -> Q25347)
Proposed by	Kopiersperre (talk)

Discussion

Some terms have had a narrower sense in historic times. Can especially be used in taxonomy.--Kopiersperre (talk) 14:20, 14 October 2014 (UTC)

@Kopiersperre:, I do not think that really works. What does it mean that stricto sensu, alum (Q190527) means potassium aluminium sulfate (Q411309) ? Items can only have one meaning, else it would be a mess. Here we are talking about the word "alum" not about item Q190527. What we may want to say is something like: "in a restrictive sense, "alum" means "Q411309", not "Q190527". One way to say this might be through qualifiers to string-type property like "potassium aluminium sulfate (Q411309): name: "alum" some qualifier: stricto sensu". But that does not seem very clear. A better place for that would be the next Wikibase-based version of the Wiktionary. --Zolo (talk) 13:28, 24 October 2014 (UTC)

You're right that Alum could be better handled at Wiktionary. But for taxons I think this is needed in wikidata. In most (all?) cases there should be only one sensu stricto meaning.--Kopiersperre (talk) 17:04, 24 October 2014 (UTC)

Kopiersperre: Really? Why? --Succu (talk) 21:18, 24 October 2014 (UTC)

Because original meanings get extended in the history of science. I have no example where something has two narrower meanings.--Kopiersperre (talk) 16:39, 25 October 2014 (UTC)

Kopiersperre Would this be better done using date qualifiers. Listing the various meanings at various times with start dates and end dates? Filceolaire (talk) 20:24, 31 October 2014 (UTC)

Filceolaire For old ones you can't figure out in many cases.--Kopiersperre (talk) 13:14, 20 November 2014 (UTC)

•  Oppose Wikidata items are about concepts, not about the meaning of words. If a word has had two different meanings over time then that word will appear in two different wikidata items (probably as an alias). Filceolaire (talk) 16:48, 2 March 2015 (UTC)
•  Oppose per Filceolaire --Pasleim (talk) 21:12, 29 March 2015 (UTC)

 Not done @Kopiersperre, Zolo, Filceolaire, Pasleim: No consensus. Josh Baumgartner (talk) 17:24, 20 April 2015 (UTC)

number of locations

   Not done

Description	Number of locations the company has physical properties.
Data type	Number (not available yet)
Template parameter	"locations" in en:template:infobox company
Domain	restaurants, chains
Allowed values	quantities
Example	Red Lobster (Q846301) => 705
Proposed by	AmaryllisGardener talk

Discussion

Useful info used in infoboxes. --AmaryllisGardener ^talk 15:02, 6 November 2014 (UTC)

@AmaryllisGardener: quantity (P1114) also has the meaning "number of instances". Could we add "number of locations as an alias or do you think it will cause problems? -Tobias1984 (talk) 15:52, 6 November 2014 (UTC)

Seems maybe a little bit too generic, but I wouldn't object to it. --AmaryllisGardener ^talk 04:18, 8 November 2014 (UTC)

 Oppose Difficult to keep up-to-date and a proper definition of location has to be given: production facilities, warehouses, offices,... Everything or with some rules ? Snipre (talk) 14:32, 9 December 2014 (UTC)

 Comment quantity (P1114) is not well defined, still I think these properties are different, namely quantity (P1114) indicates the number of instances, e.g. number of instances of a species (am I right?), while in the case of restaurants, we have only one chain of restaurants with many participants. They are not instances, they are parts of the chain. The problem with keeping up-to-date is artificial, since there are hundreds of properties that change on a daily basis and are kept in Wikidata (e.g. employees (P1128)). And the last but not the least, making Wikidata really comprehensive would mean importing data e.g. from OpenStreetMap, where the restaurant locations are indicated, would yield this property redundant, because a query on the DB would give the number. Apohllo (talk) 00:00, 16 January 2015 (UTC)

 Oppose use employees (P1128) with qualifier of (P642), e.g. Red Lobster (Q846301) => 705 with qualifier of (P642)=restaurant (Q11707) --Pasleim (talk) 21:52, 21 January 2015 (UTC)

The definition of employees (P1128) clearly states that it indicates the number of people. Extending it to the number of building/places goes way to far for me. Apohllo (talk) 09:55, 22 January 2015 (UTC)

 Not done @AmaryllisGardener, Snipre, Apohllo, Pasleim: No consensus. Josh Baumgartner (talk) 21:41, 20 April 2015 (UTC)

investigated by

   Done: investigated by (P1840) (Talk and documentation)

Description	The person or organisation that investigated/is investigating the event
Data type	Item
Template parameter	?
Domain	events that are investigated, e.g. transportation accidents, crimes, etc
Allowed values	organisations, people
Example	Grayrigg derailment (Q1028014) => Rail Accident Investigation Branch (Q7283877) + His Majesty's Railway Inspectorate (Q3133363) Plebgate (Q7204344) => metropolitan police (Q3394118) + Independent Police Complaints Commission (Q6516678) 2013 Vauxhall helicopter crash (Q3182149) => Air Accidents Investigation Branch (Q406725) murder of Victoria Climbié (Q6587566) => Herbert Laming, Baron Laming (Q1608707)
Source	Wikipedia articles, news reports, websites of investigating authorities
Robot and gadget jobs	?

Discussion

Motivation:

Proposed by: Thryduulf (talk: local | en.wp | en.wikt)

Improving the entry for Grayrigg derailment (Q1028014) I noticed this is a missing property. It would also allow, when reverse searches are possible, generating a list of notable investigations by a particular person or organisation. Thryduulf (talk: local | en.wp | en.wikt) 05:33, 23 March 2015 (UTC)

If possible, a qualifier for an investigation reference would be good (e.g. the RAIB's reference for the report into the Grayrigg derailment is "20/2008"), but I don't know how to properly propose these. Thryduulf (talk: local | en.wp | en.wikt) 05:37, 23 March 2015 (UTC)

Are there URLs for the "20/2008" report and suchlike? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 08:17, 23 March 2015 (UTC)

There is a list of reports by year on the RAIB website, e.g. [5] for 2008 (although that link will probably change at some point as the RAIB is migrating to a subdomain of gov.uk) if that is what you are asking. The reports are all PDFs linked from there. Thryduulf (talk: local | en.wp | en.wikt) 20:36, 23 March 2015 (UTC)

@Thryduulf: Thank you. What I was looking for was http://raib.gov.uk/publications/investigation_reports/reports_2008/report202008.cfm - with a view to formally proposing a property for use as a qualifer, as you suggested. What about the other types of report? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 22:19, 23 March 2015 (UTC)

Bulletins are named in the same format but a separate sequence, e.g. Bulletin 03/2013 (sometimes they are distinguished as Bnn/yyyy and Rnn/yyyy but this may be in file names only). There has only been one discontinuation report to date [6] It is not named in the document, but the file name suggests "DR01/2007" or "Discontinuation report 01/2007". There are three interim reports IR01/2007, Report IR02/2007 and Report IR1/2013. Annual reports are unlikely to be relevant. These are all related to the RAIB though, every investigating authority will have it's own format. The MAIB appears to use "report_type n/yyyy", e.g. Accident Investigation Report 7/2015, MAIB Safety Bulletin 2/2014. In all cases the number is a serial number of reports of that type in the year. The Australian Transport Safety Bureau uses "AO-yyyy-nnn" for aviation e.g. [7] and similar but "RO-yyyy-nnn" for rail, in both cases it appears to be the year and serial number of the incident not the report. For Marine accidents it uses "nnn-MO-yyyy-nnn" e.g. 306-MO-2014-001 my guess at the format is "cumulative marine incident number-MO-year of incident-serial number of incident in year". One off reports, e.g. the Hutton Enquiry, will not have a predictable format. Thryduulf (talk: local | en.wp | en.wikt) 02:06, 25 March 2015 (UTC)

Maybe actually better would be to have a property for an investigation report which links to the URI and/or ISBN of the report, with sub-properties/qualifiers for the reference and who investigated it? Thryduulf (talk: local | en.wp | en.wikt) 15:17, 25 March 2015 (UTC)

@Pigsonthewing:? Anyone else? Thryduulf (talk: local | en.wp | en.wikt) 21:16, 8 April 2015 (UTC)

•  Support. Filceolaire (talk) 20:21, 10 April 2015 (UTC)
•  Support. Emw (talk) 20:19, 12 April 2015 (UTC)

 Done investigated by (P1840) @Thryduulf, Pigsonthewing, Filceolaire, Emw: Josh Baumgartner (talk) 22:02, 20 April 2015 (UTC)

disputed author

   Not done

Description	For old works the author often is not known but only ascribed.
Data type	Item
Domain	written works
Allowed values	multiple items (which have to be humans)
Example	Hippias Major (Q634846), First Alcibiades (Q1153509) -> Plato is the disputed author but not the author
Proposed by	Mischa004 (talk)

Discussion

I want to work with Wikidataproject Books and therefore I need this property. Mischa004 (talk) 11:22, 21 January 2015 (UTC)

 Support ... at least I don't know a better solution. --Kolja21 (talk) 11:46, 21 January 2015 (UTC)

 Comment Is this best handled by a separate property, or by 'author' with qualifiers? - PKM (talk) 19:54, 22 January 2015 (UTC)

 Comment User PKM is on the right track: there is allready a qualifier sourcing circumstances (P1480) to add to statements, indicating there is something rotten with the claim. There is a list of possible cases and you might expand it after discussion on Property_talk:P1480. So no extra property needed--Giftzwerg 88 (talk) 14:36, 11 February 2015 (UTC)

Thanks, discussion continues here: Property talk:P1480#New value.--Mischa004 (talk) 10:30, 27 January 2015 (UTC)

•  Oppose. Use statement disputed by (P1310) after the 'author' statement. See First Alcibiades (Q1153509)Filceolaire (talk) 20:59, 7 March 2015 (UTC)

 CommentI think the user has withdrawn this proposal--Giftzwerg 88 (talk) 07:16, 31 March 2015 (UTC)

 Not done per lack of support, redirection of discussion. @Mischa004, Kolja21, Filceolaire, Giftzwerg 88: Josh Baumgartner (talk) 22:35, 20 April 2015 (UTC)