xep-500: first feedbacks.

xep-0500.xml

@@ -40,6 +40,14 @@
     <email>[email protected]</email>
     <jid>[email protected]</jid>
   </author>
+  <revision>
+    <version>0.1.1</version>
+    <date>2024-12-03</date>
+    <initials>jl</initials>
+    <remark>
+      <p>Include first feedbacks</p>
+    </remark>
+  </revision>
   <revision>
     <version>0.1.0</version>
     <date>2024-11-28</date>
@@ -90,68 +98,16 @@
   </ul>
 </section1>
 <section1 topic='Glossary' anchor='glossary'>
+  <p>
+    Many terms used in this XEP are defined in &xep0045; and &xep0128;. Please refer to these XEP for more informations.
+  </p>
   <dl>
     <di>
       <dt>Clients</dt>
       <dd>
         The client software used by end-users to join MUC rooms.
       </dd>
     </di>
-    <di>
-      <dt>Moderator</dt>
-      <dd>
-        A room role that is usually associated with room admins but that can be
-        granted to non-admins.
-      </dd>
-    </di>
-    <di>
-      <dt>MUC</dt>
-      <dd>
-        The multi-user chat protocol for text-based conferencing
-        (e.g. &xep0045;).
-      </dd>
-    </di>
-    <di>
-      <dt>Participant</dt>
-      <dd>
-        An occupant who does not have admin status; in a moderated room,
-        a participant is further defined as having voice (in contrast to a
-        visitor).
-        A participant has a role of "participant".
-      </dd>
-    </di>
-    <di>
-      <dt>Role</dt>
-      <dd>
-        A temporary position or privilege level within a room, distinct from a
-        user's long-lived affiliation with the room; the possible roles are
-        "moderator", "participant", and "visitor" (it is also possible to have
-        no defined role). A role lasts only for the duration of an occupant's
-        visit to a room. See &xep0045;.
-      </dd>
-    </di>
-    <di>
-      <dt>Room administrator</dt>
-      <dd>
-        A user empowered by the room owner to perform administrative functions
-        such as banning users; however, a room administrator is not allowed to
-        change the room configuration or to destroy the room. An admin has an
-        affiliation of "admin". See &xep0045;.
-      </dd>
-    </di>
-    <di>
-      <dt>Room owner</dt>
-      <dd>
-        Users that have special access to a room, and that can edit room
-        configuration. See &xep0045; - Owner Use Cases.
-      </dd>
-    </di>
-    <di>
-      <dt>Service Discovery Extensions</dt>
-      <dd>
-        See &xep0128;
-      </dd>
-    </di>
     <di>
       <dt>Slow Mode</dt>
       <dd>
@@ -165,13 +121,6 @@
         seconds, users must wait between two text messages.
       </dd>
     </di>
-    <di>
-      <dt>Visitor</dt>
-      <dd>
-        In a moderated room, an occupant who does not have voice (in contrast to
-        a participant). A visitor has a role of "visitor".
-      </dd>
-    </di>
   </dl>
 </section1>
 <section1 topic='Use Cases' anchor='usecases'>
@@ -183,7 +132,7 @@
   </p>
 </section1>
 <section1 topic="MUC configuration" anchor="muc-configuration">
-  <section2 topic="Activating Slow Mode in the MUC Room configuration">
+  <section2 topic="Activating Slow Mode in the MUC Room configuration" anchor="muc-configuration-activation">
     <p>
       Your implementation MAY allow the Slow Mode feature to be set room by
       room, by their owners.
@@ -197,7 +146,7 @@
       This field MUST have its type equal to <tt>'text-single'</tt>.
     </p>
     <p>
-      This field SHOULD use
+      This field MUST use
       <link url="https://xmpp.org/extensions/xep-0122.html">
         Data Forms Validation
       </link>, having its datatype equal to <tt>'xs:integer'</tt>.
@@ -238,8 +187,9 @@
       <field
         var='muc#roomconfig_slow_mode_duration'
         type='text-single'
-        label='Slow Mode (0=disabled, any positive integer= users can send a message every X seconds.)'
+        label='Slow Mode'
       >
+        <desc>0=disabled, any positive integer= users can send a message every X seconds.</desc>
         <validate xmlns='http://jabber.org/protocol/xdata-validate' datatype='xs:integer'>
           <range min='0'/>
         </validate>
@@ -398,11 +348,11 @@
     The rejected message MUST NOT be forwarded to other room occupants.
   </p>
 </section1>
-<section1 topic="Client handling">
+<section1 topic="Client handling" anchor="client-handling">
   <p>
     When a participant joins a room, the client SHOULD request room information
     as described in section
-    <link url="client-discovering">Client discovering</link>", and look for the
+    "<link url="#client-discovering">Client discovering</link>", and look for the
     <tt>'muc#roominfo_slow_mode_duration'</tt> field.
   </p>
   <p>
@@ -447,7 +397,7 @@
   </p>
 </section1>
 <section1 topic='XMPP Registrar Considerations' anchor='registrar'>
-  <section2 topic="Field Standardization">
+  <section2 topic="Field Standardization" anchor="registrar-field-standardization">
     <p>
       &xep0068; defines a process for standardizing the fields used within Data
       Forms scoped by a particular namespace, and the XMPP Registrar maintains a
@@ -483,7 +433,7 @@
   <field
     var='muc#roomconfig_slow_mode_duration'
     type='text-single'
-    label='Slow Mode (0=disabled, any positive integer= users can send a message every X seconds.)'
+    label='Slow Mode'
   />  
 </form_type>
 ]]></example>
@@ -502,7 +452,7 @@
   </desc>
   <field
     var='muc#roominfo_slow_mode_duration'
-    label='Slow Mode (0=disabled, any positive integer= users can send a message every X seconds.)'
+    label='Slow Mode'
   />  
 </form_type>
   ]]></example>