Search code examples
jsonstandardsspecifications

Who is responsible for updates to the JSON spec?


I am tired of working around the fact that JSON does not support binary data.

While there are workarounds, it would be nicer for me to get the specification updated to support binary data properly.

Who is responsible for updates to the JSON specification?

If you have ideas/dreams/whishes how to improve JSON, then please let me know. Just create a issue here Let's fix JSON (github)


Solution

  • According to the Wikipedia article on JSON, it has been standardized in ECMA-404, RFC 8259 and ISO/IEC 21778:2017. Realistically speaking, JSON is now such an established standard that it is impossible to change without breaking many services relying on the current JSON format. I.e. it is not going to happen.

    The most common way to get around this is to encode the binary data as Base64 and agree that's how it's done in the application layer.

    Another answer could be to use a different protocol - Wikipedia has a nice Comparison of data serialization formats.

    (And while we're picking on JSON, may I add the lack of dates as one of my personal itches.)