You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you want to modify NACM RFC8341 data node paths dynamically (ie not only given at startup time), you cannot do this using JSON encoding. The reason is that paths use instance-identifiers which need a namespace context which are not given by JSON.
XML encoding works fine.
Example using XML encoding:
…using JSON encoding #129](#129). The evaluation of NACM datanode rule path is assumed to be canonical namespace and cannot be overruled with `xmlns` rules.
If you want to modify NACM RFC8341 data node paths dynamically (ie not only given at startup time), you cannot do this using JSON encoding. The reason is that paths use instance-identifiers which need a namespace context which are not given by JSON.
XML encoding works fine.
Example using XML encoding:
The text was updated successfully, but these errors were encountered: