[Standards] XEP-136 and XEP-59 implementation comments: threading

Peter Saint-Andre stpeter at stpeter.im
Fri May 9 22:14:52 UTC 2008

On 05/09/2008 7:59 AM, Alexander Tsvyashchenko wrote:
> Hello Peter,
>>> Ok, but "parent" linking for collections still needs to be added to
>>> XEP-136 if you agree with the approach we've discussed.
>> I think it's too early to specify that in XEP-0136, because the "parent"
>> stuff is just a suggestion in XEP-0201. But if XEP-0201 moves forward
>> then we can add it to XEP-0136.
> Ok, that sounds logical - currently it's more or less "advanced" thing
> anyway, "thread" element is not used in some of the major Jabber clients
> till now even without "parent" link ...


>> Alexander, does XEP-0136 incorporate all your other feedback?
> Yes, it seems so. The issues left, as far as I remember, are either for
> other XEPs or broader than just XEP-136:
> 1) JIDs matching: the conclusion seemd to be to use 'exactMatch'
> attribute (?), but as you've pointed out this is the problem not only
> for XEP-136.

I added that:


I still need to add it for privacy lists and MUC if we feel it is
valuable there.

> 2) 'changed' element in RSM responses: was agreed to be not critically
> important right now, and belongs to XEP-59 anyway.

Yes perhaps we need to look at XEP-0059 next. :)


Peter Saint-Andre

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

More information about the Standards mailing list