[rfc-i] [xml2rfc] use of sourcecode type
cabo at tzi.org
Mon Jul 27 09:23:17 PDT 2020
> This can be quite impractical in some common usage.
Then please don’t do it…
> At least in the sip world it is pretty common to have things like this:
> message = foo / bar / baz / message-extention
> message-extension = generic-message-format
> ; message-header and message defined in base-document
> new-message = message-header other stuff
> message =/ new-message
We’ll make sure we cover that use case in the CDDL discussion as well.
> where message-header, foo, bar, and baz may take hundreds of lines of abnf to define. Even in less extreme cases it can be difficult to trace all the dependencies on a rule whose definition you want to copy. And it may well involve tracing further dependencies to other documents.
> I have in the past proposed and discussed (on the abnf-discuss list) some extensions to the abnf syntax to specify references to rules defined externally. They didn't get much interest at the time. But in any case they weren't easily and reliably automatable as long as the abnf had to be scraped out of a txt document. That might be more practical now.
More information about the rfc-interest