Shortcut: WD:PP/P

Wikidata:Property proposal/Person

From Wikidata
Jump to: navigation, search

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:AllPages.
  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. 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 31.

To add a request, you should use this form:

=== {{TranslateThis | anchor = en
| 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 = ...
  }}
|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          = 
|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.)
}}

;Motivation

(Add your motivation for this property here.) ~~~~

;{{int:Talk}}

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


Person / Person / Personne[edit]

second or maternal family name of hispanic name[edit]

   In progress
Description Spanish generally consist of two parts: the paternal and the maternal family name, see Spanish naming customs (Q259614). This property is for the second (or maternal) family name.
Data type Item
Template parameter w:Template:Spanish name and others on Template:Spanish name (Q5623839)
Domain persons
Allowed values surnames
Example Gabriel García Márquez: Márquez (Q17984015), Diego Armando Maradona Franco: Franco (Q17983447)
Source w:Template:Spanish name

This can help reduce confusion around Spanish names. --- Jura 09:03, 6 September 2014 (UTC)

Would this be a matronymic or a matriname? --Yair rand (talk) 04:33, 10 September 2014 (UTC)
Generally, but not necessarily. The first page you link has a section on it. For a more detailed explanation, see w:Spanish naming customs. --- Jura 06:20, 11 September 2014 (UTC)
Symbol support vote.svg Support Changed to "hispanic" which is more inclusive.--Micru (talk) 22:45, 20 October 2014 (UTC)
  • Symbol oppose vote.svg Oppose: Why would we think of the first word in a surname as being more surname (P734) than a second (or third or fourth) is? One can easily use surname (P734) with qualifiers like series ordinal (P1545)  "1" (and optionally instance of (P31)  patrilineality (Q223375) if it is from the father's surname) for the first surname and series ordinal (P1545)  "2" (and optionally instance of (P31)  matrilineality (Q1136773) if it is from the mother's surname) for the second surname. --Closeapple (talk) 08:24, 25 October 2014 (UTC)
    • How can we query these? Are there any working samples for this? --- Jura 08:27, 25 October 2014 (UTC)
      • WikidataQuery CLAIM[734]{CLAIM[1545]} ought to list anything that gets one. What working samples are we looking for? --Closeapple (talk) 08:46, 26 October 2014 (UTC)
        • You'd need to identify items that have 1st, but not 2nd. Or items that have one that isn't marked as 1st or 2nd. Furthermore, you need to make sure that P734 keeps working for non Hispanic names. Many things that are actually easier with a distinct property. --- Jura 17:51, 26 October 2014 (UTC)
          • Aren't those all things that would also have to be dealt with if there is a new property? --Closeapple (talk) 04:41, 27 October 2014 (UTC)
            • It's quite straightforward with a new property for the second surname. You can easily use it to check for claims in combination with claims for people born in Spain or people of Spanish nationality. Besides, there is no confusions about the sequence of the surnames and the multiplicity. --- Jura 17:27, 27 October 2014 (UTC)
Use 'Birth Name' or 'Name in native language' or 'Official name' to give the exact layout of the name and 'surname' with multiple values to list all the surnames (some people have more than 2). Symbol oppose vote.svg Oppose. Filceolaire (talk) 22:19, 31 October 2014 (UTC)
This can't really be done with these properties. It's not a question of multiple names, but of sequence (and meaning) specific to Spanish names. --- Jura 12:05, 7 March 2015 (UTC)
Jura The sequence is given in the Label or the "Birth Name". We don't need to specify this in the "family name"statement. There may be cases where you want to specify which "family name" comes from the mothers family. This is a job for a qualifier. I suggest we use named after (P138). If we have a separate property then it becomes more difficult to compile lists of people with that family name since some will use the "Family name" property and some would use this separate property. Filceolaire (talk) 13:50, 13 March 2015 (UTC)
It's not "some". This applies to a specific field. Did you read the related article? --- Jura 05:08, 21 March 2015 (UTC)
I did read the article. It says customs vary over time and between different spanish speaking countries. My proposal works for double barrelled surnames whatever their origin. It even works if a couple choose to put the maternal family name before the paternal family which is sometimes done by hispanic people living away from hispanic countries (so they have both surnames but the paternal name is last as English speaking immigration officials expect). Filceolaire (talk) 02:07, 24 April 2015 (UTC)

work period (start)[edit]

   In progress
Description period during which a person flourished (fl. = "floruit") in their professional activity
Data type Time
Template parameter "workperiod" in c:template:creator
Domain persons (including pseudonyms, house names etc.)
Allowed values any date
Example Vincent van Gogh (Q5582) => between circa 1880 and circa July 1890
Format and edit filter validation (sample: 7 digit number can be validated with edit filter Special:AbuseFilter/17)
Source eg Commons:Creator:Vincent van Gogh, "fl." in biographies, VIAF, museum sites, etc
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 Jheald (talk) ammended by Filceolaire (talk)
Discussion

Proposal amended as the discussion below Filceolaire (talk) 23:00, 10 May 2015 (UTC)
Standard property for artists, creators etc: it's not unusual that we may not know when they were born, when they died, etc, but know quite well when they were active and their works were produced.

I'm also looking to migrate content from the Commons Creator template to WD, with a view to ultimately dematerialising it from Commons altogether (see Template:Creator/wrapper/test for some early tests). But I don't want to lose any functionality or data in the process. I've done my best to fill out the birdcage above, but need some help to know how best to code what are often likely to be probably quite approximate date ranges. Jheald (talk) 23:23, 20 September 2014 (UTC)

@Jheald: Would floruit (P1317) work? --Jakob (talk) 23:59, 20 September 2014 (UTC)
@Jakec: it's kinda different. For usual "life" "floruit" floruit (P1317) should be used, but we still need new property for years of active sport career or art career. -- Vlsergey (talk) 01:02, 21 September 2014 (UTC)
@Jakec:, @Vlsergey: Thanks, I had missed floruit (P1317). I think P1317 probably should work, but would need some adaptation to its existing rules and regulations. In particular, as per the Vincent van Gogh example above, one should be able to use it when one does know the date of birth and date of death, to indicate the period of activity. Secondly, we'd need to check that standard library routines for extracting and presenting such dates (eg Module:Wikidata) cope well with a range that can be actually quite precise. Per mw:Wikibase/DataModel#Dates_and_times, one could try to code this 1885-06-00 / precision:10 / before:5 / after 5.1, but I suspect that would probably decode to "about June 1885" (@Zolo: ?); in particular, there would be no way to specify that the two ends of the range have different precisions. Alternatively, does one make two entries, with separate start date and end date qualifiers? But then does the software know how to pick that up, and to interpret it as a range? Also, with two entries, it's hard to link them to show that the range has been specified by the source. Perhaps what's needed is an adjustment to the time datatype, to make it more possible to specify ranges with really quite well-known start and end points. Jheald (talk) 06:56, 21 September 2014 (UTC)
I think it's better to have two properties. Usually only the start point is specified and end point is assumed. -- Vlsergey (talk) 14:40, 28 September 2014 (UTC)
On further thought, having looked for typical examples of how this is used on c:Template:Creator templates, I do agree with User:Vlsergey that there is a case for the two different properties.
floruit (P1317) is good for asserting a particular moment in time when the artist worked.
But often what existing c:Template:Creator templates specify is much more precise -- an actual range, with well-identified start and end points.
That's a different thing. But the question remains, how best to specify the property. start time (P580) and end time (P582) are useful as qualifiers, but what assertion should they qualify? And could one still specify end cause (P1534) as a qualifer to a qualifier? Or if one wants to be able to use properties like end cause (P1534), does that mean a new first-rank property is needed? Jheald (talk) 13:46, 30 September 2014 (UTC)
Jheald if end cause (P1534) is used as a qualifier and the qualifiers subsequently all get moved out of order it is still clear what it means so there isn't a 'qualifier of a qualifier proplem. It can be a qualifier just like start time (P580) or end time (P582). Filceolbaire (talk) 22:34, 31 October 2014 (UTC)
Maybe two new properties. 'Floruit (start date)' and 'Floruit (end date)'?. Note that the span for a 'point in time' date - like 'Floruit' uses - is an uncertainty. It should never be be used for a range. Filceolaire (talk) 22:34, 31 October 2014 (UTC)
I think you're right. I think that's a good way forward. Symbol support vote.svg Support. Jheald (talk) 01:34, 2 November 2014 (UTC)
  • Based on the comments above, I Symbol support vote.svg Support. Eurodyne (talk) 23:43, 11 December 2014 (UTC)
Symbol support vote.svg Support, though I like work period better than fluorit for these start and end dates. Still, we can have aliases. - - PKM (talk) 02:54, 15 December 2014 (UTC)
Symbol support vote.svg Support based on above comments and because I think it could be useful for writers/artists/musicians, whose exactly birth date (or death date) is unknown but we know the period of their activity. --Nastoshka (talk) 23:40, 16 February 2015 (UTC)

I don't understand what exactly is the proposal here: to replace "floruit" with two properties 'Floruit (start date)' and 'Floruit (end date)'? But then, sometimes we just know that the author was active in a particular year, but we are not sure how many years he worked before and after that moment. How do you model that with two properties? BTW, I think "work period" is a better definition than "floruit": floruit makes sense when talking about writers, artists and the like, and doesn't sound good with sportsmen or politicians or others; while "work period" is in fact more general and can cover all cases. Candalua (talk) 08:59, 17 February 2015 (UTC)

Candalua The proposal is to add a new property. The discussion has raised an alternative proposal - to replace "floruit" with two new properties giving the start and end date. This is appropriate even if the person was only active in a particular year since quoting a year in wikidata technically refers to an instant in time which we are uncertain about exactly when. It does not refer to a period in time. To refer to a period - even one year - you need a start and end date, even if these appear to be the same because all we know is that both are sometime in the same year.

Pictogram voting question.svg Question. Why not just use start time (P580) and end time (P582) on occupation (P106)? Mushroom (talk) 00:31, 13 March 2015 (UTC)

Mushroom This is a special property to use when we don't have a date of birth or death. Filceolaire (talk) 13:41, 13 March 2015 (UTC)
  • Symbol oppose vote.svg Oppose Instead we should replace "Floruit" with two new properties - 'Floruit (start date)' and 'Floruit (end date)'. Filceolaire (talk) 13:41, 13 March 2015 (UTC)
  • Symbol support vote.svg Support Jheald Mushroom Candalua Nastoshka Eurodyne I have rewritten the property proposal and added the proposal below as the discussion above. I want to use this property for collective pseudonyms as well - these have their own items, separate from the individuals using them. Filceolaire (talk) 23:00, 10 May 2015 (UTC)

work period (end)[edit]

   In progress
Description period during which a person flourished (fl. = "floruit") in their professional activity
Data type Time
Template parameter "workperiod" in c:template:creator
Domain persons (including pseudonyms, house names etc.)
Allowed values any date
Example Vincent van Gogh (Q5582) => circa July 1890
Format and edit filter validation (sample: 7 digit number can be validated with edit filter Special:AbuseFilter/17)
Source eg Commons:Creator:Vincent van Gogh, "fl." in biographies, VIAF, museum sites, etc
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 Jheald (talk) ammended by Filceolaire (talk)
Discussion

added in accordance with the discussion above. Filceolaire (talk) 23:00, 10 May 2015 (UTC)

  • Symbol support vote.svg Support see discussion above. Filceolaire (talk) 23:02, 10 May 2015 (UTC)

Project Gutenberg author ID[edit]

   In progress
Description Author identifier at Project Gutenberg (Q22673).
Data type String
Template parameter Tends to be in external links on Wikipedia
Domain People, possibly groups, companies etc.
Allowed values Stems of Project Gutenberg author URLs
Example David Christie Murray (Q16031468) => 25179 (resolves to http://www.gutenberg.org/ebooks/author/25179 )
Source External links section on Wikipedia; Project Gutenberg
Robot and gadget jobs Possible
Proposed by Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits
Discussion

Useful disambiguator; and source of open-source texts. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 15:15, 29 November 2014 (UTC)

  • Pictogram voting comment.svg Comment: shouldn't this be "25179" in the sample?
  • I'd add ".org" to the name of the property as texts may be available elsewhere. --- Jura 13:43, 30 November 2014 (UTC)
    • The text may be, but this is the identifier at "Project Gutenberg"; there's only one of those. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 18:34, 30 November 2014 (UTC)
  • Pictogram voting comment.svg Comment I have a lot of experience with PG. I have just completed a project to map all 20,000+ author names on the PG website to equivalent Wikipedia article names. Often names differ wildly so its not easy to determine that "XYZ" on PG is the same as "DFG" on Wikipedia. But I have compiled a database that is complete, about 9200 names map to Wikipedia, the rest have no Wikipedia article. The database is not based on numbers, but on names. Because PG does not make public author numbers, and they disallow robots from scraping the site to find them. So for the example above, in the PG database (available in catalog.rdf at http://www.gutenberg.org/wiki/Gutenberg:Feeds) it maps to "Murray, David Christie" which can be found with the URL http://www.gutenberg.org/author/Murray,+David+Christie .. there are no author numbers in the Gutenberg catalog. Further, it is sometimes better so search on names because Gutenberg has duplicates in the database where the same person has two different accounts under slightly different (or related) names - doing a link via name thus finds them not just one. I guess this is a long story, but before this field is created and work put into, I suggest we contact PG and find out what they suggest is best going forward: using the publicly available name info found in catalog.rdf - or use the author number which is not publicly available in any database and can't be scrapped from the website and we have no idea if PG plans on keeping those numbers in the future. I don't normally log into Wikidata feel free to contact me over at en. -- Green Cardamom (talk) 20:49, 27 January 2015 (UTC)
  • Pictogram voting comment.svg Comment ps. if name strings are used instead of numbers, there will need to be a mechanism for multiple IDs since that is the case sometimes. For example multiple people share the same Wikipedia article (husband and wife authors etc) but whom each have unique PG name IDs. -- Green Cardamom (talk) 20:53, 27 January 2015 (UTC)
  • Pictogram voting comment.svg Comment Also.. there are multiple Project Gutenbergs. -- Green Cardamom (talk) 13:31, 28 January 2015 (UTC)
  • Symbol support vote.svg Support even tough it will be tricky to map the PG identifiers with Wikidata items --Pasleim (talk) 22:49, 20 May 2015 (UTC)

East-Asian names[edit]

courtesy name
   Done: P1782
courtesy name
name bestowed upon a person at adulthood in addition to one's given name, mostly in East Asia
Description name bestowed upon a person at adulthood
Represents courtesy name
Data type String
Domain Q5
Example Kang Youwei (Q360135) -> 廣廈
art name
   Done: P1787
art-name
type of pseudonym traditionnally adopted by writers and artists in East Asia
Description name used by an artist
Represents art-name
Data type String
Domain Q5
Example Kang Youwei (Q360135) -> 長素 / 明夷 / 更生 / 西樵山人 / 游存叟 / 天游化人
posthumous name
   Done: P1786
posthumous name
name given to a person after death (East Asia)
Description honorary name given after death
Represents posthumous name
Data type String
Domain Q5
Example Emperor Taizong of Tang (Q9701) -> 文皇帝 / 文武大聖大廣孝皇帝
temple name
   Done: P1785
temple name
name bestowed to a monarch after death (East Asia)
Description name used posthumously for monarchs
Represents temple name
Data type String
Domain Q5
Example Emperor Taizong of Tang (Q9701) -> 太宗
  • Given that these names are widely used, having these dedicated properties rather than a more generic one with qualifiers may be convenient.
  • There is also Q742466 (Q742466) and probably others, but they may not been so important.
  • en.wikipedia lists Chinese era name (Q256408) in the page about Chinese names, but it is a bit different, and I do not think it is relevant here. Eras can have their own items (and they do, see Q1042896 (Q1042896)).
  • For name and surname, we have item-type properties but here the name can be whatever people want, and are used by quite many people, other by juste one person, but the list is open ended and string sounds more appropriate.
  • Courtesy name was already proposed by user:GZWDer at Wikidata:Property proposal/Archive/12 but it was not done because we did not have monolginual strings at the time.
  • Could be retrieved from some Wikipedia templates, and from CBDB ID (P497) if the are no rights issues.--Zolo (talk) 15:50, 16 December 2014 (UTC)
Can you please give some examples to clarify this proposal?--Giftzwerg 88 (talk) 11:19, 25 January 2015 (UTC)
@Giftzwerg 88: done. --Zolo (talk) 13:30, 16 February 2015 (UTC)
Symbol support vote.svg Support all above proposals. —Wylve (talk) 01:41, 30 January 2015 (UTC)
Symbol support vote.svg Support --- Jura 05:43, 11 February 2015 (UTC)
@Giftzwerg 88, Wylve, Jura1:: 3/4 done: . For art name, I actually do not know if art the property should be broadened to Western-style pseudonyms (I tend to think it should). --Zolo (talk) 07:39, 18 February 2015 (UTC)
I agree. We currently have pseudonym (P742), but I'm not sure if its scope is too broad. By the way, for the three properties created, should the values be in the traditional or simplified script and in which language code? —Wylve (talk) 12:42, 18 February 2015 (UTC)
I'd say traditions characters, because it better corresponds to what was used at the time, and because one simplified characters sometimes corresponds to several traditional characters.
I do not know for the language code either. Technically, I suppose it can usually be considered Classical Chinese (code: lzh), but that sounds a bit odd. Rethinking about it, maybe we should make it a simple string with no language code attached to it, but, if needed, with a qualifier for the writing system used. That would sound like a better solution for non-Chinese people. Take en:Gia Long. His temple name is apparently 世祖, but which language is that ? That is Vietnamese written in Chinese script but that can also be Chinese. --Zolo (talk) 13:45, 18 February 2015 (UTC)
I think lzh would be appropriate, since other zh-XX codes imply modern Chinese and "zh" is just an ambiguous code representing all variants of Chinese. "世祖" could also be written as "Thế Tổ" in Vietnamese, so it might be a bit weird having two values for Vietnamese if the former is considered written in Vietnamese. In my opinion no one solution stands out to be the suitable one at the moment. —Wylve (talk) 17:00, 18 February 2015 (UTC)
For Gia Long, using monolingual text, we would have:
  • temple name: 世祖 language: vi or whatever stand for vietnamese with Chinese script
  • temple name: Thế Tổ language: vi
The trouble is that it is not really correct as 世祖 can be Chinese as well and Thế Tổ can be used in other languages using Roman script.
I think using a "writing system" qualifier works better:
A variant of this solution would be to put the alphabetical version as a qualifier of the Chinese-character version to make it clear that this is the same name written differently, not a different name. --Zolo (talk) 21:32, 18 February 2015 (UTC)
@Wylve, Jura1, Giftzwerg 88:, can I recreate those properties with datatype = string (without language), and recommend using a writing system (P282) qualifier rather than indicate a language ? As explained above, I think it is actually better. It is also more consistent with pseudonym (P742). --Zolo (talk) 12:25, 23 February 2015 (UTC)
I'm ambivalent about this, but I will support recreating them into string. I'm not an authority on this, but I think in the long run monolingual text and multilingual text datatypes should support a more precise ISO language scheme like ISO 639-6. The current ISO 639-1 does not include historical languages and ignores the different scripts used by the same language. —Wylve (talk) 18:33, 23 February 2015 (UTC)
@Wylve: I have changed the datatype to string, with a recommended {p|282}} qualifier. courtesy name (P1782), temple name (P1785) and posthumous name (P1786). I have also created art-name (P1787), as there did not appear be really satisfying alternatives. --Zolo (talk) 08:53, 21 March 2015 (UTC)

Religious rank rework[edit]

After re-thinking through my various requests from earlier and the feedback I was given, I think all of my original questions can be answered by approving the property request religious rank and using the qualifiers of start time (P580) and conferred by (P1027). (Admins: Once religous rank is approved, the other requests can be cleared out or archived.) Sweet kate (talk) 21:28, 23 December 2014 (UTC)

religious rank[edit]

   In progress
Description subject's level in religious hierarchy
Data type Item
Template parameter "rank" in en:template:infobox Christian leader, "rank" in en:template:infobox Jewish leader
Domain Persons
Allowed values subclass of position (Q4164871), profession (Q28640) (eg. bishop (Q29182) or cardinal (Q45722))
Example Joseph Ritter (Q1706916) => cardinal (Q45722)
Source external reference, Wikipedia list article (either infobox or source)
Proposed by Sweet kate (talk)

In a variety of religious infobox templates. Rank here is independent of the occupation or position of a person, and is more analogous to military rank (P410). Alias: rank. Sweet kate (talk) 19:22, 2 December 2014 (UTC)

BA candidate.svg Weak oppose If position held (P39) is not enough, try honorific prefix (P511) and academic degree (P512).--Giftzwerg 88 (talk) 23:50, 3 December 2014 (UTC)
Hmmm. But it is not a position, honorific prefix, or academic degree. It's a rank. It does not relate to the position held or education earned. And honorific prefixes are already used in different ways for these same people — someone with religious rank cardinal (Q45722) has the honorific prefix His Eminence (Q1337757). I see that military rank (P410) was approved with no real issues, and I am unsure how this is really any different. --Sweet kate (talk) 15:47, 4 December 2014 (UTC)
(See my further thoughts above below under consecration date too.) Sweet kate (talk) 15:55, 4 December 2014 (UTC)
Symbol support vote.svg Support I think this is a separate semantic concept that can't be covered by existing properties. --Tobias1984 (talk) 09:26, 23 December 2014 (UTC)
Why do you think instance of (P31) can´t do the job? Meanwhile I´ve weekened my position, but I think we need a more generic concept, that can be used for military ranks as well or every other hierarchy. I tend to widen up the use of military rank (P410) and change the label from "military rank" to "rank" instead of creating a new one.--Giftzwerg 88 (talk) 11:34, 25 January 2015 (UTC)
You wouldn't use instance of (P31) for particulars like this anymore than you'd use it to replace position held (P39) or occupation (P106) — an individual is always inherently a human, but not inherently, at their essence, a particular rank (or position or occupation). Ranks have start dates, and go in and out of being "true"/preferred. (Once you're promoted to colonel you're not a private anymore.) I'd be fine expanding military rank (P410), but I don't know if the military-knowledgeable people would have a reason to disagree? If we do that I'd want that to have a mandatory qualifier of of (P642) — a person is rank "bishop" of (P642) => the Catholic Church or rank "general" of (P642) => the US Army. (Or whatever. Really it seems like that should be mandatory with military rank (P410) anyway. Ranks only mean anything if you know what the ranking system is.) Sweet kate (talk) 18:18, 27 January 2015 (UTC)
OK. I´d support to modify military rank (P410) in order to be able to use it for all kinds of hierarchy and to make of (P642) mandatory to describe what kind of hierarchy.--Giftzwerg 88 (talk) 13:13, 31 January 2015 (UTC)
Agreed, military rank (P410) should be able to be expanded, as even if someone holds both a military and a religious rank, qualifiers can define which hierarchy each is held within. Josh Baumgartner (talk) 18:15, 27 February 2015 (UTC)

Symbol oppose vote.svg Oppose for Catholic Church: bishop (Q29182) or cardinal (Q45722) are fonctions not ranks. — Ayack (talk) 16:30, 13 March 2015 (UTC)

hair color[edit]

   Done: P1884
hair color
person's hair color. Use P585 as qualifier if there're more than one value.
Description model's/person's hair color
Represents human hair color
Data type Item
Template parameter "hair_color" (en:Template:Infobox model), "cheveux" (fr:Modèle:Infobox Mannequin), possibly others on Template:Infobox model (Q5833821)
Domain person (Q215627)
Allowed values items for hair colors
Example Iman (Q256531): brown hair (Q2367101) ; Kristen Bell (Q178882): blonde (Q202466)
Discussion

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

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

lay name[edit]

   In progress
Description First name of clergyman. Ex. pope John Paul II - first name (secular) is Karol
Represents birth name (P1477)
Data type Multilingual text (not available yet)
Domain Q250867
Example Q989, Q502776 and many many more
Proposed by Borys Kozielski (talk)
Discussion

Wielu duchownych, w tym Jan Paweł II nie mają odpowiedniej do ich imion, nazwisk i nazwy świeckiej deklaracji. Borys Kozielski (talk) 14:21, 24 January 2015 (UTC)

Pictogram voting comment.svg Comment are you looking for the property equivalent to religious name (Q1417657)? If you are looking for the secular (not religious) name, that would be "lay name" in English, but I think we would use birth name (P1477) for that. PKM (talk) 00:49, 25 January 2015 (UTC)
pl:odwrotność religious name (Q1417657); eo: inverso religious name (Q1417657) en: reciprocal religious name (Q1417657) Marek Mazurkiewicz (talk) 01:11, 31 January 2015 (UTC)
Pictogram voting comment.svg Comment Or given name (P735)? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 20:56, 29 January 2015 (UTC)
pl: nie; eo: ne; en: no Marek Mazurkiewicz (talk) 01:11, 31 January 2015 (UTC)
@Marek Mazurkiewicz: Why not? --Yair rand (talk) 23:35, 12 March 2015 (UTC)
Pictogram voting comment.svg Comment or surname (P734) Oursana (talk) 23:54, 12 March 2015 (UTC)

DNB entry at Wikisource[edit]

   <withdrawn>
Description item with DNB entry at Wikisource
Represents Dictionary of National Biography (Q1210343)
Data type Item
Domain persons
Allowed values

items with sitelinks to Wikisource entries with DNB source text

Inverse property of main subject (P921):
If [item A] has invalid IDen (Property pr) with value [item B],
then [item B] should also have main subject (P921) with value [item A].
List of this constraint violations: Database reports/Constraint violations/Property proposal/Person#Inverse, hourly updated report
Target items of "invalid IDen (Property proposal/Person)" should have a statement with "part of (P361)" and value "Dictionary of National Biography (Q1210343)": If [item A] has this property with value [item B], [item B] is required to have property "part of (P361)" with value "Dictionary of National Biography (Q1210343)"
List of this constraint violations: Database reports/Constraint violations/Property proposal/Person#Target required claim P361 = Q1210343, hourly updated report
Target items of "invalid IDen (Property proposal/Person)" should have a statement with "instance of (P31)" and value "biography (Q36279)": If [item A] has this property with value [item B], [item B] is required to have property "instance of (P31)" with value "biography (Q36279)"
List of this constraint violations: Database reports/Constraint violations/Property proposal/Person#Target required claim P31 = Q36279, hourly updated report
Item: items with this property should also have instance of (P31) = human (Q5)
Report: Magnus' query site

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

Catholic Encyclopedia entry at Wikisource[edit]

   <withdrawn>
Description item with Catholic Encyclopedia (CE) entry at Wikisource
Represents Catholic Encyclopedia (Q302556)
Data type Item
Domain persons
Allowed values

items with sitelinks to Wikisource entries with CE source text

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

Declarator.org ID[edit]

   Done: P1883
Declarator.org ID
Person ID on Declarator.org database
Description Person ID on Declarator.org database
Data type String
Domain types of items that may bear this property
Allowed values \d+
Example Vladimir Putin (Q7747) => 582
Formatter URL http://declarator.org/person/$1/
Discussion

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

McCune-Reischauer[edit]

   In progress
Description There are many different romanizations from languages that are not written in latin letter. pinyin transliteration (P1721) already is a property. But there are many more like McCune-Reischauer and the revised romanization for Korean, Romaji for Japanese etc.
Represents McCune–Reischauer (Q621412)
Data type Monolingual text
Template parameter en:template:Infobox Korean name, de:Vorlage:Koreanischer Name
Domain Person
Allowed values names
Example Park Geun-hye (Q138048) -> Pak Kŭnhye
Source en:template:Infobox Korean name, de:Vorlage:Koreanischer Name
Robot and gadget jobs Maybe a bot can import the data from the Wikipedia templates. However, the English Wikipedia often is wrong about the McCune-Reischauer romanization. There is a nice tool by the Busan National University: http://roman.cs.pusan.ac.kr/input_eng.aspx .
Discussion

Proposed by: Christian140 (talk) I made this exemplarily for McCune-Reischauer. However, more romanizations should be considered. Not only for persons, maybe general. Movies, video games, places... See also en:Template:Infobox_East_Asian_name, en:Romanization of Russian Christian140 (talk) 11:10, 20 April 2015 (UTC)

  • @Christian140: Please provide an example. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 18:06, 20 April 2015 (UTC)
    • Let's take the current Korean president Q138048. In her English Wikipedia article en:Park Geun-hye you can see an infobox on the left side featuring her name in Hangul (박근혜), Hanja (朴槿惠) and then Hangul romanized by the revized Romanization (Bak Geun-hye) and by McCune-Reischauer (Pak Kŭnhye). I think without these properties, a table like this wouldn't be possible anymore if the template would be generated out of Wikidata. --Christian140 (talk) 18:28, 20 April 2015 (UTC)
  • Symbol support vote.svg Support but I think maybe this should be string datatype or, if it is monolingual datatype, then what language would 'Pak Kŭnhye' be (@Christian140, Pigsonthewing:) ?Filceolaire (talk) 07:09, 22 April 2015 (UTC)
    • @Filceolaire:. I think it should be made like pinyin transliteration (P1721). Actually, I only wanted to raise attention for romanizations. McCune-Reischauer is widely used in academics, but in 2000, the government of South Korea made the Q498721 their official system. For example, by McCune-Reischauer, the capital is spelled Sŏul, by the revised romanization it is spelled Seoul. But there are also other systems like Yale romanizations. However, maybe it is not relevant enough... I don't think it really has a language... or Korean? --Christian140 (talk) 16:29, 23 April 2015 (UTC)
Symbol support vote.svg Support but unsure if string or monolingual text is better --Pasleim (talk) 12:37, 15 May 2015 (UTC)

represented by[edit]

   Done: P1875
represented by
express a relationship between a subject and their agent
Description

To be used to express a relationship between a person and his/her agency, such as:

  • a contemporary artist and his/her art gallery
  • a fashion model and his/her modeling agency
Data type Item
Domain human (Q5), group of humans (Q16334295)
Allowed values human (Q5), group of humans (Q16334295) (an agent can also be an individual person)
Example Tyra Banks (Q172303) represented by Elite Model Management (Q616374); Michaël Borremans (Q284808) represented by Zeno X (Q4473899)
Source external reference (note: this should be moved to the property statements)
Discussion

Proposed by: Spinster (talk)

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

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

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

Murdered[edit]

   In progress
Description This is a property to link murderers to their victims
Represents murderer (Q16266334)
Data type Item
Template parameter Wikipedia infobox parameters, if any; ex: "population" in en:template:infobox settlement
Domain human
Allowed values type of linked items (Q template or text), list or range of allowed values, string pattern...
Example Johan Barger (Q742496)Catharina Helena Mirande (Q19685470)
Format and edit filter validation (sample: 7 digit number can be validated with edit filter Special:AbuseFilter/17)
Source external reference, Wikipedia list article, etc.
Robot and gadget jobs Should or are bots or gadgets doing any task with this? (Checking other properties for consistency, collecting data, etc.)
Motivation

I was looking for a way to link murderers to their victims. This is the inverse of killed by (P157) Jane023 (talk) 08:29, 3 May 2015 (UTC)

Discussion
Pictogram voting comment.svg Comment last discussion: Wikidata:Property_proposal/Archive/23#killed --Pasleim (talk) 20:53, 4 May 2015 (UTC)
Thanks for the link! Should I go support that one? Because I totally agree we need it. For well known murderers, it's nice to be able to link them actively to their victims and not just passively (through queries). I frankly also don't understand the objection to the inverse-property-principle, so if you could direct me there I will go oppose that one too. Thx. Jane023 (talk) 10:00, 5 May 2015 (UTC)
I think, if an inverse property is needed (I have no strong opinion on this matter), the original proposal "killed" would be are more fitting inverse of "killed by" than "murdered". After all, the other property isn't called "murdered by" and people might also be killed by an executioner in countries that apply the death penalty (such as the U.S.) or in other cases which aren't considered murder by law. Gestumblindi (talk) 21:33, 5 May 2015 (UTC)
I'd like to see wider consensus on inverse properties; they seem to me to be redundant. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 12:01, 21 May 2015 (UTC)
It's indeed redundant information and users adding claims need to do the work twice. However, one big issue is that the software doesn't yet allow querying. To get for example the name of the person who was killed by Johan Barger (Q742496), you need the query claim[157:742496] but that is not yet supported by the software. Nevertheless, it looks like the development team is hard working on the query engine and therefore it seems to me a waste of resources to create now an inverse property. That said, I'm Symbol oppose vote.svg opposing this proposal. --Pasleim (talk) 12:19, 21 May 2015 (UTC)

Spotify artist ID[edit]

   In progress
Description identifier for an artist on Spotify
Represents Spotify artist ID (Q19884154)
Data type String
Domain persons or musical ensemble (Q2088357)
Allowed values base-62 identifier
Example Laleh Pourkarim (Q2757867) => 62QZPjYQMoo5g56FP9Webq
Source https://developer.spotify.com/web-api/user-guide/#spotify-uris-and-ids
Formatter URL https://open.spotify.com/artist/$1
Motivation

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

Discussion

Signatory[edit]

   Done: P1891
signatory
a person, country, or organization that has signed an official document (use P50 for author)
Description a person, country, or organization that has signed an official document
Data type Item
Template parameter |signers=, in en:Template:Infobox document
Domain document (Q49848) and its subclasses
Allowed values items with instance of human (Q5)
Example Declaration of Independence of the United States (Q127912) signatory: Benjamin Harrison V (Q387664), Edward Rutledge (Q878666), Benjamin Franklin (Q34969), et al.
Source item, external reference (note: this should be moved to the property statements)
Robot and gadget jobs If an inverse property is made, then a robot can check for inverse relationships
Motivation

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

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

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

turned pro[edit]

   In progress
Description year that an athlete gains professional status
Data type Time
Template parameter "turnedpro" in en:template:infobox tennis biography
Domain sportsperson (Q2066131) and its subclasses
Allowed values a year
Example Andre Agassi (Q7407) → 1986
Source the ATP or WTA website
Motivation

I don't think we have a property for this, but it's useful info. --AmaryllisGardener talk 21:14, 21 May 2015 (UTC)

Discussion

coach[edit]

   <withdrawn>
Description person that is the head coach for the sportsperson
Represents coach (Q41583)
Data type Item
Template parameter |coach=, in en:Template:Infobox tennis biography
Domain sportsperson (Q2066131)
Allowed values people
Example Sabine Lisicki (Q76338)Richard Lisicki (Q17290600)
Source ATP website, Wikipedia
Motivation

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

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

Australian Dictionary of Biography (ADB)[edit]

   In progress
Description article about the person in the Australian Dictionary of Biography (ADB)
Represents Australian Dictionary of Biography (Q672680)
Data type String
Template parameter id2 of en:Template:Australian Dictionary of Biography
Domain people
Allowed values string with [A-Z,0-1] and "-"
Example Edmund Barton (Q23342) >> barton-sir-edmund-toby-71
Source Template:Australian Dictionary of Biography (Q6703319)
Formatter URL http://adb.anu.edu.au/biography/$1
  • Pictogram voting comment.svg Comment This facilitates importing the template data from Wikipedia. --- Jura 04:56, 22 May 2015 (UTC)
Symbol support vote.svg Support --Pasleim (talk) 07:48, 22 May 2015 (UTC)

Commonwealth War Graves Commission person identifier[edit]

   In progress
Description identifier for a person, in the online database of Commonwealth War Graves Commission (Q1117074)
Data type String
Template parameter |id=, in en:Template:CWGC
Domain British Commonwealth military personnel
Allowed values valid CWGC URL stems
Example James Brindley Nicolson (Q6130229)1815716
Source CWGC website; Wikipedia
Formatter URL http://www.cwgc.org/find-war-dead/casualty/$1/
Motivation

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

Discussion