Ah, so thats how we get language detection:

{"language": "cppnix", "language": "lix"}

In reply to @kfears:matrix.org
https://seriot.ch/software/parsing_json.html

In reply to @piegames:flausch.social
Are there any other specifications of JSON other than that RFC?

Quoting the linked blog post:

Yet JSON is defined in at least seven different documents: 2002 - json.org, and the business card 2006 - IETF RFC 4627, which set the application/json MIME media type 2011 - ECMAScript 262, section 15.12 2013 - ECMA 404 according to Tim Bray (RFC 7159 editor), ECMA rushed out to release it because: "Someone told the ECMA working group that the IETF had gone crazy and was going to rewrite JSON with no regard for compatibility and break the whole Internet and something had to be done urgently about this terrible situation. (...) It doesn’t address any of the gripes that were motivating the IETF revision. 2014 - IETF RFC 7158 makes the specification "Standard Tracks" instead of "Informational", allows scalars (anything other than arrays and objects) such as 123 and true at the root level as ECMA does, warns about bad practices such as duplicated keys and broken Unicode strings, without explicitly forbidding them, though. 2014 - IETF RFC 7159 was released to fix a typo in RFC 7158, which was dated from "March 2013" instead of "March 2014". 2017 - IETF RFC 8259 was released in December 2017. It basically adds two things: 1) outside of closed eco-systems, JSON MUST be encoded in UTF-8 and 2) JSON text that is not networked transmitted MAY now add the byte order mark U+FEFF, although this is not stated explicitly. Despite the clarifications they bring, RFC 7159 and 8259 contain several approximations and leaves many details loosely specified.

Quoting the linked blog post:

Yet JSON is defined in at least seven different documents:

• 2002 - json.org, and the business card
• 2006 - IETF RFC 4627, which set the application/json MIME media type
• 2011 - ECMAScript 262, section 15.12
• 2013 - ECMA 404 according to Tim Bray (RFC 7159 editor), ECMA rushed out to release it because:

"Someone told the ECMA working group that the IETF had gone crazy and was going to rewrite JSON with no regard for compatibility and break the whole Internet and something had to be done urgently about this terrible situation. (...) It doesn’t address any of the gripes that were motivating the IETF revision.

• 2014 - IETF RFC 7158 makes the specification "Standard Tracks" instead of "Informational", allows scalars (anything other than arrays and objects) such as 123 and true at the root level as ECMA does, warns about bad practices such as duplicated keys and broken Unicode strings, without explicitly forbidding them, though.
• 2014 - IETF RFC 7159 was released to fix a typo in RFC 7158, which was dated from "March 2013" instead of "March 2014". 2017 - IETF RFC 8259 was released in December 2017. It basically adds two things: 1) outside of closed eco-systems, JSON MUST be encoded in UTF-8 and 2) JSON text that is not networked transmitted MAY now add the byte order mark U+FEFF, although this is not stated explicitly.

Despite the clarifications they bring, RFC 7159 and 8259 contain several approximations and leaves many details loosely specified.