[Standards] how to treat invalid XMPP?

[Jakob Schroeter]

Hi,

Apparantly there is a number of software packages that generates invalid XMPP. 
I've seen at least unescaped ' and " in attribute values and character data, 
respectively.

http://www.xmpp.org/rfcs/rfc3920.html#xml states that an XMPP implementation 
must not generate such unescaped characters, and when it "receives such 
restricted XML data, it MUST ignore the data".

So far I just throw a parse error and disconnect the stream (when I 
implemented that, I never thought this would actually happen), but people 
complain about that. Also, that makes the receiving client look bad. However, 
just ignoring the offending character could possibly change the meaning of 
the data, so I don't think this is a good solution, either.

What do you think?

Jakob
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://mail.jabber.org/pipermail/standards/attachments/20070716/d42fa7d4/attachment.pgp