On 2023-08-29, at 22:00, Jan Lindblad (jlindbla) <[email protected]> wrote: > > Carsten, > >> Should list names be singular or plural? > > The convention is to have the list name singular, and surrounding container > name plural.
Thank you. Now I still would like a link to a document that explains all this... > A quick grep across IETF RFC YANG modules for list names ending in s versus > ending with other letters gave 370 vs 1663 = ~20% (some modules may have been > scanned more than once, due to multiple versions etc). Quick checks like this always help to determine what usage is prevailing, thanks! Is there a good place where I can rsync IETF YANG modules from? > For some transport encodings (e.g. XML), the surrounding container makes the > list contents a bit more manageable. A surrounding container is also a > convenient for use in filters and NACM rules. The specific reason for asking this question is for draft-ietf-core-sid [1], where we used singular list names, but the PYANG sid plugin creates files with a few plural names in them. (Quickly worked around with some robustness in the sid-csv tool…) Since this is not data-at-rest (*), I don’t think a container would add anything. Grüße, Carsten (*) It may seem a bit weird to call a specification file data-in-flight, but that is what a specification is — a message, here even using sx:structure. [1]: https://www.ietf.org/archive/id/draft-ietf-core-sid-20.html _______________________________________________ netmod mailing list [email protected] https://www.ietf.org/mailman/listinfo/netmod
