Le jeudi 21 novembre 2024, 17:01:12 heure normale d’Europe centrale Daniel 
Gultsch a écrit :
> The XMPP Extensions Editor has received a proposal for a new XEP.
> 
> Title: MUC Slow Mode
> Abstract:
> This specification describes a way to rate limit messages a single
> user can send to a MUC room. It includes room configuration option,
> and how servers and clients can handle such a feature.
> 
> URL: https://xmpp.org/extensions/inbox/xep-slow-mode.html
> 
> The Council will decide in the next two weeks whether to accept this
> proposal as an official XEP.
> _______________________________________________
> Standards mailing list -- [email protected]
> To unsubscribe send an email to [email protected]
> 

Hello,

thank you for your contribution! This is a useful feature and we can 
appreciate the effort put in this protoXEP.

I've a few small remarks regarding this specification:

- Glossary redefines many terms from XEP-0045. There is no need for that, it 
makes the specification more difficult to read, and it duplicates information. 
Just add a note to reference XEP-0045.

- In https://xmpp.org/extensions/inbox/xep-slow-mode.html#example-1 there is a 
confusion between label and description. Label should be a simple "Slow Mode", 
and <desc> should be used for the description (cf. https://xmpp.org/
extensions/xep-0004.html#protocol-field). It's just an example, but if 
developer copy it, it will result in bad UX for end-users.

- The topic "Client Handling" is missing an anchor, resulting in ugly URL such 
as https://xmpp.org/extensions/inbox/xep-slow-mode.html#sect-idm46190554600112 
.

- At  
https://xmpp.org/extensions/inbox/xep-slow-mode.html#sect-idm46190554660208 
(anchor is missing here too), those 2 lines contradict 
themselves:

> This field SHOULD use Data Forms Validation , having its datatype equal to ' 
xs:integer'.
>
> The 'value' of the field MUST be a positive integer, so you MUST add a 
'range' validation, as described in Data Forms Validation (XEP-0122) [3]. 

You say that Data Forms Validation is a "SHOULD", but below that you "MUST" 
add a "range" validation. You need either 2 SHOULD or 2 MUST.

- In the same section the link to "client-discovering" is incorrect and 
results in a 404.

Best,
Goffi

Attachment: signature.asc
Description: This is a digitally signed message part.

_______________________________________________
Standards mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to