Re: [Cbor] hildjj/cbor-map-entries: Explicit Map datatype for CBOR, in array format

I can give an example in Python... 

Tuples (among other types) with immutable values can be used as dict
keys: 

   {('a','b'): 'value'} 

But when serialized the tuple is converted to a CBOR array: 

A1               # map(1)
   82            # array(2)
      61         # text(1)
         61      # "a"
      61         # text(1)
         62      # "b"
   65            # text(5)
      76616C7565 # "value" 

Therefore the cbor2 decoder implementation has to know that it is being
called in a context where a hashable datatype is required and in this
case return a Tuple instead of the normal mutable List object. 

The test cases for "exotic map keys" can be found here: 

https://github.com/agronholm/cbor2/blob/818ba624df535ac7cd300aaa6fb963a83b3656e0/tests/test_encoder.py#L457

The intended use case is not for a robust wire protocol, since it would
as you say make interoperability extremely difficult, but it does allow
flexible serialization of complex objects. The Python Pickle module is
the model we are following. 

https://docs.python.org/3/library/pickle.html 

Cheers, 

Kio 

On 2021-02-18 17:52, Carsten Bormann wrote:

>> On 2021-02-18, at 17:48, Laurence Lundblade <lgl@island-resort.com> wrote:
>> 
>> This is semi-related and maybe something I'm a little confused about.
>> 
>> My understanding is that map keys/labels can be anything in CBOR including a map or array.
> 
> Yes.  
> 
> Or a Tag!
> 
>> What to do?
>> 
>> - Don't standardize any IETF protocols that use exotic map keys?
> 
> Yes.
> 
> (I don't know what's exotic, but on the implementation side generally any data structure that is mutable is a bit ugly as a map key.  E.g., languages where strings are mutable already need to jump through extra hoops here.  But, e.g., C++ handles maps with non-trivial keys just fine; these are certainly not exotic at all to a C++ programmer.)
> 
>> - Add text to Kio's proposal to restrict map keys to text string, byte string and integer?
> 
> No.
> 
> (E.g., think what https://tools.ietf.org/id/draft-ietf-cbor-tags-oid-02.html#name-distinguished-name-in-cbor- would look like without tag factoring.)
> 
>> - Write some warning against this somewhere?
> 
> Should be obvious to anyone skilled in the art :-)
> 
> (The reason CBOR can do this is that many platforms can do it -- so not supporting it in the format would have made CBOR less useful for native code/protocols for specific platforms.)
> 
> Grüße, Carsten
> 
> _______________________________________________
> CBOR mailing list
> CBOR@ietf.org
> https://www.ietf.org/mailman/listinfo/cbor