[Standards] Proposed XMPP Extension: Styling

Peter Saint-Andre stpeter at stpeter.im
Tue Nov 7 15:38:22 UTC 2017

On 11/7/17 8:16 AM, Marvin Gülker wrote:
> Am 06. November 2017 um 15:29 Uhr -0600 schrieb Sam Whited <sam at samwhited.com>:
>>> Not using something XML-based in a XEP's format
>>> also creates a precedence case from which we don't know where else it
>>> will come back at us when other XEPs are made.
>> I didn't understand this, sorry, could you please rephrase it or attempt
>> to clarify?
> Until now, XMPP is based on XML throughout all XEPs (that I'm aware
> of). >

We do have the "/me" markup in plaintext messages:


> This now introduces markup that's not XML for the first time,
> requiring a specific parser for it. What I'm saying is just that in
> future XEPs, it will be much easier to refer to this one and say "hey,
> we already have a XEP that's not based on XML, so what's wrong with
> this?". Consequently, XMPP clients are going to accumulate a plethora of
> parsers for different formats over time then.

I see your point. In fact, I have seen many private uses of XMPP that
"extend" it in just this way...


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 873 bytes
Desc: OpenPGP digital signature
URL: <http://mail.jabber.org/pipermail/standards/attachments/20171107/65eb1a85/attachment.sig>

More information about the Standards mailing list