Re: [netmod] Adding a pre-existing leaf into a new 'choice' - NBC change?

[Juergen Schoenwaelder <[e-mail]>]

On Fri, Nov 23, 2018 at 01:02:03PM +0100, Ladislav Lhotka wrote:
> > 
> > Here is an attempt to rewrite things in a way according to how I
> > understand things works. It should be possible to describe what we
> > mean. If we can't do that, we have a bigger problem. (I have changed
> > only the last two sentences.)
> > 
> > OLD
> > 
> >    The leafref built-in type is restricted to the value space of some
> >    leaf or leaf-list node in the schema tree and optionally further
> >    restricted by corresponding instance nodes in the data tree.  The
> >    "path" substatement (Section 9.9.2) is used to identify the referred
> >    leaf or leaf-list node in the schema tree.  The value space of the
> >    referring node is the value space of the referred node.
> > 
> > NEW
> > 
> >    The leafref built-in type is restricted to the value space of some
> >    leaf or leaf-list node in the schema tree and optionally further
> >    restricted by corresponding instance nodes in the data tree.  The
> >    "path" substatement (Section 9.9.2) is used to identify a leaf or
> >    leaf-list node in the data tree. The value space of the leafref
> >    node is determined by the value space of the schema tree node
> 
> The term "value space of a schema tree node" is not defined.

OK. So we say 'the value space of the type of the schema tree node'.
 
> >    definining the referenced data tree node.
> 
> With require-instance=false there needn't be any referenced data tree node.

So we add "(irrespective whether the node exists or not).

> > This likely is not perfect yet but perhaps we manage to make it
> > perfect. ;-) What is not yet clearly described I think is what
> > 'further restricted by corresponding instance nodes in the data tree'
> > means (and that I think depends on require-instance). Perhaps add
> 
> Right. In this case it is not "further restricted" but rather there is a
> discrete set of possible values.

A discrete set of possible values is a restriction so I do not
understand your comment. So here is the next iteration:

NEW:

    The leafref built-in type is restricted to the value space of some
    leaf or leaf-list node in the schema tree and optionally further
    restricted by corresponding instance nodes in the data tree (see
    Section 9.9.3).  The "path" substatement (Section 9.9.2) is used
    to identify a leaf or leaf-list node in the data tree. The value
    space of the leafref node is determined by the value space of the
    type of the schema tree node definining the referenced data tree
    node (irrespective whether the referenced data tree node exists or
    not).

/js

-- 
Juergen Schoenwaelder           Jacobs University Bremen gGmbH
Phone: [phone]         Campus Ring 1 | 28759 Bremen | Germany
Fax:   [phone]         <https://www.jacobs-university.de/>