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. > >> 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. > > Yes, I'm aware of that, but I'm not sure if it supports the above > clarified idea which would use non-namespace "foobar-value" to fetch all > values along with an xpath check to see if a tag leaf-list contained a > tag value. I thought I read that netconf didn't support the latter at > least. If it can be expressed in XPath 1.0, then NETCONF supports it. Checking that a leaf-list contains a particular value is supported. /martin _______________________________________________ netmod mailing list [email protected] https://www.ietf.org/mailman/listinfo/netmod
