@toon-format/spec 1.3.3 → 1.5.0

package/CHANGELOG.md

@@ -5,6 +5,34 @@ All notable changes to the TOON specification will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [1.5] - 2025-11-08
+
+### Added
+
+- Optional key folding for encoders: `keyFolding="safe"` mode with `flattenDepth` control to collapse single-key object chains into dotted-path notation (§13.4)
+- Optional path expansion for decoders: `expandPaths="safe"` mode to split dotted keys into nested objects, with conflict resolution tied to `strict` option (§13.4, §14.5)
+- IdentifierSegment terminology and path separator definition (fixed to `"."` in v1.5) (§1.9)
+- Deep-merge semantics for path expansion: recursive merge for objects, error on conflict when `strict=true`, last-write-wins (LWW) when `strict=false` (§13.4)
+
+### Changed
+
+- Both new features default to OFF and are fully backward-compatible
+- Safe-mode folding requires IdentifierSegment validation, collision avoidance, and no quoting
+
+## [1.4] - 2025-11-05
+
+### Changed
+
+- Removed JavaScript-specific normalization details from specification; replaced with language-agnostic requirements (Section 3)
+- Defined canonical number format for encoders: no exponent notation, no trailing zeros, no leading zeros except "0" (Section 2)
+- Clarified decoder handling of exponent notation and out-of-range numbers (Section 2)
+- Expanded `\w` regex notation to explicit character class `[A-Za-z0-9_]` for cross-language clarity (Section 7.3)
+- Clarified non-strict mode tab handling as implementation-defined (Section 12)
+
+### Added
+
+- Appendix G: Host Type Normalization Examples with guidance for Go, JavaScript, Python, and Rust implementations
+
 ## [1.3] - 2025-10-31
 
 ### Added

package/README.md

@@ -1,7 +1,7 @@
 # TOON Format Specification
 
-[![SPEC v1.3](https://img.shields.io/badge/spec-v1.3-lightgrey)](./SPEC.md)
-[![Tests](https://img.shields.io/badge/tests-306-green)](./tests/fixtures/)
+[![SPEC v1.5](https://img.shields.io/badge/spec-v1.5-lightgrey)](./SPEC.md)
+[![Tests](https://img.shields.io/badge/tests-323-green)](./tests/fixtures/)
 [![License: MIT](https://img.shields.io/badge/license-MIT-blue.svg)](./LICENSE)
 
 This repository contains the official specification for **Token-Oriented Object Notation (TOON)**, a compact, human-readable serialization format designed for passing structured data to Large Language Models with significantly reduced token usage.
@@ -10,12 +10,24 @@ This repository contains the official specification for **Token-Oriented Object
 
 [→ Read the full specification (SPEC.md)](./SPEC.md)
 
-- **Version:** 1.3 (2025-10-31)
+- **Version:** 1.5 (2025-11-10)
 - **Status:** Working Draft
 - **License:** MIT
 
 The specification includes complete grammar (ABNF), encoding rules, validation requirements, and conformance criteria.
 
+### New in v1.5
+
+- **Key Folding** (encode): Collapse nested single-key objects into compact dotted paths
+  - `{"a": {"b": {"c": 1}}}` → `a.b.c: 1`
+  - Opt-in via `keyFolding="safe"` with `flattenDepth` control
+- **Path Expansion** (decode): Expand dotted keys back to nested objects
+  - `a.b.c: 1` → `{"a": {"b": {"c": 1}}}`
+  - Opt-in via `expandPaths="safe"` with deep-merge semantics
+
+> [!NOTE]
+> Both features are opt-in to maintain backward compatibility.
+
 ## What is TOON?
 
 **Token-Oriented Object Notation** is a compact, human-readable serialization format designed for passing structured data to Large Language Models with significantly reduced token usage. It's intended for LLM input, not output.