Wikidata:Property proposal/Archive/23

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

LNB identifier

   Done: National Library of Latvia ID (P1368) (Talk and documentation)

Description	identifier issued by the National Library of Latvia (Q1133733) (LNB)
Data type	String
Domain	persons (and organizations?)
Allowed values	numbers
Example	Anšlavs Eglītis (Q615419) => 000001327
Source	library catalog www.lnb.lv or VIAF
Proposed by	Kolja21 (talk)

Discussion

Can be used by Latvian Wikipedia (Q728945). Kolja21 (talk) 20:20, 3 June 2014 (UTC)

 Support -- SERutherford (talk) 01:22, 8 June 2014 (UTC)

Northernmost point

   Done: coordinates of northernmost point (P1332) (Talk and documentation)

Description	The coordinates of the most northerly point of the item. For an item about an administrative entity this includes it's islands.
Data type	Geographic coordinates
Template parameter	none, but can be used to define a map box for this item
Domain	Places
Allowed values	coordinates
Example	sample items that would use that property, with proposed values; example: Universe (Q1) => Earth (Q2)
Format and edit filter validation	(sample: 7 digit number can be validated with edit filter Special:AbuseFilter/17)
Source	not sure
Robot and gadget jobs	no
Proposed by	Filceolaire (talk)

Discussion

This, along with the properties below, can define the limits of a map showing the place. Having coordinates is better than just having a value for the northern extent, because the algorithm defining the map can take account of the distortions due to map projections when mapping large places. Also there seems to be a lot of tourist interest in the extreme points of islands/continents (these places often have signs celebrating these facts) so this could be of use in other ways. Filceolaire (talk) 15:17, 22 May 2014 (UTC)

Why not have a single property "furtherstmost point" or "extremity" or similar, and use put the direction as a qualifier, e.g. direction (P560)→north (Q659) - Evad37 [talk] 23:28, 22 May 2014 (UTC)

In general I prefer properties that will give some info even without the qualifier. Filceolaire (talk) 10:14, 26 May 2014 (UTC)

•  Support all 4. Easier to manage with four distinct properties. --- Jura 04:31, 29 May 2014 (UTC)
•  Support all four. Filceolaire, please provide examples for these proposed properties. Thanks, Emw (talk) 19:01, 31 May 2014 (UTC)
• @Filceolaire, Evad37, Evad37, Emw:  Done and examples already given for all four. --Jakob (talk) 22:30, 31 May 2014 (UTC)

Jakob, no, "sample items that would use that property, with proposed values; example: universe (Q1) => Earth (Q2)" is the placeholder text for the 'example' field. It's used in all four proposal templates. It is not an actual example of how these properties would be used. Emw (talk) 22:35, 31 May 2014 (UTC)

@Emw: Perhaps that was poor wording on my part. What I meant was that I added the properties into an item. --Jakob (talk) 22:39, 31 May 2014 (UTC)

See Columbia County (Q488693). Thanks Jakec. Filceolaire (talk) 11:38, 1 June 2014 (UTC)

Southernmost point

   Done: coordinates of southernmost point (P1333) (Talk and documentation)

Description	The coordinates of the most southerly point of the item. For an item about an administrative entity this includes it's islands.
Data type	Geographic coordinates
Template parameter	none, but can be used to define a map box for this item
Domain	Places
Allowed values	coordinates
Example	sample items that would use that property, with proposed values; example: Universe (Q1) => Earth (Q2)
Format and edit filter validation	(sample: 7 digit number can be validated with edit filter Special:AbuseFilter/17)
Source	not sure
Robot and gadget jobs	no
Proposed by	Filceolaire (talk)

Discussion

See above. Filceolaire (talk) 15:24, 22 May 2014 (UTC)  Done --Jakob (talk) 22:32, 31 May 2014 (UTC)

Easternmost point

   Done: coordinates of easternmost point (P1334) (Talk and documentation)

Description	The coordinates of the most easterly point of the item. For an item about an administrative entity this includes it's islands.
Data type	Geographic coordinates
Template parameter	none, but can be used to define a map box for this item
Domain	Places
Allowed values	coordinates
Example	sample items that would use that property, with proposed values; example: Universe (Q1) => Earth (Q2)
Format and edit filter validation	(sample: 7 digit number can be validated with edit filter Special:AbuseFilter/17)
Source	not sure
Robot and gadget jobs	no
Proposed by	Filceolaire (talk)

Discussion

See above. Filceolaire (talk) 15:24, 22 May 2014 (UTC)

•  Done --Jakob (talk) 22:33, 31 May 2014 (UTC)

Westernmost point

   Done: coordinates of westernmost point (P1335) (Talk and documentation)

Description	The coordinates of the most westerly point of the item. For an item about an administrative entity this includes it's islands.
Data type	Geographic coordinates
Template parameter	none, but can be used to define a map box for this item
Domain	Places
Allowed values	coordinates
Example	sample items that would use that property, with proposed values; example: Universe (Q1) => Earth (Q2)
Format and edit filter validation	(sample: 7 digit number can be validated with edit filter Special:AbuseFilter/17)
Source	not sure
Robot and gadget jobs	no
Proposed by	Filceolaire (talk)

Discussion

See above. Filceolaire (talk) 15:24, 22 May 2014 (UTC)

•  Done --Jakob (talk) 22:34, 31 May 2014 (UTC)

NSK identifier

   Done: NSK ID (P1375) (Talk and documentation)

Description	identifier issued by the National and University Library in Zagreb (Q631375) (NSK)
Data type	String
Domain	persons (and organizations?)
Allowed values	numbers
Example	Marko Marulić (Q336571) => 000003507
Source	katalog.nsk.hr or partially VIAF (only added for testing purposes)
Proposed by	Kolja21 (talk)

Discussion

Useful supplement. Especially for Serbo-Croatian Wikipedia (Q58679) and Croatian Wikipedia (Q203488). --Kolja21 (talk) 01:40, 5 June 2014 (UTC)

 Support -- SERutherford (talk) 01:23, 8 June 2014 (UTC)

 Support -- Vlsergey (talk) 23:20, 22 June 2014 (UTC)

• @Kolja21, SERutherford, Vlsergey:  Done --Jakob (talk) 23:35, 22 June 2014 (UTC)

Your Paintings

   Done: Art UK artist ID (P1367) (Talk and documentation)

Description	An authority control identifier for en:BBC_Your_paintings#Your_Paintings
Data type	String
Template parameter	none
Domain	painters, even if painting was "just" a hobby for them, and they are not tagged as such on Wikidata
Allowed values	generic string, usually lowercase, no spaces
Example	Bernardino da Asola (Q2898912) => "-bernardino-da-asola"
Source	http://www.bbc.co.uk/arts/yourpaintings/artists
Robot and gadget jobs	There are several thousand pre-matched here that could be imported. After that, manually.
Proposed by	Magnus Manske (talk)

Discussion

Motivation. Magnus Manske (talk) 15:37, 13 June 2014 (UTC)

• Support If asked, I would have assumed we had this already. For each artist there is a page with artworks, many still in copyright, and so not available on Commons. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 16:30, 13 June 2014 (UTC)

•  Support}. At [1] about 300 are matched against GND ID (P227), most of them should have an item here I suppose. -- Gymel (talk) 08:09, 14 June 2014 (UTC)

 Done Notification: Magnus Manske, Andy Mabbett, Gymel.--Micru (talk) 09:10, 22 June 2014 (UTC)

honorary title

   Not done

Data type	Item
Domain	person (Q215627)
Allowed values	item
Example	Charles Lindbergh (Q1618) => Time Person of the Year (Q207826)
Format and edit filter validation	(sample: 7 digit number can be validated with edit filter Special:AbuseFilter/17)
Source	https://en.wikipedia.org/wiki/Time_Person_of_the_Year
Proposed by	Милан Јелисавчић (talk)

Discussion

Honorary titles are not suitable for award received (P166). Милан Јелисавчић (talk) 08:36, 28 May 2014 (UTC)

 Question Why is that ? Could you please elaborate on this ? Casper Tinan (talk) 12:10, 28 May 2014 (UTC)

 Not done Added alias to award received (P166). Notification: Милан Јелисавчић, Casper Tinan.--Micru (talk) 09:03, 22 June 2014 (UTC)

studied at

   Not done

Description	famous student at educated at (P69), inverse of educated at (P69)
Data type	Item
Domain	university (Q3918), or more general school (Q3914) though I would prefer two separate items student/pupil at
Allowed values	persons
Example	Beispiel: Q193510 =>studied at => Q2657000
Proposed by	Oursana (talk)

Discussion

Motivation.We have student (P802) student of (P1066) for personal relation only, but we also need the inverse of educated at (P69)Oursana (talk) 10:26, 27 May 2014 (UTC)

 Comment: Why do we need an inverse for educated at (P69)? —Wylve (talk) 11:34, 27 May 2014 (UTC)

The same reason we need an inverse for anything else. --Jakob (talk) 12:08, 27 May 2014 (UTC)

The inverse of educated at (P69) is necessary to express famous students of a certain university. Without this property we cannot show this--Oursana (talk) 13:11, 27 May 2014 (UTC)

In some weeks queries will arrive. Then it will be possible to express exactly such things without having a new property. --Pasleim (talk) 14:22, 27 May 2014 (UTC)

 Oppose  Support  Comment This property seems useful but it should not be called "student", since student (P802) already has that label. Oursana, I would support this property if you changed the label to "studied at". Emw (talk) 01:25, 28 May 2014 (UTC)

 Done thank you--Oursana (talk) 01:42, 28 May 2014 (UTC)

Oursana, sorry, that was a dumb suggestion from me. "Studied at" should obviously be an alias of "alma mater", not the label for its inverse property. Could we change the label of this property to "attendee", or something to that effect? Emw (talk) 03:20, 30 May 2014 (UTC)

I've updated my vote to oppose, per Kolja. Inverse properties make sense when there is usually a 1:1 relation (or 1:n, where n is small), but here, n can be almost 13,000. Having that many statements in one item (e.g. Harvard University (Q13371)) is a bad idea. Emw (talk) 12:56, 30 May 2014 (UTC)

 Comment Harvard University (Q13371) is linked 12.909 times. As the inverse of educated at (P69) I wouldn't support this property. Imho it only makes sense if it is used for a reasonable selection. --Kolja21 (talk) 01:55, 28 May 2014 (UTC)

Wikidata has well over 20,000,000 statements; an extra 13,000 statements would be a drop in the bucket -- 0.00065% more statements. The added convenience for users would vastly exceed the negligible extra space and time needed to handle this property. Emw (talk) 03:14, 30 May 2014 (UTC)

I don't think that 13,000 statements in one item will be more convenience than having a simple query: Show me all items with educated at (P69)=Harvard University (Q13371) --Pasleim (talk) 11:31, 30 May 2014 (UTC)

Ah, I misread again, thanks for clarifying. Good point, Kolja, Pasleim. Emw (talk) 12:56, 30 May 2014 (UTC)

 Oppose since I do not think that inverse properties are useful if the value range for one object is much bigger for the inverse property than for the original property as Kolja and Emw pointed out. If you have in mind with "famous student" a range other than all students at an educational institute (who have an item) and want to highlight only "especially famous" students this would neither seem necessary to me nor a clean solution. LG, --Marsupium (talk) 21:43, 1 June 2014 (UTC)

• @Oursana, Wylve, Pasleim, Kolja21, Emw, Marsupium:  Not done - no support. --Jakob (talk) 16:41, 13 June 2014 (UTC)

eye color

   Done: eye color (P1340) (Talk and documentation)

Description	colo(u)r of a person's eyes
Data type	Item
Template parameter	"yeux" (fr:Modèle:Infobox Mannequin), "eye_color" (en:Template:Infobox model), possibly others on Q5833821
Domain	people
Allowed values	items for eye colors
Example	Linda Evangelista (Q192171): blue-green
Source	Wikipedia

Discussion

To import from above infoboxes. --- Jura 11:16, 25 May 2014 (UTC)

•  Comment I like the idea, but wouldn't it be better just to use blue-green (Q646964) in the example you gave? --Jakob (talk) 12:19, 25 May 2014 (UTC)
  • Eye colors don't necessarily correspond to hex codes .. We could use en:blue eyes, but it's just a redirect to a section. --- Jura 13:26, 25 May 2014 (UTC)
•  Support. Interesting property of physical anthropology. Emw (talk) 01:31, 28 May 2014 (UTC)
•  Oppose. Of cause there are a lot of interesting things. But Wikidata is not an NSA project. --Kolja21 (talk) 01:47, 28 May 2014 (UTC)
  • I don't understand your argument. What is the relation to the property proposal for common storage for the French and English Wikipedia infoboxes? Aren't you simply in disagreement with Wikipedia editorial choices? --- Jura 14:46, 28 May 2014 (UTC)
    • @Jura: No, the en:Template:Infobox model is only for models and every Wikipedia can decide if they want to implement it. Wikidata is a powerful tool, therefore WD has higher demands on privacy. biometrics (Q177765) is the domain of medicine and public authorities and should be handled with care in open databases. --Kolja21 (talk) 20:54, 29 May 2014 (UTC)

Kolja, eye color is no more private or "biometric" than a photograph of a person's face. It is a very non-private piece of information about a person. It is certainly of less interest to the NSA and other modern-day bogeymen than mother (P25), father (P22), P7 (P7), P9 (P9), child (P40), kinship to subject (P1039), sex or gender (P21), place of birth (P19), date of birth (P569), native language (P103), religion or worldview (P140), ethnic group (P172), ancestral home (P66), sexual orientation (P91), medical condition (P1050), residence (P551), P1298 (P1298), employer (P108), website account on (P553) and website username or ID (P554). Your claim that "WD has higher demands on privacy" seems to be your personal preference, and is unsupported by any actual Wikidata policy as far as I can tell. The listed properties show that there is ample precedent for this kind of property. Emw (talk) 02:33, 30 May 2014 (UTC)

What you call my "personal preference" are the basics of en:Information privacy and en:Human rights. Of cause WD has gone with properties like sexual orientation (P91) already a questionable way. (If P91 would be used in a neutral way we would have at least the same number of heterosexual than homosexual persons. De facto this property is used to stigmatize a group.) So please don't make your personal indifference to the basic of Wikidata. --Kolja21 (talk) 03:20, 30 May 2014 (UTC)

Kolja, can you cite any source about eye color being protected information? And how do you respond to the fact that eye color is trivially determinable from a photograph of a person's face? Do you support putting special protections on photographs of people? If not, then what is your basis for opposing this property? I realize that eye color has been a basis of discrimination, but to claim that privacy about eye color is a basic element of human rights and information privacy seems unfounded and very unconventional. Most of the properties listed above have also been a basis of discrimination, but that doesn't mean Wikidata forbids structured data on them. Emw (talk) 04:04, 30 May 2014 (UTC)

I'm sure you know enough about databases that you know the difference between a single photo and facts that can be automatically read out and further processed. But since you like questions: What would be a property that you would reject? Can you exclude that Wikidata will be misused in future? And if not, do you care? --Kolja21 (talk) 04:37, 30 May 2014 (UTC)

Kolja, no, I obviously cannot exclude the possibility that Wikidata might be misused. But opposing properties on the broad premise that Wikidata could be misused is a paralyzing standard. By that logic we should do away with almost all Wikidata properties. It's easy to imagine scenarios where properties like mother (P25) and other family relation properties, religion or worldview (P140), sex or gender (P21), etc., etc. are used for evil -- and many are more likely than "eye color" to be misused -- but that is not a legitimate argument to ban those properties. To answer your question about properties I would reject: I would certainly reject properties like "payment card number", "Social Security number" (an ID which is considered very private in the United States), "private key" and "password". All of those have clear vectors for evil acts and are not determinable through ubiquitous things like photographs. While I don't oppose the property itself, I would also reject usages of properties like coordinate location (P625) to track the precise location of people on a pervasive, minute-by-minute basis.

How exactly do you see an "eye color" property being misused? The potential for evil with this property is much, much more remote than most of the 20 person properties listed above, and is also not substantially obstructed by the lack of a property on Wikidata. Do you think that an entity that would purvey such evil would face a significant roadblock by not having a property like "eye color"? Writing a decent automatic classifier for eye color based on public photographs is a weekend project for a decent and motivated programmer. The vector for evil is also quite abstract. What exactly would we be guarding against by not having an "eye color" property? A racist eugenics group that knows enough about technology to query Wikidata but lacks the technical savvy to automatically crop photos and find color, and plug that into downstream analysis? Any protection to human rights afforded by not having this property seems vanishingly thin.

On the other hand, having this property would help answer interesting questions, perhaps some that have positive ends towards human rights. What color were Abraham Lincoln's eyes? What proportion of European heads of state, or American CEOs or actors or television broadcasters (or models) have blue eyes? Some of these queries might actually help reveal and quantify subtle discrimination, or at least noteworthy trends and, of course, trivial factoids of passing interest. Emw (talk) 04:17, 31 May 2014 (UTC)

Thank you for your detailed answer. We agree that any information that can be used also can be misused. Of cause "eye color" itself looks harmless. The problem is "eye color" plus more that 1300 properties. All I'm saying is that we should limit the properties to the main facts that are uncontroversial. Later when we have privacy or other regulations we can increase the coverage. The other way around first collection everything and later delete properties that are already in use won't work. --Kolja21 (talk) 19:52, 1 June 2014 (UTC)

 Comment The idea to add information on persons' eye colour sounds interesting to me. However, the information could already be expressed by the current properties I think. Adopting the example it would be:

⟨ Linda Evangelista (Q192171)    ⟩ color (P462) ⟨ blue-green (Q16939403)    ⟩
applies to part (P518) ⟨ iris (Q178748)    ⟩

applies to part (P518) <eye color (Q23786)> as a qualifier might also be possible. --Marsupium (talk) 21:43, 1 June 2014 (UTC)

 Support. Some infoboxes use this and I really don't want wikidata staying that Linda Evangelist is coloured blue-green, no matter how it is qualified. Filceolaire (talk) 15:37, 3 June 2014 (UTC)

•  Support --AmaryllisGardener ^talk 16:14, 3 June 2014 (UTC)
• @Jura1, Kolja21, Emw, Marsupium, Filceolaire, AmaryllisGardener:  Done, there is sufficient support for creation now. To expand upon Filceolaire's comment, querying qualifiers can't be done, so a query for the color of a person would (in the example) return blue-green, which won't be good for obvious reasons. --Jakob (talk) 16:42, 3 June 2014 (UTC)

ranking

   Done: ranking (P1352) (Talk and documentation)

Description	ranking of sportsperson
Data type	Number (not available yet)
Domain	human (Q5)
Allowed values	range(1,100.000)
Example	Xu Xin (Q2520617) => 1, (qualifiers sport (P641) => table tennis (Q3930), start time (P580) => March 2014)
Source	databases of sports associations, e.g. ittf.com/ittf_ranking, owgr.com/ranking
Robot and gadget jobs	ranking lists can be imported by bots if the source allows it.
Proposed by	Pasleim (talk)

Discussion

Various infoboxes about sportsperson have a current ranking field. If we could store these information here on Wikidata a lot of tedious edits in the locals WPs could be saved. Pasleim (talk) 11:10, 25 May 2014 (UTC)

 Support. See also Properties for deletion. Filceolaire (talk) 15:27, 3 June 2014 (UTC)

 Support --Micru (talk) 06:29, 13 June 2014 (UTC)

• @Pasleim, Filceolaire, Micru:  Done --Jakob (talk) 16:37, 13 June 2014 (UTC)

ITTF ID

   Done: World Table Tennis player ID (P1364) (Talk and documentation)

Description	ITTF table tennis player identifier
Data type	String
Template parameter	ITTF-ID in de:Vorlage:Infobox Tischtennisspieler
Domain	human (Q5)
Allowed values	\d*
Example	Q2520617 => 110267, Q443175 => 105482
Source	ittf.com, de:Vorlage:Infobox Tischtennisspieler
Proposed by	Pasleim (talk)

Discussion

The proprety will be used to import the (free accessibly) monthly world ranking list of ITTF. --Pasleim (talk) 10:29, 25 May 2014 (UTC)

 Support at least to reference the identifier. --- Jura 11:16, 25 May 2014 (UTC)

Automatic TT rankings are used in nl-WP too: nl:Sjabloon:Infobox tafeltennisser. --Tsor (talk) 16:55, 26 May 2014 (UTC)

 Done Notification: Pasleim, Jura, Tsor. World Table Tennis player ID (P1364).--Micru (talk) 08:16, 22 June 2014 (UTC)

Named in his honor

   Not done

Description	mettre la description en anglais ici, par exemple la même que celle de la documentation de l'infobox Nommé en son honneur
Data type	objet, procédé, effet, lieu géographique, unité de mesure ou astre... inventé par ou nommé en l'honneur de la pesonne en question-invalid datatype (not in Module:i18n/datatype)
Template parameter	indiquez ici les attributs d'infobox de Wikipédia correspondants, s'il en existe, par exemple : « population » dans fr:Modèle:Infobox Subdivision administrative
Domain	astronomical object (Q6999) (objet astronomique), disease (Q12136) (maladie), aircraft (Q11436) (avion), geographic location (Q2221906) (lieu), organization (Q43229) (organisation), event (Q1656682) (évènement), work (Q386724) (œuvre), recette de cuisine, machine, bateau, rue ou place, montagne, etc. Valeurs spéciales (ayant des traitements particuliers): personnes, taxons.
Example	exemple d'élément qui utiliserait cette propriété, avec une valeur proposée; par exemple : Universe (Q1) => Earth (Q2)
Format and edit filter validation	(exemple : 7 chiffres peuvent être validés avec le filtre d'édition Special:AbuseFilter/17)
Source	référence externe, article de liste de Wikipédia (soit infobox, soit source)
Robot and gadget jobs	Devrait-il y avoir ou existe-t-il des bots ou des gadgets qui effectueront des tâches avec cette propriété? Par exemple: vérifier les autres propriétés afin d'être cohérent, collecter des données, automatiser un lien externe, etc.
Proposed by	Jean-François Clet (talk)

Discussion

Motivation. Jean-François Clet (talk) 19:52, 17 May 2014 (UTC) Il existe une propriété "nommé selon" qui permet d'inscrire l'éponyme : pourquoi pas l'inverse ? aisi il serait par exemple possible de préciser que la planète Mars à reçu le nom du dieu romain Mars, que le Mont Evrest fut nommé en honneur du britanique George Everest, que le nom de Hertz ne vient pas de la fréquence des battements du coeur humain, mais du savant allemand Heinrich Rudolf Hertz.... etc etc

--Jean-François Clet (talk) 19:52, 17 May 2014 (UTC)

 Oppose. I'm not sure if this the inverse of or a duplicate of named after (P138). Either way I don't think we need it. Filceolaire (talk) 15:23, 3 June 2014 (UTC)

 Not done Redundant. Notification: Jean-François Clet, Filceolaire.--Micru (talk) 08:56, 22 June 2014 (UTC)

PACE member id

   Done: PACE member ID (P1331) (Talk and documentation)

Description	identifier in the member file of the Parliamentary Assembly of the Council of Europe (Q939743) (PACE)
Data type	String
Domain	MPs
Allowed values	see sample
Example	Tina Acketoft (Q4933704): 5864; Aydin Abbasov (Q4054393): 5689

Discussion

Similar to US Congress Bio ID (P1157), MEP directory ID (P1186). --- Jura 06:40, 16 May 2014 (UTC)

 Support -- Innocent bystander (talk) (The user previously known as Lavallen) 12:25, 18 May 2014 (UTC)

 Support. Emw (talk) 02:07, 29 May 2014 (UTC)

• Jura1 Innocent bystander Emw  Done --Jakob (talk) 02:12, 29 May 2014 (UTC)

games / matches / appearances / races / games played / matches played / number of games / number of matches / number of appearances / number of races

   Not done

Description	A list of games/matches/appearances/races that a sportsperson/player/race driver has been awarded.
Data type	Quantity
Template parameter	e.g. "caps1", "caps2", ... "caps39" in en:template:Infobox football biography
Domain	Basically every subclass of athlete (Q2066131) like association football player (Q937857), basketball player (Q3665646), tennis player (Q10833314), any kind of race driver, ...
Allowed values	any integer number >= 0, precision (upper and lower bound) must be 0
Example	to be used as qualifier for member of sports team (P54), for example Ludwig Lachner (Q869973): member of sports team (P54) => Germany national association football team (Q43310) with start time (P580) => 1930, end time (P582) => 1934, games => 8
Source	e.g. en:template:Infobox football biography
Robot and gadget jobs	Bots could import values from Wikipedia and other relevant sources.
Proposed by	Random knowledge donator (talk)

Discussion

 Oppose Seems redundant with Team caps for local leagues and Total leagues caps. By the way, the description does not match with the proposed data type : the value for this property would be an integer not a list. Casper Tinan (talk) 11:42, 5 May 2014 (UTC)

 Not done Redundant. Notification: Random knowledge donator, Casper Tinan.--Micru (talk) 08:55, 22 June 2014 (UTC)

Wikimedia user name

   Not done

Description	A person or organisation's unified user name on Wikimedia projects, omitting the "User:" prefix.
Data type	String
Template parameter	ex: "title" (defaults to BASEPAGENMAE) in en:template:Infobox user
Domain	Person; organization (Q43229) (organization)
Allowed values	Valid, existing Wikimedia user names
Example	example: Jimmy Wales (Q181) => Jimbo Wales
Proposed by	Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits

Discussion

Note: Should only be used for self-identified users, or those with public profiles in reliable sources, who already meet Wikidata notability criteria. No "outing" should be done. Multiple values should be allowed, for those with declared alternative accounts. A qualifier should indicate the primary account. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 14:12, 9 April 2014 (UTC)

•  Comment Is this just another attempt to sneak your user page into Wikidata? --Jakob (talk) 14:29, 9 April 2014 (UTC)
  • No. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 14:32, 9 April 2014 (UTC)

Redundant to website account on (P553) and website username or ID (P554)

-- Lavallen (talk) 14:38, 9 April 2014 (UTC)

Are Wikimedia projects social media? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 14:47, 9 April 2014 (UTC)

Good q, but if it in this matter cannot be considered as one, I do not see that such a property can be included to this project. I know that it has been proposed that the account of Jimbo Wales should use this property for his userpage on enwp, but I cannot see any such statement today. -- Lavallen (talk) 14:51, 9 April 2014 (UTC)

@Pigsonthewing, Lavallen: I have renamed P553 and P554.--GZWDer (talk) 11:45, 12 April 2014 (UTC)

Also @Jakec:--GZWDer (talk) 11:47, 12 April 2014 (UTC)

Why? That's not helpful; and it's especially unhelpful to mix data types (URLs and user names) in one property. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 12:11, 14 April 2014 (UTC)

Note that P554 was intended to have the account name and not a URL as the value, so calling it "website address" could be misleading. --Yair rand (talk) 14:38, 12 May 2014 (UTC)

+1 for website account on (P553) and website username or ID (P554) for such purposes. There is a lot of services where user creates his own account, manages it, create/post/shares content. The feature of "friendship" is only small function of "social media", so even without direct support of such function Wikipedia can be considered as good value for website account on (P553) property (and account name -- as value for website username or ID (P554)). -- Vlsergey (talk) 15:07, 11 June 2014 (UTC)

 Not done Redundant with website account on (P553) and website username or ID (P554).--Micru (talk) 08:09, 12 June 2014 (UTC)

Note that the changes to website account on (P553) and website username or ID (P554) in this regard are disputed above, and the challenges to them remain unanswered. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 09:31, 22 June 2014 (UTC)

Andy, I see that the concerns about the label have been addressed. If there is anything open, please, specify what it is.--Micru (talk) 18:02, 23 June 2014 (UTC)

killed

   Not done

Description	put English description for property here, e.g. same as in the infobox documentation
Data type	Item
Domain	People
Allowed values	People
Example	John Wilkes Booth (Q180914) --> Abraham Lincoln (Q91)
Proposed by	--Jakob (talk)

Discussion

Inverse property to killed by (P157). If the killer is living, only use with strong sourcing, obviously. --Jakob (talk) 21:12, 4 March 2014 (UTC)

 Comment Why do we need an inverse property for killed by? We can query killed by to generate a list of people killed by a specific person. —Wylve (talk) 09:09, 5 March 2014 (UTC)

@Wylve, Yair rand: For the same reason we have any other inverse property. This is a textbook case where this would work because there is often a 1:1 or a few:1 relationship with notable victims and assasins. --Jakob (talk) 00:15, 11 June 2014 (UTC)

@Jakec:: Honestly, I do not see a reason for any inverse property, since we will be able to get information through queries. Victims can have killed by (P157), which links them to their killer. There's no new information added to the database with the proposed property. With items depicting the victim of a particular killer, we can satisfy the few-to-one model. —Wylve (talk) 14:59, 11 June 2014 (UTC)

 Support --- Jura 13:19, 4 May 2014 (UTC)

 Oppose, per Wylve. --Yair rand (talk) 00:00, 11 June 2014 (UTC)

 Not done Consensus not reached. Notification: Jakob, Wylve, Jura, Yair rand.--Micru (talk) 08:53, 22 June 2014 (UTC)

number of injured/injuries

   Done: number of injured (P1339) (Talk and documentation)

Description	number of people who were injured in an event, as stated in reliable sources
Data type	Number (not available yet)
Template parameter	injuries in en:template:Infobox civilian attack, en:template:Infobox battle, en:template:Infobox operational plan
Domain	Battles, wars, massacres, disasters, etc.
Allowed values	numbers
Example	September 11 attacks (Q10806) -> 6000
Source	Usually found in the infobox of the article.
Robot and gadget jobs	Bots be helpful.
Proposed by	Digipoke (talk)

Discussion

Motivation. Digipoke (talk) 22:26, 7 April 2014 (UTC)

 Comment 6000+ is not a valid value for the number data type. Danrok (talk) 13:48, 11 April 2014 (UTC)

Fixed. Digipoke (talk) 12:50, 12 April 2014 (UTC)

 Support Danrok (talk) 10:42, 10 May 2014 (UTC)

 Support Filceolaire (talk) 13:34, 3 June 2014 (UTC)

• @Digipoke, Danrok, Filceolaire:  Done

winner

   Done: winner (P1346) (Talk and documentation)

Description	the person/team/etc. who won the given competition/contest/etc.
Data type	Item
Domain	competition (Q476300)
Allowed values	human (Q5), musical ensemble (Q2088357), sports team (Q12973014) etc.
Example	2010 FIFA World Cup (Q176883) => Spain national association football team (Q42267), Eurovision Song Contest 2014 (Q5354210) => Conchita Wurst (Q113581)
Proposed by	GranD (talk)

Discussion

This is evidently an important aspect of any competition, and its value cannot be inferenced from other items' properties. GranD (talk) 08:58, 26 May 2014 (UTC)

 Support Filceolaire (talk) 13:37, 3 June 2014 (UTC)

 Support Zellfaze (talk) 23:27, 10 June 2014 (UTC)

• @GranD, Filceolaire, Zellfaze:  Done --Jakob (talk) 01:09, 11 June 2014 (UTC)

points/goal scored by

   Done: points/goal scored by (P1363) (Talk and documentation)

Description	each goal/point scorer
Data type	Item
Template parameter	put Wikipedia infobox parameters here, if existing; ex: "population" in en:template:infobox settlement
Domain	sports matches
Allowed values	team members.
Example	1966 FIFA World Cup Final (Q1065912) => Geoff Hurst (Q212738)
Format and edit filter validation	(sample: 7 digit number can be validated with edit filter Special:AbuseFilter/17)
Source	external reference, Wikipedia list article (either infobox or source)
Robot and gadget jobs	Should or are bots or gadgets doing any task with this? (Checking other properties for consistency, collecting data, etc.)
Proposed by	Filceolaire (talk)

Discussion

to record details of sports matches. Filceolaire (talk) 20:11, 10 June 2014 (UTC)

•  Comment for the date of the match, probably the right property already exists. Usually seasons match are grouped per match day: what do you think about a property for specifying the number (1, 2, 3...) of match day? A property that specify the referees can be also useful? --Paperoastro (talk) 08:22, 12 June 2014 (UTC)

For the referee we can say member of sports team (P54):[match officials] with qualifier position played on team / speciality (P413):[referee]. Filceolaire (talk) 21:27, 13 June 2014 (UTC)

•  Support --Paperoastro (talk) 08:22, 12 June 2014 (UTC)
•  Comment Basically the same comment as on assisted by: Should this be a soccer-specific property? I fear someone will one day import sports games with lots of points, don't think Wikidata should be sports database with too many details (a few details are of course ok). Though I see how in some cases such data could be useful. --Bthfan (talk) 23:12, 13 June 2014 (UTC)

  Depend on the sport: for soccer but also for rugby (see for example 2013 Six Nations Championship) it is usual to have this kind of information. For others, as basket, no. --Paperoastro (talk) 23:09, 17 June 2014 (UTC)

•  Support It would be useful also in other team sports too, it doesn't need to be used only for football/soccer. On the contrary, keeping note of the points scored during a, say, basketball match, will help us in keeping better stats. --Sannita - not just another it.wiki sysop 10:33, 20 June 2014 (UTC)
• @Filceolaire, Paperoastro, Bthfan, Sannita:  Done (and personally, I think that the more details, the better). --Jakob (talk) 18:12, 20 June 2014 (UTC)

Anime News Network ID

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

Data type	String
Domain	anime (Q1107)
Allowed values	\d+
Example	Neon Genesis Evangelion (Q662) → 49
Source	ru-wiki templates like ru:Template:Animenewsnetwork.com
Robot and gadget jobs	Autogeneration link in gadgets like Neon Genesis Evangelion (Q662) → [2]
Proposed by	Vlsergey (talk)

Discussion

Just another external ID to link with, wildly used in ru-wiki. Vlsergey (talk) 10:00, 2 June 2014 (UTC)

•  Support. Hausratte (talk) 12:18, 2 June 2014 (UTC)
•  Question Vlsergey, why not to use just one property instead of five? It seems that there are no differences in the link, and "what the item is" can be inferred from other properties. Or am I missing something?--Micru (talk) 14:29, 13 June 2014 (UTC)
  • Micru, the links are different, as far as i can see (anime.php, people.php, manga.php, company.php, release.php). Did i mistype and put same link twice somewhere? --213.87.133.2 14:50, 13 June 2014 (UTC) -- Vlsergey (talk) 12:16, 14 June 2014 (UTC)
    • Vlsergey: no, you didn't miss anything. I am just thinking that "anime.php?id=49" could be used as the whole identifier, like we do with Rottentomatoes or IMDB.--Micru (talk) 12:26, 14 June 2014 (UTC)
      • Micru: Well, it should be then something like "anime49" or "a49" AND not something with ".php" and "?id=" -- not a good idea to include different parts of URI into ID. IMDB has "nm" prefix inside his own identifier, we did not create it out of the air. Also, i don't prefer more strict properties, because we can enforce more restrictions (like only anime (Q1107) for this property), for bot and script-enforced checks. -- Vlsergey (talk) 14:34, 14 June 2014 (UTC)
        • Vlsergey, good idea! I have created a generic property, please fill out the documentation with the prefixes that you prefer to use. --Micru (talk) 11:29, 19 June 2014 (UTC)

 Done As generic property to be used with a prefix. Notification: Vlsergey, Hausratte >> P1361 (P1361).--Micru (talk) 11:29, 19 June 2014 (UTC)

candidacy in election

   Not done

Description	election in which the subject candidated
Data type	Item
Domain	person, organization
Allowed values	instances of public election (Q40231)
Example	Mitt Romney (Q4496) => 2012 United States presidential election (Q4226)
Source	w:cs:Seznam členů Poslanecké sněmovny Parlamentu České republiky po volbách 2013
Proposed by	Shlomo (talk)

Discussion

Can be used as a statement for non-succesful candidates for a public office with further information as qualifiers. Can also be used as a qualifier with position held (P39) for the succesful candidates. And can also be used for political parties running for particular elections. Shlomo (talk) 23:44, 2 February 2014 (UTC)

This would be just the reverse of candidate (P726)? (I wouldn't recommend using either of these yet, btw. Elections are complicated, and we need a full data model instead of putting things together piece by piece. See discussion at Wikidata talk:Politics infoboxs task force#Election complications.) --Yair rand (talk) 23:50, 2 February 2014 (UTC)

 Comment Is there a reason why we would need to reciprocate candidate (P726)? To me, a list of candidates, in an election item seems to be the logical way to cover this. We can find out what elections a person was selected for by querying candidate (P726). Danrok (talk) 16:22, 12 February 2014 (UTC)

 Not done Notification: Shlomo, Yair rand, Danrok. Redundant with candidate (P726).--Micru (talk) 08:19, 22 June 2014 (UTC)

succeeded by (replaced by this person)

   Done: replaced by (P1366) (Talk and documentation)

Description	a separate property like both followed by (P156) / structure replaced by (P167).
Data type	Item
Domain	person
Example	George W. Bush (Q207)=>Barack Obama (Q76)
Proposed by	GZWDer (talk)

Discussion

Motivation. GZWDer (talk) 16:28, 4 February 2014 (UTC)

@GZWDer: I don't understand what the difference to followed by (P156) / structure replaced by (P167) is. --Tobias1984 (talk) 17:38, 4 February 2014 (UTC)

There're no Chinese word to show both relation of 1 (Q199)=>2 (Q200), and that above.--GZWDer (talk) 17:44, 4 February 2014 (UTC)

It seems that this is not a semantic problem, but a grammatical one. --Wylve (talk) 10:01, 8 February 2014 (UTC)

:: Oppose. The current property is pretty much exclusively used for cases where one item replaced another. If a new property is needed then it should be for the case where a party was not replaced.

It sounds like the Chinese translation of 'Preceded by' and 'succeded by' is in error.

If you are arguing that the description of followed by (P156) in English should be changed to make clear it is only used where an item is replaced then that does not need a property proposal. Just change the description.

If you are arguing that the label or the description in chinese don't match those in English and other languages then change the Chinese label and description on the property page and discuss it on the property talk page.

OK? Filceolaire (talk) 19:28, 24 February 2014 (UTC)

 Support. I have changed my mind. It seems there is widespread use of followed by (P156) for series of books, albums from bands etc where this distinction does apply. See the discussion at Property_talk:P155#Drop_the_constraint_to_creative_work where it was agreed this property could do both duties.This is not a grammatical difference. It is a real semantic difference. Obama replaced Bush but The Lord of the Rings did not replace The Hobbit. They both followed but followed has different meanings in these two cases. Filceolaire (talk) 20:08, 24 February 2014 (UTC)

Well, it really depends on how you define 'replacement'. The Hobbit replaced The Lord of the Rings as the newest franchise/film in the Lord of the Rings universe. Obama replaced Bush as the current president of the United States. Both examples can be seen as replacements. —Wylve (talk) 17:07, 4 March 2014 (UTC)

Can we extend this beyond persons to successor states and other thing that replaced something? Any objection? Filceolaire (talk) 21:05, 24 February 2014 (UTC)

Can we change the name of this property to Replaced by with 'Suceeded by' as an alias? Filceolaire (talk) 20:36, 4 March 2014 (UTC)

@Filceolaire: Weren't you the one to suggest the current solution with followed by (P156) as qualifier for e.g. position held (P39) as can be studied in Benedict XVI (Q2494)? Sorry but I cannot see any difference between presidents and popes with respect to succession in office. -- Gymel (talk) 21:41, 4 March 2014 (UTC)

I think I was but I think GZWDer has made a valid case for having two properties - one for books and albums and TV shows, where the previous item is not replaced, and another for politicians and administrative entities, where the previous item is replaced. Filceolaire (talk) 16:00, 30 March 2014 (UTC)

No idea, where GZWDer did make that remark. Succeeding albums may "replace" each other with respect to "being the most recent album" of that band - that is trivial. And books in a series may never "replace" each other beacause some no. #25 is published well after #27: But in this case they also do not "suceeed" each other: Simply being enumerated does imply "succession" only in the most general sense of succeeding each other with respect to the numbering system given. Therefore I do not see a difference between "succession with replacement" vs. "succession without replacement" however I acknowledge that "succession" perhaps should not be the generic property modeling any kind of enumerated sequence and should rather be restricted to cases where a temporal component is involved. -- Gymel (talk) 23:31, 30 March 2014 (UTC)

 Done As replaces (P1365)/replaced by (P1366), I changed the label to "predecessor"/"successor" because it is more clear and hopefully it won't cause confusion with "followed by". Notification: GZWDer, Tobias1984, Gymel, Filceolaire, Wylve.--Micru (talk) 08:50, 22 June 2014 (UTC)

preceded by (replaces the previous person)

   Done: replaces (P1365) (Talk and documentation)

Description	a separate property like follows (P155).
Data type	Item
Domain	person
Example	Barack Obama (Q76)=>George W. Bush (Q207)
Proposed by	GZWDer (talk)

Discussion

Motivation. GZWDer (talk) 16:28, 4 February 2014 (UTC)

@GZWDer: Can you choose an example that shows why we need this property? --Tobias1984 (talk) 17:40, 4 February 2014 (UTC)

 Support See discussion above. Filceolaire (talk) 20:12, 24 February 2014 (UTC)

But can we change the name to Replaced with 'preceded by' as an alias? Filceolaire (talk) 20:39, 4 March 2014 (UTC)

 Done--Micru (talk) 08:50, 22 June 2014 (UTC)

spelling/transliteration

   Not done

Description	The common spelling or transliteration of a name.
Data type	Multilingual text (not available yet)
Example	Ivan (Q830350)=>Ivan (English, French, ...), Iwan (German), Iván (Hungarian and Spanish); Li (Q686223)=>Li (Many Latin languages), Lý (Vietnamese), Lee (Cantonese Romanisation); Mohammed (Q5837762)=>Mahometus (Latin), Maometto (Italian), Μωάμεθ (Greek), Мухаммад (Russian)
Proposed by	GZWDer (talk)

Discussion

Motivation. GZWDer (talk) 14:31, 4 March 2014 (UTC)

Wouldn't this always be the same as the label? What would be the point? --Yair rand (talk) 17:21, 4 March 2014 (UTC)

The label is hard to add a source or qualifier to.

One question from me is: what is "common spelling"? Of "Elisabeth", "Elisabet" or "Eliseba", one of them is probably more common than the other in one language, but at least in Swedish, is no form of spelling of names "wrong", it's a choice of the bearer of the name, or hir parents. -- Lavallen (talk) 07:53, 8 March 2014 (UTC)

Can you give an example of where this could be useful? --Yair rand (talk) 17:04, 9 March 2014 (UTC)

 Oppose. --Yair rand (talk) 00:02, 11 June 2014 (UTC)

 Support. Should be used as a qualifier to "Official name" (approved property awaiting monolingual datatype) and other name properties. @Yair rand: Lots of things have more than one name and each has a transliteration associated with it. Using aliases doesn't let us tie the transliterations to the names. This does. Putting it in a qualifier clearly distinguishes the official name from the unofficial, crowd sourced transliterations. Filceolaire (talk) 15:49, 30 March 2014 (UTC)

 Comment I see one problem here Mohammed (Q5837762) is in Swedish often spelled differently if it has origin from North Africa or from the Middle East. -- Lavallen (talk) 16:44, 13 April 2014 (UTC)

Then it can have two transliterations. Filceolaire (talk) 13:26, 14 April 2014 (UTC)

•  Oppose - use labels/aliases. --Jakob (talk) 08:41, 14 June 2014 (UTC)
•  Comment The items for first names don't strike me as particularly useful. They tend to amalgamate first names that are similar and display odd results depending on the language settings one uses. Maybe items for first name should have the same label in all languages and connect to other items for first names based on similarities. --- Jura 09:25, 14 June 2014 (UTC)

 Not done It might be interesting to reopen the discussion once the monolingual datatype is available. Notification: GZWDer, Lavallen, Yair rand, Filceolaire, Jakob, [User talk:Jura1|Jura]]. --Micru (talk) 08:24, 22 June 2014 (UTC)

Matches lost

   Done: number of losses (P1356) (Talk and documentation)

Description	the number of games this team lost. Use as qualifier to P710 in league items.
Data type	Number (not available yet)
Template parameter	put Wikipedia infobox parameters here, if existing; ex: "population" in en:template:infobox settlement
Domain	Sports teams
Allowed values	positive whole numbers
Example	2014 FIFA World Cup Group A (Q10260330). participant (P710):Brazil national football team (Q83459) => 0
Format and edit filter validation	(sample: 7 digit number can be validated with edit filter Special:AbuseFilter/17)
Source	external reference, Wikipedia list article (either infobox or source)
Robot and gadget jobs	Should or are bots or gadgets doing any task with this? (Checking other properties for consistency, collecting data, etc.)
Proposed by	Filceolaire (talk)

Discussion

So we can record league tables. Filceolaire (talk) 19:47, 10 June 2014 (UTC)

•  Support --Paperoastro (talk) 08:02, 12 June 2014 (UTC)
•  Support --Bthfan (talk) 22:59, 13 June 2014 (UTC)
•  Support --AmaryllisGardener ^talk 19:48, 16 June 2014 (UTC)
•  Support --Casper Tinan (talk) 21:33, 16 June 2014 (UTC)
•  Done --Jakob (talk) 22:10, 17 June 2014 (UTC)

points against Number of points/goals conceded

   Done: number of points/goals conceded (P1359) (Talk and documentation)

Description	the number of games this team won goals (or points) that this team conceded in the league. Similar to number of points/goals/set scored (P1351). Use as qualifier to P710 in league items.
Data type	Number (not available yet)
Template parameter	put Wikipedia infobox parameters here, if existing; ex: "population" in en:template:infobox settlement
Domain	Sports teams
Allowed values	positive whole numbers
Example	2014 FIFA World Cup Group A (Q10260330). participant (P710):Brazil national football team (Q83459) => 3
Format and edit filter validation	(sample: 7 digit number can be validated with edit filter Special:AbuseFilter/17)
Source	external reference, Wikipedia list article (either infobox or source)
Robot and gadget jobs	Should or are bots or gadgets doing any task with this? (Checking other properties for consistency, collecting data, etc.)
Proposed by	Filceolaire (talk)

Discussion

So we can record league tables. Filceolaire (talk) 19:47, 10 June 2014 (UTC). Editted Filceolaire (talk) 08:40, 16 June 2014 (UTC)

•  Support --Paperoastro (talk) 08:13, 12 June 2014 (UTC)
•  Support --AmaryllisGardener ^talk 19:48, 16 June 2014 (UTC)
• @Filceolaire, Paperoastro, AmaryllisGardener:  Done --Jakob (talk) 20:22, 17 June 2014 (UTC)

border crossing

   Not done

Description	Listing of border crossings on some border*** item like Albania-Greece border
Data type	Item
Domain	place
Example	Albania–Greece border (Q3088686) border crossing => Kakavia border checkpoint (Q3192041)
Proposed by	Милан Јелисавчић (talk)

Discussion

Border crossings should be listed into XXX border items. Милан Јелисавчић (talk) 12:45, 18 September 2013 (UTC)

 Weak support This could cause style issues with borders that have many crossings i.e. US-Mexico. Alternatively,and without creating a new property, each individual border crossing could have the claim: <"">is a <border crossing>[of: (...) ] i.e. using qualifiers. Macadamia1472 (talk) 08:36, 13 October 2013 (UTC)

• @Милан Јелисавчић, Macadamia1472:  Not done, not enough support. --Jakob (talk) 10:44, 13 June 2014 (UTC)

Iranian National Heritage registration number

   Done: Iranian National Heritage registration number (P1369) (Talk and documentation)

Description	Registration Number in Iranian National Heritage database
Data type	String
Template parameter	"شماره ثبت" at w:fa:الگو:جعبه اطلاعات جای‌های تاریخی ایران
Domain	Iranian National Heritage (Q5958900) (21K items)
Allowed values	number. Starting from 1
Example	Persepolis (Q129072) => "20"
Format and edit filter validation	\d+
Source	infobox at Persian Wikipedia
Robot and gadget jobs	My bot will do.
Proposed by	Amir (talk)

Discussion

It's really useful number. For example if the number is lower, the heritage has been registered sooner. Amir (talk) 18:22, 15 June 2014 (UTC)

•  Support --- Jura 07:35, 22 June 2014 (UTC)
•  Support Filceolaire (talk) 13:15, 22 June 2014 (UTC)

 Done Notification: Amir, Jura, Filceolaire.--Micru (talk) 14:59, 22 June 2014 (UTC)

coincident with

   Done: partially coincident with (P1382) (Talk and documentation)

Description	Part of this item is equivilent to part of that item. Also known as "overlaps" or "concurrency" or "partial concurrency" or "concurrent with".
Data type	put datatype here (item, string, media, coordinate, monolingual text, multilingual text, time, URL, number)-invalid datatype (not in Module:i18n/datatype)
Template parameter	at least "road route" in w:en:Template:Infobox Australian road and "component highways" in w:en:Template:Infobox road, possibly others
Domain	at least geographic location (Q2221906), road (Q34442), road number (Q3241753), possibly otheres
Allowed values	same as domain
Example	Route numbers for named roads: Gateway Motorway (Q1495794) => M1 (Q6713658), qualifiers terminus location (P609)→Bald Hills (Q4850319) & terminus location (P609)→Eight Mile Plains (Q5348998) => M2 (Q6713684), qualifiers terminus location (P609)→Eight Mile Plains (Q5348998) & terminus location (P609)→Drewvale (Q5307332) Route number concurrency (Q5159092): Interstate 70 in Pennsylvania (Q933614) => Interstate 76 (Q94752), qualifiers terminus location (P609)→New Stanton (Q1185367) & terminus location (P609)→Breezewood (Q4960352) Places: for example, municipalities in the central United States have borders unbound by townships or counties, so often an entire municipality isn't part of (P361)/has part(s) (P527) a county or township, but happens to be only partially overlapping.
Robot and gadget jobs	If item1 <coincident with> item2, then generally item2 <coincident with> item1
Proposed by	Evad37 [talk]

Discussion

For those with a more mathematical / set theory inclination, this property would be for the intersection of sets A and B, where A is not part of (P361) B and B is not part of (P361) A (Venn diagram).

This is a more generalised proposal than my previous property proposal, which was only for road routes on named roads. This propoerty would probably needs to be used with a qualifier, such as applies to part (P518), in most cases. Thanks to @Closeapple: for the suggestion. Evad37 [talk] 04:42, 19 May 2014 (UTC)

•  Support per the discussion on the earlier withdrawn #route number. This is for circumstances where one thing is not entirely part of (P361) another, but overlap. In most cases this property will be symmetrical. --Closeapple (talk) 01:26, 23 June 2014 (UTC)
•  Support --Rschen7754 20:26, 23 June 2014 (UTC)
• @Evad37, Closeapple, Rschen7754:  Done --Jakob (talk) 21:49, 23 June 2014 (UTC)

ihsi identifier

   Done: IHSI ID (P1370) (Talk and documentation)

Description	Unique code for each of the Haitian administrative units, i.e. department, arrondissement, communes, and communal sections.
Data type	String
Template parameter	ihsi in fr:Modèle:Infobox Ville d'Haïti
Domain	administrative territorial entity of Haiti (Q1779026)
Allowed values	2-6 digits plus hyphen for communal sections
Example	Pestel, Grand'Anse (Q2070394) => 0834 , 0834-06, 1011-01
Proposed by	Xapitoun (talk)

Discussion

Motivation. code IHSI (Q15623818). Xapitoun (talk) 16:19, 14 January 2014 (UTC)

I corrected the domain. Can you give a source for your example? French wikipedia fr:Pestel_(Haïti) lacks also a real source for the statement. I guess that Institut Haïtien de Statistique et d'Informatique (Q15624083) is responsible for the codes. Right? --Zuphilip (talk) 19:45, 14 January 2014 (UTC)

You can look at the fr:Code_ihsi. Xapitoun (talk) 18:54, 30 January 2014 (UTC)

•  Question: Are code IHSI (Q15623818) and Q16627844 the same item? --Closeapple (talk) 08:29, 18 May 2014 (UTC)
  • Yes, they were. I merged them.--Micru (talk) 15:12, 22 June 2014 (UTC)

 Done Notification: Xapitoun, Zuphilip, Closeapple.--Micru (talk) 15:12, 22 June 2014 (UTC)

ASI Monument ID

   Done: ASI Monument ID (P1371) (Talk and documentation)

Description	identifier assigned to monuments catalogued by the Archaeological Survey of India
Data type	String
Domain	cultural property (Q2065736), geographic location (Q2221906)
Allowed values	(Taken from Wikipedia:Template:ASI_Monument_row): Composed of multiple codes to form an identifier A one-letter code for the type of recognition: N for National monument and S for State monument. Followed by a dash. A two-letter abbreviation for the state based on ISO 3166-2:IN (Q27823) (without the IN part). Followed by a dash. Sometimes a 1 letter abbreviation for the circle if there are multiple ASI defined circles active in a state. Not followed by a dash. the number that is being provided by the ASI on their website: http://asi.nic.in/asi_monu_alphalist.asp Sometimes when the description in the ASI database itself splits up the monument in multiple parts, a suffix preceded by a dash. For example: -c
Example	Taj Mahal (Q9141) => N-UP-A28
Source	Items enumerated in http://asi.nic.in/asi_monu_alphalist.asp. These are listed in List articles linked from Wikipedia:List_of_Monuments_of_National_Importance_in_India and in Commons:Category:ASI_monuments_with_known_ID's
Robot and gadget jobs	bots should be able to link pages using the the ASI Monument template on Wikimedia Commons pages from the category Commons:Category:ASI_monuments_with_known_ID's and pull data from from Wikipedia pages belonging to Wikipedia:Category:Lists_of_Monuments_of_National_Importance or Wikipedia:Category:Lists_of_State_Protected_Monuments_in_India that contain the ASI Monument row template.
Proposed by	Blademasterx (talk)

Discussion

This is a property to identify Indian monuments and would assist the work done by the Wikidata:Cultural_heritage_task_force. This property is analogous to NRHP reference number (P649) and Kulturminne ID (P758). One possible concern may be that the ASI itself only explicitly provides the last two components of the identifier, while the other components are prefixed to make the identifier unique. For example, although item 28 in the Agra Circle in the Uttar Pradesh Section of the ASI's monument list is the Taj Mahal, searching for N-UP-A28 in a search engine does not result in any references to the Taj Mahal on non-wikimedia sites. If this is not preferred, an alternate approach may be to have separate properties for the components of the identifier. Blademasterx (talk) 20:47, 31 May 2014 (UTC)

•  Support. Thanks for the thorough documentation, Blademasterx. Emw (talk) 20:54, 31 May 2014 (UTC)

 Done Notification: Blademasterx, Emw.--Micru (talk) 15:16, 22 June 2014 (UTC)

Oxford Biography Index Number

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

Description	Oxford Biography Index Number
Data type	String
Domain	Persons
Allowed values	9 digit number
Example	Samuel Johnson (Q183266) => 101014918
Source	http://www.oxforddnb.com/ Oxford DNB
Robot and gadget jobs	yes
Proposed by	Chjohnson39 (talk) 23:28, 18 May 2014 (UTC)

Discussion

Motivation. Chjohnson39 (talk) 23:28, 18 May 2014 (UTC)

 Support -- SERutherford (talk) 23:09, 29 May 2014 (UTC)

 Support --Micru (talk) 08:05, 25 June 2014 (UTC)

• @Chjohnson39, SERutherford, Micru:  Done --Jakob (talk) 14:37, 25 June 2014 (UTC)

==> Subsequently deleted, duplicate of Oxford Dictionary of National Biography ID (P1415) -- LaddΩ chat ;) 01:29, 10 November 2014 (UTC)

Enciclopédia Açoriana

   Done: Enciclopédia Açoriana ID (P1385) (Talk and documentation)

Description	entry in Enciclopédia Açoriana (Q10272704), an encyclopedia about Azores (Q25263)
Data type	String
Domain	persons, places related to the Azores.
Allowed values	see sample
Example	Teófilo Braga (Q345926): 7408

Discussion

Make it easier to reference it. --- Jura 07:55, 24 May 2014 (UTC)

 Support -- SERutherford (talk) 01:21, 8 June 2014 (UTC)

 Support --Micru (talk) 08:05, 25 June 2014 (UTC)

• @Jura1, SERutherford, Micru:  Done --Jakob (talk) 14:45, 25 June 2014 (UTC)

Japanese High School Code

   Done: Japanese High School Code (P1386) (Talk and documentation)

Description	Highschool identification code for Japanese public schools
Data type	String
Template parameter	"高校コード" in jp:template:日本の高等学校
Domain	high school (Q9826) that are located in Japan
Example	39119A
Source	jp:高知県立伊野商業高等学校
Robot and gadget jobs	It would be nice to have it imported by bots
Proposed by	Zellfaze (talk) 11:58, 13 June 2014 (UTC)

Discussion

This exists and is currently in use in infoboxes. Zellfaze (talk) 11:58, 13 June 2014 (UTC)

 Support apparently in use in JP Wikipedia. Item for above sample seems to be Ino Business High School (Q11672444). --- Jura 21:04, 24 June 2014 (UTC)

 Support --Micru (talk) 08:05, 25 June 2014 (UTC)

• @Zellfaze, Jura1, Micru:  Done --Jakob (talk) 14:48, 25 June 2014 (UTC)

ComicBookDB ID

   Done: ComicBookDB Creator ID (P1392) (Talk and documentation)

Description	label identifier per the ComicBookDB, the comic book database. - ComicBookDB (Q17275658)
Data type	String
Template parameter	en:Template:Comicbookdb
Domain	comic book (Q1760610), graphic novel (Q725377), comic strip (Q838795), and comic book publishers, distributers, artists, writers, characters, etc.
Allowed values	Numerical Unique Identifier
Example	Creator example: Rodney Caston (Q2161172) => [3]
Proposed by	DunDunDunt (talk) 19:25, 21 June 2014 (UTC)

Discussion

Perhaps it would require multiple properties for Titles, Creators, Characters, Groups, Story Arcs, Publishers, Imprints, Podcasts, Awards, etc. DunDunDunt (talk) 19:25, 21 June 2014 (UTC)

Another good thing that could come of this would be a level of verification, which is messy without some form of authority method, to comic related items like Swagman (Q16205031). Or, more importantly, aid things like Sally Acorn from Archie Comics' Sonic the Hedgehog which, as of writing this, has no main entry; but, instead has two entries in foreign languages Princess Sally Acorn (Q6030387) & Princess Sally Acorn (Q16602112). We need to add a method of verifiability to the comics subject, especially for cataloging purposes, curated sites like ComicBookDB and Grand Comics Database would be perfect for that. DunDunDunt (talk) 18:23, 22 June 2014 (UTC)

 Support --Micru (talk) 08:05, 25 June 2014 (UTC)

 Support πr² (t • c) 17:17, 25 June 2014 (UTC)

• @DunDunDunt, Micru, PiRSquared17:  Done --Jakob (talk) 20:41, 28 June 2014 (UTC)

proxy

   Done: proxy (P1393) (Talk and documentation)

Description	person authorized to act for another
Data type	Item
Template parameter	often used as "leader_title2" and "leader_name2" en:template:infobox country, and others
Domain	person (with the power) linking to the one who acts as representative
Allowed values	person, list of persons, name of office
Example	Elizabeth II (Q9682) => David Johnston (Q41564) with qualifier applies to jurisdiction (P1001) => Canada (Q16)
Source	infoboxes of applicable places, often under the title "Royal Governor", "Governor", "Governor-General", or "Lieutenant-Governor"
Robot and gadget jobs	possibly
Proposed by	Arctic.gnome (talk)

Discussion

•  Support as nominator -- Viceroys are a key position in the governments of colonies, Commonwealth countries, and the provinces/states of Canada and Australia. They rank in-between the head of state and head of government in monarchies. Right now we have them included alongside the head of state (eg, on the page Canada (Q16)), but that's not quite accurate, and it will be confusing if we want to include all past holders of the office in that field. --Arctic.gnome (talk) 21:21, 9 November 2013 (UTC)
• This is one potential solution of many to this issue. Alternatively, suppose one were to add a viceroy as a head of state (P35), using a qualifier to indicate the specific position as Governor General of Canada (Q390776), for example, along with the item for the position holding the property of subclass of (P279)viceroy (Q244741). This would supply all the necessary data, I would think. However, I think it would be better to avoid things like head of state (P35), where we duplicate a lot of data by using an unspecific property, as opposed to simply indicating in the item of the holder of the office that the holder is either instance of (P31) or position held (P39) that office. --Yair rand (talk) 06:37, 18 November 2013 (UTC)
  • I don't really like the idea of grouping viceroys with heads of state. First, because it's technically inacurate. Second, because head of state should either have a single value, in which case the viceroy would trigger a property constraint, or it should list all of the past heads of state, in which case we would have two overlapping lists of people in the same property. --Arctic.gnome (talk) 17:59, 26 November 2013 (UTC)

All nations do not always have only one "head of state". -- Lavallen (talk) 11:35, 21 February 2014 (UTC)

•  Oppose. Use position held (P39) as you have in your examples. If you want to state that Governor of New South Wales (Q1528895) (for example) is an example of a viceroy then use subclass of (P279)=viceroy (Q244741). Or I have I misunderstood what you are proposing? Filceolaire (talk) 22:11, 1 May 2014 (UTC)

I looked again and I think I get it. This property would be sort of the inverse property of position held (P39) in that it would link from the place to the person. I'm afraid I am still opposed though. Use head of state (P35) with a qualifier - that is what qualifiers are for. Filceolaire (talk) 22:19, 1 May 2014 (UTC)

• Arctic.gnome, Filceolaire, Yair rand, Lavallen: what do you think of creating a more generic property like "proxy" with qualifier of (P642)?--Micru (talk) 15:25, 22 June 2014 (UTC)
  • Works for me. Although I would use it the other way around: head of state -> Elizabeth II -> proxy -> David Johnston. --Arctic.gnome (talk) 04:44, 23 June 2014 (UTC)
    • Ok, changed the description. If there are no opposes, I will create it in a couple of days.--Micru (talk) 19:28, 23 June 2014 (UTC)

 Done It can be qualified with applies to jurisdiction (P1001). Notification: Arctic.gnome, Filceolaire, Yair rand, Lavallen.--Micru (talk) 09:06, 29 June 2014 (UTC)

Did anyone think to count how many "proxies", past and present, there are for Elizabeth II? This isn't the right way to go about this, and this proposal has very little support so far. Danrok (talk) 15:00, 30 June 2014 (UTC)

capital of

   Done: capital of (P1376) (Talk and documentation)

Description	country, state, department, canton or other administrative division of which the municipality is the governmental seat
Data type	Item
Template parameter	None yet
Domain	administrative territorial entity (Q56061)
Allowed values	any administrative territorial entity (Q56061)
Example	Berlin (Q64) capital of Germany (Q183)
Source	same sources as capital (P36)
Robot and gadget jobs	inverse of capital (P36)
Proposed by	Emw (talk)

Discussion

This property would be the inverse of capital (P36), and provide a more appropriate property than instance of (P31) for describing that the municipality is a capital. Unlike capital (P36), which is generally one-to-one, this property can sometimes be one-to-many. For example, a city can be the capital of a state and a county within that state; Boston (Q100) can be considered the capital of both Massachusetts (Q771) and Suffolk County (Q54072) -- the latter being an administrative subdivision of the former. In these cases, the 'capital of' claim for the larger administrative subdivision would be preferred.

GZWDer, Zuphilip, Holger1959, Paperoastro, Pasleim, Izno, TomT0m, Lavallen, Arctic.gnome, Felix Reimann, Yair rand, Zolo, Jacob, Michiel1972, Bever, others -- what do you think? Emw (talk) 13:43, 3 January 2014 (UTC)

• see Wikidata:Property proposal/Archive/8#of item.--GZWDer (talk) 13:46, 3 January 2014 (UTC)

  I have concerns about using an 'of' qualifier as a general purpose mechanism to introduce inverse semantics on a property instance. If we ever want to export to OWL, or use W3C query recommendations like SPARQL, or reasoning engines, then the 'of' qualifier will likely require us to jump through hoops to represent properties and compute on them as the rest of the Semantic Web does. Emw (talk) 13:58, 3 January 2014 (UTC)

  I'm not sure if it solves the problem of identifying what kind of capital we have. In Swedish we have different words for them, not depending on what kind of administrative level they are capital, but on it's purpose. A Swedish county-capital has for example a residence for the governor, while the municipality-capital(s) have an administrative office. -- Lavallen (talk) 14:16, 3 January 2014 (UTC)

  Lavallen, you're right, 'capital of' does not solve the problem of identifying what kind of capital we have. The proposed property does one thing: it defines that the subject is a capital of the object. Like Sweden, the United States also uses a different word for county "capitals" and capitals of states and the country. County capitals are called county seats; counties are much more heterogeneous than states. But I think county seats are still capitals. Do you think it would be OK to use 'capital of' for county seats and other kinds of capital for now, and leave it to later users to refine statements with a subproperty of 'capital of' if they deem it appropriate? Emw (talk) 04:32, 4 January 2014 (UTC)

•  Neutral I can see a case both for using this property and for using instance of (P31) --> capital city (Q5119) (of (P642) --> United States of America (Q30)) (for example). --Jakob (talk) 14:40, 3 January 2014 (UTC)

  Jakob, such usage of P31 is an antipattern. With that approach, it's easy to see how we could delete all item properties and simply use P31 and P279 with qualifiers. But as Zuphilip notes below and I note above, that is not a good idea: qualifiers are not supported in W3C standards. Using qualifiers to change fundamental meaning in a property -- which of (P642) does by inverting a property -- will likely make it difficult or impossible to use effectively query. We should not use 'of' in that fashion: if a property requires an inverse, then a new property should be created and be declared an inverse in its property documentation. Emw (talk) 04:32, 4 January 2014 (UTC)

   Weak support This is starting to make sense to me. --Jakob (talk) 15:56, 5 January 2014 (UTC)

• Question: there is headquarters location (P159). can municipalities, districts etc. be regarded as organisations too? Holger1959 (talk) 22:08, 3 January 2014 (UTC)

  Holger, no, not conventionally. Organizations and administrative subdivisions have certain similarities but typically neither is treated as a subclass of the other. Thus 'capital of' would not be a subproperty of 'headquarters location' (and even it were, it would be very reasonable to keep such a 'capital of' subproperty; it's used in many third-party ontologies). Emw (talk) 04:32, 4 January 2014 (UTC)

• I (currently) don't like qualifiers because there are no query tools and qualifiers are ignored in the constraint violation templates. Thus, I prefer to have a seperate inverse property. But I am not sure if we even need this. It is easy in SPARQL to ask for the subject or object of a statement. Can/Should we not try to show all data about an entity on its page, even it is was entered on another page? Let us have a look at Berlin in dbpedia and we see "dbpedia:Berlin is dbpedia-owl:capital of dbpedia:Germany" along with 7 other statements in this block. The quoted statement is occuring on the page about Berlin as well as on the page about Germany. If you imagine that all these statements may also have some starting and ending date as qualifiers, then the complexity increases. And it is almost impossible to held such information accurate and consistent over 9 different pages. --Zuphilip (talk) 22:58, 3 January 2014 (UTC)

  Zuphilip, my goal for this property is to pare down the use of instance of (P31) as a container for this information, to avoid the acutely redundant bloat in rdf:type seen in e.g. http://dbpedia.org/page/Berlin. (40 rdf:type claims!? rdf:type Thing!? Even the dbpedia-owl rdf:type claims are incredibly redundant -- PopulatedPlace is surely and subclass of Place, as are AdministrativeRegion and Region, etc.)

  I see two options: delete 'instance of: capital' claims, or move them to 'capital of' claims with this new property. I agree that both are redundant -- they could be inferred by 'Germany capital: Berlin' etc. -- but the latter seems more palatable to me. The scalability implications of using inverse properties (which are fundamentally redundant) is a larger question for Wikidata; I don't think 'capital of' would going to be a major contributor to that. Emw (talk) 04:32, 4 January 2014 (UTC)

•  Support This is an intrinsic characteristic of a city, so I'm right to use a new property instead of P31. --Paperoastro (talk) 14:43, 5 January 2014 (UTC)
•  Oppose. Completely redundant. We should also, imo, remove the instance of (P31)capital city (Q5119) statements. A city's usage as the location of the government of a subdivision, country, or international organization does not need to be duplicated on the item for the city itself. --Yair rand (talk) 21:49, 5 January 2014 (UTC)

  Yair_rand, all inverse properties are completely redundant. So do you oppose all inverse properties? If not, why, and why not permit this one? Emw (talk) 22:43, 5 January 2014 (UTC)

  In general, I oppose inverse properties. Having duplicated statements means it takes longer to add or remove a statement, and will probably result in less complete data, and less accurate data. I could see having an exception for preceded by/followed by, and maybe also for mother/father/child, but in general, I think inverse properties are a bad idea. --Yair rand (talk) 20:06, 7 January 2014 (UTC)

• My feeling with regard to the property however is that it should not be added, not necessarily because it is an inverse, but because it is an inverse of a one-to-one property, while capital of would be a one-to-many property. In most cases, I will usually oppose a transitive property which is not constrained by the number of instances its inverse claims are made. (For perspective and this reason, I would oppose the creation of "has subclasses"/"has instances", "has children" [I didn't get around to opposing this one!], and so forth.)

  Property opposition aside, someone come poke me in a week, as I have to poke Emw for some comments he's made here and elsewhere that I've been feeling opposed to. --Izno (talk) 00:47, 7 January 2014 (UTC)

  Izno, in practice, 'capital of' would almost always be one-to-one, and very occasionally be one-to-few. Compare this to contains the administrative territorial entity (P150), the inverse of located in the administrative territorial entity (P131). P150 is indeed one-to-many; see United States of America (Q30), which can barely load because of P150. The reason to oppose properties that tend to be 1-to-10+ is scalability. Since 'capital of' would almost always be 1-to-1, virtually always be 1-to-2 or -3 or less, and extremely rarely be 1-to-4 or more, I do not think this property can be reasonably opposed because of scalability concerns. Unless one is willing to nominate contains the administrative territorial entity (P150) for deletion, I do not see how this property can be reasonably opposed.

  As a side note, contrary to what you suggest above, 'capital of' would not be transitive. Utah is part of the United States, but Washington DC is not the capital of Utah. Emw (talk) 12:55, 7 January 2014 (UTC)

  Re transitive, I have no idea why that's the word I chose. I hope the rest of that sentence makes sense with that word stricken....

  As for P150, that's an ad hominem argument: whether I would have or would not have proposed a separate property which I disagree with is irrelevant to the case at hand, especially when those properties are not particularly related. (That aside, the reason I have not nominated it for deletion is because I've been letting the most recent deletion nomination sit a while.)

  You then acknowledge that 1-1 is much preferred to 1-n and that this property would be a 1-n property which is the inverse of a 1-1 property, which as I expressed duplicates the data (in this case) unnecessarily. (I will allow that there may be some cases where it may be desirable to have an inverse property which will typically be 1-n. I can't think of one.) --Izno (talk) 20:08, 7 January 2014 (UTC)

Izno, the point I was trying to make was that, when weighing the worth of a 1-to-n inverse property, we should look deeper than the fact that n > 1 in some cases before disqualifying it. If n is 1 in roughly 98% of cases, 2 in 1.5% of cases, and >= 3 in 0.5% of cases -- as would likely be the case with 'capital of', then that has vastly different implications for performance than if n is > 10 in 50% of cases -- as is likely the case with 'contains administrative subdivision'. With 'capital of', n is not always 1, but will trend very strongly toward 1. So the scalability costs of this property would be small.

The benefits of 'capital of' would be large. In items where it applies, 'capital of' is usually the most salient piece of information about the subject; it is the first statement in those items' articles -- "Berlin is the capital city of Germany", "Boston is the capital and largest city of the state of Massachusetts", etc. It's something that users would want to see directly on the item about Berlin, and not have to run through an inference engine to find out. Having the bidirectional link afforded by this kind of inverse property would also ease navigation if someone wants to use Wikidata as the basis for Linked Data applications. Additionally, this property is used by DBpedia and others -- so having 'capital of' available on Wikidata would also make interoperating with those outside projects easier. Emw (talk) 04:24, 10 January 2014 (UTC)

Emw, no you are at least wrong what dbpedia is doing, please look carefully at that page! They use http://dbpedia.org/ontology/capital as a property connecting for example Germany with Berlin. But this (one) statement is shown at both pages: Germany -> capital -> Berlin and Berlin <- is capital of <- Germany. They don't use an inverse property "is capitol of". By the way, there are 10 statements in this example and in wikidata I would suggest to add qualifiers and sources as well for all of these statements, which will I doubt can be kept consistent for two inverse properties. --Zuphilip (talk) 11:27, 10 January 2014 (UTC)

• Redundancy (@Yair rand) can be OK if the advantages are larger than the costs. In this case, I think it is certainly useful when a user can see immediately that a place is a capital. This can probably be used in infoboxes.

The main problem of redundancy are inconsistencies, statements can contradict each other. Also, when there is no «capital of» statement for New York, is that because nobody took care to add this property to the item, or is it really not a capital at all? ;-) So you still have to do a search if New York pops up as a target item in a capital (P36) claim anywhere.

This problem can be diminished if the server would add the «capital of» property automatically each time someone adds or changes a capital (P36) statement. Another solution would be that the wikibase had an index for both sides of the relationship for all item-to-item properties (for all items where a certain property is added and for all items which are mentioned in those claims, or for the subject/source and object/target items if I may say so). It seems to me that this would be in line with the OWL definition EMW pointed to. I think that I read rumours somewhere that this question is on the developers’ to-do-list.

Another problem mentioned above (by Izno) is that extra properties, especially if they come with more at once, slow the loading time very much. In fact the loading time of the standard interface is already too slow so adding any property would be bad in that respect. Lydia Pintscher assured us that this is a high priority for the developers so I hope they will find a solution soon.

Regarding the «capital of» proposal specifically: the proposal says that when a place has more than one capital function, “the 'capital of' claim for the larger administrative subdivision would be preferred.” It appears I misunderstood this (it was about ranking the statements, not about which statements to add), but to be sure, I would like to note that being a capital of a larger unit does not always mean that a place is also capital of the smaller unit it is in. For example, Amsterdam is capital of the Netherlands but not the province it belongs to.

Finally, Lavallen's remarks about how to indicate what kind of capital we talk about (for example the residence of the governor or the meeting place for the representative council). I must say that I do not completely understand Lavallen's description of the Swedish situation. If all units of the same kind (for example, all municipalities in a certain country) have the same kind of capital, it does not matter that other units have other kinds of capitals. But Lavallen's remarks could apply, for example, to South Africa, which has spread the three branches of power (legislature, executive, and judiciary) over three different capitals. I can imagine that there are many properties where we would like to add information on what it exactly means in an individual case. This could be done with qualifiers. Perhaps, no specific properties for such qualifiers are needed: for the sex or gender (P21) property, the instance of (P31) property is beginning to be used as a qualifier, see for example Chelsea Manning (Q298423). Best regards, Bever (talk) 02:09, 10 January 2014 (UTC)

Poland also have some cases where the Governors office and the Parlament is in different cities, and therefor have two capitals. (The municipality-parlaments in Sweden can be anywhere. The municipality I am subject of have it's parlament in different locations every month.)

@Bever: To make my issue more clear: What you name "county seat" in U.S. in English is translated differently for different states of U.S. in Swedish, since the function of the county looks different in different states. Therefor is it maybe difficult to implement what I talked about. We need maybe items like "county seats in Kansas" to make it work in both languages. And that is maybe to farfetched. -- Lavallen (talk) 08:45, 10 January 2014 (UTC)

•  Support — Ivan A. Krestinin (talk) 18:15, 3 February 2014 (UTC)
• I think this needs rewording so that a broader range of relations cases be included, such as U.S. County seats, French chefs-lieus of cantons and departments etc. Circeus (talk)

Circeus, those are all types of administrative territorial entity (Q56061), which is included in the description, and noted in the 'domain' field. I've tweaked the wording and added some of your examples to make this clearer. Emw (talk) 02:27, 14 May 2014 (UTC)

 Done as capital of (P1376). While neither the arguments for creation, nor the arguments for non-creation are very strong, I have just followed the utility principle. It is useful to replace "instance of:capital", with "capital of:X" as it conveys more meaning. Whatever decision is supposed to make someone unhappy, but at least having "capital of" seems more useful than not having it. Notification: Emw, GZWDer, Lavallen, Jakob, Zuphilip, Paperoastro, Yair rand, Izno, Circeus, Ivan A. Krestinin.--Micru (talk) 19:48, 23 June 2014 (UTC)

Primary destinations

   Done: primary destinations (P1302) (Talk and documentation)

Description	Primary destinations that the route serves. Usually cities and large towns, to which, as a result of their size, a high volume of traffic is expected to go
Data type	Item
Template parameter	w:en:Template:Infobox road (destinations)
Domain	Places (roades)
Allowed values	Only places in AUS, GBR, IRL, MYS, NZL, IND, according to restrictions given in w:en:Template:Infobox road.
Proposed by	Danrok (talk) 18:36, 25 February 2013 (UTC)

Discussion

• Comments: Allowed in road infoboxes for countries AUS, GBR, IRL, MYS, NZL, IND. Danrok (talk) 18:36, 25 February 2013 (UTC)

The reason that this isn't allowed for the U.S. is because this parameter was abused, with people adding their favorite towns with no regard for selectivity. Is there some sort of mechanism to prevent this from happening here? --Rschen7754 23:37, 25 February 2013 (UTC)

I think that, in time, there will be need for plenty of controls on wikidata on just about all properties, and that controls should be easier to code and implement on wikidata due to its more structured form. My understanding is that this an essential part of this project - to improve control and management of information and statistics. Danrok (talk) 00:50, 26 February 2013 (UTC)

•  Support Fully documented property. Mange01 (talk) 20:16, 13 March 2013 (UTC)
•  Support What constitutes a primary destination will remain a topic of dispute, but standards can be decided on. They will have to reflect the type of route, length of route, etc., but the community can develop those parameters over time as the property is put into use. Joshbaumgartner (talk)
• Oppose because this property will be unverifiable. I see no indication that this property would be verifiable with the documentation on en:T:Infobox road. --Izno (talk) 22:09, 22 July 2013 (UTC)
  • Actually, in some countries it is verifiable, because the government has specified them. --Rschen7754 22:26, 22 July 2013 (UTC)
•  Comment Would have to be careful in reminding people that it is only for roads i.e. not the Top 10 destinations of LAX. Macadamia1472 (talk) 06:05, 14 October 2013 (UTC)
•  Support, in places like the UK this is a verifiable property of a road that is designated by the relevant government authority. Thryduulf (talk: local | en.wp | en.wikt) 12:45, 4 May 2014 (UTC)
• @Danrok, Rschen7754, Joshbaumgartner, Mange01, Izno, Macadamia1472: @Thryduulf:  Done --Jakob (talk) 11:46, 10 May 2014 (UTC)

route number

   Not done

Description	road number (Q3241753) (also called "route number" or "road route") that applies to a named road, or a section of a named road
Data type	Item
Template parameter	"road route" in en:Template:Infobox Australian road and "component highways" in en:Template:Infobox road
Domain	road (Q34442)
Allowed values	items with instance of (P31)→road number (Q3241753)
Example	Gateway Motorway (Q1495794) => M1 (Q6713658), <qualifier> (see below) → "Bald Hills – Eight Mile Plains" => M2 (Q6713684), <qualifier> → "Eight Mile Plains – Drewvale" Ohio Turnpike (Q1131020) => Interstate 80 in Ohio (Q16149900), <qualifier> → "Indiana state line to near Youngstown" => Interstate 90 in Ohio (Q1130984), <qualifier> → "Indiana state line to near Lorain" => Interstate 76 in Ohio (Q1130920), <qualifier> → "Youngstown to Pennsylvania state line"
Proposed by	Evad37 [talk]

Discussion

Something like part of (P361) won't work, as sometimes the numbered route runs along part of a named road only – ie where the numbered route is part of (P361) the named road's length. As far as I understand, infoboxes would need a single property/value to match to an infobox field. Some sort of qualifier, specifying the section of road that the route applies to, would be needed. It could perhaps be done with two terminus location (P609) qualifers, as applies to part (P518) only has items as allowed values, not free text. - Evad37 [talk] 17:34, 24 April 2014 (UTC)

A few comments:

1. I think the <qualifier> you're looking for above is applies to part (P518).
2. Perhaps this should property should be named something like "concurrency" or "partial concurrency" or "concurrent with" or "coincident with" or "overlaps": it seems like it is describing something like concurrency (Q5159092), and would be a symmetrical property. This could also be expanded to indicate any kind of entities that form a partial union or overlap: for example, municipalities in the central United States have borders unbound by townships or counties, so often an entire municipality isn't part of (P361)/has part(s) (P527) a county or township, but happens to be only partially overlapping.
3. In contrast, "road number" or "route number" sounds like a string that contains only the base part of the route designation (which I was actually searching for as a property just now), i.e.: Interstate 74 (Q94667) "route number" => "74"; M1 (Q6713658) "route number" => "M1"; Florida State Road A1A (Q2433285) "route number" => "A1A".

Neither of the concepts in #2 and #3 appear to be Wikidata properties right now. Maybe I'm putting too much thought into it. --Closeapple (talk) 21:29, 14 May 2014 (UTC)

@Closeapple:, thanks for your comments!

1. The allowed values for applies to part (P518) is "any item", while the qualification needed is "between this location (item) and that location (another item)"
2. I like your idea of generalising to anything that forms a partial union or overlap, and I think that "coincident with" seems like the best label (with the others suitable for 'Also known as' terms). I knew route number was a bit narrow, but couldn't myself think of how to make it more general.
3. Perhaps using "road route" and "designation" would have been clearer than including the word "number" in the proposed label, but it's probably a moot point now, given that the concept can now be generalised beyond roads - Evad37 [talk] 13:34, 16 May 2014 (UTC)

 Withdrawn in favour of the more general "coincident with" proposal – unless anyone can see how something like Interstate 74 (Q94667) "route number" => "74" would be useful. - Evad37 [talk] 04:50, 19 May 2014 (UTC)

uglybridges.com ID

   Done: BridgeReports.com ID (P1380) (Talk and documentation)

Description	http://www.uglybridges.com - extremely comprehensive database based on the National Bridge Inventory. Lists every U.S. bridge over 20 feet (6 meters) long.
Data type	String
Domain	bridges
Allowed values	7-digit number
Example	Sam Eckman Covered Bridge No. 92 (Q7407441) --> 1462163. Counties can also have this property: Columbia County (Q488693) --> pa/columbia/
Robot and gadget jobs	I can try to get Jakebot to do this, but as I am not good at that kind of programming, I am not optimistic that it will work.
Proposed by	--Jakob (talk)

Discussion

 Support ----- Jura 10:26, 10 May 2014 (UTC)

•  Support. Emw (talk) 02:30, 14 May 2014 (UTC)

 Done Jakob, Jura, Emw.--Micru (talk) 20:07, 23 June 2014 (UTC)

bridgehunter.com ID

   Done: bridgehunter.com ID (P1381) (Talk and documentation)

Description	http://bridgehunter.com - much like the above proposal, but only for historic bridges
Data type	String
Domain	bridges
Allowed values	see example
Example	Hollingshead Covered Bridge No. 40 (Q5881454) --> pa/columbia/rupert/ or 30765
Robot and gadget jobs	See above
Proposed by	--Jakob (talk)

Discussion

 Support ----- Jura 10:26, 10 May 2014 (UTC)

•  Support. Emw (talk) 02:30, 14 May 2014 (UTC)

 Done Jakob, Jura, Emw.--Micru (talk) 20:12, 23 June 2014 (UTC)

Daily Ridership

   Done: daily patronage (P1373) (Talk and documentation)

Description	Number of people who ride the said line
Data type	Number (Integer)-invalid datatype (not in Module:i18n/datatype)

Discussion

 Support but should merely be 'ridership'. Qualifiers can be used to identify the specifics, as some may publish daily ridership, others may be monthly, etc. Joshbaumgartner (talk) 04:32, 9 May 2013 (UTC)

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

 Comment Is there a way to create or source directly comparable statistics for all lines? Where the same method is used to come up with the figure. Danrok (talk) 02:37, 27 August 2013 (UTC)

•  Comment I agree but I am sure there is some standard (probably annual ridership / 365 as this would take into account seasonal variation.)

 Oppose We need a more general property not only for transportation but for number of visitors for building (see below. Snipre (talk) 13:41, 15 January 2014 (UTC)

 Support--Konggaru (talk) 09:24, 28 January 2014 (UTC)

 Support. but it should be a property for a service not a track/route. Filceolaire (talk) 21:36, 24 February 2014 (UTC)

 Support. "Number of visitors" seems more suitable for static "locations". ----- Jura 10:26, 10 May 2014 (UTC)

• @Joshbaumgartner, B.Zsolt, Danrok, Snipre, 콩가루, Filceolaire: @Jura1:  Done --Jakob (talk) 18:28, 22 June 2014 (UTC)

This seems to have gone off track. It has been created and specifically says for buses, not all types of transport. 'Ridership'? What an ugly creation, and hardly a word in common usage, I believe that the word is 'patronage'.  — billinghurst sDrewth 13:02, 29 June 2014 (UTC)

Addendum. We should also be adding something to indicate that it is an average figure. I don't believe that we are specifying actual tallies.  — billinghurst sDrewth 13:04, 29 June 2014 (UTC)

MTR station code

   Done: MTR station code (P1377) (Talk and documentation)

Description	The w:MTR Corporation issues three-letter codes for all heavy-rail stations of the Integrated MTR Network, and a three-numeral code for Light Rail stops.
Data type	String
Template parameter	"code" in en:template:Infobox MTR station
Domain	place
Example	Austin station (Q838876) => AUS
Source	https://en.wikipedia.org/wiki/List_of_MTR_station_codes
Proposed by	Liangent (talk)

Discussion

Migrate data in Property:P296. See Wikidata:Properties for deletion. Liangent (talk) 21:20, 18 October 2013 (UTC)

 Oppose. Use subclass of (P279)station code (P296) with qualifier instance of (P31):'MTR station code'. Filceolaire (talk) 22:25, 18 October 2013 (UTC). Sorry. I meant P296. Filceolaire (talk) 14:18, 3 June 2014 (UTC)

 Support, How can subclass of (P279) hold string?--GZWDer (talk) 04:31, 19 October 2013 (UTC)

 Support A.Bernhard (talk) 05:07, 24 October 2013 (UTC)

 Oppose untill consensus is reached at Wikidata:Properties_for_deletions#Bahnhofscode_.28P296.29 --Pasleim (talk) 21:56, 29 October 2013 (UTC)

 Support — Ivan A. Krestinin (talk) 16:48, 11 November 2013 (UTC)

 Support. Needed for infobox ----- Jura 10:26, 10 May 2014 (UTC)

 Done Liangent, Filceolaire, GZWDer, A.Bernhard, [[User:Ivan A. Krestinin|Ivan A. Krestinin], Pasleim, Jura.--Micru (talk) 20:01, 23 June 2014 (UTC)

China railway TMIS station code

   Done: China railway TMIS station code (P1378) (Talk and documentation)

Description	A five digit code for railway stations used in China railway system
Data type	String
Template parameter	"车站代码" in zh:template:Infobox China railway station
Domain	place
Example	Shanghai railway station (Q529728) => 30671
Source	http://hyfw.12306.cn/hyinfo/action/FwcszsAction_getljcz?q=[station-name]&limit=500&sheng=&shi=&ljdm=
Proposed by	Liangent (talk)

Discussion

Migrate data in Property:P296. See Wikidata:Properties for deletion. Liangent (talk) 21:33, 18 October 2013 (UTC)

 Oppose. Use subclass of (P279)station code (P296) with qualifier instance of (P31):'TMIS station code'. This way all stations can import their station code from property P279 with the qualifiers adding precision where required, rather than each railway having to have a different infobox. Filceolaire (talk) 22:31, 18 October 2013 (UTC)

I'm puzzled about how you see that working out. This is numerical data. --Izno (talk) 02:14, 19 October 2013 (UTC)

Sorry. I meant P296 not P279. 86.6.107.229 20:31, 6 November 2013 (UTC)

 Support --A.Bernhard (talk) 02:51, 19 October 2013 (UTC)

 Support--GZWDer (talk) 04:31, 19 October 2013 (UTC)

 Oppose until consensus is reached at Wikidata:Properties_for_deletions#Bahnhofscode_.28P296.29 --Pasleim (talk) 21:58, 29 October 2013 (UTC)

 Support — Ivan A. Krestinin (talk) 16:50, 11 November 2013 (UTC)

 Support. Needed for infobox ----- Jura 10:26, 10 May 2014 (UTC)

 Done Liangent, Filceolaire, A.Bernhard, GZWDer, Ivan A. Krestinin, --Micru (talk) 20:04, 23 June 2014 (UTC)

river water basin

   Not done

Description	see #Category of river water basin above.
Data type	Item
Example	Yangtze (Q5413) => Yangtze River basin (Q15758768)
Proposed by	GZWDer (talk)

Discussion

Motivation. GZWDer (talk) 11:17, 21 February 2014 (UTC)

 Q340406 -- Lavallen (talk) 11:51, 21 February 2014 (UTC)

 Comment How many basin articles (like Yangtze River basin (Q15758768)) we have? I think only for very large rivers. So we need create thousands items without articles for category linking. — Ivan A. Krestinin (talk) 18:58, 21 February 2014 (UTC)

 Question: Can category for the water basin (P1200) (Wikidata:Property proposal/Archive/20#Category of river water basin) be generalized for this? That would at least solve article-style items pointing to article-style items. I don't know if there are Wikidata guidelines for property links from an article-item to different category-item (that is, those that don't have a direct category's main topic (P301)/topic's main category (P910) relationship. Is pointing to a category item allowed when an article-style item doesn't exist for the concept? Since categories are always marked as instance of (P31) -> Wikimedia category (Q4167836), I wouldn't think this would be a problem. --Closeapple (talk) 09:00, 18 May 2014 (UTC)

 Oppose. Use located in/on physical feature (P706) instead. Filceolaire (talk) 14:23, 3 June 2014 (UTC)

 Question (#2): Is this intended to link a single river to its basin item, or as a property for all rivers in a basin? If it's the former, this might be unique. If it's the latter, then Filceolaire's suggestion of using located in/on physical feature (P706) is more appropriate. --Closeapple (talk) 01:43, 23 June 2014 (UTC)

 Not done Per comments use located in/on physical feature (P706). Notification: GZWDer, Lavallen, Ivan A. Krestinin, Filceolaire, Closeapple,--Micru (talk) 21:23, 26 June 2014 (UTC)

German regional key

   Done: German regional key (P1388) (Talk and documentation)

Description	identifier for municipalities and unincorporated areas in Germany
Data type	String
Domain	all administrative units in Germany, from states down to municipalities and unincorporated areas
Allowed values	up to twelve-digit number (minimum two digits)
Example	Bavaria (Q980) => 09; Bad Wildbad VVG (Q9378502) => 082355008; Lalling (Q510035) => 092715202130
Source	http://de.wikipedia.org/wiki/Amtlicher_Gemeindeschl%C3%BCssel#Regionalschl.C3.BCssel Example: https://www.destatis.de/DE/ZahlenFakten/LaenderRegionen/Regionales/Gemeindeverzeichnis/Administrativ/Archiv/GVAuszugQ/AuszugGV1QAktuell.html
Proposed by	Archer90 (talk)

Discussion

In the long run German municipality key (P439) is replaced by this new key and therefore we need this new property. Archer90 (talk) 11:02, 22 April 2014 (UTC)

 Support --Pasleim (talk) 17:05, 11 May 2014 (UTC)

 Support--Micru (talk) 21:26, 26 June 2014 (UTC)

• @Archer90, Pasleim, Micru:  Done --Jakob (talk) 23:35, 26 June 2014 (UTC)

Wikimapia

   Not done

Description	item on Wikimapia
Data type	code or url-invalid datatype (not in Module:i18n/datatype)
Domain	geographic location (Q2221906) (place)
Example 1	MISSING
Example 2	MISSING
Example 3	MISSING
Robot and gadget jobs	possible bots can add them
Proposed by	Romaine (talk)

Discussion

We already add coordinates to articles, but Wikimapia gives the exact surroundings of a specific object on a map which is considered valuable information. http://wikimapia.org The links are added to articles already like on https://en.wikipedia.org/wiki/Malate_Church <> http://wikimapia.org/156598/Malate-Church-Our-Lady-of-Remedies-Parish-Church Wikipedia articles link to Wikimapia and Wikimapia links back to Wikipedia. We like to use this information on more Wikipedias. Romaine (talk) 15:10, 14 May 2014 (UTC)

 Oppose I think we shouldn't have a property for each small internet project. We have already OpenStreetMap relation ID (P402) and I can see no advantage for Wikidata if we integrate Wikimapia also. --Archer90 (talk) 16:33, 24 May 2014 (UTC)

Wikimapia is not really a "small internet project". --Jakob (talk) 17:09, 24 May 2014 (UTC)

Compared with other projects like OpenStreetMap it is a small project and has a bad coverage. OSM Stats Wikimapia Statistics Nevertheless I don't like OpenStreetMap relation ID (P402) also. --Archer90 (talk) 15:06, 30 May 2014 (UTC)

What do you mean by "the exact surroundings"?

What are the copyright terms for Wikimapia? Is it CC-BY or CC-BY-SA or is wikimapia the only ones allowed to use the info? It's not clear I prefer to work with projects who use sharealike licenses. Filceolaire (talk) 10:39, 26 May 2014 (UTC)

Their Terms of Service say CC BY-SA 3.0. But it seems unclear if they are even allowed what they're doing because they trace aerial images from Google and the terms from Google don't allow that. See this thread or Wikipedia --Archer90 (talk) 15:24, 30 May 2014 (UTC)

 Not done Not enough support. Notification: Romaine, Archer90, Filceolaire.--Micru (talk) 21:46, 26 June 2014 (UTC)

contains settlement

   Done: contains settlement (P1383) (Talk and documentation)

Description	(list of) populated places over which a municipality has jurisdiction (For administrative divisions use contains the administrative territorial entity (P150).)
Data type	Item
Domain	administrative territorial entity (Q56061)
Allowed values	human settlement (Q486972)
Example	Surdila-Greci (Q2716662) => Brateșu Vechi (Q12128374)
Source	en:Municipality
Robot and gadget jobs	The linked object should link back using located in the administrative territorial entity (P131) (asymmetric reciprocity).
Proposed by	JulesWinnfield-hu (talk)

Discussion

Property to list the settlements that belong to a municipality from the lowest level of administrative division. contains the administrative territorial entity (P150) can't be used because of constraint violation. has part(s) (P527) is not true because is not the inverse of part of (P361) but rather is the inverse of applies to jurisdiction (P1001). It applies to Romania and many other countries. --JulesWinnfield-hu (talk) 22:48, 14 June 2014 (UTC)

•  Support Good idea! --Archer90 (talk) 12:49, 17 June 2014 (UTC)
•  Support--Micru (talk) 19:05, 23 June 2014 (UTC)
• @JulesWinnfield-hu, Archer90, Micru:  Done --Jakob (talk) 21:53, 23 June 2014 (UTC)

first season

   Not done

Description	qualifier stating what was the first season of a sportsperson for a sports organization
Data type	Item
Template parameter	"years1" (also years2, years3, etc.) in en:template:Infobox basketball biography
Domain	sportsperson, so instance of athlete (Q2066131) or subclass thereof
Allowed values	items that are about sports seasons (e.g. 2012–13 NBA season (Q113619))
Example	Tony Parker (Q193108) => member of sports team (P54) = San Antonio Spurs (Q159729) and as qualifier "start season" = 2001–02 NBA season (Q1132622)
Source	external reference, Wikipedia list article (either infobox or source)
Robot and gadget jobs	Bots could check that this property gets only used for qualifiers that qualify an item that's instance of sports organization (Q4438121) or a subclass thereof
Proposed by	Bthfan (talk)

Discussion

The values for the "years1" (years2, years2, ...) fields in en:template:Infobox basketball biography is usually either one or two dates (for example: "2011-2012" or "2012"). Usually the first one means that a basketball player has played for a certain team (stored in "team1") in the 2011/2012 season. start time (P580) and end time (P582) can be used as qualifiers for member of sports team (P54) to store this information. The problem is that there are sometimes exceptions from this rule. For example what does "2012" mean, does it mean the player has played in the 2011/2012 season for that team or in the 2012/2013 season for that team? Also there are sports seasons that only take place during the year and don't span over two different years. There's also a template in the English Wikipedia that uses this information to create links to the corresponding Wikipedia articles on the individual NBA seasons, see en:template:nbay, for a real world example see this English wikipedia page under "years2" in the template. So to keep this information, we need such a property. Bthfan (talk) 12:54, 29 June 2014 (UTC)

I want to retract my property proposal. After additional discussion it looks like this property would not solve all problems or might even create new ones. See Wikidata:Project_chat#Yet_another_sports_persons_tagging_problem for related discussion on that. --Bthfan (talk) 11:26, 1 July 2014 (UTC)

 Not done Retracted.--Micru (talk) 11:55, 1 July 2014 (UTC)

last season

   Not done

Description	qualifier stating what was the last season of a sportsperson for a sports organization
Data type	Item
Template parameter	"years1" (also years2, years3, etc.) in en:template:Infobox basketball biography
Domain	sportsperson, so instance of athlete (Q2066131) or subclass thereof
Allowed values	items that are about sports seasons (e.g. 2012–13 NBA season (Q113619))
Example	Tony Parker (Q193108) => member of sports team (P54) = San Antonio Spurs (Q159729) and as qualifier "start season" = 2001–02 NBA season (Q1132622)
Source	external reference, Wikipedia list article (either infobox or source)
Robot and gadget jobs	Bots could check that this property gets only used for qualifiers that qualify an item that's instance of sports organization (Q4438121) or a subclass thereof
Proposed by	Bthfan (talk)

Discussion

The values for the "years1" (years2, years2, ...) fields in en:template:Infobox basketball biography is usually either one or two dates (for example: "2011-2012" or "2012"). Usually the first one means that a basketball player has played for a certain team (stored in "team1") in the 2011/2012 season. start time (P580) and end time (P582) can be used as qualifiers for member of sports team (P54) to store this information. The problem is that there are sometimes exceptions from this rule. For example what does "2012" mean, does it mean the player has played in the 2011/2012 season for that team or in the 2012/2013 season for that team? Also there are sports seasons that only take place during the year and don't span over two different years. There's also a template in the English Wikipedia that uses this information to create links to the corresponding Wikipedia articles on the individual NBA seasons, see en:template:nbay, for a real world example see this English wikipedia page under "years2" in the template. So to keep this information, we need such a property.

Also see Wikidata:Property_proposal/Person#first_season on this.Bthfan (talk) 12:58, 29 June 2014 (UTC)

I want to retract my property proposal. After additional discussion it looks like this property would not solve all problems or might even create new ones. See Wikidata:Project_chat#Yet_another_sports_persons_tagging_problem for related discussion on that. --Bthfan (talk) 11:26, 1 July 2014 (UTC)

 Not done Retracted. Notification: Bthfan--Micru (talk) 11:55, 1 July 2014 (UTC)

political alignment

   Done: political alignment (P1387) (Talk and documentation)

Description	Political position of the party in the political spectrum
Data type	item (none accepted)-invalid datatype (not in Module:i18n/datatype)
Template parameter	it:Template:Partito politico (collocazione) / en:Template:Infobox political party (position)
Domain	political party (Q7278)
Allowed values	Some value could be far-left (Q1129409), left-wing (Q164597), centre-left (Q737014), centrism (Q6587194), centre-right (Q844072), right-wing (Q76074), far-right (Q204481). I don't know if other values are allowed
Example	Left, Ecology and Freedom (Q286140) => left-wing (Q164597)
Format and edit filter validation	See "Allowed value"
Source	Wikipedia (infobox)
Robot and gadget jobs	no, but it could be done by bots
Proposed by	★ → Airon 90

Discussion

 Support--Micru (talk) 09:25, 22 June 2014 (UTC)

 Support I have proposed this one before. Definitely needed and useful. Danrok (talk) 15:24, 22 June 2014 (UTC)

• User:Airon90, User:Micru, User:Danrok,  Done --Jakob (talk) 13:23, 26 June 2014 (UTC)

match time of score (minutes)

   Done: match time of event (P1390) (Talk and documentation)

Description	the time (in minutes) at which the goal/points were scored. Use as a qualifiers to "goal scored by"
Data type	Number (not available yet)
Template parameter	put Wikipedia infobox parameters here, if existing; ex: "population" in en:template:infobox settlement
Domain	sports matches
Allowed values	team members.
Example	1966 FIFA World Cup Final (Q1065912) <goal scored by> Geoff Hurst (Q212738) => 120
Format and edit filter validation	(sample: 7 digit number can be validated with edit filter Special:AbuseFilter/17)
Source	external reference, Wikipedia list article (either infobox or source)
Robot and gadget jobs	Should or are bots or gadgets doing any task with this? (Checking other properties for consistency, collecting data, etc.)
Proposed by	Filceolaire (talk)

Discussion

to record details of sports matches. Filceolaire (talk) 20:11, 10 June 2014 (UTC)

•  Support --Paperoastro (talk) 08:28, 12 June 2014 (UTC)
•  Comment Note that a bot (or a human) needs to get the order right when using this property/qualifier. After all two goals could be scored in the same minute, so if we want to keep the order, the claim index needs to be correct (at least when two or more goals have the same value for this property). --Bthfan (talk) 20:20, 20 June 2014 (UTC)
•  Support Sounds good. Jianhui67 ^{talk★contribs} 07:38, 22 June 2014 (UTC)
• I have changed the title to "match time of score" so it doesn't get confused with "Duration. OTOH, wouldn't it be better to make this a generic property like "significant point in time after start"? That way it could be used for everything not just sports.--Micru (talk) 07:52, 22 June 2014 (UTC)
• @Filceolaire, Paperoastro, Bthfan, Jianhui67, Micru:  Done. I don't think a generic property would work becuase the units would have to be adjustable (one event could have a significant point in time after 2 seconds and another could have it after 2 years). --Jakob (talk) 20:51, 27 June 2014 (UTC)

Glottolog code

   Done: Glottolog code (P1394) (Talk and documentation)

Description	Code from Glottolog (also known as "Glottocode")
Data type	String
Template parameter	"glotto" (and others up to "glotto5") in en:template:infobox language
Domain	languages, dialects, language families
Allowed values	Valid Glottolog codes, see filter.
Example	Cypriot Greek (Q245899) => cypr1249
Format and edit filter validation	/^[a-z]{4}[0-9]{4}$/
Source	Glottolog, w:User:PotatoBot/Lists/Glottolog_log, w:Wikipedia:WikiProject_Languages/Glottolog_2.2_language_names, Infobox parameters, and others
Robot and gadget jobs	Bots could definitely use the sources above to fill these in.
Proposed by	πr2 (t • c)

Discussion

This would be nice to have, and useful. πr² (t • c) 19:59, 24 June 2014 (UTC)

Would there be some way to indicate the language name according to Glottolog? πr² (t • c) 20:17, 24 June 2014 (UTC)

 Support --Micru (talk) 08:05, 25 June 2014 (UTC)

 Support --AmaryllisGardener ^talk 14:29, 26 June 2014 (UTC)

• @PiRSquared17, Micru, AmaryllisGardener:  Done --Jakob (talk) 13:14, 1 July 2014 (UTC)

Linguasphere code

   Done: Linguasphere code (P1396) (Talk and documentation)

Description	Language code used by Linguasphere Observatory to identify language/dialect (LS-2010)
Data type	String
Template parameter	"lingua" in en:template:infobox language
Domain	Languages, dialects, language families (possibly including certain phylosectors and phylozones)
Allowed values	See w:Language code and w:Linguasphere#The_Linguasphere_Register_and_Linguascale_referential_framework for details and example.
Example	Patagonian Welsh (Q3798706) => 50-ABA-abf
Format and edit filter validation	It might be possible, but it may not be worth the effort.
Source	Wikipedia infobox, Linguasphere
Robot and gadget jobs	It could be done for articles with the parameter on enwiki. Not sure about others.
Proposed by	πr2 (t • c)

Discussion

This would especially be useful for dialects with no ISO 639 code. πr² (t • c) 20:59, 24 June 2014 (UTC)

 Support --Micru (talk) 08:05, 25 June 2014 (UTC)

 Support --AmaryllisGardener ^talk 18:37, 27 June 2014 (UTC)

 Support -- SERutherford (talk) 01:09, 1 July 2014 (UTC)

• @PiRSquared17, Micru, AmaryllisGardener, SERutherford:  Done --Jakob (talk) 21:07, 1 July 2014 (UTC)

FCC Facility ID

   Done: FCC Facility ID (P1400) (Talk and documentation)

Description	ID for domestic and international (shortwave) broadcast stations
Data type	String
Template parameter	"facility_id" in en:template:infobox radio station
Domain	radio and television stations
Allowed values	1 to 5 digit number
Example	WINC (Q7950766) => 41809
Source	Wikipedia
Proposed by	AmaryllisGardener talk

Discussion

Used in infoboxes. --AmaryllisGardener ^talk 14:28, 26 June 2014 (UTC)

•  Support: I thought this already existed, but I don't see it. Very useful for keeping track of U.S. broadcast stations: Changes to call sign (Q353659) are so frequent in the last 50 years that even the U.S. government quit using them as the main index. Facility ID (Q5428597) is the authority control now. --Closeapple (talk) 17:28, 1 July 2014 (UTC)
•  Comment, all of which can be dealt with once the property is created:
  • I suggest the main label FCC Facility ID instead, to avoid confusion with other uses of "facility ID".
  • These numbers can be 1 or more digits. In fact, Facility ID 1 still exists as WRCT (Q7954933). I think the highest number right now is around 65000.
  • There will be a few rare cases where this property will only apply to an item within a time period: Sometimes, when a facility's programming changes so dramatically that its identity shifts, the Wikipedia articles don't match 1-to-1 with the Facility ID. Sometimes this is because of an old, famous identity ending: There are separate items for the "old" and "new" identity. Sometimes a station is said to "move": The public is told the station moved to a different frequency, but what really happened is that all the publicly-identifying elements were dropped from one station (Facility ID) and applied to a different station (Facility ID). When there is this kind of station move — sometimes a swap with the identity on the other station — sometimes the Wikipedia article follows the facility, but occasionally the Wikipedia article follows the programming identity.
  • There will also be instances where more than one Facility ID might apply to a Wikipedia article: usually when an individual station facility is not notable enough for a Wikipedia article, but its parent station or network has an article. These should probably be handled manually (or not at all) on Wikidata.
  • This property also exists for stations outside the United States, because the U.S. has treaty obligations to coordinate frequencies with other countries. Most Canadian and Mexican stations, and any instance of clear-channel station (Q5130615) (a concept that only exists in the Americas) almost certainly has this property. Sometimes other countries neglect to legally "notify" each other of changes, though — occasionally intentionally, if a station was "grandfathered" to stay at a certain location and power that new stations aren't allowed to have.
  • A bot could probably fill most of these with the following procedure:
    1. Grab a facility_id parameter(s) from an article infobox.
    2. Find that Facility ID in the FCC broadcast databases (which are available online and updated nightly)
    3. Make sure the call sign (Q353659) in the database matches the current name of the Wikipedia article. (English Wikipedia guideline is that North American stations use their call signs as article names.)
    4. If both Facility ID in the infobox and call sign in the article title match the FCC database, update this property on Wikidata. If it doesn't match, log it somewhere: It's either an error, a parent article about multiple stations, or some other exception. --Closeapple (talk) 17:28, 1 July 2014 (UTC)
  • @Closeapple:  Changed to FCC Facility ID. That's better. --AmaryllisGardener ^talk 18:04, 1 July 2014 (UTC)
•  Support -- SERutherford (talk) 05:48, 6 July 2014 (UTC)
• @AmaryllisGardener, Closeapple, SERutherford:  Done --Jakob (talk) 13:53, 6 July 2014 (UTC)

NCI id

   Done: National Cancer Institute ID (P1395) (Talk and documentation)

Description	Id in NCI (http://www.cancer.gov) website
Data type	String
Template parameter	it can be used in infobox disease
Domain	Cancers
Allowed values	lowercase or "/"
Example	breast cancer (Q128581) --> "cancertopics/types/breast" [4]
Format and edit filter validation	\w\/ or [a-z\/]
Source	Going through this list
Robot and gadget jobs	I'll do
Proposed by	Amir (talk)

Discussion

I'm asked to do this so we can start adding them to infobox disease Amir (talk) 08:47, 17 June 2014 (UTC)

 Support --Micru (talk) 08:05, 25 June 2014 (UTC)

 Support -- SERutherford (talk) 01:12, 1 July 2014 (UTC)

 Support --AmaryllisGardener ^talk 18:05, 1 July 2014 (UTC)

• @Ladsgroup, Micru, SERutherford, AmaryllisGardener:  Done --Jakob (talk) 19:03, 1 July 2014 (UTC)

group (periodic table of elements)

   Not done

Description	The group an element belongs to
Data type	Item
Template parameter	Infobox Element (all languages)
Domain	Elements
Allowed values	All groups
Example	rubidium (Q895) = alkali metal (Q19557)
Format and edit filter validation	Subclass of group (Q83306)
Source	Physics literature and databases
Proposed by	--Tobias1984 (talk) 14:17, 8 February 2014 (UTC)

Discussion

 Support. Emw (talk) 01:04, 14 February 2014 (UTC)

 Oppose. I think 'part of' is more appropriate here. Filceolaire (talk) 22:12, 24 February 2014 (UTC)

Two things

1. I don't understand the Subclass of group (Q83306), should not this be instance of (P31) group (Q83306) ? Group of the periodical table is the definition of a class of elements, so we want some instance of it, not a subclass ... (I ùight not understodd the filter field of the template)
2. Is not it enough to use a combination of instance / subclass here ? if alkali metal (Q19557) is a class of elements rubidium (Q895) is an instance of it, or if is a class of atoms, rubidium (Q895) is a subclass of alkali metal (Q19557). with
   ⟨ alkali metal (Q19557)    ⟩ instance of (P31) ⟨ group (Q83306)    ⟩
   we got it.

• @Emw, Tobias1984, Filceolaire:  Not done - no consensus, no discussion in about four months. --Jakob (talk) 08:37, 14 June 2014 (UTC)

Monte Carlo particle number

   Done: Monte Carlo Particle Number (P1360) (Talk and documentation)

Description	Monte Carlo particle number as described in the “Review of Particle Physics” of the Particle Data Group
Data type	Number (not available yet)
Domain	subatomic particle (Q177013) (subatomic particle)
Allowed values	integers, positive or negative
Example	photon (Q3198) => 22; electron (Q2225) => 11; positron (Q3229) => -11
Source	Particle Data Group: Monte Carlo Particle Numbering Scheme
Robot and gadget jobs	a (new) bot should get the masses and uncertainties for each particle with a certain MC particle number from the computer readable version of masses and MC numbers from Particle Data Group
Proposed by	Petermahlzahn (talk)

Discussion

It is a commonly used identification number in particle physics. I suggest especially a bot which is described above under “robot and gadget jobs”. Yours.--Petermahlzahn (talk) 11:55, 12 May 2014 (UTC)

 Support - Important property for particles. Tobias1984 (talk) 10:54, 21 May 2014 (UTC)

@Tobias1984: I think there are no disadvantages. Do you want to create the property? Yours--Petermahlzahn (talk) 10:51, 13 June 2014 (UTC)

@Petermahlzahn: I was still hoping for a second opinion if we should use number or string datatype. If we don't want to make calculations, string-datatype would be more appropriate. What do you think @Jakec:? - Tobias1984 (talk) 11:14, 13 June 2014 (UTC)

I  Support the general idea, but using the datatype will be better. This looks to me to be more of a numerical ID than a number that will be used for calculations, and strings also have the advantage that we can add them to the AuthorityControl gadget. --Jakob (talk) 11:25, 13 June 2014 (UTC)

You are right. The only “calculation” is the negation for antiparticles. Also the construction of the MCPNs is done by string operations. --Petermahlzahn (talk) 13:31, 13 June 2014 (UTC)

@Petermahlzahn, Jakec:  Done -Tobias1984 (talk) 11:06, 18 June 2014 (UTC)

spelling variants

   Not done

Description	misspellings of this taxon name (spelling variants / orthographical variants)
Data type	String
Domain	taxa
Allowed values	misspellings of taxon names
Example	Argonauta boettgeri (Q3787615) => Argonauta böttgeri
Proposed by	Brya (talk)

Discussion

Motivation. This will make it possible to put misspellings that are found in the literature (or on the wwweb) in a property. These misspellings are not taxon names (may not be used as a taxon name) but they are to be found out there. Having them in property will make them easy to find (easier than when they are put in "also known as"). - Brya (talk) 17:39, 4 April 2014 (UTC)

 Support Let's try it this way. --Succu (talk) 07:47, 5 April 2014 (UTC)

Sometimes misspellings have their own article: The spelling of Aloe fleurentiniorum (Q9606058) was later corrected to Aloe fleurentiniorum (Q2649968) (see dewiki). --Succu (talk) 10:08, 5 April 2014 (UTC)

That should not be; there is just the one scientific name: Aloe fleurentiniorum (Aloe fleurentinorum is automatically correctable, and is transient). Only when a Wikipedia has two pages (one each), which I hope we are never going to see, should there be two items. - Brya (talk) 10:38, 5 April 2014 (UTC)

In such cases (one WP, 2 articles about the same taxon, at least one only bot-created), just create a redirect out of one. Stupid bots. :)  — Felix Reimann (talk) 12:42, 5 April 2014 (UTC)

@FelixReimann: So have fun and do it. :) --Succu (talk) 19:02, 23 April 2014 (UTC)

 Oppose WD has deprecated rank for such cases, use P225.  — Felix Reimann (talk) 11:08, 5 April 2014 (UTC)

They are not deprecated names, they are not names at all, and should strictly be weeded out of P225. - Brya (talk) 16:15, 5 April 2014 (UTC)

That's not enough. We have to distinguish these „names” somehow from the correct ones. So at least we need a qualifier (see my original idea). --Succu (talk) 19:02, 23 April 2014 (UTC)

I would prefer the qualifier. Misspellings were once used as a name for the taxon (otherwise we would not store it). And the property for taxon name is P225. Storing the reason, why the name is deprecated with a corresponding qualifier is of course helpful. Should we create a list of qualifiers used in combination with taxonomic properties? For example, at the tutorial?  — Felix Reimann (talk) 06:51, 24 April 2014 (UTC)

•  Comment This is outside my area of expertise, but it appears that Aloe fleurentinorum is actually a taxon name, with start/end date qualifiers, and that a deprecated rank is appropriate. The 'Wikipedia has an article about it' problem here is avoided, in this case, because Brya (talk • contribs • logs) merged the articles on pt.wp, so I think Aloe fleurentiniorum (Q9606058) should be deleted. I could not find other outdated taxon name that is Wikipedia 'notable' in their own right, having a separate article. Do any exist? John Vandenberg (talk) 10:48, 24 April 2014 (UTC)

It may appear like a taxon name, but it isn't, by definition (Art. 61). Aloe fleurentinorum and Aloe fleurentiniorum together are just one name and this name is written Aloe fleurentiniorum. This is a matter of the Rules, and theoretically it would be possible for the Rules to be changed so that it became Aloe fleurentinorum or even something else (theoretically, this won't happen).

        But, yes, I redirected the misspelling to the correct name on pt-wiki, and yes, the item here can be deleted. - Brya (talk) 16:24, 24 April 2014 (UTC)

While I accept that Aloe fleurentinorum is the only taxon name which is valid according to the rules now, 'Aloe fleurentinorum' was used as a taxon name from 1977, when it was published as the taxon name, until some point in time (when??) where someone noticed the name didnt confirm to the rules and presumably published a notice of the naming error and correction. Despite the correction, the name 'Aloe fleurentinorum' is still used as the taxon name, even in traditional print media as recently as 2005 (e.g. [5] [6] [7] [8], etc). Pushing this name to a new property, and not including it in P225 is going to break a lot of expectations. I think this is what ranking and qualifiers solves. John Vandenberg (talk) 01:57, 25 April 2014 (UTC)

+1  — Felix Reimann (talk) 02:20, 25 April 2014 (UTC)

No, in this case Aloe fleurentiniorum is the only taxon name ever. Firstly the rules are retroactive, so even if there had once been a Aloe fleurentinorum that had been OK at the time (from a historical viewpoint, under the rules then in effect), it still would not have existed, from a nomenclatural viewpoint. However, secondly, it was not OK under the rules then in effect: it has always been wrong. Under the rules, it was not published as the taxon name; what was published is the name Aloe fleurentiniorum, even though it appeared in the original publication as the misspelling Aloe fleurentinorum. There may or may not have been a correction, this is not obligatory and actually makes no difference.

        Indeed, Aloe fleurentinorum can be found in the literature, so it would be somewhat helpful (although not greatly so) to include it in Wikidata so that it can be found, hence the proposed property. But it would be hugely confusing to put it in "taxon name", as most users would then take it for a "taxon name". What a machine would make of it is speculative, but it is hard to imagine anything good. Adding "deprecated" should be reserved for taxon names that are deprecated, not for any bit of junk dragged in because it can be found somewhere. - Brya (talk) 05:37, 25 April 2014 (UTC)

@Brya: I think your last paragraph, especially the last sentence, is where we differ. The Wikidata definition of deprecated is at Wikidata:Glossary#Rank (and Help:Ranking), which indicates that the deprecated rank should be used for erroneous values. As a result, Wikidata 'deprecated' rank is *not* reserved for cases where the relevant authority/standard/etc has deemed a value to be deprecated. Our current definition of 'deprecated' is begging to become junk data (possible intentionally), which is why I think all values with a deprecated rank should be accompanied with qualifiers that explain why the value has a 'deprecated' rank, and both human and computer should ignore any value of deprecated rank unless the qualifiers of those values are understood. If the relevant authority has deprecated a value, the deprecation processes should be recorded in the qualifiers. In this case, the nomenclatural rule which deems 'Aloe fleurentinorum' to have always been 'Aloe fleurentiniorum' should be noted in the qualifier, so that it is possible to query Wikidata to obtain a list of taxon that have run afoul of that rule. Personally I think what is missing is a rank of 'invalid', as the name 'deprecated' implies the value was once valid, whereas the documentation says use 'deprecated' for values which were never valid.

If you would be happy for 'Aloe fleurentinorum' to be stored in taxon name (i.e. P225) *if* it had a new rank of 'invalid' (or similar meaning, below 'deprecated'), rather than 'deprecated' then I agree that would be the best solution and we should ask the devs if that is acceptable. John Vandenberg (talk) 07:10, 26 April 2014 (UTC)

Regarding the proposed 'spelling variants' property, that concept is needed everywhere! Perhaps a general property is needed? Or already exists?

(Assuming neither 'invalid' or 'deprecated' ranking is adopted for this scenario...) Would you consider it acceptable for this spelling variant property to be used as a qualifier for the taxon name claim. i.e.

P225 taxon name -> 'Aloe fleurentiniorum'

PXXX spelling variant -> 'Aloe fleurentinorum'

Then the new property could be used in any situation and could be included in every general search query. John Vandenberg (talk) 07:10, 26 April 2014 (UTC)

@John Vandenberg: I agree that, in part, this is a general problem, with typo's being a universal phenomenon. In the case of Aloe fleurentinorum, the spelling variant has something of a recognized status, as it is an "original spelling".

        This approach to a deprecated status may sound fine (in theory), but I am seeing a depressing amount of software that does not work as intended (like the hidden categories in Wikipedia that are not so hidden, depending on the browser used). Wikidata is supposed to be a repository of data that is generally accessible: there are no guarantees of the quality of software that will be used to extract data. Also, a human user may well not recognize such niceties as a deprecated rank (not at all obvious) or understand what this is about, even if he recognizes it. (In the context of nomenclature "valid" is a loaded word!)

        Making this a qualifier may work, although I must admit that I am not good with the technique of this. - Brya (talk) 16:53, 26 April 2014 (UTC)

Regarding the term "valid": I fear that as Wikidata is not a data repository only for taxonomic data, loaded words cannot be avoided. If we would force the developers to rename it to something fitting to taxonomy, it would surely create issues somewhere else. I think if we extend our taxonomic tutorial and the property descriptions at their talk pages and clearly outline the ambiguity, it would already help a lot. Regarding the problem itself: Let's try to do both: Reducing the rank of a taxon name (P225) is simple and directly shows that the name with higher rank is to be preferred. I'm sure that as soon as Wikipedians get used to the concept of Wikidata, this will happen quite naturally, especially if the user interface gets the promised update and improved usability. In a second step, the specific reason why a name has been set to deprecated can be added with qualifiers: this could be nomen nudum, nomen utique rejiciendum, nomen illegitimum, or whatever fits. However, I fear that Wikipedians which know the specific differences and are able to add these are much more rare (as this almost excludes everyone who writes biological articles for fun without the scientific background). Nonetheless, this information is of course very valuable and if it is added by an expert it's great.  — Felix Reimann (talk) 14:29, 2 May 2014 (UTC)

@FelixReimann: Indeed Wikidata is not a data repository only for taxonomic data, but as better than 10% of all Wikidata-items has taxon name (P225) it would make sense to take taxonomy into account.

        I can only repeat that once "taxon name" stops being reserved for taxon names, but becomes the repository for any kind of junk, it loses its utility. A deprecated taxon name should be reserved for a taxon name that is deprecated (not to be used), not for a non-taxon name.

        As far as I can see there not much chance of Wikipedians getting used to relying on Wikidata. This is especially so for taxa as there is no working taxobox-mechanism (and apparently not much chance of one in the foreseeable future). As the datastructure in Wikidata is getting more and more complicated (ever more weird), the chance of Wikipedians being able to use it to find data is becoming ever less, not better. Besides it is dubious if the data quality in Wikidata is going up or going down on average; it looks more and more like Wikidata is condemned to become a bad copy of ITIS? - Brya (talk) 17:56, 2 May 2014 (UTC)

@Brya: We need a solution. Simply removing a statement along with all qualifiers and references ist not helpfull. --Succu (talk) 07:30, 2 May 2014 (UTC)

I agree, but a solution does not seem to be forthcoming. It would be preferable to find somewhere to put this bit of metadata, especially as it is accompanied by qualifiers and references, but there is not. It would be highly confusing to the reader to put a silly error that apparently is found in two books in as a statement that this silly error is a taxon name. - Brya (talk) 18:09, 2 May 2014 (UTC)

@Brya: You can add three more publications including the original one with this „silly” spelling. Adding a qualifer misspelled as to this misspelled taxon name would clarify this referencing issue a little bit. But this would not explain why this is a correctable misspelling according to the ICN recommendations. The qualifers are not touched by this correction. You corrected tons of misspellings, which led to a lot of merged items. Thank you very much for this, but as I tried to say above: we need a way to make this transparent for our users. Regards --Succu (talk) 19:04, 2 May 2014 (UTC)

This is a mandatory correction (not a matter of recommendations). I called it a "silly error", as both IPNI and Tropicos suggest that the original spelling was Arrojadoa marylaniae which would be correct, and which would make the deviant spelling "silly". Your references make it clear that the original spelling was Arrojadoa marylanae, which makes it not a silly error, but an "incorrect original spelling".

        I am not opposed in principle to a qualifier "sometimes misspelled as" or "incorrect original spelling:". For the "sometimes misspelled as" it would be necessary to be able to add references. A practical objection is that it would probably look complicated and be not very user-friendly (and perhaps not easy for a machine to read?). An advantage of a qualifier would be that the misspelling belongs to the name, not to the taxon. - Brya (talk) 05:58, 3 May 2014 (UTC)

---

@FelixReimann, Brya, John Vandenberg: Both codes (ICN Art. 60, ICZN Art. 32) define the term original spelling and require a correction of some spelling errors. So I'd like to propose a new qualifer called original spelling with type string. I think that has some advantages:

1. It makes clear that original published spelling is different from the correct one.
2. We don't need to deprecate names that not exist.
3. It avoids constraint violations via taxon name (P225).

I hope you can agree with this. --Succu (talk) 16:36, 3 May 2014 (UTC)

Well, it is a little more limited than "spelling variants" (there may be later spelling variants that give the same problems), but "original spelling" or "incorrect original spelling" would catch the majority of the problems. - Brya (talk) 06:02, 4 May 2014 (UTC)

@Brya: Yep, the scope is narrowed. It would be great if could register usages not covered by this proposal. Then - I hope - we would find a solution for these problem cases too. --Succu (talk) 20:25, 7 May 2014 (UTC)

I dont have any objection to a qualifier approach, so this works for me! Thanks for finding a mapping to a domain specific concept. John Vandenberg (talk) 02:45, 5 May 2014 (UTC)

@Succu:: I guess that "incorrect original spelling", "unjustified emendation of original spelling", and "typographical error" would cover it. It keeps looking more complicated than just the one "spelling variant", but OK. - Brya (talk) 05:42, 8 May 2014 (UTC)

Jakec As original spelling (P1353) was created this one should be closed. --Succu (talk) 20:39, 14 June 2014 (UTC)

As not done, right? --Jakob (talk) 17:33, 28 June 2014 (UTC)

 Not done Redundant with the newly created original spelling (P1353). Notification: Brya, Succu, Felix Reimann, John Vandenberg.--Micru (talk) 10:53, 29 June 2014 (UTC)

WWF ecoregion code

   Done: WWF ecoregion code (P1294) (Talk and documentation)

Description	WWF ecoregion code
Data type	String
Domain	ecoregion (Q295469) WWF ecoregion (Q6617741)
Allowed values	two letters followed by four digits
Example	Antipodes Subantarctic Islands tundra (Q401979) => aa1101; Albany thickets (Q4709410) => at1201
Source	https://worldwildlife.org/biome-categories/terrestrial-ecoregions
Proposed by	John Vandenberg (talk)

Discussion

Commonly used ecoregion definitions. John Vandenberg (talk) 08:21, 15 April 2014 (UTC)

 Support  — Felix Reimann (talk) 08:48, 15 April 2014 (UTC)

@John Vandenberg: Do you know any databases which use this code? --Succu (talk) 19:51, 23 April 2014 (UTC)

@Succu: It is more often a field in a research dataset, which are not always published. See e.g. http://www.unep-wcmc.org/medialibrary/2012/09/05/b71492d1/PA_coverage_ecoregions_1990-2010.xlsx John Vandenberg (talk) 21:48, 23 April 2014 (UTC)

Sorry, I've should express my concerns more explicit. Can we use this new property to express something like: species A exists in ecoregion B? --Succu (talk) 22:02, 23 April 2014 (UTC)

@Succu: The relationship between species and ecoregion is modeled in the proposed property "WWF ecoregion" below; with that property we could make statements like species A exists in WWF ecoregion Blah (Q1234). 'Blah' being the Wikidata label of the ecoregion, which is useful for some purposes provided nobody changes the ecoregion's label from the official name the WWF uses, and the Q being only useful within Wikidata, but this statement wouldnt be a credible research dataset as it doesnt contain an identifier which is well defined, and also only works in languages the WWF has controlled names for their ecoregions. This property (WWF ecoregion code) will mean extracted data can make statements like species A exists in WWF ecoregion Blah ("aa1101"), which allows an extracted dataset to be published and reused by others, and that statement can be made in any language. John Vandenberg (talk) 06:56, 24 April 2014 (UTC)

 Support. -Succu (talk) 18:16, 5 May 2014 (UTC)

 on purpose: I don't really like the magic code ""4 letters followed by...", I think it's a poor label and unreadable label for an outsider like me. I would propose to replace this with a set of items with

⟨ region ⟩ instance of (P31) ⟨ WWF ecoregion ⟩

, and to remove the WWF from the property name. to retrieve the fact that the ecoregion is an ecoregion of the WWF by their instance of (P31)/P256 (P256) combination.

 Weak oppose, per my comment TomT0m ^(talk) 11:10, 24 April 2014 (UTC)

• @TomT0m:, I have changed the domain of this property since your comment from ecoregion (Q295469) to WWF ecoregion (Q6617741), as that was the result of earlier discussions with user:FelixReimann. This magic code is not a label; it is a controlled list of codes that are in common use. The first two characters represent one of the eight biogeographic realm (Q944816), as defined by the WWF: AT = Afrotropical realm (Q388614), AN = Antarctic realm (Q571337), AA = Australasian realm (Q1077944), IM = Indomalayan realm (Q757081), NA = Nearctic realm (Q737742), NT = Neotropical realm (Q217151), OC = Oceanian realm (Q303045), and PA = Palearctic realm (Q106447). John Vandenberg (talk) 03:21, 25 April 2014 (UTC)

Right. This property is meant as an authority control property. The string ids are defined by WWF.  — Felix Reimann (talk) 07:46, 25 April 2014 (UTC)

• @John Vandenberg, FelixReimann, Succu, TomT0m:  Done --Jakob (talk) 18:25, 5 May 2014 (UTC)

derived combinations

   Not done

Description	other combinations based on this taxon name
Data type	Item
Domain	taxa
Allowed values	Q template or text
Example	Felis leo (Q15294488) => Panthera leo; Sequoia gigantea (Lindl.) Decne. (Q15024525) => Sequoiadendron giganteum (Q149851)
Robot and gadget jobs	no
Proposed by	Brya (talk)

Discussion

Motivation. The reverse of basionym (P566) and the proposed new property. More or less, a special case of "synonyms". Should help in navigation and for getting an overview. This is an 'objective' mechanism, so this does not really need a reference beyond the place of original publication / autor citation. - Brya (talk) 17:39, 4 April 2014 (UTC)

 Oppose This just creates a web of items, all pointing to another one (including cycles) giving the user no change to find the current name/status of a taxon which is to prefer. I know taxonomy is complicated but, nonetheless, we should not refrain from presenting one decision as this is for what Wikidata/Wikipedia is used for.  — Felix Reimann (talk) 12:37, 5 April 2014 (UTC)

 Comment This could give an impression about the different taxonomic concepts a taxon is involved. Not all databases refleced all these (objective) combinations. A prominent example is IUCN Red List (Q32059). --Succu (talk) 21:20, 23 April 2014 (UTC)

Well, yes, creating a web of links is surely one of the main purposes of Wikidata. And note that in this case these links need not be symmetrical; the links may bring extra information. - Brya (talk) 06:06, 3 May 2014 (UTC)

• @Brya, FelixReimann, Succu:  Not done, no support after almost 3 months. --Jakob (talk) 17:31, 28 June 2014 (UTC)

original spelling

   Done: original spelling (P1353) (Talk and documentation)

Description	Original spelling of a scientfic name, which has to be corrected in accordance with ICN Art. 60, Art. 61 and ICZN Art. 32.
Data type	String
Domain	taxa, used as qualifier to taxon name (P225)
Allowed values	string
Example	Aloe steffanieana (Q612543): taxon name (P225) = Aloe steffanieana, original spelling => Aloe steffaniana
Proposed by	Succu (talk)

Discussion

We had a longer discussion about this (see above). Please see there for the pro and cons. --Succu (talk) 07:50, 25 May 2014 (UTC) @FelixReimann, Brya, John Vandenberg:

• Support as qualifier, per previous discussion. John Vandenberg (talk) 08:03, 25 May 2014 (UTC)
• Support: This would be useful, probably best as a qualifier. I am still not convinced we have a clear picture of everything that is needed; for example Isoetes and Isoëtes are both allowed and are the same spelling (nomenclaturally). And Salix ×glaucops and Salix glaucops are also the same name (nomenclaturally). - Brya (talk) 08:56, 25 May 2014 (UTC)

Let's do this step by step. The mentioned ICN specialities Isoetes/Isoëtes (Art. 60.6) and Salix ×glaucops/Salix glaucops (Art. H.3) could be resolved by another qualifier. We could call it equivalent name, but that is not an officially used term. Another labelling witch came into my mind was alternative name but this term has a well defined meaning (see Art. 18.5/6). --Succu (talk) 15:25, 25 May 2014 (UTC)

The case of Isoetes/Isoëtes does not involve more than one name; it is the same name. Perhaps "also written as" would do it. BTW for "alternative name" you need to look in Art. 36.2, not 18.5-6. - Brya (talk) 16:59, 25 May 2014 (UTC)

OK nomen alternativum is alternative family name, sorry. We can refine this new qualifier name later, if the qualifier is officially proposed. --Succu (talk) 17:20, 25 May 2014 (UTC)

Brya - a clear supporting vote should speed up the process... --Succu (talk) 19:11, 12 June 2014 (UTC)

• @Succu, John Vandenberg, Brya:  Done

AlgaeBase URL

   Done: AlgaeBase URL (P1348) (Talk and documentation)

Description	AlgaeBase URL
Data type	URL
Template parameter	name in en:template:AlgaeBase species
Domain	taxon (Q16521)
Allowed values	URL
Example	Valonia ventricosa (Q881799) => http://www.algaebase.org/search/species/detail/?species_id=S918254202b6ad95e, Valonia (Q2086405) => http://www.algaebase.org/search/genus/detail/?genus_id=Tbe0623b49301eb05, Valoniaceae (Q3010566) => http://www.algaebase.org/browse/taxonomy/detail/?taxonid=m04b4634cf8918a0c
Format and edit filter validation	URL
Source	http://www.algaebase.org
Robot and gadget jobs	probably
Proposed by	Alexander Vasenin (talk)

Discussion

AlgaeBase is an extensive and reputable source of information about marine algae. -- Alexander Vasenin (talk) 21:21, 10 June 2014 (UTC)

@Alex.vasenin: - Is "S918254202b6ad95e" (http://www.algaebase.org/search/species/detail/?species_id=S918254202b6ad95e) the identifier of the example? It seems the URL will need some more code because the genus has the URL "http://www.algaebase.org/browse/taxonomy/?id=8215". -Tobias1984 (talk) 21:40, 10 June 2014 (UTC)

@Tobias1984: On the about page (see section "permanent links") they recommend using as permanent links http://www.algaebase.org/search/?genus=genusname, http://www.algaebase.org/search/?genus=genusname&species=speciesname or http://www.algaebase.org/search/?species=genusname%20speciesname -- Alexander Vasenin (talk) 21:50, 10 June 2014 (UTC)

@Alex.vasenin:: species_id=S918254202b6ad95e seems to make an ID. What about other ranks? --Succu (talk) 21:57, 10 June 2014 (UTC)

@ Succu: We could use http://www.algaebase.org/search/genus/detail/?genus_id=Adf0189c5090003ea for genus and http://www.algaebase.org/browse/taxonomy/?id=5130 for higher taxa (however I do not know if they are really permanent). -- Alexander Vasenin (talk) 22:22, 10 June 2014 (UTC)

@Alex.vasenin: - Can you find out if they are permanent. If they are dynamic we can't use them as identifiers. -Tobias1984 (talk) 11:13, 11 June 2014 (UTC)

I'll post here as soon as I have their reply -- Alexander Vasenin (talk) 12:28, 11 June 2014 (UTC)

@Tobias1984, Succu: I've contacted Mike Guiry from AlgaeBase and he confirmed all those links are permanent (they are not sequential to prevent scraping) -- Alexander Vasenin (talk) 18:06, 11 June 2014 (UTC)

@Tobias1984, Succu, Brya: UPDATE: since AlgaeBase use cryptic anti-scraping IDs with different URL prefixes for species, genus and other taxa we have no other choice but to keep an entire URL. I've updated the proposal. -- Alexander Vasenin (talk) 14:04, 12 June 2014 (UTC)

I don't mind this, but why not also the Index Fungorum and GRIN while we are doing this? - Brya (talk) 17:23, 11 June 2014 (UTC)

Brya make a proposal ;) --Succu (talk) 19:07, 11 June 2014 (UTC)

 Support - Useful identifier. Tobias1984 (talk) 18:49, 11 June 2014 (UTC)

 Support - But we should keep in mind that Gadget-AuthorityControl.js can't handle this at the moment. --Succu (talk) 19:07, 11 June 2014 (UTC)

• @Alex.vasenin, Tobias1984, Succu, Brya:  Done as a URL. --Jakob (talk) 10:16, 13 June 2014 (UTC)

Thanks! -- Alexander Vasenin (talk) 11:11, 13 June 2014 (UTC)

Index Fungorum ID

   Done: Index Fungorum ID (P1391) (Talk and documentation)

Description	ID number in the Index Fungorum
Data type	String
Domain	taxa of fungi
Allowed values	number
Example	154022 for Cantharellus bambusae (http://www.indexfungorum.org/names/NamesRecord.asp?RecordID=154022)
Robot and gadget jobs	Add 'http://www.indexfungorum.org/names/NamesRecord.asp?RecordID=$1' to Gadget-AuthorityControl.js
Proposed by	Brya (talk) 06:01, 14 June 2014 (UTC)

Discussion

The Index Fungorum is an authoritative taxonomic and nomenclatural database for fungi. From a nomenclatural viewpoint it is the equivalent of IPNI for plants. Taxonomically it is based on the Dictionary of the Fungi. Brya (talk) 06:01, 14 June 2014 (UTC)

 Support --Succu (talk) 06:21, 14 June 2014 (UTC)

 Support -Tobias1984 (talk) 14:00, 28 June 2014 (UTC)

• @Brya, Succu, Tobias1984:  Done --Jakob (talk) 17:37, 28 June 2014 (UTC)

Element composition

   Not done

Description	Used to describe the elemental composition of a molecule
Data type	Item
Example	ethanol (Q153): Property: oxygen (Q629) Property: carbon (Q623) Property: hydrogen (Q556). Number of atoms for each element can be given as qualifier.
Proposed by	Snipre (talk) 18:04, 15 February 2014 (UTC)

•  Comment - Isn't this the same relation as made from material (P186) --Tobias1984 (talk) 18:21, 16 February 2014 (UTC)

  This can be a solution but the concept is not really the same. Snipre (talk) 01:57, 18 February 2014 (UTC)

•  Oppose. Wouldn't has part(s) (P527) do the job? Filceolaire (talk) 22:19, 24 February 2014 (UTC)

*:@Filceolaire: ethanol (Q153): has part(s) (P527) oxygen (Q629) ? No, this is not the normal use of has part(s) (P527). Snipre (talk) 23:50, 24 February 2014 (UTC)

Oxide

   Not done

Description	The oxide (Q50690) or oxides of a chemical element.
Data type	Item
Domain	chemical elements
Allowed values	oxide compounds
Example	barium oxide (Q408892) --> barium oxide (Q408892)
Source	Nature's Building Blocks An A-Z Guide of the Elements New Edition (Q15925426)
Proposed by	--Jakob (talk)

Discussion

First of a series of proposed compound properties. If this is successful, I'll propose more (e.g. chloride, nitrate, sulfate, etc.).

@Filceolaire, Tobias1984, Snipre: What do you think? --Jakob (talk) 16:19, 3 April 2014 (UTC)

@Jakec: I think it would be better if the compounds have the statements. barium oxide (Q408892) has part(s) (P527) oxygen (Q629), barium (Q1112) Filceolaire (talk) 17:12, 3 April 2014 (UTC)

+1 Snipre (talk) 18:15, 3 April 2014 (UTC)

@Filceolaire, Snipre: But that would not be the same data because not every compound with barium and oxygen is barium oxide. --Jakob (talk) 18:35, 4 April 2014 (UTC)

@Jakec: How many salts do you have ? You want to create a property for each one ? By using a composition/function group property you can do the same work with one property. Snipre (talk) 07:59, 5 April 2014 (UTC)

How is inorganic chemistry taught? I prefer two words: oxide compounds, halogenides (fluoride compounds, chloride compounds, bromide compounds, iodide compounds)

chloride ion (Q108200), fluoride ion (Q407350), iodide ion (Q407654) is subclass of Halide (Q193086); is it redundant? --Chris.urs-o (talk) 09:39, 15 April 2014 (UTC)

• @Filceolaire, Snipre, Chris.urs-o: What about just a generic property for "salt"? --Jakob (talk) 12:45, 17 April 2014 (UTC)

For salts class just used instance of (P31): sodium chloride (Q2314) instance of (P31) chloride ion (Q108200) Snipre (talk) 13:28, 17 April 2014 (UTC)

You mean

⟨ X ⟩ subclass of (P279) ⟨ sodium chloride (Q2314) ⟩

 ? For noting a special kind of type with instance of (P31) we need a dedicated item labelled salt class. TomT0m ^(talk) 16:05, 17 April 2014 (UTC)

@TomT0m:, @Jakec: , @Chris.urs-o:, I propose to continue the classification problem under the Wikidata:WikiProject Chemistry Snipre (talk) 11:41, 28 April 2014 (UTC)

Terminologia Anatomica 98

   Done: Terminologia Anatomica 98 ID (P1323) (Talk and documentation)

Description	Terminologia Anatomica (1998 edition) identifier. Unique identifier for human anatomical terminology.
Data type	String
Template parameter	"TA98" in en:Template:infobox bone, en:Template:infobox brain, en:Template:infobox muscle.
Domain	human body (Q23852) (human body)
Allowed values	Starting from 'A' and 8 numbers follow, with divided by 3 dots (like A**.*.**.***)
Example	en:Tibia tibia (Q178366) => A02.5.06.001
Format and edit filter validation	Starting from 'A' and 8 numbers follow, with divided by 3 dots (like A**.*.**.***)
Source	http://www.unifr.ch/ifaa/Public/EntryPage/ViewTAOnLine.html (TA Online top) http://www.unifr.ch/ifaa/Public/EntryPage/TA98%20Tree/Alpha/All%20KWIC%20EN.htm (full list)
Robot and gadget jobs	Is it possible to import data which already exist in English Wikipedia articles?
Proposed by	Was a bee (talk)

Discussion

Motivation. Was a bee (talk) 20:11, 17 May 2014 (UTC)

 Support -Tobias1984 (talk) 22:53, 17 May 2014 (UTC)

 Support --Petermahlzahn (talk) 22:39, 21 May 2014 (UTC)

@Was a bee, Petermahlzahn:  Done -Tobias1984 (talk) 11:18, 22 May 2014 (UTC)

facet (of a polytope)

   Done: has facet polytope (P1312) (Talk and documentation)

Description	Facet of a polytope facet (Q3847020), in the next-lower dimension.
Data type	Item
Template parameter	Cell_List in en:Template:Infobox_polychoron, faces in en:Template:Infobox_polyhedron
Domain	polytope (Q747980)
Allowed values	any polytope (direct or indirect subclass of polytope (Q747980))
Example	dodecahedron (Q178296) => pentagon (Q127840)
Format and edit filter validation	?
Source	en:Template:Infobox_polyhedron, en:Template:Infobox_polychoron
Robot and gadget jobs	quite possibly a good thing to gather from wikipedia infoboxes.
Proposed by	Opensofias (talk)

Discussion

i'd like to describe polytopes in greater detail. other desirable properties would be the number of vertices, edges, faces, cells, etc. as well as a reference to the dual polytope, the vertex figure, and the number of dimensions. but facets is a good start, i guess. i realize that geometry and graph theory aren't really considered natural science, but i it seemed it was the closest match.. Opensofias (talk) 14:28, 23 April 2014 (UTC)

 Support. I'm not very skilled on politypes but seems a start.TomT0m ^(talk) 12:05, 7 May 2014 (UTC)

 Support -Tobias1984 (talk) 07:45, 15 May 2014 (UTC)

@Opensofias, TomT0m:  Done -Tobias1984 (talk) 09:42, 15 May 2014 (UTC)

dual to

   Done: dual to (P1322) (Talk and documentation)

Description	dual of a polytope, graph or curve
Data type	Item
Template parameter	"Dual" in en:Template:Infobox_polychoron, "dual" in en:Template:Infobox_polyhedron
Domain	polytope (Q747980), curve (Q161973), planar graph (Q547823) and perhaps more.
Allowed values	direct or indirect subclass of domain, both items have same dimension. items may be self-dual.
Example	cube (Q812880) => octahedron (Q188884)
Format and edit filter validation	?
Robot and gadget jobs	yes, please. a lot of it can be gathered from infoboxes of en.wikipedia.
Proposed by	opensofias (talk)

Discussion

this is an important property of polytopes. i suggest expanding the domain to planar graphs because the dual of the graph of a polyhedron is the graph of the dual of said polyhedron. also the dual polygon is a special case of a dual curve, described here: en:Dual_curve#Generalizations --opensofias (talk) 13:03, 16 May 2014 (UTC)

 Support -Tobias1984 (talk) 19:32, 16 May 2014 (UTC)

 Done - Tobias1984 (talk) 11:09, 22 May 2014 (UTC)

study of/description of/object of the thoery

   Not done

Description	mettre la description en anglais ici, par exemple la même que celle de la documentation de l'infobox
Data type	Item
Template parameter	mettez les paramètres de l'infobox de Wikipédia ici s'ils existent. Exemple : « population » dans fr:Modèle:Infobox Subdivision administrative
Domain	sciences or theories
Allowed values	any object which is studied by the science of the theory
Example	élément d'exemple et/ou valeur d'exemple (veuillez ajouter une ou plusieurs utilisations de la propriété. Exemple : personality theory (Q1616141) => personality (Q641118)) ; particle physics (Q18334) => subatomic particle (Q177013) ; computational complexity theory (Q205084) => complexity class (Q908207) ; ...
Source	Référence externe, article de liste de Wikipédia (soit infobox, soit source)
Proposed by	TomT0m (talk)

Discussion

fairly obvious I think :) Maybe we could reuse another subject property or generalize a little bit, or merge with the subject of a book ... TomT0m (talk) 20:39, 12 February 2014 (UTC)

 Oppose See your examples. --Succu (talk) 22:34, 25 February 2014 (UTC)

@Succu:. I'm sorry, what ? Together with |https://www.wikidata.org/w/index.php?title=Q14560&curid=16611&diff=0&oldid=112204401 this diff] I would say if you want to make sense you should watch yourself :) TomT0m (talk) 22:42, 25 February 2014 (UTC)

Why should I'am watching myself exacltly TomT0m? --Succu (talk) 22:53, 25 February 2014 (UTC)

I just would like you to express a little more clearly why you are against this property and what you propose as an alternative, Succu, because I really don't understand. TomT0m (talk) 22:58, 25 February 2014 (UTC)

oh, you just modified the order of the statement, I understand the diff now, it says nothing has changed but it's not true ... TomT0m (talk) 23:06, 25 February 2014 (UTC)

•  Not done - discussion stagnated months ago and there is no support. --Jakob (talk) 10:21, 13 June 2014 (UTC)

Anime News Network ID (person)

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

Data type	String
Domain	human (Q5)
Allowed values	\d+
Example	Hideaki Anno (Q23261) → 15
Source	ru-wiki templates like ru:Template:Animenewsnetwork.com
Robot and gadget jobs	Autogeneration link in gadgets like Hideaki Anno (Q23261) → [9]
Proposed by	Vlsergey (talk)

Discussion

Just another external ID to link with, wildly used in ru-wiki. Vlsergey (talk) 10:02, 2 June 2014 (UTC)

•  Support. Hausratte (talk) 12:19, 2 June 2014 (UTC)

Anime News Network ID (manga)

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

Data type	String
Domain	manga (Q8274)
Allowed values	\d+
Example	Neon Genesis Evangelion (Q1977621) → 2440
Source	ru-wiki templates like ru:Template:Animenewsnetwork.com
Robot and gadget jobs	Autogeneration link in gadgets like Neon Genesis Evangelion (Q1977621) → [10]
Proposed by	Vlsergey (talk)

Discussion

Just another external ID to link with, wildly used in ru-wiki. Vlsergey (talk) 10:05, 2 June 2014 (UTC)

•  Support. Hausratte (talk) 12:19, 2 June 2014 (UTC)

Anime News Network ID (company)

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

Data type	String
Domain	organization (Q43229)
Allowed values	\d+
Example	MC Entertainment (Q4043396) → 3625
Source	ru-wiki templates like ru:Template:Animenewsnetwork.com
Robot and gadget jobs	Autogeneration link in gadgets like MC Entertainment (Q4043396) → [11]
Proposed by	Vlsergey (talk)

Discussion

Just another external ID to link with, wildly used in ru-wiki. Vlsergey (talk) 10:07, 2 June 2014 (UTC)

•  Support. Hausratte (talk) 12:21, 2 June 2014 (UTC)

Anime News Network ID (releases)

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

Data type	String
Domain	book (Q571), DVD (Q5294), etc. I.e. FRBR work level.
Allowed values	\d+
Robot and gadget jobs	Autogeneration link in gadgets like 25340 → http://www.animenewsnetwork.com/encyclopedia/releases.php?id=25340
Proposed by	Vlsergey (talk)

Discussion

For the sake of completenes along with previous 4 proposal, will be used later to describe referenced sources (works). Vlsergey (talk) 10:15, 2 June 2014 (UTC)

•  Support. Hausratte (talk) 12:23, 2 June 2014 (UTC)