The Topic Naming Scheme Has No Collision Prevention

[ahassany]

The topic name substitutes / with _ in the absolute-schema-nodeid. This means interfaces_interface could result from
either interfaces/interface or from a hypothetical schema node literally named interfaces_interface. While unlikely in
practice with standard YANG modules, no normative statement rules this out or defines a canonicalization procedure. A
more robust approach would use a separator character that cannot appear in YANG identifier names (RFC 7950 §6.2 defines
that YANG identifiers consist only of alphanumerics, -, _, and ., so / → . would also create collision risk, but a
double-underscore __ or similar reserved separator could be unambiguous).