[Standards-JIG] JEP-0045 namespace changes

Peter Saint-Andre stpeter at jabber.org
Tue Feb 7 18:57:15 UTC 2006

Hash: SHA1

Constantin Nickonov wrote:
> Does anyone recall why the room configuration namespace change (ref.
> http://www.jabber.org/jeps/jep-0045.html#revs, Version 1.17) was made to
> JEP-0045 long after it was an accepted draft. As a result, existing
> implementations are in the unenviable position of choosing to keep the
> original implementation and fall out of compliance with the JEP (and
> thus, other implementations) or making the server-side change and
> leaving existing clients out in the cold.
> My recommendation would be to revert to the original namespaces, but I'm
> sure that this would probably cause similar problems for newer
> implementations. Any ideas or suggestions?

I agree that this change was probably unforutunate but I don't remember
why we made it -- perhaps there was a concern about confusion regarding
muc#user and muc#owner but I don't recall.

At this point it seems best to retain the change (MUC service
implementations could look for both the old and the new FORM_TYPEs, be
liberal in what you accept and all that) but I'm not wedded to that.
Perhaps it make sense to poll implementors to see what their preference
is (e.g., I doubt that mu-conference has been brought up to date).


- --
Peter Saint-Andre
Jabber Software Foundation

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

-------------- 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/20060207/64a68517/attachment.bin>

More information about the Standards mailing list