About BattINFO
Mission
Battery R&D runs on data that mostly cannot be reused: numbers locked in PDFs, spreadsheets with private column names, cycler exports whose meaning left the lab with the person who ran them. BattINFO's mission is to make battery data machine-readable, linked, and reusable, so that every cell, test, and dataset carries its own meaning and any tool or team can pick it up without asking.
We did not invent our own world. We build on open standards (EMMO, JSON-LD, JSON Schema, schema.org, DCAT, PROV) and make them usable by someone with a datasheet and an afternoon.
Why linked, federated data changes what battery research can do →
History
BattINFO began as an ontology: the Battery INterFace Ontology, developed in the European BIG-MAP project (part of the Battery 2030+ initiative) and now maintained as the EMMO battery domain. The ontology answered what battery concepts mean; what remained open was how a working scientist would actually use it.
This project is that answer: the implementation layer that turns the ontology into everyday tools, canonical JSON records with schemas, a Python library and CLI, automatic JSON-LD with persistent w3id.org/battinfo/… identifiers, and a publishing pipeline that ends in a citable DOI and a registry entry. It is open source (Apache-2.0) and developed in the open on GitHub.
The ecosystem
BattINFO is one layer of a larger open battery-data stack:
- EMMO domain-battery →
The ontology itself: the formal EMMO-based vocabulary of battery concepts that BattINFO implements and extends.
- Battery Genome →
The open platform where published BattINFO records become browsable cell pages, linked datasets, and federated profiles.
- battinfo-records →
The canonical record library: curated cell specs and organizations that anchor the registry.
- BIG-MAP →
The Battery 2030+ large-scale European research project this work grew out of.
- Battery Data Alliance →
Home of the Battery Data Format (BDF), the tidy tabular layer BattINFO converts raw cycler files into.
Get involved
Publish a dataset, register a cell spec, report a rough edge, or bring your tool's format to the converter matrix, every record published makes the shared library more useful. Start with your own data, or open an issue on GitHub.