Proposed XMPP Extension: Data Forms File Input Element
The XMPP Extensions Editor has received a proposal for a new XEP. Title: Data Forms File Input Element Abstract: This specification defines an element which can be used with data forms to let users upload one or more files. URL: https://xmpp.org/extensions/inbox/data-form-file-element.html The Council will decide in the next two weeks whether to accept this proposal as an official XEP.
Good evening. I am supportive of this XEP. I will be one of the firsts to implement it, once project Slixmp has support for it. Currently, I use Gemini, HTTP or IPFS URIs in order to input data over Data Forms, and this extension would singnificantly facilitate this task. Kind regards, Schimon On Mon, 16 Jun 2025 16:09:27 -0000 Daniel Gultsch <daniel@gultsch.de> wrote:
The XMPP Extensions Editor has received a proposal for a new XEP.
Title: Data Forms File Input Element Abstract: This specification defines an element which can be used with data forms to let users upload one or more files.
URL: https://xmpp.org/extensions/inbox/data-form-file-element.html
The Council will decide in the next two weeks whether to accept this proposal as an official XEP. _______________________________________________ Standards mailing list -- standards@xmpp.org To unsubscribe send an email to standards-leave@xmpp.org
Hi, Since there hasn't been much activity on this thread, I decided to drop in and express my interest as well. I have been mulling the idea of an ecommerce website which can be managed through Ad-Hoc commands and Data Forms, and this XEP would make it possible to upload product images as well. There has been some debate about the necessity of the <use> element. My thoughts on it: I like the idea because it avoids an additional file transfer from the client's own upload service to whichever one is used by the entity accepting data forms. This will help reduce the load on the client's server, which could be important if the client's server has low resources (eg. selfhosted or serving a small group) and/or if the entity serving the form wants to transfer very large files like videos or something. Since <use> is optional (as goffi has indicated in chats), it shouldn't cause development overhead, as clients can just choose not to implement it, but remains an option in cases where it's helpful. To prevent confusion, it would help if <use> being optional was explicitly mentioned under Section 3 <https://xmpp.org/extensions/inbox/data-form-file-element.html#file-input> where it is introduced. I'm not familiar enough with the Jingle File Transfer or HTTP File Upload to comment on the specifics. I will get back with my comments (if any) after reading the relevant XEPs. Best, Badri
participants (3)
-
Badri Sunderarajan -
Daniel Gultsch -
Schimon Jehudah