416
edits
Difference between revisions of "XEP-Remarks/XEP-0050:Ad-Hoc Commands"
Jump to navigation
Jump to search
XEP-Remarks/XEP-0050:Ad-Hoc Commands (view source)
Revision as of 20:41, 17 April 2020
, 20:41, 17 April 2020no edit summary
| (2 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
{{remarks}} | |||
== Undefined Sate, contradiction regarding execute, execute as attribute and action == | == Undefined Sate, contradiction regarding execute, execute as attribute and action == | ||
| Line 19: | Line 21: | ||
Original standards@ post: https://mail.jabber.org/pipermail/standards/2015-August/030137.html | Original standards@ post: https://mail.jabber.org/pipermail/standards/2015-August/030137.html | ||
=== Contradiction === | |||
Part of this confusion is that XEP-0050 makes multiple statements about execute (both the attribute and the action): | Part of this confusion is that XEP-0050 makes multiple statements about execute (both the attribute and the action): | ||
| Line 29: | Line 33: | ||
In 4.2: "The "execute" attribute specifies what the action "execute" is equivalent to." | In 4.2: "The "execute" attribute specifies what the action "execute" is equivalent to." | ||
Clearly the statements "The "execute" attribute specifies what the action "execute" is equivalent to." (in 4.2) and "The action "execute" is always allowed, and is equivalent to the action "next"." (in 3.4) contradict each other. | |||
There are currently at least two PR which try to improve the situation, an overview is given in https://github.com/xsf/xeps/pull/591#issuecomment-373313491 | There are currently at least two PR which try to improve the situation, an overview is given in https://github.com/xsf/xeps/pull/591#issuecomment-373313491 | ||