[Standards] Call for Experience: XEP-0050: Ad-Hoc Commands

Tedd Sterr teddsterr at outlook.com
Tue May 26 20:24:06 UTC 2020

It's worth noting "the execute issue" and considering a fix before advancing.

>From "Council Minutes 2018-04-18" - https://mail.jabber.org/pipermail/standards/2018-April/034790.html

3) XEP-0050 'execute' Issue
… Kev explains that it's possible to have an illegal state because 'execute' is overloaded in weird ways - there is an execute action, and an execute attribute for setting a default action, but the execute-attribute default action is not the execute action, which may well be invalid. … Dave attempts to clarify that the default for the execute action is 'complete', unless other actions are specified whereby the default is 'next' which may not even be present - Kev confirms.
Kev mentions PR #598 (https://github.com/xsf/xeps/pull/598) as his attempt to address the issue by unifying the execute attribute and action into one, and that everyone should consider carefully whether this solution will break anything.
Kev explains further that currently if execute is set to 'complete' and the execute command is run, it's actually 'next' that's run; and if there is no 'next' action defined, that's obviously a problem. Dave is justifiably mystified.
Dave suggests an alternative solution might be to deprecate the execute action; Kev thinks this could be a better solution.
Peter utters from the shadows that he recently found his marked-up paper copy of XEP-0050 from several years ago - Kev asks whether it fixes this issue - alas, they are mostly editorial notes.
Dave repeats his suggestion of deprecating the execute action, on the basis of unexpected behaviour; Sam agrees this seems like a good solution as multiple people have been confused in a similar way.

Also relevant: PR #591 (https://github.com/xsf/xeps/pull/591)

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.jabber.org/pipermail/standards/attachments/20200526/8f036bf3/attachment-0001.html>

More information about the Standards mailing list