On Fri, Sep 15, 2017 at 01:40:07PM +0200, Martin Bjorklund wrote:
>
> Also, what is mounted under a mount point is not defined in the
> schema, so a tool cannot generate this from the YANG modules.
>
This sounds broken. Manually edited tree diagrams will be a source of
pain.
> > I definitely think that "x" is a bit confusing since it both means
> > "RPC" and also "status deprecated" depending on where it is.
>
> Possibly. "x" for "deprecated" comes from smidump. "x" for "execute"
> (rwx) is of course common. So if we should change something it is
> probably "x" for "deprecated". But "x" looks better than "d"...
>
Yep, I am probably guilty for the deprecated 'x'. For obsolete,
smidump creates an 'o', so you have
+--- foo
x--- bar
o--- baz
and I guess I visually liked it (and there was no execute in SNMP
land). I guess I still kind of like this. If I would start from
scratch for YANG, I would probably not use
rw for configuration data
ro for non-configuration data
-x for rpcs and actions
-n for notifications
mp for schema mount points
but rather single letters, e.g.
c for configuration data
s for non-configuration data
r for rpcs and actions
n for notifications
m for schema mount points
but this is a significant change to what we have done so far and
finding agreement on a new notation is likely difficult.
/js
--
Juergen Schoenwaelder Jacobs University Bremen gGmbH
Phone: +49 421 200 3587 Campus Ring 1 | 28759 Bremen | Germany
Fax: +49 421 200 3103 <http://www.jacobs-university.de/>
_______________________________________________
netmod mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/netmod
