Things in XML are just strings.

Schemas are metadata, annotations to tell processors "treat this string as [some other datatype]" (note how it's not going to work if you're not using the schema and a schema-aware processor?)

And guess what? Nothing stops you from doing exactly the same thing in JSON. In fact you don't have much of a choice for the datatypes JSON doesn't natively support (dates being the most common one, but not the only one by any mean). And good JSON interfaces provide for embedding transcodings directly in the parsing or dumping (that's what the `reviver` and `replacer` arguments do in JSON.parse and JSON.stringify) for exactly that purpose.

> PS: I still don't like XML, but your comment is technically incorrect.

Nope. Specific XML dialects may have non-string datatypes (XML-RPC certainly does), but XML only has strings. In the same way CSV only has strings, but specific CSV uses may have more. That's the plain facts of the matter.

XML and JSON are representations -- so they are all just bits. It's meaningless to say that, however.

The metadata and surrounding standards are what give those bits more meaning. So compare what the standards have to offer.

(Aside: I don't like XML and I think JSON is way over-hyped and under-delivers.)

Which I did. The XML standard only offers strings, and you can add schemas to JSON.