Hi Kent, We do already have the following in 8407:
Identifiers SHOULD NOT carry any special semantics that identify data modeling properties. Only YANG statements and YANG extension statements are designed to convey machine-readable data modeling properties. I think we need to be consistent among what we are producing. I don't see any problem we are solving by adding -grouping to grouping names. Cheers, Med > -----Message d'origine----- > De : Kent Watsen <k...@watsen.net> > Envoyé : mardi 15 avril 2025 02:36 > À : Andy Bierman <a...@yumaworks.com> > Cc : Michael Richardson <m...@sandelman.ca>; netmod@ietf.org > Objet : [netmod] Re: Suggestion for rfc8407bis: Don't prefix > identifiers with their type > > > > > > On Apr 11, 2025, at 11:18 AM, Andy Bierman <a...@yumaworks.com> > wrote: > > > > This 'bad' practice (foo-grouping) has been used in RFCs as > recently as RFC 9640. > > No one seemed to care in the years the WG was working on these > documents. > > Those documents are just recently published. How about filing a > Technical Erratum to convert them all? The data model would be > unaffected... > > > > In general, avoiding redundancy is a good idea, but naming > conventions > > for different types of identifiers are quite common. > > Perhaps use "-g" instead of "-grouping"? > > The goal for the YANG to be readable. I created this convention in > order to make it more readable, because otherwise it became > confusing when "foo" could be a a substring found in many > identifiers (module names, groupings, containers, etc.). I had > issues trying to navigate the modules before, which resolved after > introducing the typing convention. > > I personally think there is bike-shedding going on here, and the > 8407bis guidance is overreaching. Strange how no one asked me why > I did this, to seek for a solution that addresses the issue I ran > into. > > > Kent // contributor > > _______________________________________________ > netmod mailing list -- netmod@ietf.org > To unsubscribe send an email to netmod-le...@ietf.org ____________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you. _______________________________________________ netmod mailing list -- netmod@ietf.org To unsubscribe send an email to netmod-le...@ietf.org
