3 ms·
It makes perfect sense -- if you provide a freeform content section of an otherwise strictly formed document (for interoperability reasons), then people will ab
by nitrogen 13y ago
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).
The point of a standardized serialization format is well-defined parsing semantics and universal interoperability.
- rat87 13y agoI thought xml was developed to be able to include binary parts on purpose since it can be useful.
- deleted 13y ago[deleted]
- troels 13y agoAnd you can't base64 encode it and store it in a string?
- einhverfr 13y agoIndeed. I see SQL comments and Postgres COMMENT ON statements used to send information to applications. Really funny, that....
- makomk 13y agoExcept 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.
- TazeTSchnitzel 13y agoIt's also meant that JSON documents don't have data encoded in comments. Working as intended.
- coldtea 13y ago>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.