Lists Home |
Date Index |
> 2. Enforce sanity, as defined at:
> by saying that once a (markup-level) namespace is declared, it
> cannot be re-declared in the same document unless it has the same
> 4. (A general thing, but has a particular impact with namespaces)
> Have an option to retain user-specified but syntax-level
> artifacts such as namespace prefixes, so that identity
> transformations (for example) are able to create
> identical-looking XML. For some reason, users grow attached to
> the prefixes that they use and get upset when they're substituted
> for 'ns0', despite the fact that the expanded names are just the
It seems that (4) may conflict with (2) in where XML documents are merged.
Will you use some form of prefix mangling in those cases?