Property talk:P566
Jump to navigation
Jump to search
Documentation
has basionym
the legitimate, previously published name on which a new combination or name at new rank is based
the legitimate, previously published name on which a new combination or name at new rank is based
[create Create a translatable help page (preferably in English) for this property to be included here]
Single value: this property generally contains a single value. (Help)
List of violations of this constraint: Database reports/Constraint violations/P566#Single value, hourly updated report, SPARQLExceptions 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/P566#Item P225, search, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P566#Item P225, search, SPARQL
Property “taxon name (P225)” declared by target items of “has basionym (P566)”: If [item A] has this property with value [item B], [item B] is required to have property “taxon name (P225)”. (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/P566#Target required claim P225, SPARQL, SPARQL (by value)
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/P566#Scope, hourly updated report, SPARQLInverse property of “basionym of (P12766)”:
if [item A] has this property (has basionym (P566)) linked to [item B],
then [item B] should also have property “basionym of (P12766)” linked to [item A]. (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303). if [item A] has this property (has basionym (P566)) linked to [item B],
then [item B] should also have property “basionym of (P12766)” linked to [item A]. (Help)
List of violations of this constraint: Database reports/Constraint violations/P566#inverse, 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/P566#Entity types
Conflicts with “basionym of (P12766)”: this property must not be used with the listed properties and 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/P566#Conflicts with P12766, search, SPARQL
Conflicts with “original combination (P1403)”: this property must not be used with the listed properties and 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/P566#Conflicts with P1403, search, SPARQL
This property is being used by:
Please notify projects that use this property before big changes (renaming, deletion, merge with another property, etc.) |
|
|
Self-referencing
[edit]Hi @Hofoen, Succu, MargaretRDonald, Lichenes, Thiotrix, Strobilomyces:
I noticed that Zorion recently add several times this property on items pointing to the item itself in value (which is usually called "self-referencing" and is often a mistake). See for instance Special:Diff/2281572154 on Clitocybe agrestis (Q10455174) (and see this query https://w.wiki/CFWf for a list of all self-references for this property).
What do you think, is it actually correct to do a self-reference here?
Cheers, VIGNERON (talk) 15:21, 30 November 2024 (UTC)
- No, it is not correct, because a species name cannot be the basionym of itself. It can be the basionym of a species name in another genus. The editor should be informed, that this self-referencing use of basionym is an error. Kind regards, Thiotrix (talk) 15:54, 30 November 2024 (UTC)
- OK I didn't know. --Zorion (talk) 18:05, 30 November 2024 (UTC)
- Hello. Yes, the official definition of "basionym" implies that a newly devised species name is not a basionym of itself. From a data-processing point of view, it might seem logical to make it self-referencing, but that is wrong. Best wishes, Strobilomyces (talk) 11:23, 9 December 2024 (UTC)
Categories:
- All Properties
- Properties with wikibase-item-datatype
- Properties used on 100000+ items
- Properties with single value constraints
- Properties with constraints on items using them
- Properties with target required claim constraints
- Properties with scope constraints
- Properties with inverse constraints
- Properties with entity type constraints
- Properties with conflicts with constraints
- Taxonomy properties
- Person properties