Not sure I like the idea of cramming ASCII type tags in to the encoded JSON.<p>I&#x27;m more partial to the way Avro does  it, where the encoded JSON remains type-tag and cruft free, and a separate schema (also JSON) is used (and required) to interpret the types, or encode to the correct binary encoding.