168
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 07:41, 19 April 2018
, 07:41, 19 April 2018→Undefined Sate
| Line 1: | Line 1: | ||
== Undefined Sate == | == Undefined Sate, contradiction regarding execute, execute as attribute and action == | ||
There is a little issue with XEP-0050: in section 3.4 bullet 3, it's is | There is a little issue with XEP-0050: in section 3.4 bullet 3, it's is | ||
| Line 19: | Line 19: | ||
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 | ||
Part of this confusion is that XEP-0050 makes multiple statements about execute (both the attribute and the action): | |||
In 2.4.2: "The "execute" attribute defines which of the included actions is considered the equivalent to "execute" for this stage." | |||
In 3.4: "If the <actions/> possesses the "execute" attribute, that value is the default button or option. If the <actions/> does not possess the "execute" attribute, there is no default button or option." | |||
and "The "execute" attribute SHOULD NOT specify a value that does not match one of the allowed actions." | |||
and, talking about the action: "The action "execute" is always allowed, and is equivalent to the action "next"." | |||
In 4.2: "The "execute" attribute specifies what the action "execute" is equivalent to." | |||
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 | |||