On February 9, 2017 7:20:22 AM Christian Hopps <[email protected]> wrote:
Martin Bjorklund <[email protected]> writes:
Christian Hopps <[email protected]> wrote:
Martin Bjorklund <[email protected]> writes:
> Christian Hopps <[email protected]> wrote:
>> 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?
Close, the idea was that I want to read all "foobar-value"s from all
modules that have that tag set.
Ok. What is the use case? It is probably not very common that
multiple modules have the exact same data structure defined.
My example is fairly forward looking I guess. The key thing to note is:
"implements" in the tag name. The idea being that one has defined a
common structure (or interface) and then associated that interface with
a tag. Now a client can, with a single xpath expression, access a value
in all modules that implement that interface.
I'm personally more excited by the use of tags as additional module
meta-data accessible via yang library. But also see no reason to preclude
this possible (even if unlikely) usage.
Lou
Thanks,
Chris.
_______________________________________________
netmod mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/netmod
