On Tue, 2026-06-02 at 13:35 +0100, Dave Cridland wrote: > > > On Tue, 2 Jun 2026 at 10:54, Daniel Gultsch <[email protected]> > wrote: > > Title: Jingle User Location > > Abstract: > > This specification defines a Jingle application extension for > > negotiating and updating user location inside an active Jingle > > session > > using the XEP-0080 User Location payload. > > > > URL: https://xmpp.org/extensions/inbox/jingle-geoloc.html > > > > > I'm not wholly sure why this would need to be encapsulated in the > Jingle content description? > > Why wouldn't this be simply sent alongside in a message? (And, in > general, I'd like this - the WhatsApp location sharing in a chat > feature is very useful!)
This is not only a question of why, but also this is directly contradicting and incompatible to the nature of Jingle. Jingle is to initiate and maintain peer-to-peer session in form of specific application data transferred via a datagram or streaming transport between entities. Jingle has mandatory requirements for conformance and this specification does not comply with any of them https://xmpp.org/extensions/xep-0166.html#conformance If sending the location via actual Jingle is desirable (which is what the abstract claims the XEP specifies, but doesn't actually do), one option is to use XEP-0080 via XEP-0247. Alternatively, if Jingle is not really a requirement and inband is a good option, either the use of XEP-0080 via a PEP node with access restrictions could be an option, or a new specification to transfer XEP-0080 via <message/> as Dave suggested could also be interesting. Marvin
_______________________________________________ Standards mailing list -- [email protected] To unsubscribe send an email to [email protected]
