[Standards] XEP-0375: View from Openfire

Sam Whited sam at samwhited.com
Tue Jul 12 16:10:54 UTC 2016

On Tue, Jul 12, 2016 at 11:01 AM, Dave Cridland <dave at cridland.net> wrote:
> Not *all* Final XEPs are going to be in Core in a Compliance Suite, simply
> because we might not have a compliance suite covering, say, IoT yet. And
> maybe there'll be exceptions to the XEP states (XEP-0054 is Historical, yet
> I'd argue it's Core), but we should be examining mismatches.

I'd argue there are two other types of XEPs: Those that are widely
used that we should discourage further use of (eg. XEP-0153 is one of
these and therefore should not be in the compliance suites in my

> - MIX doesn't (yet) belong here.

And those that are experimental and don't have many features, but that
we want to strongly encourage people develop and start working on like
MIX. These should be in the compliance suites (but only if there are
other alternatives available, such as 0045 in this example) in my


Sam Whited
pub 4096R/54083AE104EA7AD3

More information about the Standards mailing list