Shortcut: WD:PP/GEN

Wikidata:Property proposal/Generic

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:ListProperties.
  2. Check if the property is already pending or has been rejected.
  3. Check if you can give a similar label and definition as an existing Wikipedia infobox parameter, or if it can be matched to an infobox, to or from which data can be transferred automatically. See WD:WikiProject Infoboxes for suggestions.
  4. Select the right datatype for the Property.
  5. Start writing the documentation based on the preload form below and add it in the appropriate section.

Creating the property

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

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          = <!-- for external identifiers, URL pattern where $1 replaces the value -->
|filter                 = (sample: 7 digit number can be validated with edit filter [[Special:AbuseFilter/17]])
|robot and gadget jobs  = Should or are bots or gadgets doing any task with this? (Checking other properties for consistency, collecting data, etc.)
}}

;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


Generic properties[edit]

language, except for works or persons[edit]

   In progress
Description language of item. Use more specific properties language of work (or name) (P407) or original language of work (P364) for works and native language (P103) or languages spoken or published (P1412) for persons.
Data type Item
Domain any item that has or uses a language except works or persons, like names, words, phrases, proverbs.
Allowed values items for languages
Example


Jean (Q4160311), female given name → English (Q1860)
Jean (Q7521081), male given name → French (Q150)
Robot and gadget jobs no persons and no works of any kind allowed.
Discussion
  • Pictogram voting comment.svg Comment P:P364 used to have the label "language". To match more closely its description, it's now labelled "language of the original work". This leaves a gap for cases like the above. --- Jura 04:52, 12 December 2014 (UTC)
  • Symbol support vote.svg Support --- Jura 04:52, 12 December 2014 (UTC)
  • Symbol support vote.svg SupportPictogram voting comment.svg Comment One day we will have also wictionary linked, so every word must have a language. Not only names, but also radio/tv stations broadcast in languages. However names are a bad example, because names tend to move between languages, sometimes unchanged over centuries and sometimes more or less modified.--Giftzwerg 88 (talk) 05:14, 12 December 2014 (UTC)
Pictogram voting comment.svg Comment I changed the domain to "any". --- Jura 05:16, 12 December 2014 (UTC)
In that discussion User:Snipre came up with the idea to merge language of work (or name) (P407) and original language of work (P364) into a "language" property which would no longer be restricted to works. --Pasleim (talk) 12:56, 18 April 2015 (UTC)
I don't see that discussion going anywhere, nor is the merge proposal formulated that way. The result is that we still haven't sorted out this issue. --- Jura 13:03, 18 April 2015 (UTC)
@Jura1, Pigsonthewing: Agree, it might take some time until there is a consensus so I won't oppose the creation of this property. --Pasleim (talk) 09:21, 19 April 2015 (UTC)

Time2wait.svg On hold per Pasleim. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 12:02, 18 April 2015 (UTC)

  • That other two properties have just no impact on this. --- Jura 12:05, 18 April 2015 (UTC)
    • @Pigsonthewing: I removed "on hold" as Pasleim changed is comment. --- Jura 15:48, 20 April 2015 (UTC)
    @Jura: Please try to think to that possibility: language of work (or name) (P407) and original language of work (P364) merged into a new property called "language" ? Why do we have to have one property "language of work" and one property "language of name" ? Snipre (talk) 13:57, 20 April 2015 (UTC)
    The reason for this request is that someone changed the label of the P364. --- Jura 15:46, 20 April 2015 (UTC)
  • Symbol support vote.svg Support. The specialised properties are worth having but it is good to have this more general property for cases where those don't apply. Filceolaire (talk) 17:55, 18 June 2015 (UTC)
  • Symbol oppose vote.svg Oppose. We don't need specific properties, even two is too much. Single "language" property is enough. P364 shall be merged with P407 to such single property. -- Vlsergey (talk) 16:08, 26 June 2015 (UTC)
  • Symbol oppose vote.svg Oppose. Agree with Vlsergey here. One language property is enough for works and other items. It's different for people who need to differentiate native language and other spoken languages. --Hsarrazin (talk) 17:53, 1 August 2015 (UTC)


(Disjoint)UnionOf (or any better name)[edit]

   In progress
Description every instance of this class is an instance of at least/exactly one class in that list of classes
Data type Item
Domain list, or metaclass
Allowed values class list, or metaclass list (resp)
Example
< nucleon (Q102165) (View with Reasonator) > Disjoint union of search < proton (Q2294) (View with Reasonator) >
together with search < neutron (Q2348) (View with Reasonator) >
Format and edit filter validation (sample: 7 digit number can be validated with edit filter Special:AbuseFilter/17)
Robot and gadget jobs check consistency of the instantiation relation wrt. these statements
Note
This proposal is a proposal for Two properties:
  • UnionOf
  • DisjointUnionOf
(to get the definition of the first, take the text in green, resp in red for the second) plus one new qualifier :
  • Together With.
Motivation

Sometime users use has part (P527) as a kind of inverse properties of subclass of (P279). This is semantically wrong as has part if for composition relationship of physical objects (or classes of those type) that are parts of other (bigger) physical objects (or classes of those whole objects), per Help:BMP, and NOT to give a list of the subclasses, like in the example give who was modeled as has part.

There would not be a case if we were just talking of an inverse property of subclass of (P279), but we're not. Here we want to say that the set of all instances of a set of classes (here proton and neutrons), when regrouped, is exactly the set of instances of the superclass (here nucleon). No instance of nucleon is neither a proton nor a neutron.

Example : let Academics be the set of person who teaches, studies or research in a faculty.
let teacher, student, researcher (be the class of persons who teaches, rep. studies and research in a faculty.
< Academics > Union of search < Teacher >
Together with search < Students >
together with search < Researcher >
means that any student, researcher and teacher is an academic, that no person who is neither student, researcher nor teacher is an academic. But a student can also teach, as a researcher.

With the disjoint variant (in green), the constraint is added that an instance of nucleon is an instance of one and only one of the subclasses. Said differently, that the set of subclasses is a Partition of a set (Q381060) (View with Reasonator) of the subject class.

< nucleon (Q102165) (View with Reasonator) > Disjoint union of search < proton (Q2294) (View with Reasonator) >
together with search < neutron (Q2348) (View with Reasonator) >
as a nucleon is a proton or a neutron, but not both.

So the motivation is double :

  • give an alternative to those who want to put a list of subclasses of a class (don't do that, this is incorrect, do that instead)
  • improve our modeling expression power.

Note : the qualifier Together With is here because the set of subclasses must exist in the same statement. This is because if we gave the list of classes in a list of statement, we could not express that there is no other subclass needed to cover all the instances of the superclass, as Wikidata follows the open world assumption (Q851949) (View with Reasonator) (This means we could even use two statement to model two alternative divisions of the class in subclasses for all of its instances). For example let's just add a subclass to nucleon, I don't know highly energetic nucleon. It's a subclass of nucleon, but it would not make sense to add it into

< nucleon (Q102165) (View with Reasonator) > Disjoint union of search < proton (Q2294) (View with Reasonator) >
together with search < neutron (Q2348) (View with Reasonator) >

because either a proton or a neutron could be highly energetical. It's a different classification axis. TomT0m (talk) 15:26, 9 May 2015 (UTC)

Note2 : DO NOT USE if the class list is not close, of course, that is if there is instances of the superclass that is not an instance of any of the child classes, or if it's not sure whether or not.

They are inspired by owl:unionOf and owl:unionOf and owl:disjointunionof (and alldisjointclasses but only because I did not realize there was actually disjointunionof /o\). TomT0m (talk) 19:08, 7 May 2015 (UTC)

Discussion

Still:

  • "(sample: 7..."
  • "qnd"
  • line break before "wol:disjointunionof"
  • How many properties do you propose?
  • I dont see why "Disjoint" is mentionned at all.
  • "of this class .... of that list of classes" Which and which?
  • In everyday language, "UnionOf" seems (to me) related with has part (P527), not with classes.
  • If this proposal is about class partition, why not name it "class partition" or "subclass partition"?
  • If this proposal is not about class partition, why mentionning Partition of a set (Q381060)?

Visite fortuitement prolongée (talk) 21:36, 8 May 2015 (UTC)

@Visite fortuitement prolongée: should be better now. this and that is a common way to speak of resp the subject and the object of the claim. The names are the name given in owl as the links can show, but other are OK if people find this more clear. Union in math is the operation on set, for sure. I don't know about common english

There was a bug in Template:Color. I fixed it. Visite fortuitement prolongée (talk) 14:34, 9 May 2015 (UTC)

Still:

  • No slash inside "au moins une une et une seule".
  • Why "list, or metaclass" and not "Classes", like in Property talk:P279?
  • Why "class list, or metaclass list (resp)" and not "Classes", like in Property talk:P279?
  • "(sample: 7..."
  • "instanèiation"
  • Why not a semantic list after "This proposal is a proposal for"?
  • "too statement"
  • What is the difference between subclass property and "UnionOf" property?
    • Please give examples.
  • What is the difference between "UnionOf" property and "DisjointUnionOf" property?
    • Please give examples.
  • Please give an example where "Together With" qualifier property is required.

Visite fortuitement prolongée (talk) 14:34, 9 May 2015 (UTC)

Thank you, the proposal is much better now. Visite fortuitement prolongée (talk) 17:46, 9 May 2015 (UTC)
« Why "list, or metaclass" and not "Classes" » → I'll edit the Property documentation myself if the properties are created. Visite fortuitement prolongée (talk) 20:20, 11 May 2015 (UTC)
Per Help:metaclass_for an explanation. A class is a set of indvidual. two classes unionned gives another set of individuals, another class. A class of class unioned with a class of class gives a class of class, similarly. But a class should not be unioned with a metaclass to avoid some ontological problems. TomT0m (talk) 20:38, 11 May 2015 (UTC)
  • I'm not sure if I get the "Together with" qualifier point. Qualifiers are also open to be extended, so I don't see why having all values within a statement makes it more close than having one statement for each value. Qualifiers are extendable as statements are, there is no way to prohibit that. Therefore, I'm also not sure if we should actually introduce such limited classes, as that is contradictory to the open system of Wikidata. -- Bene* talk 21:08, 9 May 2015 (UTC)
    Good question. I take the opinion of Markus here : see this post on the ML. I think this makes sense for closed lists, it's an easy way to express that, way easier than for example having a sequence of items with followed by (P156)/follows (P155) terminated by
    <  > followed by search < no value Help >
    . TomT0m (talk) 09:23, 10 May 2015 (UTC)
  • Symbol support vote.svg Support "Disjoint Union of" property
  • Symbol support vote.svg Support "Union of" property

*Symbol oppose vote.svg Oppose "together with" qualifier property. Instead of listing some subclasses with a qualifier you should just add more values to the main property.

Nucleon
Disjoint union of:proton
 :neutron
OK? Filceolaire (talk) 18:43, 11 May 2015 (UTC) Ammended as discussion below. Sorry it took me so long to get back. Filceolaire (talk) 18:04, 18 June 2015 (UTC)
What you are suggesting, in the writing style that I prefer, is:
  • nucleon => proton, neutron
TomT0m want to allow several, distinct, subclass lists, like having in the same item both:
This way, it can not work. TomT0m need a change of Wikidata data structure, or a trick. "together with" is a trick. Of course, since TomT0m has not show an actual example of several, distinct, subclass lists, I do no support "together with", and you are free to oppose it. But I hope that with my explanation, you understand the need. Visite fortuitement prolongée (talk) 19:43, 11 May 2015 (UTC)
It's not a trick, it's a use of qualifiers to express close lists. TomT0m (talk)
@Visite fortuitement prolongée: A real life example : elements can be divided by for example : Monoisotopic element (Q3588104) (View with Reasonator) and non monoisotopic one. They can be divided by element groups such as noble gas (Q19609) (View with Reasonator)metalloid (Q19596) (View with Reasonator) some of these covers the set of chemical elements taken together. Some overlaps with others. TomT0m (talk) 20:30, 11 May 2015 (UTC)
@Filceolaire: No. This must be expressed in one statement. It make sense to say that Paul is a son of Jack. It also make sense that Jenny is a daughter of Jack. But from these two satements, we can't say if Jack have more children per open world assumption (Q851949) (View with Reasonator) which is reasonable in Wikidatas case. With disjoint union this does not make sense to say « nucleon union of proton » and « nucleon union of neutron », no more than in english. This has to be « nucleon union of proton and neutron ». Plus this allows us to say the list is close (see the discussion with Bene* above and the linked mail for this.) Without a qualifier this is as good as «has subclass». TomT0m (talk) 19:58, 11 May 2015 (UTC)
« Without a qualifier this is as good as «has subclass». » → Not exactly. "nucleon => UnionOf => proton, neutron, antiproton, antineutron" say more than "nucleon => subclass => proton, neutron, antiproton, antineutron"; because it say that the classes list is complete ("closed"). The difference is that without "Together With" qualifier, an item can have only 1 classes list, so we could no tell that... wait, what was this real example of you? Visite fortuitement prolongée (talk) 20:20, 11 May 2015 (UTC)
No, the meaning argument that a set of two sentence is not the same as one sentence still holds. But you're kind of tiring me. If you really don't want to be convinced follow the links to the owl properties, you'll see they uses one compound statements, not several statements with the same properties, for good reasons. TomT0m (talk) 20:30, 11 May 2015 (UTC)
@Visite fortuitement prolongée, Filceolaire: Any new question or vote ? It's been a while. TomT0m (talk) 19:49, 19 May 2015 (UTC)
Maybe you should move "(to get the definition [...] the second)" just after "a proposal for Two properties" ? Visite fortuitement prolongée (talk) 20:08, 19 May 2015 (UTC)
  • Symbol oppose vote.svg Oppose I never thought I would O in a proposal of mine the solution without the qualifier. Without it it's as good as has_subclass, as explained above. Of course I Symbol support vote.svg Support the original proposal :) TomT0m (talk) 20:14, 19 May 2015 (UTC)
  • Pictogram voting comment.svg Comment If only 2 properties are created, which work like other properties (thus allowing only one set of subclasses per item), then the tools Template:Tree (see Talk:Q309336) and http://tools.wmflabs.org/wikidata-todo/tree.html?lang=en&q=Q17205&rp=279 will work. With TomT0m's trick, those tools will likely not work. PS: They do not work. Visite fortuitement prolongée (talk) 20:11, 17 June 2015 (UTC)
    @Visite fortuitement prolongée: That's nonsense, really. First, it's not meant to ba an inverse property of subclass of. Second, I am one of the authors of this template and I can make your example work in no time, no problems, it's not hard. But the real solution is to wait for the devteam to implement simple queries to compute inverse relations, then we will be able to adapt the template properly. TomT0m (talk) 20:39, 17 June 2015 (UTC)
    Ok, I reformulate: those tools do not work without adaptation. If you can easily adapt then, then it's good. Visite fortuitement prolongée (talk) 21:52, 17 June 2015 (UTC)

coined by[edit]

   In progress
Description To indicate the person (or maybe sometimes the organisation / group of people) who has used a specific word for a concept for the first time.
Data type Item
Domain any concept, usually a newly 'named' term, movement...
Allowed values human (Q5)
Example Action painting (Q217213)Harold Rosenberg (Q959768); relational art (Q2566149)Nicolas Bourriaud (Q1979892), Stipule (Q304216)Carl Linnæus (Q1043)
Source external reference
Motivation

I've encountered many cases where a specific word for a concept was first used or coined by someone. No property exists for this yet. Quite usual in the case of artistic and cultural movement, see examples above. discoverer or inventor (P61) doesn't seem correct here. Spinster (talk) 19:05, 14 June 2015 (UTC)

Discussion
@Spinster: BA candidate.svg Weak oppose Mmm Wikidata is not about terms but about concepts, and is mutilingual, so this does not fits well. This could maybe be applied as a qualifier to properties like official name or likes, but definitely not to items. I don't understand why discoverer or inventor (P61) would not fit. TomT0m (talk) 19:16, 14 June 2015 (UTC)
See the examples above. You are correct that I should not say these are terms - they ARE concepts, regardless of their translation. I updated the proposal to reflect this. For instance, the Finnish Wikipedia article about action painting, Toimintamaalaus, mentions Harold Rosenberg. Movements and concepts like Action painting (Q217213) and relational art (Q2566149) and Stipule (Q304216) have definitely not been discovered or invented by those people (usually critics, researchers). They were "seen" and named by them for the first time, that's a different thing. Spinster (talk) 19:26, 14 June 2015 (UTC)
Pictogram voting comment.svg Comment More than 6,000 mentions of the exact phrase 'coined by' on enwp. Spinster (talk) 19:26, 14 June 2015 (UTC)
@Spinster: The person that created a new name for that concept ... did not invent that term ? There still is a confusion beetween the concept and the term :). A man can discover or describe a concept, like a taxon, then create a name for this new concept. Actually we already have a property taxon author in taxonomy I could very well see generalized. But I think a construction
< the stuff > name (or original name) (or late name) search < thename >
author search < the person >
is pretty good, it does not talk of the concept, just of the name (plus the inventor of a treasure, or a planet, for example, obviously did not create them, hence the name of the property). I don't see a need for this property. Statements with this pattern will just have to be labelled coined by in infoboxes since it's a common way to express this in english. TomT0m (talk) 19:42, 14 June 2015 (UTC)

@Spinster: Stipule (Q304216) was coined by Carl Linnæus (Q1043). I have some doubts. --Succu (talk) 21:16, 14 June 2015 (UTC)

  • Symbol oppose vote.svg Oppose, refers to terms instead of the actual entities. This is Wiktionary's domain. --Yair rand (talk) 10:02, 15 June 2015 (UTC)
  • Symbol support vote.svg Support though I think 'first described by' might be a better name, or should, at least, be an alias. Filceolaire (talk) 18:12, 18 June 2015 (UTC)
  • Perhaps this should be a qualifier on a mono-lingual text property? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 16:28, 20 June 2015 (UTC)

hanja[edit]

   In progress
Description Korean name written using hanja
Represents Hanja (Q485619)
Data type String
Template parameter "hanja" in en:Template:Infobox Korean name or en:Template:Korean
Domain anything
Allowed values \p{Han}+
Example Park Geun-hye (Q138048) → 朴槿惠 London (Q84)<native label (P1705):"London"><hanja:"런던 — 한국어">
Source external reference, Wikipedia list article, etc.
Motivation

The hanja version of the name is included in infobox/sidebar templates in many articles about Korean topics (e.g. in the infobox on en:Pyongyang, just below the infobox on en:Park_Geun-hye), in brackets after the name in the opening sentence (e.g. ko: 평양직할시) or as a column in tables (e.g. en:List of cities in South Korea). - Nikki (talk) 11:29, 26 June 2015 (UTC)

Discussion
Symbol oppose vote.svg Oppose use as proposed but Symbol support vote.svg Support as a qualifier to string and text properties in other languages. The hanja version of the name for Pyongyang should be given by official name (P1448) and/or native label (P1705) and/or name in native language (P1559), not by this property (but use the "Romanisation" qualifier to give the Latin script version of each of these names). This property could however be used to give the hanja name for "London" in a qualifier to the official name (P1448) property for use in Korean language infoboxes. I have changed the example as my version of this property. Nikki please check and confirm you copy. Filceolaire (talk) 01:01, 27 June 2015 (UTC)
@Filceolaire: Your example is incorrect, that's not en:Hanja, it's en:Hangul (the way Korean is normally written). This property would be very similar to name in kana (P1814) (which you supported without requiring it to only be used as a qualifier - has something changed since then?) - like Japanese is not primarily written in kana, Korean is not normally primarily written in hanja, and like kana is often included in name templates, in brackets in opening sentences, etc, hanja is too, so it should be allowed anywhere that name in kana (P1814) is allowed, i.e. as a qualifier if it's the hanja version of a Korean name in a statement using properties like native label (P1705), name in native language (P1559) and official name (P1448) or as its own statement if it refers to the hanja version of a Korean label (since labels can't have qualifiers themselves). - Nikki (talk) 06:40, 27 June 2015 (UTC)
You raise a good point Nikki. Thinking about it some more. There is a difference between a property called "name in Hanja" and a property called "hanja".
"name in Hanja" could be a property specifically for names. It is similar to all the other multiple "name" properties we have and it can be used as a primary property just like official name (P1448), native label (P1705) or name in native language (P1559). This is based on the assumption that if an item has multiple names then the hanja name just another, additional name independent of the other names.
If, on the other hand, each of the multiple names needs a it's own hanja version then it seems the "hanja" is an alternative way of writing those names rather than being a separate name (and should be used as a qualifier). Which case applies? Filceolaire (talk) 02:31, 28 June 2015 (UTC)

Transliteration or transcription[edit]

   In progress
Description Label from native language or value from official name (P1448), native label (P1705), name in native language (P1559)+family name (P734) etc. translated to readable form in other language including specified transformation method with mandatory qualifier determination method (P459)
Data type String
Template parameter title or subtitle (design specific)
Domain proper noun (Q147276)
Allowed values any text
Example Pyotr Ilyich Tchaikovsky (Q7315): Пётр Ильич Чайковский → (ISO 9 (Q913336)) Pëtr Ilʹič Čajkovskij
Tokyo Prefecture (Q1490): 東京都 → (Hepburn romanization (Q667558)) Tōkyō-to
Georgian (Q8108): ქართული ენა → (Georgian national system of romanization (Q1448216)) kartuli ena
Pythagoras (Q10261): Πυθαγόρας → (ancient trb.) Pythagoras; (ancient trl.) Puthagóras; (modern trb.) Pitagoras; (modern trl.) Pythagóras
Format and edit filter validation mandatory qualifier determination method (P459) set to value, which defines standard of transliteration (Q134550) or transcription (Q207714)
Robot and gadget jobs possible, quite easy for some transliterations
Motivation

Property might be useful for automatic generating readable descriptions from statements if object name is not available in any readable script in user language. This might be a standard way to provide transliteration or transcription of the name between many languages. The examples above are biased because they show romanization only, but other direction is also possible. Unfortunately I am not able to provide any such example. Paweł Ziemian (talk) 17:50, 27 June 2015 (UTC)

Discussion
We have some romanisation-properties now, like "pinyin transliteration (P1721)", so there is maybe a way to solve even other systems. But if we are to follow the pattern here, we need one property for each kind of romanisation? -- Innocent bystander (talk) 18:12, 27 June 2015 (UTC)
If the conversion is some kind of international standard like Hepburn romanization (Q667558) or ISO 9 (Q913336) it can be promoted to separate property. However, there are cases where such translation is country/language specific and generating N×N - N (country/language) properties is ridiculous. One generic property should serve for all relatively rarely used cases. If some of them became popular it can be always promoted later to dedicated property and converted by bot. Paweł Ziemian (talk) 19:10, 27 June 2015 (UTC)
One item can have multiple names, even in one language (via aliases). To be clear as to which name you are transliterating this property needs to be a qualifier to one of the other name properties. Unfortunately if this property is a qualifier then it can't have it's own qualifiers to tell you which transliteration system was used. This indicates that we need multiple properties - one for each transliteration system. Fortunately we don't need to transliterate all names since for most items, in most languages, the transliterated name will be in the label. I think. Filceolaire (talk) 03:00, 28 June 2015 (UTC)
I am not so sure about that! The Swedish transcription of for example Russian names are not always in the label, but rather the German or English, since those transcriptions are sometimes more spread in common media. And I would prefer to see a monolingual datatype in those cases, i.e. when the transcription is langauage dependant. -- Innocent bystander (talk) 10:56, 28 June 2015 (UTC)
It is not unusual that there exist a few methods for transcription from one language to another. I agree with argument that it should be a qualifier, but with requirement for auxiliary and mandatory qualifier it is impossible to implement this. This is the weakness point in my proposal. I think I should withdraw the proposal and introduce set of new proposals for specific transliterations, what was mentioned above. Paweł Ziemian (talk) 13:33, 28 June 2015 (UTC)

Hepburn romanization[edit]

   In progress
Description Property used as qualifier in official name (P1448), native label (P1705), name in native language (P1559), family name (P734) etc if it is presented in Japanese
Represents Hepburn romanization (Q667558)
Data type String
Template parameter title or subtitle (design specific)
Domain proper noun (Q147276) in Japanese
Allowed values any text
Example Tokyo Prefecture (Q1490): 東京都 → (Hepburn romanization (Q667558)) Tōkyō-to
Motivation

Property might be useful for automatic generating readable descriptions from statements for languages using latin scripts if object name is not available in any readable script in user language. Paweł Ziemian (talk) 14:09, 28 June 2015 (UTC)

Discussion
  • Symbol support vote.svg Support, I was about to propose it after working on quite a lot of japanese items :)
by the way, could you please provide a simple online automatic converter ? I could not find one that worked : only long pages of explanations :/ --Hsarrazin (talk) 17:58, 1 August 2015 (UTC)

Georgian national system of romanization[edit]

   In progress
Description Property used as qualifier in official name (P1448), native label (P1705), name in native language (P1559), family name (P734) etc if it is presented in Georgian
Represents Georgian national system of romanization (Q1448216)
Data type String
Template parameter title or subtitle (design specific)
Domain proper noun (Q147276) in Georgian
Allowed values any text
Example Georgian (Q8108): ქართული ენა → (Georgian national system of romanization (Q1448216)) kartuli ena
Robot and gadget jobs possible, there is simple character lookup table
Motivation

Property might be useful for automatic generating readable descriptions from statements for languages using latin scripts if object name is not available in any readable script in user language. Paweł Ziemian (talk) 14:18, 28 June 2015 (UTC)

Discussion
Symbol support vote.svg Support - working with Georgian names is really painful - can you please provide an online converter (if one exists ?) --Hsarrazin (talk) 18:01, 1 August 2015 (UTC)

ISO 9[edit]

   In progress
Description Property used as qualifier in official name (P1448), native label (P1705), name in native language (P1559), family name (P734) etc if it is presented in Cyrillic or Latin script. Conversion works in both directions, that is Cyrillic text can be transliterated to Latin text and Latin text can be assigned with corresponding Cyrillic text.Cyrillic text can be transliterated to corresponding Latin text.
Represents ISO 9 (Q913336)
Data type String
Template parameter title or subtitle (design specific)
Domain proper noun (Q147276) in Cyrillic or Latin script
Allowed values any text
Example Pyotr Ilyich Tchaikovsky (Q7315): Пётр Ильич Чайковский → (ISO 9 (Q913336)) Pëtr Ilʹič Čajkovskij
Robot and gadget jobs possible, there is simple character lookup table
Motivation

Property might be useful for automatic generating readable descriptions from statements between languages with Cyrillic and Latin scripts if object name is not available in any readable script in user language. Paweł Ziemian (talk) 14:33, 28 June 2015 (UTC)

Discussion
  • I would tend to support this property. The problem I would identify is that of multilingual piece of it, however. The French for (example) "Bill" is not the same as the English for Bill, so transliterating to Cyrillic from either language is going to have a different transliteration. Also, I'm not sure why we would use it as a qualifier for claims of the Wikibase Entity type rather than only for those of the String type. --Izno (talk) 19:35, 10 July 2015 (UTC)
    • I was wrong. The conversion works only from Cyrillic to Latin script, but the process is fully reversible and language independent. Fixed. Paweł Ziemian (talk) 20:53, 10 July 2015 (UTC)
  • Symbol support vote.svg Support - I was about to propose this creation myself :) --Hsarrazin (talk) 18:03, 1 August 2015 (UTC)

construct has conceptual overlap with[edit]

   In progress
Description measures of the strength, or assessments of presence, of these two constructs correlate
Data type Item
Example surgency (Q7646185)introversion and extraversion (Q127588), grit (Q4453370)Conscientiousness (Q1307067)
Motivation

I want this for my work with personality traits. There are many named traits and many of them are highly similar to one-another. Antrocent (talk) 06:38, 29 June 2015 (UTC)

Discussion
Pictogram voting comment.svg Comment Not a good idea to start a proposal saying "I want this for my work". A property is not a personal tool but a general tool which have to be useful for everyone. Snipre (talk) 07:48, 29 June 2015 (UTC)

Name Etymology[edit]

   In progress
Description An account of the origin and historical development of a name.
Data type Monolingual text
Template parameter "meaning" in en:template:infobox family name
Domain Given Name (given name (Q202444))
Allowed values text
Example Sophia (Q2302787) → Wisdom, Madison (Q1424362) → Son of Matthew, Gabriel (Q4925914) → "Able-bodied one of God"; or "messenger of God"
Source infobox
Motivation

Many people when looking for a name for a baby are interested in the meaning of the name.

Discussion
  • Symbol oppose vote.svg Oppose This is a description, which should be defined in Wikipedia or Wiktionary. It might consists of whole paragraph of text. What about support for other languages? Paweł Ziemian (talk) 17:23, 10 July 2015 (UTC)
    @Paweł Ziemian: Most meaning infobox properties for given names contain very short meaning, usualy 10 words max, many times 1 or two words, and this is why this property is useful instead of the description, that can contain multiple paragraphs with a lot more info than the etymology LeonardoBueno (talk) 19:13 , 10 July 2015 (UTC)
    I think the property proposal is good, however, we should wait for Wiktionary support in Wikidata to implement it. The data type here could be an array of items, which are words (one or more) used to create the new name. These words might come from foreign languages such as Greek, Latin or Hebrew. Machines cannot understand what the description mean, so forget about any query for it or analyze it in automatic way. You don't need to read everything from Wikidata to put it infobox. Some information might be still provided in old way as direct parameter in Wikipedia article wikicode. Paweł Ziemian (talk) 19:28, 10 July 2015 (UTC)
  • Wait for Wiktionary integration. Etymology is clearly something Wiktionary handles and if we should ever handle Wiktionary in some fashion, the etymology of a phrase will be important. Until then, we don't have the mechanisms to multilingually use this data item. --Izno (talk) 19:34, 10 July 2015 (UTC)
  • Symbol oppose vote.svg Oppose. If we do etymologies in structured data then we will link to the item for the word that the current word is derived from. This is inherently a wikitionary thing as wikidata doesn't have items for words - it has items for concepts, each of which has multiple labels. For now the place to put the monolingual text paragraph with the etymology of a name is in the wikipedia article about the name. (If the wikipedia article is a disambiguation list of people with that name then add the etymological paragraph at the top and convert the wikipedia DAB to a List.) Filceolaire (talk) 02:01, 12 July 2015 (UTC)
  • Pictogram voting comment.svg Comment I tend to agree that it's a bad idea to refer to linguistic entites in Wikidata. However, I think if the entity is actually a name, this is possible without too much problems. There is several preceding examples : human names, title names, the named after property … knowing that Wikidata wiktionary is not here until an unknown amount of time, this could be a temporary solution. I guess stuffs will have to be re-exanimated when that finally happens. (Side note Josve05a (talk)

FelixReimann (talk)
Infovarius (talk)
Daniel Mietchen (talk)
Soulkeeper (talk)
Brya (talk)
Klortho (talk)
Tobias1984 (talk)
Delusion23 (talk)
Andy Mabbett (talk)
Dan Koehl (talk)
Achim Raschka (talk)
TomT0m
Tinm

Pictogram voting comment.svg Notified participants of Wikiproject Taxonomy the nature of taxon and taxon names might be to sort out :) ) TomT0m (talk) 09:41, 12 July 2015 (UTC)

  • Pictogram voting comment.svg Comment this is already in the scope of Wikipedia. Even with Wiktionary support (we don't know if/when we get it for sure), would the structure be different? It seems to me that this would go into a monolingual string property anyways. Is this correct? --- Jura 09:53, 12 July 2015 (UTC)
    • Like I said above, I think etymology should be a link to a word item - the item for the word from which the current word is derived, so it's not a monolingual text item. A name could be derived from the Irish word for Blacksmith (like Magowan ( Q1755217)) or from the English word for Blacksmith (like Smith ( Q1158446)) but wikidata only has one item for Blacksmith.
    • We already have named after (P138). You can, for instance, use that to link personal names derived from the bible to the biblical characters they are named after. Filceolaire (talk) 13:13, 12 July 2015 (UTC)
      • enwiki seems to do mostly without such links. Wiktionary has them, but links to pages that also cover other things - they don't seem to be targeted. In conclusion, I don't think they are actually needed and monolingual string type could do for this type of information. --- Jura 09:53, 17 July 2015 (UTC)
      • As for P138: Sometimes, it's a tricky question to figure out if one was named after the other or if the other was just the best known early bearer of a name. If it's clear, I suppose people already use them. Still, the information is different from the one in this proposed property. --- Jura 09:53, 17 July 2015 (UTC)
  • Symbol oppose vote.svg Oppose. Why only English? We should create 200+ (or 6000+) similar properties for other languages? --Infovarius (talk) 22:30, 12 July 2015 (UTC)
    • It's monolingual text, so you can define the language of text. --- Jura 09:53, 17 July 2015 (UTC)
  • Pictogram voting comment.svg Comment the main issue I see is that Wikidata (and probably also Wikipedia) at some point got flooded with a large number of etymologies that are (let's say it this way:) difficult to assess. As Wikipedia is better equipped to sort out such things, I tend to concentrate on the other aspects of given names and family names for now. --- Jura 09:53, 17 July 2015 (UTC)
  • Symbol oppose vote.svg Oppose - this is for wiktionary or wp, not wikidata :/ --Hsarrazin (talk) 18:05, 1 August 2015 (UTC)

Wikimedia username[edit]

   In progress
Description this item's username on a Wikimedia project
Data type String
Domain human (Q5)
Allowed values type of linked items (Q template or text), list or range of allowed values, string pattern...
Example Justin Knapp (Q3331076) → Koavf
Format and edit filter validation check that it's a real account
Formatter URL https://meta.wikimedia.org/wiki/Special:CentralAuth/$1
Robot and gadget jobs migrate the existing uses from website account on (P553)
Motivation

Proposing with the aim of splitting website account on (P553) (see Wikidata:Project chat#Website user names)).

There are various notable people in Wikidata who are also Wikimedians (including some who are notable for work they've done as Wikimedians), so people obviously want to link to their username. There are a variety of projects in a variety of editions but now that SUL was finalised, I think it could be stored as a single Wikimedia username.

There might be a better URL which lists all the accounts which could be used as the URL formatter, but this is the only thing I'm aware of right now.

Does anyone know which characters are/aren't allowed in usernames?

- Nikki (talk) 12:25, 18 July 2015 (UTC)

Discussion

Symbol oppose vote.svg Oppose May violate WMFs privacy policy.--Kopiersperre (talk) 14:48, 18 July 2015 (UTC)

Nonsense: we already record them, using website account on (P553), and many users choose to link their real and Wikipedia identities. The privacy policy doesn't prevent us from doing so in such cases. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 20:42, 18 July 2015 (UTC)
Symbol support vote.svg Support If the disclose wasn't done inadvertently, I can support this.--Kopiersperre (talk) 19:02, 1 August 2015 (UTC)

Symbol support vote.svg Support Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 20:42, 18 July 2015 (UTC)

Symbol oppose vote.svg Emot per privacy, as Kopiersperre. There are of course exceptions, and the present system fullfills that need. -- Innocent bystander (talk) 07:15, 19 July 2015 (UTC)

RE:Nikki Regarding characters that are/aren't allowed. I do not know exactly, but I have seen notes that some users who adopted a username 10 years ago, today have characters that cannot be used in new usernames. I think @ is such a character. -- Innocent bystander (talk) 07:15, 19 July 2015 (UTC)
  • @Kopiersperre, Innocent bystander: I think we should accept these values if they disclosed the relation by themselves. See wmf:Privacy_policy#Because_You_Made_It_Public.--GZWDer (talk) 16:36, 20 July 2015 (UTC)
    • I agree, but setting a dedicated property for it, makes it to easy for the trolls to violate the rules. -- Innocent bystander (talk) 17:19, 20 July 2015 (UTC)
  • Symbol oppose vote.svg Oppose let's not create a property for every website one can possibly have an account. I'm not sure where we should draw the line but there aren't that many people who have an account here and are notable enough I think --Bene* talk 07:11, 27 July 2015 (UTC)
    • @Bene*: No one is proposing "a property for every website one can possibly have an account [on]". Wikimedia user IDs are, collectively, already in the top 15 of websites listed using website account on (P553), and almost certainly under-recorded. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 20:06, 27 July 2015 (UTC)
  • Symbol oppose vote oversat.svg Strong oppose - privacy, wm-rules, and unnecessary. --Hsarrazin (talk) 18:08, 1 August 2015 (UTC)
    • The argument "privacy" is invalid, because this data is already stored in Wikidata. "wm-rules" is meaningless. And you advance no argument as to why you believe the proposaed property to be unnecessary. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 18:11, 1 August 2015 (UTC)
no, the link between the real identity of the person and its wm identity is not already stored, except for admins or crats. A lot of considered university teachers or so, that publish in reviews, could not like to see their wm-identity displayed this way, especially, since the Global account now gives access to all contributions in all wm projects in a few clicks :/
to me, this property could be acceptable only if the contributor did it him/herself : i.e. only statements added by concerned contributor would be ok, and even then, I would be very cautious… :( --Hsarrazin (talk) 19:24, 1 August 2015 (UTC)
Nonsense. We have over 80 instances of P553 for Wikimedia projects with user names. We also have many real names and user names associated with each other in realiable sources. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 20:33, 1 August 2015 (UTC)
wow 80 !! :D — That really justifies a new property !
reliable sources does not mean that it makes those info readily available to anybody, which will be the case if those are added to wikidata in a directly usable and re-usable way (through VIAF among others). Which, in my opinion, poses problems of privacy. I personally know people, who are in VIAF, ISNI, BNF, etc., and who contribute wp, but do not want, under any circumstance, this info possibly disclosed. This property would be very problematic for some of them. Not everybody is lucky enough to work in places where wikipedia is well considered. :/ --Hsarrazin (talk) 21:43, 1 August 2015 (UTC)

literal translation[edit]

   In progress
Description literal translation
Data type Multilingual text (not available yet)
Domain things that have an official name/title in one language should be used as a modifier. Can be used as a claim for things like names.
Allowed values text
Example
Motivation
things like films, books or places often have an offical name or title. sometimes--Shisma (talk) 12:01, 20 July 2015 (UTC)
Discussion
  • I don't quite understand what it adds. If the literal translation is used, it should be the label, otherwise it's non-official and shouldn't be added to Wikidata. If somebody wants to know what something is literally translated, I suggest using a translation tool. Mbch331 (talk) 13:30, 20 July 2015 (UTC)
    • Many articles start of like my example French Riviera:

      The Côte d'Azur (French pronunciation: ​[kot daˈzyʁ]; Occitan: Còsta d'Azur; literally: 'Azure Coast'), often known …

      or Kraftwerk

      Kraftwerk (German pronunciation: [ˈkʀaftvɛɐk], "power station") is a German electronic music band formed by …

      Neither of these should have the literal translation as an alias because its simply not an alias. In order to generate the introductory phase of an article this information could be useful --15:15, 20 July 2015 (UTC)

YouTube user name[edit]

   In progress
Description User name of a person, or organisation, on YouTube
Data type String
Domain human (Q5), organization (Q43229)
Example Avril Lavigne (Q30449) => avrillavigne
Source YouTube
Formatter URL https://www.youtube.com/user/$1
Motivation

Proposing with the aim of splitting website account on (P553) (see Wikidata:Project chat#Website_user_names). Per this, YouTube is the third-most used value for P553, after Twitter & Facebook. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 18:12, 22 July 2015 (UTC)

Discussion
  • Pictogram voting comment.svg Comment The problem with Youtube is that some users have names like "https://www.youtube.com/<name>" others "https://www.youtube.com/user/<name>" or "https://www.youtube.com/channel/<name>". It's even possible that two of these exist and are unrelated, leading to different content. To avoid such ambiguity, URL-datatype seems more appropriate. --- Jura 18:43, 22 July 2015 (UTC)
  • Symbol oppose vote.svg current proposal with string datatype. --- Jura 18:47, 22 July 2015 (UTC)
  • https://www.youtube.com/mbch331 and https://www.youtube.com/user/mbch331 both point to my YouTube channel. (Wouldn't know the channel id as I never use it) Mbch331 (talk) 11:41, 23 July 2015 (UTC)
  • Try https://www.youtube.com/DonaldTrump which is for Donald Trump.
    Hillary Clinton is at https://www.youtube.com/channel/UCLRYsOHrkk5qcIhtq033bLQ (not at https://www.youtube.com/user/channel/UCLRYsOHrkk5qcIhtq033bLQ ). --- Jura 13:02, 23 July 2015 (UTC)
    • It's not clear that either of those is for the person, rather then the campaign. YouTube does not appear to use a /user/channel/ format. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 15:12, 23 July 2015 (UTC)
      • Your comment doesn't actually address the issue of custom URLs, such as "youtube.com/DonaldTrump". Merely focusing on legacy usernames (that are being phased out) doesn't seem forward orientated. For an overview, see "Understand your channel URLs". --- Jura 04:27, 24 July 2015 (UTC)
        • It most certainly does address that. And the page you cite says that, while user names are no longer issued, existing names (and the URLs of which they are part) are still valid and may still be used. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 20:15, 27 July 2015 (UTC)
  • I think the datatype here should be URL. And restraints are either it has https://youtube.com/user/<username>, which is the same as https://youtube.com/<username> or it has https://youtube.com/channel/<channelid>, where the channel id is 24 chars long (latin alphabet) and has to start which UC. User id isn't case sensative, channel id is. Mbch331 (talk) 13:16, 23 July 2015 (UTC)
    • That wouldn't work for the Donald Trump sample, try https://www.youtube.com/user/DonaldTrump --- Jura 13:19, 23 July 2015 (UTC)
      • You're right. Never noticed that this was the case. In that case all type should be unique, but youtube.com/user/$1 doesn't have to be unique when comparing to youtube.com/$1. Mbch331 (talk) 13:24, 23 July 2015 (UTC)
    • No. This property should be for YouTube user names, type=string, for the same reasons that we don't store full URLs for other identifiers. Other properties may be created for YouTube channels, if needed. We shouldn't muddle two types of identifier in this way. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 15:12, 23 July 2015 (UTC)
      • What's your plan for Donald Trump? --- Jura 15:32, 23 July 2015 (UTC)
  • Symbol support vote.svg Support I looked at YouTube's API and they distinguish user names from channel IDs. I also found [1], it seems the Donald Trump example above is a custom URL, not a user name or channel ID. I don't think storing the entire URL would be a very structured way of storing the data. - Nikki (talk) 17:48, 23 July 2015 (UTC)
    • The link you provided is most helpful, but it seems they are dropping the "legacy username" from the API. --- Jura 19:26, 23 July 2015 (UTC)
    • @Nikki: Youtube removed what they call the "legacy username" from their api and exclude the creation of new ones. For new users, only "custom URI" become available and we need to include these in one way or the other. The proposal below for a single URI based property seems better structured (it's called uniform identifier for a reason) and consistent with other properties for complex naming schemes. --- Jura 08:58, 1 August 2015 (UTC)
      • As you missed it above, I'll repeat: YouTube says that, while user names are no longer issued, existing names (and the URLs of which they are part) are still valid and may still be used. If you wish to start an RfC to change our policy on identifiers to always store full URIs rather than the UID component, please do so in an appropriate forum. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 10:41, 1 August 2015 (UTC)
        • Can you provide us with a link to what you describe as policy? --- Jura 10:45, 1 August 2015 (UTC)
      • YouTube's API still supports the username using the "forUsername" parameter (see [2] and [3]). I don't think that storing a single URL property is better structured. It would combine multiple incompatible things into a single property (channel ID and username require different API queries, custom URL doesn't seem to be usable in the API at all). There are also many possible URLs for the same ID or name (http vs https, www vs no www, desktop vs mobile, trailing slash vs no trailing slash, etc) which is not a sign of well structured data. - Nikki (talk) 17:42, 1 August 2015 (UTC)

YouTube channel id[edit]

   In progress
Description ID of the YouTube channel of a person, or organisation
Data type String
Domain human (Q5), organization (Q43229)
Allowed values UC([a-zA-Z-_0-9]){22}
Example Jordan Jansen (Q16240161) => UCDLPyCCDRSxQd1OtBkup-Bw
Source YouTube
Formatter URL https://www.youtube.com/channel/$1
Motivation

Proposing with the aim of splitting website account on (P553) (see Wikidata:Project chat#Website_user_names). Per this, YouTube is the third-most used value for P553, after Twitter & Facebook. The YouTube account can either be a username or a channel id. A channel id needs to be a separate item, because it's different from a user link. Channel id is always 24 characters long and always starts with UC. Mbch331 (talk) 16:31, 23 July 2015 (UTC)

Discussion
  • Symbol support vote.svg Support I would use "channel ID" rather than "channel name", since it's not a name someone picked. The description could then be something like "ID (starting with UC) of ..." - Nikki (talk) 16:49, 23 July 2015 (UTC)
    • Changed it to ID. Mbch331 (talk) 16:55, 23 July 2015 (UTC)
  • Support as complementary to the above proposal. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 18:47, 23 July 2015 (UTC)

YouTube address[edit]

   In progress
Description Channel address/User name/address of a person, or organisation's YouTube feed [4]
Data type URL
Domain human (Q5), organization (Q43229)
Allowed values URLs starting with https://youtube.com/
Example Avril Lavigne (Q30449) => https://www.youtube.com/user/avrillavigne
Hillary Rodham Clinton (Q6294) => https://www.youtube.com/channel/UCLRYsOHrkk5qcIhtq033bLQ
Donald Trump (Q22686) => https://www.youtube.com/DonaldTrump (not https://www.youtube.com/user/DonaldTrump)
  • Pictogram voting comment.svg Comment: This to replace the current use of website account on (P553) for Youtube. YouTube are basically channels, but these can be addressed as Youtube.com/<name> or Youtube.com/user/<name> or as Youtube.com/channel/<channel id>. Similar to other sites with complex addressing, we apply a single URL as identifier. This ensures that users aren't lost with too many concurring properties. --- Jura 17:06, 23 July 2015 (UTC)
  • Reject proposal, for the same reasons as discussed in the context of the identifier proposals. As for "lost with too many concurring [sic] properties", we have a number of other property sets where there are multiples (see property:P1217 to 1220; property:P1233 to 1235 and 1239; and a handful of others).

    Why are you opening a second discussion while the first is still underway? --Izno (talk) 17:39, 23 July 2015 (UTC)

    • It's actually the 3rd, not the 2nd. --- Jura 18:01, 23 July 2015 (UTC)
  • Oppose per proposals above. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 18:44, 23 July 2015 (UTC)