Convert CBOR to MSGPACK
Turn CBOR files into MessagePack. The same structure and key order in MessagePack, with integers, floats, booleans, null, text, lists and maps keeping their types and dates as text.
Converted in an isolated sandbox on our serversDeleted after 24 hours
Drop CBOR files on the dialor turn it to pick what to do
The same data in MessagePack.Structure and key order stay the same. Byte strings and dates become text.
What you get
One MessagePack file with the same structure as the CBOR input. Maps and lists keep their shape, and the keys stay in the same order.
Integers, floats, booleans, null and text keep their types.
What changes
MessagePack gets dates as text. Epoch times become ISO 8601 text, so a date is a readable string and not a number.
Byte strings become base64 text. Anything that reads the value afterward finds a string where the CBOR file held bytes.
CBOR and MSGPACK.What each format is.
The formats
CBOR
Concise Binary Object Representation, the binary JSON of IoT and web standards.
- Extensions
- .cbor
- MIME type
- application
/cbor - Kind
- Text and data
MessagePack
Binary JSON: the same values as JSON in a compact byte encoding.
- Extensions
- .msgpack .mpk
- MIME type
- application
/msgpack - Kind
- Text and data
In your code.The same CBOR to MSGPACK conversion through the API, for your app or your agent.
$ cv convert report.cbor report.msgpack$ cv convert report.cbor report.msgpackQuestions.What people ask about CBOR to MSGPACK.
Yes. The keys stay in the same order as in the CBOR file.
They become base64 text in the MessagePack file.
They become ISO 8601 text.
Yes. Integers, floats, booleans and null keep their types, and so do text, lists and maps.