diff --git a/xep-0369.xml b/xep-0369.xml
index fafca180..abb48c25 100644
--- a/xep-0369.xml
+++ b/xep-0369.xml
@@ -678,8 +678,8 @@
]]>
- The channel responds with an IQ-result. This stanza includes the nodes to which the user has been successfully subscribed, as well as the bare JID that will be used for the user in this channel and added to the participant list. If a user cannot be subscribed to one or more of the requested nodes (e.g., because the node does not exist), but can be subscribed to some the response simply lists the nodes successfully subscribed. If none of the nodes requested are successfully subscribed to, an error response is sent indicating the reason that the first node requested was not subscribed to. This response will also include other nodes requested where subscription failed for the same reason. A user may subsequently request subscription to nodes in a channel to which the user was not initially subscribed, by repeating the join operation. If the user is already joined to a channel, the join operation simply modifies the channel subscriptions and settings to new values.
- The channel responds with an IQ-result. This stanza includes the nodes to which the user has been successfully subscribed, as well as the bare JID that will be used for the user in this channel and added to the participant list. The following example shows the result of the above request when the request is completed in full.
+
]]>
- As noted, the participant might not be subscribed to all nodes associated with the channel (in this case only messages, participants, and subject).
-
+ If a user cannot be subscribed to one or more of the requested nodes (e.g., because the node does not exist), but can be subscribed to some the response simply lists the nodes successfully subscribed. If none of the nodes requested are successfully subscribed to, an error response is sent indicating the reason that the first node requested was not subscribed to. This response will also include other nodes requested where subscription failed for the same reason. The following response example shows a response to the initial request example where
+the participant is not be subscribed to all nodes associated with the channel (in this case only messages, participants, and subject).
+
]]>
- The channel also adds the user to the participants node and sends a notification.
+ The channel also adds the user to the participants node and sends a notification to subscribers to the participants node.
Following the MIX server side processing, the user's server will usually add the MIX channel to the user's roster using one way presence. This means that the MIX channel will get presence information from the user. This roster entry will lead to correct handling of the user's presence in the MIX channel. If the user does not wish to publish presence and the channel permits this, then this roster addition does not happen. If the channel requires presence and the user removes the channel from the user's roster, the channel MAY remove the user as a channel participant.
+
+
+ A user may subsequently modify subscription to nodes in a channel by sending a subscription modification request, as shown in the following example.
+
+
+
+
+
+
+
+
+
+
+
+
+
+]]>
@@ -784,7 +814,7 @@
-
+
urn:xmpp:mix:0
@@ -804,6 +834,56 @@
The client may also query the channel in order to find out which user preferences are supported and the options available. This will allow users to set options not specified in the standard. The result is a form template.
+
+
+
+ urn:xmpp:mix:0
+
+
+ Never
+
+
+ Allow
+
+
+ Block
+
+
+
+
+
+
+
+
+ urn:xmpp:mix:0
+
+
+ Never
+
+
+ Allow
+
+
+ Block
+
+
+
+
+]]>
+
+
+ A user may modify preferences using the corresponding set operation.
+
+
+
+
]]>
-