[Standards] XEP-0375: View from Openfire
kevin.smith at isode.com
Tue Jul 12 13:04:59 UTC 2016
> 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:
>> 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
>> 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.
More information about the Standards