InChI Joins Smart Data Models: 1 Candidate Model for Chemical Structure Identifiers

Smart Data Models’ Candidates repository now includes a new candidate standard from chemistry: inchi, with 1 candidate model translated from InChI, the IUPAC International Chemical Identifier. The InChI software and documentation are published under the MIT licence. Like every candidate, the model comes with a JSON Schema, an NGSI-LD @context and all four example serializations (NGSI-v2 and NGSI-LD, key-values and normalized), each validated against its schema.

About InChI

InChI is the open, structure-based identifier for chemical substances, developed by IUPAC and maintained by the InChI Trust. It is computed from a chemical structure and written as a version prefix followed by layers (formula, connections, hydrogen atoms, charge, stereochemistry, isotopes…). Its hashed form, the 27-character InChIKey, is used to index and search chemical databases such as PubChem, ChEBI, ChEMBL and Wikidata. This translation is based on the Technical Manual and User Guide shipped with InChI Software v1.07.5.

The model

InChI is an identifier, not a data model: it defines no entities with state. So this candidate is small on purpose. It gives NGSI-LD a way to state, without ambiguity, which chemical an observation, analysis or product refers to.

Model What it records Attributes Example
ChemicalStructureIdentifier The InChI of one chemical structure: InChI string, InChIKey, AuxInfo, the layers parsed out of the string, the InChIKey blocks and the options used 22 L-alanine (PubChem CID 5950)

Real data

The example is L-alanine, with the InChI and InChIKey exactly as published by PubChem (US government public domain). The AuxInfo line was computed with the InChI library from PubChem’s structure and reproduces PubChem’s identifiers.

Translation notes

  • Source names. InChI, InChIKey and AuxInfo are kept verbatim; the layers use the labels of the Technical Manual (formula, connections, H_atoms, stereo, isotopic, fixed_H…), nested where the manual nests them.
  • Layers for querying. The layers are parsed from the InChI string, so you can filter by formula, by molecular skeleton (the first InChIKey block) or by stereo. The InChI string remains the authoritative value.
  • Linked identifiers. InChI and InChIKey map to the CHEMINF ontology terms; the other attributes point to the relevant page of the InChI Technical Manual.
  • Additions. The entity name, identifierKind (standard, non-standard or beta), the names of the InChIKey parts and softwareVersion are Smart Data Models additions, and the metadata documents them.

Try it, and tell us what’s missing

This is a Candidate: a first, carefully sourced translation that is not yet an official Smart Data Models subject. No official subject defines a chemical identifier today. The natural next step is to link to it from models that talk about chemicals, such as air quality observations or industrial process chemical analyses. InChI extensions for reactions (RInChI), mixtures (MInChI) or nanomaterials could follow if there is demand.

Browse the model, open an issue, or send a PR:
👉 https://github.com/smart-data-models/Candidates/tree/master/standards/inchi

Bookmark the permalink.

Comments are closed.