-
In JSON, it seems to be expected that the root element is a map or an array. From reading the RFC for CBOR, I can’t find any mention of a requirement like this; ie, that a map or array is the first ob…
-
It should probably be done as part of v2.0 milestone. After branching v1.5 to avoid compatibility surprises.
In the meantime, "preferred serialization" settings are returned by PreferredUnsortedEn…
-
RFC 7049 Canonical CBOR requires encoding NaN values to 0xf97e00.
But CTAP2 Canonical CBOR forbids changing floating-point representations. I believe this means do not encode all float64 NaN or al…
-
Hello from the [IPLD project](https://github.com/ipld) ;)
For a few years we’ve been using CBOR tag 42 in `dag-cbor`. It’s actually the only tag we use, and we use it to note when something is a li…
-
It would be easier and cleaner to do this in v2.0 instead of v1.4 due to SemVer policy.
RFC 7049bis indicates additional considerations for encoding not mentioned in 7049, so future protocols are l…
-
**CTAP2 "canonical CBOR" != RFC 7049 "Canonical CBOR"** when map keys have different data types due to sorting rules. If all map keys have same data type, there's no difference.
When "Canonical CB…
-
Manually created corpus should include all RFC 7049 test data. There was one missing (issue #5), but there may be others.
-
When converting a CBORObject to a JSON String, strings consisting of hexadecimal bytes transform to some weird strings in the JSON. I noticed that changing the JSONOptions doesn't really do much and t…
-
From RFC 7049bis Draft 12:
>If NaN is an allowed value and there is no intent to support NaN
payloads or signaling NaNs, the protocol needs to pick a single
representation, for example 0xf97e00.
…
-
Hi Peter,
I am trying to use PeterO.CBOR package to encode/decode an arbitrary object to/from CBOR. My object has two values: one is an array of byte strings, the second one is just an integer.
…