It was pointed on TAPI call @ 05/21/2019 that Yang 1.0 cannot handle such (leaf)references to read-only entities (in Topology subtree) from an configurable sub-tree (ConnectivityService subtree). So now the
attributes are more loosely scoped/typed to any UUID, rather than to specific sub-tree namespace
Would this modification be required in other parts of the model? Shall we plan to roll back once YANG limitation is solved - of course if there is value (compile time control?).
It was pointed on TAPI call @ 05/21/2019 that Yang 1.0 cannot handle such (leaf)references to read-only entities (in Topology subtree) from an configurable sub-tree (ConnectivityService subtree). So now the attributes are more loosely scoped/typed to any UUID, rather than to specific sub-tree namespace