On Sun, May 15, 2005 at 03:51:58PM +0200, Tijl Houtbeckers wrote: > On Sun, 15 May 2005 09:12:21 +0200, Julian Missig <[EMAIL PROTECTED]> > wrote: > > > > >It is, however, against typical Jabber convention. It's legal XML, but > >it's not Jabber convention. Jabber convention is to use the <x/> element. > > > >Julian > > I have been using and developing with Jabber for many years now, and never > took notice of this "convention". Might I add that if such a convention > exists, I propose it to be deemed "silly" and no longer be followed. +1 > please.
+1 > Seriously now.. what's the point of calling it x? Maybe in the era before > namespace-aware parsers this could have been *slighty* usefull, but > nowadays? I suppose that's the reason. The namespaces of those extensions were typically jabber:x:something. There was another such convention: having the direct child element of an <iq/> being called query. Fortunately, we are leaving that path, as well. I even believe early versions of jabberd actually didn't check for 'presence', 'iq' or 'message', but rather the first character... -- Groetjes, ralphm _______________________________________________ jdev mailing list [email protected] http://mail.jabber.org/mailman/listinfo/jdev
