>However, they are still legal, and happen to be used in existing
applications.
>I don't think it's DOM's or XSLT's job to keep people from using them and
I
>can't see any official word from the W3C that would defend that.
This really was discussed. Declining to support them _was_ agreed to be as
legitimate a response as selecting either of the other two behaviors, and
it was left up to individual applications to pick any one of the three
options. ANY of these three will be behaviorally incompatable with either
of the others. (That's essentially why were were unable to resolve the
Great Namespace Debate; it wasn't so much that people were insisting on one
preferred solution, but that they found one solution entirely unacceptable
-- and there were folks opposed to all three.)
If you want to argue that Xerces and/or Xalan should consider adding an
option which would allow them to switch to one of the other modes... that
might be worth considering. This would mean carrying a bit more code
around, and would probably impose a few cycles of performance penalty even
in the "just warn me" mode. If you really need it, feel free to submit a
proposed patch...
