cabo

CDDL is in wide use in a number of SDOs at this point and has already been used in a number of RFCs. Proposals to make major changes its syntax...

Hi Murray, this is indeed a limitation of the current tool. I'm in the middle of fixing a related bug and may be able to lift that limitation in the...

Or not, oops. Yes, I'll have to look at this some more.

Hi Matt, the most recent version at the IETF site is https://tools.ietf.org/html/draft-ietf-cbor-cddl-04 — the version that you pointed to has been replaced by an official working group draft a while...

While there are no co-occurrence constraints in CDDL, many actual use cases can be addressed by using the fact that a group is a grammar: ``` CDDL postal = {...

Right, this would require an XPath-like mechanism to crawl the tree to find that other item (which may be later in the serialization...). This is probably done better with a...

A related question would be: What is your favorite way to navigate a JSON tree? JSONpath?

https://bib.ietf.org/public/rfc/bibxml8/reference.IANA.uuid.xml now works for me (and https://bib.ietf.org/public/rfc/bibxml8/reference.IANA.UUID.xml doesn't). I cannot track this to a specific change, but I'll close the issue anyway, as the underlying case confusion seems to have...

As a document author, maybe I want to add an annotation to a referencec such as that the referenced document was superseded by another document, possibly by another SDO (say,...

The current code in kramdown-rfc simply appends annotations to any incoming bibxml. The conflict I was envisioning doesn't exist, because one can have zero or more annotations in a reference....