toon-format--toon
Johann Schopplich
5b66523e42
- bump @toon-format/spec to ^3.3.0; update SPEC.md pointer and badges - docs: align number-form prose with §2 carve-out (canonical in [1e-6, 1e21) or zero; exponent form permitted outside) - docs/reference/spec.md: add lowercase booleans/null to encoder checklist; add Java to Appendix F language list - docs/reference/efficiency-formalization.md: drop overstated "matching TOON's requirement" claim - packages/toon/README.md: drop "What's New in v3.2" section (now stale) All 593 tests pass (packages/toon: 497, packages/cli: 96). Encoder remains conformant by default under the v3.3 §2 carve-out via String(value).
29 行
1.3 KiB
Markdown
29 行
1.3 KiB
Markdown
# TOON Specification
|
|
|
|
The TOON specification has moved to a dedicated repository: [github.com/toon-format/spec](https://github.com/toon-format/spec)
|
|
|
|
## Current Version
|
|
|
|
**Version 3.3** (2026-05-21)
|
|
|
|
## Quick Links
|
|
|
|
- **[Full Specification](https://github.com/toon-format/spec/blob/main/SPEC.md)** - Complete technical specification
|
|
- **[Changelog](https://github.com/toon-format/spec/blob/main/CHANGELOG.md)** - Version history
|
|
- **[Examples](https://github.com/toon-format/spec/tree/main/examples)** - Example TOON files
|
|
- **[Conformance Tests](https://github.com/toon-format/spec/tree/main/tests)** - Language-agnostic test fixtures for implementations
|
|
- **[Contributing](https://github.com/toon-format/spec/blob/main/CONTRIBUTING.md)** - How to propose spec changes
|
|
|
|
## Why a Separate Repo?
|
|
|
|
The specification has been moved to `toon-format/spec` to:
|
|
|
|
- Provide a canonical, language-agnostic source of truth
|
|
- Enable independent versioning of spec and implementations
|
|
- Support the growing community of TOON implementations across multiple languages
|
|
- Facilitate collaboration on spec evolution through a dedicated RFC process
|
|
|
|
## This Repository
|
|
|
|
This repository (`toon-format/toon`) remains the **reference implementation** in TypeScript/JavaScript. For specification discussions, issues, and contributions, please use the spec repository.
|