Property talk:P4132

Documentation

• Start a query
• Current uses
• Statistics by class
• List of values
• List of qualifiers
• Count

linguistic typology
classification of languages according to their linguistic trait (as opposed to historical families like romance languages)

Represents	linguistic typology (Q192625), linguistic typology (Q72775801)
Data type	Item
Domain	languoid (Q17376908)
Example	English (Q1860) → subject–verb–object (Q651641) fusional language (Q318917) nominative–accusative language (Q178435) stress-timed language (Q7888721) Láadan (Q35757) → verb–subject–object (Q166097) tonal language (Q191328)
Tracking: usage	Category:Pages using Wikidata property P4132 (Q63164409)
Lists	Items with the most statements of this property Count of items by number of statements (chart) Items with the most statements Items with the fewest statements Count of items by number of sitelinks (chart) Items with the most sitelinks Items with the most sitelinks, but no link to one Wikipedia (sample: Welsh Wikipedia, cywiki) Items with the fewest sitelinks Most linked wikis Items with the most identifier properties By value of property Most statements Fewest statements Most sitelinks Most linked wikis Total of sitelinks on items Most identifiers Fewest identifiers Items with no other statements Most recently created items Items with novalue claims Items with unknown value claims Usage history (total) Usage history (main statement) Chart by item creation date Database reports/Complex constraint violations/P4132 Database reports/Constraint violations/P4132 Map Random list
Proposal discussion	Proposal discussion
Current uses	Total 2,590 Main statement 2,584 99.8% of uses Qualifier 6 0.2% of uses
Search for values

[create Create a translatable help page (preferably in English) for this property to be included here]

Type “languoid (Q17376908)”: item must contain property “instance of (P31)” with classes “languoid (Q17376908)” or their subclasses (defined using subclass of (P279)). (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/P4132#Type Q17376908, SPARQL

Scope is as main value (Q54828448): the property must be used by specified way only (Help)

List of violations of this constraint: Database reports/Constraint violations/P4132#Scope, hourly updated report, 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/P4132#Entity types

Use instead of P31/P279
values used with this property shouldn't be in P31/P279 (Help)
Violations query: SELECT ?item ?value { ?item wdt:P4132 ?value ; ( wdt:P31 \u007C wdt:P279 ) ?value . } LIMIT 100
List of this constraint violations: Database reports/Complex constraint violations/P4132#Use instead of P31/P279

Adding word order statements from categories

I statements based on categories added.

I used enwiki/frwiki (Q9121459).

Should be used all categories for statements.

Can add more statements you.

--- Jura 12:43, 21 July 2017 (UTC)

typing property

Missed the creation proposition, but I would have opposed. There is many way to classify and a metaclass for languages + P31 would have done the trick as well. Properties union of (P2737) and disjoint union of (P2738) can describe further the ontology.

@Pamputt: « I think a more specific property would make things clearer » : can you explain how so ? I fail to see why. author  TomT0m / talk page 10:45, 25 July 2017 (UTC)

author  TomT0m / talk page 10:45, 25 July 2017 (UTC)

@TomT0m: I am not an ontology expert so I when said this new property "would make things clearer", it means that I prefer to use a specific property instead of a generic (and quite abstract) one. It is more or less the same idea that to have a property for each social network (e.g. Instagram username (P2003)) instead of only website username or ID (P554). This means that people who wants to contribute on languages may be aware of linguistic typology (P4132) that is much more specific than instance of (P31) (or other generic one) Pamputt (talk) 12:22, 25 July 2017 (UTC)

@Pamputt: Not the same … there is a formater uri for external id database. The point of using instance of (P31) is that you don’t even have to be aware that there is a specific typology property. Also there is several classifications by typology : https://www.britannica.com/science/linguistics/Language-classification . This problems do not seem to be addressable by a specific property who do not have the same problems as P31, so I think it’s a naive solution who does not really help and simplify anything … But this is my opinion. This introduces confusion by introducing several ways to do the same things. And maintenance effort to normalize, as a consequence.

for example take the feature « languages with a high ratio of consonants to vowels from languages with a low ratio of consonants to vowels ». This may be a criteria for classification of languages. We could definitely have a property « ratio of consonants to vowels » specific to languages. No need of a typology property for this « The problem lies in deciding what significance should be attached to particular typological characteristics » -> this is a problem that any classification (of anything) have !

and this is why I think we should focus on P31 for this. If we have a « phonemic inventory » property for example, and a type « Y language » defined by « language with a high phonemic inventory and a low ratio of consonants to vowels », we can easily replace the « typology : Y language » by a sparql query associated to the « Y language » class item or a computation of a lua code of the infobox. Here I think using a specific property will just encourage people to build their own custom solution for linguistic failing to notice they share the same problem with any field and reuse the solutions. author  TomT0m / talk page 13:02, 25 July 2017 (UTC)

I guess the question is why it didn't work out with P31/P279 over the last five years.
--- Jura 13:31, 25 July 2017 (UTC)

Because Pamputt did not launched an impulse ? author  TomT0m / talk page 13:43, 25 July 2017 (UTC)

Looks like it works out with P4132.
--- Jura 14:11, 25 July 2017 (UTC)

It would have if asked on PC how to without à PP. Independant. author  TomT0m / talk page 16:38, 25 July 2017 (UTC)

Do we have sample where this worked out?
--- Jura 07:53, 28 July 2017 (UTC)