Some additional items that have occurred to me during my weekend cbor hacking. Some of these changes don't add rules, it's just further clarity.
Clarify position on tags - just because the CBOR spec mentions some official-looking tags doesn't mean they're supported. And just because some of the tags are used for seemingly "reasonable" things (like bignums and bigfloats and other ways of doing bytes) doesn't mean they're supported.
"Simple values" are not supported. There's a rabbit hole in major type 7 so I included an exclusive list just for that.
Undefined shouldn't be supported .. which may be a surprise to some JS folks, it's not in our data model and we can't have it in our encodings. (This should be clarified further in our Data Model docs, we have to rule out any kind of sparse arrays for instance, ['foo',,,'bar']. That shouldn't be possible but currently is in js-*-dag-cbor:
Some additional items that have occurred to me during my weekend cbor hacking. Some of these changes don't add rules, it's just further clarity.
Undefinedshouldn't be supported .. which may be a surprise to some JS folks, it's not in our data model and we can't have it in our encodings. (This should be clarified further in our Data Model docs, we have to rule out any kind of sparse arrays for instance,['foo',,,'bar']. That shouldn't be possible but currently is in js-*-dag-cbor:(JSON does the right thing here in JS btw and coerces them to
nullbut coercion is probably the wrong thing to be doing there!).