Wikidata:Property proposal/Authority control

From Wikidata
Jump to: navigation, search
Shortcut: WD:PP/AUTH



This page is for the proposal of new properties.

Before proposing a property
  1. Check if the property already exists by looking at Wikidata:List of properties (manual list) and Special:AllPages.
  2. Check if the property is already pending or has been rejected.
  3. Check if you can give it similar label and definition as an existing Wikipedia infobox parameter, or if it can be matched to an infobox, to or from which data automatically can be transferred. See wd:Infoboxes task force for suggestions.
  4. Select the right datatype for the Property.
  5. Start writing the documentation based on the preload form below and add it in the appropriate section.

Creating the property

  1. Creation can be done after 1 week by a property creator or an administrator.
  2. See steps when creating properties.

Add a request

This page is archived, currently at Archive 24.

To add a request, you should use this form:

=== {{TranslateThis
| en = PROPERTY NAME IN ENGLISH
| de = <!-- PROPERTY NAME IN German (optional) -->
| fr = <!-- PROPERTY NAME IN French (optional) -->
<!-- |xx = property names in some other languages -->
}} ===
{{Property documentation
|status                 = <!--leave this empty-->
|description            = {{TranslateThis
  | en = put English description for property here, e.g. same as in the infobox documentation
  }}
|infobox parameter      = put Wikipedia infobox parameters here, if existing; ex: "population" in [[:en:template:infobox settlement]]
|datatype               = put datatype here (item, string, media, coordinate, monolingual text, multilingual text, time, URL, number)
|domain                 = types of items that may bear this property; preferably use Q templates, as specialized as possible, or text. ''e.g.'' {{Q|6999}} (astronomical object), {{Q|12136}} (disease), {{Q|11436}} (aircraft), and more generally {{Q|2221906}} (place), {{Q|43229}} (organization), {{Q|1656682}} (event), {{Q|386724}} (creative work), etc.  Special values (having specialized validation schemes): Persons, Taxons
|allowed values         = type of linked items (Q template or text), list or range of allowed values, string pattern...
|source                 = external reference, Wikipedia list article (either infobox or source)
|example                = sample items that would use that property, with proposed values; example: {{Q|1}} => {{Q|2}}
|filter                 = (sample: 7 digit number can be validated with edit filter [[Special:AbuseFilter/17]])
|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            = ~~~
}}
;{{int:Talk}}
(Add your motivation for this property here.) ~~~~

For a list of infobox parameters, you might want to use table format:

{{List of properties/Header}}

{{List of properties/Row|id=
|title          = audio
|type           = media
|qualifier      =
|description    = Commons sound file
|example-subject= Q187 <!-- Il Canto degli Italiani -->
|example-object = Inno di Mameli instrumental.ogg
}}

</table>

For blank forms, see Property documentation and List of properties/Row


Authority control / Normdaten / Autorité[edit]

See also Wikidata:Property proposal/Pending for approved items awaiting the deployment of currently unavailable datatypes
Already approved properties: list

Bulk proposal: museum databases[edit]

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).

User:Zolo
Jane023 (talk) 08:50, 30 May 2013 (UTC)
User:Vincent Steenberg
User:Kippelboy
User:Shonagon
Marsupium (talk) 13:46, 18 October 2013 (UTC)
GautierPoupeau (talk) 16:55, 9 January 2014 (UTC)
Multichill (talk) 19:13, 8 July 2014 (UTC)
Susannaanas (talk) 11:32, 12 August 2014 (UTC) I want to synchronize the handling of maps with this initiative
Mushroom (talk) 00:10, 24 August 2014 (UTC)
Jheald (talk) 17:09, 9 September 2014 (UTC)
Spinster (talk) 15:16, 12 September 2014 (UTC)
Pictogram voting comment.svg Notified participants to 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 (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 (talkcontribslogs). --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 (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)

Sports Reference ID[edit]

Wikidata:List of properties • v · d · e
Status:    Done
Property:P1447
Discussion

This is a very useful database for sports articles, and being able to pull their IDs from Wikidata would be immensely helpful for the projects. Jon Harald Søby (talk) 17:05, 12 August 2014 (UTC)

Symbol support vote.svg Support --- Løken (talk) 19:57, 16 August 2014 (UTC)
Symbol support vote.svg Support linking to a sportsreference profile is common in EL sections on enwiki. --AmaryllisGardener talk 20:55, 16 August 2014 (UTC)

ID on catholic.ru[edit]

Wikidata:List of properties • v · d · e
Status:    Done
Property:P1453
Discussion

Another reliable encyclopedia link. Vlsergey (talk) 18:05, 14 August 2014 (UTC)

ISO 12620 ID[edit]

Wikidata:List of properties • v · d · e
Status:    In progress
  • Description: Numeric ID from the Data Category Registry, which is a registry of linguistic terms specified by w:ISO 12620, which is a standard from w:ISO/TC 37. Each item in the registry has a PID which is a stable URI which is accessible via a RESTful interface, and it is available under a Creative Commons license. There is a web interface to the Data Category Registry as well as more information at http://www.isocat.org/index.html.
Discussion

The DCR is created and maintained by scholars all over the world. It is the subject of numerous scholarly publications (http://www.isocat.org/files/publications.html). Supporting items with links to the DCR could help with integration with Wiktionary in the future. Haplology (talk) 03:04, 19 August 2014 (UTC)

Pictogram voting comment.svg Comment As for the example: Why not 4948, 5748, or [2765 2765] for adjective (Q34698)? From my understanding, ISO 12620 is about implementing a registry for linguistic terminologies, i.e. existing vocabularies are imported to provide some kind of centralized system of reference. And isocat is one specific registry implementing that standard. Its identifiers are specific to isocat and not to ISO 12620. The listed terminilogies still exist in parallel, no attempts are made to create a combined vocabulary. Thus any concept ("class") may occurr many times in the registry. Intended usage of isocat seems not to provide direct points of refrence but rather to construct specific new sets of terminological classes for specific projects. But maybe I'm completely off the track... -- Gymel (talk) 08:27, 19 August 2014 (UTC)

WALS lect code[edit]

Wikidata:List of properties • v · d · e
Status:    Done
Property:P1466
  • Description: Language code from the World Atlas of Language Structures (wals.info).
Discussion

This would be a useful addition, as some languages with WALS codes don't have ISO 639-3 (yet). πr2 (t • c) 02:51, 22 August 2014 (UTC)

WALS genus code[edit]

Wikidata:List of properties • v · d · e
Status:    Done
Property:P1467
  • Description: Language "genus" code from the World Atlas of Language Structures (wals.info).
Discussion

This would be a useful addition, as many language families with WALS genus codes don't have ISO 639-3 (yet). πr2 (t • c) 02:51, 22 August 2014 (UTC)

WALS family code[edit]

Wikidata:List of properties • v · d · e
Status:    Done
Property:P1468
  • Description: Language (super-)family code from the World Atlas of Language Structures (wals.info).
Discussion

This would be a useful addition, as some language families with WALS codes don't have ISO 639-3 (yet). Many of these have glottocodes however. πr2 (t • c) 02:51, 22 August 2014 (UTC)

FIFA player code[edit]

Wikidata:List of properties • v · d · e
Status:    Done
Property:P1469
  • Description: Player code in the official FIFA database
Discussion

This one would be great, because it is very versatile. Not only can you use it to link to the general stats and records for a player, but also to their Confederations Cup profile and World Cup profile and so on. Jon Harald Søby (talk) 16:42, 22 August 2014 (UTC)

Patientplus ID[edit]

Wikidata:List of properties • v · d · e
Status:    Done
Property:P1461
  • Description: ID at patient.co.uk
  • Infobox parameter: it'll be used directly
  • Data type: String
  • Domain: disease (Q12136)
  • Allowed values: letters, numbers, and some extra characters like '()-
  • Suggested values: (deprecated)
  • Source: [1] and on
  • Example item and value: Asperger syndrome (Q161790) => Asperger's-Syndrome
  • Format and edit filter validation: [A-Za-z\-'\(\)]
  • Robot and gadget jobs: Dexbot will do
  • Proposed by: Amir (talk)
Discussion

I was asked by one of medicine content writer in English Wikipedia Amir (talk) 15:14, 24 August 2014 (UTC)

Symbol support vote.svg Support - Hi Amir @Ladsgroup:. Don't forget to ping the appropriate project if you request a property :) That will speed up voting. Tobias1984 (talk) 15:46, 27 August 2014 (UTC)


Tobias1984
Doc James
User:Bluerasberry
Wouterstomp
Gambo7
Daniel Mietchen
Andrew Su
Peter.C
Klortho
Remember
Matthiassamwald
Projekt ANA
Andrux
Pavel Dušek
Was a bee
Alepfu
FloNight
Genewiki123
Emw
Pictogram voting comment.svg Notified participants to Wikiproject Medicine -Tobias1984 (talk) 15:46, 27 August 2014 (UTC)

Symbol support vote.svg Support After seeing the outcome of a similiar project at en:Wikipedia_talk:WikiProject_Medicine#Wikidata_project_to_associate_drugs_with_interactions I feel like I would want this kind of property to use for other, similar government websites to get a comparable outcome. Blue Rasberry (talk) 16:47, 27 August 2014 (UTC)
Thank you, I'll do the next time Amir (talk) 20:51, 27 August 2014 (UTC)

Cycling Quotient ID[edit]

Wikidata:List of properties • v · d · e
Status:    In progress
  • Description: Identifier in Cycling Quotient (www.cqranking.com)
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)

Symbol support vote.svg Support --Micru (talk) 13:15, 12 September 2014 (UTC)

PRDL ID[edit]

Wikidata:List of properties • v · d · e
Status:    Done
Property:P1463
  • Infobox parameter: Not an infobox, but en:Template:PRDL uses this parameter
  • Data type: String
  • Domain: persons
  • Allowed values: numbers 1 to 6205
  • Suggested values: (deprecated)
  • Source: I have a spreadsheet cross-referenced by Worldcat ID.
  • Example item and value: John Calvin (Q37577) => 1 (see http://prdl.org/author_view.php?a_id=1)
  • Format and edit filter validation: 1 to 4 digit number
  • Robot and gadget jobs: I'm not sure how this works, but if it is possible for me to prepare the spreadsheet and hand it over to a bot that would be nice.
  • Proposed by: Jfhutson (talk)
Discussion

A very useful website. Jfhutson (talk) 14:25, 1 September 2014 (UTC)

Nupill Literatura Digital - Author[edit]

Wikidata:List of properties • v · d · e
Status:    Done
Property:P1473
  • Description: Author ID on Nupill Literatura Digital
Discussion

Nupill Literatura Digital is an impressive database regarding authors and books in portuguese language and about portuguese speaking countries/cultures. Certainly a must have for Wikidata. Lugusto (talk) 23:24, 9 September 2014 (UTC)

Symbol support vote.svg Support --Micru (talk) 13:15, 12 September 2014 (UTC)

Nupill Literatura Digital - Document[edit]

Wikidata:List of properties • v · d · e
Status:    Done
Property:P1474
  • Description: Work ID on Nupill Literatura Digital
Discussion

Nupill Literatura Digital is an impressive database regarding authors and books in portuguese language and about portuguese speaking countries/cultures. Certainly a must have for Wikidata. Lugusto (talk) 23:24, 9 September 2014 (UTC)

@555, Micru: Created in addition to Nupill Literatura Digital - Author (P1473). --Kolja21 (talk) 03:52, 17 September 2014 (UTC)

vici.org identifier[edit]

Wikidata:List of properties • v · d · e
Status:    Done
Property:P1481
  • Description: Identifier of a historical place of the roman empire at vici.org
Discussion

vici.org provides a mapping to Wikidata items. These links should be brought back into Wikidata to be reused by other parties. I contacted them to provide a dump of mappings to be imported in Wikidata. -- JakobVoss (talk) 13:52, 11 September 2014 (UTC) I've added a BEACON file to make life easier. It is at http://vici.org/BEACON.txt . Let me know if things need to change. Coming months I hope to link much more places.--René Voorburg (talk) 13:58, 12 September 2014 (UTC) -- Always uptodate is http://vici.org/vici/all/rdf . The dataset now contain about 20.000 objects.René Voorburg (talk) 06:19, 16 September 2014 (UTC)

Symbol support vote.svg Support --Kolja21 (talk) 23:34, 11 September 2014 (UTC)

Stack Exchange tag[edit]

Wikidata:List of properties • v · d · e
Status:    Done
Property:P1482
  • Description: Link to tag for the concept on a Stack Exchange network website like StackOverflow.com
Discussion

I've curated a list of a few thousand Stack Overflow tags and their corresponding Wikipedia articles. I asked on the project chat about how to incorporate it, and Emw suggested that this seems like the right place to store the information. I just built a list for StackOverflow.com, but I'm sure this can be done for any of the other sites.

I need a little clarification about creating such a property - is it acceptable to have multiple values of this property for the same entity? Because, for example, Apache HTTP Server (Q11354) should link to at least "apache" on StackOverflow.com, "apache-2.2" on ServerFault.com, and "apache-2.4" on ServerFault.com. Also, notice how some sites have separate tags for distinct versions of some software; would this be fine? Finally some Stack Exchange correspond to things that only have a sub-section of a Wikipedia article, and I'm not sure of the right way to refer to them on Wikidata.

Thanks for your input! Bskaggs (talk) 01:33, 12 September 2014 (UTC)

Tobias1984
Emw
Zuphilip
Danrok
Bene*
콩가루
TomT0m
Pictogram voting comment.svg Notified participants to Wikiproject Informatics @Emw:

  • "is it acceptable to have multiple values of this property for the same entity?"
Yes, I think that would be acceptable, especially in the initial implementation. Ideally, in my opinion, we would separate each version of a piece of software into its own Wikidata item even if it does not have a Wikipedia article, but that's probably too ambitious to start with. So if Apache HTTP Server (Q11354) links "apache" on StackOverflow.com, "apache-2.2" on ServerFault.com, and "apache-2.4" on ServerFault.com, that's fine. We can refine things later.
  • "Also, notice how some sites have separate tags for distinct versions of some software; would this be fine?"
Yes.
  • "Finally some Stack Exchange correspond to things that only have a sub-section of a Wikipedia article, and I'm not sure of the right way to refer to them on Wikidata."
Please create an item for those things. You can do so programmatically. Wikidata:Bots has a lot of bots that do this kind of stuff and Wikidata:Bot_requests has notes on past work.

Tobias1984
Emw
Zuphilip
Danrok
Bene*
콩가루
TomT0m
Pictogram voting comment.svg Notified participants to Wikiproject Informatics (your previous might not have gone through.) Emw (talk) 02:22, 12 September 2014 (UTC)

Symbol support vote.svg Support --Micru (talk) 13:15, 12 September 2014 (UTC)

*Symbol oppose vote.svg Oppose Unless I'm greatly mistaken, StackOverflow is a forum of sorts, so why link to it? --Jakob (talk) 11:32, 16 September 2014 (UTC)

  • Symbol support vote.svg Support Tag creation on stackoverflow is done by experienced users, users can not tag their questions with less common tags and stackoverflow itself is under "cc by-sa 3.0" so this is supporting another free knowledge database, I don't see any reason to oppose and like the idea. Also in future they can integrate their service with Wikidata for retrieving descriptions or we can compare our descriptions with theirs. –ebraminiotalk 13:45, 16 September 2014 (UTC)
  • @Bskaggs, Emw, Micru, Ebraminio: ✓ Done --Jakob (talk) 11:31, 19 September 2014 (UTC)

Cambridge Alumni Database ID[edit]

Wikidata:List of properties • v · d · e
Status:    In progress
  • Description: ID in the Cambridge Alumni Database/Alumni Cantabrigienses (ACAD)
Discussion

Alumni Cantabrigienses is a ten-volume directory listing all known students of the University of Cambridge up to 1900, with around 130,000 entries. The University Library at Cambridge has supported an online version of this ("ACAD", at venn.lib.cam.ac.uk) which has assigned an identifier to every entry and allows a static URL to be generated (see, eg, PRKR685T).

There are currently around 5000 links to ACAD on enwiki. Andrew Gray (talk) 17:32, 15 September 2014 (UTC)

This would be useful to have. It can be noted that many Oxford graduates are also included, where their degrees were recognised by Cambridge, something quite common in past centuries. So for British history the site is a substantial resource including notable people. Charles Matthews (talk) 11:03, 18 September 2014 (UTC)

Iran statistics id[edit]

Wikidata:List of properties • v · d · e
Status:    In progress
Discussion

The suggested code will be useful to find correct places at statistical tables of Iran's statistics organization. Iran has many settlements which have the same name and disambiguate of them needs this code. also in other Iran's data centers like this they uses this code (كدآماري). Yamaha5 (talk) 13:15, 16 September 2014 (UTC)

  • Symbol support vote.svg Support Looks great! –ebraminiotalk 13:32, 16 September 2014 (UTC)
  • Symbol support vote.svg Support --Kolja21 (talk) 04:22, 17 September 2014 (UTC)
  • Symbol support vote.svg Support--Çalak talk 09:08, 17 September 2014 (UTC)