On 02. 02. 22 1:00, Robert Varga wrote:
On 28/01/2022 12:12, Italo Busi wrote:
The YANG code is correct (at least it passes pyang validation) but it
fails yanglint validation just because yanglint does not support axes,
so we expect that as soon as we upload the updated draft, the IETF
datatracker will signal yang validation errors
Is there any guideline/suggestion from Netmod WG and YANG doctors on
how to deal with such a case?
I do not believe a deficiency in one tool should hold back publication.
Tools are updated more easily than SDO documents after all and one would
hope this will create a bit of an incentive to fix the tool.
+1
Lada
Regards,
Robert
_______________________________________________
yang-doctors mailing list
yang-doct...@ietf.org
https://www.ietf.org/mailman/listinfo/yang-doctors
--
Ladislav Lhotka
Head, CZ.NIC Labs
PGP Key ID: 0xB8F92B08A9F76C67
_______________________________________________
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod
