This is a big problem for people writing general JSON processors/parsers. But it's not too bad an issue for specific applications/systems using JSON... They n

This is a big problem for people writing general JSON processors/parsers. But it's not too bad an issue for specific applications/systems using JSON... They need their JSON to be in the correct form to represent their "business objects" (or whatever you want to call your application or system-specific data types), which is already a very restricted subset of JSON that a standard can't help with, and only rarely need to bump up against the oddness JSON has around the edges. (Not that people won't bump up against these issues more than they really need to -- e.g, I recently saw someone trying to rely on multiple keys to mean something specific, which is a fun/interesting idea but is crazy to want to put into production... but good specs won't stop people from wanting to do crazy things.)