-
### What is the feature you are proposing?
[CBOR](https://cbor.io/) is a binary format for serializing objects defined in [RFC 8949](https://www.rfc-editor.org/rfc/rfc8949.html). It is JSON-compatibl…
-
The [RFC 8949](https://datatracker.ietf.org/doc/html/rfc8949) describes the Concise Binary Object Representation (CBOR). It's a data format whose design goals include the possibility of extremely smal…
-
RFC 8949 obsoletes RFC 7049, and the latter is what System.Formats.Cbor is built from.
The revised RFC changes, subtly, the sorting of map keys. The new RFC uses lexicographic sorting, as noted in …
-
https://cbor.io cites this repo saying "supports everything mentioned in RFC 7049".
A new edition of RFC 7049 has become available as [RFC 8949](https://www.rfc-editor.org/rfc/rfc8949.html).
While t…
-
While, [RFC8948](https://datatracker.ietf.org/doc/html/rfc89…
-
## Introduction
Concise Binary Object Representation, aka. CBOR ([RFC 8949](https://datatracker.ietf.org/doc/html/rfc8949)) is a data format widely deployed on the web. However there is no standard…
-
See RFC 8949, where JSON is used, CBOR should be supported
-
It would be great if ucan could support CWT as well as JWT for embedded us cases.
This would also pave the way for interoperatbility with attesttation frameworks such as DICE
References:
- CBOR…
-
As far as I understand, in RFC 8949, only NEGATIVE numbers are serialized as Type1, but in this implementation, all signed numbers are serialized as type1.
I found this problem when I tried to conver…
-
`type_defect` | by mahoney@nostrum.com
___
When superscript formatting is applied to text in a definition entry () of a definition list (), the baseline of the term text () is raised above the…