Exactly. There might be a lot of (type definition) redundancy in a
document. Worst case, inconsistencies between these definitions snug in.
One example of how to avoid inconsistencies by generating a full CDDL
during draft build (independent of the choice to put that full CDDL into
the draft or not) using the cddl "1.0" tool chain can be found here:
https://github.com/ietf-rats-wg/draft-ietf-rats-corim/
Viele Grüße,
Henk
On 02.02.23 18:08, Carsten Bormann wrote:
On 2023-02-02, at 17:59, Henk Birkholz <[email protected]> wrote:
I am leaning towards a complete set of CDDL definitions in an Appendix for lazy
humans like me.
(If anybody wonders how to do the extraction to generate the appendix without
pulling in the appendix as well:
Use the RFCXML name= attribute for the collected set, and use an XPath
expression such as:
//sourcecode[not(@name) and @type='cddl']/text()
Just a hint...)
Grüße, Carsten
_______________________________________________
COSE mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/cose
