bartoszm
commented
2 years ago I will adjust the paths according to URI resolution mechanisms:
- trailing '/' for collection resources
- no trailing '/' for other resources details here: https://cdivilly.wordpress.com/2014/03/11/why-trailing-slashes-on-uris-are-important/
By checking the output two points highlight to be RFC8040/RFC7951 compatible:
1) -use-namespaces should be the default: The standard requirements should be the default.
2) final "/" should not be there per RFC8040. I see a "/" trailing all paths in the tool. This is not correct per RFC8040 paths: /data/tapi-common:context/