This is not how namespaces are designed to work, and it’s going to cause massive problems for anyone writing any sort of software to process XForms, whether it’s DOM, SAX. XSLT, XPath, or almost anything else. XForms elements should be able to be recognized by their namespace alone. You should not have to care about the host language in which they’re embedded. If we’re going to start changing the namespace for every host language that comes along, we might as well not have namespaces in the first place.
If you believe there is a single, more important, absolute requirement in the land of XML than that of the proper usage of XML namespaces: You obviously don’t understand XML.
That said, there’s got to be at least some sort of reasonable explanation to the mentioned madness quoted above, doesn’t there?
Somebody care to clue me in, cuz’ I have to admit, at first sight it very much seems like a few loose screws have rattled off the W3C XHTML2/XForms working groups wagon wheel, placing some serious doubt upon the ability of these same mentioned groups to produce a quality specification that even closely resembles any of their 1.0 counterparts.