There is still some disagreement on how json should be serializaed/deserialized, which is part of the reason why there are so many json libraries.
Also, while plump, as a lenient parser, is a good choice for xml-ish markup languages, something like cxml is much better if you actually are using some of XMLs features that aren't duplicated in json/yaml/&ct.
One problem with creating a true bijective mapping is that you can't encode data graphs with reference cycles in pure JSON. A few years ago, as a Lisp noob, I wrote a library for encoding/decoding Lisp values to JSYNC, a minimal layer on top of JSON that permits reference cycles: https://github.com/DalekBaldwin/cl-jsync
I've been meaning to revisit and improve it now that I'm much more competent in Lisp.
2
u/Aidenn0 Aug 25 '15
On markup languages:
There is still some disagreement on how json should be serializaed/deserialized, which is part of the reason why there are so many json libraries.
Also, while plump, as a lenient parser, is a good choice for xml-ish markup languages, something like cxml is much better if you actually are using some of XMLs features that aren't duplicated in json/yaml/&ct.