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

Steve Kille steve.kille at isode.com
Thu Jun 15 14:24:49 UTC 2017


Florian,

Ooops and thanks.

Fixed by:
  https://github.com/stevekille/xeps/commit/6779a94b0e5257c94dadd4a6d13aefaa21d2068a


Steve


> -----Original Message-----
> From: Standards [mailto:standards-bounces at xmpp.org] On Behalf Of Florian
> Schmaus
> Sent: 15 June 2017 15:03
> To: XMPP Standards
> Subject: Re: [Standards] Dealing with the choice to have a different MIX
> roster format
> 
> 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/da21b293484855e9ab2b58f11a7
> 4
> > 9eab37dc66f9
> 
> 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>
> 
> - Florian




More information about the Standards mailing list