Concepts

The design, in reading order: the big picture first, then the record model built up from materials to datasets, then the contracts the infrastructure holds.

The big picture

• How BattINFO is built
• BattINFO / Domain-Battery Target Architecture
• Identifiers & PURLs
• Data federation

The record model — spec and instance, from materials up

Everything in BattINFO is a spec (the reusable description) or an instance (the physical thing or event it describes). These pages walk the model bottom-up:

• Materials
• Components
• Cell specs
• Cells
• Test specs
• From cell to dataset

The contracts

What the infrastructure guarantees, and the interface specifications consumers can build against:

• The infrastructure contract
• Ingest Manifest Contract
• BattINFO CLI Specification (Scope)