3 ms·
> The second one is a number This would've been useful if you knew what kind of number it was... As for what goes into separate elements and what goes into at
by crabbone 3y ago
> The second one is a number
This would've been useful if you knew what kind of number it was...
As for what goes into separate elements and what goes into attributes: a typical answer to this is that simple types (as per XSL) go into attributes, complex types go into elements.
Compare this to JSON's screwed-up definition of "hash-tables" (the things in curly braces) which doesn't require that "keys" be unique.
XML wasn't perfect. But JSON isn't really better. It sucks in a slightly different way because people keep inventing these formats w/o much thinking, and once discover problems, don't fix them.
- adamlett 3y agoThis would've been useful if you knew what kind of number it was... JSON isn’t ambiguous when it comes to this. Numbers are arbitrary precision decimal numbers[1]. I’m guessing your issue is with how Javascript interprets JSON numbers as 32 bit floats. But that is a (mis-)feature of JavaScript and switching your serialization format to XML would not help, because JavaScript represents all numbers as 32-bit floats. [1] https://www.json.org/json-en.html https://www.json.org/json-en.html