Data Schema

JSON schema documentation for renderer metadata, benchmarks, scenes, and the taxonomy graph. All data files validate against JSON Schema Draft 2020-12.

Renderer Metadata

One file per renderer. Contains technical metadata, feature flags, editorial strengths/limitations, and community links.

Location: /data/renderers/{id}.json

Schema: /schemas/renderer.schema.json

Required: id, name, version, description, technique, language, license, platforms, repository, first_release, status, tags, strengths, limitations, best_for, features

Benchmark Results

One file per benchmark run (renderer × scene × hardware). Includes render time, memory usage, image quality metrics, and convergence data. Generate these with `renderscope publish` rather than writing them by hand.

Location: /data/benchmarks/{scene}-{renderer}-{hardware}.json

Schema: /schemas/benchmark.schema.json

Required: id, renderer, renderer_version, scene, timestamp, hardware, settings, results

Scene Metadata

One file per standard benchmark scene. Describes geometry complexity, lighting, materials, what rendering features the scene tests, and where each file format is downloaded from. The Python package's scene manifest is generated from these files, so the CLI and the site never describe a scene differently.

Location: /data/scenes/{id}.json

Schema: /schemas/scene.schema.json

Required: id, name, description, complexity, tests, source, available_formats, sources

Taxonomy Graph

Classification graph connecting renderers and technique categories. Defines nodes (renderers + categories) and edges (relationships).

Location: /data/taxonomy.json

Schema: /schemas/taxonomy.schema.json

Required: nodes, edges

Quick Start

# 1. Copy the template
cp data/renderers/_template.json data/renderers/your-renderer.json

# 2. Edit the file — fill in required fields, remove __comment_* keys

# 3. Validate
python scripts/validate_data.py

See the Contributing guide for detailed step-by-step instructions.

Back to Docs