Re: [netmod] derived-from() and derived-from-or-self() arguments

Ladislav Lhotka je 11.12.2015 ob 9:55 napisal: On 11 Dec 2015, at 09:23, Martin Bjorklund wrote: William Lupton wrote: Martin, Thanks for the reply and sorry for my delay in following up. Maybe I'm misunderstanding your point, but surely any

Re: [netmod] derived-from() and derived-from-or-self() arguments

Thanks all. > On 11 Dec 2015, at 09:50, Jernej Tuljak wrote: > > Ladislav Lhotka je 11.12.2015 ob 9:55 napisal: >> >> A code that evaluating these functions needs to know a lot about the >> underlying YANG data model anyway, so I think it is no problem to resolve >>

Re: [netmod] derived-from() and derived-from-or-self() arguments

> On 11 Dec 2015, at 12:22, Martin Bjorklund wrote: > > Jernej Tuljak wrote: >> Ladislav Lhotka je 11.12.2015 ob 9:55 napisal: On 11 Dec 2015, at 09:23, Martin Bjorklund wrote: William Lupton

Re: [netmod] derived-from() and derived-from-or-self() arguments

William Lupton wrote: > Martin, > > Thanks for the reply and sorry for my delay in following up. Maybe I'm > misunderstanding your point, but surely any node-set argument can be a > prefixed string, e.g I found this example in a NETMOD "Y26 again, > sorry" thread. >

Re: [netmod] derived-from() and derived-from-or-self() arguments

> On 11 Dec 2015, at 09:23, Martin Bjorklund wrote: > > William Lupton wrote: >> Martin, >> >> Thanks for the reply and sorry for my delay in following up. Maybe I'm >> misunderstanding your point, but surely any node-set argument can be a >>

Re: [netmod] derived-from() and derived-from-or-self() arguments

Martin, Thanks for the reply and sorry for my delay in following up. Maybe I'm misunderstanding your point, but surely any node-set argument can be a prefixed string, e.g I found this example in a NETMOD "Y26 again, sorry" thread. augment "/dnsz:zones/dnsz:zone/dnsz:rrset/dnsz:rdata" {

Re: [netmod] derived-from() and derived-from-or-self() arguments

Hi, William Lupton wrote: > Hi, > > I'm sure there's an obvious reason for this, but could someone explain why > these functions need a separate module-name argument rather than just using > that module's prefix on the identity-name argument? The only reason is that there are

[netmod] derived-from() and derived-from-or-self() arguments

Hi, I'm sure there's an obvious reason for this, but could someone explain why these functions need a separate module-name argument rather than just using that module's prefix on the identity-name argument? For example, I saw derived-from(x, "ex-module", "foo") in a recent message but (assuming