[Standards] Dealing with the choice to have a different MIX roster format

Florian Schmaus flo at geekplace.eu
Thu Jun 15 14:10:27 UTC 2017


On 15.06.2017 16:03, Florian Schmaus wrote:
> On 15.06.2017 14:20, Steve Kille wrote:
>> Jonas,
>>
>> I've gone with your option #4, as this seems clean, does not add roundtrips and avoids other issues.   
>>
>> Change in:
>>    https://github.com/stevekille/xeps/commit/da21b293484855e9ab2b58f11a749eab37dc66f9
> 
> This change introduces non-standard compliant XMPP. IQs are required to
> have at most one XML child element.
> 
> Instead of
> 
> <iq from='juliet at example.com/balcony'
>           id='bv1bs71f'
>           type='get'>
>        <query xmlns='jabber:iq:roster'/>
>        <mix-info-request xmlns=‘urn:xmpp:mix:0'/>
> </iq>
> 
> you want
> 
> <iq from='juliet at example.com/balcony'
>           id='bv1bs71f'
>           type='get'>
>        <query xmlns='jabber:iq:roster'>
>          <mix-info-request xmlns=‘urn:xmpp:mix:0'/>
>        </query>
> </iq>

I'd also s/mix-info-request/mix/.

- Florian

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 642 bytes
Desc: OpenPGP digital signature
URL: <http://mail.jabber.org/pipermail/standards/attachments/20170615/333b6f44/attachment.sig>


More information about the Standards mailing list