I think you should also describe what a XMPP client should do upon
receiving good XML 1.0 which is also bad XML 1.1.
My preference is that the client "SHOULD NOT" or "MUST NOT" interpret
it as a stream error.
On Oct 13, 2008, at 3:28 PM, Peter Saint-Andre wrote:
OK here's what I have now in my working copy of rfc3920bis:
***
12.3. Well-Formedness
There are two varieties of well-formedness:
o "XML-well-formedness" in accordance with the definition of "well-
formed" in Section 2.1 of [XML].
o "Namespace-well-formedness" in accordance with the definition of
"namespace-well-formed" in Section 7 of [XML-NAMES].
The following rules apply.
An XMPP entity MUST NOT generate data that is not XML-well-formed.
An XMPP entity MUST NOT accept data that is not XML-well-formed;
instead it MUST return an <xml-not-well-formed/> stream error and
close the stream over which the data was received.
An XMPP entity MUST NOT generate data that is not namespace-well-
formed. An XMPP server SHOULD NOT route or deliver data that is not
namespace-well-formed, but MUST NOT return a stream error in
response
to the receipt of such data.
Note: Because these restrictions were underspecified in an
earlier
revision of this specification, it is possible that
implementations based on that revision will send data that does
not comply with the restrictions; an entity SHOULD be liberal in
accepting such data.
***
__________________
Robert Quattlebaum
Jabber: [EMAIL PROTECTED]
eMail: [EMAIL PROTECTED]
www: http://www.deepdarc.com/
