On 29.10.2016 12:51, Daniel Gultsch wrote: > Also in the interest of moving forward quickly I could for example > make the prosody MAM module (which is stuck on mam:0) use stanza ids > without upgrading the module to a possible mam:2) > > I created a PR for the stanza-id XEP. https://github.com/xsf/xeps/pull/270 > Author kinda seems to be on board but we wanted to run this by the > list very quickly for some additional feedback.
What Daniel wrote is correct, we had a substantial and productive chat earlier about that topic. I'd just like to add some background. Back when XEP-0359 aka. stanza-id where developed, the choice to not make the stanza-id feature discoverable by disco#info was made deliberate. The reasoning was that if you have a XEP Y (e.g. an archiving mechanism) which re-uses stanza-id, then by discovering the 'urn:xmpp:y:...' namespace you also have the confirmation that the business rules of stanza-id/XEP-0359 are enforced by the entity. This was driven by the design principle that something is perfect not when there is nothing more to add, but when there is nothing left to take away. (We have far to many overly complex XEPs out there). So 85% of the time chatting with Daniel I argued that we should not add a disco#info mechanism to stanza-id. But the argument in favor that really got me was that it would bring us more flexibility adding <stanza-id/> to existing XEPs. Given that the attempt to add stanza-id to MAM [1] ended in much frustration and got nowhere, I'm more then willing to specify a disco#info to stanza-ids. - Florian 1: https://github.com/xsf/xeps/pull/82
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: [email protected] _______________________________________________
