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
Descriptionposition held in a french voluntary association (association loi de 1901)
Data typeItem
Domainorganization (Q43229) (organisation)
Example 1MISSING
Example 2MISSING
Example 3MISSING
Proposed byHopala!
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. Error in replyto template: Username not given. See Template:Replyto for usage. 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

DescriptionIdentifier 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
RepresentsJournalisted ID (Q18575559)
Data typeString
Template parameter|journalisted= in en:Template:UK MP links and en:Template:UK Peer links; and in its recently-created en:Template:Journalisted.
DomainPersons
Allowed valuesURL stems from Journalisted profile URLs
ExampleTom Watson (Q263802) => tom-watson (resolves to http://journalisted.com/tom-watson )
SourceWikipedia, Journalsited
Robot and gadget jobsPossible
Proposed byAndy 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 (P1731) (Talk and documentation)
DescriptionFach (Q1748957), describes the special ablilites of an operatic singers voice
RepresentsFach (Q1748957)
Data typeItem
Domainpersons: operatic singers, singers of classical music. Not intended to use for singers in other music styles.
Allowed valuesitems 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) ....
ExampleFritz Wunderlich (Q57809) => lyric tenor (Q359282)
Format and edit filter validationitems with this property need to have voice type (P412), several values are common.
Proposed byGiftzwerg 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 (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
Descriptionnumber worn on a sports player's uniform
Representsuniform number (Q599003)
Data typeNumber (not available yet)
Domainhuman (Q5)
Allowed valuesnumber
ExampleZinedine Zidane (Q1835) member of sports team (P54) France national association football team (Q47774) => 10
Proposed byHarmonia 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

Descriptionlink to the biography pages of the German parliament
Data typeURL
DomainPersons
Allowed valuesURLs like http://www.bundestag.de/bundestag/abgeordnete*/biografien/*
ExampleAngela Merkel (Q567) => http://www.bundestag.de/bundestag/abgeordnete18/biografien/M/merkel_angela.html
Proposed byHoo 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
Descriptionclaim of education, studies of the item
Data typeItem
Domainstudies, professions
Allowed valuesscience (Q336)
ExampleBeispiel: 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 jobsFü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 byOursana (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)
Descriptionpersons 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 typeItem
Template parameterHier den Infobox-Parameter einfügen, falls es einen gibt. Beispiel: "Bevölkerung" (population) in en:template:infobox settlement
DomainPersons
Allowed valueshuman (Q5)
ExampleHelene 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 byOursana (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)
  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

Descriptiondate when a , use as qualifier
Representsoath of office (Q774482)
Data typePoint in time
Template parameter"Giuramento" in it:Giudici_della_Corte_costituzionale_della_Repubblica_Italiana#Elenco_cronologico
Domainoffices held
Allowed values>DOB, <=DOD
ExampleSergio 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
Descriptionsubject currently or formerly holds the object position or public office
Data typeItem
Template parameterVarious
DomainPersons
Allowed valuesPersons
ExamplePrime Minister of Italy (Q796897) => Matteo Renzi (Q47563) (as Matteo Renzi (Q47563) => Prime Minister of Italy (Q796897) is done by position held (P39))
SourceVarious
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
Descriptionperiod between elections for a parliament, council
Data typeNumber (not available yet)
Template parameterHier den Infobox-Parameter einfügen, falls es einen gibt. Beispiel: "Bevölkerung" (population) in en:template:infobox settlement
DomainBeispiel: General council (Q1398920), parliament (Q35749)
Allowed valuesArt der verlinkten Objekte (Q-Vorlage oder Text), eine Liste der möglichen Werte oder ein Wertebereich, Muster für Strings etc.
ExampleBeispiel: Q1398920 general council of a French department => election period in years => 6
SourceExterne Referenzen, Listenartikel in der Wikipedia (entweder Infobox oder Quelle)
Robot and gadget jobsFü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 byOursana (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
Descriptionorganization that founded another organization
Data typeItem
Domainorganization (Q43229)
Allowed valuesorganization (Q43229)
ExampleXavier University (Q1849843) => Society of Jesus (Q36380); White Violet Center for Eco-Justice (Q7995505) => Sisters of Providence of Saint Mary-of-the-Woods (Q3977434)
Sourceexternal reference, Wikipedia list article (either infobox or source)
Proposed bySweet 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
Descriptionchurch that belongs to this religion
RepresentsChristianity (Q5043)
Data typewikidata (example : Q9592)-invalid datatype (not in Module:i18n/datatype)
DomainQ templates
Allowed valuestext
ExampleVytautas (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)
Sourceréférence externe, article de liste de Wikipédia (soit infobox, soit source)
Proposed bygenium ⟨✉⟩
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 (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)
DescriptionID in the Naturbase database by the Norwegian Environment Agency
RepresentsNaturbase (Q11990971)
Data typeString
Template parameterno:Mal:Naturbase
Domainplaces (and possibly species)
Allowed valuesstring pattern [A-Z][A-Z]\d{8,8}
ExampleSkipsfjord conservation area (Q19323599) => VV00000090
Format and edit filter validation(sample: 7 digit number can be validated with edit filter Special:AbuseFilter/17)
Sourceno:Mal:Naturbase
Robot and gadget jobsMy bot can import values from nowiki and nnwiki
Proposed byJon 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

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

DescriptionAmount of central government debt divided by the GDP of the country
Data typenumber (percent)-invalid datatype (not in Module:i18n/datatype)
DomainCountries, regions and cities
Allowed valuesA positive percentage
Example87%
Sourcehttp://data.worldbank.org/indicator/GC.DOD.TOTL.GD.ZS
Robot and gadget jobsGlobal Economic Map Bot can do this
Proposed byMcnabber091 (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)

Flora of North America

DescriptionTaxonId in Flora of North America (Q1429295)
Representsplant (Q756)
Data typeString
Domainplant (Q756)
ExampleOrchidaceae (Q25308) => 10638
SourceFlora of North America (Q1429295) ([FNA])
Robot and gadget jobsAdd 'http://www.efloras.org/florataxon.aspx?flora_id=1&taxon_id=$1' to Gadget-AuthorityControl.js
Proposed bySuccu (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)

Descriptionmolecular formula of a class of compounds
Data typestring + string for n= + up to n items for R1 to Rn-invalid datatype (not in Module:i18n/datatype)
Domainmaybe family of isomeric compounds (Q15711994)
ExampleQ41581 => CnH2n+2, (n = 1, 2, 3, 4, ...)
Q2602701 => R¹R²C=N−R³ with R³ IS NOT hydrogen (Q556)
SourceExterne Referenzen, Listenartikel in der Wikipedia (entweder Infobox oder Quelle)
Proposed byKopiersperre (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

DescriptionIdentifier of a chemical, in The Merck index Online.
RepresentsThe Merck Index (Q663360)
Data typeString
Template parametern/a
Domainchemical elements or compounds
Allowed valuesURL stems from The Merck Index Online
ExampleD-ribofuranose (Q179271) => mono1500008328 => https://www.rsc.org/Merck-Index/monograph/mono1500008328
SourceThe Merck Index Online
Formatter URLhttps://www.rsc.org/Merck-Index/monograph/$1
Robot and gadget jobsPossible
Proposed byAndy 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)

number confirmed

Descriptionqualifier; number of occurrences classified as confirmed for reporting purposes
Data typeNumber (not available yet)
Template parameterNone yet.
Domaindisease outbreak (Q3241045)
Allowed valuesNon-negative integers
Example2014 Ebola virus epidemic in Liberia (Q18208679) number of cases 6,253, number confirmed 2,515
SourceHealth institutes, e.g. World Health Organization, US Centers for Disease Control and Prevention
Proposed byEmw (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

Descriptionqualifier for number of cases; number of occurrences classified as probable for reporting purposes
Data typeNumber (not available yet)
Template parameterNone yet.
Domaindisease outbreak (Q3241045)
Allowed valuesNon-negative integers
Example2014 Ebola virus epidemic in Liberia (Q18208679) number of cases 6,253, number probable 1,540
SourceHealth institutes, e.g. World Health Organization, US Centers for Disease Control and Prevention
Proposed byEmw (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

Descriptionqualifier for number of cases; number of occurrences classified as suspected for reporting purposes
Data typeNumber (not available yet)
Template parameterNone yet.
Domaindisease outbreak (Q3241045)
Allowed valuesNon-negative integers
Example2014 Ebola virus epidemic in Liberia (Q18208679) number of cases 6,253, number suspected 2,480
SourceHealth institutes, e.g. World Health Organization, US Centers for Disease Control and Prevention
Proposed byEmw (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)
Descriptionprimary case, patient zero: initial patient in the population of an epidemiological investigation
Data typeItem
Template parameterNone yet.
Domaindisease outbreak (Q3241045)
Allowed valueshuman (Q5)
ExampleThomas Eric Duncan (Q18249266) index case of Ebola virus disease in the United States (Q17486597)
SourceHealth institutes, e.g. World Health Organization, US Centers for Disease Control and Prevention
Proposed byEmw (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

Descriptionthe figure exposed when a corner of a polytope is sliced off.
Data typeItem
Template parameter"vertex figure" in en:template:Infobox_polyhedron and en:template:Infobox_polychoron
Domainvertex figure (Q598843)
Allowed valuespolytope (Q747980)
Examplecuboctahedron (Q847941) => rectangle (Q209), 600-cell (Q2610844) => icosahedron (Q188758), pentagon (Q127840) => line segment (Q166154) ,
Sourceinfoboxes
Robot and gadget jobsleeching infoboxes.
Proposed byopensofias (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
Nomen ad hoc
Lore.mazza51
Wikisaurus
The Anome
The-erinaceous-one
Daniel Mietchen
Haansn08
Xenmorpha
John Samuel
  Notified participants of WikiProject Mathematics
  Support -Tobias1984 (talk) 18:11, 8 October 2014 (UTC)

second image

   Not done
Descriptionвторая важная иллюстрация к теме
Data typeCommons media file
Template parameteren:Template:Taxobox: image2
ExampleGreen-tailed Sunbird (Q3238764) => Green tailed Sunbird.jpg
Proposed byTermininja (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

Descriptionlinks a property to its inverse property. Implements owl:inverseOf.
Representsinverse element (Q338057)
Data typeProperty
DomainWikidata property (Q18616576)
Allowed valuesany Wikidata property (Q18616576)
Examplepart of (P361) => has part (P527); shares border with (P47) => shares border with (P47)
Proposed byFilceolaire (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)

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
DescriptionSpecifies if a property is transitive, non-transitive, symmettric
Data typeitem,-invalid datatype (not in Module:i18n/datatype)
DomainItem
Allowed valuesTransitive, non-transitive, symmetric.
Examplefather (P22) => non-transitive. located in the administrative territorial entity (P131) => transitive. shares border with (P47) => symmetric
Format and edit filter validationallowed values only
Robot and gadget jobsno
Proposed byFilceolaire (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)
I have created several special items to fulfill this structural need:
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)
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 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)

family

Descriptionfamily of OS, e.g. Windows NT (Q486487) for Windows 7 (Q11215)
RepresentsWindows 7 (Q11215)
Data typeItem
Template parameteren:Template:Infobox OS family
DomainWindows 7 (Q11215), Linux (Q388), OS X Mountain Lion (Q63734), Mac OS 9 (Q904519), Windows 98 (Q483132), Windows Server 2012 (Q11222)
Allowed valuesWindows NT (Q486487), Unix-like (Q14656), macOS (Q14116), Macintosh operating systems (Q43627), Windows 9x (Q609733), Windows Server (Q11219)
ExampleWindows NT (Q486487)Windows 7 (Q11215)
Format and edit filter validation(образец: проверка на правильность 7-разрядного числа может быть осуществлена фильтром правок Special:AbuseFilter/17)
Sourceru:Ш:Карточка ОС
Proposed byDimon4ezzz (обс.)
Discussion

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

Tobias1984
Emw
Zuphilip
Danrok
Bene*
콩가루
TomT0m
DrSauron
Ruud Koot
Andreasburmeister
Ilya
Toto256
MichaelSchoenitzer
Metamorforme42
Pixeldomain
User:YULdigitalpreservation
Dipsode87
Daniel Mietchen
Jsamwrites
Tinker Bell
FabC
Jasc PL
putnik
Dhx1
Tris T7
Peb Aryan
lore.mazza004
Rc1959
Premeditated
Iwan.Aucamp
LiberatorG
Primhill.Computers
FWVH (passionné d'informatique et d'électronique)
94rain
So9q
Adrijaned
Sylvain Leroux
SM5POR
Haansn08
1-Byte
Luca.favorido
  Notified participants of WikiProject Informatics

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

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)
Descriptionbrand of a product
Representsbrand (Q431289)
Data typeItem
Domainproduct (Q2424752)
Allowed valuesinstances of brand (Q431289)
ExampleLevi's 501 (Q3237209) => Levi's (Q13085298), Mercedes-Benz W205 (Q15312688) => Mercedes-Benz (Q36008)
Proposed byPasleim (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
DescriptionDate a statute or another document enters in force
Data typePoint in time
ExampleBelgian Anti-Racism Law (Q2465867) : 1981-08-18
Proposed byDereckson (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
DescriptionOfficial date of a statute or another document, in most country the date the chief of state sigs the text
Data typePoint in time
ExampleBelgian Anti-Racism Law (Q2465867) : 1981-07-30
Proposed byDereckson (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
Descriptionhow long someone has been in office; how many times someone has been elected to office
Data typeNumber (not available yet)
Domainall positive rational integers
ExampleCongressman, President
Sourceexternal reference, Wikipedia list article (either infobox or source)
Proposed byTeleComNasSprVen (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
Descriptionhow long someone is in office for a single term
Data typePoint in time
ExampleCongressman, President (10 days, 4 years)
Sourceexternal reference, Wikipedia list article (either infobox or source)
Proposed byTeleComNasSprVen (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
DescriptionThe date of the official public closing
Data typePoint in time
DomainMuseums, other public buildings, Roller coasters, attractions
Allowed valuesdates
ExampleGamla bergbanan (Q10502454) => 20 September 1987)
SourceTemplate:Infobox attraction (Q13478527)
Proposed byabbedabbtalk
Discussion

Useful in infoboxes. I use it roller coaster templates abbedabbtalk 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
Descriptionperson employed to play a church's (or other building's, or occasionally event's) organ
Data typeItem
Template parameter"organist" in en:template:infobox church
Domaingeographic location (Q2221906) (place), organization (Q43229) (organization), event (Q1656682) (event)
Allowed valuespeople
ExampleSt James' Church (Q16908818) => Theodore Stephen Tearne (Q7782056)
SourceWikipedia infoboxes
Robot and gadget jobsA bot could import these, with date qualifiers where available.
Proposed byAndy 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
Descriptionbreed of animal
Data typeItem
Template parameter"breed" in en:template:infobox animal
Domainindividual animals
Allowed valuesanimal breeds
ExampleBo (Q1273495) => Portuguese Water Dog (Q38559)
SourceWikipedia
Proposed byAmaryllisGardener 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

Descriptiona Pokémon identification number
Data typeString
DomainAny 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)
Sourcein-game informations from the Pokémon Ranger games
Proposed byJu 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
DescriptionPokémon breeding in-game mechanism
Data typeItem
DomainAny Pokémon
Allowed valuesMonster 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>
Sourcein-game informations from the Pokémon games
Proposed byJu 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)

deaths

   Not done
Descriptionpeople which died because of this in a certain timescale
Data typeNumber (not available yet)
Domain(Taxons)
Examplealcoholism (Q15326), cancer (Q12078), Ebola hemorrhagic fever (Q51993)
Proposed byImpé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

DescriptionSmithsonian American Art Museum: person/institution thesaurus id
RepresentsSmithsonian American Art Museum person/institution ID (Q19186351)
Data typeString
Template parameternone.
Domainpersons, institutions
Allowed valuesdigits
ExampleAllan D'Arcangelo (Q4730556) -> 1121 (web, RDF)
Sourcehttp://americanart.si.edu/collections/search/lod/about/browse_artists.cfm
Formatter URLhttp://edan.si.edu/saam/id/person-institution/$1
Robot and gadget jobs
Proposed byVladimir 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)

@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

Descriptionentry of described object on Parlement & Politiek, website describing Dutch politic
RepresentsParlement & Politiek (Q14042250)
Data typeString
Domainperson, organisations, terms
Allowed values12 symbols
Example
Sourcehttp://www.parlement.com/
Formatter URLhttp://www.parlement.com/id/$1
Proposed bySjoerd 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 & Politiek 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

Descriptionatlas-patrimoine93 ID
Data typeString
Domainarchitectural structures, places
ExampleBasilica of Saint-Denis (Q184407) -> 066s021
Formatter URLhttp://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

DescriptionAccident description ID per the Aviation Safety Network's database
RepresentsAviation Safety Network accident description (Q19356096)
Data typeString
Domainaviation accident (Q744913)
ExampleTransAsia Airways Flight 235 (Q18951344) => Aviation Safety Network accident description ID => 20150204-0
Format and edit filter validation8 digit number followed by '-' and a final digit can be validated with edit filter
SourceASN Aviation Safety Database
Formatter URLhttp://aviation-safety.net/database/record.php?id=$1
Robot and gadget jobspossible
Proposed byJosh 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

DescriptionWikibase occurrence number per the Aviation Safety Network's database
RepresentsAviation Safety Network Wikibase Occurrence (Q19359000)
Data typeString
Domainaviation accident (Q744913)
ExampleYverdon-les-Bains Air Club crash (Q19360289) => Aviation Safety Network Wikibase Occurrence => 174061
Format and edit filter validation6 digit number can be validated with edit filter
SourceASN Aviation Safety WikiBase
Formatter URLhttp://aviation-safety.net/wikibase/wiki.php?id=$1
Robot and gadget jobspossible
Proposed byJosh 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)
DescriptionThesaurus numbers, used for (mainly) Dutch audiovisual archives, specifically the Netherlands Institute for Sound and Vision and EYE Film Institute.
Data typeString
DomainSubjects, Persons, Names, Locations, Genres and Makers
Allowed valuesa number of unspecified length
ExampleAndré van Duin (Q523644) => 95024
Format and edit filter validation\d+
SourceOfficial site (Dutch), Overview (English)
Proposed byHusky (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)

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)

denkXweb id

DescriptiondenkXweb 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.
RepresentsdenkXweb (Q19411765)
Data typeNumber (not available yet)
Template parameter"Nummer" in de:Vorlage:Denkmalliste Hessen Tabellenzeile, first field in commons:Template:Kulturdenkmal Hessen
Domaincultural heritage monuments located in Hesse
Allowed valuesinteger up to 999999 (max. 6 digits, range might change)
ExampleLimburg Cathedral (Q564957) => 53076
Formatter URLhttp://denkxweb.denkmalpflege-hessen.de/cgi-bin/mapwalk.pl?event=Query.Details&obj=$1
Robot and gadget jobsBots 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 byCirdan (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)

LMI code

Descriptionidentifier for Romanian heritage sites
Data typeString
Domainonly instances of historic monument (Q916620) ?
ExampleGrand Hôtel du Boulevard (Q3113619) -> B-II-m-A-18678
SourceCommons:Template:Monument istoric, ro:Category:Liste de monumente istorice din România
Discussion

Zolo (talk) 06:46, 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

DescriptionUnique 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 typeNumber (not available yet)
DomainColleges and universities in the United States. As of 2015-03-10, this is about 7500 institutions.
Allowed valuespositive integers of length 6
ExampleValparaiso University (Q186047) => 152600
SourceIPEDS 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)
DescriptionIdentifier in the Dutch Digitaal Vrouwenlexicon van Nederland (Online Dictionary of Dutch Women), a biography portal of prominent women in Dutch history.
RepresentsOnline Dictionary of Dutch Women (Q13135279)
Data typeString
Domainperson
Allowed valuesa string of text characters, often the person's (last) name
ExampleJudith Leyster (Q232423) => Leyster (http://resources.huygens.knaw.nl/vrouwenlexicon/lemmata/data/Leyster)
Sourcehttp://resources.huygens.knaw.nl/vrouwenlexicon
Formatter URLhttp://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
Descriptionidentifier in the Muséofile database about 1315 French museums
Data typeString
Domainmuseum (Q33506)
Allowed valuesM\d{1,4}
ExampleLouvre Museum (Q19675) => M5031
Sourcehttp://www.culture.gouv.fr/documentation/museo/index.htm
Formatter URLhttp://www.culture.gouv.fr/public/mistral/museo_fr?ACTION=CHERCHER&FIELD_98=REF&VALUE_98=$1
Proposed byAyack (talk) at 17:34, 18 March 2015‎
Discussion
@Ayack: it already exists: Museofile (P539). --Zolo (talk) 13:54, 24 March 2015 (UTC)

non-free file URL

   Not done
DescriptionLike image (P18), but for non-free files.
Data typeURL
Domainall
Allowed values
  • .jpg, png, ...
Example24 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 byGZWDer (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
DescriptionFor use in a statement on a property, whose values are an ordering key
Representscollation (Q10513350)
Data typeBoolean-invalid datatype (not in Module:i18n/datatype)
DomainProperties
Allowed valuestrue, false
Examplepoint in time (P585) → true
Robot and gadget jobsAutomatic ordering of orderable claims and claims with orderable qualifiers upon insertion
Proposed byPetr Matas
Discussion

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

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

ordering key

   Not done
DescriptionIndicates, which qualifier should be used as a preferred ordering key for multiple statements with this property
Representscollation (Q10513350)
Data typeProperty
DomainAll properties
Allowed valuesAll properties
Examplesignificant event (P793)point in time (P585)
Robot and gadget jobsAutomatic ordering of claims with orderable qualifiers upon insertion
Proposed byPetr 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
DescriptionReverse of candidate (P726).
Data typeItem
Domainperson, party
Allowed valueselection
ExampleRajmohan Gandhi (Q734521)=>2014 Indian general election (Q3587169)
Robot and gadget jobsYes
Proposed byGZWDer (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)

DescriptionFormat for this specific property or item, defined by a regex
Data typeString
Template parameterTemplate:Constraint:Format, even Template:Property documentation
Domainproperties, possibly other items
Allowed valuesregular expressions
ExampleProperty: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
Descriptionlist properties used by a given WikiProject
Data typeProperty
DomainWikiProjects
Allowed valuesany property
ExampleWikiProject France (Q10816832): INSEE municipality code (P374), etc.
Sourcelists 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)
DescriptionProportional ratio of a linear dimension of a model to the same feature of the original
Representsscale (Q10858537)
Data typenumber?-invalid datatype (not in Module:i18n/datatype)
Template parameter"ratio" in w:en:Infobox model rail scale, possibly others
Domainmodel 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 values1:n (for smaller than lifesize), 1:1 (for lifesize), n:1 (for larger than lifesize). n is a decimal number
ExampleScalextric (Q1683328) 1:32, HO scale (Q911411) 1:87.1
Format and edit filter validation?
Sourceexternal reference, Wikipedia list article (either infobox or source)
Robot and gadget jobsNot aware of any, but bots could collect data from infoboxes
Proposed byThryduulf (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

DescriptionA list article corresponding to the membership of this category.
RepresentsWikimedia list article (Q13406463)
Data typeItem
DomainWikimedia category (Q4167836)
Allowed valuesan instance of a subclass of Wikimedia list article (Q13406463)
ExampleCategory:Geographers (Q7233691) => list of geographers (Q3243996)
Format and edit filter validationThe 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
SourceWikimedia categories
Robot and gadget jobsSome 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 byJheald (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

DescriptionA list article corresponding to the membership of this category.
RepresentsWikimedia category (Q4167836)
Data typeItem
DomainWikimedia list article (Q13406463)
Allowed valuesan instance of a subclass of Wikimedia category (Q4167836)
Examplelist of geographers (Q3243996) => Category:Geographers (Q7233691)
Format and edit filter validationThe 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
SourceWikimedia lists
Robot and gadget jobsSome 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 byJheald (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
Descriptionlinks two entities that represent related concepts
Data typeItem
Domainitems (concepts)
Allowed valuesitems (concepts)
Example
Proposed byProgVal (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
DescriptionMotto or slogan of organisation
Data typemonolingual-invalid datatype (not in Module:i18n/datatype)
Template parametermotto in en:Template:Infobox organization
Domaingeographic location (Q2221906) (place), organization (Q43229) (organization), event (Q1656682) (event)
Allowed valuestype of linked items (Q template or text), list or range of allowed values, string pattern...
ExampleThurmont (Q755596) → "...Gateway to the Mountains"; McDonald’s (Q38076) → "i’m lovin’ it"; Eurovision Song Contest 2014 (Q5354210) → "#JoinUs"
Sourceexternal reference, Wikipedia list article (either infobox or source)
Proposed byZellfaze (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 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
Descriptiondescribes a military/paramilitary/police element like squad, platoon, unit, unit collection or any other administrative division
Data typeItem
Template parameternicht bekannt
Domainbarracks (Q131263), military base (Q245016), warship (Q3114762), airbase (Q695850), real property (Q684740), Terrorist training camp (Q2405521)
Allowed valuesBeispiele: 1. Panzerdivision, Bundeswehrzentralkrankenhaus Koblenz, Qassam-Brigaden, Eighth Air Force, Provincial Reconstruction Team
ExampleMudra barracks (Q15121187) => Federal Office of Personnel Management of the Bundeswehr (Q1005474), Mudra barracks (Q15121187) => Personalamt der Bundeswehr (Q575684)
Format and edit filter validationnicht bekannt
SourceExterne Referenzen, Listenartikel in der Wikipedia (entweder Infobox oder Quelle)
Robot and gadget jobsnicht bekannt
Proposed byJotpe (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

DescriptionThe chief operating officer of an organization.
Representschief operating officer (Q623279)
Data typeItem
Domainorganization (Q43229)
Allowed valuesPeople
ExampleFacebook (Q355) => Sheryl Sandberg (Q234653), Duck Commander (Q15631659) => Jase Robertson (Q14755553), Heaven Sent Gaming (Q17275459) => Isabel Ruiz Lucero (Q17275427),
SourceOfficial website or reliable third party sources
Proposed byDunDunDunt (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
DescriptionAmount of goods and services bought from other countries in a year divided by theGDP of that country in that year
Data typeNumber (not available yet)
DomainCountries
Allowed valuesPositive percentage numbers
Example17%
Robot and gadget jobsGlobal Economic Map Bot can do this
Proposed byMcnabber091 (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

Descriptioncode of industry by ISIC (International Standard Industrial Classification of All Economic Activities)
Data typeString
Domainindustry (Q8148) (industry)
Allowed valuesSectional level: [A-U], divisional level: two digits, class level: four digits
Exampleaerospace industry (Q3477363) => 3030
Sourcehttp://unstats.un.org/unsd/cr/registry/isic-4.asp
Proposed byBezik (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

DescriptionA gallery or art collection, in the YourPaintings database
Data typeString
DomainArt galleries, museums, organisations, collections, etc.
ExampleHereford 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 )
Sourcehttp://www.bbc.co.uk/arts/yourpaintings/galleries/
Robot and gadget jobsformatterURL: http://www.bbc.co.uk/arts/yourpaintings/galleries/collections/$1
Proposed byAndy 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

DescriptionIdentifier in National Pipe Organ Register (Q19294701), operated by British Institute of Organ Studies (Q4970119).
Data typeString
Template parameterUsed in en:Template:National Pipe Organ Register (recently created)
DomainChurches, theatres, civic halls, etc.
Allowed valuesNumbers prefixed by letters
ExampleChurch of St George (Q19239882) => N06500
SourceNational Pipe Organ Register
Robot and gadget jobspossible
Proposed byAndy 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

Descriptionidentification code in the database of the Flemish organization for Immovable Heritage
RepresentsFlanders Heritage Agency (Q3262326)
Data typeNumber (not available yet)
Domaincultural heritage (Q210272)
Allowed values0-9999999
ExampleSaint Peter's Abbey (Q1170767) => 21199 resolves to https://inventaris.onroerenderfgoed.be/dibe/relict/21199
Formatter URLhttps://inventaris.onroerenderfgoed.be/dibe/relict/$1
Robot and gadget jobsbots could check whether the object exists at https://inventaris.onroerenderfgoed.be/dibe/relict/$1
Proposed byFranklyMyDear... (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

Descriptionthe Hornbostel-Sachs classification of this instrument
RepresentsHornbostel–Sachs (Q496327)
Data typeString
Template parameterhornbostel_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
Domainmusical instrument (Q34379)
Allowed valuesstring containing 0-9.-+
Exampleaerophone (Q659216) => 4, reed aerophone (Q3152896) => 422, trumpet (Q8338) => 423.233, ocarina (Q187780) => 421.221.42, castanets (Q183932) => 111.141
Sourceinfoboxes, en:Category:Lists_of_musical_instruments_by_Hornbostel-Sachs_number
Robot and gadget jobsbots could migrate values from infoboxes
Proposed byNikki (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

DescriptionWikipedia category for people with a burial site within this area
Representslocation of burial (Q18857007)
Data typeItem
Template parameterburial place (categorization)
Domaingeographical feature (Q618123)
Allowed valuesWikimedia category (Q4167836)
ExampleMinsk (Q2280)Category:Burials in Minsk (Q7976974)
SourceWikipedia 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 of people buried here (P1791). Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 14:34, 22 March 2015 (UTC)

Category of associated people

DescriptionWikipedia category for people associated with this area
Data typeItem
Domaingeographical feature (Q618123)
Allowed valuesWikimedia category (Q4167836)
ExampleMinsk (Q2280)Category:People from Minsk (Q8808730)
SourceWikipedia 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
DescriptionSpatial location related to another location (e.g. a city) that might be of interest (e.g. a tourist attraction)
Representspoint of interest (Q960648)
Data typeItem
Domainplace of interest, typically for its inherent or exhibited natural or cultural value
Allowed valuesitems located in the given item, for example museums, monuments, natural attractions like parks and beaches
ExampleAmsterdam (Q727) => Rijksmuseum (Q190804), Vondelpark (Q1419691), Grachtengordel (Q478707)
Proposed byHusky (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
DescriptionThe Lua table containing the data about the location maps for the area
Data typeItem
Template parameter(could replace some map-related parameters in some infoboxes)
Domainplaces
Allowed valuesinstances of map data module (Q18711811)
ExampleUnited States of America (Q30) -> Module:Location map/data/United States (Q16853427)
Proposed byZolo (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

Descriptionimage of road sign with place name on it
Representstown sign (Q266488)
Data typeCommons media file
Domaingeographic locations
Allowed valuesimages
ExampleOld Appleton (Q963346) = File:Old Appleton, Missouri, Road sign.jpg
Robot and gadget jobsCould 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)
DescriptionISO 639-5 code for a language family
RepresentsISO 639-5 (Q2455758)
Data typeString
Template parameteriso5 in w:en:Template:Infobox language family, iso5 in w:fr:Template:Infobox Langue
Domainlanguage family (Q25295)
Allowed values3 lowercase letters
ExampleGreek (Q9129) => grk, Algic languages (Q721612) => aql
Sourcew:en:List of ISO 639-5 codes
Proposed byVisite 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)
Descriptionday 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).
Representsname day (Q216584)
Data typeItem
Template parameter"name day" in en:Template:Infobox given name, "fête" in fr:Modèle:Infobox Prénom,
Domainitems for given names, first names
Allowed valuesitems for specific days of the year
ExampleLucy (Q17379191) = December 13 (Q2379)
Sourceinfobox

Ash Crow
Dereckson
Harmonia Amanda
Hsarrazin
Jura
Чаховіч Уладзіслаў
Sascha
Joxemai
Place Clichy
Branthecan
Azertus
ToJack
Jon Harald Søby
PKM
Pmt
Sight Contamination
MaksOttoVonStirlitz
BeatrixBelibaste
Moebeus
Dcflyer
Looniverse
Aya Reyad
Infovarius
Tris T7
Klaas van Buiten
Deborahjay
Bruno Biondi
Tokyo Akademia
ZI Jony
Laddo
Da Dapper Don
Data Gamer
Franzsimon
Arturo2R
Luca favorido
The Sir of Data Analytics
Skim
E4024
Joeykentin
  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
DescriptionThe amount donated to a political party
Data typeNumber (not available yet)
Template parametern/a
DomainPersons
Allowed valuesintegers
Examplesample 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)
Sourcee.g Electoral Commission http://www.electoralcommission.org.uk/
Robot and gadget jobsYes, can be a job.
Proposed byBattleofalma (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)
DescriptionAuthor identifier, in the BioStor database and archive of journal articles
Data typeString
Template parameterTends to be in external links or references on Wikipedia
DomainPeople, possibly groups, companies etc.
Allowed valuesStems of BioStor author URLs
ExampleJohn Eleuthère du Pont (Q3655973) => 69822
SourceWikipedia; BioStor
Formatter URLhttp://biostor.org/author/$1
Robot and gadget jobsPossible
Proposed byAndy 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)

@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
DescriptionThis property, as particular case of see also (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). see also (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 typeItem
Domainperson (Q215627)
Allowed valuesany element in the domain person (Q215627)
Exampleexample 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.
SourceA 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 jobsvalidation (only other item should be accepted)
Proposed byNastoshka (talk)
Discussion

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

original airdate

   Not done
Descriptiondate 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 typePoint in time
Template parameter"Airdate" in en:template:infobox television episode
Domainepisode (Q1983062), television film (Q506240), but certainly not restricted to those
Allowed valuesas precise as possible, but allowed to vary by region of airing
ExampleSmoked (Q7545917) => 2011-05-18
Sourceen:template:infobox television episode
Proposed byMahir256 (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
DescriptionOriginal title of a work
Data typeMonolingual text
Template parameter"title_orig" in en:template:infobox book
Domainfilmmaking, television production, novel, video game, or music album
Allowed valuesall
ExampleCzterej pancerni i pies (Q990) => Czterej pancerni i pies (when English id Four tank-men and a dog)
Proposed byRezonansowy (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: CiNii book ID (P1739) (Talk and documentation)
DescriptionIdentifier for books, in the Japanese CiNii (Q10726338) bibliography. AKA NCID
Data typeString
Template parametern/a
DomainBooks
ExampleThe 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)
SourceCiNii (Q10726338)
Formatter URLhttp://ci.nii.ac.jp/ncid/$1
Robot and gadget jobsPossible
Proposed byAndy 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 CiNii author ID (books) (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

DescriptionReference 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 typeString
Template parametern/a
DomainLepidoptera (Q28319) species of the United Kingdom
Allowed valuesIntegers below 2500; or the same suffixed with a lower-case letter.
ExampleIncurvaria praelatella (Q1355083) -> 132; Saturnia pyri (Q265918) -> 1643a
SourceOp. Cit.; also [3]
Robot and gadget jobsPossible
Proposed byAndy 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

DescriptionReference 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 typeString
Template parametern/a
DomainLepidoptera (Q28319) species of the United Kingdom
Allowed valuesTwo integers separated by a decimal point; the first integer being maximum two digits; the second four digits
ExampleIncurvaria praelatella (Q1355083) -> 8.004; Saturnia pyri (Q265918) -> 68.0011
SourceOp. Cit.; also [4]
Robot and gadget jobsPossible
Proposed byAndy 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)
Descriptionidentifiant of the Database of Vascular Plants of Canada (Canada, Greenland dans Saint-Pierre-et-Miquelon)
RepresentsTracheophyta (Q27133)
Data typeString
DomainTaxons
Allowed valuesnumber
ExamplePicea mariana (Q218425) --> 7174
Sourcehttp://data.canadensys.net/vascan/search
Proposed byFralambert (talk)
Discussion

99of9
Achim Raschka (talk)
Andrawaag (talk)
Brya (talk)
CanadianCodhead (talk)
Canley
Circeus
Dan Koehl (talk)
Daniel Mietchen (talk)
Enwebb
Faendalimas
FelixReimann (talk)
Hyperik (talk)
Infomuse (talk)
Infovarius (talk)
Jean-Marc Vanel
Joel Sachs
Klortho (talk)
Lymantria (talk)
Magnefl (talk)
MPF
Manojk
MargaretRDonald
Mellis (talk)
Michael Goodyear
Mr. Fulano (talk)
Myrmoteras (talk)
Nis Jørgensen
Oronsay
PEAK99
Peter Coxhead
PhiLiP
Andy Mabbett (talk)
Plantdrew
Prot D
pvmoutside
RaboKarbakian
Rod Page
Strobilomyces (talk)
Stuchka (talk)
Succu (talk)
TiagoLubiana (talk)
Tinm
Tom.Reding
TomT0m
Tommy Kronkvist (talk)
Tris T7 TT me
Tubezlob
William Avery
Minorax
Culex
Koala0090
Mike Krüger
Friesen5000
Salgo60
TED
GoEThe (talk)
Estopedist1
Leptospira
Melissadilara
  Notified participants of WikiProject Taxonomy 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
DescriptionID of the National Plant Germplasm System - GRIN Taxonomy for Plants
Data typeString
Domainplant taxons
ExampleSairocarpus nuttallianus => 456783
Sourcehttp://www.ars-grin.gov
Proposed byMinerv (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:

-( 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

Descriptionidentifier for nomenclatural act at ZooBank
Representsscientific name (Q15730631)
Data typeString
Domainzoology (Q431), ZooBank (Q8074026)
ExampleAmargastegos (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}$
Sourcehttp://zoobank.org/
Formatter URLhttp://zoobank.org/NomenclaturalActs/$1
Proposed bySuccu (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) 99of9
Achim Raschka (talk)
Andrawaag (talk)
Brya (talk)
CanadianCodhead (talk)
Canley
Circeus
Dan Koehl (talk)
Daniel Mietchen (talk)
Enwebb
Faendalimas
FelixReimann (talk)
Hyperik (talk)
Infomuse (talk)
Infovarius (talk)
Jean-Marc Vanel
Joel Sachs
Klortho (talk)
Lymantria (talk)
Magnefl (talk)
MPF
Manojk
MargaretRDonald
Mellis (talk)
Michael Goodyear
Mr. Fulano (talk)
Myrmoteras (talk)
Nis Jørgensen
Oronsay
PEAK99
Peter Coxhead
PhiLiP
Andy Mabbett (talk)
Plantdrew
Prot D
pvmoutside
RaboKarbakian
Rod Page
Strobilomyces (talk)
Stuchka (talk)
Succu (talk)
TiagoLubiana (talk)
Tinm
Tom.Reding
TomT0m
Tommy Kronkvist (talk)
Tris T7 TT me
Tubezlob
William Avery
Minorax
Culex
Koala0090
Mike Krüger
Friesen5000
Salgo60
TED
GoEThe (talk)
Estopedist1
Leptospira
Melissadilara
  Notified participants of WikiProject Taxonomy

  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

DescriptionTaxonId in Flora of China (Q5460442)
Representsplant (Q756)
Data typeString
Domainplant (Q756)
ExampleOrchidaceae (Q25308) => 10638
Format and edit filter validation[1-9]\d{4,9}
SourceFlora of China (Q5460442) (FOC)
Formatter URLhttp://www.efloras.org/florataxon.aspx?flora_id=2&taxon_id=$1
Proposed bySuccu (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) 99of9
Achim Raschka (talk)
Andrawaag (talk)
Brya (talk)
CanadianCodhead (talk)
Canley
Circeus
Dan Koehl (talk)
Daniel Mietchen (talk)
Enwebb
Faendalimas
FelixReimann (talk)
Hyperik (talk)
Infomuse (talk)
Infovarius (talk)
Jean-Marc Vanel
Joel Sachs
Klortho (talk)
Lymantria (talk)
Magnefl (talk)
MPF
Manojk
MargaretRDonald
Mellis (talk)
Michael Goodyear
Mr. Fulano (talk)
Myrmoteras (talk)
Nis Jørgensen
Oronsay
PEAK99
Peter Coxhead
PhiLiP
Andy Mabbett (talk)
Plantdrew
Prot D
pvmoutside
RaboKarbakian
Rod Page
Strobilomyces (talk)
Stuchka (talk)
Succu (talk)
TiagoLubiana (talk)
Tinm
Tom.Reding
TomT0m
Tommy Kronkvist (talk)
Tris T7 TT me
Tubezlob
William Avery
Minorax
Culex
Koala0090
Mike Krüger
Friesen5000
Salgo60
TED
GoEThe (talk)
Estopedist1
Leptospira
Melissadilara
  Notified participants of WikiProject Taxonomy

@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

DescriptionfamilyID in Watson & Dallwitz: The families of flowering plants
Data typeString
Domainplant families
ExampleCaryophyllaceae (Q25995) => caryophy
SourceL. Watson and M.J. Dallwitz (1992 onwards). The families of flowering plants: descriptions, illustrations, identification, and information retrieval. http://delta-intkey.com
Formatter URLhttp://delta-intkey.com/angio/www/$1.htm
Proposed byBrya
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. 99of9
Achim Raschka (talk)
Andrawaag (talk)
Brya (talk)
CanadianCodhead (talk)
Canley
Circeus
Dan Koehl (talk)
Daniel Mietchen (talk)
Enwebb
Faendalimas
FelixReimann (talk)
Hyperik (talk)
Infomuse (talk)
Infovarius (talk)
Jean-Marc Vanel
Joel Sachs
Klortho (talk)
Lymantria (talk)
Magnefl (talk)
MPF
Manojk
MargaretRDonald
Mellis (talk)
Michael Goodyear
Mr. Fulano (talk)
Myrmoteras (talk)
Nis Jørgensen
Oronsay
PEAK99
Peter Coxhead
PhiLiP
Andy Mabbett (talk)
Plantdrew
Prot D
pvmoutside
RaboKarbakian
Rod Page
Strobilomyces (talk)
Stuchka (talk)
Succu (talk)
TiagoLubiana (talk)
Tinm
Tom.Reding
TomT0m
Tommy Kronkvist (talk)
Tris T7 TT me
Tubezlob
William Avery
Minorax
Culex
Koala0090
Mike Krüger
Friesen5000
Salgo60
TED
GoEThe (talk)
Estopedist1
Leptospira
Melissadilara
  Notified participants of WikiProject Taxonomy. - 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)
DescriptionID in USDA Plants
Data typeString
Domainplants
ExamplePseudotsuga menziesii (Q156687) => PSME
SourceUSDA Plants Database
Formatter URLhttp://plants.usda.gov/core/profile?symbol=$1
Proposed byBrya
Discussion

As we already have VASCAN, it would make sense to also have its big brother. - Brya (talk) 06:39, 12 March 2015 (UTC) 99of9
Achim Raschka (talk)
Andrawaag (talk)
Brya (talk)
CanadianCodhead (talk)
Canley
Circeus
Dan Koehl (talk)
Daniel Mietchen (talk)
Enwebb
Faendalimas
FelixReimann (talk)
Hyperik (talk)
Infomuse (talk)
Infovarius (talk)
Jean-Marc Vanel
Joel Sachs
Klortho (talk)
Lymantria (talk)
Magnefl (talk)
MPF
Manojk
MargaretRDonald
Mellis (talk)
Michael Goodyear
Mr. Fulano (talk)
Myrmoteras (talk)
Nis Jørgensen
Oronsay
PEAK99
Peter Coxhead
PhiLiP
Andy Mabbett (talk)
Plantdrew
Prot D
pvmoutside
RaboKarbakian
Rod Page
Strobilomyces (talk)
Stuchka (talk)
Succu (talk)
TiagoLubiana (talk)
Tinm
Tom.Reding
TomT0m
Tommy Kronkvist (talk)
Tris T7 TT me
Tubezlob
William Avery
Minorax
Culex
Koala0090
Mike Krüger
Friesen5000
Salgo60
TED
GoEThe (talk)
Estopedist1
Leptospira
Melissadilara
  Notified participants of WikiProject Taxonomy

  •   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

DescriptionNCI 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.
RepresentsNCI Thesaurus (Q19404626)
Data typeString
DomainDiseases
Allowed valuesalphanumeric
ExampleCornelia de Lange syndrome (Q1133289)=>C75016
Sourcehttp://ncit.nci.nih.gov/ncitbrowser/ConceptReport.jsp?dictionary=NCI_Thesaurus&version=14.10d&code=C75016
Robot and gadget jobsShould or are bots or gadgets doing any task with this? (Checking other properties for consistency, collecting data, etc.)
Proposed byAndrawaag (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)

@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
DescriptionPSGC (Philippines Standard Geographic Code) for location – region code + province code + city / municipality code + barangay code
Data typeString
Template parameterNothing preset, but usually uses |blank1_name_sec1= and |blank1_info_sec1= in en:template:infobox settlement e.g. see en:Bogo, Cebu
Allowed values99 = 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
Exampleen: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
Sourceexternal 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)


property used in this template

   Withdrawn
Descriptionlist properties used in a given template
Data typeProperty
Domaintemplates
Allowed valuesany property
ExampleTemplate:Infobox person (Q6249834): date of birth (P569), date of death (P570), etc.
Sourcetemplates at Wikipedia
Discussion

Illustrate usage of properties --- Jura 05:45, 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
Descriptionqualifier for alpabetical codes containing the corresponding numerical value
Data typeString
Allowed values\d+
Exampleeuro (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)
  •   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
DescriptionThe ids as used by KulturNav, a common site for ontologies used within the cultural sector in Norway and Sweden.
Data typestring (really an ID but we don't have anything like that)-invalid datatype (not in Module:i18n/datatype)
DomainThing (Item)
Allowed valuesstring (ref to dataset)
Example 1MISSING
Example 2MISSING
Example 3MISSING
Format and edit filter validationUUID
Sourcehttp://kulturnav.org/2b94216b-f2fc-46a3-b2ce-eeb93aa19185?format=application/rdf%2Bxml (several other formats exists)
Formatter URLhttp://kulturnav.org/$1
Robot and gadget jobsManuel 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)

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

Drainage basin

   Not done
Descriptionbasin drained by a river and its tributaries which this item is within
Representsdrainage basin (Q166620)
Data typeItem
Domainriver (Q4022)
Allowed valuesinstances under drainage basin (Q166620)
ExampleAmazon (Q3783) => drainage basin => Amazon basin (Q244451)
Xingu River (Q49544) => drainage basin => Amazon basin (Q244451)
Robot and gadget jobspossible
Proposed byJosh 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)

  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
Descriptionmeaning in the narrow sense
Data typequalifier-invalid datatype (not in Module:i18n/datatype)
Domainorganism (Q7239), fossil (Q40614), but also other things
Allowed valuesorganism (Q7239), fossil (Q40614), but also other things
ExampleSensu stricto meaning of Alum is Potassium alum (Q190527 -> Q411309), In a restrictive sense bryophyte means moss (Q29993 -> Q25347)
Proposed byKopiersperre (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
DescriptionNumber of locations the company has physical properties.
Data typeNumber (not available yet)
Template parameter"locations" in en:template:infobox company
Domainrestaurants, chains
Allowed valuesquantities
ExampleRed Lobster (Q846301) => 705
Proposed byAmaryllisGardener 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

DescriptionThe person or organisation that investigated/is investigating the event
Data typeItem
Template parameter?
Domainevents that are investigated, e.g. transportation accidents, crimes, etc
Allowed valuesorganisations, people
Example
SourceWikipedia 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)

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

disputed author

   Not done
DescriptionFor old works the author often is not known but only ascribed.
Data typeItem
Domainwritten works
Allowed valuesmultiple items (which have to be humans)
ExampleHippias Major (Q634846), First Alcibiades (Q1153509) -> Plato is the disputed author but not the author
Proposed byMischa004 (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)
  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)