In CBOR examples there's need of a notation to indicate a binary string element that's too large to include on the spot, but where the element contents are defined elsewhere.
Notation 1 (is used now in some cases)
h'1234' // 'registrar_cert'
Notation 2 (may be more clear than 1 that there are more bytes? )
h'12....34' // 'registrar_cert'
Notation 2b (used in places where there's no reference to an external binary string)
h'e412....345f' / some comment what it is /
Notation 3 (may be more clear than 1 - symbolic notation, avoid the 1234)
h''
Notation 4 (also used in some places)
h'registrar_cert'
In all above cases the symbolic name binary contents registrar_cert is then defined below it or in another section.
Any preferences? I like 3 personally.
In CBOR examples there's need of a notation to indicate a binary string element that's too large to include on the spot, but where the element contents are defined elsewhere.
Notation 1 (is used now in some cases) h'1234' // 'registrar_cert'
Notation 2 (may be more clear than 1 that there are more bytes? ) h'12....34' // 'registrar_cert'
Notation 2b (used in places where there's no reference to an external binary string) h'e412....345f' / some comment what it is /
Notation 3 (may be more clear than 1 - symbolic notation, avoid the 1234) h''
Notation 4 (also used in some places) h'registrar_cert'
In all above cases the symbolic name binary contents registrar_cert is then defined below it or in another section. Any preferences? I like 3 personally.