On 19 Jan 2018, at 17:55, Peter Saint-Andre <[email protected]> wrote: > I have a meta-level question: of what use are the compliance suites and > are the benefits worth the costs?
I think the main two benefits could be 1) Give an intended direction of travel 2) Give a guideline on what implementors practically need to implement these days for interop Given that neither of these are related to compliance, it does raise the question of whether the compliance suites are actually the right way to go about this. Perhaps reframing them as a pair of (continually updated - possibly not continually republished like the compliance suites) Informational XEPs on State-Of-The-Federation and Future-Of-The-Federation would be sensible. This would also very possibly reduce tensions between suites doing the ‘right thing’ conceptually protocol-wise and doing what is needed Right Now. /K > > Peter > > On 1/19/18 10:31 AM, Sam Whited wrote: >> Hi all, >> >> As you might know I've been trying to revive the compliance suites that the >> XSF last published (in draft/final form) in 2012. >> The compliance suites are lists of features and XEPs that serve three >> purposes: >> >> - To offer client/server authors a minimal set of XEPs that should be >> implemented to ensure a good user experience >> - To push the state-of-the-art forward and expand adoption of features that >> improve the user experience by encouraging authors to seek "compliance" >> - To improve interoperability between clients and servers on the network >> >> Naturally, these goals are sometimes in conflict and each XEP or feature in >> the suites needs to be considered carefully against all three goals. >> The latest (unaccepted) compliance suites can be found here, for reference: >> https://xmpp.org/extensions/xep-0387.html >> >> I'm looking fora new document shepherd to take over curating and publishing >> the compliance suites each year. The compliance suites are a bit different >> from other XEPs, so anyone wanting to take them over needs to be willing to >> work with the council to get them published in a reasonable timeframe (I've >> historically been very bad at this; start publishing early), and needs to >> understand that it's better to publish on time than to make them perfect (it >> looks bad if we're in 2018 and the "current" draft compliance suites are >> from 2012). Anyone wanting to take over should also of course follow XSF >> business and the XMPP community and generally keep an eye on new XEPs and >> adoption of existing XEPs. >> >> If that sounds like you, please reach out and I'd be happy to help you get >> started picking back up where I left off. >> >> Thanks, >> Sam >> _______________________________________________ >> Standards mailing list >> Info: https://mail.jabber.org/mailman/listinfo/standards >> Unsubscribe: [email protected] >> _______________________________________________ >> > > > _______________________________________________ > Standards mailing list > Info: https://mail.jabber.org/mailman/listinfo/standards > Unsubscribe: [email protected] > _______________________________________________ _______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: [email protected] _______________________________________________
