On Sun, 18 Apr 2004 17:26, Matthias Wimmer wrote: > Hi Alexey! > > The <text/> element is optional. Maybe this it not clear in the part you > quoted, where you could think only the text() node contained in the > <text/> element is optional. > At at least in the schemas the <text/> element is defined to be there 0 > or 1 times (section C.1). > > Tot kijk > Matthias
I have a question about the <text/> which is probably more of a thing which I should have asked while this protocol was being drafted (only I wasn't into Jabber quite enough at the time) but... Why is <text/> in the "urn:ietf:params:xml:ns:xmpp-streams" namespace? Wouldn't it be easier for everyone involved if the optional text content was always in the _same_ namespace (say, "jabber:client"?) Then you could use methods for getting its value which would be the same for all kinds of error, instead of having to implement the same thing over and over... Mini-rant over. TX -- Trejkaz Xaoza <[EMAIL PROTECTED]> _______________________________________________ jdev mailing list [EMAIL PROTECTED] https://jabberstudio.org/mailman/listinfo/jdev
