Another and somewhat radical idea is to think of 'yang-data' as defining a data
node, like a 'container', but not a config or opstate node. Yes, this is
different from rc:yang-data, which defines a transparent node, like 'choice',
but maybe it's okay if we can get the substitution groups part
On Wed, Apr 18, 2018 at 10:47 AM, Martin Bjorklund wrote:
> Hi,
>
> Andy Bierman wrote:
> > On Wed, Apr 18, 2018 at 10:26 AM, Kent Watsen
> wrote:
> >
> > > I like Andy's proposal below, for the argument of the 'yang-data'
> > > statement to encode some meta-information regarding the
> context/
Hi,
Andy Bierman wrote:
> On Wed, Apr 18, 2018 at 10:26 AM, Kent Watsen wrote:
>
> > I like Andy's proposal below, for the argument of the 'yang-data'
> > statement to encode some meta-information regarding the context/namespace
> > in which it's used, but I wonder how it really works. For ins
On Wed, Apr 18, 2018 at 10:26 AM, Kent Watsen wrote:
> I like Andy's proposal below, for the argument of the 'yang-data'
> statement to encode some meta-information regarding the context/namespace
> in which it's used, but I wonder how it really works. For instance, would
> "top" and "error-info
Hi,
[Kent, your email program has messed up the quoting in this thread.
It becomes quite difficult to follow. And no, please don't invent a
new quoting style in every email thread...]
Kent Watsen wrote:
> I like Andy's proposal below, for the argument of the 'yang-data'
> statement to encode so
I like Andy's proposal below, for the argument of the 'yang-data' statement to
encode some meta-information regarding the context/namespace in which it's
used, but I wonder how it really works. For instance, would "top" and
"error-info" be the only allowed base-path values for the argument? and