Property talk:P103

From Wikidata
Jump to navigation Jump to search

Documentation

native language
language or languages a person has learned from early childhood
Descriptionthe native language of a person, use languages spoken, written or signed (P1412) for all other languages, or if it is not sure if the language is the native Language. For works use language of work or name (P407) and original language of film or TV show (P364)
Representsfirst language (Q36870)
Data typeItem
Domain
According to this template: person (Q215627)
According to statements in the property:
human (Q5), ethnic group (Q41710), fictional character (Q95074), legendary figure (Q13002315), character that may or may not be fictional (Q21070598) or group of humans (Q16334295)
When possible, data should only be stored as statements
Allowed valueslanguage, dialect, languoid (Q17376908) (note: this should be moved to the property statements)
ExampleLeo Tolstoy (Q7243) → Russian (Q7737)
Johann Wolfgang von Goethe (Q5879) → German (Q188)
William Shakespeare (Q692) → English (Q1860)
Miguel de Cervantes (Q5682) → Spanish (Q1321)
Jules Verne (Q33977) → French (Q150)
Tracking: usageCategory:Pages using Wikidata property P103 (Q20116989)
See alsolanguages spoken, written or signed (P1412), writing language (P6886)
Lists
Proposal discussionProposal discussion
Current uses
Total339,073
Main statement338,751>99.9% of uses
Qualifier288<0.1% of uses
Reference34<0.1% of uses
Search for values
[create Create a translatable help page (preferably in English) for this property to be included here]
Value type “languoid (Q17376908)”: This property should use items as value that contain property “instance of (P31)”. On these, the value for instance of (P31) should be an item that uses subclass of (P279) with value languoid (Q17376908) (or a subclass thereof). (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P103#Value type Q17376908, SPARQL
Item “languages spoken, written or signed (P1412)”: Items with this property should also have “languages spoken, written or signed (P1412)”. (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P103#Item P1412, search, SPARQL
Scope is as main value (Q54828448): the property must be used by specified way only (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P103#Scope, SPARQL
Allowed entity types are Wikibase item (Q29934200): the property may only be used on a certain entity type (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P103#Entity types
None of patois (Q744710): value must not be any of the specified items.
Replacement property:
Replacement values: patois (Q21014183) (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P103#none of, SPARQL
None of Jatki (Q115408318): value must not be any of the specified items.
Replacement property:
Replacement values: (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P103#none of, SPARQL
None of Eastern Punjabi (Q112664216): value must not be any of the specified items.
Replacement property:
Replacement values: Punjabi (Q58635) (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P103#none of, SPARQL
None of Western Punjabi (Q1389492): value must not be any of the specified items.
Replacement property:
Replacement values: Punjabi (Q58635) (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P103#none of, SPARQL
None of Parsi (Q25559304): value must not be any of the specified items.
Replacement property:
Replacement values: Gujarati (Q5137) (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P103#none of, SPARQL
This property is being used by:

Please notify projects that use this property before big changes (renaming, deletion, merge with another property, etc.)

 
Person properties
Name
Birth
Death
General
Education
Profession
Views
Body
Family

Wanted: Source or infobox parameter[edit]

Where can bots collect this data? Mange01 (talk) 23:47, 7 March 2013 (UTC)[reply]

Extension[edit]

Can we extend that property to books and newspapers ? Snipre (talk) 23:24, 27 March 2013 (UTC)[reply]

No. There are language of work or name (P407) and original language of film or TV show (P364). --Infovarius (talk) 07:53, 7 November 2016 (UTC)[reply]

Rename to language and merge with P:P364[edit]

As mentionned by others above, this property is also relevant for non-native languages (it certainly makes sense to say that Samuel Beckett is a French speaker). Can I rename this property ? When it is used without qualifiers, I think it can be assumed to mean "native language", though it will always be better to provide more detailed information.

If we do so, can we mege this property with P:P364 to create a general "language" property. I do not see any use it distinguishing people from works here. --Zolo (talk) 22:02, 5 April 2013 (UTC)[reply]

I know you love to merge and create experimental properties. But Wikidata is chaotic enough and people and works are two different things. "It can be assumed ..." is not a way to serious work. We need clearly defined properties for the infoboxes. Wikidata is an international project and it's hard enough to agree what we are talking about in English. --Kolja21 (talk) 23:06, 5 April 2013 (UTC)[reply]
On Samuel Beckett: It does not make sense to add all languages a person has learned in his life. What we need are two basic infos: 1.) What is the native language of the author? 2.) In what language he wrote the original version of a single work, for example Waiting for Godot? --Kolja21 (talk) 23:37, 5 April 2013 (UTC)[reply]
It is not necessary to add all languages, only those uttered in published works.--Giftzwerg 88 (talk) 13:23, 2 January 2015 (UTC)[reply]

Removal of the single value constraint[edit]

Why this property has a constraint of single value? It has a lot of constraint violations that may be (or may not be) valid data, we have to add all the people with more than one native language with an exception? Because I don't know on other places, but at least where I come from most of the children are native bilingual, and I'm sure that that's a common thing in more places in the world. -- Agabi10 (talk) 01:27, 7 October 2015 (UTC)[reply]

It's not an issue of there are some violations. Just avoid setting it to "mandatory=yes".
Clearly items that stand out on the report are problems: Q7626039, [[]]. --- Jura 06:34, 7 October 2015 (UTC)[reply]

Why is this a base separated property?[edit]

To have this property separated from languages spoken, written or signed (P1412) just adds an element of confusion. I would much prefer to see this merged to languages spoken, written or signed (P1412) and for it to have a qualifier that says native rather than make people have to know that it exists. Also in English it can be ambiguous as "a native language" can be considered different from "my native language."  — billinghurst sDrewth 21:44, 1 February 2016 (UTC)[reply]

Qualifiers aren't really easier to handle. If it's not a person's native language, don't add it to an item, use P1412 instead.
--- Jura 09:42, 13 March 2016 (UTC)[reply]

Extension from person to people[edit]

I've added ethnic group (Q41710) as possible type, because it is logical for an ethnos to have a native language. --Infovarius (talk) 07:58, 7 November 2016 (UTC)[reply]

Or is it better to use language used (P2936) for this purpose? --Infovarius (talk) 16:15, 28 May 2019 (UTC)[reply]

This should be merged with Q36870[edit]

I don't know how to do, but this property is the same as Q36870, so they should be merged. Xabier Armendaritz (talk) 15:15, 14 January 2017 (UTC)[reply]

Sorry, don't take my message above into account. I just have seen the difference — this property refers to the speaker, whereas first language (Q36870) refers to the language. Xabier Armendaritz (talk) 15:19, 14 January 2017 (UTC)[reply]
What is more: a property can not be the same as an item. They are different by nature. --Infovarius (talk) 19:22, 15 January 2017 (UTC)[reply]

Single values constraint[edit]

I removed the single values constraint. It does not make much sense as a lot of people have more than one native language. --Emu (talk) 11:19, 1 April 2021 (UTC)[reply]

Retrieved from "https://www.wikidata.org/w/index.php?title=Property_talk:P103&oldid=2116793781"