XOM API for Processing XML with Java

["Michael Kay" <mike AT saxonica.com>]

> Ok. You might still consider the most trivial fix: On 
> overflow, have saxon simply change the prefix to one that's 
> already been bound to the same URI, and continue as normal. 

It works until you start using QNames in content. Because of this problem,
the XSLT and XQuery specs have moved firmly in the direction of treating
prefixes as significant and to-be-retained, though there are exceptions for
example where you generate two attributes of the same element using the same
prefix to refer to different URIs.

But if there were enough people hitting the limit to justify coding and
testing a recovery strategy for use when the limit is encoutered, then I
would be thinking of how to remove the limit.

Michael Kay
http://www.saxonica.com/