Etienne Philip Pretorius wrote:
Peter Saint-Andre wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 7/13/09 1:33 PM, Etienne Philip Pretorius wrote:
Hello List,
What stream error would one use to best indicate that there was an
invalid xml character in the stream?
invalid-xml or bad-format?
I think bad-format. The differences are described here:
http://tools.ietf.org/html/draft-ietf-xmpp-3920bis-00#section-5.8.3.1
http://tools.ietf.org/html/draft-ietf-xmpp-3920bis-00#section-5.8.3.12
Peter
- --
Peter Saint-Andre
https://stpeter.im/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkpbjKMACgkQNL8k5A2w/vxRwwCfWEDe22V4xX+fhknL390TzjfA
O3wAoMbSVF62QHfNp2s8tQhOL1n85ouV
=cdQA
-----END PGP SIGNATURE-----
Thank you Peter Saint-Andre.
Looks like <xml-not-well-formed/> would be even better, since it covers
the case most specifically (and choosing the most specific is
recommended by the spec). With XML, there is the challenge of weaning
ourselves from using the word "invalid" universally toward using the
more cumbersome word "well-formedness" for cases such as this where the
document isn't even parsable as XML. Validity would only be if the
server was validating and the XML was found to violate constraints
specified in a schema...
best wishes,
Brett
