>It makes perfect sense -- if you provide a freeform content section of an otherwise strictly formed document (for interoperability reasons), then people will abuse it to store arbitrary, uninteroperable data (as was seen with binary blobs being dumped into XML).
That will then be their own bloody problem, not Crockfords.
Except that in practice, this has just meant that people have defined their own ad-hoc extensions to JSON that add support for comments, since it's so useful for stuff like JSON-formatted config files.
Re:JSON5 is a proposed extension to JSON
by TazeTSchnitzel on Sunday March 02, 2014 @11:20AM
(#7329589)
It's also meant that JSON documents don't have data encoded in comments. Working as intended.
Indeed. I see SQL comments and Postgres COMMENT ON statements used to send information to applications. Really funny, that....
And you can't base64 encode it and store it in a string?
The point of a standardized serialization format is well-defined parsing semantics and universal interoperability.