Introduction to TIDAS Schema
TIDAS Schema uses JSON Schema to describe LCA dataset objects, classification vocabularies, and shared types: what the 18 published logical contract Schemas and the viewer projection each cover, how far ILCD concepts are carried forward, and why passing JSON Schema is not proof of ILCD/eILCD conformance.
TIDAS Schema uses JSON Schema to describe lifecycle assessment (LCA) dataset objects, classification vocabularies, and shared types. It carries forward relevant ILCD concepts and names for JSON workflows. Whether a particular dataset is compatible with ILCD/eILCD still depends on the selected profile, field values, and the results of conversion and validation. Passing JSON Schema alone is not proof of ILCD/eILCD conformance or round-trip conversion.
Browse and download the published TIDAS JSON Schema files from this site's repository
Which files are available?
- Downloadable JSON files
- 19
- Rule files used to check data
- 18
- LCA data types
- 8
- Classification tables
- 9
- Shared field rules
- 1
- Structure used only by this website
- 1
See the versioned TIDAS Schema 0.1.0 entry for the first standalone specification release. The unversioned directory remains the site's previous publication baseline.
The public directory contains 18 logical contract Schemas: 8 dataset objects, 9 classification vocabularies, and 1 shared-types file. A nineteenth JSON asset is a viewer projection derived from the shared types. It exists only for documentation presentation and must not be used for validation or conformance. A matching file name in the tools lock does not assert structural or byte-for-byte parity.
Technical boundary
- Structural contracts: JSON Schema defines field types, hierarchy, references, and machine-enforceable structural constraints.
- Modular composition: object Schemas refer to shared types and classification vocabularies; consumers should resolve references from the chosen root object Schema.
- Diagnostics are not conformance:
tidas validate --schema-onlyperforms Schema-layer diagnostics only and does not prove eILCD convertibility. For a conformance conclusion, run fulltidas validatewith the applicable profile and perform an actual conversion check when an exchange format is required. - Observable version:
tidas-toolsReleases is the release authority. Runtidas version --format jsonto inspect the installed binary version, contract Schemas, and embedded asset fingerprints.
Next steps
Choose a root object under Data Structure (JSON Schema), assemble the referenced data, and then follow Schema Validation for Schema diagnostics and full validation.