- In the modern world, people are afraid of XML
- 95% of people still don't understand XML namespaces
- In the modern world, people are afraid of XML
- 95% of people still don't understand XML namespaces
They are in XML to avoid naming clash, and they do that well. I haven't really seen a different mechanic to solve that problem.
- Non XML namespace supporting parsers: these are xml parsers people throw together without paying attention to the fact that attributes starting with "xml" are special and *must* be rejected.
- This results in people trying to shim namespaces in after the fact; which rarely goes well.
- There are two syntaxes: `<foo xmlns="urn:example"/>` vs `<myns:foo xmlns:myns="urn:example"/>`. Most people get caught up in the latter without understanding it, and you end up with *lots* of implementations that depend on `myns`, which is meant to be arbitary and can change between serialisation/deserialisation
- The W3C style for namespace inheritence forces each element to keep a reference to it's parent: a nightmare for simple data structures.