On Thu Sep 24 12:10:37 2009, Jehan Pagès wrote:
Then I wrote the XMPP parser based upon my XML parser, hence the XMPPparser gets the qualified name directly. I could change it of course and let the ns declarations into the attributes. It is not as though it was particularly difficult. But then I add an additional, thoughuseless, complexity (check not only the qualified names, but also howthey have been qualified) to my XMPP parser + the fact that I still don't see any reason for this + the fact that I will be refusingwell-formed and valid XML (so by principle, it is also annoying: XMPPnamespace usage are not following the W3C recommandations).
<foo/> is also well-formed XML. You - hopefully - reject that too, because it's not valid XMPP.
The spec says very little - intentionally - about the validity of the XML involved.
Dave. -- Dave Cridland - mailto:dave at cridland.net - xmpp:dwd at dave.cridland.net - acap://acap.dave.cridland.net/byowner/user/dwd/bookmarks/ - http://dave.cridland.net/ Infotrope Polymer - ACAP, IMAP, ESMTP, and Lemonade
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.