Esko Dijk <[email protected]> wrote: >> My memory is that yanglint is unable to deal with sx:structure, and so >> I haven't even tried lately.
> Version 2.1.30 (about 2 years old) is used by IETF and does support it
> explicitly. See:
> https://github.com/CESNET/libyang/tree/v2.1.30?tab=readme-ov-file
Ah. I think it was more than 2 years ago that I tried.
This whole thing has taken way too long...
> The parsing output also shows that it understands the sx:structure and
> understands that a container 'voucher' is to be created from that.
> So to really understand why the 2 tools disagree someone/we need to dig
> deeper. We as authors will just say that 1 tool thinks it's all right,
> and we think it's all right, and let the YANG-doctor review determine
> if we need to change anything.
okay. Perhaps we can do this in parallel with other reviews :-)
>> Hmm. The .sid files have the module-revision in the filename. Is
>> there a reason to do that? I don't think so.
> There's a naming convention for .sid files - see Appendix A of RFC
> 9595. I would suggest we keep using that!
} The following ".sid" file ('[email protected]') has been
} generated using the following YANG modules:
so that's what we are using now...
I'm not entirely sure I understand to include the YANG revision in it,
since really it should cross YANG revisions.
I guess we should also be including the sid file "inline" the RFC in an
appendix. I kinda hate that (and I hate having the YANG file in the RFC
too), but we don't have a better answer yet.
> This is the way to know to which YANG module revision a given .sid file
> belongs to. E.g. files could be stored in an IETF FTP directory.
Yes, but since SIDs are never re-used, whatever the latest file should apply
to all revisions...
--
Michael Richardson <[email protected]> . o O ( IPv6 IøT consulting )
Sandelman Software Works Inc, Ottawa and Worldwide
signature.asc
Description: PGP signature
_______________________________________________ Anima mailing list -- [email protected] To unsubscribe send an email to [email protected]
