%% You should probably cite draft-hallambaker-jsonbcd-24 instead of this revision. @techreport{hallambaker-jsonbcd-15, number = {draft-hallambaker-jsonbcd-15}, type = {Internet-Draft}, institution = {Internet Engineering Task Force}, publisher = {Internet Engineering Task Force}, note = {Work in Progress}, url = {https://datatracker.ietf.org/doc/draft-hallambaker-jsonbcd/15/}, author = {Phillip Hallam-Baker}, title = {{Binary Encodings for JavaScript Object Notation: JSON-B, JSON-C, JSON-D}}, pagetotal = 15, year = 2019, month = oct, day = 23, abstract = {Three binary encodings for JavaScript Object Notation (JSON) are presented. JSON-B (Binary) is a strict superset of the JSON encoding that permits efficient binary encoding of intrinsic JavaScript data types. JSON-C (Compact) is a strict superset of JSON-B that supports compact representation of repeated data strings with short numeric codes. JSON-D (Data) supports additional binary data types for integer and floating-point representations for use in scientific applications where conversion between binary and decimal representations would cause a loss of precision. This document is also available online at http://mathmesh.com/Documents/draft-hallambaker-jsonbcd.html {[}1{]} .}, }