Property talk:P1412

From Wikidata
Jump to navigation Jump to search

Documentation

languages spoken, written or signed
language(s) that a person or a people speaks, writes or signs, including the native language(s)
Representslanguage proficiency (Q2390977)
Data typeItem
Domain
According to this template: person (Q215627)
According to statements in the property:
person (Q215627), primate (Q7380), humanoid robot (Q584529), group of humans (Q16334295), synthetic voice (Q79600797), pseudonym (Q61002), character that may or may not be fictional (Q21070598), human (Q5), class of fictional entities (Q15831596), group of fictional characters (Q14514600) or fictional character (Q95074)
When possible, data should only be stored as statements
Allowed values
According to this template: languoid (Q17376908)
According to statements in the property:
When possible, data should only be stored as statements
ExampleConfucius (Q4604) → Old Chinese (Q35137)
Margrethe II of Denmark (Q102139) → Danish (Q9035)
English (Q1860)
French (Q150)
Swedish (Q9027)
German (Q188)
Faroese (Q25258)
Ukrainian (Q8798)
Koko (Q1348219) → American Sign Language (Q14759)
Sourceexternal reference, Wikipedia (note: this information should be moved to a property statement; use property source website for the property (P1896))
Tracking: sameno label (Q42533381)
Tracking: usageCategory:Pages using Wikidata property P1412 (Q23909087)
See alsonative language (P103), language used (P2936), official language (P37), language of work or name (P407), writing language (P6886)
Lists
Proposal discussionProposal discussion
Current uses
Total2,903,758
Main statement2,903,354>99.9% of uses
Qualifier324<0.1% of uses
Reference80<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/P1412#Value type Q17376908, SPARQL
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/P1412#Type Q215627, Q7380, Q584529, Q16334295, Q79600797, Q61002, Q21070598, Q5, Q15831596, Q14514600, Q95074, 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/P1412#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/P1412#Entity types
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/P1412#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/P1412#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/P1412#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/P1412#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.)

Value Español (Q16775638) will be automatically replaced to value Spanish (Q1321).
Testing: TODO list
Value Spain (Q29) will be automatically replaced to value Spanish (Q1321).
Testing: TODO list
Value England (Q21) will be automatically replaced to value English (Q1860).
Testing: TODO list
Value English people (Q42406) will be automatically replaced to value English (Q1860).
Testing: TODO list
Value English (Q2017605) will be automatically replaced to value English (Q1860).
Testing: TODO list
Value France (Q142) will be automatically replaced to value French (Q150).
Testing: TODO list
Value French (Q121842) will be automatically replaced to value French (Q150).
Testing: TODO list
Value Igbo people (Q244157) will be automatically replaced to value Igbo (Q33578).
Testing: TODO list
Value Yoruba people (Q190168) will be automatically replaced to value Yoruba (Q34311).
Testing: TODO list
Value Germany (Q183) will be automatically replaced to value German (Q188).
Testing: TODO list
Contemporaries:
if [item A] has this property (P1412) linked to [item B],
then [item A] and [item B] have to coincide or coexist at some point of history.
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/P1412#Contemporary, SPARQL
This property is being used by:

he:תבנית:סופר

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

Label/description

[edit]

Can we label this just with "languages spoken" as in the proposal? This avoids having to sort native near native and other languages. --- Jura 13:23, 19 July 2014 (UTC)[reply]

✓ Done --- Jura 15:43, 24 July 2014 (UTC)[reply]

native language (P103)

[edit]

Can include native languages? or is it necessity (Q2301186)? Here it matters. So there are 2 (final) alternatives, imho: A) when native language (P103) is unknown exactly (and not specified), languages spoken, written or signed (P1412) allows to have its candidates. But when native language (P103) is determined, the same value for languages spoken, written or signed (P1412) should be deleted; B) languages spoken, written or signed (P1412) should always contain native language (P103) (descriptions need to be updated accordingly). I prefer A (not duplicating information), @Thibaut120094: seems to prefer B. What other votes/opinions? --Infovarius (talk) 15:45, 3 June 2015 (UTC)[reply]

It says "languages spoken", so let's include them and avoid complicating things. --- Jura 15:55, 3 June 2015 (UTC)[reply]

separate in two properties, "spoken" and "published"?

[edit]

On Italian Wikisource we would like to categorize the authors according to the language in which they produced some work. I found this property, but there's a problem: a person can be able to speak a language, but that doesn't mean that he necessarily published in that language.

What do you guys think about splitting this property in two:

  • languages spoken for language that a person is able to speak
  • language published into for language that a person used in published works

@Accurimbono: Candalua (talk) 12:31, 21 September 2015 (UTC)[reply]

  • Not convinced. This property, despite being somewhat basic, isn't that easy to feed.
    To address your purpose: If you have a set of works and look for their original language and author, you should be able to generate the list without a separate property. --- Jura 12:37, 21 September 2015 (UTC)[reply]
@Jura1: yes, but such a list can only be generated by some coding, the information would not be immediately usable to everybody... Candalua (talk) 14:52, 21 September 2015 (UTC)[reply]
If you see a big advantage of having an additional property for languages published in, you could request one to be created. In any case, I think anything list-related at Wikidata is "generated by some coding" and not "immediately usable to everybody". --- Jura 12:44, 22 September 2015 (UTC)[reply]

Isn't writing language (P6886) already available for this purpose? UWashPrincipalCataloger (talk) 00:47, 4 November 2020 (UTC)[reply]

Relaxing the constraint for primates

[edit]

Some primates such as Koko (Q1348219) have been taught human sign languages, which is why I expanded the constraint to also include primate (Q7380). It seems it even still causes a constraint violation, however. 🤔 NMaia (talk) 10:44, 4 May 2018 (UTC)[reply]

I'd rather not.
--- Jura 10:58, 4 May 2018 (UTC)[reply]
I'd use P31=person for such advanced primates (instead?). --Infovarius (talk) 16:11, 1 June 2018 (UTC)[reply]
It seems that 'person-animal' has now been created as a subclass of 'person', so no flags are raised at (for example) Koko's article. Arlo Barnes (talk) 19:24, 13 November 2019 (UTC)[reply]

Proficiency level

[edit]

Should this property have an accompanying qualifier about the level of proficiency? Now is not detailed enough and it seams that everyone speaks declared languages perfectly. --Милан Јелисавчић (talk) 19:14, 7 January 2019 (UTC)[reply]

It would be perfect, but how to determine it? I cannot say exact level (and it may vary with the time) even of my languages, what to say about others! --Infovarius (talk) 21:25, 3 August 2019 (UTC)[reply]
Well, Wikimedia has Q19842659, which is still subjective (although there is a scale to guide it somewhere). Arlo Barnes (talk) 19:26, 13 November 2019 (UTC)[reply]

Do ethnic groups occasionally speak languages?

[edit]

Right now, an ethnic group having a native language generates and error message, as anyone having a native language should also have a language spoken. But when a language spoken is added, it generates another error message because ethnic groups are not allowed to have spoken languages. Someone should either update the restrictions or stop Roma people from talking. Your choice. --Ehitaja (talk) 14:17, 2 August 2019 (UTC)[reply]

@Ehitaja: I've expanded the domain up to group of humans (Q16334295) - it should allow ethnic groups now. --Infovarius (talk) 21:30, 3 August 2019 (UTC)[reply]
Wonderful. I thank you in the name of those ethnic groups that do speak in a language. --Ehitaja (talk) 23:06, 3 August 2019 (UTC)[reply]
If there is consensus that this is an appropriate use of this property (and I don't see why it shouldn't be), then the description should be changed to "language(s) that a person or group speaks, writes or signs, including the native language(s)" (and likewise in every other language). I have often been in this situation and did not realize the property allowed this usage. Rigadoun (talk) 17:51, 26 February 2021 (UTC)[reply]

Is citation constraint really needed for this property?

[edit]

Today an editor added citation needed constraint to this property. Is a citation really needed even as just a suggestion constraint? It's not clear to me what citation would be used to justify a statement of language used. A reference to one of their publications? To their website? This constraint seems unnecessary to me. UWashPrincipalCataloger (talk) 21:11, 20 May 2021 (UTC)[reply]

@UWashPrincipalCataloger: I also don't believe it's needed, and don't agree with the change, and therefore reverted it.-- Darwin Ahoy! 02:52, 22 May 2021 (UTC)[reply]
@DarwIn: Thank you! UWashPrincipalCataloger (talk) 22:31, 25 May 2021 (UTC)[reply]

Labels in plural

[edit]

Hi,

Most properties (and more generally entities) have a label in singular. Why is this one plural?

Even if someone speak/write/sign multiple language (which is rare, the average is currently 1.1: https://qlever.cs.uni-freiburg.de/wikidata/O1BzQf ), each triples has only one object. The singular would make more sense.

Ping top-3 user of this property @Samatics, Olaf Kosinsky, DonKevin:

Cheers, VIGNERON (talk) 13:19, 6 September 2023 (UTC)[reply]

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