Hey folks, Travis pointed out a "bug" in ejabberd around the ordering of SASL2 elements, because XEP-0388 uses xs:sequence I suspect this isn't a bug in ejabberd, but a bug in XEP-0388 for using xs:sequence instead of xs:all - I suspect I wrote this and was just being rubbish at writing schemas, and didn't intend to impose an ordering, much less have receiving implementations depend on it. How much pain would it be to just change it? Dave.