Improvement of comparison with ASN.1 and others

[zzo38]

ASN.1 does not impose a limit of integer and floating point size, and does have decimal float as well as binary float (although both are the same type in ASN.1).
Some ASN.1 formats do support ad-hoc data without a schema (e.g. DER) while some don't (e.g. OER and PER).
Some types do not seem to be mentioned, such as OID and relative OID (both are in ASN.1), and the character sets supported for text, and bit string (also in ASN.1).
I made up ASN.1X, which adds some additional types such as: key/value list (with any types for keys and values), TRON string, rational numbers, reference to another node within the file, placeholder for out-of-band-data, and a few others as well.

[zzo38]

Another feature which it might be useful to compare is consistent framing in the binary format (in the case of ASN.1, DER has consistent framing and OER does not).
Consistent framing makes it less compact but also makes the parsing simpler to handle including the possibility to handle unknown types.
There is also, whether blocks of multiple items are preceded by a length to be skipped over, or use an ending delimiter; each has its own advantages and disadvantages.
Another type you did not list in the comparison is unordered multisets (which ASN.1 has, and in the case of Concise Encoding it seems to be the same type as the ordered list type).
(I will prefer to use ASN.1X rather than Concise Encoding or JSON or XML or some of those other ones, but different formats can be useful for different purposes so it is OK to have more than one.)

[saradarosa472-eng]

#40