Wikidata:Property proposal/Archive/26

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

binding of library

Done: binding of software library (P1372) (Talk and documentation)

Description	the subject is a software binding allowing to use the object software library in another programming language
Data type	Item
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	language binding (Q510878)
Allowed values	software library (Q188860)
Example	⟨ PyGObject (Q16948079) ⟩ binding of Search ⟨ Q605962 ⟩
Format and edit filter validation	(exemple : 7 chiffres peuvent être validés avec le filtre d'édition Special:AbuseFilter/17)
Proposed by	TomT0m ^(talk)

Other property : Target programming language; for the language which is allowed to use the library (Python in the example). (programming languages may not apply here because it may be several programming languages and only one target language)
Discussion

Needed to model software library bindings. TomT0m ^(talk) 18:44, 7 June 2014 (UTC)

Support--Micru (talk) 11:32, 19 June 2014 (UTC)

Support -Tobias1984 (talk) 18:02, 22 June 2014 (UTC)

@TomT0m, Micru, Tobias1984: Done --Jakob (talk) 18:24, 22 June 2014 (UTC)

TLS

Done: Theaterlexikon der Schweiz ID (P1362) (Talk and documentation)

Description	entry in the online encyclopedia Theaterlexikon der Schweiz (TLS) / Dictionnaire du théâtre en Suisse (DTS) [Theater Dictionary of Switzerland]. The online edition of 2012 is a static version of the text published in print in 2005.
Data type	String
Template parameter	Template:Theaterlexikon
Domain	people, groups, venues, organizations, concepts
Allowed values	see sample
Example	Gottfried Keller: Gottfried Keller; Mummenschanz: "Mummenschanz, Altstätten SG";
Source	Template:Theaterlexikon, BEACON file, template data
Robot and gadget jobs	import from WP

Discussion

Makes it easier to integrate links in Wikipedia. --- Jura 11:49, 3 May 2014 (UTC)

Comment: "Massgeblich für das Theaterlexikon online ist die gedruckte Buchausgabe." So we might better use stated in (P248) (or "Further reading", see above): edition (still missing) of Theaterlexikon der Schweiz (Q2416247). --Kolja21 (talk) 14:47, 3 May 2014 (UTC)
- I think that might mean that both should be identical (content still dates from 2005). I guess there could be people reading an offline version of Wikipedia (or Wikidata) who have the print version available: these people might be better served by your suggestion. For full referencing, the volume and pages of the print edition could be added as qualifier to this property. --- Jura 16:09, 3 May 2014 (UTC)

The book edition data (volume, page etc.) is cleary stated in the online edition, so I don't see much of a problem in just referencing the online edition ID. --AndreasPraefcke (talk) 09:54, 10 May 2014 (UTC)

Support for the online edition ID. For the other parameters in Template:Theaterlexikon (Q15853033) use stated in (P248), has edition or translation (P747), volume (P478), author (P50), original language of film or TV show (P364), page(s) (P304) --Pasleim (talk) 11:29, 25 May 2014 (UTC)
Support As a reference (stated in (P248)) one has Theaterlexikon der Schweiz (Q2416247) together with the entry number as chapter (P792) (or equivalently a combination of catalog code (P528) and catalog (P972)) and additionally the URL of the online version of the entry could be explicitly noted using reference URL (P854). Clearly a lot of work and a solution like for Lexicon istoric retic ID (P886) (found at Wikidata:List of properties/Others/en#Source properties) is to be preferred, which also like HDS ID (P902) (not found at Wikidata:List of properties/Generic#Authority control but most reference sources which are predominantly perceived as "online database" seem to be listed there) can be used as property directly attached to an item. Do we need special precautions in case the online and print versions start to become different in content? I.e. should we state now that the proposed property stands for one of the versions and supports the other only as far as appliccable? -- Gymel (talk) 07:04, 4 June 2014 (UTC)
Comment Sorry, I just now noticed that one is supposed to cite the work with page numbers page(s) (P304) but online access is only possible by means of the wiki page name. Thus there is no 'ID' and especially only a tuple (page, lemma) like in wikipedia templates could serve all the needs. Does this imply we have to wait for complex datatypes before we can proceed? -- Gymel (talk) 07:18, 4 June 2014 (UTC)

Comment Maybe I should have added this to another subpage. As the print and online edition are meant to be identical, it has become primarily an online database. The online edition seems stable despite its wiki format. --- Jura 17:34, 4 June 2014 (UTC)

Comment The online edition wil _not_ start to become different in content. It is just an online edition of a 2005 three-volume book, and not more. It uses MediaWiki as content management system, but it is not a real Wiki. --AndreasPraefcke (talk) 12:34, 29 June 2014 (UTC)

Done As Theaterlexikon der Schweiz ID (P1362). Notification: Jura, AndreasPraefcke, Pasleim, Gymel.--Micru (talk) 11:38, 19 June 2014 (UTC)

Matches won/games won

Done: number of wins (P1355) (Talk and documentation)

Description	the number of games this team won. 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)

Support I like how these new properties reach to organize a season for a sport league. Two questions: 1) game won or match won? 2) Exist a property for the points? --Paperoastro (talk) 08:01, 12 June 2014 (UTC)

Matches won is probably more generic and avoids confusion with tennis games. Name changed. Filceolaire (talk) 21:21, 13 June 2014 (UTC)

Comment If the goal of those new properties is to record all properties in a league table, we may need to record the number of points a team got (and which usually also is relevant for the final ranking in the league table). Example why the number of points might be relevant: 1) We don't know what specific mapping is used for number of wins/draws/defeats to points (although this could be stored somewhere) 2) The number of points might be different from the calculated "mapping". Some (real) example on this: A team failed to comply with certain rules by the league they play in. As penalty the league subtracted two points from their calculated number of points (so for example instead of 10 points for 5 wins they only have 8 points). --Bthfan (talk) 22:42, 13 June 2014 (UTC)

Somehow I overlooked the "Points for"/"points against" properties :) in the end we probably cannot calculate from most league entries the final ranking anyway (is this a goal?!) as Wikidata would need to store every final game result (in case two teams have the same number of points and we need the head-to-head record). Or we just order the teams via the index property. --Bthfan (talk) 12:11, 14 June 2014 (UTC)

We can use winner (P1346) to create an additional statement noting which team won. Filceolaire (talk) 22:39, 16 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:11, 17 June 2014 (UTC)

Matches drawn or tied

Done: number of draws/ties (P1357) (Talk and documentation)

Description	the number of games this team drew or tied. 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) => 1
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:06, 12 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:08, 17 June 2014 (UTC)

Points for

Done: points for (P1358) (Talk and documentation)

Description	the number of league points ('Pts') this team has. Use as qualifier to P710 in league items. Use number of points/goals/set scored (P1351) for total goals scored ('GF').
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) => 6
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:05, 12 June 2014 (UTC)

Could the new number of points/goals/set scored (P1351) property do double duty - for individual matches and for league tables? Filceolaire (talk) 20:03, 15 June 2014 (UTC)

@Filceolaire: I think number of points/goals/set scored (P1351) is sufficient to register the total of goals or points scored by the team ("GF" in the this example). But we need an other property for league points ("Pts" in the above mentioned example) to avoid confusion between both concepts. Casper Tinan (talk) 22:04, 15 June 2014 (UTC)

Thanks Casper. I have edited the description above to make this clear. Filceolaire (talk) 08:48, 16 June 2014 (UTC)

Support --AmaryllisGardener ^talk 19:48, 16 June 2014 (UTC)
Support --Casper Tinan (talk) 21:33, 16 June 2014 (UTC)
@Filceolaire, Paperoastro, AmaryllisGardener, Casper Tinan: Done --Jakob (talk) 22:06, 17 June 2014 (UTC)

event within

Not done

Description	The laregr event of which this is part of
Data type	Item
Template parameter	"partof " in en:Template:Infobox military conflict, "games" in
Domain	event (Q1656682)
Allowed values	items with instance of (P31) value that is itself an instance of or ultimately a subclass of (P279) occurrence (Q1190554)
Example	athletics at the 2004 Summer Olympics (Q339283)=>2004 Summer Olympics (Q8558), Battle of Albert (Q1992231)=>Battle of the Somme (Q132568), 2013 Stanley Cup playoffs (Q10856497)=>2012–13 NHL season (Q171706)
Proposed by	Circeus (talk)

Discussion

The many aliases of part of (P361) make it clear to me it is not intended for use with concepts and events, and a way to connect subevents seem more than appropriate for sports, and war-related articles, amongst others. Circeus (talk) 21:36, 27 March 2014 (UTC)

Oppose, can you provide more argument about why part of (P361) is bad for concepts/events? GranD (talk) 09:05, 26 May 2014 (UTC)

Oppose Danrok (talk) 19:27, 22 June 2014 (UTC)

@Circeus, GranD, Danrok: Not done --Jakob (talk) 20:45, 27 June 2014 (UTC)

product certification

Done: product certification (P1389) (Talk and documentation)

Description	certification for a product
Data type	Item
Template parameter	"Tipo" in it:Template:Vino
Domain	food (Q2095), wine (Q282) etc.
Allowed values	denominazione di origine controllata (Q654824), Denominazione di Origine Controllata e Garantita (Q2305591), Protected designation of origin (Q13439060), protected geographical indication (Q13533432), Traditional speciality guaranteed (Q2751813) and other
Example	Colline Novaresi (Q1109662) => denominazione di origine controllata (Q654824), Gloucester cheese (Q174539) => protected geographical indication (Q13533432)
Source	Riferimento esterno, lista delle voci su Wikipedia (infobox o fonte)
Proposed by	ValterVB (talk)

Discussion

ValterVB I think this needs a little more thought - or maybe just a different label in English.

Colline Novaresi (Q1109662) is a denominazione di origine controllata (Q654824). That tells us that Colline Novaresi (Q1109662) is a quality mark for wine (as well as being a place) and that denominazione di origine controllata (Q654824) is the type of quality mark. Similarly Gloucester cheese (Q174539), at least in the EU, is a restricted term and protected geographical indication (Q13533432) is the type of restricted term.

Under the TTIP treaty, if it ever gets passed, cheese makers in the USA would not be allowed to call their cheese Gloucester cheese (Q174539) because it isn't made from milk produced in the area near Gloucester defined in the protected geographical indication (Q13533432) standard for Gloucester cheese (Q174539).

Would subclass of (P279) do the job better? Would infoboxes still be able to find the information if we used subclass of (P279) instead? Filceolaire (talk) 13:12, 22 June 2014 (UTC)

Support I would prefer to call this property "product certification". In any case I don't see that much of a problem, we can use qualifiers to delimit to which places it applies (applies to part (P518) or a new one "applies to location:European Union"?). If US cheese-makers are not allowed to produce that cheese, then they are producing something a "subclass of" it for sure. Our items should make the distinction even if Wikipedias put the two concepts together. Alternatively consider award received (P166), but it seems to stretch the property too much.--Micru (talk) 15:13, 23 June 2014 (UTC)

Just realized that it can be qualified with applies to jurisdiction (P1001), no need for a new qualifier.--Micru (talk) 09:12, 29 June 2014 (UTC)

Support --Rippitippi (talk) 12:05, 24 June 2014 (UTC)

@ValterVB, Filceolaire, Micru, Rippitippi: Done --Jakob (talk) 20:42, 27 June 2014 (UTC)

replaces

Done: structure replaces (P1398) (Talk and documentation)

Description	the item which was replaced by this building or structure, at the same location
Data type	Item
Domain	~~person?~~, place, ~~organization?~~
Example	Royal Shakespeare Theatre (Q1375404) replaces Shakespeare Memorial Theatre (Q3481267)
Proposed by	Capmo (talk)

Discussion

replaces would be the complementary property of replaced by.

Support --Capmo (talk) 21:02, 2 February 2014 (UTC)

Support, but only for building and structure. For persons, organizations and etc. nominate separate properties please. — Ivan A. Krestinin (talk) 18:31, 3 February 2014 (UTC)

Support--GZWDer (talk) 16:18, 4 February 2014 (UTC)

* Not done @GZWDer, Ivan A. Krestinin, Capmo: Just realized that there is already follows (P155). --Jakob (talk) 17:24, 13 February 2014 (UTC)

Comment Jakec, follows (P155) makes a pair with followed by (P156), not with structure replaced by (P167). Are you implicitly suggesting that followed by (P156) and structure replaced by (P167) should be merged? Capmo (talk) 18:29, 13 February 2014 (UTC)

Yes, that seems like a good idea. --Jakob (talk) 19:00, 13 February 2014 (UTC)

I disagree, replaced by is not the same as succeeded by, in this context. The structure replaced by (P167) property has very specific use, it is not a generic "replaced by" property. Let's not muddle and mix-up data. Danrok (talk) 12:44, 17 February 2014 (UTC)

I also disagree with the merger, especially if you consider books and films, can followed by (P156) also be used for people, e.g. director of a museum?--Oursana (talk) 11:55, 25 February 2014 (UTC)

Oppose the description given in the proposal is a copy/paste of the description of an existing property. Proposal lacks a clear objective. Danrok (talk) 15:43, 27 February 2014 (UTC)

Support. Preceded by/Succeded by was created for TV episodes and books and albums - cases where the new item is in addition to the existing item. It has ben extended to cases such as political offices, administrative regions where the new item does replace the existing. I think we need this new "Replaces" property for structures and for political offices and for administrative regions and for all other cases where the new item replaces the old item. See the discussions at replaces/succeded by where @GZWDer: commented that "there're no Chinese word that means both 'replaced by' and 'following item' ". Filceolaire (talk) 14:32, 14 April 2014 (UTC)

Similarly I think structure replaced by (P167) should be made more general so it can be used for politicians, Kings, administrative regions and all cases where one item is replaced by another item. I'm not sure why @Ivan A. Krestinin: opposes this. Why Ivan? Filceolaire (talk) 15:37, 14 April 2014 (UTC)

Support --Oursana (talk) 11:47, 8 June 2014 (UTC)

@Capmo, Ivan A. Krestinin, GZWDer, Danrok, Oursana, Filceolaire: Done I see where the supporters are coming from now. --Jakob (talk) 15:33, 3 July 2014 (UTC)

State catalog of geographical names (Russia)

Done: State Catalogue of Geographical Names (Russia) ID (P1397) (Talk and documentation)

Description	number in state catalog of geographical names (Russia)
Data type	String
Template parameter	ru:Шаблон:НП код ГКГН, ru:Шаблон:Геокар код ГКГН, ru:Шаблон:Железнодорожная станция код ГКГН
Domain	geographic location (Q2221906) (place)
Allowed values	0000000-9999999
Example	settlements and other geographical objects (mountains, rivers, islands), for example, settlement Verhnenazarovskoye has number 0162115, river Laba has number 0161240
Source	https://rosreestr.ru/wps/portal/cc_ib_data_catalog_place_names
Proposed by	Dinamik (talk)

Discussion

Geographical objects in Russia should have number in state catalog of geographical names. These objects are: settlements, mountains, rivers, islands and others. Geographical objects can have alternative names - indication of number in state catalog of geographical names can helps us to discover different articles about one object. Settlements in Russia have properties OKATO code (P721) and OKTMO code (P764). Also settlements have numbers in state catalog of geographical names. Other geographical objects (mountains, rivers, islands) also have such property.
P. S. I'm not sure, that did this proposal ideally - so, please, fix my mistakes, if my proposal contains them. Dinamik (talk) 09:12, 14 March 2014 (UTC)

А собственно зачем этот код нужен? Как планируется его использовать? Какие ресурсы используют данные коды? Мастер теней (master of shadows) 23:11, 16 March 2014 (UTC)

Например, по номеру можно проверять название при возникновении сомнений в его корректности. Можно находить разные статьи, написанные об одном и том же объекте, и проверять наличие статей об объектах. Как бы то ни было, этот номер - характеристика географического объекта в России, причём более общая, чем ОКАТО и ОКТМО, т. к. присуща не только населённых пунктам, но и объектам физической географии. Dinamik (talk) 11:44, 19 March 2014 (UTC)

Пока что это просто некие числа, идентифицирующие объекты в конкретном каталоге. Большого смысла отображать их в карточках статей не вижу. Мастер теней (master of shadows) 23:13, 16 March 2014 (UTC)

Обязательно ли отображать все имеющиеся свойства в карточке? Если отображение номера в каталоге в карточке будет признано нецелесообразным, его можно будет не отображать. Dinamik (talk) 11:44, 19 March 2014 (UTC)

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

Done As State Catalogue of Geographical Names (Russia) ID (P1397). Notification: Dinamik, Мастер теней, Jura.--Micru (talk) 21:40, 1 July 2014 (UTC)

@Micru:: try the ping-template for notification to work. --- Jura 18:06, 2 July 2014 (UTC)

@Jura: thanks, I'll do that. I get notifications even when "ping" is not used, I thought everyone did.--Micru (talk) 18:15, 2 July 2014 (UTC)

Yes, but {{Ping}} is quicker to type than a userpage link. --Jakob (talk) 18:27, 2 July 2014 (UTC)

Jakob, I never typed a userpage in my life, I just copy and paste it from the signature :)--Micru (talk) 18:33, 2 July 2014 (UTC)

German Part of Municipality Key

Not done

Description	number sequence for the identification of parts of municipalities in Germany
Data type	String
Domain	all parts of municipalities and independent towns in Germany
Allowed values	three-digit number with left-hand zeros
Example	Nöham (Q51978) => 086
Source	http://odb.bavarikon.de/, Example: http://odb.bavarikon.de/exist/apps/odb/details.html?id=ODB_S00023053
Proposed by	Balû (talk)

Discussion

We want to create German official parts of municipalities from "Amtlichen Ortsverzeichnissen" (Amtliches Ortsverzeichnis für Bayern (1991) (Q15707237), Amtliches Ortsverzeichnis für Bayern (1978) (Q15715309), ...) and for this purpose create the Gemeindeteilschlüssel, too. Balû (talk) 06:59, 28 March 2014 (UTC)

Not done Not enough support. Notification: Balû.--Micru (talk) 08:57, 1 July 2014 (UTC)

tempo marking

Done: tempo marking (P1558) (Talk and documentation)

Description	indication about the speed or pace of a given musical piece
Data type	Item
Domain	music
Allowed values	tempo markings
Example	Étude No.1 from Trois nouvelles études (Q9255656) => adagio (Q482153)
Proposed by	Micru (talk)

Discussion

Needed for classical music.--Micru (talk) 15:05, 19 August 2014 (UTC)

Support Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 13:48, 2 September 2014 (UTC)

Support --Eurodyne (talk) 01:36, 4 October 2014 (UTC)

@Micru, Pigsonthewing, Eurodyne: Done --Jakob (talk) 21:44, 11 October 2014 (UTC)

Depends on

Done: depends on software (P1547) (Talk and documentation)

Description	the subject software depends on the object software
Data type	Item
Domain	software (Q7397)
Allowed values	should be instance of software (Q7397), or of a item which is a subclass of software (Q7397)
Example	SMPlayer (Q2596578) => MPlayer (Q131344)
Format and edit filter validation	(sample: 7 digit number can be validated with edit filter Special:AbuseFilter/17)
Source	infobox, software documentation, software packages metadata
Robot and gadget jobs	allowed values consistency check
Proposed by	Dereckson (talk)

Discussion

To be able to document relationship between softwares, when a software A depends of a software B Dereckson (talk) 16:26, 13 September 2014 (UTC)

Support Useful for front and back ends Okki (talk) 16:36, 13 September 2014 (UTC)

Support --Eurodyne (talk) 22:34, 2 October 2014 (UTC)

@Dereckson, Okki, Eurodyne: Done --Jakob (talk) 00:26, 3 October 2014 (UTC)

allmovie identifier

Done: AllMovie title ID (P1562) (Talk and documentation)

Description	identification code from the allmovie website (http://www.allmovie.com/)
Data type	texte unilingue ou multilingue-invalid datatype (not in Module:i18n/datatype)
Domain	film (Q11424)
Allowed values	any
Example	Beverly Hills Chihuahua 2 (Q1026756) => http://www.allmovie.com/movie/v516677
Proposed by	Pamputt (talk)

Discussion

Motivation: see Wikidata talk:WikiProject Movies Pamputt (talk) 20:34, 17 September 2014 (UTC)

Support Used on a lot of wiki (see Template:AllMovie title (Q6676293)). --ValterVB (talk) 20:40, 17 September 2014 (UTC)

Support Sure. --Eurodyne (talk) 22:00, 11 October 2014 (UTC)

@Pamputt, ValterVB, Eurodyne: Done --Jakob (talk) 22:02, 11 October 2014 (UTC)

Bulk proposal: museum databases

Many museums have online databases for artworks in their collections. We can link to it using described at URL (P973) but using dedicated properties would have several benefits:

more explicit about what the link is, which should me reuse easier. For instance, it would be easier to create a "description on the museum's website" link in Wikipedia if there were those specialized properties.
better for maintenance, eg use autolist to find artworks in the Metropolitan museum with no link to the Metropolitan museum's database.
for mulitlingual databases, we can adapt the link according to ther user's language using MediaWiki:Gadget-AuthorityControl.js.

One downside of those links is that we are not always sure that the artworks's ID are stable in the long run. But we would have the same issue if we used described at URL (P973) instead. And if the URL of the database changes but the IDs remain the same, it easy to update.

Note that we already have Atlas ID (P1212) for the Louvre (and the database of the Louvre is really not among the best that exist).

Notified participants of WikiProject Visual arts

As the number of potential properties is high, I would propose to decide it is ok to create them without discussion. I guess we could start with those that already have their templates on Commons, see Commons:Category:Museum database templates. --Zolo (talk) 17:11, 11 July 2014 (UTC)

I support this, though as you say it means potentially a huge number of properties - one for each collection. Is there really no other way? I am thinking of a property that can take a url slug and feed it into another property that holds the rest of the url and the institution name. Jane023 (talk) 21:22, 11 July 2014 (UTC)

@Zolo: How many properties do you think we're talking about? --AmaryllisGardener ^talk 00:49, 12 July 2014 (UTC)

@AmaryllisGardener: There are 61 in the category that Zolo linked to. @Zolo: Are there any databases in that category that already have properties? If so, could you list them here so that the closing admin/property creator doesn't accidentally create duplicate properties? --Jakob (talk) 01:29, 12 July 2014 (UTC)

@Jane023:: Different institutions use different URL formats, so that adapting one property to several museums seems more complicated than having several properties. I have seen that user:Multichill has been using Handle ID (P1184) for links to the Rijksmuseum (see The Milkmaid (Q167605)). I do not really understand what handle is about. Does this mean the main URL about the object in the website in the institution in charge of maintaining it. If so, that sounds useful as well, but perhaps more as a complement than a substitute for these properties.

@AmaryllisGardener, Jakec: I have done a bit of cleanup in the commons category. We now have around 50 databases. I guess we could have a few hundreds. The only one for which there appears to exist a property is Commons:Template:Louvre online. --Zolo (talk) 05:37, 12 July 2014 (UTC)

Well as I see it, museums are holders of moveable heritage, but their databases hold more or less the same thing as the databases of immoveable cultural heritage (the Wiki Loves Monuments listholders). The most basic info is just a number and a short description, but some institutions include whole stories about collection items, and there can be up to 20 fields per item with data stored with anything from restoration records to archival data on ownership. The easiest and best thing to do is to use the inventory number property in combination with the collection name per item. That said, I would really like to offer readers a link to the object in the listholder database, so if this means a property per institution, then fine. Jane023 (talk) 07:02, 12 July 2014 (UTC)

@Zolo: It would be nice to see some usage statistics and select first the most used ones. Some of those templates have only a couple of transclusions.--Micru (talk) 11:20, 17 July 2014 (UTC)

@Micru: Some of these template have been more systematically used than others }} and most artworks described at Commons currently do not have an item, so current usage may not be a reliable guide of their potential use. A look at Wikipedia categories and collection (P195) for the most obvious candidates suggests: more than 300 items for the Uffizi, at least 250 for the British Museum and the Musée d'Orsay and the British Museum, about 200 for the Museu Nacional d'Art de Catalunya, about 150 for the Metropolitan Museum, about 70 for the National Palace Musuem of Taipei. For the Uffizi and the Rijksmuseum Amsterdam, database ID corresponds to the inventory number (P217), but for readibility's and consistency's sake, I think a separate property would also make sense in this case.

Of course if we import data from Commons or from somewhere else, property usage could get much higher. See the imports from Europeana by BotMultichill. --Zolo (talk) 12:38, 17 July 2014 (UTC)

Like @Jane023: I see parallels to inventory number (P217), especially with the proposed application for instances of heritage register (Q15097084). All these scenarios have in common that literally hundreds or thousands of in practice mutually exclusive properties would have to be administered and therefore alternative approaches should be preferred which shift these multitudes away from properties to items. Also I deem a variant of described at URL (P973) as demonstrated in The Milkmaid (Q167605)) as quite appropriate. Maybe the point of the current proposal is not the fact "museum database" but rather "official address of the official description by the current entity in control of the object" which also could include references to printed catalogs or electronic identifiers like Handle ID (P1184) differing from reference URL (P854). This thorough and official object description would allow qualifiers similar to any citation (bibliographic reference or electronic identifier), but in addition a qualifier denoting the publication or database as a wikipedia item would be mandatory and these must fulfill adequate constraints (like is a museum database). -- Gymel (talk) 13:03, 17 July 2014 (UTC)

@Gymel:. "Shifting these multitudes away from properties" would require the use of qualifiers and such, making the structure significantly more complex. Using dedicated properties makes for much simpler statements. All they keys to understand these properties can need only be given in one place ("property X = url Y = museum Z"). And with the arrival of statements on properties, this place will probably be the property itself.

"official address of the official description by the current entity in control of the object" seems to imply that there is just one possible such description. A database might sometimes contradict the institution's own printed catalogues. I think it is fine to use catalog (P972) for catalogues published by the museum.

As for Handle, as I said I do not fully understand what it means, much less how it works. To me, there are two necessary conditions for using Handle instead of the ID in the museum's database:

there is a only one Handle per object
Handles are relatively easy to get from the URL of the database entry

There are also conditions that are not really necessary, but still desirable:

Handle is at least as stable as the database ID (the database entry's ID may be more stable than the whole URL, because the object's ID may remain the same when the structure of the museum's URLs change. If I understand it right, the Handle points to a unique URL, so that would not work for them)

A simple function can transform the Handle into a localized link (that is a link to the English version of the database for an English user and a Dutch version for a Dutch user).

If these criteria are met, I would be fine with using only Handle instead of a museum-specific property. If they are met only for some institutions, I would propose to use Handle for them, and use dedicated properties for instititions that do not yet support nice Handle manipulation. --Zolo (talk) 13:55, 17 July 2014 (UTC)

Zolo, it is easier for me to talk about this with a specific example. I was just going through some Commons engravings and I needed to repair a link to the Fitzwilliam museum website here. This is a similar case as what the Dutch RKD went through with their RKDartists database which runs on something called Adlib -suddenly all the urls changed from "something//priref=xxx" to "something//explore//xxx". Is this url change the handle? Or is the xxx the handle? Neither has anything to do with the actual inventory number of the object. Note that the Fitzwilliam doesn't just give their inventory number, but also the Lugt number for the engraving - we should probably make a en:Frits Lugt property too. Given your answer here above, what would your solution be for the Fitzwilliam? Jane023 (talk) 16:00, 17 July 2014 (UTC)

As I said I don't know how Handle works, but it is not the xxx (see The Night Watch (Q219831)). With a "Fitzwilliam Museum ID" property, you would only need to change the URL pattern from "something//priref" to ""something//explore//" in one page for all items (with the curreny system this page would be MediaWiki:Gadget-AuthorityControl.js‎). That said the page provides yes another URL: "Permanent Identifier: http://data.fitzmuseum.cam.ac.uk/id/object/149708". This is probably the one we want to use.

Ok I got it (I am not surprised that they have yet another url as a permanent marker). Thx Jane023 (talk) 17:38, 17 July 2014 (UTC)

About Lugt, we can create a new property, or we can use catalog (P972)+described at URL (P973). One of the benefits of specific properties over the generic catalog (P972) is that it makes external-linking easier, but in this case there does not to be any freely available online version of the catalogue, so it is less useful. --Zolo (talk) 16:35, 17 July 2014 (UTC)

Yes, I think the lugt number can just be a catalog entry, no website, so no need for a property. Jane023 (talk) 17:38, 17 July 2014 (UTC)

Cycling Quotient ID

Done: CQ Ranking male cyclist ID (P1541) (Talk and documentation)

Description	Identifier in Cycling Quotient (www.cqranking.com)
Data type	String
Domain	Persons
Allowed values	numbers
Example	Lance Armstrong (Q2172) => 7
Source	http://www.cqranking.com website
Robot and gadget jobs	Bots could import IDs from corresponding articles and templates on Wikipedia (see for exemple this template on the French Wikipedia).
Proposed by	Mathieudu68 ^talk

Discussion

This property, which looks like Cycling Archives cyclist ID (P1409), could help to improve items about cyclists. Mathieudu68 ^talk 15:54, 27 August 2014 (UTC)

Support --Micru (talk) 13:15, 12 September 2014 (UTC)

Support It does seem like we do have a good list of cyclists here. This could be useful as Mathieudu68 stated. --Eurodyne (talk) 01:32, 27 September 2014 (UTC)

@Mathieudu68, Micru, Eurodyne: Done --Jakob (talk) 12:21, 27 September 2014 (UTC)

Number of households

Done: number of households (P1538) (Talk and documentation)

Description	Number of households of a community
Data type	Quantity
Domain	Number of households (Country, Province, County, City, village)
Allowed values	Range 0 to 10^10
Example	Family Population = 10000
Source	Most of population databases has this item like this
Proposed by	Yamaha5 (talk)

Discussion

Yamaha5 (talk) 20:23, 25 September 2014 (UTC)

Support--Çalak _talk 20:21, 25 September 2014 (UTC)

Support –ebraminio^talk 20:37, 25 September 2014 (UTC)

@Yamaha5, Calak, Ebraminio: Done

Total Female Population

Done: female population (P1539) (Talk and documentation)

Description	Female population of a community
Data type	Quantity
Domain	Female Population (Country, Province, County, City, village)
Allowed values	Range 0 to 10^10
Example	Female Population = 10000
Source	Most of population databases has this item like this
Proposed by	Yamaha5 (talk)

Discussion

Yamaha5 (talk) 20:23, 25 September 2014 (UTC)

Support--Çalak _talk 20:21, 25 September 2014 (UTC)

Support –ebraminio^talk 20:37, 25 September 2014 (UTC)

@Yamaha5, Calak, Ebraminio: Done

Total Male Population

Done: male population (P1540) (Talk and documentation)

Description	Male population of a community
Data type	Quantity
Domain	Male Population (Country, Province, County, City, village)
Allowed values	Range 0 to 10^10
Example	Male Population = 10000
Source	Most of population databases has this item like this
Proposed by	Yamaha5 (talk)

Discussion

Yamaha5 (talk) 20:23, 25 September 2014 (UTC)

Support--Çalak _talk 20:21, 25 September 2014 (UTC)

Support –ebraminio^talk 20:37, 25 September 2014 (UTC)

@Yamaha5, Calak, Ebraminio: Done

Executive Order number

Done: Executive Order number (P1555) (Talk and documentation)

Description	This is the number for a federal Executive Order in the United States
Data type	String
Domain	U.S. federal executive orders (United States executive order (Q1338798))
Allowed values	sequential numbering, starting from 0 up to 13000s (but increasing as time goes on)
Example	All Executive Orders, e.g. Forbidding the Hoarding of Gold Coin, Gold Bullion and Gold Certificates (Q2656758)
Format and edit filter validation	numerical string, currently 5 digits or fewer
Source	w:List of United States federal executive orders
Proposed by	Dominic (talk)

Discussion

All federal Executive Orders in the United States are ordered sequentially, and this is a finite dataset that could be added to Wikidata. Currently, there is no way to signify the number outside of the title. Dominic (talk) 14:57, 30 September 2014 (UTC)

Support. Emw (talk) 00:50, 2 October 2014 (UTC)
Support --Eurodyne (talk) 19:42, 6 October 2014 (UTC)
@Dominic, Emw, Eurodyne: Done --Jakob (talk) 21:30, 11 October 2014 (UTC)

zbMATH Author-ID

Done: zbMATH author ID (P1556) (Talk and documentation)

Description	identifier of a person in the Zentralblatt MATH database
Data type	String
Domain	human (Q5)
Allowed values	single and unique value
Example	Israel Gelfand (Q315414) → gelfand.israel-m
Proposed by	Danneks (talk)

Discussion

Provides access to the authority control data of mathematicians in a human-readable form, consensus was reached on ru.wp side (WikiProject Mathematics) to use it as a template parameter in ru:Шаблон:Внешние ссылки. Danneks (talk) 20:30, 4 October 2014 (UTC)

Support; zbmath is a first class database of mathematicians, and we should keep links with zbmath for each item where its applicable, Bezik (talk) 21:23, 4 October 2014 (UTC)
Support. -- Vlsergey (talk) 09:36, 5 October 2014 (UTC)
Support --Eurodyne (talk) 00:44, 10 October 2014 (UTC)
@Danneks, Bezik, Vlsergey, Eurodyne: Done --Jakob (talk) 21:34, 11 October 2014 (UTC)

Enciclopedia de la Literatura en México author

Done: Enciclopedia de la Literatura en México ID (P1565) (Talk and documentation)

Description	Enciclopedia de la Literatura en México author ID
Data type	String
Domain	Persons
Allowed values	Integer (^\d+$)
Example	Francisco J. Santamaría (Q8962435) => 1004
Format and edit filter validation	^\d+$
Source	http://www.elem.mx/autores
Robot and gadget jobs	Using mix'n'match
Proposed by	Magnus Manske (talk)

Discussion

Suggested to me by a Mexican digital humanities student. Site has ca. 5,000 authors, stable IDs, relevant. The site and dataset are mainted by the Mexican National Council for Culture and Arts. Magnus Manske (talk) 11:40, 12 October 2014 (UTC)

Support --Kolja21 (talk) 04:28, 13 October 2014 (UTC)

Support Per nom. Eurodyne (talk) 00:33, 14 October 2014 (UTC)

@Magnus Manske, Kolja21, Eurodyne:: done. --Zolo (talk) 10:40, 18 October 2014 (UTC)

intersections

Not done

Description	Notable intersections of a highway
Data type	Item
Domain	Highways
Allowed values	Highways
Example	Interstate 80 (Q94873) --> Interstate 81 (Q94877)
Source	Google maps and other online mapping projects
Proposed by	--Jakob (Scream about the things I've broken)

Discussion

Comment - Qualifier for location of intersection would be useful. We might have this already, I'm not sure. --Jakob (Scream about the things I've broken) 00:48, 8 October 2013 (UTC)

Support per nom. Joshbaumgartner (talk) 11:26, 12 October 2013 (UTC)

Comment When/where do you think this information would be used? Macadamia1472 (talk) 08:41, 13 October 2013 (UTC)

What is "notable"? --Rs chen 7754 19:29, 12 October 2013 (UTC)

Oppose until we have a definition of notable. --Rs chen 7754 21:53, 18 October 2013 (UTC)

Notable means it has its own item already. --Jakob (Scream about the things I've broken) 21:50, 22 October 2013 (UTC)

What would you do for something like w:en:Interstate 5 in California, however? --Rs chen 7754 21:57, 23 October 2013 (UTC)

@Rschen7754: I have not been watching this page, which is why it took me this long to get back. Items for pages like the one you mentioned would not use this property. --Jakob (Scream about the things I've broken) 17:11, 8 November 2013 (UTC)

Yeah, I can't support this until something more concrete is nailed down. --Rs chen 7754 18:14, 8 November 2013 (UTC)

@Rschen7754: Seems pretty concrete to me. @Macadamia1472: This might be useful in the mileage tables. --Jakob (talk) 01:55, 31 December 2013 (UTC)

Comment The information that interstate 80 intersect with interstate 81 somewhere on its 2500 miles seems useless for me. Do you not want to say where they intersect? The infobox in en:Interstate_80 shows major junctions with information where they intersect and the order might be important as well. Maybe, one could think of a property that a "place lies on/near the road" and/or a "road goes trough/nearby a place". An intersection between two roads would then be a place with two or more of these properties. --Zuphilip (talk) 12:45, 31 December 2013 (UTC)

I imagined we would have something like Interstate 80 (Q94873) intersects Interstate 81 (Q94877) at coordinate location (P625) 41.045958,-76.013775. --Jakob (talk) 13:13, 31 December 2013 (UTC)

- Still oppose; where's the constraints? --Rs chen 7754 14:59, 3 January 2014 (UTC)
  - @Rschen7754: How about, must at the level of state highway or above? Not every little road that crosses a highway will be added. --Jakob (talk) 15:46, 13 May 2014 (UTC)
    - @Jakec: But what about w:en:California State Route 1? --Rs chen 7754 08:52, 18 June 2014 (UTC)
      - @Rschen7754: If your asking about concurrences, these could be tagged with a qualifier like instance of (P31) --> concurrence. --Jakob (talk) 09:27, 18 June 2014 (UTC)
        @Jakec: have you noticed how many junctions would have to be included on such an item? --Rs chen 7754 10:03, 18 June 2014 (UTC)
        @Rschen7754: Maybe 50-ish at most? I realized that national-level highways are more of a concern here, so perhaps they should only be linked to other national-level highways, not state-level highways (state-level highways can still be linked to national-level ones). --Jakob (talk) 16:44, 22 June 2014 (UTC)
        Certainly more than 50, and California State Route 1 is certainly not a national highway. --Rs chen 7754 18:48, 23 June 2014 (UTC)
        @Rschen7754: I know that. "Certainly more than 50" - OK, about 60. Most highways won't have nearly as many, and can thus use this easily. For instance, Pennsylvania Route 487 (Q1339535) has only 14, as does Pennsylvania Route 42 (Q1052748). --Jakob (talk) 21:43, 23 June 2014 (UTC)
        What about w:en:California State Route 33? w:en:California State Route 99? w:en:U.S. Route 101 in California? w:en:Interstate 5 in California? You're clearly not thinking this through. --Rs chen 7754 22:07, 23 June 2014 (UTC)
        The first two only have a few dozen intersections. The last two are national-level highways, so intersections to state-level highways wouldn't be mentioned. --Jakob (talk) 23:03, 23 June 2014 (UTC)
        But really, when we've done this for the infobox on enwiki, we had to put in a hard limit of 10 junctions, because people would keep adding in their favorite junctions. And I never knew that U.S. Route 101 in California and Interstate 5 in California were national articles... --Rs chen 7754 00:25, 24 June 2014 (UTC)
Support. Clearly useful for roads. Seems reasonably constrained; I don't see any massive room for misuse, especially given the provisional definition of 'notable' above. Emw (talk) 02:20, 14 May 2014 (UTC)
Weak oppose. I think this might be going too far in the way of simply duplicating large amounts of OSM data. --Yair rand (talk) 02:11, 24 June 2014 (UTC)
- This is the data used for creating a diagram of a highway so I think it's okay that it duplicates OSM data. Support Filceolaire (talk) 14:43, 29 June 2014 (UTC)

Jakob, Macadamia1472, Joshbaumgartner, Rs, Zuphilip, Emw, Yair rand, Filceolaire, regarding the limits. What do you think of calling this property "notable intersections" and only allowing as many values as are used by the infoboxes linked to the item?--Micru (talk) 09:06, 1 July 2014 (UTC)

Well, but on en.wikipedia there is a hard limit of 10 junctions, while on de.wikipedia they list every junction... --Rs chen 7754 10:04, 1 July 2014 (UTC)

Rschen7754, can you provide some examples of articles with a high number of junctions?--Micru (talk) 10:47, 1 July 2014 (UTC)

I already have above: w:en:California State Route 1, w:en:California State Route 99, w:en:California State Route 33, w:en:Interstate 5 in California... --Rs chen 7754 10:57, 1 July 2014 (UTC)

Rschen7754, I was referring to the junctions in the infobox. Those articles contain all the junctions, but in the infobox there are only major junctions. I'm seeing that dewiki is not listing them all either.--Micru (talk) 11:07, 1 July 2014 (UTC)

Compare w:de:California State Route 52 and w:en:California State Route 52. --Rs chen 7754 11:14, 1 July 2014 (UTC)

Rschen7754, what is the problem? Each wikipedia can use a different criteria for selecting their major junctions, it is just a matter of qualifying them with stated in (P248) or criterion used (P1013). Later on it is possible to filter them accordingly with a lua script.--Micru (talk) 11:22, 1 July 2014 (UTC)

@Rschen: Is your main objection that items could become overloaded with statements and become impossible to view without crashing browsers, or is it something else? --Jakob (talk) 00:11, 2 July 2014 (UTC)

Partially, and because of the years of work it would take to transfer data over here. Also, on the English Wikipedia I have seen dozens of editors revert warring over the tiniest details of a junction list. I don't want to transfer those edit wars over here. (Keep in mind that I've been working with road junction lists and road infoboxes since 2006). --Rs chen 7754 00:24, 2 July 2014 (UTC)

Want a buttload of junctions on a state-level highway? w:en:Kentucky Route 80#Major intersections. --NE2 (talk) 19:35, 1 July 2014 (UTC)

Oppose at this time, as the ins and outs are not determined, and the current proposal presents the possibility of hundreds of items being added for some routes, or the possibility of meddling with standards that differ between wikis. Now, on the other hand, if WikiData adds the option for arrays, I can see this allowing us to add data for complete junction tables (mileage, locations, intersections and exit numbers... everything but notes) to a single item. - Floydian (talk) 20:15, 1 July 2014 (UTC)

Oppose for now. Basically per Floydian. T C N7JM 20:21, 1 July 2014 (UTC)

Oppose, would likely contain indiscriminate amounts of data. —Scott5114 ↗ [EXACT CHANGE ONLY] 20:27, 1 July 2014 (UTC)

Question, Rschen7754, was it really necessary to engage in canvassing? We are supposed to be a plural project that has to accommodate the wishes of several communities. If one community doesn't want to use certain data, nobody is forcing them to, they can just ignore it.--Micru (talk) 21:28, 1 July 2014 (UTC)

It was a neutral notification, because I was genuinely unsure if the solution would fit our needs. As the English Wikipedia has the most highway articles on Wikimedia, and the most organized road editor community, it made sense that their needs should be considered. Of course, you are welcome to ask for their thoughts as well. Remember, Wikidata is here to serve the needs of the projects, including the English Wikipedia. Also, keep in mind that two of the "canvassed" commenters are local admins here. --Rs chen 7754 23:03, 1 July 2014 (UTC)

Oppose at this time. The proposal needs to be refined significantly to be useful for Wikipedia articles. Imzadi 1979 → 01:54, 2 July 2014 (UTC)

Not done Probably can be solved with queries.--Micru (talk) 08:56, 18 October 2014 (UTC)

number of parking spaces

Not done

Description	number of parking spaces at this place
Data type	Number (not available yet)
Template parameter	"parking" in en:template:Infobox convention center (might not always be a number)
Domain	geographic location (Q2221906), building (Q41176), etc.
Example	ExCeL London (Q826480) => 3700
Source	articles, websites, etc.
Proposed by	Danrok (talk) 02:01, 13 July 2014 (UTC)

Discussion

If this "might not always be a number", then Number (not available yet) is the wrong datatype, isn't it? --Yair rand (talk) 02:28, 8 September 2014 (UTC)

Not done Lacking support.--Micru (talk) 08:57, 18 October 2014 (UTC)

Railway

Comment Does this relate to railway line in the sense of a portion of track within the network or does it mean a train service running on this portion? In german, "Eisenbahnstrecke" und "Eisenbahnlinie" are two different things. Ridership numbers, rolling stock and depot are typical info about a service, while electrification or gauge describe the track portion. There is no 1:1 relation between the two and it might be reasonable to treat them as a separate type of objects. --Rudolph Buch (talk) 10:56, 10 April 2013 (UTC)

infrastructure and service should be split. - Gonioul (talk) 16:10, 16 August 2013 (UTC)

Department or region of railway

Not done

Description	The railways in ex-USSR countries have some subdivisions (departmments or directions, in Russia replaced by regions) (Russian: отделение or регион, Ukrainian: дирекція or регіон). Each station is dependent to one of these subdivisions
Data type	Item
Template parameter	department or region
Domain	place
Example	Hrebinka (Q4148354) => Poltava Directorate of Railway Transportation (Q12141883), Babaevo (Q4074147) => Q4124182, Tarasivka (Q12160031) => Kyiv Directorate of Railway Transportation (Q12110167)
Source	Station references (for example [1])
Proposed by	Ahonc (talk)

Discussion: Comment - I think it is typical for every country to have railway districts that differ from other subdivisions. You could change the property so it works for every country. Would something like "is in railway district"? The railway districts can be sorted using "subclass of". --Tobias1984 (talk) 15:45, 28 July 2013 (UTC); Comment - I do not know about other countries, incl. Ukraine, but in Russia 99% of railways are administratively divided into 16 railway companies (e.g. en:Moscow Railway), which are subdivided into several departments or regions (e.g. ru:Московско-Курский регион Московской железной дороги). However, logistically railways form several "networks" (e.g. ru:Московский железнодорожный узел), which are subdivided into "directions", e.g. ru:Горьковское направление Московской железной дороги, parts of which may be administered by one department and parts by another, and these "directions" can possess several "branches" (e.g. ru:Железнодорожная ветка Кривандино — Рязановка). So the structure is no less complicated than with settlements, and I am at loss on how to name all this. YLSS (talk) 13:23, 11 November 2013 (UTC); Support, it is needed for infoboxes. — Ivan A. Krestinin (talk) 16:44, 11 November 2013 (UTC)

Ahonc, Tobias1984, YLSS, Ivan A. Krestinin: Recently we had approved the property applies to jurisdiction (P1001), I think it could be used for this case too. If there are no concerns about using p1001 for this, I will close this proposal.--Micru (talk) 18:34, 25 November 2013 (UTC)

applies to jurisdiction (P1001) is inverse. — Ivan A. Krestinin (talk) 19:30, 25 November 2013 (UTC)

Ivan A. Krestinin: True, what about "contains jurisdiction"?--Micru (talk) 19:36, 25 November 2013 (UTC)

I personally wouldn't mix different trees of subdivision. A typical place belongs to a political district, postal district, voting district, police district, military district. Of course all of these could be but into one property with a qualifier asking for the "type of jurisdiction" - But I'm not sure that is the current paradigm, also because of the inability to do constraint violations within qualifiers at the moment. --Tobias1984 (talk) 15:10, 27 November 2013 (UTC)

Not done Lacking support and probably too domain specific.--Micru (talk) 08:59, 18 October 2014 (UTC)

Strahler number

Done: maximum Strahler number (P1548) (Talk and documentation)

Description	See w:Strahler number. To summarize, a level 1 stream has no tributaries, a level 2 stream has only level 1 tributaries, a level 3 stream has level 2 tributaries, and so on. But in the example of the level 3 stream, it is only a level 3 stream above the confluence of two level two streams, which in turn, only apply to streams downstream of their first tributary. Hence the multiple values in the example bellow. coordinate location (P625) could possibly be used as a qualifier to indicate what parts of the stream have what Strahler number (an item won't work because the first tributary of any given stream is not always notable).
Data type	Number (not available yet)
Domain	streams
Allowed values	1 to 12
Example	West Branch Fishing Creek (Q15269492) --> 1 (from headwaters to Swanks Run), 2 (from Swanks Run to Painter Run), 3 (from Painter Run to mouth)
Proposed by	--Jakob (talk)

Discussion

Support. Seems useful! Jakob, please provide a proper description. Emw (talk) 13:43, 7 June 2014 (UTC)
Support --Micru (talk) 19:16, 23 June 2014 (UTC)
Oppose: It seems quite subjective, though maybe there's something I'm missing here. Based on a reading of Strahler number, the number appears to be relative to whatever data set a person is working on at the time. Having one coordinate for the first headwater only establishes where one of the order 1 streams is. Wouldn't one have to make subjective decisions about every ditch feeding into every tributary of the system to decide where whether each contributing tributary's mouth has a particular Strahler number when it joins? --Closeapple (talk) 14:37, 2 July 2014 (UTC)

@Closeapple: If I am not mistaken, the Strahler number only considers (officially) named tributaries, so that would solve that issue. --Jakob (talk) 14:41, 2 July 2014 (UTC)

@Jakec: Who would determine that though? For example, in the U.S., USGS GNIS is continuously added to, and that's handled by a different group that the one that maintains the National Hydrography Database; one state agency might have names for things that it has determined through research, while another does not. (I'm thinking of maybe a conservation agency vs. the transportation/highway department that puts signs up for river bridges.) The chances of the Strahler number from one source for one flow correctly meshing into a tributary's Strahler number from another source seems very low — it might even change with new editions of a source. It almost seems more stable if it were numbered backwards: Counting the tributary level upwards from the lowest mouth would lead to a more stable order number; but maybe that defeats whatever purpose people would use the Strahler number for. (What would someone use this number from Wikidata for, anyway?) --Closeapple (talk) 15:49, 2 July 2014 (UTC)

We could use multiple values and set ranks for them. If we also have multiple Strahler numbers, that might make things a bit messy though, so perhaps this property should refer to the highest Strahler number (i.e. the one at the mouth). --Jakob (talk) 15:29, 3 July 2014 (UTC)

Support. A bit fuzzy, but let's give it a try. --- Jura 22:19, 27 September 2014 (UTC)
Support Per Jura. --Eurodyne (talk) 04:22, 3 October 2014 (UTC)
@Micru, Closeapple, Jura1, Eurodyne: Done --Jakob (talk) 01:24, 7 October 2014 (UTC)

ICHTO

Not done

Description	Iranian Cultural Heritage, Handcrafts, Tourism Organization monument registration no
Data type	Number (not available yet)
Domain	geographic location (Q2221906)
Allowed values	1 - 100,000
Example	Persepolis (Q129072) => item 12751 note: all items with their registration numbers have already moved to fa.wikipedia, so we just need to copy numbers from fa.wiki to wiki data.
Source	http://iranshahrpedia.ir/fa/indexer
Robot and gadget jobs	Yes
Proposed by	Monfie (talk)

Discussion

(About 30,000 monuments are registered in Iran (here) and have a unique ID. All of them have articles in persian wikipedia.) Monfie (talk) 13:29, 22 September 2014 (UTC)

@مانفی : You should improve your exemple, I can't help you if I have not a proper link. --Fralambert (talk) 02:17, 24 September 2014 (UTC)

I did correct my example.Monfie (talk) 09:49, 24 September 2014 (UTC)

Excuse me for bad news. The property you are requesting for is already created Property:P1369. You can add a Persian label for that --دوستدار ایران بزرگ (talk) 17:00, 6 October 2014 (UTC)

Withdraw. I don't understand what is bad news!! If it is already exist it is good news that we can use it and the only problem was the creator did not add it to the list (I added now) so I proposed it again.Monfie (talk) 07:56, 8 October 2014 (UTC)
Not done Property already exists. Is there a list of properties at Wikidata:WikiProject Iranian Persian? -Tobias1984 (talk) 09:00, 8 October 2014 (UTC)

GeoNames ID

Done: GeoNames ID (P1566) (Talk and documentation)

Description	ID in http://www.geonames.org/
Data type	String
Domain	place
Allowed values	numbers
Example	Monte Boglia (Q870031)=>6285788
Format and edit filter validation	numbers
Source	GeoNames (Q830106)
Robot and gadget jobs	from dumps and [2] (also import P625)
Proposed by	GZWDer (talk)

Discussion

GZWDer (talk) 06:16, 5 October 2014 (UTC)

Support Per nom. Eurodyne (talk) 05:55, 18 October 2014 (UTC)
Support But the linked example doesn't work. --Micru (talk) 09:16, 18 October 2014 (UTC)
@GZWDer, Eurodyne, Micru: Done --Jakob (talk) 18:21, 18 October 2014 (UTC)

NIS/INS code

Done: NIS/INS code (P1567) (Talk and documentation)

Description	code used by the Belgium statistics institute
Data type	String
Template parameter	fr:Modèle:Infobox Commune de Belgique
Domain	blah
Allowed values	5 digit-string
Format and edit filter validation	5 digit-string
Source	http://statbel.fgov.be/fr/statistiques/collecte_donnees/nomenclatures/geo_admin/
Proposed by	Zolo (talk)

Discussion

See NIS code (Q614874)

Could not find the conventional English translation (if any).Zolo (talk) 07:28, 9 October 2014 (UTC)

Support Seem usefull. --Fralambert (talk) 21:11, 9 October 2014 (UTC)

Support --Micru (talk) 09:17, 18 October 2014 (UTC)

@Zolo, Fralambert, Micru: Done --Jakob (talk) 18:35, 18 October 2014 (UTC)

Yandex.Music ID

Done: Yandex Music artist ID (P1553) (Talk and documentation)

Description	Yandex Music (Q4537983) author or group ID
Data type	String
Template parameter	none
Domain	human (Q5), musical ensemble (Q2088357)
Allowed values	\d+
Example	Queen (Q15862) → 79215
Source	Template Template:Music yandex (Q10991674) from ru-wiki
Robot and gadget jobs	URL like Queen (Q15862) → 79215 → http://music.yandex.ru/#!/artist/79215
Proposed by	Vlsergey (talk)

Discussion

Author ID for legal free-to-listen music website, wildly used in ru-wiki. Vlsergey (talk) 14:45, 14 June 2014 (UTC)

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

Support --Eurodyne (talk) 00:13, 5 October 2014 (UTC)

@Vlsergey, Micru, Eurodyne: Done --Jakob (talk) 01:28, 7 October 2014 (UTC)

Wikispecies person page

Not done

Description	page on Wikispecies, about a person who is a taxonomic authority
Data type	Wikispecies article title-invalid datatype (not in Module:i18n/datatype)
Template parameter	n/a
Domain	Persons
Allowed values	Wikispecies article titles
Example	Joseph-Étienne Giraud (Q6280725) => wikispecies:Joseph-Étienne Giraud
Format and edit filter validation	(sample: 7 digit number can be validated with edit filter Special:AbuseFilter/17)
Source	Possibly Wikipedia taxoboxes?
Robot and gadget jobs	Could be done from taxoboxes, Wikipedia lists, reverse lookup from species names on Wikispecies.
Proposed by	Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits

Discussion

N.B. Not to be confused with taxon author (P405). Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 20:52, 4 September 2014 (UTC)

It would seem more logical to me to add a sitelink from the Wikidata item for the taxon author to the wikispecies page for the person. Regards, Dipsacus fullonum (talk) 23:09, 4 September 2014 (UTC)

Perhaps, but that's a separate issue. See below. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 12:46, 5 September 2014 (UTC)

Oppose. Sitelink to Wikispecies should be used. —Wylve (talk) 02:55, 5 September 2014 (UTC)

This is not going to happen for the foreseeable future. In the meantime, we can use an ordinary property, comparable with Commons category (P373), or with a link to non-Wikimedia database like VIAF ID (P214). Once sitelinks are available, then we can get a bot to swap them over. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 12:48, 5 September 2014 (UTC)

Support --- Jura 22:24, 27 September 2014 (UTC)
Oppose Per Wylve. --Eurodyne (talk) 04:19, 29 September 2014 (UTC)
- @Eurodyne: Please explain how a sitelink to Wikispecies can be used. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 12:35, 30 September 2014 (UTC)
  - @Pigsonthewing: Perhaps through the "Pages on other sites linked to this item" section on items. --Jakob (talk) 19:42, 2 October 2014 (UTC)
    - @Jakec: Please can you do that for the author given in the proposal, Joseph-Étienne Giraud, by way of example? It's not working for me. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 20:05, 2 October 2014 (UTC)
      - Sorry, I was mistaken. That function seems to only work for Wikidata. --Jakob (talk) 17:37, 4 October 2014 (UTC)

Not done To be solved by sitelinks.--Micru (talk) 10:26, 18 October 2014 (UTC)

country for sport

Done: country for sport (P1532) (Talk and documentation)

Description	country that person represents or have rights to represent on international sports events
Data type	Item
Template parameter	country
Domain	Person (sportsmen)
Allowed values	both countries and some additional items like England (Q21) and Chinese Taipei (Q216923)
Example	Janet Lee (Q455653) → Chinese Taipei (Q216923); Ad Wheeler (Q18015449) → England (Q21)
Source	Wikipedia infoboxes, also some incorrect values of country of citizenship (P27) shall be moved there ASAP
Robot and gadget jobs	incorrect values of country of citizenship (P27) shall be moved there ASAP
Proposed by	Vlsergey (talk)

Discussion

Country-alike parameter from sport infoboxes. Vlsergey (talk) 06:43, 16 September 2014 (UTC)

Wouldn't these need to be associated with particular instances of participation? If so, it would probably be a qualifier, in which case it could just as well use "country". OTOH, maybe not, as the represented area isn't always a country. --Yair rand (talk) 07:38, 16 September 2014 (UTC)

@Yair rand: When used for event entity it could be used as qualifier of person as well, but primary goal is person infoboxes. -- Vlsergey (talk) 08:06, 16 September 2014 (UTC)

Support. --putnik 11:57, 16 September 2014 (UTC)

Support. DonRumata (talk) 12:09, 16 September 2014 (UTC)

Support. It's all the same to me but I want a quick fix. Сидик из ПТУ (talk) 17:29, 16 September 2014 (UTC)

@Vlsergey, Yair rand, Putnik, DonRumata, Сидик из ПТУ: Done --Jakob (talk) 11:29, 25 September 2014 (UTC)

Family name identical to this first name

Done: family name identical to this given name (P1533) (Talk and documentation)

Description	The surname/family name spelled the same was as this given name/first name is:
Data type	Item
Domain	given names/first names
Allowed values	items for surnames
Example	Sylvain (Q16281827) (given name): Sylvain (Q18001608) (family name)

Provides a simple way to link the two items together. --- Jura 18:27, 18 September 2014 (UTC)

Support--- Jura 08:20, 21 September 2014 (UTC)
Support--Harmonia Amanda (talk) 19:02, 20 September 2014 (UTC)
Support Michiel1972 (talk) 09:42, 22 September 2014 (UTC)
@Jura1, Harmonia Amanda, Michiel1972: Done --Jakob (talk) 11:32, 25 September 2014 (UTC)

monogram

Done: monogram (P1543) (Talk and documentation)

Description	image of a person's monogram
Data type	Commons media file
Template parameter	ru:Шаблон:Государственный деятель → монограмма
Domain	human (Q5)
Allowed values	images
Example	Ivan VI of Russia (Q151781) → File:John III Russia Monogram.gif, Elizabeth I of Russia (Q130752) → File:Imperial Monogram of Empress Elizabeth I of Russia.svg
Proposed by	--putnik

Discussion

Like signature (P109) for monograms. Some people have only a signature or monogram, but some have both. --putnik 12:36, 19 September 2014 (UTC)

Support --- Jura 22:22, 27 September 2014 (UTC)
Support --Eurodyne (talk) 22:59, 27 September 2014 (UTC)
@Putnik, Jura1, Eurodyne: Done --Jakob (talk) 23:43, 27 September 2014 (UTC)

name in native language

Done: name in native language (P1559) (Talk and documentation)

Description	person current name in the native person language
Data type	Monolingual text
Template parameter	wildly used in all person infoboxes in ruwiki
Domain	Persons
Allowed values	—
Example	Barack Obama (Q76) → (en) "Barack Hussein Obama II"
Source	infoboxes
Robot and gadget jobs	need constrain that only native native language (P103) or spoken languages languages spoken, written or signed (P1412) are allowed
Proposed by	Vlsergey (talk)

Discussion

The last common parameter from ruwiki infoboxes. Vlsergey (talk) 14:38, 28 September 2014 (UTC)

Comment If we want this property, it should be more generic. E. g. for books we need the name in original language too. --putnik 16:01, 28 September 2014 (UTC)

@putnik: book already have P357 (P357). You can get it from entity or from original using edition or translation of (P629) for translations. -- Vlsergey (talk) 16:15, 28 September 2014 (UTC)

@Vlsergey: Ok, books have P357 (P357). But what about cities and other geographic features? --putnik 16:38, 28 September 2014 (UTC)

Well, may be it's shall be applicable to them as well. But it's hard to decide what language shall we calling "native" for cities, for example for Jerusalem (Q1218). -- Vlsergey (talk) 16:42, 28 September 2014 (UTC)

For places (specifically GLAM instutitions for {{Institution/wrapper}}) I have been told to use the official name (P1448) property, which was quite recently created. Jheald (talk) 07:06, 29 September 2014 (UTC)

Ok. If all other entities already have a property for the native language name, then

Support. --putnik 20:29, 29 September 2014 (UTC)

Strong support - the only way to store it safely…, and it is absolutely necessary each time the person's name is used in a language that does not use the same writing (not only Russian, all of them) :) --Hsarrazin (talk) 18:27, 9 October 2014 (UTC)

@Vlsergey, Jheald, Putnik, Hsarrazin: Done --Jakob (talk) 21:48, 11 October 2014 (UTC)
@Vlsergey, Putnik: Please emphasize the difference between this property and birth name (P1477). --Infovarius (talk) 21:40, 16 November 2014 (UTC)

given name version for other gender

Done: given name version for other gender (P1560) (Talk and documentation)

Description	female version of a male given name, male version of a female given name. Add primarily the closest matching one.
Data type	Item
Domain	given names
Allowed values	given names for other gender
Example	Riccardo (Q15720880) given name version for other gender Riccarda (Q18000607)

Discussion

Allows cross-referencing them. --- Jura 18:48, 2 October 2014 (UTC)

Support even though this wouldn't be used on an item about a person. --AmaryllisGardener ^talk 18:58, 2 October 2014 (UTC)
~~Weak oppose~~ Neutral personal and family names currently is a mess due to complicated translation problems, it will just increase it along with original research (because any given sources will be about single language item, not multilanguage "entity" introduced by Wikidata) -- Vlsergey (talk) 22:44, 2 October 2014 (UTC)
- @Vlsergey:: WD:WikiProject Names is working on cleaning up that mess. If you look at a few of the most frequent given names, you will notice that the items are in much better shape than they were just 2 or 3 months ago.
  To evaluate this property proposal, I think one should check how it could work on the sample item, not any random item that hasn't been cleaned up yet. --- Jura 04:13, 3 October 2014 (UTC)
  - @Jura1: So, would you mind to provide the source for given example? Also, considering given example, are you sure that Riccardo (Q15720880) is a real first name of Richard I of England (Q42305)? -- Vlsergey (talk) 04:21, 3 October 2014 (UTC)
    - @Vlsergey: For the sample item, please see it:Riccardo#Varianti "Femminili".
      The second question isn't directly related to the sample items/this proposal, but the point is explained at WD:WikiProject Names. The item you mention should also have Richard (Q1249148) in P735. --- Jura 04:31, 3 October 2014 (UTC)
      - @Jura1: thank you for the source, it seems that it is really possible to create reliable names ontology. Sadly, current status of such ontology and links to Q-items is not in good shape. I just checked the first name in the list (John (Q4925477)) and found John Paul II (Q989) as it's holder. Well... I can only hope someone would not only introduce those properties but will be able to track them and add appropriate sources and clean the existed mess. Somehow. No idea how to do it now, considering requirement to preserve interwiki. Good luck to you. -- Vlsergey (talk</spamaran>) 05:18, 3 October 2014 (UTC)
        Yes, there is indeed much to do and it will take some time. BTW, would you reconsider your initial vote? --- Jura 07:33, 4 October 2014 (UTC)

Support : much better than considering male and female version as the same item, when they are objectively written differently - obviously, this is only needed in languages where the names have different endings according to gender ;) --Hsarrazin (talk) 18:07, 5 October 2014 (UTC)

@Vlsergey, Jura1, AmaryllisGardener, Hsarrazin: Done --Jakob (talk) 21:51, 11 October 2014 (UTC)

mass

Not done

Description	description how heavy an vehicle is
Data type	Number (not available yet)
Template parameter	put Wikipedia infobox parameters here, if existing; ex: "population" in en:template:infobox settlement
Domain	aircraft (Q11436) (aircraft), BMW F 800 (Q796496)(MotorcycleModel), motorcycle (Q34493)(Motorcycle), motor car (Q1420) (automobile)
Allowed values	pounds or kg
Example	the motorcycle has a mass of 200kg
Format and edit filter validation	(sample: 7 digit number can be validated with edit filter Special:AbuseFilter/17)
Source	http://en.wikipedia.org/wiki/Template:Infobox_fictional_vehicle
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	194.121.90.163

Discussion

Every vehicle has a mass therefore we should have a matching property. Also the themplate has a mass property http://en.wikipedia.org/wiki/Template:Infobox_fictional_vehicle 194.121.90.163 13:43, 1 July 2014 (UTC)

Mass is a generic property, not specific to transport. Shouldn't this be discussed more widely? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 14:06, 1 July 2014 (UTC)
- is there a category for physical units like mass, torque etc? --194.121.90.163 12:38, 16 July 2014 (UTC)
  - Try Wikidata:Property proposal/Unsorted. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 20:12, 16 July 2014 (UTC)

duplicate of the already approved but pending property Wikidata:Property_proposal/Pending/2#Mass_2 --Pasleim (talk) 20:27, 24 September 2014 (UTC)

Aircraft / Flugzeug / Avion

See: en:Template:Infobox aircraft

Comment I think we should replace all of these with the 'technical specification' property (see at the end of the page) with 'dimension' qualifier. Filceolaire (talk) 17:18, 21 September 2013 (UTC)

Oppose Unique properties are best for many of these because it will make both entry and access of data easier and work better with qualifiers. More detail added to the discussion below. Joshbaumgartner (talk) 06:03, 7 October 2013 (UTC)

Aspect ratio / Flügelstreckung / Allongement

Not done

Description	An indicator of long wings.
Data type	Number (not available yet)
Example 1	MISSING
Example 2	MISSING
Example 3	MISSING

Support but lets make the description an actual description of aspect ratio (a very specific measurement). Joshbaumgartner (talk) 06:03, 7 October 2013 (UTC)
@Joshbaumgartner: Can you add an example that only has one number. I can't assess which ratio makes more sense. --Tobias1984 (talk) 20:40, 5 February 2014 (UTC)

Capacity (ballast) / Wasserballast / Ballast

Not done

Description	Authorised amount of water ballast.
Data type	Number (not available yet)
Example 1	MISSING
Example 2	MISSING
Example 3	MISSING

Planeload / Flächenbelastung / Charge alaire

Not done

Description	The requirement for lift from the main plane.
Data type	Number (not available yet)
Example 1	MISSING
Example 2	MISSING
Example 3	MISSING

Comment - Force will be a generic property. A qualifier might be more appropriate. --Tobias1984 (talk) 14:01, 16 May 2013 (UTC)

Rate of sink (minimum) / geringstes Sinken / Taux de chute minimale

Not done

Description	How fast will the glider go towards the ground in calm air.
Data type	Number - default m/s.-invalid datatype (not in Module:i18n/datatype)
Example 1	MISSING
Example 2	MISSING
Example 3	MISSING

Comment - Can't this be calculated from the glide ratio? --Tobias1984 (talk) 14:01, 16 May 2013 (UTC)

Answer - no. Minimal sink occurs at a lower speed than best glide, but how much lower depends on how flat the polar of the aircraft in question is. See also en:Polar curve. Poul G (talk) 10:13, 10 August 2013 (UTC)

displacement (en) (engine displacement (Q466511)) / cilindrata (it) / 배기량 (ko)

Not done

Description	displacement of the car's engine
Data type	Number (not available yet)
Template parameter	w:en:Template:pistonspecs : displacement
Domain	term (car engine)
Example	Opel C20LET (Q3338601) --- ( displacement ) ---> 1998 cubic centimetre (Q1022113)
Source	we could read "displacement " from en:Template:Infobox automobile engine
Robot and gadget jobs	we could read "displacement " from en:Template:Infobox automobile engine
Proposed by	LucaBiondi (talk) 21:12, 3 September 2013 (UTC)

Discussion: Support common and useful data point for engines. Joshbaumgartner (talk) 07:02, 2 October 2013 (UTC); Support--Konggaru (talk) 09:20, 28 January 2014 (UTC)

cylinder bore (en) (bore (Q245657)) / alesaggio (it)

Not done

Description	cylinder bore of the car's engine
Data type	Number (not available yet)
Template parameter	w:en:Template:pistonspecs : bore
Domain	term (car engine)
Example	Opel X25XE (Q8041641) --- ( cylinder bore ) ---> 81.6 millimetre (Q174789)
Source	we could read "cylinder bore" from en:Template:Infobox automobile engine
Robot and gadget jobs	we could read "cylinder bore" from en:Template:Infobox automobile engine
Proposed by	LucaBiondi (talk) 21:24, 3 September 2013 (UTC)

Discussion: Support common defined data point for engines. Joshbaumgartner (talk) 07:02, 2 October 2013 (UTC)

piston stroke (en) (stroke (Q671554)) / corsa (it)

Not done

Description	piston stroke of the car's engine
Data type	Number (not available yet)
Template parameter	w:en:Template:pistonspecs : stroke
Domain	term (car engine)
Example	Opel X25XE (Q8041641) --- ( piston stroke ) ---> 79.6 millimetre (Q174789)
Source	we could read "piston stroke" from en:Template:Infobox automobile engine
Robot and gadget jobs	we could read "piston stroke" from en:Template:Infobox automobile engine
Proposed by	LucaBiondi (talk) 21:34, 3 September 2013 (UTC)

Discussion

Better propose a similar property like the significant event (P793) property but for elements of an intem with a qualifier "dimension".

Ex.:

Opel X25XE (Q8041641) (item)

Element (property): stroke (Q671554) (property value)

Dimension (qualifier): 79.6 (qualifier value)

Element (property): engine configuration (Q2576663) (property value)

Dimension (qualifier): XX (qualifier value)

Element (property): bore (Q245657) (property value)

Dimension (qualifier): 81.6 (qualifier value)

Snipre (talk) 18:28, 5 September 2013 (UTC)

Hi Snipre, i agree with you! Below i write my new proposal. Tell me what do you think and if it's clear.LucaBiondi (talk) 21:23, 5 September 2013 (UTC)

Support I find distinct properties much easier to use, they allow for more use of qualifiers, and will be easier for article writers to access the data in future phases of the project. Joshbaumgartner (talk) 07:02, 2 October 2013 (UTC)

technical specifications (en) / caratteristiche tecniche (it)

Not done

Description	property for elements of an item with a qualifier "dimension". Should be similar to significant event (P793)
Data type	Item
Domain	term
Example	see example below
Proposed by	LucaBiondi (talk) 21:23, 5 September 2013 (UTC)

Example:

Opel X25XE (Q8041641) (item)

technical specification (property): engine configuration (Q2576663) (property value)

instance of (P31) (qualifier): V6 (Q10856569) (qualifier value type item)

technical specification (property): stroke (Q671554) (property value)

Dimension (qualifier): 79.6 mm (qualifier value type number+dimension)

technical specification (property): bore (Q245657) (property value)

Dimension (qualifier): 81.6 mm (qualifier value type number with dimension)

Discussion

I've rewritten your example because I found the previous version a bit confusing. Please revert if I misunderstood something.

The 'Dimension' qualifier needs a separate property proposal from that for 'technical specification' so I've added that below. Filceolaire (talk) 13:38, 21 September 2013 (UTC)

Support as rewritten. Filceolaire (talk) 13:38, 21 September 2013 (UTC)

Support Thanks Filceolaire for rewrite my example, I agree with youLucaBiondi (talk) 21:12, 21 September 2013 (UTC)

Comment this one we need to solve, but there are some issues. Some specific products on wikipedia have their own dedicated article. Other products share an article with variant products, so more than one set of specifications appears in the article. I've looked at vehicles before, and it seems like a big headache because the the Wikipedia articles are in a form which doesn't match the structure of automotive design. The articles are a closer match to automotive marketing, i.e. based more on branding, than tech specs. --Danrok (talk) 01:02, 28 September 2013 (UTC)

Oppose I don't think it is wise to make the database more vertical like this. Since, at least currently, we cannot add qualifiers to qualifiers, I think it is better to have each specification as its own property, leaving us free to add qualifiers to the value. For example:

R-3350 Duplex-Cyclone (Q786848) (item) : power output (property) : 2200 HP (value) : engine speed (qualifier) : 2800 RPM (qualifier value)

but if we bury it a level deeper per this proposal, we lose that option:

R-3350 Duplex-Cyclone (Q786848) (item) : technical specification (property) : power output (value) : measurement (qualifier) : 2200 HP (qualifier value) : engine speed (qualifier) : 2800 RPM (qualifier value)

obviously the engine speed qualifier has to be dropped because we can't nest qualifiers. Joshbaumgartner (talk) 07:02, 2 October 2013 (UTC)

I presume you want to specify that the power output quoted was measured at that rpm. You don't need to nest the qualifiers for this - you just have two qualifiers.

Where you have two values for output power measured at two different speeds you still don't need to nest qualifiers. You just have to have power output value twice, each with it's own qualifiers. Filceolaire (talk) 21:20, 6 November 2013 (UTC)

dimension (en) / dimensioni (it)/

Not done

Description	qualifier for 'technical specification' (see above)
Data type	number (units=length)-invalid datatype (not in Module:i18n/datatype)
Domain	claims using the 'technical specification' property
Allowed values	positive numbers
Example	see example above
Proposed by	Filceolaire (talk) 13:38, 21 September 2013 (UTC)

Discussion: Support as proposer Filceolaire (talk) 13:38, 21 September 2013 (UTC); Support as proposed by FilceolaireLucaBiondi (talk) 21:12, 21 September 2013 (UTC); Support but not merely as a qualifier for technical specification, but as a broadly useable qualifier for a great many properties. It should probably not be limited to positive numbers either. In fact there may be a generic property proposal of the same title already. Joshbaumgartner (talk) 07:02, 2 October 2013 (UTC); Oppose "Dimension" is too generic. Instead it would be better to have a "heigth", "width" and "depth".--Micru (talk) 20:29, 24 November 2013 (UTC)

combustors

Not done

Description	description of combustors
Data type	String
Template parameter	w:en:Template:jetspecs : combustion
Domain	jet engines
Example	Westinghouse J30 (Q7988946) => combustors => annular stainless steel
Robot and gadget jobs	importation from articles using template 'jetspecs'
Proposed by	Joshbaumgartner (talk) 02:07, 3 October 2013 (UTC)

Support Per 'jetspecs' infobox. Joshbaumgartner (talk) 02:07, 3 October 2013 (UTC)

Comment As per Danrok's comments on 'turbine' below, this may be better as an item data type. Joshbaumgartner (talk) 00:50, 27 October 2013 (UTC)

Comment I would create an item for annular combustor. You can always give that item the statement "made from = stainless steel". I don't anything about the topic, but I'm speculating that the material itself is not unusual. Otherwise you would need a few items like "annular ceramic combustor", or use qualifiers to highlight special alloys of specific turbines. --Tobias1984 (talk) 14:24, 25 November 2013 (UTC)

turbine

Not done

Description	description of turbine
Data type	String
Template parameter	w:en:Template:jetspecs : turbine
Domain	jet engines
Example	Westinghouse J30 (Q7988946) => turbine => single-stage axial
Robot and gadget jobs	importation from articles using template 'jetspecs'
Proposed by	Joshbaumgartner (talk) 02:07, 3 October 2013 (UTC)

Support Per 'jetspecs' infobox. Joshbaumgartner (talk) 02:07, 3 October 2013 (UTC)

Comment might it be better if this was an item data type? We could then create items such as single-stage axial, that would help standardize the text, and allow for different languages. --Danrok (talk) 13:45, 22 October 2013 (UTC)

Comment I would be fine with that. We can see if anyone has ideas on it, but I'm fine with it either way. Joshbaumgartner (talk) 00:48, 27 October 2013 (UTC)

Comment Should be item datatype. But we also already have powered by (P516). Am I misreading the example? --Tobias1984 (talk) 14:10, 25 November 2013 (UTC)

overall pressure ratio

Not done

Description	overall pressure ratio of the engine
Data type	String
Template parameter	w:en:Template:jetspecs : compression
Domain	jet engines
Example	Westinghouse J30 (Q7988946) => overall pressure ratio => 3:1
Robot and gadget jobs	importation from articles using template 'jetspecs'
Proposed by	Joshbaumgartner (talk) 02:07, 3 October 2013 (UTC)

Support Per 'jetspecs' infobox. Joshbaumgartner (talk) 02:07, 3 October 2013 (UTC)

Comment Again I would prefer the ratios expressed as a single number in relation to one. --Tobias1984 (talk) 14:20, 25 November 2013 (UTC)

+1 with Tobias1984 Snipre (talk) 20:01, 8 January 2014 (UTC)

Première date

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

Description	The date of first performance of a creative work
Data type	Point in time
Template parameter	various; for example `\|performed=` in en:Infobox musical composition
Domain	Musical compositions, plays, films
Allowed values	dates
Example	Rondo in C minor (Q18121432) => 1984
Source	various
Robot and gadget jobs	Likely
Proposed by	Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits

Discussion

We have publication date (P577), but the première of a work may be months ahead of its commercial release. We have start time (P580), but a work may be written or made months before its première. The Rondo given as an example above was written in 1865, first performed (premièred) in 1984 (over 100 years later), and first published in 1985. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 09:54, 24 September 2014 (UTC)

Support For broadcasting addition to original broadcaster (P449). --Kolja21 (talk) 01:14, 25 September 2014 (UTC)

Support --Micru (talk) 09:45, 18 October 2014 (UTC)

Support --Mike Linksvayer (talk) 19:52, 18 October 2014 (UTC)

Done @Pigsonthewing, Kolja21, Mike Linksvayer: --Micru (talk) 16:23, 21 October 2014 (UTC)

Note: Deleted. Dub of date of first performance (P1191). --Kolja21 (talk) 22:53, 21 October 2014 (UTC)

RISS catalog

Done: RISS catalog (P1575) (Talk and documentation)

Description	Union catalog of South Korea and Japan, maintained by RISS (Q12622641)
Data type	String
Domain	version, edition or translation (Q3331189)
Allowed values	M + numbers
Example	Unkenrufe (1st German edition) (Q18325681) => M9738793
Source	http://www.riss4u.net/
Robot and gadget jobs	add http://www.riss.kr/link?id=$
Proposed by	Kolja21 (talk)

Discussion

We have no Korean library catalog yet. This union catalog contains books we won't find anywhere else. (Please replace the above example if you know a useful work from Korean or Japan.) Kolja21 (talk) 07:02, 19 October 2014 (UTC)

Support --Micru (talk) 16:54, 21 October 2014 (UTC)

Support -Tobias1984 (talk) 16:57, 21 October 2014 (UTC)

Done @Tobias1984, Kolja21: --Micru (talk) 17:06, 21 October 2014 (UTC)

Gregory–Aland–Number (GA-Number)

Done: Gregory-Aland-Number (P1577) (Talk and documentation)

Description	Identifier according to Caspar René Gregory (Q215644) and Kurt Aland (Q61806) issued by Institute for New Testament Textual Research (Q477451) and widely used to identify Greek manuskripts of the New Testament. First introduced in 1908 by Gregory in Die griechischen Handschriften des Neuen Testaments (Q1218457)
Data type	String
Domain	only needed for items of Greek manuskripts of the New Testament.
Allowed values	there are four different kinds of IDs. 1. Papyrus numbers: P1 up to P128 today. The numbers will be limited to numbers below P150 in reasonable time. 2. Uncial numbers: go from 01 to 0323. The first zero must be maintained. The numbers will be limited to numbers below 0400 in reasonable time. 3. Minuscle numbers: go from 1 to 2247, the numbers will be limited to numbers below 3000 in reasonable time. 4. Lectionary numbers: lectionary numbers have an "L" in first place and go from l1 (not 11!) to l2279 (not 12279). The numbers will be limited to numbers below l3000 within reasonable time. There are meanwhile also numbers for coptic manuscripts, there are however no simple rules for these IDs and they seem to be incomplete, so it is reasonable to refrain from using this property for items of Coptic New Testament manuscripts.
Example	Rylands Library Papyrus P52 (Q1165472), GA-Number: P52
Format and edit filter validation	ID´s are never longer than five characters, the limitation in numbers are shown above. Unique value. Two items with the same values are either errors or duplicates.
Source	Page of the Institut für Neutestamentliche Textforschung Münster, list of New Testament papyri (Q1417837) list of New Testament uncials (Q1419177) list of New Testament minuscules (Q1809193) list of New Testament lectionaries (Q643705)
Robot and gadget jobs	Items must have instance of (P31) + manuscript (Q87167) and language of work or name (P407)+ Greek (Q9129) or Ancient Greek (Q35497). Usualy the item must have the allready proposed but yet not created property "is a copy of" + New Testament (Q18813), or items of any part of the New Testament. Lectionaries must have instance of (P31) + lectionary (Q284465) and ID must start with "l".
Proposed by	Giftzwerg 88 (talk)

Discussion

GA-Numbers are very common for New Testament manuskripts. The number provides access to the Institut für Neutestamentliche Textforschung Münster database which is the most important source for all data concerning the manuscripts, provides photos or scans and transcriptions of the greek texts. The GA number is enough to source all statements of an item you can think of. There are many articles named after the GA Number as Papyrus 66 (Q666654), Uncial 070 (Q695524), Minuscule 69 (Q1128804), Lectionary 1681 (Q1816555) and so on. Giftzwerg 88 (talk) 17:03, 28 September 2014 (UTC)

@Giftzwerg 88: Why not to use catalog code (P528) with qualifier catalog (P972)?--Micru (talk) 09:57, 18 October 2014 (UTC)

GA-Numbers are used since 1908. Gregory´s proposals were given to more than 100 famous scolars all around the globe and allmost all of them agreed and cherished this system of numbering of manuskripts.Have a look on this publications (German). The whole world uses this numbers since Gregory´s book. GA numbers then were used in all critical editions of the Greek New Testament. The first editions of Novum Testamentum Gce (Q746704) used an different numbering, but changed to GA Numbers very soon, and made them poular in all publications. This numbers are older than Kurt Aland (Q61806) who as able to identifiy different fragmants with different GA- numbers that belonged to one manuskript, so he reformed and enhanced the list of Gregory with new numbers for some more manuskripts Gregory did not know about. At last Aland founded the Instituft für Neutestamentliche Forschung and handed over the authority of numbering of new Manuscripts to the institute. But this numbers are some 50 years older than INTF and the cataloge of the INTF.--Giftzwerg 88 (talk) 12:41, 18 October 2014 (UTC)

I need this number badly for infoboxes used in articles concerning New Testament manuskripts. I just cant use wikidata items to fill the infobox, because there are no GA-Numbers to fill in, so the manuscript is nameless. The infobox is multilingual in its contents and can be used in every language, it is just the header that may be needed to translate. You can find this box for example in this articles https://de.wikipedia.org/wiki/Papyrus_66 https://en.wikipedia.org/wiki/Papyrus_66 https://id.wikipedia.org/wiki/Papirus_66 https://pl.wikipedia.org/wiki/Papirus_Bodmer_II, the box is allmost the same in all languages and all of them contain the GA-Number P66 in the header or elsewhere in the box. --Giftzwerg 88 (talk) 20:13, 18 October 2014 (UTC)

Whats the issue with this proposal? Please put a vote or ask your questions or give comments to this proposal.--Giftzwerg 88 (talk) 14:01, 23 October 2014 (UTC)

Support These IDs appear to we widely used, and, if I understand correctly, new IDs can be attributed, even when no new edition of Die griechischen Handschriften des Neuen Testaments (Q1218457). So it seems akin to other "authority controls" and a dedicated property seems like the simplest solution. --Zolo (talk) 16:22, 23 October 2014 (UTC)

Comment Why monolingual text for an identifier? Usually we use string-datatype for that. -Tobias1984 (talk) 07:14, 24 October 2014 (UTC)

You are right. Identifiers don´t have a language. I just thougt about identifiers are the same in any language. Changed to datatype string. Thank you for your valued comment.--Giftzwerg 88 (talk) 07:41, 24 October 2014 (UTC)

Support Looks good now. -Tobias1984 (talk) 09:36, 24 October 2014 (UTC)

Done -Tobias1984 (talk) 09:41, 24 October 2014 (UTC)

Beilstein Registry Number

Done: Reaxys registry number (P1579) (Talk and documentation)

Description	A Beilstein Registry Number unique identifier for organic chemical compounds in the Beilstein database.
Data type	~~number~~ string-invalid datatype (not in Module:i18n/datatype)
Template parameter	`\|Beilstein=` in en:Template:Chembox
Domain	Chemical compounds
Allowed values	positive integers, expressed as strings
Example	acetone (Q49546) => 635680
Format and edit filter validation	tbc
Source	Beilstein database
Robot and gadget jobs	Bot could import
Proposed by	Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits

Discussion

- Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 12:29, 17 October 2014 (UTC)

Support Snipre (talk) 16:18, 17 October 2014 (UTC)
Support Kopiersperre (talk) 20:54, 20 October 2014 (UTC)
Comment I think string-datatype would be more appropriate. -Tobias1984 (talk) 11:07, 26 October 2014 (UTC)
Done -Tobias1984 (talk) 16:53, 26 October 2014 (UTC)

Gmelin Number

Done: Gmelin number (P1578) (Talk and documentation)

Description	A Gmelin database number unique identifier for inorganic chemical compounds.
Data type	~~number~~ string-invalid datatype (not in Module:i18n/datatype)
Template parameter	`\|Gmelin=` in en:Template:Chembox
Domain	Chemical compounds
Allowed values	positive integers, expressed as strings
Example	acetone (Q49546) => 1466
Format and edit filter validation	tbc
Source	Gmelin database
Robot and gadget jobs	Bot could import
Proposed by	Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits

Discussion

- Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 12:29, 17 October 2014 (UTC)

Support Snipre (talk) 16:17, 17 October 2014 (UTC)
Support Eurodyne (talk) 17:42, 19 October 2014 (UTC)
Comment We are probably not doing any calculations with these numbers, so datatype string would be more appropriate. -Tobias1984 (talk) 22:21, 24 October 2014 (UTC)
- Why would we do that, when the validation is "positive integers"? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 12:39, 25 October 2014 (UTC)
  - A string can consist of 0 to 9 and we can easily check for that. Using integer numbers will mean that they will be converted for languages that use different numbers. -Tobias1984 (talk) 18:35, 25 October 2014 (UTC)
    - OK, happy with that explanation. Thank you. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 16:23, 26 October 2014 (UTC)
Support -Tobias1984 (talk) 16:30, 26 October 2014 (UTC)
Done -Tobias1984 (talk) 16:53, 26 October 2014 (UTC)

Number of edges

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

Description	Number of edges
Data type	Quantity
Domain	maths
Allowed values	blah
Proposed by	Zolo (talk)

Discussion

I was propmpted to propose this by fr:Modèle:Infobox Solide de Johnson. I do not feel knowledgeable enough to have an opinion about whether it makes sense to use the same property for number of edges in a geometric figures and number of edges in a graph (@TomT0m: ?). --Zolo (talk) 18:08, 5 October 2014 (UTC)

Support -Tobias1984 (talk) 17:16, 6 October 2014 (UTC)

Support --Eurodyne (talk) 00:48, 10 October 2014 (UTC)

@Zolo, Tobias1984, Eurodyne: Done --Jakob (talk) 18:44, 18 October 2014 (UTC)

Number of vertices

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

Description	Number of vertices
Data type	Quantity
Domain	maths
Allowed values	blah
Proposed by	Zolo (talk)

Discussion

Notified participants of WikiProject Mathematics

@Zolo: and

Support I made a ping-template for WikiProject Mathematics now. -Tobias1984 (talk) 17:14, 6 October 2014 (UTC)

Support --opensofias (talk) 17:28, 6 October 2014 (UTC)

@Zolo, Tobias1984, Opensofias: Done --Jakob (talk) 18:49, 18 October 2014 (UTC)

University of Barcelona authority ID

Done: University of Barcelona authority ID (former scheme) (P1580) (Talk and documentation)

Description	ID in the University of Barcelona authority catalogue
Data type	String
Domain	Persons
Allowed values	"a" followed by numbers
Example	Pieter van der Aa (Q533876) => a1160658
Source	external database
Proposed by	--Micru (talk) 18:15, 21 October 2014 (UTC)

Discussion

Needed for cawiki.--Micru (talk) 18:15, 21 October 2014 (UTC)

Support Tobias1984 (talk) 18:50, 21 October 2014 (UTC)

Comment 1) For caWP we have CANTIC ID (former scheme) (P1273): Pieter van der Aa (Q533876) => a10640745. Both catalogues are located in Barcelona. Do you have more information? (Do they work together? Is one catalogue more important than the other?) 2) The title "Autoritats UB ID" is ambiguous, since "UB" (Universitätsbibliothek) also stands for "university library". --Kolja21 (talk) 23:11, 21 October 2014 (UTC)

@Kolja21: I forwarded your question and the answer was: the Universitat of Barcelona participates in CANTIC, and the IDs are the same whenever the registers match. The problem is that Càntic has a narrower scope, so there are items in UB that do not have an ID in Cantic. The numbers are:

173265 total number of author registers at UB
62200 matching registers with Càntic
111065 only at UB and not on Càntic

I am told that it is possible to import only those that are not available at Càntic, and they have information about some people that is not available in other authority catalogues (like for this person).

I changed the label so it is not confused with Universitätsbibliothek.--Micru (talk) 11:23, 23 October 2014 (UTC)

Support Thanks for the background info! --Kolja21 (talk) 19:52, 23 October 2014 (UTC)

Support--KRLS (talk) 18:36, 24 October 2014 (UTC)

Support -- SERutherford (talk) 05:11, 26 October 2014 (UTC)

Support Mushroom (talk) 11:53, 26 October 2014 (UTC)

Support Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 16:21, 26 October 2014 (UTC)

Done -Tobias1984 (talk) 17:13, 26 October 2014 (UTC)

lifestyle

Done: lifestyle (P1576) (Talk and documentation)

Description	typical way of life of an individual, group, or culture
Data type	Item
Domain	all topics specially people's Item
Allowed values	Item
Example	Sadegh Hedayat (Q315017) => vegetarianism (Q83364), Alexandra David-Néel (Q230456) => mysticism (Q45996)
Proposed by	Yamaha5 (talk)

Discussion

We need this property for topics which people Identified as by community or them-self Yamaha5 (talk) 13:30, 8 October 2014 (UTC)

@Yamaha5: the topic of "identity" is complex, changed to lifestyle (Q32090) which might be more clear and

Support.--Micru (talk) 22:29, 20 October 2014 (UTC)

Thanks :) Yamaha5 (talk) 22:33, 20 October 2014 (UTC)

Done Property:P1576 −ebraminio^talk 20:07, 22 October 2014 (UTC)

outcome

Not done

Description	resulting outcome of an event, a process, or an action
Data type	Item
Template parameter	"result" in en:template:Infobox military conflict
Domain	event (Q1656682) (event)
Allowed values	Q items such as resulting event, article which describes a treaty, and so on, as per sources.
Example	Long War (Q690361) => Peace of Zsitvatorok (Q695212)
Source	infobox and article text
Robot and gadget jobs	Some can be done by bots, extracting from infoboxes
Proposed by	Danrok (talk) 17:36, 22 June 2014 (UTC)

Discussion

Support Name and description changed to use it in more fields.--Micru (talk) 11:34, 17 August 2014 (UTC)
Comment: Danrok, Micru, I think this property would be redundant with the generic property has effect (P1542). Help:Modeling causes has background. Emw (talk) 13:53, 28 September 2014 (UTC)

OK, seems to be the same thing. Danrok (talk) 14:20, 28 September 2014 (UTC)

@Emw: I agree, this property was proposed before p1542 was created, but now it is redundant.--Micru (talk) 19:54, 28 September 2014 (UTC)

Not done --Micru (talk) 19:54, 28 September 2014 (UTC)

number of survivors

Done: number of survivors (P1561) (Talk and documentation)

Description	number of people surviving an incident. Paralell to number of deaths (P1120)
Data type	Number (not available yet)
Domain	aviation accident (Q744913) and other incidents, etc.
Allowed values	whole numbers
Example	Essing bridge accident (Q10489191) => 1
Source	external reference, articles, etc.
Proposed by	ℇsquilo

Support If we have number of deaths, I think this property could be useful... --Eurodyne (talk) 21:44, 27 September 2014 (UTC)
Support. Clearly useful. Emw (talk) 13:54, 28 September 2014 (UTC)
Support Needed because sometimes this is the only known figure, e.g. boat full of an unknown number of people sinks, only the survivors can be reliably counted. Danrok (talk) 14:23, 28 September 2014 (UTC)
@Esquilo, Emw, Danrok: Done --Jakob (talk) 21:55, 11 October 2014 (UTC)

election map

Not done

Description	Map file of the result of the election
Data type	Commons media file
Template parameter	English Template:Infobox election map_image Français Modèle:Infobox Élection générale carte Español Plantilla:Ficha de elección mapa
Domain	Existing file
Allowed values	map (Q4006) with French legislative constituency (Q2973941) that show the result of an election, the election process, ...
Example	2013 Iranian presidential election (Q626198) --> File:نتیجهٔ انتخابات ۱۳۹۲.png 2013 German federal election (Q555931) --> File:Direktmandate nach Partei und Vorsprung – Bundestagswahl 2013, endgueltiges Ergebnis.svg
Source	see Politics infoboxs task force
Robot and gadget jobs	user:Dom bot could help to collect data from Wikipedia
Proposed by	Dom (talk)

Discussion

. Dom (talk) 05:54, 28 November 2013 (UTC)

Support Pikolas (talk) 18:36, 28 November 2013 (UTC)

Perhaps something like "election map image" might be a better label? --Yair rand (talk) 20:50, 28 November 2013 (UTC)

Modified in election map. --Dom (talk) 04:28, 29 November 2013 (UTC)

Question What about using image (P18) with a qualifier? --Pasleim (talk) 14:29, 25 February 2014 (UTC)

@Pasleim: Why not, but which qualifier ? But for me it's look simpler to use a direct property. --Dom (talk) 07:14, 16 March 2014 (UTC)

I think Domain should be 'election items' (Domain is the class of items which can use this property) Similarly Allowed Values should (I think) be 'commons file which show election results as a map' but image (P18) should probably be used instead, even without a qualifier (if its used on an election item then it shows the election) or with qualifier 'Depicts:electoral divisions; results' so I guess I

Oppose. I would support a more generic 'map' property which would be used to link to images which are maps and could be used on lots of different types of items - battles, places etc. Filceolaire (talk) 13:51, 3 June 2014 (UTC)

@Filceolaire:Why not, but these property are not : route map (P15), taxon range map image (P181), bathymetry image (P207) and locator map image (P242). You must understand that generic is not always better, so can you explain why it would be better. Saying that all these properties "... map" could be replace by one named "map" is not enough. You must explain why it would not be ambiguous. For example I imagine a case that for a party we could need the properties locator map image (P242) for the headquarter and the "election map" for the result of the last election. This project is not progressing fast enough because it's not simple enough. --Dom (talk) 05:51, 4 June 2014 (UTC)

Dom I agree that it needs to be a simple as needed to achieve our goals and no simpler.

The election map is associated with an election item, not a party item. A party takes part in lots of elections. Each election should have it's own item with a link to the map for that election. Changing the name to 'map' will not cause confusion. If there is confusion then use depicts (P180) as a qualifier to resolve the confusion. If the confusion is because we have three election maps each depicting the percentage of the vote received by a different party over the country then having an 'election map' property will not resolve the confusion - any map that an 'election' item links to is probably an election map.

headquarters location (P159) links to an item. Use locator map image (P242) as a qualifier to headquarters location (P159) if you need more info. Even if this was replaced by a generic 'map' property it would be obvious that it refers to the headquarters because it is a qualifier to headquarters location (P159). Do not use locator map image (P242) in a direct statement about the party because the locator map you are linking to does not show the location of the party; it shows the location of the party headquarters building. Do use locator map image (P242) directly in the item about the building where the party has it's headquarters because the map is about that building but you could use a generic 'map' property for this without losing any information.

For similar reasons we don't need special properties route map (P15). If its on an item about a road then it's a map of the road.

I think 'map' could replace taxon range map image (P181) too. If we have a map showing the location of the type specimen then use 'map' as a qualifier to taxonomic type (P427). Any other map linked from an item on a species is going to be a range map.

bathymetry image (P207) is a bit special. An item about a lake which links to a map is likely linking to a map of the lake, not the lake bottom. We could use depicts (P180) as a qualifier but there is at least a case for keeping this one.

Having one 'map' property is, in my opinion, much simpler than having five different map properties which an editor has to choose between. Filceolaire (talk) 19:39, 7 June 2014 (UTC)

@Dom, Pikolas, Yair rand, Pasleim, Filceolaire: Not done, no consensus and discussion stagnated four months ago. --Jakob (talk) 21:57, 11 October 2014 (UTC)

Typeface name sample

Not done

Description	Picture with the name of the typeface, written in the typeface
Data type	Commons media file
Template parameter	"image" in en:Template:Infobox_typeface, "Bild" in de:Vorlage:Infobox_Schriftart
Domain	typeface (Q17451) (typeface)
Allowed values	Pictures on Commons (svg is prefered)
Example	Helvetica (Q504745) => Helvetica font.svg; Source Code Pro (Q15974966) => Source Code Pro - Typeface name sample.svg
Source	en:Template:Infobox_typeface, de:Vorlage:Infobox_Schriftart
Proposed by	Stiegenaufgang (talk)

Discussion

Could be used in Template:Infobox typeface (Q12423690). Stiegenaufgang (talk) 20:34, 17 April 2014 (UTC)

Will a typeface item have more than one type of image? If not, image (P18) will be sufficient. John Vandenberg (talk) 21:25, 17 April 2014 (UTC)

A typeface should only have one typface name specimen. But if the typeface name specimen is using the image (P18) property, which property can be used for the infobox property "sample" in the typeface infobox?--Stiegenaufgang (talk) 23:25, 17 April 2014 (UTC)

Support --- Jura 18:26, 7 May 2014 (UTC)
Comment I think a "sample" property can make things clearer but I don't see why it should be restricted to typefaces. --Zolo ({i{int:Talkpagelinktext}}) 07:27, 8 May 2014 (UTC)

I also think that a sample property would be better than a specific property. So it would be great if the "typeface name specimen" would use the image (P18) property and the "typeface sample specimen" would use the sample property. It would also be great to mention this in the property description. --Stiegenaufgang (talk) 22:28, 9 May 2014 (UTC)

To add simply a sample, image would probably be sufficient. This type of sample is a bit like an auto-portrait. --- Jura 17:52, 22 May 2014 (UTC)

Oppose Stiegenaufgang, I recommend using image (P18) with qualifier depicts (P180)->sample (Q49906).--Micru (talk) 13:33, 23 May 2014 (UTC)

Comment I think using depicts (P180)sample (Q49906) as a qualifier isn't a good idea since its meaning is/should be thought a bit narrower: sample (Q49906) isn't a physical object. However, it will be possible to find a solution for that, and depicts (P180) isn't really well-defined ATM anyway. --Marsupium (talk) 13:26, 19 July 2014 (UTC)

It's "sample of type face name written in the type face font", not just Lorem ipsum .. How about "autoportrait" as property name? --- Jura 13:38, 19 July 2014 (UTC)

Not done Lacking support and probably too domain specific.--Micru (talk) 09:25, 18 October 2014 (UTC)

WORK

Not done

Description	work whom the person is one of the creators
Data type	Item
Domain	work (Q386724)
Allowed values	list or range of allowed values
Example	Ludwig van Beethoven (Q255) => Für Elise (Q11980)
Proposed by	Rical (talk)

Discussion

This property could help to buid lists of works in wikisource author pages or elsewhere. Rical (talk) 10:00, 2 September 2014 (UTC)

Isn't this just the inverse of creator/author/composer? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 13:44, 2 September 2014 (UTC)

Yes, each creator create works, each work comes from creators, an N to N link. As a first step. Also organisations or groups could create works. And works could be composite, picture from a photographer, music from violins... But these cases seem all ok by simple links.

But not always symetric as item objects. A work can be from a main author as a reference, but minor for this author and not to notice. --Rical (talk) 14:31, 2 September 2014 (UTC)

@Rical: Could you give an example of this asymmetry, please? For Für Elise (Q11980), property composer (P86) seems to work perfectly. Danneks (talk) 14:59, 2 September 2014 (UTC)

@Danneks: In my use of wikidata I mistake myself. In the module that I write, I must select the works from an author, this is not the job of the database. Now I only see the data links works/creators as symetric. --Rical (talk) 15:33, 2 September 2014 (UTC)

@Rical:, that seems to be notable work (P800) ? (I am not really convinced that this property was a good idea though)--Zolo (talk) 16:37, 2 September 2014 (UTC)

@Zolo:, Yes exactly, thanks. I just added it in Wikidata:List_of_properties/Person. --Rical (talk) 08:08, 3 September 2014 (UTC)

I'm testing person/work/edition elements related to itwikisource pages, and I see a main issue: the need of introduce explicitely and manually inverse properties (t.i. to add propetry "author" to work elements, then to add manually the inverse "work" property in author elements - is reduntant and redundance is the first cause of database corruption. I'd like an immediate effort to avoid any redundancy into inverse relationships, t.i. inverse relationships should be automatized (both when created and when edited) as soon as possible. --Alex (talk) 09:52, 4 September 2014 (UTC)

But why we need to create them? They are displayed rather nicely, e.g. in Reasonator. Danneks (talk) 15:57, 4 September 2014 (UTC)

I'm not so interested into looking at them here or by a tool; I'm very interested about using them into itwikisource pages! Can I export into itwikisource dynamically Reasonator output? Alex (talk) 16:59, 4 September 2014 (UTC)

I guess displaying this data in Wikisource will be possible when this bug is resolved. It is on the development plan. Danneks (talk) 14:33, 5 September 2014 (UTC)

Can we activate an automatic loop-back-link eachtime a user try to define a link known as symetric ?

Could we also use these symetric links in an item, in the section "Wikisource pages linked to this item", example in "Nelson Mandela", necessary to "activate" wikidatas for a wikisource Author:page ? Ask also to Tpt who built these links. --Rical (talk) 20:04, 4 September 2014 (UTC)

Not done An author can have too many works, better to use queries. For significant works use notable work (P800).--Micru (talk) 09:28, 18 October 2014 (UTC)

exemplar of

Done: exemplar of (P1574) (Talk and documentation)

Description	property for manuscripts, autographs, incunabula, distict printed copies
Data type	Item
Domain	mainly for items of Manuskripts, in a lesser degree for items of autographs, inkunabula, distict printed copys of literary works or editions
Allowed values	items of editions or literary works
Example	Codex Sinaiticus (Q152962) with Bible (Q1845), New Testament (Q18813), Septuagint (Q29334); Book of Kells (Q204221) with Vulgate (Q131175)+ Vetus Latina (Q170093); Sibyllenbuch fragment (Q7507354) with Sibylline oracles (Q740092); Isaiah scroll (Q1824743) with Isaiah (Q131458)
Format and edit filter validation	linked items ought to have instance of (P31) + literary work (Q7725634) (any subclass instead), or edition or translation of (P629) with work item; Items with this property ought to have instance of (P31) with manuscript (Q87167), language of work or name (P407) in most cases and additional properties collection (P195), inventory number (P217), P357 (P357)
Proposed by	Giftzwerg 88 (talk)

Discussion

Needed to link manuskript items to work items or edition items. Giftzwerg 88 (talk) 23:55, 27 September 2014 (UTC)

Comment I think definition of this property sould be wider by including other art, like architecture, painting or scupture. Like Pont des Arts (Q18048389) is a copy of pont des Arts (Q18048386). or Fortress of Louisbourg (Q540062) is a copy of the 18th century fort. --Fralambert (talk) 01:58, 28 September 2014 (UTC)

First I thougt of naming it "is a manuskript of", but I´d prefer and support a wider definition. However this property makes no assertion if this item is the "original" or a "secundary" copy. So the Mona Lisa of the louvre is just a copy of Mona Lisa out of several like M. L. of Prado and M. L. of Isleworth.--Giftzwerg 88 (talk) 15:19, 28 September 2014 (UTC)

@Giftzwerg 88, Fralembert: You will be interested on what Micru has to say about this and by the Functional Requirements for Bibliographic Records (Q16388) item. This is the exemplar of property of that model. TomT0m ^(talk) 20:46, 28 September 2014 (UTC)

Have a look on WikiProject Books about manuskript properties. This proposal is necessary to get the complete chain from work to edition/translation to a single manuscript or distinct printed copy. Manuscript items are the last links in the chain. --Giftzwerg 88 (talk) 23:10, 28 September 2014 (UTC)

@Giftzwerg 88, Fralembert, TomT0m: I am not sure this property is a "must". I am more inclined towards a more generic property like "manifestation of" (see proposal above) to group together all related physical entities and then between the instances of that class you can use "based on" (or even "follows", or "replaces") to indicate precedence.--Micru (talk) 16:17, 2 October 2014 (UTC)

sounds very abstract like Kim Jong-il (Q10665) is a manifestation of evil (Q15292) --Giftzwerg 88 (talk) 11:06, 3 October 2014 (UTC)

@Giftzwerg 88: Yes, that is the point, to link something abstract with something specific :) But this property is at FRBR "item" level to link two items where one has precedence. To me it seems redundat with "follows", but if that makes it more clear and allows better constraint checks, then I see no problem with it.--Micru (talk) 10:44, 4 October 2014 (UTC)

@Giftzwerg 88:I think we are a little lost here. I don't understand exactly what is the purpose of your proposal. First, I was thinking of the book is a derivative of the older book (it's why I was thinking about the copy). Now I am not totally sure if it is about a particuliar printed copy of a book or a derivative work of the book. --Fralambert (talk) 12:24, 3 October 2014 (UTC)

I am talking about a particuliar printed copy witch is a valuable gift of Professor Layton to the university, and one of five known survivers of this work. It has an ex libri of Layton, annotation on page 16 by Professor Moriarti, damages on page 41, pages 129 and 139 are mising and some Fingerprints are on the leather envelope. It is found in the Sackler Library by shelf number B 46756 G. We might have an Item of this special copy, but we can not link it to "Handbook of modern Philosophy" by Thomas Moore, a printed edition of 1746. Im also talking about Codex Sinaiticus, which can not be linked or otherwise connected to New Testament. We have only very few items about single copies of books, but all manuskripts are single copies and also all autographs.

It applies also to this cases: https://www.wikidata.org/wiki/Wikidata:WikiProject_Books#Single_copy_item_properties and there you can also see the problem if you use edition or translation of (P629). Lincoln Bible (Q1816474) is not an edition of Bible, lets say it is a (printed or hand writen) copy of the King-James-Bible of 1829 or whatever edition you name, one out of many copies or may be the sole surviver of this edition.--Giftzwerg 88 (talk) 12:58, 3 October 2014 (UTC)

Support OK, I understand. It would be usefull for book like Histoire du blason et science des armoiries, who is part of a classified heritage collection. --Fralambert (talk) 18:34, 3 October 2014 (UTC)

Oppose. I think the newly created property manifestation of (P1557) would work in lieu of this property. Mvolz (talk) 23:40, 11 October 2014 (UTC)
- Comment I don't think is the same concept; it is one level above as described by FRBR discussed above. But perhaps an "exemplar of" should be created instead of this one specific to manuscripts. Mike Linksvayer (talk) 20:21, 18 October 2014 (UTC)
- In this case Codex Sinaiticus (Q152962) is a manifestation of (P1557) the Bible (Q1845), Codex Sinaiticus (Q152962) is a manifestation of (P1557) the New Testament (Q18813). I just does not fit, is sounds very strange and abstract. The reader whats to know, what kind of manifestation it is. Is it a movie, a picture, a scan, a light projection? BTW the German label of this proposed property "ist ein Exemplar von" an can be used for distinct single copies of printed books and for manuskripts as well. I just could not find a more suitable label in English.--Giftzwerg 88 (talk) 22:05, 18 October 2014 (UTC)
  - Support Ah, I did not read very carefully, notice now "is a copy of", not specific to manuscripts at all. Still I wonder why the English description wouldn't also be "is an exemplar of"; I haven't thought about it deeply but it seems "copy" might be considerably more overloaded. --Mike Linksvayer (talk) 22:21, 18 October 2014 (UTC)
    - Changed label to "exemplar of" as stated in w:FRBR. At least that label is less loaded than "copy", which might be a relationship between exemplars.--Micru (talk) 22:41, 18 October 2014 (UTC)

Done @Giftzwerg 88, Fralambert, Mike Linksvayer, Mvolz: --Micru (talk) 17:02, 21 October 2014 (UTC)

Recording studio

Not done

Description	Place where a musical recording was made (or for a live album, where it was overdubbed and had post-production)
Data type	Item
Template parameter	`\|Studio=`, just added to in en:template:infobox album
Domain	work (Q386724) (creative work)
Allowed values	May have multiple values
Example	The Dark Side of the Moon (Q150901) => Abbey Road Studios (Q209651)
Source	external reference, Wikipedia infoboxes and categories (e.g. w:en:Category:Albums recorded at Abbey Road Studios)
Robot and gadget jobs	Once infobox field is populated; or from categories
Proposed by	Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits

Discussion

For live album venues, use P766 (P766). Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 12:09, 30 September 2014 (UTC)

Don't we already have a property for that, recorded at studio or venue (P483) ? But I don't know if it applies to both studio and live recordings. Okki (talk) 22:40, 3 October 2014 (UTC)

I think it is save to use recorded at studio or venue (P483) for studio as well. P766 (P766) is imho for events.--Giftzwerg 88 (talk) 10:58, 4 October 2014 (UTC)

Not done Redundant with recorded at studio or venue (P483).--Micru (talk) 09:46, 18 October 2014 (UTC)