once this deletion XEP is stable, could it be merged into XEP-0363? Otherwise, it looks like an extension of an extension, which is a bit odd. It’s optional anyway, or we could explicitly note in the document that it’s a new experimental feature, like how a stable release software can still include some experimental features.
On Tue, 10 Nov 2026 at 16:06, Goffi <goffi@goffi.org> wrote:
Hi Matthew,
I've raised my concerns about XEP-0498 duplication, however as the author of this spec, I'm biased, and if other council members don't see a problem here, I won't block (experimentation will tell anyway).
But I have a problem with that added to a stable XEP. This is not a correction following feedback, implementation issue, or evolution of technologies, this is a brand new feature, and it would go directly to stable without going though the normal, experimental workflow. That means that if there is anything to change (like problem seen during experimentation), it will be a mess to fix.
I agree it would have been better if it was included much earlier or from the beginning. But it would not be the first time we have updated a XEP with features which were within the scope of that XEP, and I don't see the harm in it, if done with review. If there are indeed any future changes required in this feature, it is not carved in stone, we have updated Stable XEPs many times before (maybe I set my own trap here by pushing to rename "Draft" to "Stable" years ago!).
The downsides of splitting important related functionality across multiple XEPs outweigh any such concerns for me.
That said, my objections are not strong and if this is the consensus, I can go with that. I want to see this deployed more than I care what XEP number it has. I shall update or submit a replacement PR. Thanks for your consideration!
Regards, Matthew _______________________________________________ Standards mailing list -- standards@xmpp.org To unsubscribe send an email to standards-leave@xmpp.org