Jürgen, On Fri, Jan 27, 2023 at 09:18:32PM +0100, Jürgen Schönwälder wrote: > Depending on context, I think it is 'modeling' when it is about > choosing the type or 'rendering' / 'representing' when it is about how > a type's value is rendered (in XML). Some proposals:
I've incorporated all of these suggestions and published as -01. Thanks. > > What I would have preferred to exist in the YANG language is a bits type > > that provides for automatic default naming for unassigned positions. Thus, > > using your example: > > <flags>restart b1</flags> > > > > I understand the motivations to not do this since there's a desire to have > > stable naming for the position 1 element. Thus, we're driven to this > > discussion. > > I assume there are use cases where this would be useful and perhaps > others where it is less so. But more likely nobody thought about this > 13 years ago. I do not know whether we have a YANG next issue for this > but this may be an issue worth to look at if there is ever another > version of YANG. Agreed. It might be useful for the YANG doctors to comment on how things have been modeled for unknown bit state elsewhere as they've done their work. I find it likely that other modules have chosen to not be this thorough. It's my hope that this pattern is a useful one and becomes recommended. -- Jeff _______________________________________________ netmod mailing list [email protected] https://www.ietf.org/mailman/listinfo/netmod
