Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Missing low level information ? #28

Open
sbernard31 opened this issue Aug 9, 2024 · 0 comments
Open

Missing low level information ? #28

sbernard31 opened this issue Aug 9, 2024 · 0 comments

Comments

@sbernard31
Copy link

I'm implementing SenML Cbor and I need to check that some data are encoded in a specific way.

Eg. rfc8428§6. CBOR Representation (application/senml+cbor):

o For JSON Numbers, the CBOR representation can use integers,
floating-point numbers, or decimal fractions (CBOR Tag 4);
however, a representation SHOULD be chosen such that when the CBOR
value is converted to an IEEE double-precision, floating-point
value, it has exactly the same value as the original JSON Number
converted to that form. For the version number, only an unsigned
integer is allowed.

o Characters in the String Value are encoded using a text string
with a definite length (major type 3). Octets in the Data Value
are encoded using a byte string with a definite length (major type
2).

...

o For streaming SenSML in CBOR representation, the array containing
the records SHOULD be a CBOR array with an indefinite length; for
non-streaming SenML, an array with a definite length MUST be used.

Unless I missed something it is very impossible to check that ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant