Re: [Cbor] Chair review of cbor-file-magic 08

[Christian Amsüss <[e-mail]>]

Hello Michael, Carsten, CBOR,

The document has been submitted to the IESG. The shepherd writeup
contains a note that about three items need minor few-word changes,
these are:


There is a "CBOR objects" in the abstract,
you wanted to do something about that.


On Mon, Mar 07, 2022 at 10:21:17PM +0100, Carsten Bormann wrote:
> The tags allocated in 5.3 are described in Appendix A.
> This should make clear that the data item is actually /any/.
> (Byte string normally and in cases of 55800 and 55801, but /any/ in case of tag 55799.)

I think it is confusing to users if the registry describes the value for
one case that is more restrictive than the general value.

Would it make sense to put "depends on context" in there? (It's not like
the registry is CDDL typed).


Speaking of the registry: The shepherd writeup form makes a point of
asking that the used registry be identified, and 'Concise Binary Object
Representation (CBOR) Tags' doe snot show up once in the IANA
considerations. (It talks of 'registering CBOR tags', which is obvious
to us with the context, but not necessarily to an editor who does not
have all the lists indexed by abbreviations).

BR
c

-- 
To use raw power is to make yourself infinitely vulnerable to greater powers.
  -- Bene Gesserit axiom