- Reactions are typically displayed in a summarizing fashion visually attached + Reactions are typically displayed in a summarized fashion visually attached to the message they belong to.
@@ -154,8 +154,8 @@ client sends a <message> stanza containing a <reactions> element. The chosen emoji is included in a <reaction> element within the <reactions> element. The message is referred to by including its - id or in MUCs its stanza-id as defined in &xep0359; in the 'id' attribute - of the reactions element. + ID or in MUCs its stanza-id as defined in &xep0359; in the 'id' attribute + of the <reactions> element.
Messages MUST NOT contain more then one <reactions> element
+Messages MUST NOT contain more than one <reactions> element
A message containing a <reactions> element SHOULD be of type 'chat' or 'groupchat'. @@ -251,7 +251,7 @@ with this specification.
- A receiving client SHOULD show reactions attached to the message they where + A receiving client SHOULD show reactions attached to the message they were in response to. Reactions MAY be displayed in a summarized fashion.
@@ -265,21 +265,21 @@
If a message is updated using &xep0308;, the 'id' attribute of the - <reactions> element SHOULD reference the original message id. + <reactions> element SHOULD reference the original message ID. A receiving entity SHOULD accept messages with a <reactions> element - referencing a message correction and SHOULD handle such element as if - it was using the message id of the original message. + referencing a message correction and SHOULD handle such elements as if + it was using the message ID of the original message.
- In direct conversations, a reaction MUST only be accepted if the senders + In direct conversations, a reaction MUST only be accepted if the sender's bare JID matches the bare JID of any of the two involved parties.
In MUCs and MUC PMs, the recipient SHOULD ensure that the real bare JID of the sending occupant did not already send a reaction to that message to accept it as a new reaction, e.g. by keeping track of leave/join - presences since the message was send. This implies that in semi-anonymous + presences since the message was sent. This implies that in semi-anonymous MUCs it MAY be impossible to attach reactions to a message received from the history. A reaction MAY still be a valid reaction update (as per the next paragraph) if it was not accepted as a new reaction. @@ -287,16 +287,16 @@
A reaction MUST only be considered an update if it orignates from the same sender as a previous reaction message. In direct conversations, this means - the bare JID MUST match the original bare JID. In MUCs and MUC PMs the - senders full JID MAY not match the original full JID, but the recipient + the bare JID MUST match the original bare JID. In MUCs and MUC PMs, the + sender's full JID MAY not match the original full JID, but the recipient MUST ensure that the real bare JID of the sending occupant is the same as the real bare JID of the previous reaction message, e.g. by keeping track of leave/join presences.
If a message containing a <reactions> element arrives delayed, which - means it carries a <delay/> element, as defined in &xep0203; it SHOULD - only be accepted, if no newer reaction from the same sender was already + means it carries a <delay/> element as defined in &xep0203;, it SHOULD + only be accepted if no newer reaction from the same sender was already accepted.
- For other message types the sender should use the 'id' from a &xep0359; + For other message types, the sender should use the 'id' from a &xep0359; <origin-id> if present, or the value of the 'id' attribute on the <message> otherwise.