My experience is a bit different.
I use Chameleon+xmldict to generate dozen of different JSON formats, my input being a XML template plus Chameleon templating instructions. And I have found that JSON can be 100% percent expressed from XML.
JSON -> XBRL, but not all XBRL -> JSON
Re:Don't Invent XML Languages (2006)
by philipswood on Saturday March 09, 2024 @02:42AM
(#39650159)
XML comes from spreadsheets?
<narrator>It doesn’t.</narrator>
Re:Don't Invent XML Languages (2006)
by philipswood on Saturday March 09, 2024 @06:05AM
(#39650921)
<utterance sc:utterance-speaker="narrator">
It doesn't.
</utterance>
<!-- indeed it is a SGML profile, like HTML -->
Re:Don't Invent XML Languages (2006)
by occamrazor on Saturday March 09, 2024 @10:37AM
(#39652291)
Pedantic remark: HTML 4.0 is an SGML profile, but HTML 5 isn’t anymore.
I'm sorry, I meant XBRL: https://en.wikipedia.org/wiki/XBRL
XML comes from spreadsheets, and so it was the first mover. Whereas json came from key-value pairs. I think key-value pairs are much easier to picture in your mind, and for the vast majority of work people are doing, it's just simpler.
I think XML is wildly complicated for simply APIs.