+1
-1
| { | ||
| "name": "ploon", | ||
| "version": "1.0.1", | ||
| "version": "1.0.2", | ||
| "description": "Path-Level Object Oriented Notation - The Most Token-Efficient Format for Nested Hierarchical Data", | ||
@@ -5,0 +5,0 @@ "type": "module", |
+33
-11
@@ -21,15 +21,25 @@ # ๐ PLOON: Path-Level Object Oriented Notation | ||
| ### Token Efficiency | ||
| ### Key Findings | ||
| PLOON achieves **superior token efficiency** compared to all formats, including TOON: | ||
| | Metric | vs JSON | vs XML | vs YAML | vs TOON | | ||
| |--------|---------|--------|---------|---------| | ||
| | **File Size (Standard)** | 66.2% โ | 62.4% โ | 48.5% โ | **36.0% โ** | | ||
| | **File Size (Minified)** | 66.5% โ | 62.8% โ | 49.0% โ | **36.5% โ** | | ||
| | **Token Count (Standard)** | 49.1% โ | 48.7% โ | 24.8% โ | **14.1% โ** | | ||
| | **Token Count (Minified)** | 49.1% โ | 48.7% โ | 24.8% โ | **14.1% โ** | | ||
| | **Round-Trip Accuracy** | - | - | - | **100%** (5/5) | | ||
| | Feature | PLOON | TOON | | ||
| |---------|-------|------| | ||
| | **Hierarchy** | Path-based (depth:index) | Indentation-based | | ||
| | **Advantage** | Constant token cost per path | Human-readable | | ||
| | **Best for** | Deep nesting (2+ levels) | Flat/shallow data | | ||
| | **Token savings** | **44% vs JSON** (standard)<br>**47% vs JSON** (minified) | ~40% vs JSON | | ||
| | **vs TOON** | **4.4% better** (standard)<br>**9.4% better** (minified) | baseline | | ||
| | **Deep nesting** | **+56% vs TOON** (companies dataset) | Poor scaling | | ||
| **PLOON beats TOON on BOTH metrics:** | ||
| - 36.0% smaller file size (36.5% minified) | ||
| - 14.1% fewer tokens with depth:index format + nested object support | ||
| ### Cost Savings (GPT-5 @ $1.25/1M tokens) | ||
| - **Average savings:** $616.25 per 1M API calls vs JSON | ||
| **ROI Example (10M API calls/month):** | ||
| - With JSON: $18,707.48/month | ||
| - With PLOON: $12,544.98/month | ||
| - **Monthly Savings: $6,162.50** (32.9% reduction) | ||
| --- | ||
@@ -389,3 +399,5 @@ | ||
| Paths use `depth:index` format for constant token cost: | ||
| PLOON uses dual path notation to distinguish arrays from objects: | ||
| **Arrays** use `depth:index` format: | ||
| - `1:1` - First item at depth 1 | ||
@@ -396,2 +408,12 @@ - `2:1` - First child (depth 2) of item 1:1 | ||
| **Objects** use `depth ` format (depth + space): | ||
| - `2 ` - Object at depth 2 | ||
| - `3 ` - Nested object at depth 3 | ||
| - `4 ` - Deeply nested object at depth 4 | ||
| **Schema Notation:** | ||
| - Arrays: `fieldName#(nestedFields)` - e.g., `items#(id,name,price)` | ||
| - Objects: `fieldName{nestedFields}` - e.g., `address{street,city,zip}` | ||
| - Both can nest infinitely: `customer{name,address{city,country{code,name}}}` | ||
| ### Escaping | ||
@@ -398,0 +420,0 @@ |
133735
0.55%540
4.25%