> *****************************************
> Camp 3 : Implemented Namespace Aware Code
> *****************************************
>
> What does code out there do?
one of the xml processors which is available with the cl-http server handles
namespaces with a mechanism similar to that which tim has described here. the
names are managed as symbols interned in packages. the packages are given two
names with indefinite extent - the uri and a unique name which is used as a
prefix when reserializing. in addition to these static bindings, both
attribute-based and pi-based bindings are supported - the first to be
conformant, the second in order to support dtd-based validation and attribute
defaulting. these bindings have dynamic scope and extent in the parsing process.
during the parse all names to be retained as part of the dom/dtd are interned
in the package which is named by the respective prefix. the prefixes are not retained.