Rob Shakir
Rob Shakir
This is indeed a spec error, thanks for pointing it out. We'll update the spec.
The specification is under active development. We did update the specification to cover some of these cases, and are continuing to work through clarifications that are needed based on completing...
I will look at this today -- I want to be *very* careful with making changes to keys in `Dir`, since there are expectations from existing consumers here. I'd like...
```yang module a { prefix "a"; namespace "urn:a"; leaf foo { type string; } } ``` ```yang module b { prefix "b"; namespace "urn:b"; leaf foo { type string; }...
In this case, there's only a clash if we look at the 'root' '/' that is not owned by any module itself. ygot does this, so ends up with a...
I don't think this is solely in ygot. My example was - but: ```yang module a { namespace a; prefix "urn:a"; container a { } } ``` ```yang module b...
I'm not quite sure that's true -- `augment` can be used in a number of different scenarios, many of which won't end up with clashing names -- if we do...
@wenovus -- the problem is that this will give non-deterministic behaviour in the `Entry` tree that we output. For example, if I run with module `a` and `b` from above,...
Sure - I'm open to adding additional options here -- can you start a doc please? (Google doc is probably best, we can share it with interested contributors.)
gNMI does not support prefixed paths - currently by design. Based on the usability problems I described above this is something we tried to avoid. Given that gNMI and YANG...