moparisthebest/xeps
1
0
Fork 0
mirror of https://github.com/moparisthebest/xeps synced 2024-11-25 02:32:18 -05:00
Code Issues Releases Wiki Activity

Editorial

Browse Source
This commit is contained in:
Steve Kille 2018-06-06 14:09:04 +01:00
parent d01853d08f
commit 8480980769
1 changed files with 17 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

25
xep-0403.xml
View File

@ -38,6 +38,14 @@
<shortname>MIX-PRESENCE</shortname> <shortname>MIX-PRESENCE</shortname>
&ksmithisode; &ksmithisode;
&skille; &skille;
<revision>
<version>0.2.1</version>
<date>2018-06-06</date>
<initials>sek</initials>
<remark><p>
</p></remark>
</revision>
<revision> <revision>
<version>0.2.0</version> <version>0.2.0</version>
<date>2018-06-05</date> <date>2018-06-05</date>
@ -48,7 +56,8 @@
Add vCard routing; Add vCard routing;
Add mix information to presence; Add mix information to presence;
</p></remark> </p></remark>
</revision><revision> </revision>
<revision>
<version>0.1.0</version> <version>0.1.0</version>
<date>2018-05-21</date> <date>2018-05-21</date>
<initials>sek</initials> <initials>sek</initials>
@ -63,7 +72,7 @@
</p> </p>
<p> <p>
MIX-CORE shares participant JIDs, which enables messages to be exchange directly. MIX-CORE shares participant JIDs, which enables messages to be exchange directly.
To facilitate communication between clients IQ stanza messages MAY be routed through a MIX channel. This is needed because many XMPP clients will block IQ stanzas from an unknown JID. Routing IQ stanzas avoids this. To facilitate communication between clients IQ stanzas MAY be routed through a MIX channel. This is needed because IQ stanzas from an unknown JID may be blocked. Routing IQ stanzas through the channel avoids this.
</p> </p>
</section1> </section1>
@ -76,8 +85,8 @@
<li>The mechanism must work cleanly for participants with multiple clients.</li> <li>The mechanism must work cleanly for participants with multiple clients.</li>
<li>Standard presence messages must be used to share presence.</li> <li>Standard presence messages must be used to share presence.</li>
<li>Nick changes should be visible as changes (and not as a new user).</li> <li>Nick changes should be visible as changes (and not as a new user).</li>
<li>Where &xep0404; (MIX-ANON) is not used, participants must be able to directly contact other participants.</li> <li>Where &xep0404; (MIX-ANON) is not used, a mechanism is needed so that participants are able to directly contact other participants.</li>
<li>IQ stanzas, including vCard, can be communicated through a channel.</li> <li>IQ stanzas, including vCard, can be be sent indirectly through a MIX channel.</li>
</ol> </ol>
@ -87,7 +96,7 @@
<section2 topic="Participant Information in Presence" anchor="concept-participant-info"> <section2 topic="Participant Information in Presence" anchor="concept-participant-info">
<p> <p>
A MIX channel MAY distribute presence information about channel participants. In order to share JID and Nick information about a participant, this information is encoded in the presence message. This allows full presence information to be shared for each participant without the need for the client to perform any lookup. A MIX channel implementing this specification MUST be able to distribute presence information about channel participants. In order to share JID and Nick information about a participant, this information is encoded in the presence message. This allows full presence information to be shared for each participant without the need for the client to perform any lookup.
</p> </p>
</section2> </section2>
@ -98,9 +107,9 @@
Participants in Presence messages and in IQ messages relayed through a channel are identified by an encoded JID of the form are encoded, using the format "&lt;stable-participant-identifier&gt;#&lt;channel&gt;@&lt;mix domain&gt;". This provides a stable JID for each participant. This JID format is used in three places: Participants in Presence messages and in IQ messages relayed through a channel are identified by an encoded JID of the form are encoded, using the format "&lt;stable-participant-identifier&gt;#&lt;channel&gt;@&lt;mix domain&gt;". This provides a stable JID for each participant. This JID format is used in three places:
</p> </p>
<ol> <ol>
<li>The 'from' of presence stanzas generated by the channel.</li> <li>The 'from' of presence stanzas generated by the channel, where the from encodes the Stable Participant ID of the participant to which the presence stanza relates.</li>
<li>The 'to' of IQ stanzas being sent to the channel.</li> <li>The 'to' of IQ stanzas being addresses to a participant and being sent to the channel for indirect communication.</li>
<li>The 'from' of IQ stanzas coming from the channel.</li> <li>The 'from' of IQ stanzas coming from the channel, to reflect the sending participant where this stanza is being relayed by the channel.</li>
</ol> </ol>
<p> <p>
These JIDs will be used to represent specific JID clients. The resource associated with the encoded JID MUST be the resource value from the associated client JID, except where MIX-ANON is followed. These JIDs will be used to represent specific JID clients. The resource associated with the encoded JID MUST be the resource value from the associated client JID, except where MIX-ANON is followed.