|author||Steve Kille <email@example.com>||2018-01-02 09:52:42 +0000|
|committer||Steve Kille <firstname.lastname@example.org>||2018-01-02 09:52:42 +0000|
Participant's node join clarification & Join Clarificatons
1 files changed, 1 insertions, 1 deletions
diff --git a/xep-0369.xml b/xep-0369.xml
index 29db8b1..3db2f6c 100644
@@ -518,7 +518,7 @@ This approach enables flexible support of multiple clients for a MIX channel pa
<p>Each channel participant is represented as an item of the 'urn:xmpp:mix:nodes:participants' channel node. Each item is named by the bare proxy JID of the participant. For example 'email@example.com' might name the node item associated with participant 'firstname.lastname@example.org'. Information is stored in a <participant/> element qualified by the 'urn:xmpp:mix:1' namespace. The nick associated with the user is mandatory and is stored in a <nick/> child element of the <participant/> element. The nick for each channel participant MUST be different to the nick of other participants.
- When a user joins a channel, the user's bare JID is added to the participants node by the MIX service. When a user leaves a channel, they are removed from the participants node. The participants node MUST NOT be directly modified using pubsub.
+ When a user joins a channel, the user's bare proxy JID is added to the participants node by the MIX service. When a user leaves a channel, the user's bare proxy JID is removed from the participants node. The participants node MUST NOT be directly modified using pubsub.
Users MAY subscribe to and read information this node, when permitted by the channel. Standard PubSub access will allow a full list of participants and associated nicks to be determined. By subscribing to the node, a user will be informed of changes to the Participants Node.