[Standards-JIG] JEP-0045 config field names

Peter Saint-Andre stpeter at jabber.org
Thu May 4 21:55:48 UTC 2006


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Heiner Wolf wrote:
> Hi,
> 
> in JEP-0045 I read in the configuration form example: <field 
> label='Make Room Moderated?' type='boolean' 
> var='muc#roomconfig_moderatedroom'> <value>0</value> </field>
> 
> The var used to be var='muc#owner_moderatedroom'. ejabberd's MUC
> sends and expects var='moderated'.
> 
> I understand that the var name is the service's choice. Is this
> correct?
> 
> This is ok as long as a natural or artificial intelligence looks at
> the label text and clicks the thing in a form. But if a client wants
> to set the value without presenting a form, then it must know the
> name. My client tries to set the 'Make Room Moderated' state
> programmatically. I don't know which var name to use. Depends on the
> MUC. I have to find out the MUC version and guess from that the
> variable name, which could change with any version. This is not good.
> 
> 
> Would it be possible to standardize in JEP-0045 a set of frequently
> used vars for MUC?

They already are standardized:

http://www.jabber.org/jeps/jep-0045.html#registrar-formtype-owner

IMHO ejabberd has a bug here (the configuration variable is *not*
"moderated").

I apologize for the change in variable names a while back (no more
"muc#owner_*") but we discussed this on the list and I think the
consensus was not to go back.

Peter

- --
Peter Saint-Andre
Jabber Software Foundation
http://www.jabber.org/people/stpeter.shtml

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFEWnhkNF1RSzyt3NURAmRyAKChiLKDgYTAJ+qE8mrbCxqmx+/OMQCeOGyK
tqoqNXIPR5k35Ek1qqTrfqc=
=WHEh
-----END PGP SIGNATURE-----
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3641 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://mail.jabber.org/pipermail/standards/attachments/20060504/f37fe9d7/attachment.bin>


More information about the Standards mailing list