-
Section 9 contains the following text:
> When the JavaScript value is a non-integer number, it is converted to a 64-bit CBOR floating point number. Otherwise, when the JavaScript type corresponds t…
-
See https://tools.ietf.org/html/rfc7049#section-3.9.
This makes it possible to compare objects for bitwise equality (it also makes signatures/signature verification easier).
-
RFC7049 appears to be referenced with ! to make it normative, however, from a non-normative section.
I am overall a bit worried from where the new ReSpec error and warnings suddenly come from...
-
Implement a 'binary' data type. This to be marshalled as CBOR: see https://tools.ietf.org/html/rfc7049
-
Recently there has been a new JSON spec being drafted, might be a good idea to discuss in regards to binary data encodings.
https://github.com/json5/json5/issues/190
-
Title says it all.
-
The binary.md file, which describes the CBOR representation of dhall expressions, has content like the following (emphasis added):
> The encoding logic includes several optimizations for more compa…
-
- http://bsonspec.org/
- https://github.com/lightbend/config/blob/master/HOCON.md
- http://amzn.github.io/ion-docs/docs/spec.html
- https://github.com/FasterXML/smile-format-specification
- https:…
-
Working with tests for the binary encoding and reviewing changes to `.dhallb` files is currently tricky as the binary files are hard to read and GitHub can't show the diffs.
I think it would be bet…
-
I received feedback from some of our security people that [DER](https://www.itu.int/ITU-T/studygroups/com17/languages/X.690-0207.pdf) is easier to parse securely than [CBOR](https://tools.ietf.org/htm…