Open main menu

Wikidata:Property proposal/Archive/31

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

Contents

memorial location

   Withdrawn
Descriptionlocation of memorial to this person or event
Data typeitem, coordinate-invalid datatype (not in Module:i18n/datatype)
Domainpeople, events
Allowed valuesplaces, coordinates
ExampleMarchioness disaster (Q6757026)Southwark Cathedral (Q922967)
SourceWikipedia articles
Motivation

Improving the entry for Marchioness disaster (Q6757026) I found this is apparently missing. We have the location of graves, but not memorials that I can find. Notable memorials can reference the event they commemorate, but this doesn't work for memorials to notable events that are not individually notable. Thryduulf (talk: local | en.wp | en.wikt) 00:42, 3 May 2015 (UTC)

Discussion

measured by

   Done: measured by (P1880) (Talk and documentation)
Descriptionfor a quantity, unit or concept that specific instruments have been developed to measure
Data typeItem
Examplepsychopathy (Q366886) => Hare Psychopathy Checklist (Q1033930), Levenson Self-Report Psychopathy Scale (Q6535196)
Proposed byAntrocent (talk)
Discussion

I am interested in personality and structuring what personality traits are measured by what tests could be useful. Antrocent (talk) 18:19, 21 January 2015 (UTC)

area

This was approved nearly two years ago. How long does it take to get a number? Too long. -- Unbuttered Parsnip (talk) 10:40, 31 March 2015 (UTC)

@Unbuttered Parsnip: The developers have to create a new datatype for that kind of property first, so it can take some time. -- Innocent bystander (talk) 11:14, 31 March 2015 (UTC)
(a) it's a number
(b) it's been nearly two years
(c) there are about half a million pages waiting for it. -- Unbuttered Parsnip (talk) 13:26, 31 March 2015 (UTC)
It is not just a number, unit properties are a good deal more complex than the existing number datatype. I have several things on hold awaiting this development, but there is a lot on the development plate. Josh Baumgartner (talk) 22:32, 2 April 2015 (UTC)

vice-county

   Done: vice-county (P1887) (Talk and documentation)
DescriptionThe Watsonian (British Isles, except Ireland) or Praeger (Ireland) Vice-county in which the place is located, for the purposes of biological recording.
Data typeItem
Template parameterna
Domaingeographic location (Q2221906) (place), in the w:British Isles.
Allowed valuesinstances of vice-county (Q7925010)
ExampleSandwell Valley RSPB reserve (Q7417062) => Staffordshire (Q17581852)
Format and edit filter validationinstances of vice-county (Q7925010)
Sourcevarious external lists and publications
Robot and gadget jobsPossibly, based on coordinates, avoiding edges of vice-counties, or from Wikipedia or other lists
Proposed byAndy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits
Discussion

Note: I've been using located in the administrative territorial entity (P131), but that's a kludge, and Vice-counties are not used for administrative purposes. Not to be copnfused with traditional or modern administrative counties (which often have the same names). Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 20:19, 4 September 2014 (UTC)

  Comment @Pigsonthewing: I am not sure your proposition seem different of P1134 (P1134). --Fralambert (talk) 19:47, 7 September 2014 (UTC)
That's been obsoleted in favour of located on terrain feature (P706); WVCs are notional, not "terrain features". Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 20:47, 6 March 2015 (UTC)
located on terrain feature (P706) doesn't fit, but location (P276)? --Pasleim (talk) 06:58, 26 April 2015 (UTC)
  •   Support, but please find a label that doesn't associate it with country (P17) (example: "biological vice-country in the British Isles" or "Watsonian/Praeger vice country"). --- Jura 11:24, 27 April 2015 (UTC)

  Done. @Pigsonthewing, Fralambert, Pasleim, Jura1: Josh Baumgartner (talk) 16:56, 14 May 2015 (UTC)

Income classification (Philippines)

DescriptionClassification is a set of bands for each of municipality / city > province. Range is 1 - 6. Actual classification is a combination of average revenue, population and area. It is determined by Philippine National Statistics Coordination Board (NCSB) with reference from Bureau of LGU Finance
Data typeNumber (not available yet)
Template parameterNot currently fixed within infobox settlement although |blank_name_sec1= and |blank_info_sec1= are frequently used
Domain(P17 = Philippines Q928) .and. (P31 with instance {municipality Q24764, or city Q515, or province Q24746})
Allowed valuessingle numeric digit range 1 to 6
ExampleUbay (Q406015) => 1st class municipality
Format and edit filter validationnot at this stage
SourceMunicipality income class; City income class; Province income Class.
Robot and gadget jobsnot yet
Discussion

Motivation:

Proposed by: Unbuttered Parsnip (talk)

An official dimension of Philippine settlement classification currently missing Unbuttered Parsnip (talk) 06:15, 29 March 2015 (UTC)

  •   Oppose. I think this would be better to create an item for each of these 6 classifications and link to them using instance of (P31) so we have "Ubay (Q406015):instance of (P31):Class 1 filipino settlement". Filceolaire (talk) 20:35, 10 April 2015 (UTC)
  •   Support This is a well-defined classification; there is no need to clutter up the instance of (P31) statement with this. Having its own property for statements would make it very clear, easy to use, and easy to get the data from. Josh Baumgartner (talk) 17:06, 20 April 2015 (UTC)
  •   Support too technical for P31. --- Jura 23:28, 20 April 2015 (UTC)
  •   Support, but with a datatype of "item"; and an item for each of the six types. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 21:04, 24 April 2015 (UTC)
  •   Support with datatype "item" --Pasleim (talk) 07:37, 26 April 2015 (UTC)

LinkedIn Company Page ID

   Not done
DescriptionThis is the unique identifier of a company page on LinkedIn, providing access to the social media page of the company, as well as official information and jobs from the company.
Data typenombre-invalid datatype (not in Module:i18n/datatype)
Domainorganization (Q43229) (organisation)
Allowed valuesnumber
ExampleIBM (Q37156) => 1009
Format and edit filter validationonly digits, a check can be performed using the url of the page
Sourcehttps://www.linkedin.com/
Formatter URLhttps://www.linkedin.com/company/$1
Proposed byTeolemon (talk)
Discussion

Motivation: As part of the Job and Occupations Task Force, to improve linked data around companies and jobs. I've just done the same for Glassdoor as well.Teolemon (talk) 08:25, 14 October 2014 (UTC)

@Jakec:. Though it may seem more consistent with other things, p553:Linkedin, P554: would not tell that this is a company identifier and that the URL should containt "/company". I guess a separate property would be needed (well, I would be in favor of replacing P553 with "Facebook account" et al. properties anyway). --Zolo (talk) 08:48, 19 October 2014 (UTC)
@Zolo: one can use not "p553:Linkedin", but some "p553:Linkedin Company Page", thus any bot/gadget will understand how URL could be constructed. -- Vlsergey (talk) 11:52, 13 May 2015 (UTC)
  Comment Is this code widely using on business? --Liuxinyu970226 (talk) 10:36, 10 January 2015 (UTC)
@Teolemon: Do you wish to comment on the above? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 18:40, 6 March 2015 (UTC)

  Not done No support. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 19:02, 8 May 2015 (UTC)

applies to taxon

   Not done
DescriptionUsed as qualifier. see Wikidata:Chemistry_task_force/Properties & Wikidata:Molecular_biology_task_force/Properties.
Data typeItem
Domainchemicals
Allowed valuestaxa
Examplesee the example above.
Proposed byGZWDer (talk)
Discussion

Motivation. GZWDer (talk) 15:39, 1 December 2013 (UTC)

Motivation? Example? --Succu (talk) 16:56, 1 December 2013 (UTC)
mercuric chloride (Q143200)<lethal dose>41 mg/kg with qualifier taxon=rabbit (Q9394), route of administration (P636)=dermal, specifically=median lethal dose (Q711849).--GZWDer (talk) 05:18, 2 December 2013 (UTC)
Why not just use taxon name (P225)? - Brya (talk) 03:53, 4 December 2013 (UTC)
I think P225 is not senseful - instead of a plain string, it should of course connect to the item (aka concept). Nonetheless - I'm not sure if a new taxonomic-specific property is required which itself is used only as qualifier but not used as property in the taxonomic model itself. Either, you could use P89 (P89) which we already have or - what I propose - an even more general property - for example something like "applied to". But I have to confess that I do not see the overall Wikidata qualifier model yet. Nonetheless, in combination with your property "lethal dose" a more generic qualifier property could IMHO be sufficient.  — Felix Reimann (talk) 11:40, 4 December 2013 (UTC)
I don't really see why not. But perhaps the intent is to indicate one of a few model organisms (there are not all that many different ones used, I believe) and then it might work to have a property with a few pre-defined values? - Brya (talk) 17:55, 4 December 2013 (UTC)
  Support I think it would be useful as a qualifier for items like nodding disease (Q895930). In the statement for "possible causes" the qualifier for the parasite is not always a species. So a more general qualifier would be good. --Tobias1984 (talk) 10:27, 9 December 2013 (UTC)
Still, I believe that for the lethal dose example, a more general qualifier would be sufficient. You would have my support there. However, for your example, Tobias, wouldn't you need to propose a property "possible cause" which than can have taxa as well as for example toxic substances as target, i.e., the proposed property would not work.  — Felix Reimann (talk) 16:37, 9 December 2013 (UTC)
@FelixReimann: I am still uncertain about a lot of connections between medicine and the rest of the Wikidata-space, so I can only give you bad answers. The property "possible cause" is already created and in my example (nodding disease (Q895930)) I linked it to "parasitic disease". But linking directly to the parasite or toxic would be possible too. There is still a lot to figure out. --Tobias1984 (talk) 21:28, 9 December 2013 (UTC)
  Oppose P89 (P89) is enough. Snipre (talk) 15:35, 12 December 2013 (UTC)
@Snipre: But not everything we want to link is a species. So either we have to rename it or create another property. --Tobias1984 (talk) 16:03, 12 December 2013 (UTC)
Now I am confused. In the example given we saw a model organism in which a certain test result was obtained, but apparently the discussion is now about vectors?
        These look like two quite different things to me. Medical and pharmaceutical testing uses a quite limited number of model organisms, which are often quite special. Rabbits used for tests are not comparable to rabbits in general, let alone wild rabbits. A new property for this seems possible, although it should not be called "taxon", as these often have nothing to do with taxa, but are man-made organisms.
        On the other hand vectors which transmit diseases are wild animals, in no way distinguishable from others of the same species. For these "taxon name" still seems the straightforward option. - Brya (talk) 17:38, 12 December 2013 (UTC)
@Tobias1984: I agree for the question of the name of the property P89 (P89) but in the toxicity framework they don't considered the real species only the type of animal. Here we can consider different ways of using P89 (P89) according to the data we want to save. Snipre (talk) 12:46, 29 January 2014 (UTC)
  Comment. This property would need a more specific name; "taxon" is too ambiguous. I agree with Felix that something like "applies to", or perhaps "observed in", would be preferable if we want to capture this information in a qualifier claim.
On the other hand, we should also be mindful that qualifiers will not be queryable for the foreseeable future. So taxon-specific LD properties might be a better way to model this data, since then all the values will be queryable. Lethal dose (LD) properties for different taxa like those in GZWDer's example can be clustered together by automated statement ordering. The relationship between them can be formally captured with 'subproperty of' statements in the property's documentation template. Emw (talk) 05:38, 1 February 2014 (UTC)
  Comment P89 was deleted by user:Delusion23 after being deprecated by user:Jakob at Wikidata:Requests for deletions/Archive/2014/Properties/1#Taxonomic rank properties. John Vandenberg (talk) 07:10, 15 April 2014 (UTC)

@John Vandenberg, Emw, FelixReimann, Brya, Snipre, Tobias1984: I have changed the name to "applies to taxon", in consonance with other properties like applies to part (P518) and applies to jurisdiction (P1001). If there are no further objections I will create this property in the next days--Micru (talk) 09:45, 7 July 2014 (UTC)

@Micru: Instead of creating a new property shouldn't we merge applies to part (P518) and applies to jurisdiction (P1001) a one with the label applied to and use this new property for our case ? In the case of interest taxon is not very understandable. Snipre (talk) 09:21, 9 July 2014 (UTC)
@Snipre: I think that is a good idea. I had nominated applies to jurisdiction (P1001) for deletion, probably we can convert applies to part (P518) into a generic "applies to" property and merge both. Then this property wouldn't be necessary.--Micru (talk) 09:48, 9 July 2014 (UTC)
@John Vandenberg, Emw, FelixReimann, Brya, Tobias1984, GZWDer: Please put your comment there. Snipre (talk) 12:39, 9 July 2014 (UTC)

@John Vandenberg, Emw, FelixReimann, Brya, Snipre, Tobias1984: It seems applies to jurisdiction (P1001) was kept. What now? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 10:43, 16 March 2015 (UTC)

This property applies to jurisdiction (P1001) is a mess so instead of trying to extend it better propose a new one. Snipre (talk) 11:48, 16 March 2015 (UTC)

Not done; no consensus. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 11:07, 22 May 2015 (UTC)

IRAC code

   Not done
DescriptionInsecticide Resistance Action Committee (IRAC) class
Data typeItem
Domainchemical compound (Q11173)
Allowed values1A, 1B, ..., 25, 28
ExampleDichlorvos == dichlorvos (Q420622) == 1B
Format and edit filter validationlimited number of allowed values (50 alltogether)
SourceIRAC MoA Classification Scheme 7.3
Proposed byKopiersperre (talk)
Discussion

Insecticides can be classified by their target site into mode of action groups (IRAC Mode of Action Classification Poster). This is already available as a big table in german wikipedia (de:Insecticide Resistance Action Committee); I want this in Wikidata, too. This is my first proposal, please apologise when it's not conform to the rules. --Kopiersperre (talk) 21:05, 24 July 2014 (UTC)

  Question - Wouldn't string be better for this property? No need to translate this code. No statements need to be attached to the code, if items were created for it? -Tobias1984 (talk) 22:14, 24 July 2014 (UTC)
I'm not sure. Some of the groups (like 1A – carbamate (Q422899), 1B – organophosphate (Q411097), 3A – Pyrethroid (Q745766) and 4A – neonicotinoid (Q902225)) have articles (=an item). In my opinion there should not just be a string (e.g. "3A"), but a link to the group article (e.g. Pyrethroid (Q745766)).--Kopiersperre (talk) 12:46, 25 July 2014 (UTC)
User Rjh told me, that the proposal should be extended:
  • ) The IRAC Code (example: "1A" – Carbamates) as item
  • ) The mode of action (example: Group 1 – Acetylcholinesterase inhibitors) as item--Kopiersperre (talk) 01:27, 2 August 2014 (UTC)
Please provide a complete exemple. Snipre (talk) 22:04, 27 August 2014 (UTC)
I can't figure out what's missing.--Kopiersperre (talk) 13:55, 19 September 2014 (UTC)
Property, value, qualifier, value. You propose two relations: this means two different properties or one property and a qualifier. Snipre (talk) 14:00, 23 September 2014 (UTC)
Kopiersperre; I think that Snipre is suggesting you need to propose a 'mode of action' property as well. Does that make sense to you? Is there another property that could be used for this? Filceolaire (talk) 22:56, 2 November 2014 (UTC)
I just wanted to know if the mode of action was necessary or not in the definition of the IRAC Code. Snipre (talk) 11:46, 16 March 2015 (UTC)
@Kopiersperre: Would you like to respond? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 10:36, 16 March 2015 (UTC)

Not done - no support, no response from proponent. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 11:06, 22 May 2015 (UTC)

IUPAC name

   On hold
Descriptionfull name of a molecule according to IUPAC nomenclature
Data typeMultilingual text (not available yet)
Template parameter"IUPACName" in en:template:chembox
DomainMolecules, especially useful for organic molecules
Exampleethanol (Q153) => Ethanol; acetone (Q49546) => Propanone;
SourceThe many sources of IUPAC nomenclature are listed [=nomenclature here]
Robot and gadget jobsBots could import names from the prescribed infoboxes on various Wikipedias
Proposed byWylve (talk)
Discussion

IUPAC nomenclature is one of the standard naming systems of molecules. This information is also used on many Wikipedia infoboxes. —Wylve (talk) 04:59, 30 November 2014 (UTC)

Saehrimnir
Leyo
Snipre
Jasper Deng
Dcirovic
Walkerma
Egon Willighagen
Denise Slenter
Daniel Mietchen
Andy Mabbett
Kopiersperre
Emily Temple-Wood
Pablo Busatto (Almondega)
Nothingserious
Antony Williams (EPA)
TomT0m
Wostr
Devon Fyson
User:DePiep
User:DavRosen
Benjaminabel
99of9
Kubaello
Fractaler
Sebotic
Netha
Hugo
Samuel Clark
Tris T7
Leiem
  Notified participants of WikiProject Chemistry --Tobias1984 (talk) 09:36, 30 November 2014 (UTC)

  Support. Emw (talk) 15:39, 30 November 2014 (UTC)
@Emw, Wylve: WikiProject Chemistry has this property listed under multilingual-text-dataype. I too think, that string is a bad idea because the IUPAC naming convention exists for many languages. Currently we only have mono-lingual available as datatype. I am still not sure what the difference of multi- and monolingual will be, but we should decide for one of them. --Tobias1984 (talk) 15:52, 30 November 2014 (UTC)
It really depends on how multilingual will be implemented. The definition here is not clear IMO. Regardless of which datatype we settle on, we should not create this property until there is a consensus on this problem. I don't wish to go through the P357 (P357) => title (P1476) fiasco again. —Wylve (talk) 17:30, 30 November 2014 (UTC)
@Wylve, Emw, Tobias1984: This property can't be string: different rules apply for the different langages. Ex.: in English 3-Propanol, in French propan-3-ol; sulfide in English, sulfure in French. The normal datatype is at least monolingual datatype. But the multilingual datatype is still in discussion. No real refusal from the development team, only comment about the number of properties which can use this datatype. The difference between the monolingual and the multilingual datatype is the relation between property and value. With the monolingual datatype there is only one relation property-value. You can create additonal relations for each langage you want to add but in the data structure but you still have property-value pairs. With the multilingual datatype you assume several values for one property property-value-value-value... Monolingual datatype is useful when only a few number of values in different languages will be added. If now you assume that you want to translate one value in all possible languages, then the monolingual datatype is limited. For comparison, the monolingual datatype is a table with two cells (value+langage). Each time you add a new value you create a new table. The multilingual datatype is a table of X lines and two columns. Snipre (talk) 21:58, 30 November 2014 (UTC)
@Snipre, Emw, Tobias1984:: I have changed the proposed datatype to multilingual text. —Wylve (talk) 00:26, 1 December 2014 (UTC)

Gray's Anatomy 1918 page

   Not done
DescriptionThe page number of this article's respective entry in the 1918 edition of Gray's Anatomy
Data typeString
Template parameter"GrayPage" in en:template:infobox anatomy
Domainanatomical articles on EN WP and many other language wikis.
Allowed valuesnumber from 1 to 1396 (from page 1 to page 1396)
Exampleintervertebral disc (Q502781) => "289" (page 289)
Format and edit filter validationnumber from 1 to 1396 (from page 1 to page 1396)
Sourcewikipedia infoboxes, already populated.
Robot and gadget jobsA bot could be automated to take data from the infoboxes.
Proposed byFrom discussion at Property_talk:P1698 --Was a bee (talk)
Discussion

Not a few parts of English Wikipedia's Anatomy articles are made from public domain anatomy book "Gray's Anatomy 1918 edition." Sharing its source pages through WikiData is valuable not only for EN WP, but also for many other WPs which translated large quantities of anatomy articles from EN WP.Was a bee (talk) 04:32, 18 January 2015 (UTC)

  Support -- LaddΩ chat ;) 15:01, 18 January 2015 (UTC)
  Oppose There is already a page property and a reference data structure. Redundant. Snipre (talk) 11:09, 21 February 2015 (UTC)
  Comment Thank you @Snipre: for commenting. I forgot to stated explicitly the relationship between this property proposal ("Gray's Anatomy 1918 page") and the already-existing property ("Gray's Anatomy 1918 subject": Property:P1698). Historical and technical reason, the way to refer to Gray's anatomy in Wikipedia infoboxes uses 2 digits, "subject" and "page". Property:P1698 is for "subject", and this proposal is for "page". History in brief....
1. Formerly Gray's anatomy was linked to the copy hosted at Yahoo!. And Yahoo needs subject digit to link.
2. But Yahoo had some problems (about 20% of their page was blanked one years ago. And now, Yahoo's Gray is down).
3. So, in English Wikipedia, currently Gray's anatomy was linked to Open Library. Open Library needs page digit to link.
For more details, see en:Template:Gray's Anatomy link and its talk page, and Property_talk:P1698. As a result, we need this "page" property to link to the each pages of the book. I feel sorry for my low skill to explaining this complex situation clearly. Thanks. --Was a bee (talk) 17:19, 8 March 2015 (UTC) bit added explanation of the situation. --Was a bee (talk) 09:59, 10 March 2015 (UTC)
@Was a bee: Don't feel sorry, it's a normal way to act when working in a specialized field. But your explanations are not very in favor of creating new property: you say that you use one parameter to link Yahoo's webpages to WP but that now Yahoo is not working anymore so why do we need to create a property for dead links ? From your explanation better delete this outdated data and use only valid data. Snipre (talk) 14:20, 10 March 2015 (UTC)
@Was a bee: I just spend a little time to understand your way to use this reference and I think you don't read help:sources. Gray's Anatomy is a book so the first step is to create a item for the book. Here we reach the first problem: this are several editions. So we have to create a item for the work and others items for each edition
work item: Gray's Anatomy (Q200306)
edition item for 20th edition: Gray's Anatomy (20th edition) (Q19558994)
So now to use the reference to 20th edition, just use stated in (P248): Gray's Anatomy (20th edition) (Q19558994) and page(s) (P304): XXX where the page is the real page number of the book. Then if you want to include a URL for a online copy use the properties reference URL (P854) or archive URL (P1065).
So the property P1698 (P1698) is not more useful and can be deleted. Snipre (talk) 09:14, 11 March 2015 (UTC)
@Snipre: We can't delete it, because the English anatomy infobox uses the data. The book can be used as a source, but it is also used as an identifier on English Wikipedia. We have to accepts that, even if it is somewhat redundant on Wikidata. --Tobias1984 (talk) 09:21, 11 March 2015 (UTC)
@Tobias1984: This not a data, this just a piece of code used to create an URL to webpages which no longer exist. That's typically a case of URL obsolescence. If en:WP wants to keep this kind of data, why not but plenty of other WPs have other rules so I don't think that en:WP has some priority. WD is an international project not an en project. I am ready to find solutions but global solutions and not solutions for every type of infoboxes from every WP. The solution I propose is to see if the subject parameter can be correlated with a real chapter in the book. If yes, use chapter (P792) instead of P1698 (P1698). Snipre (talk) 09:45, 11 March 2015 (UTC)
@Tobias1984: Sorry but please look at that page: beside old yahoo webpages this are 3 others online versions of the book. So why do we have to create a special structure for outdated links if we have the possibility to use active links which require less data (only the page number) ? Snipre (talk) 09:51, 11 March 2015 (UTC)
@Snipre: I am sure, we can find a way of improving the current situation, but we have to inform the communities that we are changing something. And we need a working solution in place, before we can switch over to the better version. We can't break these links, even if it is just for one day. --Tobias1984 (talk) 10:10, 11 March 2015 (UTC)
@Tobias1984: We don't break anything because we don't modify anything in en:WP articles. These are the guys which want to use WD data in infoboxes to see how they want the final data. I just want to have the answer of Was a bee and after we can organize the deletion process of the property (which is only 5 days old). Snipre (talk) 10:42, 11 March 2015 (UTC)
@Tobias1984, Was a bee: The problem if we look at the use of P1698 (P1698) is the specificity of the property to one book and one type of URL. If we allow that we will create bunch of properties only for URL creation. This is not the goal of WD.
The best way is to use this structure
described by source (P1343): Gray's Anatomy (20th edition) (Q19558994)
reference stated in (P248): Gray's Anatomy (20th edition) (Q19558994), page(s) (P304): XXX
Then we can use lua to extract that information in the infobox to create the link or if this is too complex we can use directly the properties reference URL (P854) or archive URL (P1065) to store the URL in the reference section and at the end use lua to extract it in the infoboxes.
This is not the most simple way but if we think about anatomy and all possible online references, we just can't create a specific property for each online version. Snipre (talk) 14:15, 11 March 2015 (UTC)
@Snipre, Tobias1984: thank you very much for discussion. That "structure" idea seems very interesting. I want to know more about the idea. Before that, let me put here the background motivation. Perhaps this is something redundant, but I think this can be some help for discussion.
Motivation: "Why Gray's anatomy (1918)?": Gray's Anatomy (1918) is widely used in Wikipedia. Actually major part of English Wikipedia anatomy articles consist of copy-and-paste from Gray's Anatomy 1918 edition (because it is Public domain). And there are numerous articles, outside of EnWP, created based on translation from EnWp anatomy articles (in other words, translation of Gray's Anatomy 1918 text). I don't know exact portion, but I suppose 30%-50% of anatomy text in EnWp would be made by copy-and-paste from Gray's Anatomy 1918 (and I suppose 20%-30% anatomy text in other language Wikipedia). So I feel systematic sourcing of Gray's Anatomy 1918 through Wikidata, in a way that all language projects can easily use, is important. And from this line....
Both data would be nice: However I don't claim about what type or format is suitable for implementation of these data (Property, structure, or something else? Simply because I don't know well...), from the motivation above, I feel both subject-data and page-data are needed. Because websites which uses page (Open Archive and HathiTrust) are book-reader style website (which providing book content as images, like this). So we can not machine-translate that. This point is not problematic for English speaking readers. Because Gray's Anatomy is written in English. But for non-English speakers this point can be problematic. Websites which uses subject (Bartleby and Yahoo) providing book content as plain-text. So we can easily copy-and-paste and machine-translate that (like this).
Future vision: At Wikiproject:Anatomy in EnWp, there has been proposed that inclusion of links to other online anatomy texts (for example Sobotta's Human Anatomy). So Snipre's worrying about "one property for one book" sounds reasonable to me. I also feel that more smartly expandable style would be nice.
Test case: I tried making test case for Snipre's idea at frontal lobe (Q749520). I feel this can possibly be a solution. What do you think?
Thank you very much. --Was a bee (talk) 17:11, 14 March 2015 (UTC) bit added future vision. --Was a bee (talk) 10:19, 15 March 2015 (UTC)
@Was a bee: I think the important thing is that the solution can be used in Wikipedia. We probably need to talk to the lua-module and wikidata-module people. The other thing I would prefer is creating an item for each edition of Gray's anatomy. Filling 10 string-fields in thousands of items is very prone to errors. --Tobias1984 (talk) 11:08, 15 March 2015 (UTC)
@Tobias1984: thank you for advice. I post WP:Anatomy and Module:Wikidata.
And about " The other thing I would prefer is creating an item for each edition of Gray's anatomy", User:Snipre made item for 20th edition (Gray's Anatomy (20th edition) (Q19558994)). I feel it seems OK by this, at least for our current task. --Was a bee (talk) 17:13, 17 March 2015 (UTC)
Hello everyone, I'm one of the Anatomy editors at EN:WP. Gray's Anatomy is an english-language textbook and the 1918 edition contains a lot of material which has formed the basis for the EN:WP, and by virtue of translation probably a significant portion of other language articles too, as is noted above. I think whether or not page numbers of relevant textbooks should be included is a question for wikidata regulars. 1918 page numbers sure, but there's another 39 editions after that, and what's the benefit to editors? None as far as I can tell other than 1918. I can think of some downsides (from my point of view) however -- creating an extraordinary number of items, large maintenance value, little (other than 1918) multilingual use, and I am not sure why Gray's should get this special treatment as compared with other textbooks. Page numbers other than 1918 are only really useful if a user has bought the textbook, so for recent editions are we encouraging this? Lastly there are international and local editions of the more recent editions, I'm not sure if they differ in page numbers. So I think 1918 page numbers yes, but am not too supportive of fields for the remaining 39 editions. --LT910001 (talk) 20:09, 19 March 2015 (UTC)
We have Help:Sources which provides the structure for the items used as references. @Was a bee: I modified the qualifier structure in frontal lobe (Q749520): put only the relevant data, i.e. the item of the edition, the page number. All other data (author, edition number, publication date,...) can be retrieved from the edition data. Then use archive url only for archive links and for normal links use reference URL (P854). Snipre (talk) 12:39, 18 March 2015 (UTC)
@Was a bee: You can use the reference structure to add several URLs to the same statement. By the way you can create all URLs and at the end you don't need to create the lua function to build the urls on the client sid~. See the examples at frontal lobe (Q749520). If you apply a strict way to enter this type of data (bot) you can select the desired URL by filtering the title data from all references. So if you want to use only the Bartleby web site, you can filter the references using the title data and display only this one in your infobox. But here you need lua expertise.Snipre (talk) 13:02, 18 March 2015 (UTC)
Thank you @Snipre:. At EnWp Module:Wikidata, User:Paweł had made new function for us, which enables us calling any data we want from Wikidata. So, now, there are no big barrier for storing data at reference section (or any other sections). However some conditional branch code would be needed if we stably use data at reference section, I think such conditional branch code is not so difficult (because there is already nice function made by Paweł). So I'll try to bot-request of importing "Gray page" data from EnWp and moving "Gray Subject" data into its reference section. Thanks!--Was a bee (talk) 19:12, 24 March 2015 (UTC)
  Info Wikidata:Bot_requests#Gray's Anatomy data was proposed. --Was a bee (talk) 17:12, 25 March 2015 (UTC)
  •   Oppose}. I think we can manage with the existing properties. I have editted frontal lobe (Q749520) to add links to the Yahoo copy and the chapter name (instead of the Yahoo chapter specific number). There is nothing to stop us creating a separate item for the Yahoo edition of the book if it is really felt to be needed but I would rather we find a more general solution - like creating a Wikisource edition to link to, with proper #section links to each section instead of these links to pages and chapters. Filceolaire (talk) 18:15, 20 March 2015 (UTC)
Note that I have added P1698 (P1698) to the Wikidata:Properties_for_deletion. Filceolaire (talk) 18:39, 20 March 2015 (UTC)
Specifically we should use described by source (P1343) with qualifiers for chapter (P792), page(s) (P304) and section, verse, paragraph, or clause (P958) and references (with reference URL (P854)) to online editions - like frontal lobe (Q749520). Filceolaire (talk) 16:59, 22 March 2015 (UTC)
Thanks Filceolaire. I proposed the bot-request which includes the same heart you wrote just here. If property deletion doesn't delete data, we can process the property deletion request independently from the bot request. --Was a bee (talk) 17:27, 25 March 2015 (UTC)
Was a bee when it is agreed that a property should be deleted then the property name is changed to add (DEPRECATED) to discourage people from using it. Once the statements using the property are all deleted or rewritten to use another property then the property is deleted. Hope this helps. Filceolaire (talk) 20:11, 1 April 2015 (UTC)

Icelandic last name

   Withdrawn
Descriptionlastname formed from an Icelandic given name. See en:Icelandic name.
Data typeMonolingual text
Template parameterWikipedia infobox parameters, if any; ex: "population" in en:template:infobox settlement
DomainIcelandic given names
ExampleBjörn (Q8851571) => "Björnsson", "Björnsdóttir"
Sourceexternal reference, Wikipedia list article, etc.
  • Simplify decoding Icelandic names. --- Jura 10:27, 1 May 2015 (UTC)
It should be generise to a patronym, to use with a slavic (e.g. Russian: Пётр → Петрович, Петровна) and other nations' names. -- Sergey kudryavtsev (talk) 19:52, 2 May 2015 (UTC)
Ideally, yes, but I'm a bit hesitant to do that. If it's too broad, it's harder to build/expand. We can't even do constraint checks on languages. Icelandic patronyms/matronyms have the main advantage of being in use. Depending on how it works we could do a more generic property later. --- Jura 01:34, 3 May 2015 (UTC)
I agree with Sergey that this should be patronym. I can't see anything special about the Icelandic use of them which would require an Iceland-specific property. I'm not sure exactly what you mean by "being in use" but if you mean that people in Iceland have names which include patronymics, well, so do most people in Russia (see en:Eastern Slavic naming customs) and some people in Indonesia (en:Indonesian names), to mention the other two I'm most familiar with.
Also, is monolingual text the best choice here? given name (P735) and family name (P734) are both links to items, and if patronymics were also links to items, we could link them to the names they're derived from. I also suspect there are quite a few which are used as surnames as well and therefore already have items. - Nikki (talk) 19:46, 10 May 2015 (UTC)
I suppose it depends how you plan to use it. BTW, the idea is not to indicate patronymic surnames, but last names that are patronymic. --- Jura 19:54, 10 May 2015 (UTC)
I think text is the best choice for datatype. in the example given "Björn" is the name that you can make statements about. There is not much you can say about "Björnsson" and "Björnsdottir" except that they are derived from "Björn". Having said that I think we should create the inverse property. "Given name from which this surname is derived" with example Selma Björnsdóttir (Q175119)=>Björn (Q8851571). Filceolaire (talk) 18:24, 11 May 2015 (UTC)

seats won

   Not done
Descriptionnumber of seats won for a party in an election
Representselection (Q40231)
Data typeNumber (not available yet)
Template parameterseats1 in en:Template:Infobox election as one example
Domainelection-items
Allowed valuespositive integer
Example 1MISSING
Example 2MISSING
Example 3MISSING
Sourceexternal reference, Wikipedia list article, etc.
Robot and gadget jobsplausible
Motivation

I am trying to find a way to describe how many seats each party or group of parties in a legistative chamber got after an general election. An earlier proposals like this one got denied a new property, mainy because some users thought we instead should list all elected MP's and in the items about them tell which political party they represents. (I cannot find that discussion at the moment.) That will in many cases solve the issue, but there are many many elections, we do not know that much about. In the 1930/31 city-elections in Sweden, all we know is the name of the political parties and the number of seats they got. We do not even know their names and in some cases we do not even know how many votes they got. Another problem can be seen here. The Swedish riksdag (with 349 seats) has since the beginning of the 4-year-period in october 2014 had 395 MP's. -- Innocent bystander (talk) 12:31, 24 May 2015 (UTC)

Discussion

we have number of seats (P1342) and number of representatives in an organization/legislature (P1410), which should be sufficient--Oursana (talk) 13:49, 24 May 2015 (UTC)

Thank, @Oursana:, I speedy archive this one! -- Innocent bystander (talk) 18:05, 24 May 2015 (UTC)

proposed by

   Not done
Discussion

Might be useful to link conjectures (and algorithms, constructions, maybe some other methods) with those humans who described them for the first time and made them notable. Some people are already using notable work (P800) for algorithms (I've seen it in William Kahan (Q92782)), which doesn't look quite correct. Danneks (talk) 16:58, 2 September 2014 (UTC)

  Support, I don't think the use of the work notion property is wrong, a work is the product of human thinking and/or realization, it does not have to be an artwork. But if someone conjectured something, the work is the act of conjecturing, and if someone proved, the work is the act of proving, and the result is the proof.
This raise a question : how do we model the difference beetween a conjecture and a theorem ? A conjecture is a math property supposed to be true, and a theorem is a math formula or idea for which there exists a proof.
So maybe a better modeling could be an item to the proof in this case, the proof will have one or several authors. I can't think of an equivalent for conjectures, maybe an item to the scientific publication or letter in which the author made the conjecture ? We can call this class of documents conjecturing documents, and we could say the author of a conjecture is the author of a conjecturing documents. The conjecture itself beeing the item about the formula/property. Maybe, in a longer perspective, we can express all these in terms of more generic properties ?
Anyway I would recommand to change the scope of this propery to maths formulas or properties, whether they are proved, disproved, undecidable or whatever. TomT0m (talk) 11:17, 20 September 2014 (UTC)
Actually, we already have something like that in Universe (Q1), connected with multiverse (Q3327819)! Maybe we can use described by source (P1343) with instance of=conjecture or proposal as a qualifier? Danneks (talk) 14:12, 20 September 2014 (UTC) No, it is not not clear whether the item is conjectured, or the statement that it is described by source... But maybe P794 (P794) would do? Danneks (talk) 15:04, 20 September 2014 (UTC)
I'm not a huge fan of P794 (P794) as it is not really well defined by itself and needs a lot of domain knoledge to be understood, I think its use has to be specified in the main property (the as qualifier used with this property means ...). I think a good solution could be . With a statement and a
< Poincaré conjecture (Q203586)     > conjectured by search < Q81082 >
I think we're not so bad. TomT0m (talk) 17:26, 20 September 2014 (UTC)
That sounds good, but I don't see why we should restrict usage of this property to statements in some formal language (those which can, in a precise sense, be proved). I think that it can describe any propositions, including one about Q1 and Q3327819, and that provability or existence of formalization in a given system are additional properties. Danneks (talk) 19:15, 20 September 2014 (UTC)
@Danneks: We got different name for this : theories. Theories may have authors, and are refuted rather than proved or disproved ... The ontological nature of maths is different from other sciences (at least controversial :)), and mathematical statements can be proved, whereas theories are different in nature (theories are models of the world); so that justifies the different properties I think. But yes, we can discuss the analog problems for Lorentz ether theory (Q1870029) or general relativity (Q11452).
But I (re)realize we are talking about the proposed by property /o\ but anyway I would be fine with author, this is a kind of authorship. I don't really know which meaning is added by the proposed by idea. Except something that seem very cultural : artists are authors, scientists are theory creators ? TomT0m (talk) 19:53, 20 September 2014 (UTC)
I thought that only single works have authors, and that there are no authorship rights for theories yet :) But for many theories there is a person who is clearly associated with it, who described it and said that it is a good theory for the first time... Is this too ambiguous? I agree that conjectures and theories are proposed in different ways, but anyway there are (often) a person who proposes it, and a community which accepts it or not. Mathematical community accepts something if it is proved, natural scientists have other criteria for evaluating hypotheses. Both are notable for the history of science, so why to split? If you are only interested in scientific facts, then it makes a little difference who proposed something, but it is important from a historical or sociological viewpoint. Danneks (talk) 20:34, 20 September 2014 (UTC)
@Danneks: It's not because their is no copyrights or authorship rights on scientific theories that there can't be authors to them :) Actualy in french wikipedia the larger definition of author is
De manière générale, un auteur (du latin auctor) est une personne qui est la cause, le responsable. On peut être l'auteur d'une découverte, d'un accident…
Trad :
In general, an author (from latin auctor) is the person who is the cause, the responsible. One can be author of a discovery, an accident...
so the difference seems indeed cultural. In this sense the author property is enough, so why to split :) ? I don't really like the english wikipedia's definition because it seems somehow self referencing : an author is someone whom society gives author rights. Author rights are given to people who authored. (yes I skipped parts :) ) Really legalist but that does not tell much about authorship, except a restriction of the kind of works who gives legal rights. In conclusion I agree with you : we need only one property. At most :), I'm perfectly fine saying Einstein is the author of Relativity theories, even if he never had legal rights on them, thank humanity ;) TomT0m (talk) 21:32, 20 September 2014 (UTC)
An author is an author of the whole work, and it could be argued that a theorem is not a theorem without a proof. And a theory may be subsequentially refined by many people. Maybe discoverer or inventor (P61) is better? The general definition of invent applies perfectly to abstract objects. If it can be used together with a qualifier published in (P1433), it will be great. Or maybe we need a qualifier description published in? Danneks (talk) 11:22, 21 September 2014 (UTC)
@Danneks: We already have proved by (P1318) for the author of a proof. (Maybe we should have a converse property refuted by anyway). I'm fine with discoverer or inventor (P61), although it may be a good solution for taxon author (P405), maybe author (P50) as well. TomT0m (talk) 14:11, 21 September 2014 (UTC)
@TomT0m: OK, I will use discoverer or inventor (P61) then. I think we can close this proposal and discuss whether we need to model the content of (some) scientific articles in another place. Danneks (talk) 15:10, 21 September 2014 (UTC)
@Danneks: For the record, we should document this on WikiProject Mathematics and/or on the conjecture and theorem items. TomT0m (talk) 15:52, 21 September 2014 (UTC)

Side effect

   Done: side effect (P1909) (Talk and documentation)
DescriptionSide effects of a drug or medical procedure
Data typeItem
Template parameter?
DomainPharmaceutical drugs, medical procedures, ...
Allowed valuesAny symptom
ExampleInfluenza vaccine (Q383260)sore throat (Q1292082)
Format and edit filter validation?
SourceMedical publications
Robot and gadget jobs?

Subject items: side effect (Q3269441), adverse drug reaction (Q45959)

Not sure if we need to distinguish between positive and negative side effects at this point. This will help to generate infoboxes that describe a vaccine. --Tobias1984 (talk) 15:30, 24 May 2015 (UTC)

Discussion

Tobias1984
Doc James
User:Bluerasberry
Wouterstomp
Gambo7
Daniel Mietchen
Andrew Su
Peter.C
Klortho
Remember
Matthiassamwald
Projekt ANA
Andrux
Pavel Dušek
Was a bee
Alepfu
FloNight
Genewiki123
Emw
emitraka
Lschriml
Mvolz
Franciaio
User:Lucas559
User:Jtuom
Chris Mungall
ChristianKl
Gstupp
Geoide
Sintakso
علاء
Dr. Abhijeet Safai
Adert
CFCF
Jtuom
Lucas559
Drchriswilliams
Okkn
CAPTAIN RAJU
LeadSongDog
Ozzie10aaaa
Sami Mlouhi
Marsupium
Netha Hussain
Abhijeet Safai
ShelleyAdams
Fractaler
Seppi333
Shani Evenstein
Csisc
linuxo
Arash
Morgankevinj
Anandhisuresh
TiagoLubiana
ZI Jony
Viveknalgirkar   Notified participants of WikiProject Medicine --Tobias1984 (talk) 15:31, 24 May 2015 (UTC)

  Support Emitraka (talk) 19:48, 26 May 2015 (UTC)
  Support Sebotic (talk) 18:04, 28 May 2015 (UTC)
  Done --Tobias1984 (talk) 09:30, 30 May 2015 (UTC)

decreased expression in

DescriptionThis property should link a gene and a disease and indicate that a decreased expression of the gene is found in the disease
Data typeItem
Domaingene (Q7187)
Allowed valuesWikidata Item ID (Q*) with subclass disease (Q12136)
ExampleCDKN2ASkin melanoma
SourceClinvar, Pubmed
Robot and gadget jobsRobots will add this property to the appropriate WD items.
Motivation

This new property, together with serveral others, should serve the description of gene <> disease relations. Sebotic (talk) 02:01, 22 May 2015 (UTC)

Discussion
  Support Andrawaag (talk) 09:39, 22 May 2015 (UTC)
  Support Emitraka (talk) 19:42, 26 May 2015 (UTC)
  Support Andrew Su (talk) 23:33, 27 May 2015 (UTC)
  Support --Genewiki123 (talk) 23:37, 27 May 2015 (UTC)
  Done --Tobias1984 (talk) 09:48, 30 May 2015 (UTC)


increased expression in

DescriptionThis property should link a gene and a disease and indicate that increased an expression of the gene is found in the disease
Data typeItem
Domaingene (Q7187)
Allowed valuesWikidata Item ID (Q*) with subclass disease (Q12136)
ExampleEGFRSkin melanoma
SourceClinvar, Pubmed
Robot and gadget jobsRobots will add this property to the appropriate WD items.
Motivation

This new property, together with serveral others, should serve the description of gene <> disease relations. Sebotic (talk) 02:01, 22 May 2015 (UTC)

Discussion
  Support Emitraka (talk) 19:51, 26 May 2015 (UTC)
  Support Andrew Su (talk) 23:33, 27 May 2015 (UTC)
  Support --Genewiki123 (talk) 23:36, 27 May 2015 (UTC)
  Done --Tobias1984 (talk) 09:56, 30 May 2015 (UTC)

has deletion association with

DescriptionThis property should link a gene and a disease due to a deletion
Data typeItem
Domaingene (Q7187)
Allowed valuesWikidata Item ID (Q*) with subclass disease (Q12136)
ExampleCFTRCystic Fibrosis
SourceClinvar, Pubmed
Robot and gadget jobsRobots will add this property to the appropriate WD items.
Motivation

This new property, together with serveral others, should serve the description of gene <> disease relations. Sebotic (talk) 02:01, 22 May 2015 (UTC)

Discussion
  Support Emitraka (talk) 19:53, 26 May 2015 (UTC)
  Support Andrew Su (talk) 23:33, 27 May 2015 (UTC)
  Support --Genewiki123 (talk) 23:36, 27 May 2015 (UTC)
  Done --Tobias1984 (talk) 10:02, 30 May 2015 (UTC)

has duplication association with

DescriptionThis property should link a gene and a disease due to a duplication
Data typeItem
Domaingene (Q7187)
Allowed valuesWikidata Item ID (Q*) with subclass disease (Q12136)
ExamplePMP22Charcot–Marie–Tooth disease
SourceClinvar, Pubmed
Robot and gadget jobsRobots will add this property to the appropriate WD items.
Motivation

This new property, together with serveral others, should serve the description of gene <> disease relations. Sebotic (talk) 02:01, 22 May 2015 (UTC)

Discussion
  Support Andrew Su (talk) 23:33, 27 May 2015 (UTC)
  Support --Genewiki123 (talk) 23:36, 27 May 2015 (UTC)
  Done --Tobias1984 (talk) 10:07, 30 May 2015 (UTC)

has insertion association with

DescriptionThis property should link a gene and a disease due to an insertion
Data typeItem
Domaingene (Q7187)
Allowed valuesWikidata Item ID (Q*) with subclass disease (Q12136)
ExampleNOD2Crohns' disease
SourceClinvar, Pubmed
Robot and gadget jobsRobots will add this property to the appropriate WD items.
Motivation

This new property, together with serveral others, should serve the description of gene <> disease relations. Sebotic (talk) 02:01, 22 May 2015 (UTC)

Discussion
  Support Emitraka (talk) 19:56, 26 May 2015 (UTC)
  Support Andrew Su (talk) 23:33, 27 May 2015 (UTC)
  Support --Genewiki123 (talk) 23:36, 27 May 2015 (UTC)
  Done --Tobias1984 (talk) 10:11, 30 May 2015 (UTC)

has inversion association with

DescriptionThis property should link a gene and a disease due to an inversion
Data typeItem
Domaingene (Q7187)
Allowed valuesWikidata Item ID (Q*) with subclass disease (Q12136)
ExampleF8Hemophilia A
SourceClinvar, Pubmed
Robot and gadget jobsRobots will add this property to the appropriate WD items.
Motivation

This new property, together with serveral others, should serve the description of gene <> disease relations. Sebotic (talk) 02:01, 22 May 2015 (UTC)

Discussion
  Support Emitraka (talk) 19:56, 26 May 2015 (UTC)
  Support Andrew Su (talk) 23:33, 27 May 2015 (UTC)
  Done --Tobias1984 (talk) 10:13, 30 May 2015 (UTC)

has substitution association with

DescriptionThis property should link a gene and a disease due to a substitution
Data typeItem
Domaingene (Q7187)
Allowed valuesWikidata Item ID (Q*) with subclass disease (Q12136)
ExampleBRCA1 (Q227339)breast cancer (Q128581)
SourceClinvar, Pubmed
Robot and gadget jobsRobots will add this property to the appropriate WD items.
Motivation

This new property, together with serveral others, should serve the description of gene <> disease relations. Sebotic (talk) 02:01, 22 May 2015 (UTC)

Discussion
  Support Emitraka (talk) 19:55, 26 May 2015 (UTC)
  Support Andrew Su (talk) 23:33, 27 May 2015 (UTC)
  Done --Tobias1984 (talk) 10:16, 30 May 2015 (UTC)

has posttranslational modification association with

DescriptionThis property should link a gene and a disease due to an altered posttranslational modification
Data typeItem
Domaingene (Q7187), protein (Q8054)
Allowed valuesWikidata Item ID (Q*) with subclass disease (Q12136)
ExampleMITFSkin melanoma
SourceClinvar, Pubmed
Robot and gadget jobsRobots will add this property to the appropriate WD items.
Motivation

This new property, together with serveral others, should serve the description of gene <> disease relations. Sebotic (talk) 02:01, 22 May 2015 (UTC)

Discussion
  Support Emitraka (talk) 19:55, 26 May 2015 (UTC)
  Support Andrew Su (talk) 23:33, 27 May 2015 (UTC)
  Done --Tobias1984 (talk) 10:19, 30 May 2015 (UTC)

altered regulation leads to

DescriptionThis property should link a gene and a disease due to altered regulation
Data typeItem
Domaingene (Q7187)
Allowed valuesWikidata Item ID (Q*) with subclass disease (Q12136)
ExampleSNCAParkinson's Disease
SourceClinvar, Pubmed
Robot and gadget jobsRobots will add this property to the appropriate WD items.
Motivation

This new property, together with serveral others, should serve the description of gene <> disease relations. Sebotic (talk) 02:01, 22 May 2015 (UTC)

Discussion
  Support Emitraka (talk) 19:54, 26 May 2015 (UTC)
  Support Andrew Su (talk) 23:33, 27 May 2015 (UTC)
  Done --Tobias1984 (talk) 10:21, 30 May 2015 (UTC)

different from

   Done: different from (P1889) (Talk and documentation)
DescriptionThis item is different from that one, and they are often confused. In contrast to said to be the same as (P460) that expresses uncertainty "... the statement is disputed", different from expresses a strong negation
Data typeItem
Template parameternot that I know of
Domainany item
Allowed valuesany item
ExamplePhilip A. Goodwin (Q7183094) (a politician) is different from Philip Russell Goodwin (Q7184251) (a painter). Many pairs in P245 (ULAN) Unique value are examples of "different from" (and the rest should be merged).
Sourceowl:differentFrom (OWL) and gvp:aat2100_distinguished_from (Getty's LOD)
Robot and gadget jobs
  • Check that the two items do not have the same authority identifier (AAT, TGN, ULAN, VIAF, GND, etc). The "Unique value constraint" on these identifiers already checks this (eg see P245 (ULAN) Unique value), but together with an explicit claim "different from", we can split that section into "Delete authority identifier from one of the items" vs "Merge the two items".
  • Check that the two items are not subject of the same statement: if Q1 different from Q2, there should be no statements Q3 P1 Q1 and Q3 P1 Q2. Of course, that's a warning not a certain mistake.
Proposed byVladimir Alexiev (talk)
Discussion

Automated jobs (and less often people) make mistakes and identify two things that are in fact different. It's useful to document the difference, so others won't repeat the same mistake. It can also be used to improve authority identifier management (see the first "robot job" above).

Important: Obviously it's crucial to add a reference to such a statement, lest endless discussion ensues. But what to add? I found that Philip A. Goodwin (Q7183094) is different from Philip Russell Goodwin (Q7184251) by inspecting their properties (different years, different professions), and ULAN for the latter. Ideally, I'd like to add a comment to that effect and my user name: but I can't do that in a reference. --Vladimir Alexiev (talk) 21:52, 11 January 2015 (UTC)

  •   Support --- Jura 16:17, 7 February 2015 (UTC)
  • I think this should be placed in talk pages instead of item, as clients don't need it.--GZWDer (talk) 06:14, 16 February 2015 (UTC)
         select * {?x gvp:aat2100_distinguished_from ?y}
  •   Support agree with Vladimir TomT0m (talk) 14:01, 22 March 2015 (UTC)
  •   Question - Is the intent that this essentially work as a "not to be confused with" statement? If so, I support it as useful externally as well as internally. Josh Baumgartner (talk) 18:01, 27 February 2015 (UTC)
    @Joshbaumgartner: It certainly is a useful usecase. TomT0m (talk) 14:07, 22 March 2015 (UTC)
  • Isn't the fact that we have two objects in our database always going to imply this property (except where that property contains a "same as")? Objects are different concepts always. --Izno (talk) 17:28, 9 March 2015 (UTC)
    @Izno: This depends on whether or not we make the unique name assumption (Q7886954)    . The OWL language, from which this property proposal is inspired, does not make it, so ... maybe in Wikidata in general it is not possible to make it, although it will be possible safely in subsets of Wikidata's dataset. TomT0m (talk) 14:07, 22 March 2015 (UTC)
The purpose is exactly "not to be confused with" (see the description). This will be used sparingly on two items that are likely to, or already have been, confused. OWL has a similar statement: owl:differentFrom. --Vladimir Alexiev (talk) 09:37, 1 April 2015 (UTC)
@Vladimir Alexiev, GZWDer, Jura1, Joshbaumgartner, TomT0m, Izno:@Filceolaire, T.seppelt:   Done, see different from (P1889). --George (Talk · Contribs · CentralAuth · Log) 16:39, 19 May 2015 (UTC)

The historical name of this

   Not done
DescriptionObject for this historical name
Data typeItem
Domainhistorical names, items without links to other Wikimedia projects
Allowed valuesgeographical object (Q618123), organization (Q43229) and others.
ExampleQ17126687Belarusian National Technical University (Q815268)
Q15626860Belarusian National Technical University (Q815268)

Leningrad → Saint Petersburg (Q656)
Motivation

Суть заключается в том, чтобы ссылаясь в статье на элемент, описывающий историческое название объекта, использовалось его название, но при этом гиперссылка вела на статью про объект. Сейчас же, если человек, например, родился в Ленинграде, то в карточке всё равно выдаст Санкт-Петербург, если создать отдельную страницу для названия Ленинград, то в статье вовсе не будет гиперссылки на Санкт-Петербург, хоть и будет выводится правильное название. (ru) – (Please translate this into English.) Чаховіч Уладзіслаў (talk) 12:24, 4 May 2015 (UTC)

Discussion
@Чаховіч Уладзіслаў:   Oppose, use
< Q17126687     > official name (P1448)   < 815268 >
valid in period (P1264)   < the period >
or follows (P155) and co. if you're not referring to a name but a former organization. Note that the datatype of official name is not item but string (@Infovarius, Ivan A. Krestinin: could one of you please translate ?) TomT0m (talk) 18:08, 7 May 2015 (UTC)
Возможно создание отдельного элемента для имени действительно избыточно и достаточно воспользоваться свойством official name (P1448) с квалификаторами start time (P580), end time (P582)? Хотя если у названия будет существенно больше свойств, чем просто дата начала/дата окончания действия, то может быть имеет смысл и отдельный элемент создать. — Ivan A. Krestinin (talk) 20:56, 7 May 2015 (UTC)
Квалификаторы создают много проблем, например, как карточка определит, что человек учился именно в период, когда БНТУ носил название Q15626860? Получается, что нужно искать и ручками вводить дату окончания (или поступления?), а если это так, то какой в этом смысл, если можно просто написать Q15626860?--Чаховіч Уладзіслаў (talk) 08:44, 9 May 2015 (UTC)
Соглашусь, предлагаемое вами решение проще варианта с квалификаторами, но есть у него и проблемы. Например, когда кто-то захочет составить список всех людей учившихся в этом университете, то запрос сильно усложнится. Пожалуй не возьмусь судить какой же из подходов лучше,   Neutral. — Ivan A. Krestinin (talk) 19:45, 18 May 2015 (UTC)

  Not done No support. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 13:40, 21 May 2015 (UTC)

Budget

   Withdrawn
Descriptionspecify the budget for producing something (an event or a product)
Data typeString
Template parameterex: "budget" in en:Template:Infobox film
Domainfor example film (Q11424), event (Q1656682), building (Q41176)
ExamplePretty Woman (Q207954), Eurovision Song Contest 2015 (Q15215081), Empire State Building (Q9188)
Robot and gadget jobsData can be transferred automatically from en:Template:Infobox film
Motivation

The property "budget" would add information to several instances where it is applicable. Datatype may have to be a string (or "string+number" for $1 or "number+string" for 1€) to allow for different currencies. --Bensin (talk) 22:10, 24 May 2015 (UTC)

Wikidata:Property_proposal/Pending/2#cost probably would suffice. The datatype is coming soon. --Izno (talk)
Great! In that case I withdraw my proposal. --Bensin (talk) 15:43, 25 May 2015 (UTC)
Discussion

Web Gallery of Art id

DescriptionWeb Gallery of Art identifier
RepresentsWeb Gallery of Art (Q1464063)
Data typeString
Domainperson
Allowed valuesalphabetical? Not sure if it should be UPPERCASE or lowercase
ExampleAgostino Busti (Q395600) -> BAMBAIA, leading to http://www.wga.hu/html/b/bambaia/index.html
Robot and gadget jobsmigrate catalog code (P528) with catalog (P972) = Web Gallery of Art (Q1464063) to this property
Proposed byVladimir Alexiev (talk)
Discussion

WGA seems to be a quite extensive catalog, with a lot of pictures.

Currently it's mapped to catalog code (P528) with qualifier catalog (P972) = Web Gallery of Art (Q1464063), but I don't see why it does not deserve a prop of its own.

The formatterURL would need special handling:

  • lowercase the id (if in fact the id should be in UPPERCASE, which I'm not sure about)
  • double the first letter: BAMBAIA -> b/bambaia (that's a common trick used to avoid overloading a file directory system)

Vladimir Alexiev (talk) 18:25, 13 February 2015 (UTC)

  Support --Nastoshka (talk) 23:22, 16 February 2015 (UTC)
  Support --Magnus Manske (talk) 18:49, 19 March 2015 (UTC)
  Support --Jane023 (talk) 14:38, 14 April 2015 (UTC)
  Comment I suggest the ID includes the prefix; not only makes that linking easier, but some entries (like this one) have an additional "first name specifier" which also includes a "/". --Magnus Manske (talk) 14:50, 14 April 2015 (UTC)
  • @Magnus Manske: But if the identifier in the example given is "BAMBAIA", not "b/bambaia", the URL structure may later change. We need a method of specifying more complex formatter URLs. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 20:43, 19 April 2015 (UTC)
  • I side with @Magnus Manske: on this one. http://www.wga.hu/html/f/fernande "FERNANDEZ, Spanish artists (not related)" is a disambiguation page that we should not consume. http://www.wga.hu/html/f/fernande/pedro "FERNÁNDEZ, Pedro" has a complex URL structure. "FERNÁNDEZ, Pedro" is a name not an ID: dropping the trailing "Z" seems adhoc/random to me. @Pigsonthewing: if the URL structure changes, we can fix that with a bot. IMHO that's better than complicating formatterURL beyond recognition to cope with complex and unclear rules of a single authority. --Vladimir Alexiev (talk) 10:01, 11 May 2015 (UTC)

@Vladimir Alexiev, Nastoshka, Magnus Manske, Jane023:   Done Web Gallery of Art ID (P1882) Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 19:07, 8 May 2015 (UTC)

@Pigsonthewing: The property shows Formatter URL https://tools.wmflabs.org/mix-n-match/api.php?query=redirect&catalog=11&ext_id=$1 , is that the new standard way? Going through Mix-n-match introduces an extra bottleneck and point of failure (eg Mix-n-match does not work right now). I think it's better to point directly to the WGA site. Note: the WGA URLs have to be in lowercase; http://www.wga.hu/html/f/FERNANDE does NOT work. --Vladimir Alexiev (talk) 10:08, 11 May 2015 (UTC)

I investigated some more WGA painters:

So I propose:

  • the ID to include all parts except the first repeated letter, eg bambaia, fernande/pedro, master/zunk_sp/zunk_cat, bierstad, meifren, platzer1, master/xunk_bo.
  • formatterURL to be extended with only this option: to repeat the first letter.

--Vladimir Alexiev (talk) 10:21, 11 May 2015 (UTC)

EAGLE id

   Done: EAGLE id (P1900) (Talk and documentation)
Descriptionidentifier of an epigraphic concept in EAGLE Vocabulary (Q19371183) (Europeana network of Ancient Greek and Latin Epigraphy)
RepresentsEAGLE Vocabulary (Q19371183)
Data typeString
Domainmaterials, types of inscriptions, object types (support of inscribed object), inscription writing/execution techniques, decoration types
Examplerostrum (Q13581079) -> objtyp/lod/1961
Sourcehttp://www.eagle-network.eu/resources/vocabularies/
Formatter URLhttp://www.eagle-network.eu/voc/$1
Robot and gadget jobsMix 'n' match is best suitable for this job
Discussion

MOVED FROM GENERIC PROPERTY PROPOSAL

Proposed by Pietromarialiuzzo (talk)

Motivazione Pietromarialiuzzo (talk) 15:53, 26 January 2015 (UTC) Vorrei rendere i vocabolari specifici dell'epigrafia creati dal progetto EAGLE accessibili a tutti collegandoli a wikidata perché altri progetti ne possano usufruire liberamente e per contribuire con questo lavoro alla missione di wikidata. Seguo un consiglio datomi a Berlino dal team di Wikidata a Settembre dello scorso anno, sebbene con ampio ritardo... spero di aver compilato il modulo di richiesta bene, ci sono molte cose che non capisco.

@Pietromarialiuzzo:

  • translate to English
  • Move to WD:PP/AUTH
  • "Represents Rostrum" is wrong. Make an item for "EAGLE repository" and quote in "subject item" above

--Vladimir Alexiev (talk) 15:25, 23 February 2015 (UTC)

Thanks @Vladimir Alexiev:, I am new here so, please help me to understand what is the best way I can do this. I am trying to explain this in a better way rather than translating if that is ok. I have been suggested buy the wikidata team to map our EAGLE project Vocabularies to Wikidata. We have only concept related to ancient epigraphy and I would like to add to corresponding items in Wikidata a link to our items, if that is fine. I would then add a property to these items to say "This is item as ID xxx in EAGLE". I am not sure if this is best practice for aligning vocabularies, please let me know if there is a different way to do this. I do not understand why I should create a EAGLE repository item and I do not know if I have done this alright, but I have tried to follow your suggestion. Thank you very much!--Pietromarialiuzzo (talk) 10:48, 2 March 2015 (UTC)

The repository item is so we have somewhere where we can explain what the EAGLE project is and can link the proposed property to this. Filceolaire (talk) 16:24, 2 March 2015 (UTC)

@Pietromarialiuzzo: All the above is clear, but we're trying to help you get it into better shape. It is getting better.

     <dc:description xmlns:dc="http://purl.org/dc/elements/1.1/"
                     rdf:about="http//:www.eagle-network.eu/resources/vocabularies/objtyp.html"/>

I think it should be rdf:resource, and the URL is malformed

  • And again, I suggest to move this whole section to WD:PP/AUTH

--Vladimir Alexiev (talk) 11:45, 4 March 2015 (UTC)

Thanks a lot @Vladimir Alexiev:, you have spotted many things indeed which tell you how much non expert I am. I really appreciate your help. I have no idea why that Tematres instance is still there, but is an old version which should not exist anymore that is also why you don't find there Rostrum. the skos vocabulary was exported from there and then updated as such abandoning tematres. The vocabularies are listed and described here: http://www.eagle-network.eu/resources/vocabularies/. They are:

Then each concept has a url in this form http://www.eagle-network.eu/voc/objtyp/lod/1961 (http://www.eagle-network.eu/voc/typeins/lod/1 and so on) where the number is unique and the part before lod instead is the name of the vocabulary as above. I am aware that the /lod/ bit is superfluous but for many reasons in our workflow we could not change that at this stage. I have now fixed the errors in the skos and next sunday it should be uploaded and ok. this should be uri and you can have the html or the rdf. I do not know turtle unfortunately but I will have a look at how to do it for sure. If you suggest to have many "coreferencing prop" that is also fine, please let me know what is the best and I am happy to go down that way. I have nothing at all also against moving this to WD:PP/AUTH but I do not know how to do it: cut and paste everything? Thank you very much indeed. yours --Pietromarialiuzzo (talk) 21:33, 4 March 2015 (UTC)

@Pietromarialiuzzo: thanks for moving it here.

  • Thanks for all clarifications! So now regarding this property: which of the 8 EAGLE thesauri is it representing? Or maybe you'd like to add more props, to represent more of the thesauri?
  • "Non-expert": you guys use a Wikidata instance (only the second project after Wikidata to do it), so I would guess there are more people in the project who can contribute to these discussions.

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

In my view they are not divided, what we want to say, somehow is "this is an epigraphic concept/item". but I am happy to split if necessary. @Sannita: is definitely our man on Wikidata! We use Wikibase for another aspect of EAGLE which is translations of inscriptions, but I think the rdf version of our vocabularies would be any way useful. Am I wrong? Thanks a lot! --Pietromarialiuzzo (talk) 09:05, 30 March 2015 (UTC)

@Vladimir Alexiev: @Pietromarialiuzzo: here I am! :) I'm really sorry to ping you this late, and to answer this late.
Yes, I'm part of the Wikimedia Italia team that helps the EAGLE team in understanding how to work with Wikibase. I think I can easily answer to the multiple vocabularies: I think it's better to create just one ID that may cover them all, so the value would be, for example, "objtyp/lod/333", the link in the .js "http://www.eagle-network.eu/voc/$1.html" and the result would be
< cowshed (Q681337)     > EAGLE vocabulary ID search < objtyp/lod/333 >
< hymn (Q484692)     > EAGLE vocabulary ID search < typeins/lod/65 >
< graffito (Q3567529)     > EAGLE vocabulary ID search < writing/lod/9 >
< amphibolite (Q335239)     > EAGLE vocabulary ID search < material/lod/43 >
...and so on. If you're ok with that, I can correct the request with all we discussed here. -- Sannita - not just another it.wiki sysop 15:41, 29 April 2015 (UTC)
Thank you very much @Sannita:! this would be perfect for me! --Pietromarialiuzzo (talk) 19:41, 29 April 2015 (UTC)
  Support @Sannita: It's a bit unusual to include the term type in the ID but why not. Will save you the trouble of having to define 8 IDs. If possible, please remove the word "lod/" since it's parasitic: the semantic URL of something should be COOLURI and not include technological terms. (A friend of mine called Miro some years ago made an email accont called miremail@somewhere.com: silly account name.) Can you rework your resolution to avoid it? --Vladimir Alexiev (talk) 06:26, 30 April 2015 (UTC)
@Vladimir Alexiev: Yeah, the "/lod/" part might seem silly, and it is probably better to drop it, but I can't rework it, it's something that EAGLE has to work. I'll forward the request, though. --Sannita - not just another it.wiki sysop 20:59, 1 May 2015 (UTC)
Just to notice that I fixed the info provided in the template. Sannita - not just another it.wiki sysop 14:38, 8 May 2015 (UTC)
Thanks to all, sorry for the late reply. We cannot for internal reasons at this stage remove lod/ although I agree that it should not be there at this point. There is a long story behind it which might not be entirely relevant here. is there something we can leave with? projects have been using the uri as they are, even if they are not 100% cool.. please let me know. thank you very much. --Pietromarialiuzzo (talk) 21:48, 18 May 2015 (UTC)

@Pietromarialiuzzo, Vladimir Alexiev, Sannita:   Done EAGLE id (P1900) (a round number!) Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 15:05, 26 May 2015 (UTC)

Added all examples above (plus Acanthus for decoration and Aemilianus for dating) to Property:P1900, hopefully soon they'll appear on Property_talk:P1900. @Sannita, Pietromarialiuzzo: http://www.eagle-network.eu/voc/statpreserv.html doesn't resolve, are you sure that's a valid EAGLE ConceptScheme? --Vladimir Alexiev (talk) 08:56, 29 May 2015 (UTC)

BALaT person/organisation id

Descriptionidentifier for person or organisation in the People & Institutions database of BALaT (Belgian Art Links & Tools), maintained by KIK-IRPA, Belgium's Royal Institute for Cultural Heritage.
Domainperson, organisation
Allowed valuesstring of numbers
ExamplePeter Paul Rubens (Q5599)364
Robot and gadget jobsMix'n'Match
Motivation

Extensive database of creators of artworks in Belgian institutions, maintained by Belgium's main cultural heritage research institute (Belgian equivalent of the Dutch RKD). Spinster (talk) 10:37, 3 May 2015 (UTC)

Discussion

@Spinster, T.seppelt:   Done BALaT person/organisation id (P1901) Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 15:34, 26 May 2015 (UTC)

Dictionary of Medieval Names from European Sources

DescriptionDictionary of personal names attested from medieval European sources, with slightly over 1,000 entries as of May 2015.
Representsgiven name (Q202444)
DomainGiven names
Allowed valuesP31 one of given name (Q202444), female given name (Q11879590), male given name (Q12308941), unisex given name (Q3409032)
ExampleAndrewAndrew (Q18042461)
Sourceexternal reference
Formatter URLhttp://dmnes.org/name/$1
Motivation

Wikidata currently has fairly good coverage of personal names, and a lot of work has been done to add given name values to biograhies. However, those name items themselves don't always link out to good authority/reference sources. DMNES should help fill this gap. @Magnus Manske: has set it up on mix-and-match pending an identifier. Andrew Gray (talk) 18:59, 4 May 2015 (UTC)

Discussion
  Support --Magnus Manske (talk) 19:34, 4 May 2015 (UTC)
  Support --T.seppelt (talk) 19:46, 4 May 2015 (UTC)

@Andrew Gray, Magnus Manske, T.seppelt:   Done (while sitting in a lounge at Frankfurt Airport (Q46033)!) Dictionary of Medieval Names from European Sources entry (P1888) Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 07:09, 15 May 2015 (UTC)

RSL periodical identifier

   Withdrawn
Descriptionidentifier of the Russian State Library for periodical
Data typeString
DomainQ1092563
Allowed valuesnine decimal digits
ExampleOtechestvennye Zapiski (Q2661947) => 004940962
Illustratsiya Magazine (Q15628819) => 003353086
Niva (Q4318426) => 007577122
Moskvityanin (Q685331) => 007567519
Computer Bild (Q445723) => 003392467 Iskatel' (Q4203834) => 002383305
Format and edit filter validation[0-9]{9}
SourceRSL catalog database
Formatter URLhttp://aleph.rsl.ru/F?func=find-b&find_code=SYS&local_base=xser&request=$1
Robot and gadget jobsMay be seached by ISSN: 2308-815X for Computer Bild (Q445723)
Motivation

The RSL ID (person) (P947) used for persones. But for magazines and other periodical is needed other property to change URL formatter (local_base=xser instead of local_base=RSL11).

This property may be used in a authority control templates for periodical. Also it helps to search a scanned issues at http://search.rsl.ru/ (e.g. try "@id 3353086" for the issues of Illustratsiya Magazine (Q15628819)). -- Sergey kudryavtsev (talk) 13:53, 8 May 2015 (UTC)

Discussion

I withdrawn this propose to start new one (see next section), more generic solution. -- Sergey kudryavtsev (talk) 07:38, 22 May 2015 (UTC)

Biblioteca Nacional de Chile author identifier

   Done: BNC ID (P1890) (Talk and documentation)
Descriptionsubject's Biblioteca Nacional de Chile authority control number
RepresentsCollective Catalog of Bibliographic Authorities of Chile (Q19896851)
Data typeString
Template parametercommons:Template:Authority control (not included)
Domainpeople, authors, politicians, newspaper editors...
Allowed values9 digits, suffixed by another digit
Example
Format and edit filter validation8 digit number can be validated with edit filter Special:AbuseFilter/17
SourceBiblioteca Nacional de Chile
Formatter URLhttp://www.bncatalogo.cl/F?func=direct&local_base=red10&doc_number=$1
Motivation

I personally feel Chilean stuff is under represented (in properties of Wikidata). The Catalogo of Chile's National Library contains valuable information of a large number of people, from Chile and abroad. Diego Grez (talk) 20:11, 11 May 2015 (UTC)

Discussion

@Diego Grez, Sergey kudryavtsev, Kolja21:   Done BNC ID (P1890) Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 11:45, 21 May 2015 (UTC)

Ministry of Education of Chile school ID number

Template parameteren:Template:InfoEscuela
Domainschool, high school, middle school, primary school
Allowed valuesNumbers only (up to 5 digits)
Robot and gadget jobsThere are lists of all schools with RBDs, we could match them up with schools that have an item on Wikidata, and have a bot add them to each.--Diego Grez (talk) 15:05, 18 May 2015 (UTC)
Motivation

This is the definite source of information about schools in Chile, it contains every single one of them, and we should use it as a source. Diego Grez (talk) 15:05, 18 May 2015 (UTC)

Discussion
  Comment en:Template:InfoEscuela has no documentation page and is - since 2012 - only use by 1 article. The link to www.mime.mineduc.cl only produces: wait ... wait ... wait ... but no result. --Kolja21 (talk) 20:31, 18 May 2015 (UTC)
The website works for me, perhaps it has a restriction on foreign countries... I don't know. --Diego Grez (talk) 03:53, 19 May 2015 (UTC)
Website works for me (currently in Barcelona). Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 07:39, 19 May 2015 (UTC)

@Diego Grez, Kolja21:   Done Ministry of Education of Chile school ID (P1919) Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 20:07, 30 May 2015 (UTC)

Librivox author ID

DescriptionAuthor ID for an author represented at LibriVox (Q1070969)
Data typeString
Domaininstance of (P31): human (Q5)
Allowed values[0-9]+
ExampleCharles Leale (Q2959615)8423
Format and edit filter validationunknown
Sourceexternal reference
Formatter URLhttps://librivox.org/author/$1
Motivation

Librivox is already linked to from Wikipedia and Wikisource. I believe to cut down on redundancy we can use Wikidata. Hazmat2 (talk) 12:50, 20 May 2015 (UTC)

Discussion

@Hazmat2:   Done LibriVox author ID (P1899) Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 14:31, 26 May 2015 (UTC)

hair color

   Done: hair color (P1884) (Talk and documentation)
Descriptionmodel's/person's hair color
Data typeItem
Template parameter"hair_color" (en:Template:Infobox model), "cheveux" (fr:Modèle:Infobox Mannequin), possibly others on Template:Infobox model (Q5833821)
Domainperson (Q215627)
Allowed valuesitems for hair colors
ExampleIman (Q256531): brown hair (Q2367101) ; Kristen Bell (Q178882): blond (Q202466)
Discussion

To import from the above infoboxes. --- Jura 16:45, 17 January 2015 (UTC)

  •   Oppose this is not property to apply on persons. If you want to use it, you should name it "natural hair colour" as everything else can change every week. But does anyone know the natural hair colour of models? H2O2 made Marylin Monroe a blonde and after a time every natural hair colour is fifty shades of grey.--Giftzwerg 88 (talk) 13:04, 21 January 2015 (UTC)
    • Is there an issue with the infoboxes above that are being used at Wikipedia? Is there a problem with the editorial choices of English and French Wikipedia? Do we have to correct from Wikidata? --- Jura 18:37, 21 January 2015 (UTC)
  •   Comment BTW, one can use "point in time" as qualifier. --- Jura 18:37, 21 January 2015 (UTC)
in order to get longer lists also propose "colour of strands", good luck with Cyndi Lauper (Q1545). Not even god knows all the colours and points in time.--Giftzwerg 88 (talk) 16:13, 24 January 2015 (UTC)
Is there an article about her with one of the above infoboxes? BTW, please respond to the above qeustions: Is there a problem with the editorial choices of English and French Wikipedia? Do we have to correct from Wikidata? --- Jura 19:05, 28 January 2015 (UTC)
For sure I don´t know, if there are any issues with the English or French Wikipedia, because I´m not involved in the editorial choices.--Giftzwerg 88 (talk) 22:26, 31 January 2015 (UTC)
Your opposition to importing their infobox data challenges their editorial choices. --- Jura 05:28, 10 February 2015 (UTC)
  Comment eye color (P1340) exists. Matěj Suchánek (talk) 17:02, 1 March 2015 (UTC)
  Weak support Per talk at Wikidata:Property proposal/Archive/23#eye color. I am afraid this data will be criticized repeatedly and maybe even removed. Let's give it a try, after all it describes people the same way as eye color (P1340). Matěj Suchánek (talk) 17:38, 11 March 2015 (UTC)
  •   Weak support I agree with Matěj Suchánek. Let's give it a try, and see whether modification of this property is needed. --Милан Јелисавчић (talk) 08:38, 12 March 2015 (UTC)
  •   Support. This is a basic property of the appearance of humans, many types of non-human animal, and fictional entities. Jura, I have broadened the domain of this property to accommodate using it on non-human animals -- please revert if you disagree and we can discuss! Emw (talk) 02:44, 13 March 2015 (UTC)
    • Let's keep it to humans. It's seems already complicated enough to get this created. --- Jura 04:26, 13 March 2015 (UTC)
  •   Support. in cases where there is a real dispute we have the tools to represent that dispute or we can omit the hair colour (or color) in those cases. Filceolaire (talk) 13:19, 13 March 2015 (UTC)
  •   Support as "natural hair color". Please, natural. --AmaryllisGardener talk 00:06, 25 March 2015 (UTC)
    • Ideally, I'd agree, but that would make it difficult to verify and it might not be what one is looking for. A qualifier could do to specify "natural color" --- Jura 08:14, 25 March 2015 (UTC)

DNB entry at Wikisource

   Withdrawn
Descriptionitem with DNB entry at Wikisource
RepresentsDictionary of National Biography (Q1210343)
Data typeItem
Domainpersons
Allowed valuesitems with sitelinks to Wikisource entries with DNB source text
  Inverse property of “main subject (P921):
if [item A] has this property (Property proposal/Archive/31) linked to [item B],
then [item B] should also have property “main subject (P921)” linked to [item A].
List of this constraint violations: Database reports/Constraint violations/Property proposal/Archive/31#Inverse, hourly updated report, SPARQL
  Target items of "PROPERTY PROPOSAL/ARCHIVE/31 (Property proposal/Archive/31)" should have a statement with "part of (P361)" and value "Dictionary of National Biography (Q1210343)": If [item A] has this property with value [item B], [item B] is required to have property "part of (P361)" with value "Dictionary of National Biography (Q1210343)"
List of this constraint violations: Database reports/Constraint violations/Property proposal/Archive/31#Target required claim P361 = Q1210343, hourly updated report, SPARQL
  Target items of "PROPERTY PROPOSAL/ARCHIVE/31 (Property proposal/Archive/31)" should have a statement with "instance of (P31)" and value "biography (Q36279)": If [item A] has this property with value [item B], [item B] is required to have property "instance of (P31)" with value "biography (Q36279)"
List of this constraint violations: Database reports/Constraint violations/Property proposal/Archive/31#Target required claim P31 = Q36279, hourly updated report, SPARQL
  Item: items with this property should also have instance of (P31) = human (Q5)
List of this constraint violations: Database reports/Constraint violations/Property proposal/Archive/31#Item P31 = Q5, hourly updated report, SPARQL
ExampleTerence Albert O'Brien (Q2649185) => O'Brien, Terence Albert (DNB00) (Q19080926); John Bird Sumner (Q549733) => Sumner, John Bird (DNB00) (Q19070399);
Sources:Category:DNB biographies (30690 entries)
  •   Oppose. In general each person has one wikidata item so the DNB wikisource page about a person should link to the same wikidata item as the wikipedia articles about that person. Use described by source (P1343) instead - see Q19049325. Filceolaire (talk) 00:38, 22 March 2015 (UTC)
  •   Comment Wikisource can have multiple entries about the same person, taken from various reference works (Catholic encyclopedia, Brittanica, DNB, each of which can have multiple editions). This property needs to be made more general so it can be used to link to all of these entries, with a qualifier to indicate the work it is from. We probably also need a symmetric property to link back the other way. Filceolaire (talk) 16:33, 22 March 2015 (UTC)
    • Does Wikisource not have a higher-level page, or category, for all such works by and or about an individual? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 16:37, 22 March 2015 (UTC)
      Good question imo. Visite fortuitement prolongée (talk) 20:34, 22 March 2015 (UTC)
      Agree. The author pages? --- Jura 15:05, 24 March 2015 (UTC)
      English Wikisource, anyway, is quite weak on "topic classification". The category system is primarily there to classify the types of texts, not their content. Disambiguation pages exist, but are sparse compared to English Wikipedia, which is therefore not a specially helpful analogy.
      The actual construction that applies generally is the use of the Portal: namespace. In that context the Author: namespace pages are the special case of authors, treated somewhat more systematically. For an individual person, not an author, a dedicated page hovers perhaps between a disambiguation page (in mainspace, which should go by title of work really), and an actual Portal:.
      So things are not in great shape, really. A potential application of Wikidata is to use the related "main subject" item here as the key to the compilation of a better solution "page", which could be on a "portal tool". Charles Matthews (talk) 17:10, 24 March 2015 (UTC)
      Wikidata is here to structure content of other Wikimedia sites, so generating an index for DNB should be within its capabilities. --- Jura 17:20, 24 March 2015 (UTC)
    • Here is somebody with multiple item: Terence Albert O'Brien (Q2649185), O'Brien, Terence Albert (DNB00) (Q19080926), Terence Albert O'Brien (Q19657243). Visite fortuitement prolongée (talk) 20:34, 22 March 2015 (UTC)
      • The immediate problem is that they all have the label (in English, at least) "Terence Albert O'Brien" whereas one should have the label, say, "Dictionary of National Biography biography of Terence Albert O'Brien" and another "Catholic Encyclopedia biography of Terence Albert O'Brien". Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 20:36, 24 March 2015 (UTC)
        • Yeah, it's a pity this wasn't planned out before they were created. But where the only sitelink fits that WS pattern, it would be easy enough for a bot to change the labels along with setting the right properties (instance of: whatever) Andrew Gray (talk) 21:36, 24 March 2015 (UTC)
    • For the symmetric property, Sumner, John Bird (DNB00) (Q19070399) has already instance of (P31) biography (Q36279) and main subject (P921) John Bird Sumner (Q549733), it could be sufficient. And maybe a computed symmetric of that would be sufficient, without the need to create a "DNB entry at Wikisource" property. Visite fortuitement prolongée (talk) 20:34, 22 March 2015 (UTC)
  •   Comment I added a proposal for CE at Wikisource below and completed this proposal with some of the constraints. --- Jura 15:05, 24 March 2015 (UTC)
  •   Oppose, but   Support for a more generic property which can deal with all reference works (Catholic encyclopedia, Brittanica, DNB, ...) and their various editions.--Pasleim (talk) 21:04, 29 March 2015 (UTC)

Catholic Encyclopedia entry at Wikisource

   Withdrawn
Descriptionitem with Catholic Encyclopedia (CE) entry at Wikisource
RepresentsCatholic Encyclopedia (Q302556)
Data typeItem
Domainpersons
Allowed valuesitems with sitelinks to Wikisource entries with CE source text
  Inverse property of “main subject (P921):
if [item A] has this property (Property proposal/Archive/31) linked to [item B],
then [item B] should also have property “main subject (P921)” linked to [item A].
List of this constraint violations: Database reports/Constraint violations/Property proposal/Archive/31#Inverse, hourly updated report, SPARQL
  Target items of "PROPERTY PROPOSAL/ARCHIVE/31 (Property proposal/Archive/31)" should have a statement with "part of (P361)" and value "Catholic Encyclopedia (Q302556)": If [item A] has this property with value [item B], [item B] is required to have property "part of (P361)" with value "Catholic Encyclopedia (Q302556)"
List of this constraint violations: Database reports/Constraint violations/Property proposal/Archive/31#Target required claim P361 = Q302556, hourly updated report, SPARQL
  Target items of "PROPERTY PROPOSAL/ARCHIVE/31 (Property proposal/Archive/31)" should have a statement with "instance of (P31)" and value "biography (Q36279)": If [item A] has this property with value [item B], [item B] is required to have property "instance of (P31)" with value "biography (Q36279)"
List of this constraint violations: Database reports/Constraint violations/Property proposal/Archive/31#Target required claim P31 = Q36279, hourly updated report, SPARQL
ExampleTerence Albert O'Brien (Q2649185) => Terence Albert O'Brien (Q19657243)
Sources:Category:CE biographies (11579 entries)
Discussion
  • @Andrew Gray, Charles Matthews, Filceolaire, Visite fortuitement prolongée, Pigsonthewing:: This in addition to the DNB property above. --- Jura 15:05, 24 March 2015 (UTC)
  •   Oppose. Use described by source (P1343) instead.  – The preceding unsigned comment was added by Filceolaire (talk • contribs) at 25.04.2015, 13:26 (UTC).
    • I stroke out the above vote as it wasn't signed. Pasleim undid that and signed it for Filceolaire today. --- Jura 08:19, 18 April 2015 (UTC)
  •   Comment but then described by source (P1343) is "Recommended only for printed dictionaries and encyclopedias." "[..] so better to avoid described by source (P1343) for online resources". --- Jura 02:52, 1 April 2015 (UTC)
    •   Comment: The source is a printed encyclopedia that has been transcribed at Wikisource. We currently use the method as described. However, the downside is that there is no direct link to its entry transcribed at WS. Hazmat2 (talk) 16:46, 1 April 2015 (UTC)
      • Well, it seems to be primarily for offline resources. As qualifiers are only partially supported, any solution that relies on them is only marginally helpful. --- Jura 08:28, 2 April 2015 (UTC)
  •   Oppose. If described by source (P1343) doesn't fit create a property for "online sources" of more general use instead. -- Blackcat (talk) 08:25, 13 April 2015 (UTC)
  •   Comment What about links to http://www.newadvent.org/cathen/ like http://www.newadvent.org/cathen/11193d.htm for Terence Albert O'Brien (Q2649185) and/or Terence Albert O'Brien (Q19657243)? en:WP records about 10.500 of them thus coverage of "newadvent" CE identifiers also might be almost complete. However the main point seems to be that we can (must?) state but really would need the inverse property specifically for this encyclopedia. @Pasleim: do you have any ideas for the "more generic approach" you proposed at the DNB proposal above? -- Gymel (talk) 00:44, 18 April 2015 (UTC)
    • From User talk:Pasleim#Property_proposal, it seems he just opposes it, but doesn't actually want to sort things out. Maybe Blackcat will do it. If we keep waiting, the Wikisource stuff might eventually become problematic. People keep mixing it into items with P31:Q5. --- Jura 05:52, 18 April 2015 (UTC)
      • @Jura1: I want to sort things out, thats why I support a more generic property. But from [1] it seems that you're just not interested in this approach. --Pasleim (talk) 07:40, 18 April 2015 (UTC)
        • No, I'm not interested in the approach you suggest (and don't practice either). --- Jura 07:55, 18 April 2015 (UTC)
    • @Gymel: I would strike out the words Catholic Encyclopedia and DNB and call the property something like reference work entry at Wikisource with a mandatory qualifier of (P642) with possible values Dictionary of National Biography (Q1210343), Catholic Encyclopedia (Q302556), Dictionary of Christian Biography and Literature to the End of the Sixth Century (Q5273965), A Dictionary of Saintly Women (Q19021230) etc. There are many more reference works at Wikisource. Creating a new property for each of these works is just exhausting. --Pasleim (talk) 07:40, 18 April 2015 (UTC)
      I think one should review the handling of reference works in wikidata in broad generality, the time would be right to carry thogether what properties still missing for that purpose could be and craft a "Best Current Practice". Based on that it should be relatively easy to deal with the special case of "wikisource editions" of reference works: The main difference being that we do not only have citations plus an URL for the content but also a corresponding wikidata item and in theory information in the reference article item should help us to reduce qualifying information in the respective reference recorded in the subject item.
      Eventually wikidata will probably have a certain amount of items on their own for reference articles outside of wikisource (having identifyable authors is only one reason I can think about for making them notable here), thus I would say that having a separate item is the peculiar point in our situation, not the fact that the edition is hosted by some wikimedia project... -- Gymel (talk) 08:28, 18 April 2015 (UTC)
      • Not sure if its worth breaking these entries done into the equivalent of thousands of reference items. With dedicated properties, most information about these works could actually remain on the property itself. --- Jura 15:11, 21 April 2015 (UTC)
      • I'm usually fine with dedicated properties: A discussion takes place and users settle on the appropriate form of recording reference fragments. With items silly situations like the following might go unnoticed: Dictionary of Art Historians (Q17166797) is a purely online reference work and my impression is that it's entries are referenced completely by wikidata items. Unfortunately this is done by means of where frag is the individual string for insertion into https://dictionaryofarthistorians.org/$1.html to access the article on x. Thus we have all the data for that online dictionary, but no links at all (and currently not even any means to export the qualifier data)!
      However the discussion here is about one reference source existing in several independent (and slightly differing?) versions on the web: In that case I consider different (and therefore independent) properties as not being an optimal solution. -- Gymel (talk) 21:21, 22 April 2015 (UTC)

Declarator.org ID

DescriptionPerson ID on Declarator.org database
Data typeString
Domaintypes of items that may bear this property
Allowed values\d+
ExampleVladimir Putin (Q7747) => 582
Formatter URLhttp://declarator.org/person/$1/
Discussion

Declarator.org is a database of income of Russian officials, maintained by Transparency International. Now it has about 9000 records. —putnik 16:39, 17 April 2015 (UTC)

represented by

   Done: represented by (P1875) (Talk and documentation)
DescriptionTo be used to express a relationship between a person and his/her agency, such as:
  • a contemporary artist and his/her art gallery
  • a fashion model and his/her modeling agency
Data typeItem
Domainhuman (Q5), group of humans (Q16334295)
Allowed valueshuman (Q5), group of humans (Q16334295) (an agent can also be an individual person)
ExampleTyra Banks (Q172303) represented by Elite Model Management (Q616374); Michaël Borremans (Q284808) represented by Zeno X (Q4473899)
Sourceexternal reference
Discussion

Proposed by: Spinster (talk)

The most similar properties I found, were member of (P463) (just doesn't feel right) and affiliation (P1416), which comes close, but seems not 100% appropriate. Spinster (talk) 12:21, 20 April 2015 (UTC)

  •   Support - Jane023 (talk) 12:45, 20 April 2015 (UTC)
  •   Comment A record label does not represent an artist; their manager or agent does. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 18:04, 20 April 2015 (UTC)
    • Agreed, but these managers and agents are probably less notable than record labels? In any case, I removed these as a possible use case for this property - we might need a separate property for the relation between a musical artist and record label then. Spinster (talk) 10:55, 21 April 2015 (UTC)
  •   Support. Filceolaire (talk) 07:13, 22 April 2015 (UTC)
  •   Support. This property would be a subproperty of (P1647) member of (P463). Good idea. Emw (talk) 23:00, 22 April 2015 (UTC)
Emw, Spinster I'm not sure this is a subproperty of 'member of'. Football players for instance are members of (effectively employees of) a football club and are paid by the club. They also have agents who act on their behalf/represent them in negotiations with clubs and sponsors. Agents collect a percentage of the fees and can be said to be paid by/employed by the players that they represent. I can see a real distinction here between member of and represented by.
This is confused by consultancy type organisation where the 'consultants' are employed by the consultancy. The consultancy then sends the consultants to advise clients so the consultants seems to be sort of 'represented by' the consultant but I think that relationship is better represented by employer (P108) aka 'employed by'. Filceolaire (talk) 19:35, 23 April 2015 (UTC)

@Spinster, Jane023, Filceolaire, Emw:   Done represented by (P1875) Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 19:03, 1 May 2015 (UTC)

Spotify artist ID

Motivation

Spotify is a very popular music streaming service and linking Artists to it is a good start. As Netflix ID (P1874) exists and Spotify has roughly the same position as Netflix on it's market I thought it should be motivated.  – The preceding unsigned comment was added by Pajn (talk • contribs).

Discussion

@Pajn:   Done Spotify artist ID (P1902) Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 15:41, 26 May 2015 (UTC)

Signatory

   Done: signatory (P1891) (Talk and documentation)
Descriptiona person, country, or organization that has signed an official document
Data typeItem
Template parameter|signers=, in en:Template:Infobox document
Domaindocument (Q49848) and its subclasses
Allowed valuesitems with instance of human (Q5)
ExampleU.S. Declaration of Independence (Q127912) signatory: Benjamin Harrison V (Q387664), Edward Rutledge (Q878666), Benjamin Franklin (Q34969), et al.
Sourceitem, external reference
Robot and gadget jobsIf an inverse property is made, then a robot can check for inverse relationships
Motivation

Between Wikipedia and Wikisource, we are starting to gather many official documents or references to documents. Signatories are key pieces of information. Hazmat2 (talk) 19:35, 12 May 2015 (UTC)

Discussion
  Support --Pasleim (talk) 12:27, 15 May 2015 (UTC)
  Support --Kolja21 (talk) 17:42, 15 May 2015 (UTC)
  Support--Oursana (talk) 22:00, 15 May 2015 (UTC)

@Hazmat2, Pasleim, Kolja21, Oursana, Filceolaire:   Done signatory (P1891) Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 11:59, 21 May 2015 (UTC)

coach

   Withdrawn
Descriptionperson that is the head coach for the sportsperson
Representscoach (Q41583)
Data typeItem
Template parameter|coach=, in en:Template:Infobox tennis biography
Domainathlete (Q2066131)
Allowed valuespeople
ExampleSabine Lisicki (Q76338)Richard Lisicki (Q17290600)
SourceATP website, Wikipedia
Motivation

Useful info. --AmaryllisGardener talk 21:57, 21 May 2015 (UTC)

Discussion
similar to head coach (P286) especially because most language labels, except the English one, do not restrict that property to teams. --Pasleim (talk) 07:47, 22 May 2015 (UTC)
In some sports, team managers are also called "coach". Suggest to re-label head coach (P286). Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 09:57, 22 May 2015 (UTC)
Relabelling head coach (P286) would solve the problem. Could we relabel it to "head coach" or "coach" and have "team manager" as an alias? --AmaryllisGardener talk 14:29, 22 May 2015 (UTC)
+1 --Pasleim (talk) 14:43, 22 May 2015 (UTC)
Ok, I boldly changed the label. --AmaryllisGardener talk 19:26, 22 May 2015 (UTC)
@AmaryllisGardener: Thank you. Would you like to withdraw this proposal, now? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 20:11, 22 May 2015 (UTC)
Yes. I'm not sure how to change the template, but withdrawn. --AmaryllisGardener talk 21:38, 22 May 2015 (UTC)

Australian Dictionary of Biography (ADB)

Data typeString
Template parameter|id2=, in en:Template:Australian Dictionary of Biography
Domainpeople
Allowed valuesstring with [A-Z,0-1] and "-"
SourceTemplate:Cite Australian Dictionary of Biography (Q6703319)
  •   Comment This facilitates importing the template data from Wikipedia. --- Jura 04:56, 22 May 2015 (UTC)
  Support --Pasleim (talk) 07:48, 22 May 2015 (UTC)

@Jura1, Pasleim:   Done Australian Dictionary of Biography ID (P1907) Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 20:13, 29 May 2015 (UTC)

Commonwealth War Graves Commission person identifier

   Done: CWGC person ID (P1908) (Talk and documentation)
Template parameter|id=, in en:Template:CWGC
DomainBritish Commonwealth military personnel
Allowed valuesvalid CWGC URL stems
Motivation

CWGC website has details of individuals' burials (or commemorations if no body was found) and service records. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 18:03, 22 May 2015 (UTC)

Discussion

  Done CWGC person ID (P1908) Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 20:21, 29 May 2015 (UTC)

Goals and Games

   Not done
DescriptionGoals for goals which a handball player etc. shoot in a contest.
Games for games which a handball player etc. played ad a contest.
Data typeNumber (not available yet)
Template parameter"nationalcaps(goals)" in en:Template:Infobox handball biography; "länderspiele (tore)" in de:Template:Infobox Handballer
Domainpersons, teams and contest
Allowed valuespositive number
ExampleAndy Schmid (Q527482) => 140?
SourceWikipedia?
Motivation

So I can build a infobox for handball players which is based on the dates of the wikidata project. --Malo95 (talk) 15:41, 30 May 2015 (UTC)

Discussion

@Malo95: The description seems confusing to me. Do you mean the number of goal scored by a given player or the number of attempts/throws including the misses and the throws blocked by the goal keeper ? For the number of goal scored, we already have number of points/goals/set scored (P1351) and points for (P1358). --Casper Tinan (talk) 16:10, 30 May 2015 (UTC)

@Casper Tinan: Thank you for your answer it was exactly what I searched. But I didn't found it. Thank you. So my proposal can be deleted. --Malo95 (talk) 12:54, 31 May 2015 (UTC)

Not done; withdrawn. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 19:04, 31 May 2015 (UTC)

cathedral

Discussion
Can you propose a more general property ? This is ready specific. Snipre (talk) 13:54, 25 November 2014 (UTC)
I propose seat. The original request is really referring to the seat of a religious administrative entity like a diocese/eparchy/etc. To keep it religious, we would need to broaden the domain to also include diocese (Q665487) or similar, and broaden the allowed values to all place of worship (Q1370598). Or we can go much broader and let it also cover county seat (Q62049), municipality seat (Q15303838), etc. Sweet kate (talk) 18:12, 25 November 2014 (UTC)
done --Чаховіч Уладзіслаў (talk) 18:53, 25 November 2014 (UTC)
  Support with these changes. (I also tweaked the English description above since I wrote it in the first place.) I'd suggest aliases "seat" and "home church." Sweet kate (talk) 15:22, 26 November 2014 (UTC)
  Comment why not headquarters location (P159)? Apohllo (talk) 00:23, 16 January 2015 (UTC)
Diocese of Minsk and Slutsk (Q1974198) => cathedral: Holy Spirit Cathedral (Q2588857)
Diocese of Minsk and Slutsk (Q1974198) => headquarters location (P159): Building of the Minsk diocesan administration (Q18785146)--Чаховіч Уладзіслаў (talk) 12:26, 16 January 2015 (UTC)
Чаховіч Уладзіслаў could you please provide examples that have at least English titles? It's hard to understand the arguments without them. Apohllo (talk) 14:35, 16 January 2015 (UTC)
No, unfortunately. I added a translation. --Чаховіч Уладзіслаў (talk) 20:40, 16 January 2015 (UTC)
  Support It makes sense. Still I am a bit concerned with the English label. Apohllo (talk) 14:52, 17 January 2015 (UTC)
  Support Should mention an optional P794 (P794) qualifier to also add a pro-cathedral (Q1649060), co-cathedral (Q2577114) or metropolitan cathedral (still needs its own item, Metropolitan cathedral (Q1173650) is a disambig or actually list of metropolitan cathedrals). Ahoerstemeier (talk) 21:00, 27 April 2015 (UTC)

FundRef registry name

   Done: no label (P1905) (Talk and documentation)
Descriptionstandardised name, in the FundRef taxonomy of funder names
RepresentsFundref registry (Q19822542)
Data typeString
Domainorganisations
Allowed valuesEntries in the FundRef registry
ExampleEuropean Geosciences Union (Q1376656) => European Geosciences Union
SourceRDF and CSV files available under CC0 from http://www.crossref.org/fundref/fundref_registry.html
Robot and gadget jobsA Mix & Match job or similar could import the entire RDF file.
Discussion

FundRef's standardised "Funder Names" are used by Crossref (Q5188229); see [2]. Once populated, I will approach CrossRef and suggest that they reciprocally add Wikidata IDs to their database.

@Magnus Manske, Daniel Mietchen: Should the datatype by monolingual? The RDF file gives language codes, e.g. <skosxl:literalForm xml:lang="de">Deutscher Akademischer Austausch dienst</skosxl:literalForm>

Proposed by: Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 08:51, 21 April 2015 (UTC)

  Support Funny that you should propose this now — I was playing around with the list on Monday and had planned to propose the property over the weekend. While the CSV is basically monolingual per entry, the RDF typically has at least one English name (sometimes more, e.g. for China Primary Health Care Foundation) in addition to the name in the local language. I could thus see arguments in favour of both mono- and multinigual text, but think it would be better to go with monolingual and handle the language information by way of Wikidata descriptions and aliases. Plus, it would be useful to add the FundRef DOI to the corresponding items (example: International University of Korea (Q6054165)). --Daniel Mietchen (talk) 19:50, 24 April 2015 (UTC)

@Daniel Mietchen:   Done P1905 (P1905) Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 14:29, 27 May 2015 (UTC)

@Magnus Manske: Would this work on Mix&Match? RDF and CSV files available under CC0 from http://www.crossref.org/fundref/fundref_registry.html Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 14:36, 27 May 2015 (UTC)
Well, I have some data ready to import from the CSV; however, (a) mix'n'match does handle IDs, not monolingual strings, and (b) wouldn't the ID be 501100001649? --Magnus Manske (talk) 21:47, 27 May 2015 (UTC)
I'm fine with switching it to multilingual. As for the IDs, I think we can just use DOI (P356), so "10.13039/501100001649" for the case above. --Daniel Mietchen (talk) 22:43, 27 May 2015 (UTC)
@Magnus Manske: If we have a property for their IDs, yes, but this is "standardised name, in the FundRef taxonomy of funder names". Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 19:57, 28 May 2015 (UTC)

office held by head of state

Descriptionpolitical office that is fulfilled by the head of state of this item
Data typeItem
Domaininstances of administrative territorial entity (Q56061)
Allowed valuesinstances of position (Q4164871)
ExampleIsrael (Q801)President of Israel (Q327948)
Sourceexternal reference, Wikipedia list article, etc.
Motivation

See also office held by head of government (P1313), created a year ago. A similar option should exist for heads of state. --Yair rand (talk) 19:59, 18 May 2015 (UTC)

@Yair rand:   Done office held by head of state (P1906) Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 14:44, 27 May 2015 (UTC)

Participating team

DescriptionLike 'Participant' (P1344) but for teams. For an event like a cycle race or a football match you can use this property to list the teams and P1344 to list the individuals (with 'member of sports team' (P54)' as a qualifier for the individuals)
Data typeItem
Template parameterWikipedia infobox parameters, if any; ex: "population" in en:template:infobox settlement
Domainsports competitions and leagues
Allowed valuessports teams, Olympic teams
Example2014 FIFA World Cup Final (Q15926885)Argentina national football team (Q79800)
Format and edit filter validation(sample: 7 digit number can be validated with edit filter Special:AbuseFilter/17)
Sourceexternal reference, Wikipedia list article, etc.
Robot and gadget jobsShould or are bots or gadgets doing any task with this? (Checking other properties for consistency, collecting data, etc.)
Motivation

needed to complete info for football matches, cycle races, formula 1 races, Olympic events and other sports competitions where you need to record the results for each individual but also the results for the team. Filceolaire (talk) 00:00, 24 May 2015 (UTC)

Discussion

Danish urban area code

Descriptionidentifier for an urban area in Denmark
Data typeString
Domainurban areas
Allowed values5 digits, \d{5}
Example01100 for Copenhagen (Q1748), 10040 for Roskilde (Q26563)
Sourcehttp://www.statistikbanken.dk/BY1, da:Skabelon:Metadata Indbyggertal DK. Format: mmm-uuuuu. mmm is municipality code (Denmark) (P1168)
Motivation

Easier way to map data from external sources like Statistics Denmark to wikipedia articles. Steenth (talk) 21:50, 2 May 2015 (UTC)

Discussion

  Support --Laketown (talk) 20:23, 19 May 2015 (UTC)

@Steenth, Laketown, Thryduulf, Innocent bystander, Pasleim:   Done Danish urban area code (P1894) Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 14:16, 21 May 2015 (UTC)

OpenPlaques plaque identifier

DescriptionThe OpenPlaques identifier for a commemorative plaque on a building or other structure
Data typeString
DomainBuildings; other structures
Allowed valuesValid OpenPlaques URL stems for plaques
ExampleBirmingham Repertory Theatre (Q4916786)1576
Sourcehttp://openplaques.org/
Formatter URLhttp://openplaques.org/plaques/$1
Motivation

Not to be confused with OpenPlaques subject ID (P1430), which is for the subject of plaques. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 16:18, 9 May 2015 (UTC)

Discussion

@Filceolaire, Pasleim:   Done OpenPlaques plaque ID (P1893) Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 13:50, 21 May 2015 (UTC)

Commonwealth War Graves Commission burial ground identifier

Template parameter|id= and |name=, in en:Template:CWGC cemetery
Domaincemeteries or churches/churchyards
Allowed valuesstrings comparing a number and a text sting, separated by a slash
Motivation

CWGC website has details of individual burials. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 15:44, 22 May 2015 (UTC)

Discussion
  • The mere number doesn't seem to work. Looks much like an url. Maybe the url-datatype would be better. --- Jura 10:06, 24 May 2015 (UTC)
    • This is not a proposal to use a "mere number". Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 15:17, 27 May 2015 (UTC)
      • Yes, this is why I didn't like it. From the template at enwiki it seems that it's sufficient to change the formatter url to make it possible to use only the number. --- Jura 20:34, 29 May 2015 (UTC)
        I'd go ahead and create it as a mere number. Otherwise CWGC person ID (P1908) lacks its companion. --- Jura 13:02, 30 May 2015 (UTC)

@Jura1:   Done CWGC burial ground ID (P1920) Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 20:23, 30 May 2015 (UTC)

Given that there seems to have been a misunderstanding about the definition of this property, I asked it to be deleted at Wikidata:Properties_for_deletion#Property:P1920. Once resolved, we can create it. --- Jura 06:34, 1 June 2015 (UTC)

orbiter

   Done: vessel (P1876) (Talk and documentation)
Descriptionspacecraft used on this space mission
Representsspacecraft (Q40218)
Data typeItem
Allowed valuesinstances of spacecraft (Q40218) (ex.: Columbia, Discovery,... )
ExampleSTS-1 (Q217543) -> spacecraft -> Columbia (Q54383)
Soyuz TMA-8 (Q1231148) -> spacecraft -> Soyuz-TMA (Q2425489)
SourceNasa web site, other
Proposed byAdert (talk)
Discussion

I think it is indispensable for the space shuttle's missions Adert (talk) 00:05, 28 February 2015 (UTC)

  •   Support - Cleaned up some of the details, added an example, English label/desc. Josh Baumgartner (talk) 21:17, 2 March 2015 (UTC)
  •   SupportIvan A. Krestinin (talk) 21:28, 2 March 2015 (UTC)
  • Comment. Needs a more inclusive name. Not every mission may orbit (consider, for example, lunar, Martian or asteroid exploration). We might even widen this to voyages in ships or planes. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 23:51, 6 March 2015 (UTC)
    • Then, "Spacecraft"?? --Adert (talk) 13:18, 7 March 2015 (UTC)
  •   Support if you call it "spacecraft" --Pasleim (talk) 07:45, 26 April 2015 (UTC)
    • Ok! --Adert (talk) 19:47, 3 May 2015 (UTC) *I update the template --Adert (talk) 20:01, 3 May 2015 (UTC)

@Adert, Joshbaumgartner, Ivan A. Krestinin, Pasleim:   Done vessel (P1876) Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 20:04, 3 May 2015 (UTC)

not-a-taxon-name

   Not done
Descriptionintended for scientific names that once were published, but that may not be used for a taxon (no matter what taxonomy is followed): such as later homonyms, combinations with later homonyms, etc
Data typeString
Allowed valuesscientific names
ExamplePachyneurum J.J.Amann (1912) non Bunge (1839) (Q17280121) => Pachyneurum J.J.Amann ; Pachyneurum revolvens (Q17268007) => Pachyneurum revolvens
Proposed byBrya (talk)
Discussion

A lot of stuff is imported from various databases. Some databases (CoL and The Plant List being notorious) have a lot of names that may not be used as a name of a taxon, ever (illegitimate names, later homonyms, rejected earlier homonyms, and combinations with these). Still, they are out there, and they are being imported here. They must be weeded out of "taxon name", where they create havoc. Having this property allows these names to be put somewhere, and then taxon rank (P105) could be added (perhaps even parent taxon (P171)). Brya (talk) 07:57, 18 January 2015 (UTC)

  • Brya I think this can be done using existing properties but I'm not completely sure. If this is an obsolete name for a taxon then use taxon name (P225) with an end date qualifier and mark that name "deprecated". If it is enough of an entity to deserve it's own separate item then use instance of (P31) to link to "obsolete taxon" or taxon rank (P105) to link to "obsolete species" i.e. create some new items instead of a new property. Does this make sense? Filceolaire (talk) 17:22, 20 March 2015 (UTC)
@Filceolaire No, this is a hundred percent guaranteed not to work. In most cases, this approach is what caused the problem in the first place: there are dedicated databases that have entries clearly marked as not being taxon names, and then there comes a user (often enough a highly educated professional) who takes these entries and then promotes them to newly existing species and genera.
        And, no, these things are not notable enough to rate an item, but there are Wikipedia's that have a page on them. BTW, often enough it proves not possible to delete/redirect such pages on a Wikipedia; this will often enough give the response "Sure, this is a fictitious species, and the page is in violation of basic Wikipedia policy, but so what: it is valuable content, and we must keep it" (happens time and again).
        In addition, deprecating a taxon name (in as far as it may work at all) is necessary for something else, namely for taxon name that has actually been used, and could theoretically be used again in future, but is not used now. There are a lot of shades of grey that could need to be expressed, without dragging in taxa that do not exist, never have existed, and that never can exist.
        As shown by the example these items are now handled by "instance of", but this is not all that satisfactory. It will do, to make it clear that they are not taxon names, but it would be better to have a property which allows adding details. For example the taxobox module now (provisionally) in use cannot handle cases where such a name is a basionym (short term this is not so bad as the taxobox module does not work for many other names either (the structure chosen is too complicated for my taste), but long-term this will cause problems). There are constraint violation problems now as well (like here). - Brya (talk) 11:16, 21 March 2015 (UTC)
Sorry Brya but I still don't get it. You want to make the following statements:
What do these statements mean?
Is Pachyneurum J.J.Amann (1912) non Bunge (1839) (Q17280121) not a taxon name or is it Pachyneurum J.J.Amann?
If they are not taxon names then what are they and how did they get in the databases?
You describe Pachyneurum revolvens (Q17268007) as "name that must not be used" but Wikidata is not just for taxonomy and that sounds like a great name for my rockabilly band. Why can't I use it?
That's 4 questions. Filceolaire (talk) 15:12, 21 March 2015 (UTC)
Well, Pachyneurum J.J.Amann (1912) non Bunge (1839) is not, never has been, and never can be used as the correct name of a taxon (the whole string "Pachyneurum J.J.Amann (1912) non Bunge (1839)" is just a matter of notation: it is the Pachyneurum that counts). This is because there is a Pachyneurum Bunge (1839) which may be used as the correct name of a taxon (and is: Pachyneurum (Q15943018)). There also exists a Pachyneurum E.B.Bartram (1939) non Bunge (1839), which also may not be used as the correct name of a taxon. All three are formal names (are "validly published"), that is, they exist in that particular nomenclatural universe. Q17280121 is an item that refers only to a formal scientific name (a name that may not be used).
        Names such as these are in databases so that people are forewarned not to used them (the two later ones) and to decode possible problem cases.
        You may use Pachyneurum revolvens for your rockabilly band, like any other string you like. However, it may not be used as the scientific name of a plant. There is a rulebook that says so.
Hope this covers it, - Brya (talk) 16:32, 21 March 2015 (UTC)
Why not use "instance of (P31) Q-do-not-use-on-a-taxon" ? Visite fortuitement prolongée (talk) 20:12, 21 March 2015 (UTC)
That is how I am doing it at the moment (but with the relevant term without the instead of "Q-do-not-use-on-a-taxon"), and this works to a degree, but:
  • This does not allow indicating the correct spelling, or even the name at all, in a property. As it is now, these can only be put in a label.
  • This does not allow correct author citation of other scientific names. These other scientific names are for existing taxa and do have pages on Wikipedia's. They cannot have a correct author citation as Wikidata has a complicated mechanism for entering authors, which involves more than one item. - Brya (talk) 05:48, 22 March 2015 (UTC)
  • "This does not allow indicating the correct spelling" →‎ Your current proposal does not allow indicating the correct name of a taxon. And for the spellling, there is already IPA transcription (P898).
  • "This does not allow correct author citation of other scientific names." →‎ What do you mean by that?
Visite fortuitement prolongée (talk) 20:17, 22 March 2015 (UTC)
"Your current proposal does not allow indicating the correct name of a taxon." This does not come into it, and has nothing whatsoever to with the proposed property.
        Well, conceivably IPA transcription (P898) may be used, but this is really something else, there can easily be three IPA transcription (P898) for each not-a-taxon-name (which is closely constrained).
        ""This does not allow correct author citation of other scientific names." →‎ What do you mean by that?" See below. - Brya (talk) 12:27, 23 March 2015 (UTC)
Brya from you answer it seems that this property does not link from a subject item to another item or a value. Rather it tells you something about the subject item. The standard way to do this is with instance of (P31) as Visite fortuitement prolongée said just above. So we say "Pachyneurum J.J.Amann (1912) non Bunge (1839) (Q17280121):instance of (P31):Unacceptable taxon name - does not comply with International Code of Nomenclature for algae, fungi, and plants (Q693148)" where "Unacceptable taxon name - does not comply with International Code of Nomenclature for algae, fungi, and plants (Q693148)" is a new Qitem. This statement should have a reference linking to the edition/chapter/page in the Nomenclature that the name doesn't comply with. If the reason the name is not acceptable is that it clashes with another name then you should think about a property for linking to the item for the taxon that it clashes with. In the meantime I   Oppose the creation of this new property as, so far as I can see, it wouldn't work as you have described it. Filceolaire (talk) 04:14, 22 March 2015 (UTC)
@Filceolaire. No, this "this property does not link from a subject item to another item or a value.": it is a string property. This is nothing exceptional: "taxon name" is also a string property. See also directly above. - Brya (talk) 05:55, 22 March 2015 (UTC)
Brya sorry about that. My mistake. I am feeling really dumb here but what does the statement "<Not a Taxon name "Pachyneurum J.J.Amann"> actually mean and what does it tell us about the subject item.
Why can't you use taxon name (P225) to indicate the correct spelling. Is the problem with these incorrect names that they are misspelled?
You mention problems using the "correct author citation" above by 'correct' I assume you mean citation of the taxon name, author and date in the approved compressed format. I assume you understand why wikidata uses three separate properties to indicate the taxon name, author name and date. Filceolaire (talk) 17:29, 22 March 2015 (UTC)
@Filceolaire Well, it is very specialised topic, and the proposed property is uniquely designed to fit in with how Wikidata handles this, which is also complicated (needlessly so in my opinion). The statement"<Not a Taxon name "Pachyneurum J.J.Amann"> tells us that there is a scientific name Pachyneurum with that spelling, published by Amann, and that this scientific name may not be used as a taxon name. Other than the name there is no subject item. This could also be filled in "<Not a Taxon name "Pachyneurum"> but this looks less clear to me (maybe I will change my mind once the property is in use).
        A different example is Bisaschersonia clusiifolia (Q17235272), this is a name that was published as a political statement (part of a revolution attempt), and it is no more than a curiosity item. Again, there never was a taxon by that name.
        It is not possible to use taxon name (P225), as P225 is a Wikidata-defined property (not existing anywhere else), for the correct name of a taxon (the name that is in use in the real world), usually as on a Wikipedia-page, but sometimes as in the cited reference. There are lots of other names that may not be filled in in taxon name (P225), like synonyms.
        No, "author citation" is not "citation of the taxon name, author and date in the approved compressed format". Author citation is about what authors may be cited and in what relationship to each other. Date is not formally part of the author citation, although in practice it is often cited along with it. The present way of author citation used in Wikidata for algae, fungi and plants in the case of later combinations is that each item provides the author(s) who made the new combination. To get the complete authorship it is then necessary to also go to the item that holds the basionym, and get the authorship of the basionym (for animals it is different) and combine it with the other authors to give the complete author citation. - Brya (talk) 12:18, 23 March 2015 (UTC)
If I understand correctly, the full name of Pachyneurum J.J.Amann (1912) non Bunge (1839) (Q17280121) is "Pachyneurum J.J.Amann (1912) non Bunge (1839)". So a reword of the current 2 examples is: Q"Pachyneurum J.J.Amann (1912) non Bunge (1839)" => "Pachyneurum J.J.Amann (1912) non Bunge (1839)" ; Q"Pachyneurum revolvens" => "Pachyneurum revolvens". The third part is redundant. This is a flawed design, a waste of ressources, and an useless point of failure. It could be abbreviated to a boolean, such Q"Pachyneurum J.J.Amann (1912) non Bunge (1839)" => yes. Or, if I reverse the meaning: Q"Pachyneurum J.J.Amann (1912) non Bunge (1839)" => no ; Q"Pachyneurum Bunge (1839)" => yes. Or, with P31: Q"Pachyneurum J.J.Amann (1912) non Bunge (1839)" =instance of (P31)=> Q"unacceptable taxon name DO NOT USE exept for historical purpose" ; Q"Pachyneurum Bunge (1839)" =instance of (P31)=> Q"acceptable taxon name" or taxon (Q16521) (thanks to Filceolaire for "unacceptable" adjectiv). Therefore I   Oppose the proposal in its current wording. Visite fortuitement prolongée (talk) 20:17, 22 March 2015 (UTC)

Note done No support. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 11:13, 22 May 2015 (UTC)

Fauna-Europaea-ID

Descriptionidentifier in Fauna Europaea
RepresentsFauna Europaea (Q2745977)
Data typeString
Domainanimal (Q729)
Exampleanimal (Q729) → 1
Sourcehttp://www.faunaeur.org/
Formatter URLhttp://www.faunaeur.org/full_results.php?id=$1
Begründung

The article Fauna Europaea - all European animal species on the web gives some background information. Succu (talk) 08:43, 10 May 2015 (UTC) @Gregor Hagedorn, 99of9
Achim Raschka (talk)
Andrawaag (talk)
Brya (talk)
CanadianCodhead (talk)
Circeus
Dan Koehl (talk)
Daniel Mietchen (talk)
Enwebb
Faendalimas
FelixReimann (talk)
Infomuse (talk)
Infovarius (talk)
Jean-Marc Vanel
Joel Sachs
Josve05a (talk)
Klortho (talk)
Lymantria (talk)
MPF
Manojk
MargaretRDonald
Mellis (talk)
Michael Goodyear
Mr. Fulano (talk)
Nis Jørgensen
PEAK99
Peter Coxhead
PhiLiP
Andy Mabbett (talk)
Plantdrew
Prot D
pvmoutside
RaboKarbakian
Rod Page
Strobilomyces (talk)
Tinm
Tom.Reding
TomT0m
Tommy Kronkvist (talk)
Tris T7 TT me
Tubezlob
William Avery
  Notified participants of WikiProject Taxonomy

Discussion
  Support --Tobias1984 (talk) 08:55, 10 May 2015 (UTC)
  Support - I guess this will do. The introduction of the cited paper says all the wrong things (sounds just like the introduction of the Catalogue of Life!), and the linguistic errors in the paper don't inspire confidence either. However, whenever I used the site (which was not often) it seemed okay (considerably better than CoL, anyway). - Brya (talk) 09:01, 10 May 2015 (UTC)
Looks good to me as proposed. I know some of the team that runs the database, and that they welcome suggestions for improvements. Will abstain from a vote. --Daniel Mietchen (talk) 09:30, 10 May 2015 (UTC)

@Gregor Hagedorn, Tobias1984, Brya, Daniel Mietchen:   Done Fauna Europaea ID (P1895) Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 14:41, 21 May 2015 (UTC)

DMS V (DSM 5)

DomainMedicine
Allowed valuesAny DSM-5 identifier that is valid.
Motivation

We store DSM-4, which is more and more out of date. Storing DSM-5 separate would probably be the easiest for infobox maintainance. Please note that en:DSM-5_codes is under copyright investigation at the moment. --Tobias1984 (talk) 08:02, 6 May 2015 (UTC)

Discussion

Tobias1984
Doc James
User:Bluerasberry
Wouterstomp
Gambo7
Daniel Mietchen
Andrew Su
Peter.C
Klortho
Remember
Matthiassamwald
Projekt ANA
Andrux
Pavel Dušek
Was a bee
Alepfu
FloNight
Genewiki123
Emw
emitraka
Lschriml
Mvolz
Franciaio
User:Lucas559
User:Jtuom
Chris Mungall
ChristianKl
Gstupp
Geoide
Sintakso
علاء
Dr. Abhijeet Safai
Adert
CFCF
Jtuom
Lucas559
Drchriswilliams
Okkn
CAPTAIN RAJU
LeadSongDog
Ozzie10aaaa
Sami Mlouhi
Marsupium
Netha Hussain
Abhijeet Safai
ShelleyAdams
Fractaler
Seppi333
Shani Evenstein
Csisc
linuxo
Arash
Morgankevinj
Anandhisuresh
TiagoLubiana
ZI Jony
Viveknalgirkar
  Notified participants of WikiProject Medicine --Tobias1984 (talk) 08:03, 6 May 2015 (UTC)

  • Include, assuming that we have the legal right to import this identification system. The DSM is most used English language standard for classifying mental disorders. Version 4 was released in 2000 and version 5, this version proposed, was released in 2013. I am unsure about the legal right we have to import this system in Wikidata. Sometimes the organizations which produce these systems assert a right to restrict their use, perhaps asserting copyright over the text or a patent on the system. While I think this system would be useful to include in Wikidata, I am not knowledgeable about the right we have to import it. Blue Rasberry (talk) 20:03, 11 May 2015 (UTC)
  •   Support Including the number to link to the DSM is not a copyvio. Using that number to copy data from the DSM into wikidata probably is a copyvio. Given that we shouldn't import the data it is even more important to link back to the DSM so users can get the data there - if they can access the DSM. Filceolaire (talk) 08:48, 3 June 2015 (UTC)
  • Question: Should we deprecate/ remove DSM-4, once this is created? Should we have a more generic "DMSM" property, with a qualifier? @Tobias1984: Please provide a description. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 09:19, 3 June 2015 (UTC)
    • @Pigsonthewing: I think we should keep DSM-4 and DSM-5 separate, because it is much easier to handle for infoboxes. In the future it might be possible to have a property "DMSM" with statements using DSM-4 and DSM-5 as a source, but I think that the current Wikidata<->Wikipedia APIs could not handle such a lookup. --Tobias1984 (talk) 09:30, 3 June 2015 (UTC)

@Tobias1984, Bluerasberry, Filceolaire:   Done DSM-5 classification (P1930) Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 10:08, 3 June 2015 (UTC)

Vaccine for

VIOLIN ID

   Done: VIOLIN ID (P1925) (Talk and documentation)
DomainVaccines, ...
Allowed valuesValid IDs

Identity control for vaccines and related subject. --Tobias1984 (talk) 15:48, 24 May 2015 (UTC)

Discussion

@Tobias1984:   Done VIOLIN ID (P1925) Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 09:31, 3 June 2015 (UTC)

Vaccine Ontology ID

DomainVaccines
Allowed valuesValid IDs
Formatter URLhttp://www.ontobee.org/browser/rdf.php?o=VO&iri=http://purl.obolibrary.org/obo/$1

Identity control for vaccines and related subject. --Tobias1984 (talk) 15:48, 24 May 2015 (UTC)

Discussion
  Support Emitraka (talk) 19:50, 26 May 2015 (UTC)
  Support --Genewiki123 (talk) 23:36, 27 May 2015 (UTC)
  Support Sebotic (talk) 18:08, 28 May 2015 (UTC)
  Support Andrawaag (talk) 17:55, 2 June 2015 (UTC)

@Tobias1984, Emitraka, Genewiki123, Sebotic, Andrawaag:   Done Vaccine Ontology ID (P1928). The formater URL is rejected by the validator :-( Perhaps User:Magnus Manske can oblige with a work-around? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 09:41, 3 June 2015 (UTC)

Odd, just http://purl.obolibrary.org/obo/$1 works for me (note that the server will rewrite the URL, but so what?). Example where it doesn't work? --Magnus Manske (talk) 09:47, 3 June 2015 (UTC)

Clinvar Accession Number

Domaininstance of genetic variation (Q349856)
Allowed valuesRCV000000000.0 - RCV999999999.* (* is an integer representing the release number, will slowly increase with time)
Robot and gadget jobsRobots will add and edit the Clinvar Accession Numbers on appropriate WD items
Motivation

Clinvar is the most sophisticated open database for human genomic variation affecting human traits and human disease risk. The Clinvar accession number will serve as the link between a WD genetic variant item and its source in Clinvar. Clinvar is a stable, high quality and widely used reference for genomic variation in humans. Sebotic (talk) 23:14, 1 June 2015 (UTC)

Discussion
  Support Andrawaag (talk) 17:55, 2 June 2015 (UTC)
  Support Emitraka (talk) 19:33, 2 June 2015 (UTC)
  Support Andrew Su (talk) 20:07, 2 June 2015 (UTC)

@Sebotic, Andrawaag, Emitraka, Andrew Su:   Done ClinVar Variation ID (P1929). Is there a formatter URL? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 09:49, 3 June 2015 (UTC)

@Pigsonthewing:: The formatter URL would be http://www.ncbi.nlm.nih.gov/clinvar/$1/ ($1 representing the respective value)

upstream software

   Not done
Descriptionsoftware which is "upstream", meaning that patches are inherited from it
Data typeItem
Domainsoftware
Allowed valuessoftware
ExampleRed Hat Linux (Q220182) = Fedora (Q48267), Ubuntu (Q381) = Q7593
Proposed byTobias1984 (talk) 11:50, 26 August 2014 (UTC)
Discussion
  • Important information in software development. Tobias1984 (talk) 11:50, 26 August 2014 (UTC)

Tobias1984
Emw
Zuphilip
Danrok
Bene*
콩가루
TomT0m
DrSauron
Ruud Koot
Andreasburmeister
Ilya
Toto256
MichaelSchoenitzer
Metamorforme42
Pixeldomain
User:YULdigitalpreservation
Dipsode87
Pintoch
Daniel Mietchen
Jsamwrites
Tinker Bell
FabC
Jasc PL
putnik
Dhx1
Tris T7
Peb Aryan
lore.mazza004
Rc1959
Premeditated
Iwan.Aucamp
LiberatorG
  Notified participants of WikiProject Informatics -Tobias1984 (talk) 11:11, 19 October 2014 (UTC)

  •   Oppose. Use based on (P144) instead. Filceolaire (talk) 23:46, 2 November 2014 (UTC)
  • I think Filceolaire's suggestion makes sense. —Ruud 16:51, 19 December 2014 (UTC)

Not done. Use based on (P144). Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 11:22, 22 May 2015 (UTC)

Smithsonian volcano identifier

DescriptionIdentifier of volcano in the Smithsonian Global Volcanism Program
RepresentsVolcano Number (Q7940064)
Data typeString
Template parameter"VNUM" in it:Template:Montagna
Domainvolcano (Q8072)
Allowed valuesInstances of volcano (Q8072) or mountain (Q8502)
ExampleKrakatau (Q82613) => 262000
Sourcehttp://www.volcano.si.edu/
Formatter URLhttp://www.volcano.si.edu/volcano.cfm?vn=$1
Motivation

to uniquely identify volcanoes ValterVB (talk) 20:21, 28 April 2015 (UTC)

Discussion

@TomT0m, Pasleim, Paolobon140:   Done by User:GZWDer, Smithsonian volcano ID (P1886) Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 19:43, 9 May 2015 (UTC)

Volcanic explosivity index

Motivation

to provide a relative measure of the explosiveness of volcanic eruptions ValterVB (talk) 20:30, 28 April 2015 (UTC)

Discussion
  •   Support seems a useful and well established information. TomT0m (talk) 07:10, 29 April 2015 (UTC)
  •   Comment Copy edited; suggest using datatype=item, and creating an item for each of the ten allowed values. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 07:22, 29 April 2015 (UTC)
  •   Support but unsure about the datatype --Pasleim (talk) 21:03, 4 May 2015 (UTC)

@ValterVB, TomT0m, Filceolaire, Pasleim: - anyone - any objections to using datatype=item? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 15:52, 25 May 2015 (UTC)

  Support item datatype. TomT0m (talk) 15:55, 25 May 2015 (UTC)
  Question I couldn't find any items for the intensities of the volcanic explosivity index. How would item-datatype look like in this case? --Tobias1984 (talk) 16:01, 25 May 2015 (UTC)
There is 9 values, I say we would have something like
< eruption > intensity search < explosivity 1 eruption >
with
< explosivity one eruption > instance of (P31)   < eruption explosivity level >
Now I think about it we also could model this with classes of eruption like explosivity one eruption and with
< explosivity one eruption > instance of (P31)   < class of eruption (sorted by explosivity) >
. We can do both of course. TomT0m (talk) 16:27, 25 May 2015 (UTC)
  Support I have no problem with changing the datatype to item as there is no provision for decimal places (no such thing as a 2.3 eruption). Filceolaire (talk) 17:50, 25 May 2015 (UTC)
  Answer   Support @Tobias1984:Each value should though link to its description which is provided here https://en.wikipedia.org/wiki/Volcanic_explosivity_index Paolobon140 (talk) 14:45, 26 May 2015 (UTC)
  Support No objections --ValterVB (talk) 17:38, 26 May 2015 (UTC)

@ValterVB, TomT0m, Filceolaire, Pasleim, Tobias1984:   Done volcanic explosivity index (P1903). Please create the necessary items. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 20:25, 26 May 2015 (UTC)

@ValterVB, TomT0m, Filceolaire, Pasleim, Tobias1984, Pigsonthewing: Thank you Pigsonthewing for providing this new item; however the new item might be incomplete: each of the values from 1 to 9 should in fact contain a description of the value itself as already done e.g. in https://www.wikidata.org/wiki/Q3679744 where each of the values admitted into the item link to its descripion: would be necessary to provide a description for each of the 9 values that can be found at http://ete.cet.edu/gcc/?/volcanoes_explosivity/ so that value 0 will contain "Hawaiian" as a description; value 1 will contain "Hawaiian/Strombolian", 2 will contain "Strombolian/Vulcanian" up to 8 which will be described as "Supervolcanic". Italian Wikipedia already has a working infobox taht you can find at https://it.wikipedia.org/wiki/Monte_Kanla-on where the originating template is https://it.wikipedia.org/wiki/Template:Montagna property VEI.Paolobon140 (talk) 08:04, 27 May 2015 (UTC)
@Paolobon140: You can - as I indicted above - create these items yourself, and include any description which you see fit. Do you need help? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 08:59, 27 May 2015 (UTC)
@Pigsonthewing: Thank you Andy, i now clearly learnt how to do it; can you please delete or rename https://www.wikidata.org/wiki/Q19984231 which is my previous VEI 0 test? I will replace it asap.Paolobon140 (talk) 13:42, 27 May 2015 (UTC)
@Paolobon140: I've merged them - but in future, you can just edit the values to the new ones. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 14:09, 27 May 2015 (UTC)


Discussion

Vox-ATypI classification

DescriptionA classification for typefaces.
RepresentsVox-ATypI classification (Q1437688)
Data typeItem
Template parameter"classifications" in en:template:infobox font
Domaintypeface (Q17451)
Allowed valuesinstance of Vox-ATypI classification (Q1437688)
ExampleDidot (Q933861) => Didone (Q693749)
Proposed byTypingAway (talk)
Discussion

Widely used classification for typefaces. TypingAway (talk) 17:02, 12 January 2015 (UTC)

  •   Support. Note that I have changed the datatype to item and edited the proposal to match. Filceolaire (talk) 20:45, 7 March 2015 (UTC)

@TypingAway, Filceolaire:   Done Vox-ATypI classification (P1878) Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 20:34, 3 May 2015 (UTC)

after a work by

DescriptionQualifier of the creator of a work of art (can be anonymous (Q4233718) or a specific, named person). Used when the artwork is strongly inspired by, and looks very much like, an artwork of an other master. This property is different from the following:
  • inspired by (P941) (when one work was inspired by another work - this property connects two works of art, not their creators)
  • based on (P144) (similar: between two artworks, not their creators)
  • manner of (P1777) (a new work was created 'in the style of' another painter, but it is not considered to be a copy of another work or to be strongly inspired by another existing work of the original master)
Data typeItem
DomainQualifier of creator (P170)
Allowed valueshuman (Q5)
ExampleThe bellows repairer (Q1989774) => Cornelis Massijs (Q2199365) after a work by Hieronymus Bosch (Q130531)
Sourceexternal reference
Discussion

Motivation: Noticed that this property is missing from the Anonymous works qualifiers that were proposed and approved earlier. As said above, this property not only applies to anonymous works.

Proposed by: Spinster (talk)

  Comment Take a look at this Wikidata search to get an idea of where such a property/qualifier may be used. Spinster (talk) 11:55, 20 April 2015 (UTC)

@Spinster:   Done after a work by (P1877) Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 20:28, 3 May 2015 (UTC)

@Spinster:   Question Any reason why the anonymous (Q4233718) item is used instead of
< work > creator (P170)   < no value Help >
 ? Other   Question Why a qualifier and not the whole item ? TomT0m (talk) 18:57, 23 May 2015 (UTC)
It's a qualifier because one person works after the work of another person, it's not a direct relationship to the artwork. As for the use of anonymous (Q4233718) instead of
< work > creator (P170)   < no value Help >
, I have no idea (sometimes I think the latter would be more correct, but I go along with what appears to be consensus in this case). @Multichill: I think you are able to explain why we use anonymous (Q4233718) instead of
< work > creator (P170)   < no value Help >
? Spinster (talk) 19:04, 23 May 2015 (UTC)
OOps, I meant unknown value Help, of course ... TomT0m (talk) 19:31, 23 May 2015 (UTC)

list of characters

Descriptionlink to the article with the list of characters for this work
Data typeItem
Domaintelevision series (Q5398426) and similar, i.e. radio series
ExampleHeroes (Q83401) => list of Heroes characters (Q1538416)
SourceWikipedia articles
Proposed byputnik
Discussion

Motivation: We already have characters (P674), but it is not appropriate to refer to the lists of characters, which are many in Wikipedia. —putnik 02:16, 27 April 2015 (UTC)

@putnik, AmaryllisGardener:   Done list of characters (P1881) Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 12:37, 8 May 2015 (UTC)

incipit, first verse, first line

   Done: first line (P1922) (Talk and documentation)
Descriptionpour citer le premier vers ou la première ligne d'un poème au titre générique (sonnet, chanson) ou distinguer plusieurs poèmes du même auteur portant le même titre (voir chez Baudelaire, par ex.) (fr) – (Please translate this into English.)
Data typeMonolingual text
Domainmainly poem (Q5185279) and sub-classes… but also songs, etc.
Allowed valuesthe first line of the litterary work…
Sourcewikisource mostly, etc.
Robot and gadget jobscould probably be retrieved automatically through script or bot from the ws page
Motivation

hundreds of poems have no real title… or similar titles — this is a classical method to distinguish poems in libraries or litterary citations… Hsarrazin (talk) 10:02, 23 May 2015 (UTC)

Discussion
  •   Stöder Widely used on Wikisource, and maybe also can be applied to articles about these works in Wikipedia! Observe that we almost always here talks about works that are so old that copyright isn't an issue. We have an index on svws from the 17th century, which this property can be applied to every poem, since none of them have an official title, AFAIK. We only know them by the first words in the poem and maybe their number. -- Innocent bystander (talk) 10:36, 23 May 2015 (UTC)
even for works in copyright, the short citation in order to recognize the work would probably not be a pb… either fair use or just granted by the law (in France : short citations are all right). --Hsarrazin (talk) 11:28, 23 May 2015 (UTC)
  • Gymel, if I understand the question correctly, this would go in the edition item of a work item, no ? i.e. work : so-and-so… edition so-and-so 1, incipit : so-and-notso, or is it just the contrary :/ ?
  • I just did it this way for poems in 2 or more editions (on ws), where the titles or incipit were different in diff. editions :) --Hsarrazin (talk) 22:45, 25 May 2015 (UTC)
Well, for manuscript materials you could have several versions which "culminate" in the first edited version - AFAIK the incipit of that one would be choosen for the Einheitsincipit. I have to admit that I'm not aware of any project or institution using that concept, it well might be just a theoretical provision anticipating some cataloguing needs. The "usual" application of the "regular" incipit (in manuscripts) seems to differentiate versions which could be confused when considering only the title (and the Einheitsincipit would solve the complimentary task of grouping together versions with differing or absent titles - Wikidata can achieve that differently by relating all versions to a work or expression item, maybe with exemplar of (P1574)). Also there is a strong application in cataloging of music manuscripts, cf. RISM announces incipit search. Thus for wikidata items representing (versions of) songs we'll actually have to incipits, the music one (coded as letters) and the text one (taken as-is).
Thus I'd propose to leave the issue of Einheitsincipit until we sight one in the wild but consider music incipits as additional use case for the property (is the textual notation system unambigous or does it have to be specified by a qualifier? I have no idea) -- Gymel (talk) 20:38, 26 May 2015 (UTC)

@Hsarrazin, Innocent bystander, Visite fortuitement prolongée, Gymel, Sergey kudryavtsev:   Done first line (P1922) Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 21:01, 30 May 2015 (UTC)

end of online service

   Not done
Descriptionthe date at which online service ceased for a video game or platform
Data typePoint in time
DomainVideo games, online platforms
Allowed valuesDate
ExampleXbox (Q132020) → April 15, 2010
Motivation

This property would be extremely useful for video games that no longer have an online service, but still have a single-player mode. You could use end time (P582) for MMOs, but this sort of item is technically is still playable, it just doesn't have an online service. It could also be used for platforms that not longer have an online service, but are still playable offline (for example, Xbox (Q132020)'s online services shut down in 2010) --George (Talk · Contribs · CentralAuth · Log) 08:49, 24 May 2015 (UTC)

Discussion
  Oppose, other solutions exists :
  1. use significant event (P793)  . .
  2. (better imho) : use or create items like Xbox Live (Q170073)    , and express statements like
    < Xbox Live (Q170073)     > end search <  April 15, 2010 >
    , and create a property online service. This would give : which makes easier to find not only the online service end, but also every informations on the service, like the beginning. TomT0m (talk) 10:43, 24 May 2015 (UTC)
I definately like the idea of the "online service" property, however I think it would be easier to create an individual property, without the complex use of qualifiers. Also, for individual video games, solution 2 wouldn't work. --George (Talk · Contribs · CentralAuth · Log) 18:37, 24 May 2015 (UTC)
Example of a video game:
< Army of Two (Q689877)     > end of online service search < August 11, 2011 >
--George (Talk · Contribs · CentralAuth · Log) 18:57, 24 May 2015 (UTC)
@Caliburn: Why would not that work ? it's possible to create an item. Note that this does not need a qualifieras the property end time (P582)   (and also service entry (P729)   or end cause (P1534)) can be used on the service item. TomT0m (talk) 19:05, 24 May 2015 (UTC)
Revising, I believe your second solution would work best. Thanks for the suggestion! :D I will create the new request momentarily. --George (Talk · Contribs · CentralAuth · Log) 19:12, 24 May 2015 (UTC)

preview version

   Not done
DescriptionAs for software version identifier (P348) except that it is for preview version of a software
Data typeString
Template parameter"latest preview version" in en:Template:Infobox software
Domaincomputing
ExampleJOSM (Q12877) => 8190
Discussion

Motivation

Proposé par: Pamputt (talk)

This property is equivalent to software version identifier (P348). It corresponds to the number of the development version of a software. As it is used by infobox, it should be present on Wikidata. Pamputt (talk) 05:53, 14 April 2015 (UTC)

  Oppose - use qualifier version type (P548) for this. Josh Baumgartner (talk) 22:55, 20 April 2015 (UTC)
  Oppose use software version identifier (P348) and qualifier version type (P548) --Pasleim (talk) 19:13, 26 April 2015 (UTC)

Accession number

   Not done
DescriptionThe unique (to the collection) identifier created by an institution such as an art gallery, library, archive or museum (GLAMs), when adding an object (or set of objects) to their collection. Commonly called an "accession number", but may contain alphanumeric characters and punctuation such as (but not limited to) dashes, commas, periods and slashes.
Data typeString
Template parameter"accession" in en:Template:Infobox artwork and "registration" in en:Template:Infobox artefact.
DomainAny physical object or set of objects which may be accessioned.
Allowed valuesAny string
ExampleSorrow (Q13107262) => 1973.128.GR (see infobox; references on en:Sorrow (Van Gogh))
Sourceen:Accession number (library science)
Robot and gadget jobsPart of GLAM data uploads. Import from Wikipedia.
Proposed byAndy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits
Discussion

Motivation. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 23:23, 19 March 2014 (UTC)

You can use inventory number (P217) or catalog code (P528). Pyb (talk) 07:37, 20 March 2014 (UTC)
P528 is for "the catalogue name of an astronomic object" (someone only gave it the alias "accession number" recently, after seeing this proposal; I've removed it. P217, a "string identifying a physical object or a set of physical objects in a collection" might work; what do others think? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 09:24, 20 March 2014 (UTC)
I think P217 would be fine, especially if we add accession number to the description. - PKM (talk) 21:51, 27 October 2014 (UTC)

Variety of identifiers

Various museums use all kinds of numbers, sometimes even by department. Examples from the British Museum (from here):

Code Identifier Type Examples
assetid BM Asset Id 69989; 687142
bigno BM Big Number EA99; EA10898; EA10558,14
cmcatno BM Coins & Medals Number BA1p222.1023; BC.1067; EO8p330.1134; MI1p21.76N; MI1p36.154B
codexid BM Codex Id 3494578
grcatno BM Greece & Roman Number Bronze 716; CIL VI 8467; Vase A793.3; Sculpture C159; CIL VI 166 = 30706; CIL XV 6350, 66; CIL VI 2602*; Waywell 1978 368; Old Catalogue No. 123
otherid BM Other number BS.10058; BS.4799.c; BS.6639a; Hay 468; I.Brit.Mus.Gr. I App:7text edition...; Kropp M; P. Ramesseum 13; Sheet.1; S.1272Sheet.10; Sallier 4Sheet.9; Sheet.1P. Ramesseum 3
prn BM Public Reference Number PPA44216; RRM192762; YCA66158
regno BM Registration number S.6223; S.2534; .49; .18192.a; .10466.19; 1977,1105.53; 1920,1115.1.2; 1979,0108.59.A; 1878,1217.123-140; Oc1946,1027.5

Of these, prn is used in the URL, eg http://collection.britishmuseum.org/id/object/YCA62958.

It's a very good question whether to allow such big variety. Considerations:

  • An identifier like "Accession number" is useless without also pointing the collection (inventory number (P217) says the same)
  • The same object may have several identifiers, in different or even the same collection
  • The identifier name (kind) is important for curators to make sense what it is about: they use this name in their daily work
  • We got a bunch of Authority Control properties (eg AAT ID (P1014), CONA ID (P1669)) that point to the register/thesaurus/database
  • A register/thesaurus/database is a collection of records about things (people, places, works/objects)

So I think that we shouldn't have generic properties like inventory number (P217), catalog code (P528) or "Accession number". We should have specific properties, such as "RKD Inventory number", "Astronomical catalog code", "Library of Congress accession number", "British Museum Asset Id", "British Museum Public Reference Number".

We might have a maximum one generic "Inventory number", which is assumed to point to the item's collection, but that's limiting. --Vladimir Alexiev (talk) 11:31, 7 January 2015 (UTC)

Inventory number inventory number (P217) ist meant to describe the numbering of the owner or whoever runs the museum/library/collection. So inv number is what e.g. British Museum assigns to an item of the collection. There is usualy only one inv. nr., if there are two, then one of the numbers is outdated (use qualifier start time (P580), end time (P582) if possible). Cases like this happen, when collections are put together so there is a renumbering necessary. Its not good to remove the old inv. nr. because it might be used in older publications. Every item with inv number belongs to a collection, so it needs allways collection (P195). Id agree to use inv nr and collection as qualifier, however there are difficulties to handle it this way, but that´s only a software issue. It is possible to give an item collection (P195) without inventory number (P217). Inv nr. implies Physical inventory (Q475356), a process, that is usualy done every year where all items are counted. I would not change this property.
The Catalogue numbers catalog code (P528) are not limited in quantities, an item can be described in multiple catalogues, so it is possible to use it as a generic property for all kinds of catalogues and databases. It´s possible to give an item twenty catalogue numbers and the cataloge or database of the authority as a qualifier. I´d agree with this solution. We then could delete half of all properties and save us from discussing 5000 databases as properties in the next years. For authoritiy control it is not necessary to have ownership of the item. Stars or astronmical objects have no owner, so stars like Sirius (Q3409) have no inv. number, but many catalogue numbers. BUT: If we have specific authority control numbers like GND ID (P227), we can link it automaticaly with a weblink to the dataset. We´d loose these valuable links. And we have the same problem in processing: Infoboxes can not handle qualifiers.--Giftzwerg 88 (talk) 14:47, 7 January 2015 (UTC)
A generic "inventory number" is only meaningful when qualified with a Collection or Authority List (database, thesaurus). Eg most paintings at the Mauritshuis are on permanent loan from, and owned by the Rijksmuseum. So for such painting, we need to know WHOSE inventory number, in order to make sense of it.
I strongly disagree to replace the gazillion Autority Control properties (and more coming daily: Wikidata:Property_proposal/Authority_control) with a single property plus qualifier. There's a ton of knowledge encoded in the descriptions of these properties, an appropriate editorial process, coreferencing routines (mix-n-match), and editors identify with them. Also, dealing with such qualifiers is cumbersome. Don't break a good practice.
  Disagree Ergo: use this generic property ONLY for "insigificant" accession numbers that don't merit the creation of an Autority Control property --Vladimir Alexiev (talk) 16:13, 19 January 2015 (UTC)
  Oppose. Use catalog (P972) catalog code (P528) for the accession number specific to an institution with qualifier catalog code (P528) catalog (P972) for the catalog this number refers to. Infoboxes can easily harvest the accession number for humans who will be able to figure out the relevant institution. For machines reading the data we have the extra info they need in the qualifier. Only create new properties for codes that are applicable to multiple institutions. Filceolaire (talk) 21:17, 20 March 2015 (UTC)
  Oppose per Filceolaire --Pasleim (talk) 21:25, 29 March 2015 (UTC)
  Not done No consensus. --Sannita - not just another it.wiki sysop 22:47, 1 May 2015 (UTC)

religious name

   Not done
Descriptionname taken upon joining a religious community
Representsreligious name (Q1417657)
Data typeMultilingual text (not available yet)
DomainPersons
Allowed valuestext
Examplesample items that would use that property, with proposed values; example: Théodore Guérin (Q434579) => Sister St. Theodore, Mother Theodore; Anastasie Brown (Q4751905) => Sister Anastasie, Mother Anastasie
Format and edit filter validation(sample: 7 digit number can be validated with edit filter Special:AbuseFilter/17)
Sourceexternal reference, Wikipedia list article (either infobox or source)
Robot and gadget jobsShould or are bots or gadgets doing any task with this? (Checking other properties for consistency, collecting data, etc.)
Proposed bySweet kate (talk)
Discussion

I end up editing lots of nuns. They often take a religious name other than their birth name — Jane Brown becomes "Sister Anastasie" or what have you. Also common among religious brothers, monks, etc. Sweet kate (talk) 16:47, 12 November 2014 (UTC)

Same as Wikidata:Property_proposal/Person#imię świeckie (pl)? -- Gymel (talk) 21:17, 24 February 2015 (UTC)
  •   Support since we already have lots of other specific name properties. For most of these the religious name will match the label (since they are notable as a nun/priest) but even so it is good to record that this is a religious name. Filceolaire (talk) 23:18, 20 March 2015 (UTC)
  •   Support per Filceolaire Popcorndude (talk) 16:33, 9 May 2015 (UTC)

Please close and archive: the requester had repeated the request at another place already last November and the property had been created as religious name (P1635), cf. Wikidata:Property proposal/Archive/27#P1635. -- Gymel (talk) 23:32, 23 May 2015 (UTC)

Not done. Duplicate of religious name (P1635). Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 12:47, 24 May 2015 (UTC)

game mode

   Not done
Descriptiongame mode of a video game in terms of gameplay (examples for first person shooters: deathmatch, capture the flag, etc.)
Data typeItem
Domainvideo games
Allowed valuesany game mode item which is not already covered by game mode (P404)
ExampleXonotic (Q596536) => deathmatch (Q48510)
Sourcehttps://de.wikipedia.org/wiki/Spielmodus_(Computerspiel)
Discussion

Motivation: This is about “game modes” found in video games. Sometimes, a video game has not just one set of rules and that's it, sometimes, the same video game provides multiple sets of rules to play the game. For example, this is extremely common in first-person shooters: You have free-for-all deathmatch (goal: kill the most opponents until a kill or time limit (or both) has been hit), team deathmatch, capture the flag, king of the hill, last man standing, and many more. There is a very good article in the German Wikipedia about this, see Source.

Not to be confused with game mode (P404). That property is specifically limited to things like “singleplayer”, “multiplayer”, etc. Sadly, this is also called “game mode”, but it describes a different aspect: The number of players involved. English does a very poor job in differentiating those two aspects. If you know a better term for this proposed property (and maybe game mode (P404)), please let me know!

Another problem with “game modes” as they are currently presented in Wikidata is that they are poorly documented/defined. I.e. deathmatch (Q48510) is ambigious and without description, the term “deathmatch” can refer either to “everyone vs everyone” or refer to a team variant of this, where at least 2 teams compete for the highest score. This is commonly called “team deathmatch”, but I've seen a few games which just call this “deathmatch” and the “all vs all” variant is sometimes also called “free for all”. In the example I've provided, I understood “Deathmatch” in the traditional sense. But IMO the “game mode” items in Wikidata surely need to be cleaned up as well. :-/ Please discuss, I am still new to Wikidata. :)

Proposed by: Wiki-Wuzzy (talk)

@Wiki-Wuzzy: I agree the existing game mode (P404) is a bit restrictive, but can we simply broaden it a bit to allow for more options? Maybe some Q's need to be created to cover the different sorts of deathmatches or whatever game modes are worth noting, but I would hate to be creating new properties that are essentially duplicates except for usage restrictions. Josh Baumgartner (talk) 23:34, 20 April 2015 (UTC)
  •   Support let's see where it goes --- Jura 12:11, 30 April 2015 (UTC)
  Oppose game mode (P404) actually would accept deathmatch (Q48510), last man standing (Q17042400), player versus player (Q719798), and other things could easily be added, they just have to be subclasses of game mode (Q1971694). Popcorndude (talk) 19:11, 5 May 2015 (UTC)
  Oppose use game mode (P404) --Pasleim (talk) 23:18, 20 May 2015 (UTC)
  Oppose use game mode (P404) Snipre (talk) 12:32, 22 May 2015 (UTC)

Not done; use game mode (P404). Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 12:45, 24 May 2015 (UTC)

highest note

   Done: highest note (P1897) (Talk and documentation)
Descriptionhighest note that an instrument can play or singer can sing
Data typeItem
Domainmusical instruments, singers, microphones, recording media
Allowed valuesmusical notes
Exampledouble bass (Q80019) → <D5>
Motivation

See discussion above. Filceolaire (talk) 19:34, 11 May 2015 (UTC)

Discussion
  •   Support --- Jura 08:46, 22 May 2015 (UTC)

@Filceolaire, Jura1:   Done highest note (P1897). Please create the necessary items. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 12:44, 22 May 2015 (UTC)

lowest note

   Done: lowest note (P1898) (Talk and documentation)
Descriptionlowest note that an instrument can play or singer can sing
Data typeItem
Domainmusical instruments, singers, microphones, recording media
Allowed valuesmusical notes
Exampledouble bass (Q80019) → <E1>
Robot and gadget jobsno
Motivation

See discussion above. Filceolaire (talk) 19:34, 11 May 2015 (UTC)

Discussion
  •   Support --- Jura 08:46, 22 May 2015 (UTC)

@Filceolaire, Jura1:   Done lowest note (P1898). Please create the necessary items. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 12:46, 22 May 2015 (UTC)