json5-spec
json5-spec copied to clipboard
json5
The JSON5 Data Interchange Format
JSON5 is defined as "JSON for Humans," but it arbitrarily limits itself to the features available in ECMAScript 5.1. (Except for unescaped line and paragraph separator characters. So, technically, JSON5...
Have you thought about some sort of support for embedding binary data? (blobs) Unicode strings are not generic - not all escape sequences are valid Unicode. What people typically do,...
JSON5 is a good format. Simple, easy to understand, easy to write, JSON compatible. There have been multiple parsers and stringifiers written for it across the internet and Github. An...
All you need is "It is recommended (but not required) that dates and times be represented as strings formatted per ISO 8601". Then anyone who needs to build a library...
These are simpler than UTF-16 surrogate escapes and easy to tack on in both identifiers and strings.
Inspired by [this tweet](https://twitter.com/slightlylate/status/1573405274257473543) and some responses ([1](https://twitter.com/slightlylate/status/1573409608844349441), [2](https://twitter.com/schweinepriestr/status/1573567185892564997)) I've come here to ask: Was there ever an attempt to make JSON5 part of JS/ECMAScript? I searched quite a bit,...
const object = {id: 123n} stringify can be stored as {"id": 123n} Can be correctly converted to bigint instead of number during parse
# Proposal Even though [JSON RFC 8259](https://datatracker.ietf.org/doc/html/rfc8259#section-4) states that "names within an object SHOULD be unique", it leaves duplicate object name behavior undefined. The RFC warns that only objects with...
Given the ECMA-404 standard is also covered by TC39, could/should we submit JSON5/6/... as version updates / proposals? https://www.ecma-international.org/publications-and-standards/standards/ecma-404/
Unicode code points in the range U+D800 to U+DFFF are used for encoding UTF-16 surrogate pairs, and can not occur on their own in a valid Unicode sequence. However, the...
