diff --git a/xep-0369.xml b/xep-0369.xml
index db510fa0..8ab1655e 100644
--- a/xep-0369.xml
+++ b/xep-0369.xml
@@ -35,6 +35,12 @@
Minor editorial fixes MIX is specified as a family of XEPs that address the full set of requirements. Only two of these XEPs are mandatory for providing a MIX service. The others provide additional services and are used when these additional services are required. Each of these specifications has a short name, which is used to refer the specific XEP. The term MIX is used to refer to the family of XEPs. MIX is extensible, and it is anticipated that further XEPs will be added to this family. The XEPs are:
MIX will enable a wide range of auxiliary services. The goal of the MIX family of specification is to set out the core capabilities needed for MIX. It is anticipated that additional XEPs will be written to extend the current MIX specification, and the MIX specification family notes some areas where this may happen. Profiles referencing sets of related MIX XEPs may be developed in the future.
MIX defines a number standard nodes, and this specification defines three of these nodes and the framework for adding further nodes.
+ MIX defines a number of standard nodes, and this specification defines three of these nodes and the framework for adding further nodes.
-
-
@@ -655,15 +660,15 @@
It may be useful for clients to read the participants list. However it is not necessary for message and presence display, as both messages and presence contain sufficient information to enable display.
Name Node Description Update Distribution
- Messages 'urn:xmpp:mix:nodes:messages' For distributing messages to the channel. Each item of this node will contain a message sent to the channel. Message Message
-
+ Participants 'urn:xmpp:mix:nodes:participants' For storing the list of participants and the associated nick. Channel participants are added when they join the channel and removed when they leave Join/Leave/Set Nick PubSub Participants 'urn:xmpp:mix:nodes:participants' For storing the list of participants and the associated nick. Channel participants are added when they join the channel and removed when they leave. Join/Leave/Set Nick PubSub Information 'urn:xmpp:mix:nodes:info' For storing general channel information, such as description. PubSub 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. + Users MAY subscribe to, and read information from 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.
The participants node is MANDATORY. The Participants node is a permanent node with one item per participant.
A MIX service MUST NOT advertise support for &xep0313;, as MAM is supported by the channels and not by the service. A MIX service MUST NOT advertise support for generic &xep0060;, as although MIX makes use of PubSub it is not a generic PubSub service.
@@ -1058,7 +1063,7 @@- A user MAY subsequently modify subscription to nodes in a channel by sending a subscription modification request encoded as a <update-subscription/> child element of <iq/> element. The <update-subscription/> element is qualified by the 'urn:xmpp:mix:core:1' namespace. The requested notes are encoded as <subscribe/> child elements of the <update-subscription/> element with the node name encoded as a 'node' attribute. This modification goes directly from client to MIX channel, as this change does not impact the roster and so does not need any local action. The following example shows subscription modification. + A user MAY subsequently modify subscription to nodes in a channel by sending a subscription modification request encoded as a <update-subscription/> child element of <iq/> element. The <update-subscription/> element is qualified by the 'urn:xmpp:mix:core:1' namespace. The requested nodes are encoded as <subscribe/> child elements of the <update-subscription/> element with the node name encoded as a 'node' attribute. This modification goes directly from client to the MIX channel, as this change does not impact the roster and so does not need any local action. The following example shows subscription modification.