.TH "CBOR2JSON" "1" "November 2022" "8.1.0"
.SH "NAME"
\fBcbor2json\fR \- convert CBOR wire protocol to JSON
.SH SYNOPSIS
.RS 2
.nf
cbor2json test\.cbor > test\.json
.fi
.RE
.SH DESCRIPTION
.P
\fBcbor2json\fP creates a JSON file that mirrors (somewhat) the intent of the input
.br
set of CBOR files\.  For the subset of CBOR that directly maps to JSON, the
.br
output will seem reasonable\.  For CBOR inputs that do not map nicely to JSON,
.br
substitutions are made that may or may not match your expectations\.  For
.br
example, the input:
.RS 2
.nf
0xc100
  c1                \-\- Tag 1 (Date)
    00              \-\- 0
.fi
.RE
.P
produces the following output that does not round\-trip back to the same CBOR
.br
input:
.RS 2
.nf
"1970\-01\-01T00:00:00\.000Z"
.fi
.RE
.SH OPTIONS
.P
\fB\-\fP: read from stdin instead of a file\.  This is the default\.
.P
\fB\-x [string]\fP: read the input from the hex\-encoded string on the command line
.P
\fB\-V, \-\-version\fP: print the node\-cbor version and exit
.P
\fB\-h, \-\-help\fP: print some help text and exit
.SH SEE ALSO

.RS 1
.IP \(bu 2
.UR https://github.com/hildjj/node-cbor
.I node-cbor
.UE
.IP \(bu 2
.UR https://www.rfc-editor.org/rfc/rfc8949.html
.I RFC 8949
.UE

.RE