> On Tue, Sep 05, 2017 at 11:44:29AM -0700, Andy Bierman wrote: > > Blind cut-and-paste is not a good design goal. > > Definitions that stand on their own since they are not context > sensitive is IMHO a plus. If I am n pages down a YANG tree and I want > to know whether I look at config false or config true leaves, > searching backwards is really painful if you read on paper (oh, how
Isn't this something that is fixed with display (human representation) tools? > > I still don't know what it means to define hierarchical data and say the > > parent is deprecated but not the descendant nodes. > > It is odd but can happen anyway. A current augmentation of something > that got deprecated likely stays current. I would hope that tools warn > if they see this but that's it. How is anything ever expunged if parsing tools do not refuse to load a module that depends on a deprecated node that it is attempting to augment? _______________________________________________ netmod mailing list netmod@ietf.org https://www.ietf.org/mailman/listinfo/netmod
