[Standards] Taking a Machete to MIX

Tedd Sterr teddsterr at outlook.com
Mon May 21 16:06:30 UTC 2018

Fist impression: eight is a lot! (There's a lot of functionality to cover, I know.)

I presume the intention of splitting up MIX is to make it easier to both understand and implement, however, purely separating a large document into multiple smaller ones doesn't immediately achieve this (it just means you have to read several smaller documents instead of one big one.) Not to say that's all you've actually done, but it's hard to tell from this summary.

I'd expect 'Core' to contain all of the necessary/mandatory functionality, and then the additional satellite documents contain the nice-to-have-but-essentially-optional features. Which may well be the case, but it says that 'PAM' is mandatory, while 'Presence' is optional, and the rest are ...?

My point is that it's difficult to tell what's mandatory and what's optional, and so it's still going to require combing through all eight documents first to find out what's necessary and second to decide what's desirable.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.jabber.org/pipermail/standards/attachments/20180521/5c40489f/attachment.html>

More information about the Standards mailing list