Given the size of MIX, I wonder if it wouldn't be sensible to split the XEP into a baseline XEP and one profile XEP for every use case.
I do believe that this would lead to smaller XEPs which are easier to review. And it would also make it clear which mechanisms and features are provided by "core" MIX and how they are used for a specific use case profile like persistent IM groupchats. The discussion whether or not MIX groupchats would have a subject, topic and/or description, and what being mandatory would then only be relevant to the "IM groupchat" MIX-profile XEP. Feels like an advantage, because that question is not relevant to other MIX use cases. And yes, I do have, for example, an idea for a MIX-profile for IoT in mind, which would IMHO benefit from a split. I did the same with the new OpenPGP XEPs (OX, XEP-0373/-0374) and, so far, I find this favourable over one big monolithic XEP. What do you think? - Florian
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: [email protected] _______________________________________________
