[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [YANG] import statement
Andy Bierman píše v So 03. 05. 2008 v 10:13 -0700:
> Ladislav Lhotka wrote:
> > Juergen Schoenwaelder píše v So 03. 05. 2008 v 16:32 +0200:
> >
> >> There are also examples. An augment of foo-cont simply sticks nodes
> >> into the foo-cont container; there is no new instantiation of
> >> foo-cont.
> >>
> >
> > Example on pages 82 and 83 contradicts what you are saying: the augment
> > statement in namespace http://example.com/schema/ds0 takes the schema
> > subtree defined by "container interfaces" in namespace
> > http://example.com/schema/interfaces, augments it and effectively places
> > the result at the spot of the augment statement in the
> > http://example.com/schema/ds0 namespace.
> >
>
> 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).
Lada
>
>
> > Lada
> >
>
> Andy
>
> _______________________________________________
> YANG mailing list
> YANG at ietf.org
> https://www.ietf.org/mailman/listinfo/yang
--
Ladislav Lhotka, CESNET
PGP Key ID: E74E8C0C
_______________________________________________
YANG mailing list
YANG at ietf.org
https://www.ietf.org/mailman/listinfo/yang