442 lines
27 KiB
Markdown
442 lines
27 KiB
Markdown
# BJData
|
|
|
|
The [BJData format](https://neurojson.org) was derived from and improved upon
|
|
[Universal Binary JSON(UBJSON)](https://ubjson.org) specification (Draft 12). Specifically, it introduces an optimized
|
|
array container for efficient storage of N-dimensional packed arrays (**ND-arrays**); it also adds four new type markers -
|
|
`[u] - uint16`, `[m] - uint32`, `[M] - uint64`, and `[h] - float16` - to unambiguously map common binary numeric types
|
|
(Draft 3 adds `[B] - byte`); furthermore, it uses little-endian (LE) to store all numerics instead of big-endian (BE) as in UBJSON to
|
|
avoid unnecessary conversions on commonly available platforms.
|
|
|
|
Compared to other binary JSON-like formats such as MessagePack and CBOR, both BJData and UBJSON demonstrate a rare
|
|
combination of being both binary and **quasi-human-readable**. This is because all semantic elements in BJData and
|
|
UBJSON, including the data-type markers and name/string types, are directly human-readable. Data stored in the
|
|
BJData/UBJSON format is not only compact in size, fast to read/write, but also can be directly searched or read using
|
|
simple processing.
|
|
|
|
!!! abstract "References"
|
|
|
|
- [BJData Specification (Draft 3)](https://neurojson.org/bjdata/draft3)
|
|
- [BJData Specification (Draft 2)](https://neurojson.org/bjdata/draft2)
|
|
|
|
!!! info "Supported drafts"
|
|
|
|
The library supports BJData Draft 2 (the default) and Draft 3, except for column-major N-dimensional arrays (see
|
|
below). The draft used for writing is selected with the
|
|
[`version` parameter](../../api/basic_json/bjdata_version_t.md) of
|
|
[`to_bjdata`](../../api/basic_json/to_bjdata.md); [`from_bjdata`](../../api/basic_json/from_bjdata.md) has no such
|
|
parameter and reads the markers of both drafts.
|
|
|
|
!!! warning "Draft 4 and column-major ND-arrays are not supported"
|
|
|
|
BJData Draft 4 (April 2026) adds structure-of-arrays (SoA) containers (`[$` or `{$` followed by a schema object)
|
|
and the extension type `E`. `from_bjdata` does not implement them and throws
|
|
[`parse_error.112`](../../home/exceptions.md#jsonexceptionparse_error112) for such input; `to_bjdata` never writes
|
|
them.
|
|
|
|
Likewise, column-major ND-arrays of Draft 3 (the `#` marker followed by an array that wraps the dimension vector)
|
|
are rejected with [`parse_error.113`](../../home/exceptions.md#jsonexceptionparse_error113).
|
|
|
|
## Byte layout
|
|
|
|
BJData follows the structure of UBJSON: a one-byte, human-readable ASCII *type marker* followed by the payload of that type, with strings prefixed by a length that is itself an integer value. In contrast to UBJSON, numbers are stored in little-endian byte order, and additional markers cover unsigned 16/32/64-bit integers, half-precision floats, and bytes. Containers can be written unoptimized (opened with `[` or `{`, closed with `]` or `}`) or optimized with a count (`#`), optionally preceded by a declared element type (`$`). BJData extends the optimized form: the count can be a list of dimensions, which stores an N-dimensional packed array as a flat sequence of values without any per-element markers.
|
|
|
|
Consider the following JSON value (shown formatted for readability):
|
|
|
|
```json
|
|
{
|
|
"id": 300,
|
|
"name": "json",
|
|
"pi": 3.14,
|
|
"tags": [
|
|
"a",
|
|
"b"
|
|
]
|
|
}
|
|
```
|
|
|
|
`to_bjdata` encodes it to 51 bytes (shown in hexadecimal; the encoding contains no whitespace). The colors mark the role of each byte: <span class="bl bl-t">type/marker</span> <span class="bl bl-l">length/count/size</span> <span class="bl bl-d">data</span>.
|
|
|
|
<div class="byte-layout" markdown="0"><table>
|
|
<thead><tr><th>JSON</th><th>Bytes</th><th>Meaning</th></tr></thead><tbody>
|
|
<tr><td><code>{</code></td><td><span class="bl bl-t">7B</span></td><td>object start (<code>{</code>)</td></tr>
|
|
<tr><td><code>"id": 300,</code></td><td><span class="bl bl-l">69 02</span> <span class="bl bl-d">69 64</span> <span class="bl bl-t">49</span> <span class="bl bl-d">2C 01</span></td><td>key: length 2 as int8 (<code>i</code>), then UTF-8 bytes; value: int16 (<code>I</code>), little-endian</td></tr>
|
|
<tr><td><code>"name": "json",</code></td><td><span class="bl bl-l">69 04</span> <span class="bl bl-d">6E 61 6D 65</span> <span class="bl bl-t">53</span> <span class="bl bl-l">69 04</span> <span class="bl bl-d">6A 73 6F 6E</span></td><td>key: length 4; value: string (<code>S</code>), length 4 as int8, UTF-8 bytes</td></tr>
|
|
<tr><td><code>"pi": 3.14,</code></td><td><span class="bl bl-l">69 02</span> <span class="bl bl-d">70 69</span> <span class="bl bl-t">44</span> <span class="bl bl-d">1F 85 EB 51 B8 1E 09 40</span></td><td>key: length 2; value: float64 (<code>D</code>), little-endian</td></tr>
|
|
<tr><td><code>"tags": [</code></td><td><span class="bl bl-l">69 04</span> <span class="bl bl-d">74 61 67 73</span> <span class="bl bl-t">5B</span></td><td>key: length 4; value: array start (<code>[</code>)</td></tr>
|
|
<tr><td><code>"a",</code></td><td><span class="bl bl-t">53</span> <span class="bl bl-l">69 01</span> <span class="bl bl-d">61</span></td><td>string, length 1</td></tr>
|
|
<tr><td><code>"b"</code></td><td><span class="bl bl-t">53</span> <span class="bl bl-l">69 01</span> <span class="bl bl-d">62</span></td><td>string, length 1</td></tr>
|
|
<tr><td><code>]</code></td><td><span class="bl bl-t">5D</span></td><td>array end (<code>]</code>)</td></tr>
|
|
<tr><td><code>}</code></td><td><span class="bl bl-t">7D</span></td><td>object end (<code>}</code>)</td></tr>
|
|
</tbody></table></div>
|
|
|
|
## Serialization
|
|
|
|
The library uses the following mapping from JSON values types to BJData types according to the BJData specification:
|
|
|
|
| JSON value type | value/range | BJData type | marker |
|
|
|-----------------|-------------------------------------------|-------------|-------------------------------------------------------------------------|
|
|
| null | `null` | null | `Z` |
|
|
| boolean | `true` | true | `T` |
|
|
| boolean | `false` | false | `F` |
|
|
| number_integer | -9223372036854775808..-2147483649 | int64 | `L` |
|
|
| number_integer | -2147483648..-32769 | int32 | `l` |
|
|
| number_integer | -32768..-129 | int16 | `I` |
|
|
| number_integer | -128..127 | int8 | `i` |
|
|
| number_integer | 128..255 | uint8 | `U` |
|
|
| number_integer | 256..32767 | int16 | `I` |
|
|
| number_integer | 32768..65535 | uint16 | `u` |
|
|
| number_integer | 65536..2147483647 | int32 | `l` |
|
|
| number_integer | 2147483648..4294967295 | uint32 | `m` |
|
|
| number_integer | 4294967296..9223372036854775807 | int64 | `L` |
|
|
| number_integer | 9223372036854775808..18446744073709551615 | uint64 | `M` |
|
|
| number_unsigned | 0..127 | int8 | `i` |
|
|
| number_unsigned | 128..255 | uint8 | `U` |
|
|
| number_unsigned | 256..32767 | int16 | `I` |
|
|
| number_unsigned | 32768..65535 | uint16 | `u` |
|
|
| number_unsigned | 65536..2147483647 | int32 | `l` |
|
|
| number_unsigned | 2147483648..4294967295 | uint32 | `m` |
|
|
| number_unsigned | 4294967296..9223372036854775807 | int64 | `L` |
|
|
| number_unsigned | 9223372036854775808..18446744073709551615 | uint64 | `M` |
|
|
| number_float | *any value* | float64 | `D` |
|
|
| string | *with shortest length indicator* | string | `S` |
|
|
| array | *see notes on optimized format/ND-array* | array | `[` |
|
|
| object | *see notes on optimized format* | map | `{` |
|
|
| binary | *see notes on binary values* | array | `[$B` (Draft 3 with `use_size` and `use_type`), `[U`, or `[B` otherwise |
|
|
|
|
!!! success "Complete mapping"
|
|
|
|
The mapping is **complete** in the sense that any JSON value type can be converted to a BJData value.
|
|
|
|
Any BJData output created by `to_bjdata` can be successfully parsed by `from_bjdata`.
|
|
|
|
!!! warning "Size constraints"
|
|
|
|
The following values can **not** be converted to a BJData value:
|
|
|
|
- strings with more than 18446744073709551615 bytes, i.e., 2<sup>64</sup>-1 bytes (theoretical)
|
|
|
|
!!! warning "UTF-8 validation of string values and object keys"
|
|
|
|
BJData strings must use UTF-8 encoding. By default (the [`error_handler`](../../api/basic_json/to_bjdata.md)
|
|
parameter left at `keep`), `to_bjdata()` writes the bytes of string values and object keys unchanged, even if they
|
|
are not valid UTF-8. With `error_handler_t::strict`, it throws
|
|
[`type_error.316`](../../home/exceptions.md#jsonexceptiontype_error316) for ill-formed UTF-8 instead;
|
|
`replace`/`ignore` sanitize the string. [`JSON_STRICT_BINARY_UTF8`](../../api/macros/json_strict_binary_utf8.md)
|
|
makes `strict` the default.
|
|
|
|
!!! info "Unused BJData markers"
|
|
|
|
The following markers are not written:
|
|
|
|
- `N`: no-op values are not created (they are skipped when reading).
|
|
- `C`: single-character strings are serialized with `S` markers (`C` is read, and written for the elements of
|
|
ND-arrays with `"_ArrayType_": "char"`).
|
|
- `h`: floating-point numbers are written as `D`, not as float16 (`h` is read).
|
|
- `B`: only written in Draft 3 mode.
|
|
- `d` is only written for `single` ND-arrays or if `number_float_t` is `float`; `H` is only written for integers
|
|
wider than 64 bits (custom `number_integer_t`/`number_unsigned_t`). An unsigned integer above 9223372036854775807
|
|
is written as `M`.
|
|
|
|
!!! info "NaN/infinity handling"
|
|
|
|
If NaN or Infinity are stored inside a JSON number, they are serialized properly. This behavior differs from the
|
|
[`dump()`](../../api/basic_json/dump.md) function which serializes NaN or Infinity to `#!json null`.
|
|
|
|
!!! info "Endianness"
|
|
|
|
A breaking difference between BJData and UBJSON is the endianness of numerical values. In BJData, all numerical data
|
|
types (integers `UiuImlML` and floating-point values `hdD`) are stored in the little-endian (LE) byte order as
|
|
opposed to big-endian as used by UBJSON. Adopting LE to store numeric records avoids unnecessary byte swapping on
|
|
most modern computers where LE is used as the default byte order.
|
|
|
|
!!! info "Optimized formats"
|
|
|
|
Optimized formats for containers are supported via two parameters of
|
|
[`to_bjdata`](../../api/basic_json/to_bjdata.md):
|
|
|
|
- Parameter `use_size` adds size information to the beginning of a container and removes the closing marker.
|
|
- Parameter `use_type` further checks whether all elements of a container have the same type and adds the type
|
|
marker to the beginning of the container. The `use_type` parameter must only be used together with
|
|
`use_size = true`.
|
|
|
|
Note that `use_size = true` alone may result in larger representations - the benefit of this parameter is that the
|
|
receiving side is immediately informed of the number of elements in the container.
|
|
|
|
!!! info "ND-array optimized format"
|
|
|
|
BJData extends UBJSON's optimized array **size** marker to support ND-arrays of uniform numerical data types
|
|
(referred to as *packed arrays*). For example, the 2-D `uint8` integer array `[[1,2],[3,4],[5,6]]`, stored as nested
|
|
optimized array in UBJSON `[ [$U#i2 1 2 [$U#i2 3 4 [$U#i2 5 6 ]`, can be further compressed in BJData to
|
|
`[$U#[$i#i2 3 2 1 2 3 4 5 6` or `[$U#[i3 i2] 1 2 3 4 5 6`.
|
|
|
|
To maintain type and size information, ND-arrays are converted to JSON objects following the **annotated array
|
|
format** (defined in the [JData specification (Draft 3)][JDataAAFmt]), when parsed using
|
|
[`from_bjdata`](../../api/basic_json/from_bjdata.md). For example, the above 2-D `uint8` array can be parsed and
|
|
accessed as
|
|
|
|
```json
|
|
{
|
|
"_ArrayType_": "uint8",
|
|
"_ArraySize_": [3,2],
|
|
"_ArrayData_": [1,2,3,4,5,6]
|
|
}
|
|
```
|
|
|
|
ND-arrays with the element type `h` (float16) are returned with `"_ArrayType_": "half"`. `to_bjdata` does not pack
|
|
`"half"` objects; they are written as regular objects, which read back as an equal value.
|
|
|
|
Likewise, when a JSON object in the above form is serialized using
|
|
[`to_bjdata`](../../api/basic_json/to_bjdata.md), it is automatically converted into a compact BJData ND-array.
|
|
|
|
When parsing, an ND-array whose dimension vector is empty, contains a single integer, contains two integers with the
|
|
first being 1, or contains a 0 is returned as a regular (possibly empty) array rather than an annotated object.
|
|
|
|
An object is only converted if the annotation describes a packed array that is parsed back into the same annotated
|
|
object; otherwise it is serialized as a regular JSON object, so the annotation is never lost in a round trip. This requires
|
|
all of the following:
|
|
|
|
- the object has exactly the three keys `"_ArrayType_"`, `"_ArraySize_"`, and `"_ArrayData_"` (any other key, e.g.,
|
|
`"_ArrayOrder_"`, makes it a regular object),
|
|
- `"_ArrayType_"` is one of `uint8`, `int8`, `uint16`, `int16`, `uint32`, `int32`, `uint64`, `int64`, `single`,
|
|
`double`, `char`, or (only with `version = bjdata_version_t::draft3`, since the `B` marker is not part of Draft 2)
|
|
`byte`; the names are case-sensitive,
|
|
- `"_ArraySize_"` is an array, since the dimensions are written as the ND-array header's length,
|
|
- `"_ArraySize_"` has at least two entries and is not a two-entry row vector (`[1,N]`), since other shapes are
|
|
parsed back as a regular array (`[1,2,2]` is packed, `[1,4]` is not),
|
|
- every entry of `"_ArraySize_"` is a positive integer, and their product is representable as a `std::size_t`,
|
|
- `"_ArrayData_"` is an array holding exactly that many elements, and
|
|
- every element of `"_ArrayData_"` is a number of the kind named by `"_ArrayType_"`: for the integer types, an
|
|
integer (a floating-point number such as `1.0` does not qualify) that fits the named width (for `char`, 0..127);
|
|
for `double`, a floating-point number (an integer such as `1` does not qualify); for `single`, a floating-point
|
|
number that survives narrowing to `float` and back without change (for instance, `0.1` does not, since it is not
|
|
exactly representable as `float`).
|
|
|
|
With `ordered_json`, an annotated object read from BJData has its keys in the order `"_ArrayType_"`,
|
|
`"_ArraySize_"`, `"_ArrayData_"`; with `json`, they are sorted like those of any other object.
|
|
|
|
The current version of this library does not yet support automatic detection of and conversion from a nested JSON
|
|
array input to a BJData ND-array.
|
|
|
|
[JDataAAFmt]: https://github.com/NeuroJSON/jdata/blob/Draft-3/JData_specification.md#annotated-storage-of-n-d-arrays
|
|
|
|
!!! info "Restrictions in optimized data types for arrays and objects"
|
|
|
|
Due to diminished space saving, hampered readability, and increased security risks, in BJData, the
|
|
allowed data types following the `$` marker in an optimized array and object container are restricted to
|
|
**non-zero-fixed-length** data types. Therefore, the valid optimized type markers can only be one of
|
|
`UiuImlMLhdDC`, plus `B` since Draft 3 (the reader accepts `B` in both drafts). This also means other variable (`[{SH`) or zero-length types (`TFZN`) can not be used in an
|
|
optimized array or object in BJData. The library enforces this restriction for both drafts. A `C` (char) element above 127 is rejected on read with
|
|
[`parse_error.113`](../../home/exceptions.md#jsonexceptionparse_error113), in 1-D and in N-dimensional arrays. With `use_type`, the
|
|
elements must have the same marker (`[1,200,3]` is not optimized, since it mixes `i` and `U`); booleans, null,
|
|
strings, arrays, and objects are never optimized with `$`.
|
|
|
|
!!! info "Binary values"
|
|
|
|
BJData provides a dedicated `B` marker (defined in the [BJData specification (Draft 3)][BJDataBinArr]) that is used
|
|
in optimized arrays to designate binary data. This means that, unlike UBJSON, binary data can be both serialized and
|
|
deserialized.
|
|
|
|
To preserve compatibility with BJData Draft 2, the Draft 3 optimized binary array must be explicitly enabled: pass
|
|
`version = bjdata_version_t::draft3` together with `use_size = true` and `use_type = true` to
|
|
[`to_bjdata`](../../api/basic_json/to_bjdata.md). With Draft 3 and only `use_size` (or neither), a binary value is
|
|
written as an array of `B` elements.
|
|
|
|
In Draft 2 mode (default), if the JSON data contains the binary type, the value is stored as a list of integers, as
|
|
suggested by the BJData documentation. In particular, this means that the serialization and the deserialization of
|
|
JSON containing binary values into BJData and back will result in a different JSON object.
|
|
|
|
[BJDataBinArr]: https://github.com/NeuroJSON/bjdata/blob/Draft-3/Binary_JData_Specification.md#optimized-binary-array
|
|
|
|
??? example "Example: serialize JSON values to BJData, with and without size/type optimization"
|
|
|
|
```cpp
|
|
#include <iostream>
|
|
#include <iomanip>
|
|
#include <nlohmann/json.hpp>
|
|
|
|
using nlohmann::json;
|
|
using namespace nlohmann::literals;
|
|
|
|
// function to print BJData's diagnostic format
|
|
void print_byte(uint8_t byte)
|
|
{
|
|
if (32 < byte and byte < 128)
|
|
{
|
|
std::cout << static_cast<char>(byte);
|
|
}
|
|
else
|
|
{
|
|
std::cout << static_cast<int>(byte);
|
|
}
|
|
}
|
|
|
|
int main()
|
|
{
|
|
// create a JSON value
|
|
json j = R"({"compact": true, "schema": false})"_json;
|
|
|
|
// serialize it to BJData
|
|
std::vector<std::uint8_t> v = json::to_bjdata(j);
|
|
|
|
// print the vector content
|
|
for (auto& byte : v)
|
|
{
|
|
print_byte(byte);
|
|
}
|
|
std::cout << '\n';
|
|
|
|
// create an array of numbers
|
|
json array = {1, 2, 3, 4, 5, 6, 7, 8};
|
|
|
|
// serialize it to BJData using default representation
|
|
std::vector<std::uint8_t> v_array = json::to_bjdata(array);
|
|
// serialize it to BJData using size optimization
|
|
std::vector<std::uint8_t> v_array_size = json::to_bjdata(array, true);
|
|
// serialize it to BJData using type optimization
|
|
std::vector<std::uint8_t> v_array_size_and_type = json::to_bjdata(array, true, true);
|
|
|
|
// print the vector contents
|
|
for (auto& byte : v_array)
|
|
{
|
|
print_byte(byte);
|
|
}
|
|
std::cout << '\n';
|
|
|
|
for (auto& byte : v_array_size)
|
|
{
|
|
print_byte(byte);
|
|
}
|
|
std::cout << '\n';
|
|
|
|
for (auto& byte : v_array_size_and_type)
|
|
{
|
|
print_byte(byte);
|
|
}
|
|
std::cout << '\n';
|
|
}
|
|
|
|
```
|
|
|
|
Output:
|
|
|
|
```c
|
|
{i7compactTi6schemaF}
|
|
[i1i2i3i4i5i6i7i8]
|
|
[#i8i1i2i3i4i5i6i7i8
|
|
[$i#i812345678
|
|
|
|
```
|
|
|
|
## Deserialization
|
|
|
|
The library maps BJData types to JSON value types as follows:
|
|
|
|
| BJData type | JSON value type | marker |
|
|
|-----------------------|--------------------------------------------------|----------|
|
|
| no-op | *no value, next value is read* | `N` |
|
|
| null | `null` | `Z` |
|
|
| false | `false` | `F` |
|
|
| true | `true` | `T` |
|
|
| float16 | number_float | `h` |
|
|
| float32 | number_float | `d` |
|
|
| float64 | number_float | `D` |
|
|
| high-precision number | number_integer, number_unsigned, or number_float | `H` |
|
|
| uint8 | number_unsigned | `U` |
|
|
| int8 | number_integer | `i` |
|
|
| uint16 | number_unsigned | `u` |
|
|
| int16 | number_integer | `I` |
|
|
| uint32 | number_unsigned | `m` |
|
|
| int32 | number_integer | `l` |
|
|
| uint64 | number_unsigned | `M` |
|
|
| int64 | number_integer | `L` |
|
|
| byte | number_unsigned | `B` |
|
|
| string | string | `S` |
|
|
| char | string | `C` |
|
|
| array | array (optimized values are supported) | `[` |
|
|
| ND-array | object (in JData annotated array format) | `[$.#[.` |
|
|
| object | object (optimized values are supported) | `{` |
|
|
| binary | binary (strongly-typed byte array) | `[$B` |
|
|
|
|
!!! success "Complete mapping"
|
|
|
|
The mapping is **complete** for the BJData types of Draft 2 and Draft 3 with one exception: column-major
|
|
N-dimensional arrays are rejected with [`parse_error.113`](../../home/exceptions.md#jsonexceptionparse_error113).
|
|
The Draft 4 constructs (structure-of-arrays containers and the extension type `E`) are not supported either.
|
|
|
|
The digits of an `H` value are parsed like a JSON number: integers that fit 64 bits become `number_integer` or
|
|
`number_unsigned`, anything else a `number_float`; invalid text throws
|
|
[`parse_error.115`](../../home/exceptions.md#jsonexceptionparse_error115).
|
|
|
|
!!! info "Duplicate object keys"
|
|
|
|
If an object contains the same key more than once, `from_bjdata` accepts it and keeps the last value; with
|
|
`ordered_json`, the key keeps the position of its first occurrence.
|
|
|
|
!!! warning "Ill-formed UTF-8 in string values and object keys"
|
|
|
|
BJData strings must use UTF-8 encoding, but checking it on read is opt-in: with the
|
|
[`error_handler`](../../api/basic_json/from_bjdata.md) parameter left at `keep` (the default), `from_bjdata()`
|
|
accepts a string value or object key whose bytes are not valid UTF-8 and hands them back unchanged. Passing
|
|
`error_handler_t::strict` makes `from_bjdata()` check and throw
|
|
[`parse_error.113`](../../home/exceptions.md#jsonexceptionparse_error113) for ill-formed UTF-8, and
|
|
`replace`/`ignore` sanitize the string instead of keeping it. However,
|
|
[`dump()`](../../api/basic_json/dump.md) still requires valid UTF-8 and throws
|
|
[`type_error.316`](../../home/exceptions.md#jsonexceptiontype_error316) for a value read with the default
|
|
`keep` handler, unless an error handler is passed that replaces or ignores the ill-formed bytes. `to_bjdata()`'s
|
|
own `error_handler` parameter defaults to `keep` (see above), so such a value is written back unchanged.
|
|
|
|
!!! info "Round trips"
|
|
|
|
A value returned by [`from_bjdata`](../../api/basic_json/from_bjdata.md) can be serialized with
|
|
[`to_bjdata`](../../api/basic_json/to_bjdata.md) using any combination of options and parsed back into an equal
|
|
value, and serializing that value again with the same options produces the same bytes. The exception is binary
|
|
values: they are only written as an optimized binary array (`[$B`) if Draft 3 is enabled and both `use_size` and
|
|
`use_type` are set. Otherwise, they are written as arrays of integers and parsed back as such (see the notes on
|
|
binary values above), and serializing such an array again may choose different, but equally valid, type markers.
|
|
The bytes can then differ, but parsing them again yields the same value.
|
|
|
|
??? example "Example: deserialize a JSON value from BJData"
|
|
|
|
```cpp
|
|
#include <iostream>
|
|
#include <iomanip>
|
|
#include <nlohmann/json.hpp>
|
|
|
|
using nlohmann::json;
|
|
|
|
int main()
|
|
{
|
|
// create byte vector
|
|
std::vector<std::uint8_t> v = {0x7B, 0x69, 0x07, 0x63, 0x6F, 0x6D, 0x70, 0x61,
|
|
0x63, 0x74, 0x54, 0x69, 0x06, 0x73, 0x63, 0x68,
|
|
0x65, 0x6D, 0x61, 0x69, 0x00, 0x7D
|
|
};
|
|
|
|
// deserialize it with BJData
|
|
json j = json::from_bjdata(v);
|
|
|
|
// print the deserialized JSON value
|
|
std::cout << std::setw(2) << j << '\n';
|
|
}
|
|
|
|
```
|
|
|
|
Output:
|
|
|
|
```json
|
|
{
|
|
"compact": true,
|
|
"schema": 0
|
|
}
|
|
|
|
```
|
|
|
|
## See also
|
|
|
|
- [Binary formats](index.md) - overview and comparison of the supported binary formats
|
|
- [Binary values](../binary_values.md) - how binary values and subtypes map to BJData
|
|
- [`to_bjdata`](../../api/basic_json/to_bjdata.md) - serialize a JSON value to BJData
|
|
- [`from_bjdata`](../../api/basic_json/from_bjdata.md) - parse a JSON value from BJData
|
|
- [`JSON_STRICT_BINARY_UTF8`](../../api/macros/json_strict_binary_utf8.md) - reject ill-formed UTF-8 in strings
|
|
- [SAX interface](../parsing/sax_interface.md) - decode binary formats without building a value
|