Wen Bo Li

The least impactful way would be to only prefix when there is a conflict. Rob's example is an edge case: the naming would need to be done after processing each...

What about repeating options a-c (e-f) with: Prefix only nodes created by an augment? On Wed, Oct 7, 2020 at 4:47 PM Rob Shakir wrote: > @wenovus -- the problem...

I'm a bit worried here, does gNMI support qualified names in its [path proto](https://github.com/openconfig/reference/blob/master/rpc/gnmi/gnmi-path-conventions.md#constructing-paths)? If we do make the namespace (module name, node name), then this means that devices need...

Ok, here it is: [design doc](https://docs.google.com/document/d/16NTMl-evSojfUA2-thxLcvGIHCMNh37HKE6R6HXOY4k/edit?usp=sharing).

One follow-up question is what should be the RFC7951 JSON format? RFC7951 always adds a context name for the JSON, and since the level is virtual, it's unclear to me...

RFC7951, section 3: > This document defines JSON encoding for YANG data trees and their subtrees. Despite the above, I personally think the RFC failed to consider the full JSON...

It looks like the reason is because once augments are applied, they are removed from `Entry.Augments` during `Modules.Process`. This doesn't seem to be the right thing to do. Would having...

Thanks Stuart for reporting this issue and the suggested comment. I've added the documentation fix at https://github.com/openconfig/ygot/pull/736. @robshakir I think the right fix is that by default, users **don't** have...

Yes this does appear to be an oversight. When adding nodes to the `schematree` we should skip through choice/case elements instead of adding them. I think fixing involves changing `schemaTreeChildrenAdd()`...

Initial fix here: https://github.com/openconfig/ygot/commit/cf0bfc7828c97b83835e1c2872a782944a1103cf not done yet, look to get some feedback before finishing.