From 9d5d201be9f0ac9b7fc03fe91d4aad58d0fdbb06 Mon Sep 17 00:00:00 2001
From: Steve Kille <steve.kille@isode.com>
Date: Fri, 16 Jun 2017 07:14:17 +0100
Subject: [PATCH] New roster namespace

---
 xep-0369.xml | 9 +++++----
 1 file changed, 5 insertions(+), 4 deletions(-)

diff --git a/xep-0369.xml b/xep-0369.xml
index 233943cb..6dcd7432 100644
--- a/xep-0369.xml
+++ b/xep-0369.xml
@@ -48,6 +48,7 @@
       Extend Roster Get to select format;
       Ensure that text defining attributes and elements reference the namespace;
       Change mix_nick_register to nick-register;
+      Separate namespace for roster information;
     </p></remark>
   </revision>
   <revision>
@@ -2529,13 +2530,13 @@ This approach  enables flexible support of multiple clients for a MIX channel pa
   </section2>
 
   <section2 topic="MIX Roster Item Capability Sharing" anchor="mix-roster-capability-sharing">
-    <p>It is useful for a MIX client to know which roster members are MIX channels, as this will facilitate convenient presentation of subscribed MIX channels to the user.  A MIX client MAY request that the server return this additional information. The server MUST return the additional information. The request is made by extending the standard roster get request by adding a child element &lt;mix-info-request/&gt; to the &lt;query/&gt; element.  The &lt;mix-info-request/&gt; is qualified by the ‘urn:xmpp:mix:0' namespace.</p>
+    <p>It is useful for a MIX client to know which roster members are MIX channels, as this will facilitate convenient presentation of subscribed MIX channels to the user.  A MIX client MAY request that the server return this additional information that annotates roster elements with MIX capability. The server MUST return the additional information. The request is made by extending the standard roster get request by adding a child element &lt;annotate/&gt; to the &lt;query/&gt; element.  The &lt;mix-info-request/&gt; is qualified by the ‘urn:xmpp:mix:roster:0' namespace.</p>
     <example caption="Roster Get Requesting MIX Information"><![CDATA[
 <iq from='juliet@example.com/balcony'
           id='bv1bs71f'
           type='get'>
        <query xmlns='jabber:iq:roster'>
-              <mix-info-request xmlns=‘urn:xmpp:mix:0'/>
+              <annotate xmlns=‘urn:xmpp:mix:roster:0'/>
        <query/>
      </iq>
 ]]></example>  
@@ -2546,12 +2547,12 @@ This approach  enables flexible support of multiple clients for a MIX channel pa
 ]]></example>
 
     <p>
-      MIX channels in the roster information returned in response to a request for this additional MIX information MUST have an element &lt;channel/&gt; qualified by the ‘urn:xmpp:mix:0' namespace  included in the roster item, as shown inf the following example.
+      MIX channels in the roster information returned in response to a request for this additional MIX information MUST have an element &lt;channel/&gt; qualified by the ‘urn:xmpp:mix:roster:0' namespace  included in the roster item, as shown inf the following example.
     </p>
 
     <example caption="Roster Item Encoding of a MIX Channel"><![CDATA[
   <item jid='balcony@example.net'>
-      <channel xmlns=‘urn:xmpp:mix:0'/>
+      <channel xmlns=‘urn:xmpp:mix:roster:0'/>
   </item>
 ]]></example>