Kent Watsen <[email protected]> writes:
>> On Dec 12, 2021, at 5:11 PM, Michael Richardson <[email protected]>
>> wrote:
>>
>>
>> Carsten Bormann <[email protected]> wrote:
>>> On 2021-12-12, at 22:17, Michael Richardson <[email protected]> wrote:
>>
>>>> I'm working on draft-richardson-anima-rfc8366bis, trying to make it
>>>> RFC8791.
>>> […]
>>>> What I don't know how to deal with:
>>
>>> RFC 8792?
>>
>> If I put \ into the original .yang file, then it won't process.
>> So if RFC8792 is the solution, then I think that I probably prefer to have
>> ::include do it. Otherwise, I have to add another step to the workflow.
>>
>> I'd also want assurance that the YANG module extractor knows about 8792.
>> Maybe given that Kent is a leader author on that... it's already taken care
>> of.
>
> `pyang` and I think `yanglint` also know how to extract folded <artwork> and
> <sourcecode> elements.
>
> That said, I have never needed to fold a YANG module in an I-D. As Juergen
> mentioned, YANG’s built-in mechanisms have always enabled me to fit within
> 69-columns.
Indeed. In this case, one can simple break the offending line like this:
namespace
"urn:ietf:params:xml:ns:yang:iana-voucher-assertion-type";
The conventions of RFC 8792 should be used only where it is absolutely
necessary.
Lada
>
> Unsure about module-extractor. My guess is that it will barf ;)
>
> K.
>
>
> _______________________________________________
> netmod mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/netmod
--
Ladislav Lhotka
Head, CZ.NIC Labs
PGP Key ID: 0xB8F92B08A9F76C67
_______________________________________________
netmod mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/netmod
