I would say that both versions say no body element in the message stanza, however the original could have been interpreted as no body content to the message but a body in the subject would be ok. Which is probably why it's been cleared up I expect.

That's my view on it, no <body> at all when changing subject of a muc room.

Cheers

Kirk

On 9 Jun 2010, at 19:06, "Alejandro R. Sedeño" <[email protected]> wrote:

Hi all,

I was just noticing that some phrasing in XEP-0045 changed since I last
looked at it.

In v1.22, Section 8.1 (Modifying the Room Subject) read:

"…The subject is changed by sending a message of type "groupchat" to the
<r...@service>, containing no body but a <subject/> that specifies the
new subject:"

Since v1.23, Section 8.1 (Modifying the Room Subject) reads:

"…The subject is changed by sending a message of type "groupchat" to the
<r...@service>, where the <message/> MUST contain a <subject/> element
that specifies the new subject but SHOULD NOT contain any other element
(e.g., no <body/> element or <thread/> element)."

A client I work on, BarnOwl [1], has been, perhaps incorrectly, using
the former wording to allow for a <subject/> element along with a
<body/> element to indicate a subject for the particular message,
without changing the topic of MUC. This is used to emulate a feature
that every IM since Zephyr [2] is lacking, which allows for multiple
threaded conversations to exist in a single forum [3].

I'm interested in getting feedback on this usage and perhaps getting it
standardized.

Thanks,
-Alejandro

[1] http://barnowl.mit.edu/
[2] http://en.wikipedia.org/wiki/Zephyr_%28protocol%29
[3] http://stuff.mit.edu/afs/sipb/project/doc/izephyr/html/node23.html

Reply via email to