Re: [YANG] import statement

Ladislav Lhotka <lhotka@cesnet.cz> wrote:
> 
> Martin Bjorklund píše v So 03. 05. 2008 v 21:10 +0200:
> > Ladislav Lhotka <lhotka@cesnet.cz> wrote:
> > > 
> > > Andy Bierman píše v So 03. 05. 2008 v 10:13 -0700:
> > > > It's a bit tricky.
> > > > Augment puts nodes from the augmenting namespace and
> > > > puts it 'someplace else', which could be the same namespace.
> > > > 
> > > > The uses-stmt takes nodes from 'somewhere else' and puts them 'here',
> > > > in the namespace for 'here'.
> > > 
> > > That's all right, but I still think one can imagine the augment
> > > statement to be replaced by the content of its target node (augmented as
> > > specified) and said content keeps its original namespace. If it is not
> > > so, then I am seriously confused and don't really know why augment can
> > > appear in different places in the schema tree (under module, container
> > > and list).
> > 
> > "augment" just extends some other data model, identified by the target
> > node.  This target node expression can be absolute or relative
> > (descendant form).  When augment appears under container or list, the
> > descendant form must be used.  It will extend the current data model
> > in the same module.  The use case is this:
> 
> Then augment performs two fundamentally different things

I don't agree.  Why?

> With the absolute form, can the target node be e.g., a container inside
> a grouping?

Currently you cannot augment a grouping.  This is something we have
been talking about though.  We should probably discuss this in a
separate thread on the netmod list.

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