Property talk:P1843

Documentation

taxon common name
common or vernacular name of a biological taxon

Represents	common name (Q502895)
Data type	Monolingual text
Domain	According to this template: taxon (Q16521) According to statements in the property: taxon (Q16521) and polyphyletic common name (Q55983715) When possible, data should only be stored as statements
Allowed values	[^\/]*
Example	House Sparrow (Q14683) → House Sparrow
Source	http://www.soortenbank.nl/ http://plants.usda.gov/core/profile?symbol=PSME https://www.dyntaxa.se/taxon/info/2000976
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 most identifier properties Items with no other statements <most recently created items> Items with novalue claims Items with unknown value claims Usage history Chart by item creation date Database reports/Constraint violations/P1843 <random list>
Proposal discussion	Proposal discussion
Current uses	144,248

Explanations [Edit]

Guidelines by languageEdit

FrenchEdit

The first word of compound names and the following words are uppercaseed only if they are proper names or species names, but not the adjectives.

Correct examples: "Grand Boucage", "Cyclamen à fleur immaculée", "Cyclamen à feuille de Lierre" and "Cyclamen de Perse", etc.

Type “taxon (Q16521), polyphyletic common name (Q55983715)”: element must contain property “instance of (P31)” with classes “taxon (Q16521), polyphyletic common name (Q55983715)” or their subclasses (defined using subclass of (P279)). (Help)
Exceptions are possible as rare values may exist.
List of this constraint violations: Database reports/Constraint violations/P1843#type Q16521, Q55983715, SPARQL, SPARQL (new)

Item “taxon name (P225)”: Items with this property should also have “taxon name (P225)”. (Help)
Exceptions are possible as rare values may exist.
List of this constraint violations: Database reports/Constraint violations/P1843#Item P225, SPARQL, SPARQL (new)

Format “[^\/]*”: value must be formatted using this pattern (PCRE syntax). (Help)
Exceptions are possible as rare values may exist.
List of this constraint violations: Database reports/Constraint violations/P1843#Format, SPARQL, SPARQL (new)

Scope is as main value (Q54828448): the property must be used by specified way only (Help)
List of this constraint violations: Database reports/Constraint violations/P1843#scope, hourly updated report, SPARQL, SPARQL (new)

This property is being used by:

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

Strange propertyEdit

Many times it simply repeats label and aliases. --Infovarius (talk) 17:41, 29 June 2016 (UTC)

And this is strange? Why, Infovarius? --Succu (talk) 20:46, 29 June 2016 (UTC)

Because it is duplication. --Infovarius (talk) 18:35, 5 July 2016 (UTC)

If taxon name (P225) repeats labels and/or aliases because taxon common name (P1843) is present this is not strange, Infovarius? --Succu (talk) 18:38, 5 July 2016 (UTC)

taxon name (P225) has mostly single (or a few) values, it's standardized. This property can have hundreds/thousands of values, several per each language. Which are already at labels/aliases. --Infovarius (talk) 19:18, 5 July 2016 (UTC)

So what? Having a source for labels/aliases (some of them are abstruse) is inconvenient? --Succu (talk) 19:32, 5 July 2016 (UTC)

I do not appreciate and understand the "so what". It is duplication. The notion of sources of labels has been shot down in the past so this is that same discussion through the back-door. There is no point to them so imho this property is superfluous. Thanks, GerardM (talk) 12:08, 15 October 2017 (UTC)