Re: [xmpp] RFC 3920 violates XML 1.0?

[Kevin Smith <[e-mail]>]

On Wed, Oct 20, 2010 at 6:06 PM, Matthew Miller <[e-mail]> wrote:
> I could be reading things wrong, but I believe RFC 3920 (specifically section 4.7.3) is violating XML 1.0[1].
>
> In section 3[2], it states the following:
>
> This specification does not constrain the application semantics, use, or (beyond syntax) names of the element types and attributes, except that names beginning with a match to (('X'|'x')('M'|'m')('L'|'l')) are reserved for standardization in this or future versions of this specification.
>
> Given that, the stream error condition <xml-not-well-formed/> from 4.7.3 would be violating this rule.  Note that this also applies to 3920bis.
>
> I'm not sure anyone's actually seen this, and I only discovered it as QA was filling in the corners of our latest work.  I'm also not sure what to do about this, either.  We could change this to "not-well-formed" or something like that in the bis drafts, but it could be a problem for implementations against the current spec.  Then again, this is a stream-level, non-recoverable error, so maybe it doesn't get encountered this way (-:

There's a train of thought that says that sending something the entity
won't understand in response to invalid XML is poetic justice :)

/K