Shortcut: WD:PP/P

Wikidata:Property proposal/Person

From Wikidata
Jump to: navigation, search
Property proposal: Generic Authority control Person Organization Event
Place Space Economics Transportation Natural science
Property metadata Creative work References Term Unsorted Sister projects

See also:
Wikidata:Property proposal/Pending – properties which have been approved but which are on hold waiting for the appropriate datatype to be made available.
Wikidata:Properties for deletion – proposals for the deletion of properties.

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:ListProperties.
  2. Check if the property is already pending or has been rejected.
  3. Check if you can give a similar label and definition as an existing Wikipedia infobox parameter, or if it can be matched to an infobox, to or from which data can be transferred automatically. See WD:WikiProject Infoboxes 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. Change status=ready on template to attract the attention of a property creator.
  2. Creation can be done after 1 week by a property creator or an administrator.
  3. See steps when creating properties.

Add a request

This page is archived, currently at Archive 41.

To add a request, you should use this form:

=== {{TranslateThis | anchor = en
| 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 = ...
|subject item           = <!-- <!-- item corresponding to the concept represented by the property, if applicable; example: item ORCID (Q51044) for property ORCID (P496) --> -->
|infobox parameter      = Wikipedia infobox parameters, if any; 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
|allowed values         = type of linked items (Q template or text), list or range of allowed values, string pattern...
|source                 = external reference, Wikipedia list article, etc.
|example                = {{Q|1}} → {{Q|2}}
|formatter URL          = <!-- for external identifiers, URL pattern where $1 replaces the value -->
|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.)


(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


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

Property proposal: Generic Authority control Person Organization Event
Place Space Economics Transportation Natural science
Property metadata Creative work References Term Unsorted Sister projects

Person / Person / Personne[edit]


Biographical Directory of Federal Judges id[edit]

   In progress
Description identifier for a judge in the Biographical Directory of Federal Judges
Data type String
Template parameter 1 in en:Template:FJC Bio and other language versions
Domain Q5
Allowed values \d+
Example Robert Gibson (Q7344755) → 851 -> [1]
Source from the website, or wikipedia templates.
Formatter URL$1&cid=999&ctype=na&instate=na
Robot and gadget jobs import from enwiki

The Biographical Directory of Federal Judges (Q4914870) is an directory of information about US Federal Judges. It is in the public domain, it is a useful source of information, as well as a unique identifier. Silverfish (talk) 19:03, 18 November 2015 (UTC)

Proposal format
  • Closed this as not done, because the request has been open for about a month and it lacks a proper motivation and description and the example is unclear. This makes it impossible to create the property. Mbch331 (talk) 11:40, 8 November 2015 (UTC)
    • Mbch331: Rationale is "implement Wikidata phase 2". Additional details are available by clicking on the template link for full details. I took the liberty to structure the discussion above. --- Jura 12:26, 8 November 2015 (UTC)
      • We shouldn't guess what it's meant for, we shouldn't go to other projects to see why a proposal has been done. The example doesn't match the allowed values, so the example is invalid. When asked for more information by 2 opposes, no information is provided. When I mark the proposal as not done, additional information is provided. The information needed to create a property should be provided upon the moment of proposing the property. And still not all information is provided. A link to a template isn't a property title. If you still want this property, place a proper request that doesn't make others guessing at what you want. Mbch331 (talk) 14:30, 8 November 2015 (UTC)
        • It's not clear if all opposes actually read the proposal, so I'd rather not get involved. IMHO the template needs to be checked in detail to assess the proposal. Obviously, it can help to re-state the project goal each time and, yes, including "en:Template:" in the label isn't needed, but we wouldn't have done that anyways. --- Jura 15:50, 8 November 2015 (UTC)
          • I assure you I read the proposal in full. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 17:54, 13 November 2015 (UTC)
          • I assure the same. The description is "..." and the motivation is "(Add your motivation for this property here.)". I've gone further and read the linked template, but it is a WP template and doesn't say anything about Wikidata implementation. If we don't have that information, then there really isn't anything to work with here and thus my opposition until the proposal is fleshed out to actually explain what the property is, what it is meant to do, and how it should be implemented. Josh Baumgartner (talk) 00:43, 18 November 2015 (UTC)
            • At least one of you had a look at the template. I wonder if there are several ways to implement this. Personally, I think there would be just one. Josh, could you list the variants? --- Jura 09:12, 18 November 2015 (UTC)
  • I have added what I think is the necessary information for the property, as I think it seems useful. I invite Jura1 to check it, and everyone else to see if they support now we have the information filled in. Silverfish (talk) 19:03, 18 November 2015 (UTC)
    • Josh Baumgartner might think there would be several ways of doing it, so I'm curious to learn more about them. --- Jura 16:26, 19 November 2015 (UTC)
  • Symbol support vote.svg Support @Silverfish, Jura1: This proposal looks good now. Josh Baumgartner (talk) 19:58, 19 November 2015 (UTC)
    • @Joshbaumgartner: can you advise us of possible alternate ways of implementing this, given the template at Wikipedia? --- Jura 10:15, 21 November 2015 (UTC)
      • Josh doesn't seem (and he can correct me if I'm wrong) to be saying there are sensible alternative ways of implementing this, but previously opposed the property as there was no implementation given. I've now provided one he seems happy with. Silverfish (talk) 19:27, 21 November 2015 (UTC)
        • As he is a property creator and given that he opposed it initially, I think he might have several options in mind. I think it's important to review them before we support or oppose this property. @Joshbaumgartner: please comment. --- Jura 12:54, 23 November 2015 (UTC)

Biography at the Bürgerschaft Bremen[edit]

Description link to the biography pages of the Bürgerschaft Bremen
Data type URL
Domain Persons
Allowed values URLs like*
Example Sandra Ahrens (Q2220948)
Proposed by Olaf Kosinsky

Ergänzung zu: Biographie beim Deutschen Bundestag (P1713) Olaf Kosinsky (talk) 09:56, 14 October 2015 (UTC)

@Olaf Kosinsky: The template says "url", but the id seems to be "631" for the example. What is the "358"? If we can only save the "631" and construct the URL for all examples it would be more like an identifier which would be preferrable. --Tobias1984 (talk) 20:24, 3 November 2015 (UTC)
358 is just the reference to the list of members – so id instead of url would be possible. But I see there a problem – nether the less if id- or url-datatype – by the fact that the urls are not valid anymore after each election. So after each election they will all be 404-pages. I'm not sure how to handle that. -- MichaelSchoenitzer (talk) 17:42, 7 November 2015 (UTC)
@MichaelSchoenitzer: Not a real identifier in that case. We could ask the people that run the database to assign real identifiers that don't 404 in the future. Otherwise I see no real benefit in including this. --Tobias1984 (talk) 14:24, 8 November 2015 (UTC)
It's still a valid description useful for this kind of politician for several years. I'd use URL datatype, we would just need to find a way to set them to "historic" (at some point in the future). --- Jura 15:45, 8 November 2015 (UTC), --- Jura 15:52, 8 November 2015 (UTC)
Makes we wonder, what will we do with all the Obama-related resources in 2017? --- Jura 14:16, 18 November 2015 (UTC)

Genius artist ID[edit]

   In progress
Description identifier for an artist on
Data type String
Domain persons or musical ensemble (Q2088357)
Allowed values string
Example Chuck Berry (Q5921) → Chuck-berry
Formatter URL$1

For the Genius (Q3419343) network of websites. Similar to Spotify artist ID (P1902) or MusicBrainz artist ID (P434). Sweet kate (talk) 21:21, 30 October 2015 (UTC)



   In progress
Description entry in the Dictionary of National Biography
Data type Item
Domain people primarily
Allowed values items for DNB entries at Wikisource
Example Edward of Norwich, 2nd Duke of York (Q452639)‘Plantagenet,’ Edward (Q19019224)
Source items with described by source (P1343) and such entries
Robot and gadget jobs KrBot for constraint checks
  • Symbol support vote.svg Support The current solution with described by source (P1343) (outcome of a previous proposal) doesn't allow efficient constraint checks. P1343 being used on a mix of items. Obviously, it could be a "subproperty" of P1343. --- Jura 09:31, 4 November 2015 (UTC)
    What kind of constraint checks is needed? -- Sergey kudryavtsev (talk) 04:08, 5 November 2015 (UTC)
  • Symbol support vote.svg Support Good idea to do it this way. Jonathan Groß (talk) 09:41, 4 November 2015 (UTC)
  • Symbol support vote.svg Support seems reasonable enough. Andrew Gray (talk) 12:30, 4 November 2015 (UTC)
also, @Charles Matthews: Andrew Gray (talk) 12:30, 4 November 2015 (UTC)
  • Comment. This limits DNB entries to the first edition and first two supplements. i.e. those currently in the US public domain and so on Wikisource. There are nearly ten further DNB volumes (decade supplements, plus one volume for people who were afterthoughts), before the ODNB arrived in 2004 with actual identifiers. Therefore this property is somewhat artificial from a bibliographical point of view. In other words, one can imagine cases where described by source (P1343) would still have to be used for the DNB. I don't object, but the proposal has to be seen as ad hoc. Charles Matthews (talk) 13:39, 4 November 2015 (UTC)
  • Symbol oppose vote.svg Oppose All encyclopedias should be handle same way. I prefer the solution with described by source (P1343), which allow to add new encyclopedia without a request a new property. -- Sergey kudryavtsev (talk) 04:08, 5 November 2015 (UTC)
  • Symbol oppose vote.svg Oppose per discussions Wikidata:Property proposal/Archive/31#DNB entry at Wikisource and Wikidata:Property proposal/Archive/31#Catholic Encyclopedia entry at Wikisource --Pasleim (talk) 09:22, 11 November 2015 (UTC)
    • @Pasleim:: in 6 months, such a templateproperty hasn't seen the day and, independently of the others, I think the mere size of DNB warrants the ease offered by specific property. --- Jura 00:42, 15 November 2015 (UTC)
  • Symbol oppose vote.svg Oppose as per Pasleim--Kopiersperre (talk) 13:02, 14 November 2015 (UTC)
  • Pictogram voting comment.svg Comment I am quite comfortable with the "described by" approach as something like enWP can pull a count and information about references. The issue I see at the moment is that the property has been used in two ways.
    1. to the overarching work where it is a non-specific reference, ie. such a work contains an article (and no more detail), though detail of vol. and page, or article could be given and is often used in the reverse way with "published in …"
    2. to the article (as has been done with DNB articles)
So it is a bit of a mess. The means to resolve that is to work out which it is to be, or if both are acceptable then how they are differentiated. To me it makes sense to have a qualifier to describe the parent work of the article. We also need to consider how this can work, such as at the WSes, which have the articles and need to run quick/simple data pulls to the their wiki, not wanting to run high-powered queries.

So maybe it is needs a fuller exploration of what is looking to be achieved and whether we have the components in place rather than some of the simpler "I don't like it" responses.  — billinghurst sDrewth 03:12, 15 November 2015 (UTC)

The combination of described by source (P1343) with section, verse, or paragraph (P958) can be used as a statement with qualifier and also within a reference claim. Specifying the overarching work (recte: specific edition of that work?) has huge merits as previous discussions emphasized, it`'s that work which allows accessing the quality of the reference. Infering this from information contained in a target item might be currently beyond the capabilities of most data consumers. However when we have specific items for entries in reference works they usually have additional statements which must be accessible, too. A minimal approach could consist of introducing a qualifier only property "reference item" to be used together with described by source (P1343) (in both situations). One probably will not be able to prohibit use of this item in contexts without overarching work of "dictionary" type, but IMHO use for journal articles or even individual blog entries seems to be appropriate. -- Gymel (talk) 11:44, 15 November 2015 (UTC)
You can specify this on the property definition page. Just as we do for most other online works. No need to repeat it on every P31:Q5. --- Jura 11:56, 15 November 2015 (UTC)
@billinghurst: This situation is appear due to Wikidata:WikiProject DNB#Examples : Subject of DNB entry recomends an improper use of P1343. I consider that this should be coverted to use with stated in (P248) as qualifiers. I can run my bot to fix it. -- Sergey kudryavtsev (talk) 08:31, 17 November 2015 (UTC)
@Sergey kudryavtsev, Gymel, Jura1: I am not sure what any of you are arguing in your later comments. I would suggest that would be resolved by examples of what would be right, and what is wrong. For P1343 which is right and which is wrong?  — billinghurst sDrewth 09:21, 17 November 2015 (UTC)
Supposedly the current use for P1343 is the outcome of a lengthy debate, thus I don't see a point of doing that change.
It's a non-issue if we use a separate property for DNB. --- Jura 09:32, 17 November 2015 (UTC)
I'm not principally opposing a dedicated property, but my proposal would be:
So P1343 gives only a gist from what's recorded in more detail in Q19019224 (questionable use of chapter (P792) there IMHO) and emphasizes the broader publishing context of the source. This is still a bit more indirect than in other cases without Wikidsource edition, where we appreciate a direct web link to the article via an additional qualifier . -- Gymel (talk) 10:36, 17 November 2015 (UTC)
@billinghurst: For P1343 which is right and which is wrong? — Usage rules of P1343 described in Property talk:P1343, of course. DNB is stored at enwikisource, so it should follow the second example in Property talk:P1343. I consider that the property usage rules have a highest priority over any project rules. Jura1 told some kind of "debates". But the property usage rules has scope whole Wikidata. There isn't even any notification at Property talk:P1343 about this consensus.
The motivation to use a qualfier. In the fact stated in (P248) as qualfier optimizes a retrieving information for a computer programs. If article item be a value of P1343, then a program code is obliged to inspect a claims in all item stored as P1343 values. But if a article item stored as a qualfier value for known values (such as Dictionary of National Biography (1885-1900) (Q15987216), Brockhaus and Efron Encyclopedic Dictionary (Q602358) etc), then a program code may search only claims of P1343 with values needed to its purpose.
The logic P1343 with stated in (P248) and reference URL (P854) as qualfiers is already programmed in LUA-modules at least in ruwiki and ruwikisource. -- Sergey kudryavtsev (talk) 11:21, 17 November 2015 (UTC)
It doesn't currently work for DNB in ruwiki (with any approach), but a fix is available if a new property would be created. --- Jura 14:12, 18 November 2015 (UTC)

Diccionari Biogràfic de Dones (ca) – (Please translate this into English.)[edit]

Description – (Please translate this into English.)
Data type String
Template parameter |id= in ca:Template:Diccionari Biogràfic de Dones
Domain see template
Allowed values see template
Example Maria Anna Josepha Althann (Q1895642)2034
Source template
Formatter URL$1
  • Symbol support vote.svg Support --- Jura 08:26, 5 November 2015 (UTC)
    • Please provide a valid formatter URL and English-language label and description. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 19:27, 6 November 2015 (UTC)
      • formatter URL is now provided. English label and description should not be a requirement in a multilinugal project in which everyone - even non english native speakers - are invited to participate. --Pasleim (talk) 00:22, 19 November 2015 (UTC)
        • They are indeed invited, and rightly so; nonetheless, the language in which this page - indeed, this project - is conducted is English. It is clear that Jura possesses workable English skills. Furthermore, the language he used in the proposal submission and his comments on it is English. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 12:57, 19 November 2015 (UTC)
  • Pictogram voting comment.svg Comment, for further information, please see the version of the proposal before someone removed content. --- Jura 20:03, 6 November 2015 (UTC)
  • Pictogram voting comment.svg Comment I moved this to the usual "format of proposal" section. --- Jura 09:02, 18 November 2015 (UTC)
  • It seems you inserted a section header above my comment. Correcting. --- Jura 18:21, 18 November 2015 (UTC)

Structurae ID (person)[edit]

   In progress
Description identifier for a person in the Structurae database
Represents Structurae (Q1061861)
Data type String
Domain civil engineer (Q13582652), architect (Q42973)
Example Jörg Schlaich (Q68932)joerg-schlaich
Source 9701 values (de, en, fr)
Formatter URL$1

As important as Structurae ID (structure) (P454) --Kopiersperre (talk) 12:55, 14 November 2015 (UTC)



married name[edit]

   In progress
Description married name
Data type Monolingual text
Template parameter various, often not distinguished from "full name"
Domain persons
Allowed values text
Example Hillary Clinton; Hillary Rodham Clinton; Hillary Rodham-Clinton; Svetlana Andropovna; Maria Garcia de Vega (full married names, per reliable sources)
Source external reference, Wikipedia article

We already have the property "family name," but this does not distinguish between a woman's family name at birth and her later married name(s). We should have the ability to distinguish between the two. At present we can only enter married names in the "family name" property without explanation or distinction, or the "also known as" alias field also without explanation or distinction. Dirtlawyer1 (talk) 08:35, 19 October 2015 (UTC)


This is the first time I have made such a request, and I am not familiar with all of the requested information items above. If you have questions, please ask. Please be patient with this rookie. Thanks. Dirtlawyer1 (talk) 08:35, 19 October 2015 (UTC)

This works only if you know the wedding day. --Pasleim (talk) 21:18, 19 October 2015 (UTC)
Or year, or any other vague span of time in which the name change may have happened. And if it's completely unknown, one should probably put start date: unknown anyway. --Yair rand (talk) 23:25, 19 October 2015 (UTC)
  • Pictogram voting comment.svg Comment just to clarify (as there is no sample), for Q6294 would this read "Clinton" or "Hillary Clinton"? --- Jura 07:07, 20 October 2015 (UTC)
  • @Jura1: Well, sir, that's subject to negotiation, but I would suggest that the new property structure should parallel that of the existing "birth name" property, and be a complete name with the language specified. Married names often vary widely in structure, with the relatively simple taking of the husband's surname (e.g., Hillary Clinton), the creation of a compound name (e.g., Hillary Rodham-Clinton), the use of both husband surname and the wife's maiden surname as a middle name without hyphen (e.g., Hillary Rodham Clinton), a different feminine surname form in Russian and several other Slavic languages (e.g., Svetlana Andropovna), or Spanish married combined name forms (Hillary Rodham de Clinton). I'm sure there are numerous other cultural and linguistic variations with which I am unfamiliar, combined with what is often the complete choice of the parties in the relatively new scenario of same-sex marriages. I know that in several countries, such as Germany, the format of married names has been strictly regulated by law, while in most English-speaking countries, the only limitations are social customs, which have been evolving toward greater flexibility and variation since the 1960s. Dirtlawyer1 (talk) 13:08, 20 October 2015 (UTC)
Pictogram voting comment.svg Comment yet one more naming property ? It's already complicate to choose a property in the list. I Symbol oppose vote.svg Oppose. Use "begin date" / "end date" on the (approximate) mariage date and preferred rank on the name valid ATM. Let's use Wikidata data model powerfulness ! author  TomT0m / talk page 17:46, 20 October 2015 (UTC)
@TomT0m: I appreciate your opinion, but it ignores the simple fact that for the overwhelming majority of our subjects with married names, we have neither an exact date nor even a year of their marriage. Of course, the situation is even more complicated for persons who have been married more than once. We need a property that identifies and collects all married names of a subject person within a single property, and that provides the flexibility to address the multiple married name formats not only in English-speaking countries, but multiple countries and cultures around the world. Stuffing married names into the "family name" property -- which only permits the entry of single-word linked family names -- does not do that. Please see my comment @Jura1 above regarding examples of the multiple formats of married names around the globe; the "family name" property simply is not made to purpose. Thanks. Dirtlawyer1 (talk) 19:08, 20 October 2015 (UTC)
@Dirtlawyer1: "the "family name" property simply is not made to purpose" => See the study about names on the talkpage of Wikidata:WikiProject Name for the different naming schemes in the world. This IS NOT a problem about married names, this is about all naming scheme. A scecialized property for married named won't help at all. I don't see how such a property will help if there is no known date either. It's exactly the same problem. It's enough to put the last known name with the "preferred" rank, and to use end date qualifiers and maybe qualifier about the order in sequence if we have no name. author  TomT0m / talk page 19:15, 20 October 2015 (UTC)
  • Symbol support vote.svg Support The advantage of having "married name" as a simple string parallel to birth name (P1477) is that this is very easy to extract and use (and very easy to understand). Any scheme that involves qualifiers immediately is made a lot harder to query -- even more so if one would then have to filter out any other reasons why a name might have been changed. In contrast with two simple properties for birth-name and married-name, it becomes very easy to see whether one of those fields is missing.<br?>I am not against making sure that the married family-name is also reflected as a value for family name (P734) -- just as the relevant family-name part of a birth name (P1477) would be reflected in that way. Having an explicit property for the full married name as a string, parallel to birth name (P1477), in fact makes it easier to achieve and maintain appropriate values for the family name (P734) property, because it then becomes easy to check that values corresponding to both the birth name (P1477) string and the married-name string are present -- when these two properties are known and distinct, then there ought to be the correspondingly appropriate number of distinct values for family name (P734). Jheald (talk) 19:45, 20 October 2015 (UTC)
    • @Jheald: This argument has little to do with "married name" as such, it would hold for the name of the person as well. Plus ... it's a lot worse. A person can be married several time, how would this work ? We would have to create a "second married name" ? This would be a property mess. For this, rename "name at birth" "full name", and use ranks and date, per the same reasoning I used above. author  TomT0m / talk page 20:03, 20 October 2015 (UTC)
      • @TomT0m: If we were to go down that route, it would make it very difficult to systematically extract birth names for a particular group of people. Having to use comparison operators on qualifier dates for a variety of full name values would kill query performance stone dead.
        Yes, there will be cases where there will be more than one married name. But in such cases one will usually want to extract all of them, and one can use an ORDER BY clause. On the other hand, one may well want the original birth name in a separate column, and that would be a total nightmare with the system you suggest. Jheald (talk) 21:20, 20 October 2015 (UTC)
        • @Jheald: I'm pretty sure it's not harder to do a min or max in SPARQL than to do an order by clause. (plus I'm pretty dubious that it's not really a usecase to extract birth names for a particular group of people. To extract the birth name or someone for its infobox OK, apart from that ... I really hate the proliferation of naming properties we can currently see pop down in the suggest list. You really have to be an expert to choose the right one. author  TomT0m / talk page 21:27, 20 October 2015 (UTC)
        • PS: It is possible, see for example. author  TomT0m / talk page 21:30, 20 October 2015 (UTC)
          • The point is that you are then relying on all of the date qualifiers to be in place and to be correct, simply to extract the birth name -- it's a lot more robust simply to have a birth name property, then you don't have to rely on any qualifiers to identify the right value.
            Yes, you could introduce an additional sub-query for each individual, to join in all the names and all the date qualifiers into the query, with an ORDER BY and a LIMIT 1 to extract the earliest (if all of the qualifiers are there and correct) -- but it makes a hell of a lot more work; plus you would probably have to hand-optimise it, because the auto-optimiser is a bit random when it comes to queries involving sub-queries. (A sub-query is needed rather than GROUP BY because one can extract the earliest date with GROUP BY and MIN(), but there's no obvious way to get the name that goes with it).
            Finally, I don't think it is unrealistic for users to potentially want a list of individuals that included a column of birth-names and a separate column of married names. Particularly for a print-out, that is very often exactly the format one wants. (Something like this, though at the moment we're a bit short of data). Jheald (talk) 22:07, 20 October 2015 (UTC)
  • A further thought: it may make most sense to introduce the "married name" property as a qualifier to spouse (P26). This would be the way to most directly associate the property with the right dates (if available) and the right spouse. Jheald (talk) 22:35, 20 October 2015 (UTC)
    • @Jheald: Good thought, but that only works if (a) we know at least the common, if not full name of the spouse, and (b) the spouse field may be entered as a plain text string (not linked text) for non-notable spouses. Dirtlawyer1 (talk) 18:38, 21 October 2015 (UTC)
    • Not sure how this would work for Molly Meacher (Q1943636) or Angela Merkel (Q567). --- Jura 13:03, 26 October 2015 (UTC)
      • @Jura1: I will let Jheald speak for himself, but I believe that Angela Merkel's legal married name is "Angela Dorothea Merkel," in keeping with the German name laws. When Merkel divorced her first husband she kept the Merkel name, and did not take her second husband's name when she remarried in 1998 (presumably because she was already well known publicly and politically as "Angela Merkel"). Had Merkel taken her second husband's name, as an example, the proposed property should be able to accommodate additional married names from second and third marriages, etc. Molly Meacher's legal married name is "Molly Christine Meacher," which appears to be relatively straightforward. Dirtlawyer1 (talk) 21:15, 26 October 2015 (UTC)
  • Symbol oppose vote.svg Oppose per Yair rand. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 19:58, 23 October 2015 (UTC)
  • Strong Symbol support vote.svg Support. Saying <family name:Clinton> with a start date doesn't tell us if her married name is Hilary Clinton or Hilary Rodham-Clinton or Hilary Clinton Rodham. We need this property with text datatype to specify the name she uses. 'Family name' can then be a qualifier to 'married name' to show what family names she uses since she is married with a different set of 'family names' as qualifier to her birth name. Joe Filceolaire (talk) 22:28, 25 October 2015 (UTC)
  • Symbol support vote.svg Support, but it will need to be clarified that it is to be the full name, not just the assumed family name (or we can do it that way and make it 'item' datatype in line with 'family name'). Josh Baumgartner (talk) 01:22, 18 November 2015 (UTC)
    • Josh, it is intended that the datatype be text (not a linked item) and that the full married name be used, not just the assumed family name. Because of the various different types and forms of married names -- e.g., husband's family name, compound-hyphenated name, feminine version of husband's family name, maiden name as middle name + husband's family name, etc. -- the simplest and most accurate way to enter the name in every instance is text format. As it is, we do not have items for every surname. Dirtlawyer1 (talk) 14:05, 18 November 2015 (UTC)


   In progress
Description name the subject is known by
Represents name (Q82799)
Data type Monolingual text
Example see below

We currently have several name properties which apply to certain specific types of names. However, sources do not always provide such definition when they provide a name, so there is no way to create a claim for the subject's name and know for sure which property to use. An educated guess constitutes a certain amount of original research. A contributor might see 'John Smith' and assume that given name (P735)  John and family name (P734)  Smith are appropriate, but even as uncontroversial as this may be to a native English speaker, there are many different linguistic constructs for names and many do not conform to first-last format. Even if we do add properties to cover all of the different classes of name out there, we will still have cases where the exact type is unknown, so we need a super-property that covers all of the name properties:

There are various ways in which this property can be used:

In an ideal world, all values would eventually be sorted into appropriate sub-categories as sources are found to substantiate such claims. The reality is that much of this type of specific detail is not available for some subjects and therefore the overarching property is needed. Josh Baumgartner (talk) 22:45, 20 October 2015 (UTC)

  • Why not just have a different property for each type of name, instead of the as (P794) business? There aren't even a dozen of them, I think. --Yair rand (talk) 23:11, 20 October 2015 (UTC)
    • @Yair rand: That is what I thought at first, but what do you do when you know it is their name (per your source), but it is not clear what class of name it falls under (because your source does not specify)? You are left to guess, which is not appropriate for a sourced statement. The other problem is that not all name classes have their own properties, and it is possible that the community will deem some of them too specific to warrant their own property. I actually would support a broad set of such properties, but there are cases where the right one does not exist. However, as I noted above, even if they all did, you still need this property to avoid invalid claims based on guessing. Josh Baumgartner (talk) 21:41, 21 October 2015 (UTC)
      • So, why the broad usage examples? I could support a property for situations where the name type just isn't known, but if you're specifying anyway, I don't see why this should be used. Also, the monolingual datatype is probably wrong. --Yair rand (talk) 22:02, 26 October 2015 (UTC)
        • @Yair rand: I'm not sure I understand your question, I am proposing that this be used in exactly that case: where the name type is not known (see the first example I show). As for monolingual datatype, I'm open as to how to do that better. Is a simple string a better plan? Josh Baumgartner (talk) 16:41, 28 October 2015 (UTC)
          @Joshbaumgartner: In the second example given above, you list "name <Leo Tolstoy>" along with the given name and family name properties. If the given name and family name are already specified, why the extra statement? Or am I reading the example incorrectly?
          Regarding datatype, the properties given name (P735) and family name (P734) both use the item datatype, which allows for more structured data (along with easier handling of multilingual issues, in my opinion). The "name" property would also need to be item datatype for other name properties to be subproperty of (P1647) of it, as suggested by Filceolaire below. --Yair rand (talk) 22:26, 28 October 2015 (UTC)
@Yair rand: Maybe the model of my second example won't prove to be how this is used, but even if that proves true, use for the first case is sufficient to warrant creation of this property. Also, details of how we apply subproperty of (P1647) is a discussion that does not necessarily relate to whether or not we should have the property. Making the datatype 'item' would be a huge burden to create an item for every permutation of a full name that might be cited. Josh Baumgartner (talk) 19:19, 18 November 2015 (UTC)
  • Strong Symbol support vote.svg Support. We need this as a property for other names to be subproperty of (P1647) of to use with a "search including subproperties" function - when we finally get one. We need it so that when we specify two given names, three family names, a patronymic (property needed for this) we can show how all these are put together - sometimes birth name isn't right for this. Joe Filceolaire (talk) 22:21, 25 October 2015 (UTC)
  • Symbol support vote.svg Support - Per Joe's comment immediately above. Can we add married name to the list, too? Dirtlawyer1 (talk) 06:17, 14 November 2015 (UTC)

first name identical to this family name[edit]

Description given first name that is the same as a last name. Use on items for last names.
Data type Item
Domain surnames/family names
Allowed values items for given first names
Example Sylvain (Q18001608) (family name): Sylvain (Q16281827) (given name)
Robot and gadget jobs Checking and correcting the "inverse of" relation with family name identical to this first name (P1533)

As an inverse of family name identical to this first name (P1533) to make it easier navigation between both of them. Actually when a surname is added as a given name it can be hard finding which element should be connected there instead, when it is easy to find it in the other way. Agabi10 (talk) 12:14, 11 October 2015 (UTC)

  • Symbol support vote.svg Support for symmetry: if you like having it ;). To avoid having them mixed up or merged, P1533 is generally sufficient. --- Jura 13:18, 18 October 2015 (UTC)
  • Symbol oppose vote.svg Oppose as creating inverse properties for their own sake bloats the database, makes items take longer to load and increases workload on contributors. Ideally, WD will eventually have support for true inverse properties which don't need to be individually entered and maintained, but instead automatically mirror to facilitate navigation within WD. I doubt that is coming any time soon, but creating a bunch of inverse properties just to facilitate navigation within WD is not a good plan. They are sometimes warranted, but in this case, I would have to say that family name identical to this first name (P1533) is sufficient. Note also that if there is both a family name and a given name that are the same, they should both be instances of a general name item that covers all applications of the name and this will give you a way to click-navigate from one to the other. Josh Baumgartner (talk) 23:40, 6 November 2015 (UTC)
  • Sorted to person from unsorted. Josh Baumgartner (talk) 23:41, 6 November 2015 (UTC)
  • Pictogram voting question.svg Question Josh Baumgartner I think that I don't understand what you mean. Even if in the future the software mirrors the symmetric properties still two properties will be required to know which property has to be mirrored with each of them (or a way to have more than one name in each property and choose the correct one, or even a renaming of properties to "name-surname relation" to make sense in both of the elements). Also I don't understand how family name identical to this first name (P1533) can be sufficient if the one I know is the surname and I don't know if a name element exists. Also having one element that combines the names and surnames spelled in the same way as you suggest to make it easier the navigation wouldn't bloat the database more than creating one property for that? As far as I know an element and a property are both one row in the database, and while the same property can be used in more than one element a new element will be needed for each couple. -- Agabi10 (talk) 21:07, 7 November 2015 (UTC)
    • @Joshbaumgartner: Still waiting an answer to my question. -- Agabi10 (talk) 17:33, 15 November 2015 (UTC)
    • @Agabi10: Regardless of whether or not such a technical development ever happens, I oppose this property as unnecessary bloat. In fact, I don't even see a purpose for family name identical to this first name (P1533) in a structured database, much less a needless reflection of it. However, it is there and if the structure of given and family names being subsets of a general name item isn't handy for you and you have to put a direct link between the two, then family name identical to this first name (P1533) would do it. There is no need to have to enter that information on both family and given name items. I'm not sure I understand your question about knowing the surname but not the other, since even with your proposal, you would have to know both family and given name to be able to create the statement, and if you know both then why not use family name identical to this first name (P1533)? Josh Baumgartner (talk) 01:16, 18 November 2015 (UTC)
    • @Joshbaumgartner: I agree with you in the reasoning that this property and family name identical to this first name (P1533) would be completely useless, but only in a state of the database where there is no type constraint violations in where a surname was used as a value for the name property or in the other way. I know that the people who adds the properties to any of the name/surname elements (even if it is me or any other) will have to know, at least for a moment, that there is an element created for the other one to be able to put the property. The thing is that if after them someone tries to correct constraint violations related to elements with that property where the incorrect one is put they will find it easier.
      I also know that the ideal solution would be that the suggestion drop down shows first a value with a name instance for a name property, and the same happens with all of the other properties, which, as far as I know at this moment is not necessarily true. This would decrease the number of violations. Having correct names and descriptions for all the entities in all the languages would also help, but that's too idealistic. Being able to search for a value without having to use external tools (even if Magnus' tools are great) would also make it all of this easier to find elements with family name identical to this first name (P1533) with the current element as a value.
      As you can see I know that there are more ways to solve it that are also technically possible, but at this specific moment I think that an inverse property is the most feasible one. At least now I understand better why you are opposing and even if the explanation doesn't make you change your mind at least I hope that now both of us are understanding what the other wanted to make clear.  – The preceding unsigned comment was added by Agabi10 (talk • contribs).
  • Symbol oppose vote.svg Oppose per Josh B. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 18:16, 18 November 2015 (UTC)



   In progress
Description group of high ranking officials, usually representing the executive branch of government
Represents cabinet (Q640506)
Data type Item
Template parameter parameter gouvernement 1 in fr:Modèle:Infobox Personnalité politique ; gabinet in ca:Plantilla:Infotaula de polític and similar cases
Domain Person

John Prescott (Q332393), as qualifier of Deputy Prime Minister of the United Kingdom (Q1507619)Blair ministry (Q3112705)

Yanis Varoufakis (Q40688), as qualifier of Finance minister of Greece (Q19752714)First Cabinet of Alexis Tsipras (Q18912888)

This property is for individuals holding or having held ministerial (cabinet) positions. The purpose is to add a qualifier to instances of position held (P39) that are children of minister (Q83307) or Secretary of State (Q736559) (any cabinet position). The qualifier would link to the item (and Wikipedia page) relative to the cabinet (also called ministry or government in some contexts), next to most frequently used qualifiers such as start time (P580), end time (P582), follows (P155) and followed by (P156). An alternative subject item is government (Q7188), due to the discrepancy in the use of the word government vs. cabinet in some languages. Place Clichy (talk) 06:37, 3 September 2015 (UTC)

Wouldn't member of (P463) work for this? Joe Filceolaire (talk) 12:31, 3 September 2015 (UTC)
Indeed that's the idea. However I'm not sure that member of (P463) can be used as a qualifier to another property. More importantly, I think it would be useful to have a property specifically labelled for cabinet membership, as member of (P463) does not seem to be currently understood or used for that purpose. Also, in the same way that position held (P39) will be used to track only the most noticeable positions held during a person's lifetime (such as a leadership position, or at least positions that would make a person eligible for an article on Wikipedia) rather than just any position they have held at some point, a property specifically labelled for membership in an executive branch is quite a different thing, in my opinion, from the generic notion of membership. Place Clichy (talk) 19:45, 3 September 2015 (UTC)
Why would it need to be a qualifier? Also, I don't think your understanding of position held (P39) is correct --Yair rand (talk) 13:18, 20 October 2015 (UTC)
Pictogram voting question.svg Question @Yair rand, Place Clichy: If I am understanding things right, this is for cases where a person holds an office/seat that is part of a cabinet. If these two claims are true:
It can simply be inferred that during the time period where 'A' and 'B' overlap:
Doesn't this obviate the need for the 'cabinet' property, since it can be derived by query? Josh Baumgartner (talk) 22:07, 21 October 2015 (UTC)

Sports and competition[edit]

personal best[edit]

Description an individual's best performance in a given discipline
Represents personal record (Q21142177)
Data type Number
Template parameter "pb" in en:template:infobox sportsperson
Domain person
Allowed values times or distances (up to two decimal places)
Example Usain Bolt (Q1189)field of work (P101)100 metres (Q164761) → personal best = 9.58 seconds
Format and edit filter validation number
Source external reference (e.g. IAAF website) or Wikipedia infobox
Robot and gadget jobs Potential to have bot tasks to fetch external data from certain sports body websites
See also record held (P1000)

The addition of this property will allow the inclusion of one of the key statistics of a person involved in sports such as athletics, cycling, swimming, weightlifting, etc. This information is almost always documented in Wikipedia articles for the person. Unifying it through WikiData is highly desirable as this piece of data does not need qualification and works across languages. Ide'ally this property should be able to be qualified by the corresponding sport/event, point in time, and location. This is my first time proposing so any advice on how best to technically achieve that would be much appreciated.

Looking to the future, as a personal best is the base unit for sport records, queries on the data could establish higher level records (world, continental, etc.) through this property and produce rankings. Sillyfolkboy (talk) 18:05, 18 October 2015 (UTC)

  • Pictogram voting comment.svg Comment, I added record held (P1000) in the description above. --- Jura 07:10, 20 October 2015 (UTC)
  • I agree that this is very desirable type of information to collect on WD. However, using it as a qualifier may not offer the best flexibility for this, and instead it should be a basic property:
I disagree with this modelling.
< competes in sport / discipline > 100 meters search < personal best >
9.58 seconds search < {{{5}}} >
seems way better. A rule of thumb : the "main snak"
< competes in sport / discipline > 100 meters search object or value >
< Usain Bolt (Q1189) (View with Reasonator) > personal best search < 9.58 seconds >
should be meaningful by itself. Which is the case when "competes in sport" is the main property, but not for "personal best" which is useless without qualifiers. author  TomT0m / talk page 10:30, 15 November 2015 (UTC)
Symbol support vote.svg Support Either way, I support creation of this property; how it gets used can be developed by those actually applying it. Josh Baumgartner (talk) 20:45, 22 October 2015 (UTC)
@Joshbaumgartner: I agree that there are benefits to separating "personal best" from "field of work" at the top level. This allows us to separately document a speciality and keep data on personal bests more broadly in non-specialities. Decathletes for example shouldn't have all ten events as their speciality, but rather decathlon as their speciality, and their bests for each event separately.
I'm not sure if the "position played" property is a better choice for specific variations of a discipline – the idea of competing in an event is quite different from a specialised team position. The former is much more changeable. Certainly, in terms of the track and field example I feel that "position played on team / speciality" would be better characterised as "sprinter" in this case, rather than a specific sprint event (e.g. 100 metres). Do you know of any other better options than the more generalised "field of work" one? Sillyfolkboy (talk) 17:26, 25 October 2015 (UTC)
@Sillyfolkboy: I do not know another property off hand. Field of work (with which we can say that a scientist works in the field of nuclear physics) certainly seems more of a stretch than position played (where the only question is whether it should be limited to position within a team or not, but at least it is clearly sport-focused). Personally, I see no reason why position played on team / speciality (P413) should be limited to team sports, and would be happy with correcting its description accordingly. Josh Baumgartner (talk) 19:19, 26 October 2015 (UTC)
@Joshbaumgartner: I think the high level idea for this property gets really problematic for runners, cyclists, swimmers and gymnasts, as their speciality covers a range of events. It would seem counter intuitive to have many events listed as a specialism. It works fine for sports where athletes are limited in their abilities to fulfil a role (e.g. very rarely is a ski jumper also a skier, or a goalkeeper also a forward). Maybe "participant of" (P1344) is a better fit for listing various non-speciality sporting events? Sillyfolkboy (talk) 20:09, 26 October 2015 (UTC)
  • Symbol support vote.svg Support. We need this property. We also need a more specific property than sport (P641) to specify which particular competition within athletics/gymnastics/cycling etc. a sportsperson competed in and further whether it was junior/senior/womens/mens/mixed pairs/paralympic classification etc. level. But that is another discussion. Joe Filceolaire (talk) 22:38, 25 October 2015 (UTC)
  • Symbol support vote.svg Support. Thryduulf (talk: local | en.wp | en.wikt) 12:53, 26 October 2015 (UTC)
  • Symbol support vote.svg Support --AmaryllisGardener talk 16:29, 10 November 2015 (UTC)

Sports disciplines competed in[edit]

Description ... Disciplines or events an athlete competes in within a sport
Data type Item
Domain Person
Example Haile Gebrselassie (Q171500)sport (P641)/field of work (P101)/position played on team / speciality (P413) → Sports disciplines competed in → marathon (Q40244), 5000 metres (Q240500), 10,000 metres (Q163892), half marathon (Q215677)

Following on from the above request on personal bests, I believe there is a desire to have a property on the specific sports discipline or events that athletes take part in. Josh Baumgartner above recommended position played on team / speciality (P413) to indicate this, but I think there is a difference here. For a number of sports, the competitor will compete in a variety of distinct events. P413 deals with a specialism, which correlates relatively well to sports where people specialise (e.g. football defender, quarterback, shot putter).

However it works poorly for people where it would be useful to list the many events they compete in, e.g. Haile Gebrselassie (Q171500), Bradley Wiggins (Q193876), Simone Biles (Q7520267). The specialism of P143 is better defined as the higher-level occupation (distance runner, cyclist, artistic gymnast). The more general field of work (P101) and sport (P641) work better at the higher level too, as events within a sport aren't really sports themselves. Effectively this property would allow us to specify, for example that Haile Gebrselassie competes in the sport of athletics (P641), in which he specialises as a long-distance runner (P413), and competes in the events of A, B and C (this new property). Sillyfolkboy (talk) 23:03, 2 November 2015 (UTC)

  • Symbol support vote.svg Support but the datatype should be item I think. Thryduulf (talk: local | en.wp | en.wikt) 22:08, 3 November 2015 (UTC)
  • Symbol support vote.svg Support a needed clarification. Antrocent (talk) 15:12, 4 November 2015 (UTC)
  • Pictogram voting question.svg Question do we good definitions of what is a sport and what is a discipline ? author  TomT0m / talk page 17:41, 8 November 2015 (UTC)
    • @TomT0m: I think it's any event that a sportsperson can enter in a tournament that represents just one aspect of a sport (i.e. not the sport itself). So yes for gymnastics rings, mixed doubles tennis, and 400 metres. No to gymnastics, tennis or sprinting. On a related note, weight-classes and sailboat-classes could be defined as special instances of the sports disciplines concept. Sillyfolkboy (talk) 22:09, 13 November 2015 (UTC)
      • @Sillyfolkboy: That does not answer on the definition of a "sport", this is just examples :) If I quote the frwiki definition of "sport" : "Le sport est un ensemble d'exercices physiques se pratiquant sous forme de jeux individuels ou collectifs pouvant donner lieu à des compétitions." => "Sport is a set of physical exercises that are played as individual or collective games and that can occur as competitions". Then "400 metres" is one of that exercises, and "athletics" is just a subclass of sport. author  TomT0m / talk page 11:36, 14 November 2015 (UTC)
        • @TomT0m: One could take the sports governing body approach, in that the sport is the whole thing organised by that body, while the athletes specialise in the disciplines/events within that sport (the Olympics makes this same distinction). The events are aspects of the same sport, not distinct sports in themselves. By comparison, while 100 metres and 200 metres are aspects of track and field (thus events, not sports), skiing and football are not aspects of the same sport (thus not events but sports). Sillyfolkboy (talk) 15:01, 14 November 2015 (UTC)
          • @Sillyfolkboy: Good point. But I think we should be consistent and take into account the token/type distinction as a foundation for Wikidata's ontology, see Help:Classification for an introduction, and use Olympics definitions as one of the alternative and use their item as "Olymic sport" and "Olympic disciple" (as metaclasses probably). There is always events involved anyway in a sport, there is no sport without people playing it at one time or another, informally or in competition :) author  TomT0m / talk page 15:09, 14 November 2015 (UTC)
            • @TomT0m: This concept is common in other sports ontologies (e.g. BBC's sport:subDiscipline). I believe the sub-sport idea needs to be free from competition hierarchy, chiefly to reflect general definitions on biographies. Not doing so effectively means that for sportspeople we would remove a connection with the sport under which they are commonly defined, in favour of the subdiscipline they compete in. This is unhelpful both in team sports, where the "sport" would, for example, become "11-a-side football", rather than the parent "association football", and also for sports with classes, "light welterweight" instead of "boxing". Alternatively, if we continue to list the main sport with the events as the person's "sport" then we have a conceptual hierarchy within that group which is not reflected data-wise on that item. The lack of an adequate property is the reason why sportspeople's events, classes, and subdivisions are largely absent from Wikidata, even though they are commonplace in biographical infoboxes of many sports. Sillyfolkboy (talk) 19:34, 14 November 2015 (UTC)
              • @Sillyfolkboy: That make sense, BUT : I think Wikidata should be confortable dealing with alternative ontologies to be able to represent different POV and deal with cultural differences. The solution I propose is totally compatible with your approach. It's just a minor disagreement in definitions that is actually dealable with the "metaclass" concept alone and a few competing but coexisting peacefully properties if really needed. Let's try to classify sport game using the principles used in Help:Classification
                The "tokens" or "instances" are games or actual competition, like 1998 FIFA World Cup Final (Q585295). Some are formalized using a set of rules governing the kind of people allowed to play or how to score, who is the winner, what are the components of the game ... . Let's take the class of all game that follows the same rules than 1998 FIFA World Cup Final (Q585295). It's association football match (Q16466010). It's a subclass of "sport game", as all instances of association football games are also sport game. We can imho assimilate all the classes of this kind to what you call a "discipline", or sometime a "sport". We can model this by a "metaclass" called (in english) "sport discipline", or whatever each locutors of each language wants, what's important is how we define it : a class of games following the same rule. What's define a discipline item is then clearly the rules of the game. Let's take another class of games : boxing games. It's also obviously a subclass of "sport game", as all instances of boxing games are also sport game. But there is "classes" of players, and the rule furthers refine the classification of the games with properties of the players, heavy one are not allowed to compete with finer ones, males and female can't compete together in the same game. There is then several subclasses of "boxing game" like "female boxing game" as one of them. For athletics : this is a sport that regroups games of very different kind. We can class the game by "100 meters", "marathons". They both are subclasses of "running games". For some historical reasons or whatever other, running games are classified as "athletic games" together with "pole vault" and others. I'd say "athletic games" is an instance of what you call a "sport" : it's a metaclass as it's an instance of a class of games. By putting an "instance of" : "Olympic sport" to the "athletics game" item and all the item of the like ("association football", ...) we can reflect pretty easily different classifications of game like the one you are suggesting, or other classifications based on practical federations organizations, or more "theorical" ones. Those "metaclasses" can be used to define more or less precise properties. author  TomT0m / talk page 11:09, 15 November 2015 (UTC)
                • @TomT0m: Am I reading it right that your alternative to having this property is to have all the sports disciplines listed as sports on a biography, with each discipline being a sub-class of the parent sport on its own item? I think the "Olympic sport" idea is a distraction because 99.9% of a sub-discipline's existence is non-Olympic in nature. For example, if we are listing Usain Bolt's personal best in the sub-sportsdiscipline of 100 metres, then it should have no relation to the Olympics at all because there is no real world connection between that performance and the Olympics (it was set at the World Championships). Sillyfolkboy (talk) 15:03, 15 November 2015 (UTC)
                  • @Sillyfolkboy: That would work indeed. As 100 meters or 200 meters are subclasses of athletics, we know he is an athlete, so "Sport: athletism" would be nothing but redundant. The "Olympic sport" was just an illustration of the flexibility of such an approach. author  TomT0m / talk page 15:36, 15 November 2015 (UTC)
  • Symbol support vote.svg Support. I think we need this a lot so we can distinguish, for instance, between 'tennis' and 'mixed doubles tennis'. This is a flexible approach that allows us to reflect different definitions, and not beeing ambiguous about what we mean. author  TomT0m / talk page 15:09, 14 November 2015 (UTC)
  • Symbol support vote.svg Support There is going to be a lot of hashing over what constitutes a 'sport' and what is merely a 'discipline' and I know that the label, description, etc. will be sorted out as we go through this, but I the basis is sound, so let's get the property in place and exactly how it is used can be developed as a result. Josh Baumgartner (talk) 21:12, 13 November 2015 (UTC)

Batting style[edit]

   batting style
Description whether a cricketer bats left or right handed
Data type Item
Template parameter "batting" in en:template:Infobox cricketer
Domain cricketers (occupation (P106):cricketer (Q12299841))
Allowed values right-handed (Q3039938), left-handedness (Q789447)
Example Phillip Hughes (Q3381076)left-handedness (Q789447), Ian Botham (Q982121)right-handed (Q3039938)
Source external reference, Wikipedia list article, etc.
Robot and gadget jobs import from en.wp infoboxes

This is a defining feature for cricketers. See also shooting handedness (P423) and playing hand (P741) for other sports and handedness (P552) generally (which is usually but no necessarily the same as batting style). Thryduulf (talk: local | en.wp | en.wikt) 15:32, 10 November 2015 (UTC)

I suggest to merge shooting handedness (P423) and playing hand (P741) and define it as a general property of handedness in sports. --Pasleim (talk) 09:15, 11 November 2015 (UTC)
Merge and use the existing items, per Pasleim. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 20:10, 13 November 2015 (UTC)

Two issues with the above comments

  1. Maybe it is more the time for those who have created the properties to assist in their redefinition. If one looks at the talk page for the proposed property to change it is very specific in the components that apply. For a general user to go and to modify this could be problematic, and such a change needs some level of imprimatur or governing and declared process. Someone clueless making that redefinition is simply going to be problematic.
  2. What is the cricketer bats right-handed, and plays tennis left-handed. It is quite well-known for even professional cricketers to bat one side, and bowl the other (eg. Michael Clarke) so without some delicate redesigning of the property, the simple statement of merge is a simple fail.  — billinghurst sDrewth 04:03, 15 November 2015 (UTC)

bowling style[edit]

   In progress
Description type of bowling employed by a cricketer
Represents Types of bowlers in cricket (Q7860947)
Data type Item
Template parameter "bowling" in en:Template:Infobox cricketer
Domain cricketers (occupation (P106):cricketer (Q12299841)
Allowed values instance of (P31) or subclass of (P279):Types of bowlers in cricket (Q7860947)
Example Sanath Jayasuriya (Q378810)Left-arm orthodox spin (Q1520158)
Source external reference, Wikipedia list article, etc.
Robot and gadget jobs import from infoboxes

This is the key defining characteristic for cricket bowlers. Not all types have items yet and those that do don't seem well developed, but I will work on this. Thryduulf (talk: local | en.wp | en.wikt) 15:50, 10 November 2015 (UTC)

  • Pictogram voting question.svg Question Would work? I would be hesitant to have to create numerous 'x style/method' properties for all of the different sports and specialties. Josh Baumgartner (talk) 21:21, 13 November 2015 (UTC)
    • That would reflect the "role" parameter in en:Template:Infobox cricketer (which would be one of bowler (Q21479668), "batsman", "wicket-keeper", "all-rounder" or "fielder" - I can't find entries for them immediately), not the type of bowler they are, so I don't think it is adequate here (as having a bowling style is not exclusive to those whose primary role is as a bowler). I can understand the reluctance to have countless properties for all sports but I don't think that will be necessary. I certainly can't think of an equivalent "type/style/method" property required for motorsport, football (soccer), rugby (union or league), archery, or (with lesser confidence) netball, volleyball, basketball, tennis, badminton or table tennis. It wouldn't surprise me if there was something similar with pitchers in baseball, but I don't know that sport well enough to be certain. Thryduulf (talk: local | en.wp | en.wikt) 22:41, 13 November 2015 (UTC)
      • @Thryduulf: Good point, so it seems a 'style' property is needed. I do know that there are baseball pitcher equivalents, as there are for chess players, just to name a couple I am familiar with. What about broadening this to be a general property ('style') that can cover all of these (and any others that come up)? Josh Baumgartner (talk) 22:48, 13 November 2015 (UTC)
        • Hmm, that's not a bad thought. It would need a good label and description crafting, if we want to avoid it being used for things like music genres, artistic movements, etc. "playing style" is my first thought, but I'm not sure I'm happy with that. Thryduulf (talk: local | en.wp | en.wikt) 00:49, 14 November 2015 (UTC)
  • support Something for which there is a need as it is a basic and standard component of cricket books (eg. Wisden bible) and commentary to describe someone who bowls accordingly. How well it is transportable to other components should not unreasonably delay its creation.  — billinghurst sDrewth 06:15, 21 November 2015 (UTC)

team caps for local leagues[edit]

   In progress
Description A number of appearances of player for every team he played with at local leauges.
Data type Number
Template parameter en:template:Infobox football biography caps
Domain person
Allowed values 0-1000
Source External reference, Wikipedia list article
Robot and gadget jobs they should be allowed
Proposed by Xaris333 (talk) 01:26, 3 May 2013 (UTC)

I am concerned about the name of this property. Different Wikipedia have different methods of choosing which matches do and don't go in the infobox, and I am take-my-car-if-I'm-wrong confident that we will not get a uniform consensus. Some Wikipedia go for the regular season of the league only, others for league + playoffs, others for league + playoffs + cups, and there are a couple of other deviations from these main categories. If we don't name this precisely enough, we will create a mess – English/German/French/Italian speaking editors would probably end up doing different things with the same parameter, and end users at individual wikis would have to painstakingly trawl through the values to work out which one is suitable for their wiki's purposes. I would suggest different properties for league and cup competitions, potentially one more for playoffs, plus one for total appearances. It may seem like overkill, but those three/four parameters would cover almost every conceivable use for this data. —WFC— 07:21, 3 May 2013 (UTC)

I change the name. Team caps for local leagues. Let see if this could be done, and then we could propose for cups, international legues etc. Xaris333 (talk) 12:17, 3 May 2013 (UTC)
Bonsoir, excuse me but i'm best in french :) Le problème est que chaque wikipedia fonctionne différement, les francophones comptent championnat + coupes dans l'infobox, les anglophones seulement le championnat, le problème vient également des sources, des sites ont parfois des divergences notamment pour les joueurs du passé, même chose pour les clubs : la différence entre club professionnel et amateur est faite dans les infobox joueurs dans fr.wikipedia pas dans en.wikipedia, les équipes B ne sont également pas indiquées sur fr. wki (sauf pour les pays où le club B est une filiale, exemple l'Espagne)--Remy34 (talk) 19:21, 5 May 2013 (UTC)
Ok. What do you suggest? We can and must find a global solution what we want to have on wikidata about team caps and goals. It would be really helpfull for users all over the world. Xaris333 (talk) 20:10, 5 May 2013 (UTC)
Je n'ai pas de suggestion ni d'idée, s'il existait un organisme central des statistiques de footballeur ce serait beaucoup plus simple...--Remy34 (talk) 07:38, 6 May 2013 (UTC)
une suggestion si recenser les sources statistiques de qualité pour remplir les données concernat les matchs - buts en championnat et dans les autres compétitions (coupes, play offs)--Remy34 (talk) 21:37, 7 May 2013 (UTC)

Symbol oppose vote.svg Oppose Why a property so specific ? In my opinion, it would be more appropriate to have a property "Total matches played" that could be used as a qualifier of the property member of sports team (P54) but also as a qualifier of a new property "takes part in" when the value is a sport competition. With this structure, the "Total league caps" property is no longer needed and the syntax is simplified. Same goes for the "Team goals for local leagues" and "Total leagues goals" properties : a "Total points scored" property should do the trick and could also be used for other sports than only hockey, football, handball and water-polo. Casper Tinan (talk) 14:21, 8 February 2014 (UTC)

team goals for local leagues[edit]

   In progress
Description A number of goals of player for every team he played with at local leauges.
Data type Number
Template parameter en:template:Infobox football biography goals
Domain person
Allowed values 0-300
Source External reference, Wikipedia list article
Robot and gadget jobs they should be allowed
Proposed by Xaris333 (talk) 01:26, 3 May 2013 (UTC)

My comments at team caps apply equally here. —WFC— 07:22, 3 May 2013 (UTC)

Same for me. My comments at team caps also apply here. Casper Tinan (talk) 14:22, 8 February 2014 (UTC)

total leagues caps[edit]

   In progress
Description The sum of the appearances of player for all the teams he played with (for former player, for local leauges).
Data type Number
Template parameter en:template:Infobox football biography totalcaps
Domain person
Allowed values 0-1000
Source External reference, Wikipedia list article
Robot and gadget jobs they should be allowed
Proposed by Xaris333 (talk) 01:26, 3 May 2013 (UTC)

total leagues goals[edit]

   In progress
Description The sum of the goals of player for all the teams he played with (for former player, for local leauges).
Data type Number
Template parameter en:template:Infobox football biography totalgoals
Domain person
Allowed values 0-1000
Source External reference, Wikipedia list article
Robot and gadget jobs they should be allowed
Proposed by Xaris333 (talk) 01:26, 3 May 2013 (UTC)

My comments at team caps apply to a certain extent here, in the sense that if we have multiple parameters for appearances, there would be multiple relevant totals. —WFC— 07:25, 3 May 2013 (UTC)

Symbol oppose vote.svg Oppose See my comments about "Team caps".--Casper Tinan (talk) 14:24, 8 February 2014 (UTC)

Competitor number[edit]

   Not done
Description The current number of a player
Data type Number
Template parameter en:template:Infobox football biography clubnumber
Domain person
Allowed values 0-1000
Source External reference, Wikipedia list article
Robot and gadget jobs they should be allowed
Proposed by Xaris333 (talk) 01:26, 3 May 2013 (UTC)
Although admittedly a rare case, there have been historic cases of players being given the squad number 0. Thumperward (talk) 13:56, 3 May 2013 (UTC)
Symbol oppose vote.svg Oppose unless broadened to be usable for all sports players who are assigned numbers. The label should be something more broadly applicable, such as 'jersey number' or maybe even 'competitor number', and the allowed values should be expanded to allow for 00 or larger numbers that are used in some sports. Thus we can avoid having a property like this for every sport. Joshbaumgartner (talk) 09:44, 9 May 2013 (UTC)
I change it to competitor number. Xaris333 (talk) 17:09, 9 May 2013 (UTC)
Symbol support vote.svg Support with implemented changes. Joshbaumgartner (talk) 13:07, 12 May 2013 (UTC)

 Not done - use sport number (P1618). Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 18:28, 23 November 2015 (UTC)


abilities (fictional figure)[edit]

   In progress
Description special abilities of a superhero/villain or other fictional figure
Represents ability (Q1347367)
Data type Item
Template parameter "powers" in en:template:Infobox comics character and title
Allowed values Abilities listed at en:List of superhuman features and abilities in fiction, though not limited to the list
Example Scarlet Witch (Q929285)reality warping (Q21451555)
Source external reference, Wikipedia list article, etc.

Would be nice for items about super-characters. You can move this proposal if it's in the wrong place. --AmaryllisGardener talk 01:41, 11 November 2015 (UTC)

  • Symbol support vote.svg Support. Joe Filceolaire (talk) 10:44, 11 November 2015 (UTC)
  • Symbol support vote.svg Support Mbch331 (talk) 21:34, 11 November 2015 (UTC)
  • Symbol support vote.svg Support as a broader 'ability' property. I see no reason to limit it to superheroes and their powers, but instead any notable abilities of an entity ought to be able to use this property. Josh Baumgartner (talk) 21:23, 13 November 2015 (UTC)
    Like reading (Q199657)? Jonathan Groß (talk) 21:54, 13 November 2015 (UTC)
If it is notable that an item is capable of reading (Q199657) then I would think so. Josh Baumgartner (talk) 22:53, 13 November 2015 (UTC)
Yeah, but how would we determine if something is notable or not? Someone could add "ability > reading", "ability > speaking", "ability > walking" and so on to all person items ... what would we do about it? Revert those edits? Jonathan Groß (talk) 12:33, 17 November 2015 (UTC)
Fictional characters only, That's how you solve that problem. Also, perhaps make an item called something like "superhuman ability", then set up a constraint, and there you go. --AmaryllisGardener talk 19:33, 24 November 2015 (UTC) player id[edit]

   In progress
Description player id at
Data type String
Template parameter pid in en:template:NFT_player
Domain human
Allowed values numerical value
Example David Beckham (Q10520)2189
Source the website or wikipedia templates
Formatter URL$1.html
Robot and gadget jobs bots could be created to import from templates

National Football Teams ( seems to be a useful resource for information about domestic and international football (soccer). There are templates that use the website on various language wikipedias, and at least the english template is widely used (18263 transclusions) Silverfish (talk) 23:41, 22 November 2015 (UTC)

  • Pictogram voting comment.svg Comment Suggest labelling as, say, " ID", to avoid ambiguity. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 22:05, 24 November 2015 (UTC)
    • That seems sensible. I've made it player id, as there might be other ids we could use from the website. Silverfish (talk) 23:22, 24 November 2015 (UTC)

Prosopographia Attica (it) – (Please translate this into English.)[edit]

   In progress
Description identifier for a person in Prosopographia Attica (Q2113277) by Johannes Kirchner (Q1697841)
Represents Prosopographia Attica (Q2113277)
Data type Number
Domain Q5
Allowed values Natural numbers between 1 and 15588
Example Hypereides (Q314447) → 13912
Format and edit filter validation 1-digit to 5-digit numbers
Source Band 1 and Band 2

PA (Prosopographia Attica) is, along with the wider PAA (A Prosopography of Ancient Athens), the most important catalog of ancient Athenian citizens; it's used by many modern sources like Davies' Athenian propertied families; moreover, it's available online gratis, unlike PAA, so users can read it easily. Epìdosis 16:38, 24 November 2015 (UTC)


elected in[edit]

   In progress
Description the election a person gained a position from, used as qualifier
Data type Item
Domain elected officials
Allowed values humans who have been elected to a role
Example Ted Strickland . position held -> Governor of Ohio ( elected in - > Ohio gubernatorial election, 2006 )

Antrocent (talk) 23:21, 27 November 2015 (UTC)

  • Symbol support vote.svg Support if we really do not have this already. I can't find anything but I'd be surprised if there wasn't something. Thryduulf (talk: local | en.wp | en.wikt) 23:58, 27 November 2015 (UTC)