Names defined in MaterialX documents displace library names and cause strange behavior about materialx HOT 2 OPEN

This is a great observation, @JGamache-autodesk, and it's definitely worthwhile to fix this.

Although we could move imported libraries into their own document, this wouldn't necessarily resolve the overlap in namespaces between content documents and library documents, and references to angle would still be ambiguous.

Another option would be to leverage the existing namespace functionality in MaterialX to eliminate this overlap, e.g. assigning imported libraries to a namespace such as std by default. The user could always override this behavior when other namespaces were desired, but this ought to eliminate the namespace overlap between content documents and the standard libraries that are required for shader generation and rendering.

from materialx.

At first glance I like the idea of namespacing libraries.

Currently libraries are "flattened" and the namespace embedded as a prefix for the name (which can also cause name clashes) so maybe it could be as "easy" as adding a namespace to the "standard" libraries, It could even be per library: e.g. "std", "pbr", "bxdf" etc.

That said, I think it can get "tricky" if you start to namespace default type def, geom defs, unit defs etc.
I think these really should be reserved keywords and always loaded in first.

Maybe as a short-term validation change if the imported libraries clash with an existing loaded name this should throw an exception as most likely something will break.

from materialx.