Re:Show HN: CommerceTXT – An open standard for AI shopping c...
by inerte on Friday December 19, 2025 @12:19PM
(#46328333)
Wouldn't be easier on everybody (servers and clients) to just expose Structured Data in a text file then? And add the 1 or 2 things it doesn't have?
[ Parent
| on HN ]
Re:Show HN: CommerceTXT – An open standard for AI shopping c...
by tsazan on Friday December 19, 2025 @12:31PM
(#46328490)
That solves bandwidth. It fails on tokens.
JSON syntax is heavy. Brackets and quotes consume context window.
More importantly, Schema.org is a dictionary of facts. It lacks behavior. It defines what a product is, but not how to sell it.
It has no concept of @SEMANTIC_LOGIC or @BRAND_VOICE. We need a format that carries both data and instructions efficiently. JSON-LD is too verbose and too static for that.
Re:Show HN: CommerceTXT – An open standard for AI shopping c...
by reddalo on Friday December 19, 2025 @01:12PM
(#46328956)
> JSON syntax is heavy.
I'd say it's not heavy. JSON syntax is pretty lean compared to XML.
Re:Show HN: CommerceTXT – An open standard for AI shopping c...
by tsazan on Friday December 19, 2025 @01:44PM
(#46329356)
JSON is lean for data exchange between machines.
But in the LLM economy, the currency is tokens, not bytes.
To an LLM tokenizer, every bracket and quote is a distinct cost. In our tests, this 'syntax tax' accounts for up to 30% of the payload.
We chose a line-oriented format to minimize overhead and maximize the context window for actual commerce data.