[Standards-JIG] XEP-0136 Thoughts and Musings

Peter Saint-Andre stpeter at jabber.org
Tue Nov 7 19:55:40 UTC 2006

Chris Mullins wrote:
> Section 5.2 forbids logging Message Thread Identifiers. It seems like
> these would be very natural ways of grouping messages, and tagging with
> metadata. Many clients use these today. Why are they forbidden?

It seems good to include threads.

> Collections seem insufficient for given heavy IM usage over a long
> period of time. A Mechanism to tag collections with keywords and
> metadata seems needed. The <note/> mechanism that’s there seems
> insufficient. 

I doubt that tagging will be of great interest to most people, but for
those who care it would be a helpful feature.

> An automated mechanism for having the server create
> collections based on conversations, and dates seems like it would be good.

Does anything in the spec forbid that?

> Being able to add tasks and other items into these collections, such as
> “Task Item”, “Important!” or “Follow up on 11/29/2006” would be nice. I
> don’t want to spec all these now, but having a mechanism for adding them
> later is needed.

Are those messages to self, or annotations on existing messages? Perhaps
that's more a matter of application integration than XMPP message
archiving per se.

> Conversations that migrate from 1:1 to MUC don't seem to be addressed.

You mean server-side logging of MUC rooms? That seems to be the
responsibility of the MUC service, no? But it might be helpful for an
application to note somehow that the 1-1 morphed into a MUC.


Peter Saint-Andre
Jabber Software Foundation

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 7358 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://mail.jabber.org/pipermail/standards/attachments/20061107/38eead4a/attachment.bin>

More information about the Standards mailing list