Hi Marvin,
I'll try to summarize the difference between Responses and Actions:
A Response is supposed to be exactly equivalent to a "manual" text response, without any magic implied. That is, manually typing "yes" in a client that doesn't support Quick Response is 100% equivalent to selecting the "yes" Quick Response in a client that supports the XEP. An implication of the absence of "magic" here is, that Responses only apply to the most recently received message, because without magic there is no "reference" from the response to the original message.
Actions are not compatible with clients that don't support Quick Response, as they require "understanding" the <action> element and responding with an <action-selected>. Because clients are free to generate unique ids here, the selection of an action is not limited to the last message, there is no problem relating the response to the original message. A "fallback" body is something that bots can choose to do anyway, by allowing to trigger the action via a plaintext response too (or comparable).
Hope that clears it up,
Syndace
Gesendet: Dienstag, 21. April 2020 um 13:08 Uhr
Von: "Marvin W" <[email protected]>
An: [email protected]
Betreff: Re: [Standards] Proposed XMPP Extension: Quick Response
Von: "Marvin W" <[email protected]>
An: [email protected]
Betreff: Re: [Standards] Proposed XMPP Extension: Quick Response
Hi,
Do I see it right, that the only relevant difference between a
"Response" and an "Action" is that legacy clients will display a
selected Response as message but won't display a selected Action at all?
Was it a deliberate decision to not have a fallback body for Actions?
Marvin
On 4/21/20 12:44 PM, [email protected] wrote:
> The XMPP Extensions Editor has received a proposal for a new XEP.
>
> Title: Quick Response
> Abstract:
> Quickly respond to automated messages.
>
> URL: https://xmpp.org/extensions/inbox/quick-response.html
>
> The Council will decide in the next two weeks whether to accept this
> proposal as an official XEP.
> _______________________________________________
> Standards mailing list
> Info: https://mail.jabber.org/mailman/listinfo/standards
> Unsubscribe: [email protected]
> _______________________________________________
>
_______________________________________________
Standards mailing list
Info: https://mail.jabber.org/mailman/listinfo/standards
Unsubscribe: [email protected]
_______________________________________________
Do I see it right, that the only relevant difference between a
"Response" and an "Action" is that legacy clients will display a
selected Response as message but won't display a selected Action at all?
Was it a deliberate decision to not have a fallback body for Actions?
Marvin
On 4/21/20 12:44 PM, [email protected] wrote:
> The XMPP Extensions Editor has received a proposal for a new XEP.
>
> Title: Quick Response
> Abstract:
> Quickly respond to automated messages.
>
> URL: https://xmpp.org/extensions/inbox/quick-response.html
>
> The Council will decide in the next two weeks whether to accept this
> proposal as an official XEP.
> _______________________________________________
> Standards mailing list
> Info: https://mail.jabber.org/mailman/listinfo/standards
> Unsubscribe: [email protected]
> _______________________________________________
>
_______________________________________________
Standards mailing list
Info: https://mail.jabber.org/mailman/listinfo/standards
Unsubscribe: [email protected]
_______________________________________________
_______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: [email protected] _______________________________________________
