Hi, Libervia is currently implementing XEP-0447 instead of SIMS as it is supposed to be a reiteration of XEP-0385. However, it can't currently handle multiple files in the same message because of §3.3 "Attaching a source" which uses the message ID (and thus we can only have one <file-sharing> element per <message>).
This can be easily fixed by adding an 'id' attribute to <file-sharing> element, allowing multiple <file-sharing> in a <message>, and update §3.3 to use the new 'id' and to make <sources> a child of <attach-to>. I think that multiple files in a single message should be part of XMPP, but I also need it for my ActivityPub Gateway, and I guess that Slidge and other gateways will have the same issue. An other point is that we should not have 2 XEPs doing nearly the same thing, thus we should deprecate either XEP-0385 or XEP-0447. Here are some points I've said on xsf@ room: - XEP-0385 depends on XEP-0372 (Reference), and while it may be nice to have a reference, it should be optional (it should be possible to have files available just as attachments). Also it's visible from the example, but not clear at all in the description, XEP-0372 is not even quoted in the XEP. - file-metadata has been split to XEP-0447 with XEP-0447, and this was the right thing to do instead of weirdly relying on Jingle FT stuff. - XEP-0447 has source attachment, which is a neat feature But all that could have been fixed directly on XEP-0385. Anyway, we have 2 really similar XEPs, please let's choose one right now transfer the authors from the other one and deprecate the later, and move on. I personally want something usable both for <message> and pubsub, and I like the source attachment feature. Reference to a message is nice, but should be optional IMO. I can make a PR in coming days, but which one should we chose? I propose to move on XEP-0447, transfer author from XEP-0385 there, and deprecate XEP-0385. Thanks, Goffi _______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: [email protected] _______________________________________________
