RE: namespace prefix weirdness
> > In fact if Saxon delayed the decision to generate the xmlns="" > > undeclaration > > until after namespace fixup, it could reassign the default ("") > > prefix, and > > generate a more pleasing output tree. But it doesn't. > > So is this purely an aesthetic issue? It has no effect on subsequent > processing? > The choice of namespace prefixes, unfortunately, is not completely arbitrary, (a) because you might be using constructs that use namespace prefixes in element or attribute content, and (b) because you might require that the result document is valid against a DTD that disallows the presence of certain xmlns:xxx attributes. But the XSLT specification essentially mandates a minimum set of prefixes that must be declared in the result tree, while leaving the XSLT processor free to declare additional prefixes if it needs to. This is what Saxon has done in this case. Michael Kay
PURCHASE STYLUS STUDIO ONLINE TODAY!
Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!
Download The World's Best XML IDE!
Accelerate XML development with our award-winning XML IDE - Download a free trial today!
Subscribe in XML format