Aaargh, sorry! Once again not to the list. I am really not used to mailing list, sorry for this. ---------- Forwarded message ---------- From: Jehan Pagès <jehan.marmottard at gmail.com> Date: 2009/9/24 Subject: Re: [xmpp] Use of namespace in RFC 3920 To: Curtis King <cking at mumbo.ca> Hi, On Thu, Sep 24, 2009 at 1:42 PM, Curtis King <cking at mumbo.ca> wrote: > > What does this all gain us? I think there needs to-be a real benefit to > making such a change and I don't see one. Only a lot of potential pain. > IMHO, we should be tightening the scope of XML which can be sent not > loosening it. > That's indeed what I am doing. Right now XMPP is not really following XML rules. It made new ones, and make it more difficult. Let's make the example from my experience. I am writing currently an XMPP library, and I wrote also an XML library. My XML library, like most of the others I have tried (the one which deals well with XML and XML namespace RFC, at least), does expand the name of XML elements into qualified names. So honestly it doesn't care how it has been expanded, not does XML by definition. The problem is that the XMPP RFC does. And this is problematic and a lot of pain for me. If I want to really do like the XMPP RFC proposes, I should modify my XML parser with surcharge about where a namespace has been declared or set as default. This is what is lot of pain, according to me. This is the current XMPP RFC which tightens XML and make its use painful, not the opposite. Bye. Jehan
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.