Hi,
2016-11-01 5:57 GMT+01:00 Evgeny Khramtsov <[email protected]>: >> The by attribute should contain the archiving entity. For regular >> users the archiving entity is the user account itself. > > This was not clear for me. And is still unclear what "archiving > entity" means. That's why I put server's JID to "by". However, I don't > care and will put there any JID if the spec says so *clearly*. So currently the patch reads > The 'by'-attribute MUST by set to the JID of the archiving entity. For > regular user archives for instance this is the bare JID of the account and > for MUC this is the room’s bare JID. Ok you are right. I think I was introducing a new phrase with the 'archiving entity.' I changed my PR to use the phrase 'address of the archive' instead which is used in the sections before. https://gultsch.de/xep-0313.html#archives_id I hope the section is clear enough. @Evgeny: In case this wasn't clear I didn't just decide whether the by-attribute should contain the user jid or the server jid. Instead this is something that comes logically when you read the rest of the XEP (disco is also being announced on the same jid). In fact I even copied the old archived-id example which also sets the by-attribute the the account jid. cheers Daniel _______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: [email protected] _______________________________________________
