Convert CBOR to YAML
Turn CBOR files into YAML. The same structure and key order; a CBOR sequence becomes a list.
Converted in an isolated sandbox on our serversDeleted after 24 hours
Drop CBOR files on the dialor turn it to pick what to do
Binary CBOR as readable YAML.The structure and key order stay as they are. Byte strings and dates become text.
What you get
One YAML file with the same structure and the same key order as the CBOR file. Maps stay maps and arrays stay lists, so the data reads the same way, now as plain text you can open in any editor.
A CBOR sequence, which is several items one after another, becomes a list in the YAML file.
What changes on the way
Byte strings become base64 text. Epoch times, which CBOR marks with tag 1, become ISO 8601 text. Other tags are unwrapped, so you get the value inside without the tag.
Integers beyond 64 bits become text. The digits are kept, but the value is no longer a number in the YAML file.
When it stops
A file that cannot be parsed as CBOR stops the conversion with
input_corrupted. This code means the file could not be parsed.To go the other way, use YAML to CBOR.
CBOR and YAML.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
YAML
YAML configuration and data files.
- Extensions
- .yaml .yml
- MIME type
- application
/yaml - Kind
- Text and data
In your code.The same CBOR to YAML conversion through the API, for your app or your agent.
$ cv convert report.cbor report.yaml$ cv convert report.cbor report.yamlQuestions.What people ask about CBOR to YAML.
Yes. The YAML file keeps the same structure and key order as the CBOR file.
They become base64 text in the YAML file.
Epoch times, marked with tag 1, become ISO 8601 text.
The CBOR file could not be parsed, so the conversion stops with input_corrupted.