From 2405be6a666c09673f2c97dd60383df4e85b73aa Mon Sep 17 00:00:00 2001 From: mikael-lovqvists-claude-agent Date: Tue, 24 Mar 2026 00:00:03 +0000 Subject: [PATCH] future-plans: semantically-aware formatting for acronyms and proper names Co-Authored-By: Claude Sonnet 4.6 --- future-plans.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/future-plans.md b/future-plans.md index 586cd06..f93e344 100644 --- a/future-plans.md +++ b/future-plans.md @@ -169,6 +169,14 @@ Some fields naturally belong together (e.g. `frequency_stability` and Structured records are the more powerful option but require a schema system and more complex UI. Grouping/linkage is a lighter short-term win. +#### Semantically-aware formatting (acronyms, proper names) +Formatters that apply title case or similar text transformations can corrupt acronyms +(e.g. `NPN` → `Npn`) or brand/proper names. The root cause is that free-text field +values carry no semantic metadata about what kind of string they are. A long-term +fix requires fields to be semantically rich enough that formatters know whether a +value is an acronym, brand name, common noun, number, etc., and apply appropriate +rules per token. Relates to field types and structured field value work. + #### Renderer/parser result cache Once parsers and formatters run per-render, a cache keyed on field value + template version would avoid redundant work on large inventories. Invalidated when any