Poking in here just to make a specific point about a couple examples given so far...
I think naming a YANG list node `foo-list` not great, b/c it's somewhat easier/better to think of a YANG list node as a "list item" so a slightly better name would be `foo-item`, and probably the best name would be `foo` (this is really obvious when you look at XML data). Regarding the `foo-grouping` example, aren't grouping names always found in only 2 places (and nothing else is used in those places), the `grouping` definition and `uses` statements? I would think that the presence of the keyword `grouping` or `uses` is probably enough to highlight the identifier as a grouping. :) Thanks, Chris. [email protected] writes:
Kent, I’m afraid to not follow you here. The text below was in RFC8407!! I wasn’t involved when that text was added to 8407. Cheers, Med De : Kent Watsen <[email protected]> Envoyé : mardi 15 avril 2025 06:29 À : BOUCADAIR Mohamed INNOV/NET <[email protected]> Cc : [email protected] Objet : Re: [netmod] Suggestion for rfc8407bis: Don't prefix identifiers with their type Hi Med, On Apr 14, 2025, at 10:48 PM, [email protected] wrote: 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. You self-pushed for this and many other changes in 8407 bis. Consensus was weak. Now you are asserting said items without acknowledging that it is quiet common to use, e.g., "-type" (951 cases) and "-list" (241 cases). ____________________________________________________________________________________________________________ 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 -- [email protected] To unsubscribe send an email to [email protected]
_______________________________________________ netmod mailing list -- [email protected] To unsubscribe send an email to [email protected]
