The issue is that either your choice of extensions to standard JSON turn out to be useful and used - which causes the value of having a standard to become erod

The issue is that either your choice of extensions to standard JSON turn out to be useful and used - which causes the value of having a standard to become eroded, or they remain unused - in which case your work to support a bigger/wider format was redundant. Both outcomes are to some degree negative. All the actual JSON extensions you describe are completely reasonable and reflect failings in JSON as a standard but the solution should be for everyone to agree on a JSON v1.1 standard which fixes the failings rather than have every JSON v1.0 tool support their own particular set of extensions, rigorously defined or not.