RFC 3920: 11.2, says xml-names is to be used, xml-names, section: 4.1, Namespace Constraint: Prefix Declared, says:
The namespace prefix, unless it is xml or xmlns, must have been declared in a namespace declaration<http://www.w3.org/TR/1999/REC-xml-names-19990114/#dt-NSDecl>attribute in either the start-tag of the element where the prefix is used or in an an ancestor element (i.e. an element in whose content<http://www.w3.org/TR/REC-xml#dt-content>the prefixed markup occurs). That pretty much sums it up, actually, xml-names goes on to say: This constraint may lead to operational difficulties in the case where the namespace declaration attribute is provided, not directly in the XML document entity <http://www.w3.org/TR/REC-xml#dt-docent>, but via a default attribute declared in an external entity. Such declarations may not be read by software which is based on a non-validating XML processor. Many XML applications, presumably including namespace-sensitive ones, fail to require validating processors. For correct operation with such applications, namespace declarations must be provided either directly or via default attributes declared in the internal subset of the DTD<http://www.w3.org/TR/REC-xml#dt-doctype> . So please go and log a bug against ejabberd. On Fri, Feb 29, 2008 at 3:45 PM, Sergei Golovan <[EMAIL PROTECTED]> wrote: > On 2/29/08, Norman Rasmussen <[EMAIL PROTECTED]> wrote: > > The point is that: > > > > <stream:stream > > xmlns:stream='http://etherx.jabber.org/streams'<http://etherx.jabber.org/streams%27> > > > > <message><gajim:die/></message> > > </stream> > > > > contains an unbound prefix 'gajim', so MUST be rejected by all XMPP > > parsers.. If you want to send xml that looks similar to that, you need > to > > transmit one of the following: > > Just find any rule in RFC 3290 which forbids this stanza with unbound > prefix and I'll immediately file a bugreport to ejabberd. > > -- > Sergei Golovan > -- - Norman Rasmussen - Email: [EMAIL PROTECTED] - Home page: http://norman.rasmussen.co.za/
