Property talk:P427

Latest comment: 7 months ago by Maculosae tegmine lyncis in topic Constraints

Documentation

taxonomic type
name-bearing genus or species of this nominal family or genus (or subfamily or subgenus)
DescriptionThis is used to indicate the type genus of this family (or subfamily, etc) or the type species of this genus (or subgenus, etc). It is not intended to indicate a type specimen, etc.
Representsnomenclatural type (Q116538381)
Data typeItem
Domaintaxon (Q16521)
Allowed valuestaxon (Q16521) (note: this should be moved to the property statements)
ExampleMethanomicrobiales (Q4044130)Methanomicrobium (Q4044129)
Drosophila (Q312154)Drosophila funebris (Q3715460)
Acanthocalycium ferrarii (Q337692)Rausch 572 (Q19359611)
Cactaceae (Q14560)cactus (Q10856673)
Lists
Proposal discussionProposal discussion
Current uses
Total32,729
Main statement32,704>99.9% of uses
Qualifier24<0.1% of uses
Reference1<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 “taxon (Q16521), type (Q3707858): 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 taxon (Q16521), type (Q3707858) (or a subclass thereof). (Help)
List of violations of this constraint: Database reports/Constraint violations/P427#Value type Q16521, Q3707858, hourly updated report, SPARQL
Type “taxon (Q16521): item must contain property “instance of (P31)” with classes “taxon (Q16521)” 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/P427#Type Q16521, SPARQL
Item “taxon name (P225): Items with this property should also have “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/P427#Item P225, search, SPARQL
Item “parent taxon (P171): Items with this property should also have “parent taxon (P171)”. (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/P427#Item P171, search, SPARQL
Item “taxon rank (P105): Items with this property should also have “taxon rank (P105)”. (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/P427#Item P105, search, SPARQL
Qualifiers “object has role (P3831): this property should be used only with the listed qualifiers. (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/P427#allowed qualifiers, SPARQL
Scope is as main value (Q54828448), as qualifier (Q54828449): 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/P427#Scope, SPARQL
Allowed entity types are Wikibase item (Q29934200), Wikibase MediaInfo (Q59712033): 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/P427#Entity types

Remark edit

Types are nomenclatural in nature rather than taxonomic. A type can be several things: it is safe to say that the type of a name of a species (or subspecies, etc) is usually a type specimen. However, this is a rather general statement which can be misread all too easily.

A statement often encountered is that a type always is a type specimen, and this is not correct. What would be correct is that in zoology a type of a name of a species or subspecies always is a type specimen (if in fact there is a type, and there may not be). This statement is not correct for algae, fungi & plants, or for prokaryotes. It also would not be correct to say that in zoology a type always is a type specimen, as the type of a name of a genus or subgenus is a species (the type species), and the type of a name of a family, subfamily, etc is a genus (the type genus). Etc.

P.S. Note that a type does not define a taxon. Defining a taxon is done by a taxonomist, and a particular taxon (with one particular fixed type) may have any number of competing definitions (circumscriptions). The function of a type is to act as an anchor for a taxon: as scientific names are connected to types, types are vital for determining the correct name. - Brya (talk) 05:10, 12 July 2013 (UTC)Reply

Problem? edit

What about the type for a species, which is a physical specimen held somewhere? How is this accommodated here? (Or do we only envisage types above the species level, but even they are anchored by a paricular physical (in general) specimen... MargaretRDonald (talk) 23:49, 17 September 2018 (UTC)Reply

I posted this question on Wikidata talk:WikiProject Taxonomy. — The Erinaceous One 🦔 07:26, 6 January 2023 (UTC)Reply

Constraints edit

Hello, some changes I made have been reverted; see the taxonomic type (P427) entry on Mellivora (Q13564654) and Articles 67ff. of International Code of Zoological Nomenclature (Q13011) for how this is/was working. Is there a reason for the reversion? Thank you, Maculosae tegmine lyncis (talk) 21:50, 13 September 2023 (UTC)Reply

Return to "P427" page.