Schema Validation

TIDAS data structures are defined with JSON Schema. The supported batch validation entry point is tidas validate in the unified Rust CLI. It uses the integrity-locked JSON Schema, ILCD XSD, and rules assets embedded in the installed version, without an external source tree or Python environment. Record the actual binary and asset fingerprints with tidas version --format json; use tidas-tools Releases as the release authority.

Validate a TIDAS JSON package

tidas validate ./tidas-package \
  --input-format tidas-json \
  --issues ./issues.jsonl \
  --format json

• The positional input directory contains the canonical TIDAS category subdirectories.

• --issues atomically writes the complete deterministic JSONL issue stream.

• --format json keeps stdout to a stable machine-readable report; diagnostics and progress use stderr.

• --report <path> atomically persists the complete report.

Run Schema diagnostics only

tidas validate ./tidas-package \
  --input-format tidas-json \
  --schema-only \
  --format json

--schema-only checks the Schema layer only. It skips full package, reference, and conversion-profile checks, so it does not prove eILCD convertibility and is not complete conformance evidence.

Validate an ILCD XML package

tidas validate ./ilcd-package \
  --input-format ilcd-xml \
  --issues ./issues.jsonl \
  --format json

The validator uses only the integrity-locked XSD assets embedded in the binary and reuses offline validation contexts.

Inspect validator fingerprints

Record the validation protocol, engine, and Schema-lock fingerprints before a reproducible CI or batch run:

tidas validate --describe --format json
tidas version --format json

The document-validation-batch.v1 protocol validates exactly the manifest documents and produces deterministic issue events plus a final evidence hash:

tidas validate ./batch-root \
  --protocol document-validation-batch.v1 \
  --input-manifest ./document-validation-batch.v1.jsonl \
  --events ./validation-events.jsonl \
  --format json

Validation Content Overview

TIDAS validation combines two types of checks:

1. Structure Validation (JSON Schema Standard)

• Check for missing fields (required)

• Check field type matching (string, number, etc.)

• Check field values against definitions (format, enum, etc.)

• Support inter-module reference resolution ($ref)

2. Package and classification logic

For classification structures like flows, processes, sources:

• Hierarchy Check: Verify @level sequence is correct

• Code Rules: Verify child items use parent item codes as prefix

• Process Classification Industry Matching: Verify industry codes comply with national standard mapping logic

• Reference and Package Checks: Apply cross-module and package constraints from locked assets

Validation Result Output

The normal report contains bounded issue counts and the issue-stream hash; --issues preserves every issue. Document issues represent a completed scan, while the report and exit status distinguish data issues from protocol or runtime failures. Automation should parse the stable --format json report instead of matching human-readable text.

For JSON Schema fields and modules, see Data Structure (JSON Schema). For installation, platform support, and legacy-command migration, see the unified TIDAS CLI.