[JDEV] client proposal

[Scott Robinson]

Interleaved response.

Scott.

* Ryan Eatmon translated into ASCII [Wed, Sep 08, 1999 at 04:42:15PM -0500][<37D6D837.3A86CCEE at ti.com>]
[snap]
> > However, we've added a little coherency to our protocol. 
> > There is a tag called <ext/> which should be used by 
> > message modifiers to hold non-standard extensions.
> 
> I'm a little confused by what exactly you mean by that...  Are you
> saying that *are* using XML for the message body formatting but not
> dictating the base level of formatting supported by all clients?
> 

The Jabber-XML protocol does not specify a standard in formatting the
message. That is an option for clients to add. Thus, all extra-formatting
information (if not using MIME-extensions) should be placed in the <ext/>
field. Beyond that, the main jabber protocol doesn't care.

Further discussion of various formatting techniques is valid, but being
placed into the Jabber protocol isn't. We've very specifically left out
formatting information.

Either way, I don't believe what you specified was formatting but more a
example set of fields. Those are always valid within the XML spec.

[snip]