Property talk:P352

Format “([OPQ]\d\d|[A-Z]\d[A-Z])[A-Z\d][A-Z\d]\d([A-Z][A-Z\d]{2}\d)?”: value must be formatted using this pattern (PCRE syntax). (Help)

List of violations of this constraint: Database reports/Constraint violations/P352#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/P352#Unique value, SPARQL (every item), SPARQL (by value)

Single value: this property generally contains a single value. (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/P352#Single value, SPARQL

Type “protein (Q8054), peptide (Q172847)”: item must contain property “instance of (P31), subclass of (P279)” with classes “protein (Q8054), peptide (Q172847)” 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/P352#Type Q8054, Q172847, 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/P352#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/P352#Scope, SPARQL

This property is being used by: it:Template:Proteina ca:Plantilla:Proteïna, ca:Plantilla:Infotaula proteïna ga:Teimpléad:WD Bosca Sonraí Comhdhúil Cheimiceach de:Vorlage:UniProt Please notify projects that use this property before big changes (renaming, deletion, merge with another property, etc.)

I suppose there are both a human and a mouse ID? How do we distinguish? — Fnielsen (talk) 14:44, 17 April 2013 (UTC)[reply]

Any UniProt ID (and any protein in nature, for that matter) is associated with a specific taxon so they are already "distinguished". Wikidata proteins having a UniProt ID therefore should also have a "found in taxon" statement. If you want to make a generic protein item this is then the same as a protein family. --SCIdude (talk) 08:10, 30 August 2019 (UTC)[reply]

UniProt (Q905695) also offers a taxonomic database, see Template:UniProt Taxonomy (Q14444500). It is meant for instances of taxon (Q16521), but is uses all-numeric IDs, such as Nymphon stroemi (Q2320595) => 511525. Should this be handled by a different property? LaddΩ chat ;) 12:16, 11 March 2014 (UTC)[reply]

I don't think so (and the bot devs apparently don't either). Our "found in taxon" uses the WikiSpecies tree of life, and if you find taxa in UniProt not covered here, our tree should be augmented. --SCIdude (talk) 08:14, 30 August 2019 (UTC)[reply]

The url pattern currently uses www.uniprot.org but for wikidata this should be purl.uniprot.org. Changing this would make it easier for doing queries from sparql.uniprot.org into wikidata without conversion.  – The preceding unsigned comment was added by 129.194.231.5 (talk • contribs).

In the GO consortium we changed our prefix from UniProt to UniProtKB several years ago, on request of UniProt. See GO Prefix registry entry. I prefer the simpler UniProt as a prefix, but we are locked into UniProtKB in GO. Should we register this as a synonym prefix in Wikidata? Cmungall (talk) 02:03, 26 March 2017 (UTC)[reply]

Currently, the example on this page (RELN) is neither a UniProt entry name (which would be RELN_HUMAN) or a UniProt Accession (which would be P78509). The regular expression provided on the page is actually for UniProt Accessions, not identifiers (see here). Basically, this page should be split for UniProt entry names and UniProt accession numbers. For more on this difference and split see official documentation here.

Splitting would not be as intended, the intended use of this property is for accessions, as this allows also linking to UniProt. The example actually linked to the gene item, which I fixed. --SCIdude (talk) 14:47, 3 May 2020 (UTC)[reply]