Convert MSGPACK to CBOR

Turn MSGPACK files into CBOR. The same structure and key order in CBOR, with integers, floats, booleans, null, text, arrays and maps keeping their types and dates as text.

Converted in an isolated sandbox on our serversDeleted after 24 hours

Drop MSGPACK files on the dialor turn it to pick what to do

MessagePack data as CBOR.The same structure and key order, with types kept where CBOR has them.

  1. What you get

    One CBOR file with the same structure and key order as the MessagePack input. Integers, floats, booleans, null, text, arrays and maps keep their types.

    Dates are kept as text.

  2. What changes

    Binary values become base64 text. Timestamps become ISO 8601 text in UTC. Anything that reads the CBOR file sees these values as text, not as binary or timestamp types.

MSGPACK and CBOR.What each format is.

The formats

From · MSGPACK

MessagePack

Binary JSON: the same values as JSON in a compact byte encoding.

Extensions
.msgpack .mpk
MIME type
application/msgpack
Kind
Text and data
To · CBOR

CBOR

Concise Binary Object Representation, the binary JSON of IoT and web standards.

Extensions
.cbor
MIME type
application/cbor
Kind
Text and data

In your code.The same MSGPACK to CBOR conversion through the API, for your app or your agent.

terminal
$ cv convert report.msgpack report.cbor
$ cv convert report.msgpack report.cbor

Questions.What people ask about MSGPACK to CBOR.

01OF 04

Yes. The CBOR file has the same structure and key order as the MessagePack file.

They become base64 text. The CBOR file holds them as text, not as binary.

As ISO 8601 text in UTC.

Yes. Integers and floats keep their types, along with booleans, null, text, arrays and maps.

More conversions.Other ways in and out of MSGPACK and CBOR.