RE: [YANG] so many naming scopes

I also like to move the "SHOULD, SHOULD NOT, MAY and similar
style information to a guidelines document. 

Be aware though, that this guidelines document will become our
CLR guide. Similar to how RFC4181 became our CLR document for
MIB modules. I am not saying that is bad. I in fact like some
rules for standardized Data Models such that we will see
consistency. It will help make things easier to use and read.

Bert Wijnen 

> -----Oorspronkelijk bericht-----
> Van: Phil Shafer [mailto:phil@juniper.net]
> Verzonden: donderdag 10 januari 2008 3:35
> Aan: j.schoenwaelder@jacobs-university.de
> CC: yang@ietf.org
> Onderwerp: Re: [YANG] so many naming scopes 
> 
> 
> Juergen Schoenwaelder writes:
> >So lets remove this "SHOULD NOT differ only in case" rule from the
> >language specification and lets start a guidelines document (or an
> >appendix for simplicity) where we collect such guidelines.
> 
> Sounds great.
> 
> Thanks,
>  Phil
> 
> 
> _______________________________________________
> YANG mailing list
> YANG@ietf.org
> https://www1.ietf.org/mailman/listinfo/yang
> 

_______________________________________________
YANG mailing list
YANG@ietf.org
https://www1.ietf.org/mailman/listinfo/yang