Property talk:P1992

Format “[0-9A-F]{8}-[0-9A-F]{4}-[0-9A-F]{4}-[0-9A-F]{4}-[0-9A-F]{12}”: value must be formatted using this pattern (PCRE syntax). (Help)

List of violations of this constraint: Database reports/Constraint violations/P1992#Format, hourly updated report, SPARQL

Distinct values: this property likely contains a value that is different from all other items. (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/P1992#Unique value, SPARQL (every item), SPARQL (by value)

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/P1992#Entity types

Scope is as main value (Q54828448), as reference (Q54828450): 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/P1992#Scope, SPARQL

Type “taxon (Q16521), taxonomic treatment (Q32945461)”: item must contain property “instance of (P31)” with classes “taxon (Q16521), taxonomic treatment (Q32945461)” 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/P1992#Type Q16521, Q32945461, SPARQL

This property is being used by: ar:قالب:معرفات الأصنوفة/نسخة Please notify projects that use this property before big changes (renaming, deletion, merge with another property, etc.)

There are currently some on Wikidata:Database reports/uuid. --- Jura 08:34, 9 November 2019 (UTC)[reply]

One of the two regexes allows both formats, but the property constraint is uppercase only. Default format for UUID is lowercase (at least for urn:uuid: ). Can the values be converted to lowercase? --- Jura 09:05, 9 November 2019 (UTC)[reply]

Unfortunately, right now for for https://treatment.plazi.org/id/6D0C7764-FFDD-FFEE-07AA-FC36FDB0FB07.rdf rdf:about is set to http://treatment.plazi.org/id/6D0C7764FFDDFFEE07AAFC36FDB0FB07, which means that linked data won't link after importing to external system. So we just have a link to RDF, not an RDF resource. Lockal (talk) 03:42, 2 February 2023 (UTC)[reply]

Hello, it seems that this property is now used in a new way by BiodiversityBot, e.g. in Perinereis kaustiana Teixeira, Fourreau, Sampere-Valverde & Carvalho 2024 (Q125621827).

The issue is that currently we have item-requires-statement constraint (Q21503247) property (P2306) taxon name (P225).

I suggest to remove that constraint, and instead to put a subject type constraint (Q21503250) class (P2308) taxon (Q16521) & taxonomic treatment (Q32945461).

In case there is of no objection, I will do it soon. Christian Ferrer (talk) 07:55, 23 May 2024 (UTC)[reply]