[Standards] XEP-0375: View from Openfire

Guus der Kinderen guus.der.kinderen at gmail.com
Tue Jul 12 14:55:47 UTC 2016


Perhaps we shouldn't mention MIX at all in this particular compliance
suite. The MIX specification isn't definitive by a long shot, and although
there are some early implementations, it hardly qualifies for something to
be compliant with nowadays. I'd save it for the next editions of the
complicance suite specification.

I'd like to see the "core server" specifications to be removed completely.
As it stands, it's of little use, and I doubt if there are server
implementations that strive to be "core", but not "advanced".

- Guus

On 12 July 2016 at 15:04, Kevin Smith <kevin.smith at isode.com> wrote:

>
> > On 12 Jul 2016, at 13:49, Ralph Meijer <ralphm at ik.nu> wrote:
> >
> > On 2016-07-12 05:11, Sam Whited wrote:
> >> I've tried to address some of this feedback here:
> >>
> >> https://github.com/xsf/xeps/pull/206
> >>
> >> I think the only thing I left out was getting rid of the IM compliance
> >> suites (in case any of the IoT crowd chime in).
> >>
> >> I also added MIX as a possible provider of "Group Chat" and merged the
> >> web compliance suites into a single item, making BOSH and Websockets
> >> interchangeable. More suggestions for web-friendly features would be
> >> appreciated from web client authors (maybe they're similar to mobile
> >> concerns?).
> >>
> >> Let me know what you think. It could probably use a bit of description
> >> about what the providers column means now; I envision a comma as being
> >> an OR as in "MUC or MIX".
> >
> > Although I strongly believe in the prospects of what MIX will bring to
> > the table, to me, it doesn't make sense to put in any reference to MIX
> > at this point in time. The point of this suite is to get
> > interoperability between a wide array of client and server
> > implementations so that things Just Work™. MIX is nowhere near mature
> > enough that this is achievable within 2016.
>
> I think that’s right. I think a note about MIX might be well-placed, but
> not as part of the compliance tables.
>
> /K
>
> _______________________________________________
> Standards mailing list
> Info: http://mail.jabber.org/mailman/listinfo/standards
> Unsubscribe: Standards-unsubscribe at xmpp.org
> _______________________________________________
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.jabber.org/pipermail/standards/attachments/20160712/7b0454e3/attachment.html>


More information about the Standards mailing list