Wikidata:Property proposal/Archive/1

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

Generic / Allgemein / Général

Over 9000

  • Description: Whether indeed, this value is over 9000
  • Datatype: integer
  • Links:
  • Domain:
  • Comments: OTHER INFORMATION
 Not done KSRSLY? Sven Manguard Wha? 02:24, 5 February 2013 (UTC)
 Neutral This clearly should be a boolean, not an integer --Jeroen De Dauw (talk) 13:04, 5 February 2013 (UTC)
 Oppose Who on earth needs this? --Giftzwerg 88 (talk) 21:34, 5 February 2013 (UTC)

Image / Abbildung / Image

Status:    Done

→ Property:P18

In addition to this, we could have many more. For instance, for an animal species: photo of male, photo of female, skeleton, etc. Any idea on how to label them ? Is "male" ok, or "image of male" ? --Zolo (talk) 15:26, 3 February 2013 (UTC)
I think that "image of male" is better because "male" is ambiguous. Tpt (talk) 16:40, 3 February 2013 (UTC)
A "relevant illustration" seems too vague. Some entities are images (ex. w:Esperanto jubilee symbol). Some are things that could be photographed, or drawn. Some might be image files themselves. Some might be a specific entity that could have images of it, and some might be classes of things, and images would be of examples of it. --Yair rand (talk) 06:29, 4 February 2013 (UTC)
We can probably find a more accurate description, but I think we need a simple property that would work for Shakespeare, Barack Obama, and probably also Moscow and the Loch Ness Monster. --Zolo (talk) 08:34, 4 February 2013 (UTC)
✓ Done. Property:P18. Tpt (talk) 19:52, 4 February 2013 (UTC)
We have Property:P10 (Commons media file, AKA: picture) already. Happy chaos. --Kolja21 (talk) 20:35, 4 February 2013 (UTC)
I think that we should merge Property:P18 with Property:P10 and rename Property:P10 "Image". Tpt (talk) 20:37, 4 February 2013 (UTC)
Pro merge (delete P18), but a Commons media file can be a video, so I think the description is ok. --Kolja21 (talk) 20:51, 4 February 2013 (UTC)
On IRC there was some discussion about this; I think we should keep both P10 and P18, but encourage people to use P18 only for still images (and rename it to "image" rather than "photo"). P10 is a super-type of P18, as you say, and we should retain it for when we have that. James F. (talk) 21:07, 4 February 2013 (UTC)
If we first add the properties and then discuss how we might use them, it's better to stop phase 2 now, before someone has to do the clean up. Also the software is not ready yet. (We should test the software, improve it, think about the guidelines and than start with phase 2.) --Kolja21 (talk) 21:34, 4 February 2013 (UTC)
Software is never 'finished', it will always be changing. I don't think we should stop now just because we don't have the full set of features yet - but I agree that we should not rush too much with this, and instead discuss here. :-) James F. (talk) 22:30, 4 February 2013 (UTC)

Pronunciation

  • Description: An IPA pronunciation of the Topic
  • Datatype: StringValue
  • Links: Most Wiktionary and many Wikipedia Articles etc.
  • Comments: Would help users who do not know how to pronounce the topic. Would also help Text-to-Speech engines pronounce the topic should they ever come across it. See this for more implementation ideas. --Macadamia1472 (talk) 04:28, 3 February 2013 (UTC)
  • The main reason I propose centralising pronunciations is that one person could work out the pronunciation and then any Wikimedia project, be it Wikipedia, Wiktionary, Wikispecies, Wikivoyage etc. could use it through a template as simple as {{pronounce|WORD}}. Also this makes it possible for users to one day set a preference to see the pronunciation, if possible, under the title of each article. Centralising it in Wikidata not Wiktionary etc. also makes it easily accessible to computers programs such as Text-to-Speech engines, fulfiling one of Wikidata's goals. Also see my idea on how we can internationalise it below. --Macadamia1472 (talk) 05:35, 4 February 2013 (UTC)
  •  Support This could be used with templates such as en:Template:IPAc-en and test2wiki:Template:IPAc-en (the latter uses Lua).--Snaevar (talk) 14:44, 3 February 2013 (UTC)
  •  Neutral Helps as wikidata would provide pronunciation on all wikipedia. For example, name of person which is spoken same in all languages but need multiple entries according to different language in many case such as articles having words other than names. Example-Independence movement of India - differently written and spoken in different wikipedia of french, hindi, chinese
  • Can we do this on a language-by-language basis? Not every language uses the same term for an entity, let alone the same pronunciation. πr2 (t • c) 18:00, 3 February 2013 (UTC)
  • Different language WikiData sites have different labels, descriptions and aliases for the same Item ID so we definitely could (and should) do it separately for each language. Whilst there is a WikiData in British English facilitating dialects might require the ability to add multiple pronunciations like with aliases. In this case we would have to tag each one with a country or region; Annoying but not impossible nor necessary at the start. --Macadamia1472 (talk) 05:35, 4 February 2013 (UTC)
  • That means that if we change the label, we need to change the pronunciation. I am a bit weary of the synchronization problems that may arise. I guess we should have a "Wikidata of Words" in addition to the "Wikidata of items", or maybe we should work toward integration of omegawiki. --Zolo (talk) 09:13, 4 February 2013 (UTC)

is in

  • Description: Describes an object's relationship with another
  • Datatype: Item
  • Domain: All
  • Comments: For example, the United States is in NATO, the Mona Lisa is in The Louvre. Not to be used instead of properties such as continent Macadamia1472 (talk) 08:09, 5 February 2013 (UTC)
"is in" is too generic in my opinion. For international organisations, there should be a separate property for it like "member of". For paintings or other works of art, there should be a property called "gallery" or "collection". --Wylve (talk) 18:09, 5 February 2013 (UTC)
 Oppose Agree with Wylve, this is too general (except as a super-type, perhaps). James F. (talk) 21:21, 5 February 2013 (UTC)
 Oppose Too generic, see: Wikidata talk:Property proposal#is a. --Kolja21 (talk) 23:32, 5 February 2013 (UTC)
 Oppose Too generic.--Snaevar (talk) 13:14, 6 February 2013 (UTC)
 Not done Consensus against this. Sven Manguard Wha? 03:29, 7 February 2013 (UTC)

created by

  • Description: Links object to person (or company, organisation) who is primarily responsible for creatively producing it
  • Datatype:' Item
  • Domain: All
  • Comments: Examples: The World Wide Web was "created by" Tim Berners-Lee. The Harry Potter books were all "created by" JK Rowling etc. Tom Morris (talk) 21:19, 5 February 2013 (UTC)
    This sounds like a good idea - we might want to sub-type it for general creative works (author, editor, … as below), but I think we should go ahead with this too. James F. (talk) 21:23, 5 February 2013 (UTC)
     Oppose Too generic. Harry Potter has an author (Property:P50). We should start with a World Wide Mix, where we have to guess what the property might stands for. --Kolja21 (talk) 23:39, 5 February 2013 (UTC)
 Oppose Too generic.--Snaevar (talk) 13:14, 6 February 2013 (UTC)
 Not done Consensus against this. Sven Manguard Wha? 03:29, 7 February 2013 (UTC)

has (EN), hat (DE)

  • Description: Example: Histiophryne psychedelica "has" "binocular vision".
  • Datatype: Item, quality, whatever fits
  • Source: ?
  • Domain: Pretty much anything
  • Infobox parameter: N/A
  • Comments: Surprised this one doesn't already exist. Bob the Wikipedian (talk) 23:59, 16 February 2013 (UTC)
 Oppose To unprecise. This wont help wikidata in structuring data. --Sk!d (talk) 00:21, 17 February 2013 (UTC)
 Oppose We don't need general properties which can be used in 20 or 50 relations but specific properties. How you want to build an infobox with 10 relations based on a "has" property ? Snipre (talk) 02:03, 17 February 2013 (UTC)
 Oppose --Kolja21 (talk) 02:49, 17 February 2013 (UTC)
 Not done consensus against. Sven Manguard Wha? 05:06, 18 February 2013 (UTC)

Named after / Benannt nach (Namenspatron) / ...

Status:    Done

→ Property:P138

Exists in w:en:Template:Infobox planet. --EugeneZelenko (talk) 04:38, 16 February 2013 (UTC)
 Support --Paperoastro (talk) 23:36, 16 February 2013 (UTC)
 Support – specific examples it would be useful for: w:Coriolis effect → w:Gaspard-Gustave Coriolis, w:Pascal's triangle → w:Blaise Pascal, w:Islets of Langerhans → w:Paul Langerhans, etc. The Anonymouse (talk | contribs) 08:00, 19 February 2013 (UTC)
 Support seems logical.--Arnaugir (talk) 19:29, 19 February 2013 (UTC)
 Support --Kolja21 (talk) 19:46, 19 February 2013 (UTC)
✓ Done Property:P138. --EugeneZelenko (talk) 04:14, 23 February 2013 (UTC)

Authority control / Normdaten / Autorité

Main type of item (entity) / Art des Objekts / Type principal

Status:    Done

→ Property:P107

✓ Done Needed for templates and might help to solve the "is a" problem. --ThorstenX1 (talk) 10:52, 11 February 2013 (UTC)

Person / Person / Personne

Place of birth / Geburtsort / Lieu de naissance

Status:    Done

→ Property:P19

Place of death / Sterbeort / Lieu de décès

Status:    Done

→ Property:P20

✓ Done Property:P20. Tpt (talk) 19:55, 4 February 2013 (UTC)

Gender / Geschlecht / Genre (sexe)

Status:    Done

→ Property:P21

✓ Done Property:P21. Tpt (talk) 19:56, 4 February 2013 (UTC)

Father / Vater / Père

Status:    Done

→ Property:P22

Mother / Mutter / Mère

Status:    Done

→ Property:P25

Spouse / Ehegatte / Conjoint

Nationality country of citizenship

Status:    Done

→ Property:P27

  • Description: nationality of a person ( to which country he belong)
  • Datatype: ItemValue
  • Links:
  • Comments:--Nizil Shah (talk) 19:58, 4 February 2013 (UTC)
    That sounds like a property we should definitely have, but we need to think on how to implement this. Currently, it makes use of Q42884 and Q862086 that refer to ethnic group, not nationality. "German" or "Indian" in the purely legal sense do not seem to have items of their own, and I am not sure they can have one. Using the contry's item would make for clean semantics, but that may sound rather awkward in terms of natural language. --Zolo (talk) 20:35, 4 February 2013 (UTC)
  • ✓ Done by someone before me - Property:P27. We decided to rename it to "country of citizenship" because it's "Germany" not "German", etc. - hope that's OK. James F. (talk) 21:19, 4 February 2013 (UTC)

Sexuality/Sexual Orientation

Status:    Done

→ Property:P91

  • Description: Sexual orientation of a person. Usual Options: Heterosexual (straight), Homosexual (Gay/Lesbian), Bisexual, Asexual
  • Datatype: Item
  • Links:
  • Domain: Person
  • Comments: Reedy (talk) 00:34, 5 February 2013 (UTC)
 Oppose In some cases this might be of general interest, normally it's none of your business. --Kolja21 (talk) 06:31, 5 February 2013 (UTC)
I disagree. If someone has publicly stated their sexual orientation, why should we not include it? Legoktm (talk) 17:12, 5 February 2013 (UTC)
 Oppose "private property"! Wikidata is not yellow press, the same with length, diameter, cup size, how often... Whoever edits a box about a person will feel urged to make a statement about sexual orientation, even if there is no public source about it.--Giftzwerg 88 (talk) 17:34, 5 February 2013 (UTC)
 Oppose With personal data we must be very careful. For instance, the sexual orientation is an issue on which researchers do not have a consensus if it is a valid classification at all. It is a bit like race, but more complex. --Teemu (talk) 10:25, 6 February 2013 (UTC)
 Support Sexual orientation is a perfectly valid thing to include in Wikidata if there are clear sources to say someone self-identifies a particular way. And there are a lot of people for whom their sexual orientation is an important matter. Is it "yellow journalism" to say Harvey Milk is gay? Perhaps it's intrusive to say Martin Luther King is black or that the Pope is a Catholic. Tom Morris (talk) 20:25, 5 February 2013 (UTC)
Where do we need this info? At least not in Wikipedia, because it's not encyclopedia material, just trivia. --Stryn (talk) 20:31, 5 February 2013 (UTC)
In some cases, like those cited by Tom Morris, those are indeed key things to undertand what makes the pesron important. What bugs me is: where should we stop ? And I am afraid this is something of a cultural matter. For instance, many infoboxes in English Wikipedia include religion or ethnicity, while that would sound rather out of place to many French people. --Zolo (talk) 20:41, 5 February 2013 (UTC)
It isn't just "trivia", any more than the Pope's religion is trivia. There are a large number of categories on English Wikipedia which are based around a person being LGBT. It's of interest to people in gender and queer studies to be able to locate, say, lesbian writers or gay filmmakers. For some individuals, their sexual orientation is of trivial importance, for other people it is of great importance and is, like race or religion or national origin, something which profoundly shapes their character, interests, self-understanding, social role, beliefs and career. You can't understand Derek Jarman or Peter Tatchell unless you understand that they are gay. You can't understand the life of Alan Turing unless you deal with the fact that he was convicted of and punished for being gay. Tom Morris (talk) 20:56, 5 February 2013 (UTC)
 Support No more prone to abuse than any number of properties. It'd have to have a description like "the sexual orientation of the subject IF AND ONLY IF they have stated it themselves, unambiguously, or it has been widely agreed upon by historians after their death", but, I don't see any problem with such a property in general. — PinkAmpers&(Je vous invite à me parler) 20:51, 5 February 2013 (UTC)
Just wait the extension of the referencing to create that property and then delete every entry which doesn't have a reference. Snipre (talk) 21:00, 5 February 2013 (UTC)
 Oppose At this stage, is this really the piece of information the general support for the project needs to be tested with? I do understand the cultural value of the information, but I oppose to the quantification offered by storing it. --Susannaanas (talk) 11:17, 6 February 2013 (UTC)
✓ Done Created using PinkAmpersand's wording. James F. (talk) 21:01, 5 February 2013 (UTC)
I'm drawing up some proposed guidelines on the talk page, and will post again here to invite everyone to dicuss, once I'm done with them. — PinkAmpers&(Je vous invite à me parler) 21:24, 5 February 2013 (UTC)
Actually, if you really want to undertand someone, you will probably read a real text about him. Just seeing in a database that Alan Turing was gay will not carry you very far. I suppose this kind of property is more useful for data-mining or things like that. --Zolo (talk) 21:08, 5 February 2013 (UTC)

I've posted some proposed usage guidelines at Property talk:P91, and invite all of you to comment. Thanks. — PinkAmpers&(Je vous invite à me parler) 21:54, 5 February 2013 (UTC)

Member of sports team

Status:    Done

→ Property:P54

Former member of sports team

Ancestral home / Herkunftsort / Lieu d'origine

Status:    Done

→ Property:P66

✓ Done As a basic property for Chinese people, I think creating this property is uncontroversial, therefore I've already created it -- Property:P66. Let me know if you have any comments.--Stevenliuyi (talk) 07:39, 5 February 2013 (UTC)
This is an international project. Please add first the translations. --Kolja21 (talk) 07:45, 5 February 2013 (UTC)
I added English translation. Sorry that I don't have the ability to add other translations. en:Ancestral home (Chinese) has more information about this property.--Stevenliuyi (talk) 08:04, 5 February 2013 (UTC)
Thanks, if seen this article but unfortunately there is no German and no Frensh translation. Literally it's "Stammsitz" in German, but I don't know if this is correct. --Kolja21 (talk) 08:26, 5 February 2013 (UTC)
I wonder if there is a good translation. en:wp says: "A subjective concept (...)" At least "Stammsitz" is a real pace, maybe a castle. Therefore, this is a chinese thing and "Ancestral home" (en) is imho only half right. --Goldzahn (talk) 14:07, 5 February 2013 (UTC)
I looked it up in a dictionary (Chinesisch-Deutsches Universalwörterbuch by Wilfried Fuchsenberger), the corresponding entry is (I don't know German, I just type it): "j-s Heimat f, j-s Herkunft(sort) f(m)." Hope this would help.--Stevenliuyi (talk) 16:00, 5 February 2013 (UTC)
Thanks, than "Herkunftsort" is correct. ("Heimatsort" is a place someone will or hopes to return.) --Kolja21 (talk) 06:46, 6 February 2013 (UTC)

Occupation / Tätigkeit / Profession

Status:    Done

→ Property:P106

  • Description: Occupation of a person
  • Datatype: Item
  • Links:
  • Comments: Basic info
Note: see also Property:P101 (field of work). SPQRobin (talk) 23:07, 8 February 2013 (UTC)
✓ Done --ThorstenX1 (talk) 11:20, 10 February 2013 (UTC)

Native Language

Status:    Done

→ Property:P103

  • Description: the native language of a person
  • Datatype: item
  • Links: LINKS TO EXISTING VOCAULARIES THAT CONTAINS A SUCH PROPERTY
  • Domain: Person
  • Comments: (especially useful for writers)

--Hsarrazin (talk) 20:51, 5 February 2013 (UTC)

Support, and "known languages" (as in: foreign languages the person speaks fluently) is useful too, like our Babel. SPQRobin (talk) 23:07, 7 February 2013 (UTC)
✓ Done Property:P103 --Stevenliuyi (talk) 13:15, 8 February 2013 (UTC)
I would like to ask for a chance. This shouldn't be a single value constraint for people who were brought up bilingual have two native languages. Take me for example I have two native languages French and Dutch Jhowie Nitnek 10:56, 24 March 2021 (UTC)
Hm, I would have preferred just one property for all languages a person speaks, using qualifiers to provide the level of expertise (basic/advanced/fluent/native). Also, this just simply point to a Wikidata item, not an external vocabulary, I think - we should have items for pretty much every language... -- Duesentrieb (talk) 13:36, 8 February 2013 (UTC)
That would indeed be better, once we can set such qualifiers. SPQRobin (talk) 23:09, 8 February 2013 (UTC)

member of political party

Status:    Done

→ Property:P102

  • Description: The political party a person is a member
  • Datatype: Item
  • Links:
  • Domain: People
  • Infobox parameter example:
  • Comments: Would not include 'Republican' if they support Republican ideas, must be affiliated with the actual party. The party they voted for is also insufficient.Macadamia1472 (talk) 08:56, 6 February 2013 (UTC)

half-brother / Halbbruder / demi-frère

  • Description: To denote blood siblings of only one common parent (e.g., same mother, different fathers)
  • Datatype: Item
  • Links: Wikidata:List_of_properties#Relationships already has similar properties of step-father and step-mother
  • Domain: Person
  • Infobox parameter example:
  • Comments: If half-brother is accepted, then we should also create half-sister and possibly step-sister, step-brother and step-child (to compliment the already existing step-father, step-mother and child). I'm new to wikidata so I don't know if I have to create a new suggestion for each of those properties. I also don't know how fine grained properties should be, one can more specifically be a paternal half-sibling (same father) or maternal half-sibling (same mother), so they may be preferred instead of the more generic term. /Ch1902 (talk) 21:48, 6 February 2013 (UTC)
Oppose. See discussion in talk page. Snipre (talk) 15:42, 7 February 2013 (UTC)

Signature

Status:    Done

→ Property:P109

✓ Done Property:P109 --Stevenliuyi (talk) 08:58, 14 February 2013 (UTC)

Place of burial (grave) / Begräbnisort / Lieu d'enterrement

Status:    Done

→ Property:P119

  • Description: Place where a person is buried
  • Datatype: Item
  • Links: Q1526 We know where he was and is burried.
  • Infobox parameter example:
  • Comments: Property used by biographical infoboxes only if it is different from place of death. It can replace place of death if it is unknown.--Giftzwerg 88 (talk) 11:47, 3 February 2013 (UTC)
 Support Used in en:Template:Infobox_royalty. /Ch1902 (talk) 11:18, 14 February 2013 (UTC)
 Support --Viscontino talk 17:01, 14 February 2013 (UTC)
 Support --Kolja21 (talk) 02:56, 17 February 2013 (UTC)
✓ Done Created as Property:P119 Sven Manguard Wha? 05:11, 18 February 2013 (UTC)

Other family relationships: Mother-in-law, father-in-law, great-grandparent, great-uncle, great-aunt, half-brother, half-sister, aunt

 Oppose If you have the direct relationships you don't need to create the full list of possible relationship: an aunt can be defined as the sister of the mother/father. It is simplest to create a code which will be able to extract the data and to build a whole set of relations instead of managing for each person a list of 10-70 possible relations. Snipre (talk) 02:07, 17 February 2013 (UTC)
We won't always know details of the various linking relatives, e.g. for historical figures or fictional people. I'm also not convinced that deriving various relationships would be as simple as you seem to think, even with fairly complete data. Dates may be important; e.g. is my sister's ex-husband my child's (ex-)uncle, if they were divorced before my child's birth? --Avenue (talk) 18:06, 17 February 2013 (UTC)
In that case a property called "nondirect relationship" with a qualifier describing the nature of the relationship is enough. Snipre (talk) 18:14, 17 February 2013 (UTC)
 Oppose --Kolja21 (talk) 02:57, 17 February 2013 (UTC)
 Oppose -- enhancement of irrelevant or allmost useless information giving little or no benefits to the described person. Has also to be maintained and proofed.--Giftzwerg 88 (talk) 12:49, 17 February 2013 (UTC)
 Not done consensus against. Sven Manguard Wha? 05:12, 18 February 2013 (UTC)

Stepchild

 Oppose Not used in infoboxes. --Kolja21 (talk) 17:44, 17 February 2013 (UTC)
They are present in infoboxes, as in the linked example. Would you prefer we record them as children, with a qualifier indicating they are stepchildren? --Avenue (talk) 18:16, 17 February 2013 (UTC)
This would be a good solution. --Kolja21 (talk) 18:27, 17 February 2013 (UTC)
 Oppose, on the grounds that Property:P40 (child) will handle this once qualifiers are implemented. --Avenue (talk) 21:28, 17 February 2013 (UTC)
 Not done consensus against Sven Manguard Wha? 05:13, 18 February 2013 (UTC)

employer / Arbeitgeber / employeur (P108)

Status:    Done

→ Property:P108

  • Description: Person was at some point employed by this business, and received salary
  • Datatype: Item
  • Links:
  • Domain: Corporations, businesses, schools, theatre,
  • Comments:
Used by any infobox? --Kolja21 (talk) 22:45, 13 February 2013 (UTC)
Infobox "person" has a category "occupation" which lists businesses a person has been working at, and positions at which a he/she has worked. The position should be a qualifier of this property, as well as the time when he/she worked there. Janjko (talk) 23:22, 13 February 2013 (UTC)
 Support --Viscontino talk 17:05, 14 February 2013 (UTC)
 Support if renamed Employer, since en:template:infobox person has a parameter named "Employer". Mange01 (talk) 18:41, 18 February 2013 (UTC)
Changed. Sven Manguard Wha? 18:51, 18 February 2013 (UTC)
✓ Done Item was created a week ago by Janjko. --Kolja21 (talk) 15:27, 19 February 2013 (UTC)

Religion

Status:    Done

→ Property:P140

  • Wikipedia only requires that it be supported by reliable sources. It doesn't add the 2nd criterion of it being "important in his or her career." As Wikidata is intended to supply data to Wikipedia, I don't see how we can have more restrictive criteria than they do? Shawn in Montreal (talk) 19:21, 23 February 2013 (UTC)
Thank you! "career" was not the most proper word - I thought of saints and bishops, for instance. --Eric-92 (talk) 04:20, 24 February 2013 (UTC)

Organization / Organisation / Organisation

Member state / Gliedstaat / État membre (P100)

  • Description: states participating in an international organisation
  • Datatype: item
  • Links: w:Member_state
  • Infobox parameter example:
  • Comments: I was a bit too enthusiastic and didn't know I had to propose it first :) I think it's quite obvious, the only issue I think is whether states of a federal country (German Länder, US states, ...) should have a separate property or not. SPQRobin (talk) 22:21, 7 February 2013 (UTC)

Founder / Gründer / Fondateur

Status:    Done

→ Property:P112

  • Description: Who created the organization
  • Datatype: Item
  • Links:
  • Infobox parameter example:
  • Comments: A Founder can be a country, city, person, another organization
This seems a duplicate of the one above. Or is it WHO created the organisation? Reedy (talk) 02:09, 5 February 2013 (UTC)
I changed the description. --Stryn (talk) 07:32, 5 February 2013 (UTC)
 Support --Чаховіч Уладзіслаў (talk) 15:54, 10 February 2013 (UTC)
 Support --Viscontino talk 17:06, 14 February 2013 (UTC)
✓ Done. Property:P112 --Goldzahn (talk) 00:32, 17 February 2013 (UTC)

Official website

Status:    Done

→ Property:P856

See here. There is already an approved request for this. There for ✓ Done --Sk!d (talk) 00:50, 17 February 2013 (UTC)
I don't find that property. The only similar thing I find is stated in and imported from. Mange01 (talk) 20:47, 17 March 2013 (UTC)

Airlines

Hubs

Status:    Done

→ Property:P113

✓ Done Property:P113 --Goldzahn (talk) 04:25, 17 February 2013 (UTC)

Destinations

aircraft in fleet

Status:    Done

→ Property:P121

Airport lounge

Airline Alliance

Status:    Done

→ Property:P114

✓ Done Property:P114 --Goldzahn (talk) 04:51, 17 February 2013 (UTC)

Work / Werk / Œuvre

Art / Kunst / Art

Commissioner / Kommittent / Commanditeur (mécène)

Status:    Done

→ Property:P88

✓ Done Property:P88. Let me know if you have any comments. --Appo92 (talk) 08:44, 6 February 2013 (UTC)

Literature / Literatur / Littérature

Author / Autor / Auteur (P50)

Status:    Done

→ Property:P50

Editor / Herausgeber / Éditeur (P98)

Status:    Done

→ Property:P98

Illustrator / Illustrator / Illustrateur

Status:    Done

→ Property:P110

 Support --Чаховіч Уладзіслаў (talk) 15:52, 10 February 2013 (UTC)
✓ Done Property:P110--Hosiryuhosi (talk) 10:46, 15 February 2013 (UTC)

Publisher / Verlag / maison d'édition

Status:    Done

→ Property:P123

✓ Done as P123 Sven Manguard Wha? 20:54, 18 February 2013 (UTC)

Music / Musik / Musique

Composer / Komponist / Compositeur

Status:    Done

→ Property:P86

✓ Done Property:P86. Let me know if you have any comments. --Appo92 (talk) 08:45, 6 February 2013 (UTC)

Librettist / Librettist / Librettiste

Status:    Done

→ Property:P87

✓ Done Property:P87. Let me know if you have any comments. --Appo92 (talk) 08:44, 6 February 2013 (UTC)

Film / Film / Film

Youtube Subscribers

  • Description: How many subscribers a youtube channel has
  • Datatype: Media?
  • Source: none
  • Domain: youtube channels
  • Infobox parameter: none
  • Comments: none
 Oppose Changes to much, is no indicator for anything (Fakeaccounts). Conny (talk) 09:46, 21 February 2013 (UTC).
 Oppose As above Snipre (talk) 09:57, 21 February 2013 (UTC)
 Oppose Danrok (talk) 20:17, 21 February 2013 (UTC)
 Oppose Kolja21 (talk) 20:09, 22 February 2013 (UTC)

Based on

Status:    Done

→ Property:P144

 Support Used by en:Template:Infobox film. --Kolja21 (talk) 00:14, 13 February 2013 (UTC)
 Support More exhaustively, the information can be extracted via {{based on}} (3529 transclusions) for films. --whym (talk) 10:02, 18 February 2013 (UTC)
So should we create a Template:Has inspired property for books that are the base for movies? --Aubrey (talk) 09:30, 21 February 2013 (UTC)
Works that have inspired or been adapted as other works has certainly has emerged as a category structure at English Wikipedia, however I don't believe it corresponds to any template field. Shawn in Montreal (talk) 19:57, 21 February 2013 (UTC)
 Support Let's get some non-controversial properties made. Espeso (talk) 05:36, 24 February 2013 (UTC)
 Support Danrok (talk) 14:39, 24 February 2013 (UTC)
✓ Done Property:P144. --EugeneZelenko (talk) 14:45, 24 February 2013 (UTC)

Term / Sachbegriff / Terme

Astronomical objects

astronomical object

  • Description: Type of astronomical object: star, comet, asteroid, etc.
  • Datatype: Item
  • Links:
  • Comments:
Is this a duplicate of Property:P31? --Beta16 (talk) 08:30, 5 February 2013 (UTC)
probably yes, it would be used Property:P31... --Paperoastro (talk) 09:00, 5 February 2013 (UTC)
 Not done duplicate property --Paperoastro (talk) 11:26, 12 February 2013 (UTC)

constellation / sternbild / constellation

Status:    Done

→ Property:P59

✓ Done Property:P59. --Paperoastro (talk) 20:54, 10 February 2013 (UTC)

discovered by / entdeckt von / découverte par

Status:    Done

→ Property:P61

 Support -- MichaelSchoenitzer (talk) 01:19, 9 February 2013 (UTC)
 Support although this could be generalised for non-astronomical objects as well. πr2 (t • c) 16:37, 9 February 2013 (UTC)
✓ Done Property:P61. --Paperoastro (talk) 13:27, 13 February 2013 (UTC)

site of astronomical discovery / / lieu de découverte

Status:    Done

→ Property:P65

 Support --Paperoastro (talk) 22:06, 6 February 2013 (UTC)
 Support same as above comment. πr2 (t • c) 16:37, 9 February 2013 (UTC)
 Comment some users changes label and description following your suggestion. --Paperoastro (talk) 00:07, 13 February 2013 (UTC)
✓ Done Property:P65. --Paperoastro (talk) 00:07, 13 February 2013 (UTC)

natural satellite / natürlicher Satellit / satellite naturel

Status:    Done

→ Property:P96

 Support -- MichaelSchoenitzer (talk) 01:19, 9 February 2013 (UTC)

Planets / Planeten / Planètes

Status:    Done

→ Property:P99

  • Description: Planets that orbit around a star (valid both for solar system and for extrasolar planets)
  • Datatype: Item
  • Links:
  • Comments:
Can be combined with natural satellites? Within the meaning is the same. Additionally companion star may be not only the planets. --Art-top (talk) 19:34, 7 February 2013 (UTC)
I created this property, but I'm agree to combine it with natural satellite to create a more general property that comprehends satellite, planets and stars. We need only the right name... --Paperoastro (talk) 19:47, 7 February 2013 (UTC)
 Support Don't see the need to unify "Planet" and "Moon", there are enough of both, and much more in near future. -- MichaelSchoenitzer (talk) 01:19, 9 February 2013 (UTC)
 Support I'm sorry, but I changed my opinion: natural satellites and planets have precise and different definitions and, in my opinion in the future manage query and bot with different and clear-defined properties will be more simple. --Paperoastro (talk) 11:19, 9 February 2013 (UTC)
 Support Planets [in our Solar System] have a specific definition by the IAU, but we could still have some kind of "in orbit around" property. Also support for exoplanets, unless someone thinks they should be separate. πr2 (t • c) 16:37, 9 February 2013 (UTC)

Host galaxy

Status:    Done

→ Property:P116

I chose "galaxy" since that seems to be the form of other entries here, such as for "country". But indeed, whether or not "host" is added should not matter much, except from perhaps clarity. Njardarlogar (talk) 23:29, 14 February 2013 (UTC)
✓ Done --Paperoastro (talk) 11:40, 17 February 2013 (UTC)

Biology / Biologie / Biologie

Physically Interacts With (molecular biology)

  • Description: This property may be used to describe relationship between two physical entities.
  • Datatype: Item
  • Links: http://purl.obolibrary.org/obo/INO_0000026
  • Domain: Protein, Gene
  • Infobox parameter example:
  • Comments: This property is primarily intended to be used to establish relationships between gene topics. For example, connecting Cyclin-dependent_kinase_2 with interaction partner CEBPA based on evidence http://www.ncbi.nlm.nih.gov/pubmed/11684017
Any idea how to make the label more specific ? I fear that a property with such a vegue name will often be misused.--Zolo (talk) 12:56, 10 February 2013 (UTC)
There could be many more specific sub-properties. Binds_to, Phosphorylates, degrades, etc. Is their a pattern for grouping related properties like these together?Genewiki123 (talk) 21:52, 11 February 2013 (UTC)

Taxon rank

Status:    Done

→ Property:P105

  • Description: taxonomical rank, e.g. species, genus, family...
  • Datatype: StringValue
  • Links:
  • Infobox parameter example:
  • Comments: Datatype could be Item(s)?
 Support - Datatype should be items IMO. It's either going to be this property, or the over-use of "is a". Personally I would prefer the former.-Soulkeeper (talk) 17:20, 8 February 2013 (UTC)

IUCN Red List Classification / /

Status:    Done

→ Property:P141

  • Description: The IUCN Red List Classification for organisms listed in the list. The value of the property should be the most updated one published by IUCN, using the most updated status system possible. Every status has an item.
  • Datatype: Item
  • Links:
  • Infobox parameter example: w:Template:Taxobox
  • Comments: --Wylve (talk) 17:17, 19 February 2013 (UTC)
 Support Very important for all livingforms. Conny (talk) 09:42, 21 February 2013 (UTC).

 Support Danrok (talk) 20:18, 21 February 2013 (UTC)

 Support and created as Property:P141. Espeso (talk) 05:55, 24 February 2013 (UTC)

Languages / Sprachen / Langues

Language family / Sprachfamilie / Langues par famille (P133)

Status:    Done

→ Property:P133

  • Description: The classification of a language
  • Datatype: Item
  • Links:
  • Infobox parameter example:
  • Comments: The full classification could be calculated through the specific class of the language to its class and so on.
Datatype should be "item", shouldn't it ?
I would think so. --Yair rand (talk) 06:08, 4 February 2013 (UTC)
Fixed. Ebe123 (talk) 20:59, 4 February 2013 (UTC)
 Support --Kolja21 (talk) 22:23, 21 February 2013 (UTC)

Dialect / Dialekt / Dialecte (P134)

Status:    Done

→ Property:P134

  • Description: dialect of the language
  • Datatype: Item
  • Links:
  • Infobox parameter example:
  • Comments: Might contain more than 1 item (i.e. list)

Place

Coat of arms image // Armoiries

Status:    Done

→ Property:P94

✓ Done Property:P94

Anthem description / Nationalhymne / Hymne national

Status:    Done

→ Property:P85

I think it would be better to just have a property anthem with a link to the item about the anthem. In that item you then can add the description, melody, composer etc. --Blackpen (talk) 13:18, 6 February 2013 (UTC)
This is sorted. We have Anthem, which I would hesitate to call "description"--by implication "anthem" means "title of anthem". The value itself is not a string containing a description. And the original property Property:P48 was a media type, so the description was changed to "anthem recording". This pattern should be followed with the other items like coat of arms, etc., that can have both an item link and an image. Espeso (talk) 16:16, 6 February 2013 (UTC)
✓ Done It was already created, and I am moving it from the "added without discussion" section, since we had some discussion here, and no objections.--Ymblanter (talk) 17:35, 7 February 2013 (UTC)

Antarctic Claim

Email / /

Generic

Country / Staat / Pays

Status:    Done

→ Property:P17

Note: was created as Property:P17. SPQRobin (talk) 23:23, 8 February 2013 (UTC)

Municipality / Gemeinde/ Commune

Status:    Done

→ Property:P68

Already done: Property:P68. --Stryn (talk) 07:58, 8 February 2013 (UTC)

Capital / Hauptstadt / Capitale

Status:    Done

→ Property:P36

  • Description: Capital of a Country, Province, Largest Area of a Place
  • Datatype: Item
  • Links:
  • Infobox parameter example:
  • Comments: I was thinking of making this Capital City but to make it applicable to a provice or other geographical item, just capital.Napoleon.tan (Napoleon.tan)
    • This would be confusing. It some city os the capital of X, which level is it capital of? I think thre should be a property for each level. So Washington is a national capital, La Plata is the capital city of level 1 Buenos Aires province, some city is the capital of some level 2 county, and so on.--NaBUru38 (talk) 21:44, 8 February 2013 (UTC)

Note: was created as Property:P36. SPQRobin (talk) 23:25, 8 February 2013 (UTC)

    • But which administrative level does P36 refer to? For example, Paris is the capital of both Île-de-France and France. That's why I think there should be several capital city properties. --NaBUru38 (talk) 15:05, 9 February 2013 (UTC)
    Each state, region, province, département... has its capital (sometimes called chef-lieu in french). Could you explain better what the problem is? Thanks.--Eric-92 (talk) 23:29, 9 February 2013 (UTC)
    • Ohe, now I understand that this property means "the capital city of the item is Y". I think that there should be symmetric properties, like, "this item is the capital city of France" and "this item is the capital city of Île-de-France". --NaBUru38 (talk) 14:39, 13 February 2013 (UTC)

Ward / - / -

  • Description: an administrative jurisdiction or subdivision in any of various countries and within some international
  • Datatype: Item
  • Links:
  • Infobox parameter example:
  • Comments: Used to specify sub division of a prefecture in geo in Japan
Oppose. Wait for a global structure for administrative division. Snipre (talk) 15:48, 7 February 2013 (UTC)

Prefecture / - / -

  • Description: an administrative jurisdiction or subdivision in any of various countries and within some international
  • Datatype: Item
  • Links:
  • Infobox parameter example:
  • Comments: Used to specify locations on countries such as Japan. Example of use Tokyo Station
Oppose. Wait for a global structure for administrative division. Snipre (talk) 15:47, 7 February 2013 (UTC)

Map / /

Status:    Done

→ Property:P15

  • Description: link to map file
  • Datatype: Commons media file
  • Links:
  • Infobox parameter example:
  • Comments:

Exists as Property:P15 JAn Dudík (talk) 12:05, 20 February 2013 (UTC)

Country / Land / Pays

Type of government / Regierungsform / Régime politique (P122)

Status:    Done

→ Property:P122

 Support Used in infobox. (Better than <Canada> is a <sovereign state>.) --ThorstenX1 (talk) 06:10, 10 February 2013 (UTC)
✓ Done --Kolja21 (talk) 19:32, 18 February 2013 (UTC)

top-level domain / Top-Level-Domain / Domaine internet (P78)

Status:    Done

→ Property:P78

  • Description: top-level domain for the country, territory, or organization
  • Datatype: item
  • Links:
  • Infobox parameter example:
  • Comments: already created; I am organizing the discussion so that if there are no objections, I am going to move the item from the category "Added without discussion"--Ymblanter (talk) 17:40, 7 February 2013 (UTC)

Note: was created as Property:P78. SPQRobin (talk) 23:27, 8 February 2013 (UTC)

type of administrative division

Status:    Done

→ Property:P132

  • Description: type of administrative division
  • Datatype: item
  • Links: Property:P132
  • Infobox parameter example:
  • Comments: ✓ Done following various disussions.

Roads / Straßen / routes

Highway shield / Straßenschild / cartouche

Status:    Done

→ Property:P14

✓ Done as non-controversial. --Rschen7754 19:43, 4 February 2013 (UTC)

Map / Karte / carte

Status:    Done

→ Property:P15

✓ Done as non-controversial. --Rschen7754 19:43, 4 February 2013 (UTC)

Highway system / Straßennetz / réseau routier

Status:    Done

→ Property:P16

Changed to "highway system". --Rschen7754 19:33, 4 February 2013 (UTC)
✓ Done as non-controversial. --Rschen7754 19:43, 4 February 2013 (UTC)

Maintenance / Betreiber / entretien

Status:    Done

→ Property:P126

Status:    Done

→ Property:P127

I will be creating both within the next day if there's no further objections. --Rschen7754 21:48, 4 February 2013 (UTC)

This is needed for every road individually? There aren't just maintenance organizations for large regions? --Yair rand (talk) 11:44, 7 February 2013 (UTC)
Yes, because not every road is maintained by the same government agency. --Rschen7754 20:49, 11 February 2013 (UTC)
✓ Done both. --Rschen7754 03:47, 19 February 2013 (UTC)
Both = road maintenance (Property:P126) and road owner (Property:P127). --Kolja21 (talk) 14:08, 19 February 2013 (UTC)

Would not it be better to use generic "owner" and "maintainer" properties, not these road specific? There was "road mainteiner" property with "Wikimedia Foundation" as value added to Wikipedia article (now removed). Which made me think of this. --Papuass (talk) 09:36, 21 February 2013 (UTC)

Buildings and structures / Gebäude/ bâtiments

Architect / / Architecte

Status:    Done

→ Property:P84

Architect isn't the good term because for some infrastructures we can have engineers, soldiers or civil servants. Conceptors or something like that would be better141.6.11.15 12:58, 4 February 2013 (UTC)
Architect is different from engineer, we should create both properties --Appo92 (talk) 18:20, 5 February 2013 (UTC)
It is dependent of the building: often bridges or building like Eiffel tower are designed by engineers who are doing the job of architect. It's different, but the job is often the same, so conceptor can be a trade-off. Snipre (talk) 15:31, 7 February 2013 (UTC)
 Support --Чаховіч Уладзіслаў (talk) 15:49, 10 February 2013 (UTC)

Architectural style / Baustil / Style

Status:    Done

→ Property:P149

 Support --Чаховіч Уладзіслаў (talk) 15:49, 10 February 2013 (UTC)
 Support Should have the label "Architectural style" (= infobox). --Kolja21 (talk) 17:45, 19 February 2013 (UTC)
 Support "Architectural style" --Faux (talk) 21:03, 19 February 2013 (UTC)
 Comment. Is there any point in making that specific to architecture ? Why not a general-purpose "aesthetic style" property that would apply to artworks, novels, etc. --Zolo (talk) 18:14, 20 February 2013 (UTC)
But wouldn't it get confusing, as there are distinct articles for "modernism" as related to architecture, music, visual arts and literature, per en:Modernism (disambiguation)? This is so for a quite a few other movement/style terms. Shawn in Montreal (talk) 18:41, 20 February 2013 (UTC)
A building should be set to "modernism (architecture)" and a novel to "modernim (literature)" regardless of the properties we should. Having different properties for different kinds of art may make it easier for bots to resolve disambiguation, but I think they can manage it without that. --Zolo (talk) 20:02, 20 February 2013 (UTC)
 Support Danrok (talk) 20:04, 21 February 2013 (UTC)
 Support If clear descriptions will allow users or bots to distinguish the various "isms", great. Shawn in Montreal (talk) 20:17, 21 February 2013 (UTC)
✓ Done as P:149 Sven Manguard Wha? 17:38, 24 February 2013 (UTC)

Trains

Line / / Ligne de train

Status:    Done

→ Property:P81

  • Description: The Line where the train station belongs to
  • Datatype: Item
  • Links:
  • Infobox parameter example:
  • Comments: Example of use Tokyo Station
 Support-- DangSunM (T · C) 21:16, 7 February 2013 (UTC)
 Support--Incola (talk) 19:58, 10 February 2013 (UTC)

Operator / Betreiber / ...

Status:    Done

→ Property:P137

  • Description: Companies which operate the services. For example, JR East for Yamanote Line.
  • Datatype: Item
  • Links:
  • Domain: Infrastructure, service
  • Infobox parameter example:
  • Comments:

Kwj2772 (talk) 17:47, 13 February 2013 (UTC)

 Support --Kolja21 (talk) 20:04, 13 February 2013 (UTC)
 Support --Faux (talk) 18:55, 18 February 2013 (UTC)
✓ Done Kwj2772 (talk) 12:08, 22 February 2013 (UTC)

Event / Ereignis / Évènement

Sports related

League / Liga / ligue

Status:    Done

→ Property:P118

Retrieved from "https://www.wikidata.org/w/index.php?title=Wikidata:Property_proposal/Archive/1&oldid=1388777965"