Property talk:P700

From Wikidata
Jump to navigation Jump to search

Documentation

Kemler code
code describing the hazards of a chemical in transport
Descriptioncode describing the hazards of a chemical in tranport
RepresentsKemler codes (Q905863)
Data typeExternal identifier
Template parameterfr:infobox chimie, en:chembox, de:Chemikalien
Domain
According to this template: chemistry
According to statements in the property:
chemical substance (Q79529)
When possible, data should only be stored as statements
Allowed valuesX?[2-9][02-9][2-9]?
Examplesodium azide (Q407577)60
compressed air (Q143746)20
Methoxymethyl isocyanate (Q82002989)663
aluminium borohydride (Q3277682)X333
SourceADR 2011
Formatter URLhttps://mormegil.toolforge.org/propertylinker/kemlercode.php?code=$1
Tracking: usageCategory:Pages using Wikidata property P700 (Q47461896)
See alsoUN number (P695), UN classification code (P875), UN class (P874)
Lists
Proposal discussionProposal discussion
Current uses
Total59
Main statement5593.2% of uses
Qualifier46.8% of uses
Search for values
[create Create a translatable help page (preferably in English) for this property to be included here]
Type “chemical substance (Q79529): item must contain property “instance of (P31), subclass of (P279)” with classes “chemical substance (Q79529)” 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/P700#Type Q79529, SPARQL
Format “X?[2-9][02-9][2-9]?: value must be formatted using this pattern (PCRE syntax). (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/P700#Format, SPARQL
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/P700#Single value, SPARQL
Format “223|225|238|239|263|265|268|323|X323|333|X333|336|338|X338|339|362|X362|368|382|X382|423|X423|43|X432|446|462|X462|482|X482|50|539|55|556|558|559|56|568|606|623|638|639|642|663|664|665|668|X668|669|768|X80|823|839|X839|842|856|883|884|885|886|X886|89|90|99|20|22|23|25|26|28|30|33|36|39|40|44|46|48|64|65|66|68|69|70|78|80|83|84|85|86|88|38|58|59|60|63|X83|X88: value must be formatted using this pattern (PCRE syntax). (Help)
List of violations of this constraint: Database reports/Constraint violations/P700#Format, hourly updated report, 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/P700#Entity types
Scope is as main value (Q54828448): 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/P700#Scope, SPARQL