-
Notifications
You must be signed in to change notification settings - Fork 123
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
1 changed file
with
15 additions
and
15 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -70,7 +70,7 @@ | |
parties. Other possible uses include voting and checking to-do list items. | ||
</p> | ||
<p> | ||
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. | ||
</p> | ||
<p> | ||
|
@@ -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. | ||
</p> | ||
<example caption="Romeo sends a message"><![CDATA[ | ||
<message to='[email protected]/balcony' id='744f6e18-a57a-11e9-a656-4889e7820c76' type='chat'> | ||
|
@@ -238,7 +238,7 @@ | |
</section2> | ||
</section1> | ||
<section1 topic='Business Rules' anchor='rules'> | ||
<p>Messages MUST NOT contain more then one <reactions> element</p> | ||
<p>Messages MUST NOT contain more than one <reactions> element</p> | ||
<p> | ||
A message containing a <reactions> element SHOULD be of type 'chat' | ||
or 'groupchat'. | ||
|
@@ -251,7 +251,7 @@ | |
with this specification. | ||
</p> | ||
<p> | ||
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. | ||
</p> | ||
<p> | ||
|
@@ -265,38 +265,38 @@ | |
</p> | ||
<p> | ||
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. | ||
</p> | ||
<section2 topic='Acceptable reactions' anchor='acceptable-reactions'> | ||
<p> | ||
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. | ||
</p> | ||
<p> | ||
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. | ||
</p> | ||
<p> | ||
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. | ||
</p> | ||
<p> | ||
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. | ||
</p> | ||
</section2> | ||
|
@@ -313,7 +313,7 @@ | |
be reacted to. | ||
</p> | ||
<p> | ||
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. | ||
</p> | ||
|