Reconciliate XEP-0317: Hats and ejabberd MUC Hats #4380
Description
ejabberd is now implementing XEP-0317: Hats but with some specificity documented in https://docs.ejabberd.im/tutorials/muc-hats/
This require clients to maintain ejabberd specific implementations which creates quite messy code.
Proposal
Use accountjid and not jid as specified in the XEP
<field var='accountjid'
type='jid-single'
label='Jabber ID'>
<required/>
</field>When assigning use list-single hat and not separated text-single hat_title and 'hat_uri' as specified in the XEP
<field label='The role'
type='list-single'
var='hat'>
<option label='Teacher'><value>http://tech.example.edu/hats#Teacher</value></option>
<option label='Teacher's Assistant'><value>http://tech.example.edu/hats#TeacherAssistant</value></option>
<option label='Test Proctor'><value>http://tech.example.edu/hats#Proctor</value></option>
</field>The client doesn't have to "show" the complex URI in its UI, only the label is important. By separating them in two text-single you force the client to hack things to hide the URI.
For now I'm putting my implementation in pause in Movim.
I've done an important PR on the XEP with several changes to integrate some of your proposals, see xsf/xeps#1437