moparisthebest
/
xeps
mirror of https://github.com/moparisthebest/xeps
1
0
Fork 0
Code Issues Releases Wiki Activity

editorial

This commit is contained in:
Steve Kille 2018-06-05 13:01:40 +01:00
parent ba8a5d0fa3
commit 69234eea15
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
xep-0369.xml
View File

@ -412,7 +412,7 @@
<li>XMPP clients can implement MUC and this specification in a way that provides a coherent user experience.</li>
<li>XMPP servers can implement this specification and also provide a MUC interface in order to support clients that only implement MUC.</li>
</ul>
<p>This specification gives guidance on supporting both MUC and MIX representations of chatrooms.</p>
<p>MIX gives guidance on supporting both MUC and MIX representations of chatrooms.</p>
</section1>
<section1 topic='Requirements' anchor='reqs'>
@ -1161,7 +1161,7 @@
<body>Harpier cries: 'tis time, 'tis time.</body>
<mix xmlns='urn:xmpp:mix:core:0'>
<nick>thirdwitch</nick>
<jid>123456#coven@mix.shakespeare.example</jid>
<jid>hag66@shakespeare.example</jid>
</mix>
</message>
]]></example>
@ -1184,7 +1184,7 @@
The messages sent to participants have a different message id to the originally submitted message. This does not impact most recipients, but it does not allow the message originator to correlate the message with the submitted message. To address this the MIX channel MUST include an additional &lt;submission-id&gt; element in the &lt;mix&gt; element of the message copy going back to the originator's bare JID. The &lt;submission-id&gt; element holds the original id provided by the sender. This enables the originator to correlate the received message with the message submitted.
</p>
<example caption="Channel Reflects Message back to Originator"><![CDATA[
<message from='coven@mix.shakespeare.example'
<message from='coven@mix.shakespeare.example/123456'
to='hag66@shakespeare.example'
id='77E07BB0-55CF-4BD4-890E-3F7C0E686BBD'
type='groupchat'>