Open nedmsmith opened 2 years ago
Note that the TCG endorsement specification also defines string equivalents whenever there is a numeric code point definition.
two aspects to consider (a) defining JSON signature format and global tagging (b) internal code point definition and how to handle binary values.
The current corim doesn't anticipate cases where a JSON encoding might be the CDDL output. For example bit fields &(bit : 1, bit : 2 ...) might have a JSON encoding of {"bit1" / "bit2" / ...}. While it may be possible for a CBOR to JSON converter to reasonably infer the JSON. Such a tool / standard hasn't been defined.
Applying this to corim would also align with IETF RATS conventions for specifications involving CDDL, JSON and CBOR encodings.