Re: [netmod] Module tags

[Martin Bjorklund <[e-mail]>]

Christian Hopps <[e-mail]> wrote:
> Martin Bjorklund <[e-mail]> writes:
> >> > Also I am not sure it is a good idea to add configuration meta-data
> >> > that really should be common across all modules into the modules
> >> > themselves.  Another approach is to keep a separate list with the
> >> > tags, indexed by modulename and revision.
> >>
> >> I don't understand what your getting at here. Are you referring to the
> >> grouping that gets used by a module author inside their module? The tags
> >> set for a given module are specific to that module only.
> >
> > I meant that instead of using the grouping in every module, you could
> > have a separate structure in your module:
> >
> >   container module-tags {
> >     list module {
> >       key "name revision";
> >       leaf name { ... }
> >       leaf revisoin { ...}
> >       leaf-list tag { ... }
> >     }
> >   }
> >
> > This way you will handle configuration of tags for all modules, and
> > they don't have to have a special uses statement.
> 
> 
> The reason I went with the grouping and in-module list was that I
> thought one could then create selecting xpath expressions, e.g.,
> 
>    get foobar-value[../tags="ietf:implements:foobar"]

I'm not sure I understand what you're after, but I am pretty sure that
if it can be done with a per-module structure that you propose, then
it can also be done with a single structure.

Is the idea that you want to read a certain leaf in a certain module,
but only if that module has been dynamically tagged with a certain
tag?

> I'm not sure if netconf supports this use of xpath directly, but one can
> imagine other systems or protocols supporting it.

NETCONF does support XPath filtering.


/martin