On 1 Mar 2019, at 09:18, Dave Cridland <[email protected]> wrote:
>
>
>
> On Fri, 1 Mar 2019 at 08:35, Ненахов Андрей <[email protected]
> <mailto:[email protected]>> wrote:
> This was discussed in July 2018 and, I guess, moved nowhere, but I'll raise
> the issue once again. Any decent messenger bar XMPP based ones have
> capabilities to signal type of user activity beyond just "composing a
> message", but also "recording voice message", "recording video message",
> "uploading file", ....
>
> We NEED that in our clients, and, subsequently, we'd prefer it to be an XMPP
> standard.
>
> So far we've extended XEP-0085 by adding a "type" attribute to <composing>
> element:
> <message
> from='[email protected] <mailto:[email protected]>/pda'
> to='[email protected] <mailto:[email protected]>/elsinore'
> type='chat'>
> <composing type='audio' xmlns='http://jabber.org/protocol/chatstates'/
> <http://jabber.org/protocol/chatstates'/>>
> </message>
>
>
> Counter-proposal:
>
> <composing xmlns='...'>
> <subtype xmlns='something-else' type='audio'/>
> </composing>
>
> I believe this should work fine and means we're not changing XEP-0085 (which
> is, indeed, Final).
I don’t immediately see issues with this.
/K
_______________________________________________
Standards mailing list
Info: https://mail.jabber.org/mailman/listinfo/standards
Unsubscribe: [email protected]
_______________________________________________
