Am Mittwoch, den 21.10.2020, 16:28 +0100 schrieb Dave Cridland: > > This specification is primarily intended for, and used for, the > purpose of transferring a file from one user to another. > > In practise, the clients upload a file, thereby obtaining a URL, and > pass that URL somehow to the other party. > > My question - and it is a question - is whether we ought to be > advancing this specification when its usage is contingent on the > proper definition of that "somehow". > > I can see arguments both ways - this can be used independently, after > all, but it's primary use is as part of the "complete breakfast" of > file transfer. Advancing something to Final which is habitually only > used with a somewhat undocumented use of OOB (XEP-0066) feels a bit > wrong, but there's technically nothing incorrect by process in doing > so. > > So what do we feel as a group?
I was going to raise similar question, even drafted the response. because I've seen this challenge while implementing client side. But then re-read the spec, thought it over again, and removed the question. Because it has nothing to do with this spec. It's more to OOB itself. --rr
_______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: standards-unsubscr...@xmpp.org _______________________________________________
