On 11/7/17 8:16 AM, Marvin Gülker wrote: > Am 06. November 2017 um 15:29 Uhr -0600 schrieb Sam Whited > <[email protected]>: >>> 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: https://xmpp.org/extensions/xep-0245.html > 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... Peter
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: [email protected] _______________________________________________
