[standards-jig] Essence of Jabber
mikelin at MIT.EDU
Fri Mar 8 09:00:27 UTC 2002
While we're on this topic, can someone explain, clearly, succinctly, and
with references to the XML Namespaces recommendation, precisely what, if
anything, makes the Jabber XML stream noncompliant with XML Namespaces?
We should really write something about this as an informational JEP,
since the issue comes up so much.
Who has been in an Athena lab for 12 hours.
On Fri, 2002-03-08 at 03:54, Fabrice DESRE wrote:
> Julian Missig wrote:
> > Yeah, I understand. I just assumed "don't break on unknown extensions -
> > just ignore" was supposed to be more of a parser-level rather than
> > application level, but yes, it should be application level too.
> Sorry to insist Julian, but this can't be at parser level. It has to
> be specified at application level ONLY - unless if you're using a custom
> parser of course (but who will ?).
> > I was
> > just emphasizing that we want to be sure we mention that the parser
> > should be XML compliant (I know some clients had non-validating
> > "parsers" which crashed on unknown elements...)
> IMHO, these are to distincts issues :
> 1) application behaviour : as you explained it, any jabber application
> should ignore unknow elements and recover gracefully.
> 2) XML compliance : sadly i'm sure that almost no jabber software is
> really XML compliant - namespaces are not handled properly in the
> servers (both open source and commercial), and this misbehaviour has led
> the client developpers to be somewhat liberal with namespaces.
> All this came from what I would reckon as a design fault : imposing a
> default namespace definition in the stream element, and even the prefix
> of the stream element !
> I hope that this will be fixed in jabberNG.
> Fabrice Desre - France Telecom R&D/DTL/TAL
> Tel: +(33) 2 96 05 31 43
> Fax: +(33) 2 96 05 39 45
> Standards-JIG mailing list
> Standards-JIG at jabber.org
More information about the Standards