Some previous discussion on HN: https://news.ycombinator.com/item?id=30218954
It’s not clear to me what advantages, if any, this encoding has over the current semi-standard of Protocol Buffers (+ clones such as Thrift).
I am also unsure where this fits in with other security-focused formats such as Saltpack and more general efforts at future-proofing attempts such as Multiformats.
Likewise, it was not clear to me why this would be more secure than pretty much any other format. There’s a bit of a disconnect between the goals and the result.
It’s pretty strict about formats and representable values, and specifies a bunch of types not natively represented in JSON, so it’d be less prone to issues caused by ambiguous parsing/validation, which has been the cause of some major security holes.
When I got to the part about graphs and trees, that felt like a really bad scope creep.