Re: Extending XEP-0313 with trimming support

Kevin Smith via Standards <[email protected]> Tue, 31 Mar 2026 11:59:17 +0100
Newsgroups gmane.network.jabber.standards-jig
Message-ID <[email protected]>
On 31 Mar 2026, at 11:46, Marvin W. via Standards <[email protected]> wrote:
> 
> I don't think this belongs into XEP-0313. It's an entirely new feature,
> arguably needing to pass the "Experimental" state of XEPs, including
> passing through Last Call. XEP-0313 is already Stable

I think Matthew’s change is doing this the right way for Stable - Stable allows changes to the XEP as long as they’re backwards/forwards compatible, which AFAICS Matthew’s proposal is.

> and probably
> could even be advanced to Final by now

Yes, if the XEP was final, not making the change because of being Final would be a very strong argument - but it’s not, and we should probably be following process for the state the XEP is in, rather than the state it might later reach.

> The pull request lacks an XML schema for the new namespace and element
> and thus formally can't be merged into a Stable XEP (with schema being
> mandatory for stable XEPs according to XEP-0001).

True, and true.

> I would propose to add time-based trimming as well.

Fair to want to expire by time, I think, although it’s only one query to get the desired ID from the time.

/K
_______________________________________________
Standards mailing list -- [email protected]
To unsubscribe send an email to [email protected]