Property talk:P1412

From Wikidata
Jump to: navigation, search

Documentation

languages spoken, written or signed
language(s) that a person speaks or writes, including the native language(s)
Represents no label (Q6486795)
Data type Item
Domain
According to this template: person (Q215627)
According to statements in the property:
person (Q215627) and fictional character (Q95074)
When possible, data should only be stored as statements
Allowed values languoid (Q17376908) (note: this should be moved to the property statements)
Example Margrethe II of Denmark (Q102139)Danish (Q9035), English (Q1860), French (Q150), Swedish (Q9027), German (Q188) and Faroese (Q25258)
Confucius (Q4604)Old Chinese (Q35137)
Source external reference, Wikipedia (note: this information should be moved to a property statement; use property source website for the property (P1896))
Tracking: usage Category:Pages using Wikidata property P1412 (Q23909087)
See also native language (P103), language used (P2936), official language (P37), language of work or name (P407)
Lists
Proposal discussion Property proposal/Archive/24#P1412
Current uses 551,030
[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).
List of this constraint violations: Database reports/Constraint violations/P1412#Value type Q17376908, hourly updated report, SPARQL
Type “person (Q215627), fictional character (Q95074): element must contain property “instance of (P31)” with classes “person (Q215627), fictional character (Q95074)” or their subclasses (defined using subclass of (P279)).
Exceptions are possible as rare values may exist.
List of this constraint violations: Database reports/Constraint violations/P1412#Type Q215627, Q95074, SPARQL
Value only: this property can only be used in value (not qualifier or source).
Exceptions are possible as rare values may exist.
List of this constraint violations: Database reports/Constraint violations/P1412#Value only, SPARQL
Contemporaries:
if [item A] has this property (languages spoken, written or signed (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.
List of this constraint violations: Database reports/Constraint violations/P1412#Contemporary
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.
List of this constraint violations: Database reports/Constraint violations/P1412#Contemporary, SPARQL
This property is being used by:

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)

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

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)

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

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)

  • 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)
@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)
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)