[Standards] LAST CALL: XEP-0423 (XMPP Compliance Suites 2020)

Guus der Kinderen guus.der.kinderen at gmail.com
Wed Oct 23 18:20:46 UTC 2019

Thanks for the effort to push this well before the end of the year. :)

On my first reading, I noticed two things:

XEP-0385 "Stateless Inline Media Sharing (SIMS)" is mentioned both in
section 1.1 "Changes since 2019", but also in section 3 "Future
Development". Is that an error, or intended? I'd argue that if you're
including something in this edition of the CS, then there's no point of
adding it also as a 'keep an eye on this one for the future'

I am surprised to see XEP-0392 "Consistent Color Generation" in the CS.
What's the rationale to include it? Without giving this to much thought,
I've regarded this XEP more as a useful guide for those who'd explicitly
choose to implement a, rather than something that is required to implement
to be considered 'compliant'. I'm expecting that there are projects that
explicitly not want this (in favor of marketing-driven decisions on
look-and-feel, themes, colors, etc). Is the functionality described this
XEP of such a nature that we'd be willing to mandate it?



On Wed, 23 Oct 2019 at 17:07, Jonas Schäfer <jonas at wielicki.name> wrote:

> This message constitutes notice of a Last Call for comments on
> XEP-0423.
> Title: XMPP Compliance Suites 2020
> Abstract:
> This document defines XMPP application categories for different use
> cases (Core, Web, IM, and Mobile), and specifies the required XEPs
> that client and server software needs to implement for compliance with
> the use cases.
> URL: https://xmpp.org/extensions/xep-0423.html
> This Last Call begins today and shall end at the close of business on
> 2019-11-06.
> Please consider the following questions during this Last Call and send
> your feedback to the standards at xmpp.org discussion list:
> 1. Is this specification needed to fill gaps in the XMPP protocol
> stack or to clarify an existing protocol?
> 2. Does the specification solve the problem stated in the introduction
> and requirements?
> 3. Do you plan to implement this specification in your code? If not,
> why not?
> 4. Do you have any security concerns related to this specification?
> 5. Is the specification accurate and clearly written?
> Your feedback is appreciated!
> _______________________________________________
> Standards mailing list
> Info: https://mail.jabber.org/mailman/listinfo/standards
> Unsubscribe: Standards-unsubscribe at xmpp.org
> _______________________________________________
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.jabber.org/pipermail/standards/attachments/20191023/36621141/attachment-0001.html>

More information about the Standards mailing list