Re: [netmod] List name: singular or plural?

["Jan Lindblad (jlindbla)" <[e-mail]>]

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...

This is the oldest and most authoritative message/ thread I found:
<https://mailarchive.ietf.org/arch/msg/yang-doctors/rqcJ2GXxuFBHITIen2jB-zVNpWM/>
Re: [yang-doctors] Consistency for naming lists and leaf-lists<https://mailarchive.ietf.org/arch/msg/yang-doctors/rqcJ2GXxuFBHITIen2jB-zVNpWM/>
mailarchive.ietf.org<https://mailarchive.ietf.org/arch/msg/yang-doctors/rqcJ2GXxuFBHITIen2jB-zVNpWM/>
[favicon.ico]<https://mailarchive.ietf.org/arch/msg/yang-doctors/rqcJ2GXxuFBHITIen2jB-zVNpWM/>

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?

Not sure about rsync, but you can certainly git clone from here:
<https://github.com/YangModels/yang.git>
[yang.png]
YangModels/yang: YANG modules from standards organizations such as the IETF, The IEEE, The Metro Ethernet Forum, open source such as Open Daylight or vendor specific modules<https://github.com/YangModels/yang.git>
github.com<https://github.com/YangModels/yang.git>

That will give you all the IETF RFC YANGs, as well as lots of drafts and experimental modules. The repo also contains modules from a number of other SDOs and a large number of vendor modules.

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…)

Good.

Since this is not data-at-rest (*), I don’t think a container would add anything.

Without a closer look, it's hard for me to judge :-) but if clients ever want to handle the list as 'one unit', a surrounding container may help.

Best Regards,
/jan

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