3 ms·
When I was writing an xbrl-to-json library I suddenly realized that they are not perfectly transferable. XML comes from spreadsheets, and so it was the first m
by scoofy 3y ago
When I was writing an xbrl-to-json library I suddenly realized that they are not perfectly transferable.
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.
- philipswood 3y agoXML comes from spreadsheets?
- kstrauser 3y ago<narrator>It doesn’t.</narrator>
- philipswood 3y ago<utterance sc:utterance-speaker="narrator"> It doesn't. </utterance> <!-- indeed it is a SGML profile, like HTML -->
- occamrazor 3y agoPedantic remark: HTML 4.0 is an SGML profile, but HTML 5 isn’t anymore.
- scoofy 3y agoI'm sorry, I meant XBRL: https://en.wikipedia.org/wiki/XBRL https://en.wikipedia.org/wiki/XBRL
- lolive 3y agoMy 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.
- scoofy 3y agoJSON -> XBRL, but not all XBRL -> JSON