Stop Comparing JSON and XML
yegor256.com
yegor256.com
I feel a bit sorry for XML. A modern evolution of SGML, which pursued ideas of reliable data storage for decades, XML was an attempt to be user-friendly, to be easy to deal with manually. It was after all rather similar to HTML, on appearance.
However, XML is too verbose for automated processing, and too inconvenient for manual work today when there is JSON - or other more "humane" formats. So it seems it's on the way out.
JSON is hardly great: rather, it's the second-worst of the popular data interchange formats today. XML is the worst.
ASN.1 isn't really popular, which is good; I'd hate to have to decide between ASN.1 and XML.
If JSON has JSONPath and JSONSchema. It looks like it is another XML, then.
For what they are, I quite like protobufs. I tend to prefer something with a human-readable version, but protobufs do get the job done.
Human-readability is why canonical S-expressions (e.g. (3:foo3:bar), which can be displayed as (foo bar), ("foo" #626172#), (|Zm9v|3:bar) or any permutation thereof) are still the best thing around.