Lists Home |
Date Index |
> Alan Gutierrez wrote:
>> In my SAX library, XStrategy, I combined namespaces and events.
>> The XStrategy framwork maintains a stack of namespaces in scope
>> by default. It seemed impossible to get anything done without it.
> If you're int he unfortunate situation of needing to resolve namespace
> prefixes in attribute values and element content, as is the case in an
> XSLT processor or a schema validator, then you absolutely need to do
> this. However, probably at least 90% of use cases are much simpler and
> just need to know the namespaces of each element and attribute, and this
> doesn't require any extra work.
For people inventing languages which use Qnames in element or attribute
values, I commend making your own prefix->namespace declaration element
instead of piggybacking on the XML namespaces system.
That way you can have sanity: namespace must have prefix, prefix cannot be
remapped or reused, no default namaspace. I did this in Schematron without
The XML Namespaces rec does not cover Qnames in values: that is semantics
that is up to the schema developer. XSLT does it one way, XML Schemas does
it another way, and Schematron does it another.